Starter
Side projects and first deployments
PRICE
Announced at launch
- One or a few small applications
- Shared platform resources
- Community support
PRICING
Plans built around what you run.
Pricing should be as understandable as a deployment. Here is the shape of the plans — what they include and who they’re for. Exact prices, allowances, and billing units are commercial details we will publish at launch, not numbers we invent today.
Builder
Independent developers and small teams shipping real products
PRICE
Announced at launch
- More applications and services
- Larger resource envelopes
- Persistent storage included
- Email support
Team
Product teams and agencies delivering for clients
PRICE
Announced at launch
- Projects for each client or product
- Organization and role-based collaboration
- Priority support
Plan names, counts, and limits above describe structure, not final commercial terms. No fabricated prices, no invented free tier — the real numbers land here when they’re decided.
EVERY PLAN, EVERY DAY
What’s included across the board.
- Deployments from GitHub, container images, and templates
- Public HTTPS addresses on ideployed.app, plus custom domains with managed TLS
- Private services with explicit, directed connections
- Environment configuration with masked secrets
- Build and runtime logs, deployment history, and rollbacks
- Persistent volumes for stateful templates
ALSO PART OF THE PICTURE
Usage you can see, capacity you control.
The platform direction includes usage visibility, resource plans, billing and subscriptions, and capacity controls — so you always know what you’re consuming and what it costs. Health checks become configurable as your applications grow more demanding.
Exact allowances, scaling behavior, billing units, and region choices are published when they’re final. Until then, this page stays honest about being a structure, not a price list.
YOUR NEXT CHAPTER
Good ideas deserve
to be out there.
Bring your code. Make something people can use.