Infrastructure
A cluster of your own
A dedicated stack runs Anythink on its own Kubernetes cluster, separate from other customers. Anythink builds and runs it for you.
Anythink gives enterprise teams a managed backend with roles, row-level security and encrypted secrets, on a dedicated Kubernetes cluster if you need one.
Give a CI pipeline a scoped API key that expires.
The Anythink dashboard
API keys live under My Account.
The Anythink CLI
Permission names are checked before the key is created.
$ anythink fetch /permissions$ anythink api-keys create github-actions \--permissions orders:read,orders:update \--expires-in 90 --save-as ciClaude, through MCP
Ask for the key and the permissions it needs.
you › “Create a 90-day API key called github-actions that can only read and update orders, and tell me if any permission couldn't be granted.”
Controls every project gets, plus infrastructure of your own.
Infrastructure
A dedicated stack runs Anythink on its own Kubernetes cluster, separate from other customers. Anythink builds and runs it for you.
Access
Row-level security separates group membership from group roles, so a customer's team can read its own records while staff-only records stay hidden.
Secrets
Secrets use AES-256-GCM with a per-secret salt and nonce. They're write-only through the API, the dashboard and the CLI.
Integrations
Configure your own client ID and secret for Slack, Google and other providers, so users approve your organisation's app.
The access, secrets and environment controls that come with every project, plus a dedicated stack when you need one.
Enterprise customers can run Anythink on their own Kubernetes cluster, separate from the shared platform. We build and run it for you, on request.
Permissions follow an entity:action pattern for every entity. Row-level security grants records to users or whole groups, and group members read their team's data while staff-only records stay private.
API keys, tokens and secret fields are encrypted with AES-256-GCM and never shown again after they're saved. Workflows and integrations use them without exposing the value.
The CLI's migrate command copies entities, workflows, roles and permissions, settings and menus from one project to another, with a dry run first.
Set your own client ID and secret per provider, so users approve your organisation's app rather than a shared one. Connections can belong to the project or to an individual user.
Each key carries only the permissions you list and expires after a set number of days. The CLI checks that every permission exists and that you hold it.
How it works
Tell us about your workload and integration needs. We'll agree whether a dedicated stack is right for you.
Anythink provisions your dedicated Kubernetes cluster and runs it for you.
Create entities, roles and permissions, set row-level security and groups, and store credentials as encrypted secrets.
Build in a staging project, preview with anythink migrate --dry-run, then promote to production.
Dedicated stack
A dedicated stack, with its own Kubernetes cluster, is built on request. It is not self-serve.
Talk to us →Yes. Enterprise customers can have a dedicated stack: Anythink running on its own Kubernetes cluster rather than the shared platform. It's built for you on request rather than provisioned self-serve, so contact sales to discuss what you need.
JWT and API key authentication with scoped, expiring keys; sign-in with Google, Apple and LinkedIn; role-based access control with entity-scoped permissions; row-level security for users and groups; and encrypted secrets (AES-256-GCM). Integrations can use your own OAuth apps.
No. Anythink is a managed service, and the dedicated stack is run by Anythink for you. You get separate infrastructure without operating it yourself.
Keep staging and production as separate projects and use anythink migrate. Run it with --dry-run to preview the changes, then again to apply them, adding --include-workflows, --include-roles, --include-settings or --include-menus as needed.
A dedicated stack on its own Kubernetes cluster, deployed in the DigitalOcean region you choose, plus single sign-on (SSO) for your organisation, a custom SLA and compliance terms agreed in the contract, and a dedicated support team. It's built on request rather than self-serve, so talk to us about what you need.
Still have questions?
Get in TouchEvery feature reads from the same data model, so each one you add works with the rest.
The dashboard, the CLI, MCP and the SDK, plus guides for moving from other platforms.
How founders, agencies and enterprise teams use Anythink.
Guides and reference at docs.anythink.cloud.
Enterprise projects can run on their own Kubernetes cluster, set up on request. Tell us what you need and we will scope it with you.