Skip to content

docs(llms): present Team as available-soon, not a self-serve tier #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mastermanas805 merged 1 commit into from
Jun 4, 2026
Merged

docs(llms): present Team as available-soon, not a self-serve tier #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions llms.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ The `email` field must parse as a valid RFC 5322 address (validated via Go `mail

## Tiers

The public, self-serve tiers visible at `/pricing` are: Anonymous, Hobby, Pro, and Team.
The public, self-serve tiers visible at `/pricing` are: Anonymous, Hobby, and Pro. Team is not yet a self-serve tier — it is available soon; contact support@instanode.dev for onboarding.
Hobby Plus and Growth exist in `plans.yaml` as upsell-only intermediate tiers (reachable
via dashboard prompts when a Hobby user hits a wall) and are deliberately omitted from
the public tier ladder to keep the customer-facing comparison simple. Both still surface
Expand All @@ -100,7 +100,7 @@ on `/api/v1/capabilities` for agent introspection.

> **Upgrading auto-promotes in-flight deployment TTLs.** When a team upgrades to any paid tier (Hobby / Hobby Plus / Pro / Growth / Team), the Razorpay subscription.charged webhook flips the team's `default_deployment_ttl_policy` from `auto_24h` to `permanent` (so every future `POST /deploy/new` defaults to no TTL) AND promotes every existing `auto_24h` non-terminal deploy to permanent (clearing `expires_at`). Per-deploy `ttl_policy='custom'` and `ttl_policy='permanent'` rows are never touched — only the `auto_24h` class is rolled forward. To restore the 24h-default behaviour after an upgrade, `PATCH /api/v1/team/settings {"default_deployment_ttl_policy":"auto_24h"}`.
- **Pro**: $49/mo. 10 GB Postgres, 512 MB Redis, 5 GB Mongo, 50 GB storage, 10 apps.
- **Team**: $199/mo. Unlimited everything (Postgres / Redis / Mongo / queues / storage / deployments / vault entries), 50 custom domains, 90-day backups with self-serve restore, RBAC + audit log. SSO/SAML and a 99.9% SLA are coming soon (not yet available). Self-serve assisted-Razorpay path is rolling out — for now contact support@instanode.dev for onboarding.
- **Team**: available soon — not yet self-serve. Planned at $199/mo with unlimited everything (Postgres / Redis / Mongo / queues / storage / deployments / vault entries), 50 custom domains, 90-day backups with self-serve restore, RBAC + audit log; SSO/SAML and a 99.9% SLA are also planned. Team cannot be purchased or claimed today — contact support@instanode.dev for onboarding.

## Conventions an LLM should follow when scripting against the platform

Expand Down
Loading