Skip to main content
Reliant

Reliant Cloud

Hosting, releases and observability for apps built with agents.

Reliant Cloud is a hosting and delivery platform, like GitLab, Vercel and Supabase in one, that runs what you ship with Forge and monitors it.

It hosts your app and its database, builds each release once and promotes it through your environments, and watches what it runs, with the evidence your agent needs to fix what breaks.

Part 1 of 6

Hosting

Reliant Cloud runs your services, workers, jobs, static sites and Postgres databases. Each environment is its own deployment with its own data, and one command ships it.

8 shipped
  • Services, workers and jobs hosted

    Shipped

    Services, workers and jobs run hosted under a restricted profile: read-only root filesystem, no service-account token, quotas and egress containment.

    forge env deploy prodStatus and details
  • Managed Postgres

    Shipped

    Each environment gets Postgres that the platform provisions and operates, on its own server, so no other tenant shares it and staging never holds a credential for prod’s data.

    Status and details
  • Backups and point-in-time restore

    Shipped

    Hosted databases archive WAL continuously and take a daily base backup. A point-in-time restore is a declaration: a new database booted from the source’s backups at the moment you name.

    Status and details
  • Static hosting with a CDN

    Shipped

    Static sites are served from a platform-owned bucket behind a CDN, invalidated on each release, with per-environment runtime config that needs no rebuild.

    Status and details
  • Custom domains with automatic HTTPS

    Shipped

    Add a hostname and publish the DNS records Forge prints. The platform verifies it and issues, renews and serves its certificate.

    forge domain add app.example.com --env prodStatus and details
  • Per-PR preview environments

    Shipped

    A pull request becomes its own environment, copied from a template env. Your CI creates, deploys and deletes it; an expired hosted preview is deleted by the platform.

    forge env preview create --pr <n> --ttl <d>Status and details
  • Write-only hosted secrets

    Shipped

    Secrets are write-only: set once, never read back, scoped to one organization and environment, in an OpenBao-backed store.

    Status and details
  • One static site free

    Shipped

    One hosted static site is free, with no billing set up. Each environment’s site counts as one site.

    Status and details

Limits

  • One hosted region

    Hosted services and managed databases run in one region, GCP us-central1, with no region choice. Static sites are served through the CDN edge.

    On the features page
  • Hosted frontends are static exports

    Reliant hosting serves a frontend only as a static export: no server-side rendering, server actions, middleware or request-time cookies. A Vite SPA or a statically exportable Next.js app fits as it is; one that needs a server runs as a container on a cluster you run.

    On the features page
  • Hosted backends do not autoscale

    A hosted service or worker runs the replica count its env declares; it does not scale with traffic, and a managed database does not grow on its own. Raise the replicas or the shape in the env and deploy, or run the workload on a cluster you run with your own autoscaler.

    On the features page
Everything about hosting: what runs, what it costs, how to leave

Part 2 of 6

Release management

A release is built once and promoted through your environments by digest. Each promotion is checked, recorded and judged, and an earlier release is one redeploy away.

7 shipped
  • Build once, promote by digest

    Shipped

    A release is an immutable set of artifact digests, built once. Prod deploys exactly the bytes that passed staging.

    forge env deploy prod --from stagingStatus and details
  • Prove each deploy is good

    Shipped

    After a deploy, compares the window after the promotion with the equal window before it, per service, and exits pass, fail, could not tell or timed out.

    forge obs check prod --waitStatus and details
  • Prod gated on staging's verdict

    Shipped

    Declare a HealthGate and prod refuses a promotion until staging holds a passing verdict for that release, with an audited override for incidents.

    Status and details
  • Required checks and your approvals

    Shipped

    An environment refuses a promotion that lacks its required checks, or that your own approval system did not approve, enforced where the environment’s ledger lives.

    Status and details
  • Migrations gate every rollout

    Shipped

    Migrations run under a Postgres advisory lock before any new pod starts, so replicas never race to apply one and no pod runs on an unmigrated schema.

    Status and details
  • Rollback floors per environment

    Shipped

    Redeploy any earlier release, down to a floor. A release with a migration that breaks rollback raises the floor itself, so a redeploy never lands below a breaking schema change.

    Status and details
  • Release timeline per environment

    Shipped

    Every promotion is an append-only entry: what was live at any moment, and what changed in it, from commits and pull requests to migrations, gates and health.

    forge env releasesStatus and details

Part 3 of 6

Observability and monitoring

Logs, traces, metrics, errors and real-user sessions from every environment, tied to the release that produced them. Your agent reads the same evidence from the shell.

