Your first application

This route connects the existing management and application interfaces. Start with a configured installation; it is not an unattended cloud installer or a customer account-registration flow.

PrerequisitesCopy Anchor Link

The installation owner supplies its management HTTPS origin, trusted consumer identity, technical tenant, allowed locations/capacity profiles and credential delivery mechanism. Source integration also needs an approved repository/check policy. Receive credentials through protected server configuration, never chat, application source, browser environment variables or Git remote URLs.

Use the SDK and maintained native clients from the same reviewed source release. The package is currently private source; the SDK setup guide explains preparation. Supported framework and engine versions live in the owning guides and release manifests. Do not silently substitute another version or an upstream cloud SDK.

Admit a project through the management APICopy Anchor Link

Initialize createManagement in your consumer's server with the operator-supplied endpoint, tenant and scoped credential. Persist one logical idempotency key before submitting a mutation. management.projects.create({name}, options) returns a durably accepted operation. Poll management.operations.get(operationId) within your caller's observation budget. Acceptance does not mean an application or database is already running.

Read the created project and its environment inventory through that same client. Select Preview explicitly. Read placement policy/locations and establish the authorized allocation before requesting dependent services. The placement guide contains the implemented arguments and revision checks. A missing policy or physical capacity is an actionable admission failure, not permission to buy a server or choose another tenant's cell.

Declare portable requirementsCopy Anchor Link

Commit astrogate.json alongside the application source:

{
  "version": 1,
  "framework": "next",
  "database": { "initializationRef": "sha256:<reviewed-plan-digest>" }
}

Replace the placeholder with a registered schema/permission initialization plan. Use vite for the supported React/Vite lane. This manifest declares portable requirements only. Installation addresses, credentials, domain registrations, capacity grants and resolved environment bindings remain separate inputs. Optional test datasets require explicit safe Preview/Staging registration.

Start an authorized workspaceCopy Anchor Link

Use the installation's astrogate-dependencies CLI and protected target file. The hosting guide documents exact start/status/stop arguments and the local-application alternative. The controller resolves declared dependencies, checks readiness and starts or reuses the scoped workspace. SDK imports do not launch engines or choose a target.

Open the returned protected Preview URL. Use resolved public bindings in the browser and request-scoped sessions on the application server. Follow database usage and identity for native schema inference, login, permissions and logout. A ready engine does not make a user authorized.

Build and publish a releaseCopy Anchor Link

Use a checked source revision and the registered GitHub/Forgejo policy through the shared deployment operation. The same coordinator builds the immutable artifact, checks the candidate, switches traffic and drains the previous release. Do not add deployment scripts to each framework, Git platform or consumer product.

Production uses a separate explicit authorized environment. A branch label cannot select it. Before publication, register the exact domain and binding, review schema/permission compatibility and verify Production credentials/data are not copied from Preview. Follow routing for hostname and TLS readiness. A compatible application rollback does not undo database writes.

Verify and recoverCopy Anchor Link

Verify the actual HTTPS application, a permitted database read/write, file access where enabled, and denied access from another environment. Retain operation IDs and source/artifact references rather than treating a rendered page as the full acceptance check. Operations explains logs, retries, waiting states, quota failures and safe recovery. Stop retains workspace source/data; deletion and retention-aware cleanup are explicit separate operations.