Teams, projects & environments

Your team is the account: one wallet, your people. Inside it, projects are independent units that each get their own private network. Inside a project, environments (like main, staging) are deploy targets. Money is always team-level — one balance funds everything.

Superjolt has three nested levels. Knowing them makes everything else — billing, networking, access — fall into place.

Team  (your account — one wallet, your members)
└── Project  (a unit of work — its own private network)
    └── Environment  (a deploy target: main, staging, …)
        └── VMs · domains · config

Team

Your team is your Superjolt account. It holds:

• The wallet — one balance funds everything you run across all your projects and environments. There’s no per-project billing; see Billing FAQ.
• Members — the people who can manage the team, each with a role (owner / admin / member). Add or remove teammates from the dashboard.

Rename it any time (the name is display-only; IDs don’t change). New to Superjolt? You get a team automatically.

Project

A project is a self-contained unit of work — one app, one product, one experiment. Within a team you can have as many as you like, and they’re isolated from each other.

The defining property: each project is its own private network. VMs in the same project reach each other by name (db, api); VMs in different projects cannot reach each other privately. So a project is the natural boundary for “these services belong together” — see Project networking.

A project owns its VMs, custom domains, and API tokens.

Environment

Inside a project, an environment is a deploy target — main by default, plus any you add (staging, preview, …). Every project starts with main.

Environments let you run the same app’s staging and production side by side in one project. Scoped per environment:

• VMs and domains
• Config vars (your env secrets)

But not money — the wallet stays at the team level, so one balance funds every environment.

Where everything lives

In practice

create a "shop" project with a staging and a production environment

Your agent calls create_project and create_environment. From there, VMs you create in shop share a private network, while staging and production keep their own config and deploys — all funded by your one team balance.