Astrogate platform guide
Documentation version: 858adedd187db2e94614b1dfd389e4bf98e6e202:ac5d527caaa1f97eee9d71262e7c843ae7b24000e01ba5b44931108b2b489c0d
Astrogate supplies reusable infrastructure through a scoped management API and an application SDK. A consumer product owns its own interface, user onboarding and commercial policy. It does not write to infrastructure databases, provider APIs or Kubernetes directly.
The current validated release supports the controlled Linux ARM64 Shared profile for Next.js and React/Vite, with database, application identity, files, Git, versioned jobs and schedules. Registered installation policy determines which capabilities are actually available. A tested source implementation is not a public SaaS signup, an npm registry release or an availability guarantee.
Start here
- Follow your first application using an authorized installation and an explicitly selected Preview environment.
- Choose the correct SDK entrypoint for management, browser, React, application server or read-only operator inventory.
- Use the database, identity, files, jobs and schedules and Git guides for actual supported behavior.
- Follow hosting, deployments and routing before exposing an application.
- Use operation recovery for pending work, errors, compatible rollback and capacity exhaustion.
Three different authorities
| Client | Authority | Keep private |
|---|---|---|
| Consumer server | Registered technical tenant/project/environment and management capabilities | Management credential and deployment policy |
| Application browser/server | Native application user session plus explicit resource grants | Issuer credentials and server-only service sessions |
| Infrastructure operator | Personal operator login or separately issued read-only inventory scope | Provider, installation, database and recovery credentials |
A database UUID, Git branch, domain name, NODE_ENV or astrogate.json cannot
grant any of those permissions. Production is always an explicit authorized
environment. Preview data, credentials and external effects remain separate.
Reference and support boundary
The API reference is generated from the same OpenAPI source as Go/TypeScript
transport models. The SDK guide links that reference and explains
native-client type inference. HTML, per-page Markdown, search, exports,
llms.txt and the documentation MCP use the same versioned publication selection.
Documentation access never grants infrastructure management access.
Operator procedures require operator authentication. Implementation-source and validation links can require access to the private infrastructure repository. The supported-profile record owns exact evidence. Cold recovery permits interruption and post-checkpoint loss; continuous customer HA, untested isolation profiles, offline operation and other providers are not implied by these guides.