Environments that survive a laptop wipe.
State lives in the manifest and named volumes, not in a folder you forgot to document.
Your whole stack.
One workspace.
Jortos turns your repo, services, secrets and previews into a reproducible environment that boots in seconds.
Works with Docker, Node, Python and Go. No daemon to manage.
# jortos.yaml
services:
web: { from: ./apps/web, port: 3000 }
api: { from: ./apps/api, port: 8080 }
db: { image: postgres:16, volume: pgdata }
cache: { image: redis:7 }Boot the same environment every time.
One manifest describes services, ports, volumes and secrets. Jortos builds it on your laptop, in CI and on a teammate's machine without drift.
One commandjortos up
Cold bootunder a minute on a warm cache
Offlineruns without a network once built
services:
web:
from: ./apps/web
port: 3000
api:
from: ./apps/api
port: 8080
db:
image: postgres:16
volume: pgdata
cache:
image: redis:7
env:
from: .env.localBranch previews
Every branch gets its own isolated stack and URL. Share it before the review starts.
Secrets, scoped
Inject secrets per service and per environment. Nothing lands in the image.
CI parity
The same manifest runs in your pipeline, so a green build means the same stack.
Shared build cache
Layers are cached across teammates. The second boot is much faster than the first.
A preview URL for every branch.
Push a branch and Jortos builds it, seeds it with your fixtures and keeps it alive while the review is open.
feat/billing-retrypr-482.preview.jortos.devready
fix/oauth-callbackpr-479.preview.jortos.devready
chore/upgrade-postgrespr-476.preview.jortos.devbuilding
feat/usage-meterpr-471.preview.jortos.devready
Built for platform teams who own the path to production.
Jortos does not replace your orchestrator. It gives every engineer the same local and preview environment, then gets out of the way.
Describe the stack once. No onboarding document rots in a wiki.
Reproduce any branch from its manifest and its commit.
Keep the workflow local first, so the network is never the bottleneck.
Pricing that follows the team.
Team
Per seat
Shared previews and build cache.
- Everything in Solo
- Branch preview URLs
- Shared cache and secrets
- SSO via your identity provider
Give every engineer the same stack.
Start with one repository. Invite the team when the first preview lands.