Identity & SSO
OIDC tokens gate every route; tenant binding comes from the token.
The platform
SkyForge is the app plane of a 60-service sovereign platform. The five product surfaces below expose 148 real operations; each is a backend with its own contract. Below them sit the integrated services every deploy composes.
Capability groups
Each card links to a deep-dive: what it does, its real sub-capabilities, the full method+path endpoint catalog, a worked example, and where it sits in the architecture.
Push a repo; get a governed, routable app.
The unit of ownership is an App — {name, repo, branch} inside a tenant. Around it hangs everything that keeps a deploy safe: a resumable deploy saga, secure admission, revisions and rollback, autoscaling, crons, PR previews, a full CI/CD control plane, self-hosted runners, DBaaS/secret addons and a sovereign-exit export.
Hermetic builds with waved agent autonomy.
The sovereign build rail underneath SkyForge. A build run moves through source → built → gating → merged; builds fail closed on any non-hermetic dependency, provenance is signed, and the merge decision requires unanimous green gates. Self-approval is impossible by construction — the approver identity comes from edge-stamped headers, never a body field (FAC09).
A leased environment per PR — reclaimed on its own.
Disposable environments with a lease lifecycle: PR previews, seeded sandboxes and demo environments, each governed by teardown policies, cost guardrails and expiring-lease sweeps. Every environment carries a cost estimate and can attach evidence, so an ephemeral env is auditable rather than a leak waiting to happen.
Declare a backend; get collections, functions and an SDK.
Provision a complete backend from a single declaration: schema-bound collections with fail-closed row policies, declared buckets, and Knative-semantics functions with scale-to-zero and per-invocation metering. Production engines — Hasura, Directus, Cosmo, Temporal, Authentik, RustFS — are composed automatically as fail-loud adapters (BAAS16), reused, never installed in parallel.
Run a suite; produce signed release evidence.
The test and device lab behind a release: suites and test runs, a real-device farm with reservations and sessions, performance budgets, accessibility audits, flaky-test quarantine and human-in-the-loop sessions. A quality-gate evaluation turns run results into a pass/fail verdict, and release evidence is retrievable per release for audit.
Integrated services
Identity, secrets, databases, supply-chain admission, observability and billing are first-class platform services — an app gets them the moment it exists, governed by the same tenancy and audit model.
OIDC tokens gate every route; tenant binding comes from the token.
Addons are database claims — Postgres, distributed SQL, cache, object, search.
Cosign signature + SBOM + scan admission for every image.
Secret custody; the platform stores refs, never credentials.
Metrics ticks drive autoscale; audit is fanned here.
Auto-rollbacks emit incidents to the AIOps feed.
The independent pre-deploy gate verdict.
vCPU-hr / GB-hr / egress metered per second.
Metered usage rolls up into transparent billing.
SkyForge is SS-47 on the StratoGroup platform — SkyForge is one of 60 governed services on the StratoGroup sovereign platform. The five surfaces on this portal expose 148 real operations; the platform as a whole exposes 1,420.