Skip to content
JacqOS
Get started

Cloud Getting Started

JacqOS Startup Cloud is the hosted V1 runtime for teams that want to run a verified JacqOS app without operating their own control plane. It runs on the JacqOS-managed Hetzner Startup Cloud, uses WorkOS-backed account identity, and keeps the same proof model you use locally: observations first, derived facts second, explicit effects, and replayable evidence.

Use Startup Cloud after a local app already verifies. Cloud adds a hosted runtime cell, deployment lifecycle, scoped runtime tokens, Studio work views, health and usage summaries, and exportable replay evidence. It does not replace local verification or change what makes JacqOS auditable.

Startup Cloud Vs Enterprise BYOC

Section titled “Startup Cloud Vs Enterprise BYOC”
ProductWho operates itV1 scope
Startup CloudJacqOS, on HetznerPublish verified apps, promote a hosted evaluator, use Studio and runtime APIs, export hosted evidence.
Enterprise BYOCYour infrastructure teamSeparate enterprise deployment model. It is not part of this Startup Cloud V1 flow.

The rest of this section documents Startup Cloud. Enterprise BYOC has different networking, identity, and operations contracts.

What Cloud Preserves

Section titled “What Cloud Preserves”
ConceptCloud guarantee
lineage_idHosted observations append to one explicit history. A cloud work view always names the lineage it reads or writes.
evaluator_digestThe promoted evaluator identity is carried through deploy, promote, Studio views, export, and replay.
package_digestCloud runs the verified evaluation package that was deployed. Stale or mismatched package identity blocks mutation.
Hosted runtime identityRuntime URLs are scoped by project, app, environment, lineage, package, and evaluator identity.
ProvenanceHosted facts, intents, effects, and Activity entries trace back to observations and runtime receipts.
Effect authorityExactly one promoted activation per cloud lineage may execute effects. Shadow, paused, archived, or stale activations are observable but not effect-authoritative.
Replay/exportHosted evidence exports with redacted observations, semantic digests, and provenance so a clean local replay can recompute the same identity.

Cloud metrics are management/runtime summaries. They tell you health, request counts, observation counts, effect counts, storage size, degradation, and last export status. They are not canonical app facts.

Choose Your Path

Section titled “Choose Your Path”
PathUse it whenStart
StudioYou want the guided macOS SwiftUI Studio flow: sign in, publish, select a cloud work view, chat, inspect Activity/provenance, append observations with warnings, and watch health/metrics.Publish with Studio
CLIYou want copyable commands for CI, operators, or infrastructure automation.Publish with the Cloud CLI

Both paths produce the same hosted contract: a promoted evaluator, scoped runtime tokens, append-only observations, hosted facts and intents, effect receipts, provenance, and replay exports.

Public Endpoints

Section titled “Public Endpoints”
SurfaceURL
Docs and installerhttps://www.jacqos.io
Shell installerhttps://www.jacqos.io/install.sh
Windows installerhttps://www.jacqos.io/install.ps1
Cloud management APIhttps://cloud.jacqos.io
Management healthhttps://cloud.jacqos.io/api/v0/health
Runtime APIhttps://runtime.cloud.jacqos.io
Runtime healthhttps://runtime.cloud.jacqos.io/healthz
App observe endpointhttps://runtime.cloud.jacqos.io/v0/apps/<app-id>/envs/<environment-id>/observe

You do not need Rust, Cargo, Node.js, WorkOS API keys, database passwords, Railway tokens, Hetzner tokens, or operator ingress tokens to build and publish a JacqOS app.

First Local Proof

Section titled “First Local Proof”

Install JacqOS, scaffold a small app, and prove it locally before you touch Cloud:

Terminal window
curl -fsSL https://www.jacqos.io/install.sh | sh
jacqos scaffold appointment-booking
cd appointment-booking
jacqos replay fixtures/happy-path.jsonl
jacqos verify

jacqos verify must pass before Cloud publish. A failed fixture, invariant, or redaction check blocks deployment locally; Cloud never receives an unverified package.

The V1 Workflow

Section titled “The V1 Workflow”
  1. Sign in to the macOS SwiftUI Studio Cloud panel or jacqos cloud login.
  2. Select a project, app, and environment.
  3. Deploy a verified package handoff.
  4. Promote exactly one package as the effect-authoritative activation.
  5. Choose the cloud deployment as a Studio work view.
  6. Chat with the hosted app, inspect Activity and provenance, and append new observations when you explicitly accept the cloud write warning.
  7. Watch deployment health, usage metrics, replay/export status, and runtime degradation from the Cloud dashboard.
  8. Export hosted evidence and replay it locally when you need an audit artifact or a clean reproduction.

Automated Auth For Agents

Section titled “Automated Auth For Agents”

Human Studio sign-in uses the configured WorkOS-backed management plane. Studio does not ask users to type a management URL; if the app is not configured, Cloud account actions show a blocking configuration error.

Coding agents and CI can test Studio auth without a browser. The automated path uses an AgentMail-backed test email inbox, starts WorkOS Magic Auth, reads the verification email through AgentMail’s structured message API, completes the code flow through the local Studio API, and writes a redacted receipt. The environment variable name for the AgentMail API key is JACQOS_AUTH_TESTING_EMAIL_API_KEY. Store only the variable name in docs or scripts; never publish or commit the value.

Next Steps

Section titled “Next Steps”