Platform
The LongLink Platform owns the shared operating model. It stores users, organizations, memberships, applications, infrastructure registries, reconciliation Operations, and deployment state, then exposes the API and web shell used to manage them.
It does not replace application code. Applications still run as separate SDK services; the LongLink Platform provides the governed layer around them: identity, access decisions, resource provisioning, routing, rollout verification, logs, and status.
Production runtime traffic is mediated by the API proxy and the per-compute TLS gateway. The API authorizes the user and forwards approved requests with trusted runtime headers; the gateway accepts only authenticated proxy traffic and routes it to the internal application service.
Shared Foundation
| Capability | Platform responsibility |
|---|---|
Authentication | Email, password, OAuth, OIDC, sessions, and current-user context. |
Organizations | Tenant boundaries, memberships, and organization resources. |
Permissions | Organization and application roles enforced before runtime access. |
Languages | Locale-aware web shell and application page rendering. |
Theming | Shared visual system and user interface preferences. |
Application shell | Consistent navigation around platform and runtime pages. |
Application contract | Metadata, routing, deployment, logs, and runtime access for application services. |
Databases | Organization databases, shared schemas, and application schemas. |
Storage | One S3-compatible bucket per Organization, with shared and application prefixes. |
Routing | Gateway-backed routing from authenticated users to internal application services. |
Deployment | Container image inspection, Kubernetes resources, and rollout verification. |
Logs | Runtime log access for deployment checks and troubleshooting. |
Status | Application, registry, and operation state tracked by the platform. |