Runtime options

Causet has two runtime deployment options:

The interactive learning environment and causet build compile are authoring tools — they are not a substitute for a runtime when you need live intents.

See What runs today? for current availability, maturity, and production-support details.

Learn the model (no runtime required)

Browser tutorials

The interactive learning environment runs in your browser — in-memory compiler and rules engine, no signup, no network. For a real runtime, use the local wallet quickstart.

CLI compile and validate

causet build validate --runtime ./your-app
causet build compile --runtime ./your-app --out dist

Local runtime

curl -fsSL https://install.causet.io/install.sh | bash
causet version
 
causet local up
causet context use env local

Your app points at:

CAUSET_API_URL=http://localhost:8085

Local service ports (authoritative)

Synchronized from install.causet.io/docker-compose.yml:

Then submit intents via the SDK or CLI — no Cloud login required.

causet local status
causet local logs
causet local down

Full details: CLI.

Managed hosted runtime (Causet Cloud)

1. Install the CLI and request early access at causet.io
2. causet login and causet init
3. causet deploy --fork sandbox
4. Submit intents: causet intent … or client.submitIntent() from your app
5. Inspect: causet inspect timeline …

CAUSET_API_URL=https://api.causet.cloud

End-to-end adoption loop

1. Define the workflow in .causet files
2. Compile: causet build compile
3. Deploy: causet deploy --fork sandbox --yes
4. Retrofit one API route — Retrofit an Existing App
5. Trigger the endpoint and inspect the timeline
6. Simulate failure and verify retry / webhook behavior
7. Replay/repair if needed — Replay

Related

• CLI
• Install Causet
• Production Rollout Checklist
• What runs today?