9 shipped
  • Query prod from the shell

    Shipped

    Logs, traces and metrics answer from the shell, locally or for a hosted environment, as JSON with runnable next commands.

    forge obs logsStatus and details
  • Trace trees with uninstrumented time

    Shipped

    A trace prints as a tree with errors and the critical path expanded, linked logs, and the time that went to uninstrumented code.

    forge obs traceStatus and details
  • Error issues tied to releases

    Shipped

    Errors group into issues with the culprit, frames, trace and suspect commits. A resolved issue reopens when a later release brings it back.

    forge obs issues prodStatus and details
  • Production alerts out of the box

    Shipped

    Every environment starts with alert rules for error rate, latency, crash loops, failed deploys, new and regressed issues, uptime and certificates, delivered in the app, to Slack or to PagerDuty.

    Status and details
  • Alerts as code, run locally

    Shipped

    Alert rules and routes are code, validated at render, recorded in the release, and evaluated locally through a real Alertmanager.

    forge obs alerts checkStatus and details
  • Bad releases flagged automatically

    Shipped

    Every promotion is judged when its window closes, under the environment’s policy. A failing release raises ReleaseRegressed with the findings and its commit range.

    Status and details
  • Uptime and certificate probes

    Shipped

    The platform probes your public frontends and routes from outside, with nothing to declare, and alerts on failing checks and certificates about to expire.

    Status and details
  • Real-user sessions and replay

    Shipped

    The browser SDK reports through a same-origin relay that never forwards cookies or credentials, and one user’s visit prints as a timeline. Replay is opt-in and always masked.

    forge obs sessionStatus and details
  • Dashboards derived from code

    Shipped

    Dashboards are generated from what you deploy, and an audit explains why an empty panel is empty.

    forge obs dashboards auditStatus and details

Part 4 of 6

Testing

Tests run against real Postgres from the first commit, in unit, integration and end-to-end tiers, so a green run means the code works against the database it will meet in production.

2 shipped3 coming
  • Real Postgres in every test

    Shipped

    Database tests run against a real embedded Postgres, each test on its own copy of a migrated template, with no Docker and no database mocks.

    Status and details
  • Unit, integration and e2e tiers

    Shipped

    Unit tests use the real subject with generated mocks, integration tests a real migrated Postgres, and end-to-end tests a running dev stack.

    Status and details
  • Test reports for every run

    Coming

    Every run of your test lanes is recorded with its results, kept per commit and per release, and shown as a report.

    forge test reportStatus and details
  • Code coverage, merged across lanes

    Coming

    Coverage from unit, integration and end-to-end runs merged into one report, per lane and combined, by package and by file.

    Status and details
  • Flaky-test detection

    Coming

    Each test gets a flake score from its run history, so a test that passes and fails on the same code is named before it wastes a merge.

    Status and details

Part 5 of 6

Performance

Production profiles show where time and memory go, and feed the compiler, so the code paths production runs hot get optimized.

2 shipped1 coming
  • Continuous CPU and heap profiling

    Shipped

    Every process samples a CPU profile every five minutes and a heap snapshot every two hours. It is on by default locally; one line in the env file turns it on for a hosted environment.

    forge obs profileStatus and details
  • Profile-guided builds from production

    Shipped

    Turns the CPU profiles your environment collects into each Go binary’s default.pgo, which you commit; every build then optimizes the call sites production runs hot.

    forge pgo pullStatus and details
  • Profile-guided builds, refreshed weekly

    Coming

    A scheduled workflow pulls the week’s CPU profiles and opens a pull request with every binary’s refreshed default.pgo.

    Status and details

Limits

  • Hosted profiling is opt-in

    Continuous CPU and heap profiling is on by default only in local dev. A hosted env collects profiles once its env file turns profiles on, which is one line.

    On the features page

Part 6 of 6

Security

Dependencies are scanned, images are signed, tenants are isolated, and production data is read only through an audited path.

5 shipped1 beta1 coming
  • Dependency and image scanning

    Shipped

    Runs govulncheck over every Go module and npm audit over every frontend, refuses a pass it did not verify, and takes reviewed, expiring exemptions instead of silent ignores.

    forge ci vuln-scanStatus and details
  • Vulnerabilities by release and environment

    Beta

    The console’s Vulnerabilities page lists known vulnerabilities for each release and environment, and calls a release clean only when every artifact in it was scanned.

    Status and details
  • Signed images, SBOM and provenance

    Shipped

    The generated image workflow signs every image it pushes with a keyless signature bound to its digest, with an SBOM and build provenance attested.

    Status and details
  • An SBOM recorded with every release

    Coming

    Every release cut records a CycloneDX SBOM per artifact, stored with the release, so its vulnerabilities can be checked again after it ships.

    Status and details
  • Audited read-only prod queries

    Shipped

    Runs one statement in a read-only transaction, as a role that cannot read secret columns, and demands a reason; on a hosted environment it needs the organization’s db:query grant and records an audit row.

    forge db queryStatus and details
  • Databases fenced off by default

    Shipped

    A hosted database accepts connections only from your own workloads and has no internet egress, by default.

    Status and details
  • Tenant workloads sandboxed

    Shipped

    Hosted workloads run on an isolated runtime in per-organization, per-environment namespaces, and a cross-tenant test suite proves no query, secret or network path crosses tenants.

    Status and details

Ship your app on Reliant Cloud.

Deploy a static site or a service with no account, or let your agent deploy it. Claim it when you want to keep it.