diff --git a/docs/limits.md b/docs/limits.md index 5f8c25b..a2d7a50 100644 --- a/docs/limits.md +++ b/docs/limits.md @@ -23,7 +23,9 @@ cannot be purchased or claimed today; `POST /api/v1/billing/checkout` and When it ships, Team is planned at $199/mo with high finite limits (not unlimited): 50 GB Postgres / 100 connections, 1.5 GB Redis, 40 GB MongoDB / 50 connections, 40 GB queues, 300 GB object storage, 30 GB vector, 100 deployment apps, 1000 vault -entries, 100k webhooks, 50 custom domains, 90-day backups with self-serve restore, +entries, 100k webhooks, 50 custom domains, 90-day backups with self-serve restore +(backups cover Postgres, pgvector, MongoDB & Redis; restore is self-serve for +Postgres/pgvector/MongoDB — Redis is backup-only today, restore coming soon), and RBAC + audit log. Capacity beyond these caps (or dedicated/isolated infra, multi-region, or compliance such as SOC2/BAA/SSO/SLA/DPA) is Enterprise — contact sales@instanode.dev. diff --git a/llms.txt b/llms.txt index 6339fc4..40ac316 100644 --- a/llms.txt +++ b/llms.txt @@ -103,7 +103,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. Resource-count cap: 5 active resources per service (redis is 3 — Redis RAM is the binding cost). Per-tier counts are introspectable via `resource_count_limit` on `/api/v1/capabilities`. -- **Team**: available soon — not yet self-serve. Planned at $199/mo with high finite limits (50 GB Postgres, 1.5 GB Redis, 40 GB Mongo, 40 GB queues, 300 GB storage, 30 GB vector, 100 deployments, 1000 vault entries, 100k webhooks), 50 custom domains, 90-day backups with self-serve restore, RBAC + audit log; SSO/SAML and a 99.9% SLA are also planned. Capacity beyond these caps (or dedicated/isolated infra, multi-region, or compliance such as SOC2/BAA/SSO/SLA/DPA) is Enterprise — contact sales. Team cannot be purchased or claimed today — contact contact@instanode.dev for onboarding. +- **Team**: available soon — not yet self-serve. Planned at $199/mo with high finite limits (50 GB Postgres, 1.5 GB Redis, 40 GB Mongo, 40 GB queues, 300 GB storage, 30 GB vector, 100 deployments, 1000 vault entries, 100k webhooks), 50 custom domains, 90-day backups with self-serve restore (backups cover Postgres, pgvector, MongoDB & Redis; restore is self-serve for Postgres/pgvector/MongoDB — Redis is backup-only today, restore coming soon), RBAC + audit log; SSO/SAML and a 99.9% SLA are also planned. Capacity beyond these caps (or dedicated/isolated infra, multi-region, or compliance such as SOC2/BAA/SSO/SLA/DPA) is Enterprise — contact sales. Team cannot be purchased or claimed today — contact contact@instanode.dev for onboarding. - **Enterprise**: custom limits, dedicated infra, compliance; contact sales@instanode.dev. Not a self-serve tier and not in `plans.yaml` — no price, no checkout. Triggers: needs more than Team's caps, dedicated/isolated or multi-region infra, or SOC2/BAA/SSO/SLA/custom DPA. ## Conventions an LLM should follow when scripting against the platform diff --git a/pages/pricing.md b/pages/pricing.md index cbff720..6b07fe2 100644 --- a/pages/pricing.md +++ b/pages/pricing.md @@ -50,7 +50,7 @@ Team is **not yet self-serve**: it cannot be purchased or claimed today. Email c - 1000 vault entries - 100k stored webhooks - 50 custom domains -- 90-day backups with self-serve restore +- 90-day backups (Postgres, pgvector, MongoDB & Redis) with self-serve restore for Postgres, pgvector & MongoDB — Redis is backup-only today (restore coming soon) - RBAC + audit log - SSO / SAML and a 99.9% SLA are coming soon (not yet available)