For Agencies

A project per client, started from your template

Anythink gives agencies a project per client, a branded dashboard to hand over, and a CLI that copies your template project into each new client project.

Start free Read the docs

The same task, three ways

Start a client project from your template.

The Anythink dashboard

Create the project and invite the client. The template copy is not in the dashboard yet.

The Anythink CLI

Create, connect, preview the copy, then run it.

$ anythink projects create "Acme Ltd" --region lon1$ anythink projects use <project-id>$ anythink migrate --from agency-template --to acme-ltd \--include-workflows --include-roles \--include-settings --include-menus --dry-run$ anythink users invite jo@acme.com Jo Bloggs --role-id 3

✓Project Acme Ltd created in lon1
✓Dry run lists entities, workflows, roles, settings and menus
✓Jo Bloggs invited with role 3

Claude, through MCP

Ask for the client project in one request.

you › “Create a project called Acme Ltd in London, copy our agency template's entities, workflows, roles, settings and menus into it, show me a dry run first, then invite jo@acme.com as an editor.”

✓Created Acme Ltd in London
✓Showed a dry run of the template copy
✓Copied entities, workflows, roles, settings and menus
✓Invited jo@acme.com as an editor

Why agencies standardise on Anythink

One template, many clients, each with a project of their own.

Templates

Your standard backend, copied in one command

migrate copies entities and fields, and when you ask, workflows, roles and permissions, settings, menus, files and data. Permissions are remapped to the client project's entities.

Anythink CLI →Core concepts →

Branding

The client's colours, logos and email domain

Each project carries its own theme, menus and sending domain, so the dashboard you hand over looks like the client's.

Branded dashboards →Branding and menus →

Integrations

Each user connects their own accounts

User-scoped connections let a client's staff connect their own calendar or Slack, and workflows act on their behalf.

Integrations →Integrations quick start →

Handover

A dashboard, not a support ticket

Clients work in grid, kanban, calendar and map views with charts on their own data, under roles you set, so routine changes don't come back to you.

Dashboards →Data views →

Build it once, deliver it to every client

Your template becomes the starting point, and each client gets a project and a dashboard of their own.

A project per client

Each client gets their own project with separate data, users, roles, API keys and integrations. Switch between them in the CLI with saved profiles.

Start every client from a template

Build your standard backend once. anythink migrate copies its entities, workflows, roles, settings and menus into each new client project, with a dry run first.

Dashboards in the client's brand

Set the client's colours, grey palette, corner radius, logos and menus, and send their system email from their own verified domain.

Connections per user

A client's users can each connect their own Slack, Google Calendar or AI account, so workflows post and book as them rather than as one shared login.

A dashboard your client can run

Invite the client's team with a role, and give them grid, kanban, calendar and map views and charts over their own data. They manage their business without a custom admin panel.

A project per client

Each client gets their own project with separate data, users, roles, API keys and integrations. Switch between them in the CLI with saved profiles.

01 / 05

How it works

Build a template project

Model your standard entities, roles, workflows and menus once, in a project you keep as the template.

Create the client project

Create a project for the client and connect to it with anythink projects use. Each project picks its own plan.

Copy the template

Run anythink migrate from the template to the client project with a dry run, then for real.

Brand it

Set the client's colours, logos and menus, and verify their sending domain so system email comes from them.

Hand it over

Invite the client's team with roles, and let each user connect their own integrations.

Brand each client project

Set colours, logos and menus, and send system email from the client's own domain.

White-label platform →

Frequently Asked Questions

Can I use Anythink for multiple client projects?

Yes. Each project is self-contained with its own entities, data, users, roles, API keys and integrations. Each project also picks its own plan, so you can match costs to each client.

Can I customise the branding for client projects?

Yes. Each project has its own primary colour, grey palette, corner radius, square and standard logos, and menus, and can send system email from the client's verified domain. It's branding rather than full white-label: the dashboard stays on an Anythink address and Anythink marks remain.

How do I reuse a template backend across clients?

Keep a template project with your standard entities, workflows, roles and menus. For each new client, create a project and run anythink migrate --from <template-profile> --to <client-profile> with the --include flags you need. Run it with --dry-run first to preview the changes.

Can each of my client's users connect their own accounts?

Yes. Integration connections can be project-wide or belong to a single user. A user-scoped connection lets each person connect their own Google Calendar, Slack or AI provider account, and only that user sees it.

Still have questions?

Get in Touch

Ways to build with it

The dashboard, the CLI, MCP and the SDK, plus guides for moving from other platforms.

Solution

Content Management

Anythink works as a headless CMS: model content types, edit them in the Anythink dashboard, and serve them to your website through a public REST API.

Solution

Flexible Data Views

Switch any entity between a grid, a kanban board, a calendar, a map and charts in the Anythink dashboard, all on the same records your API serves.

Solution

Branded dashboard

Brand the Anythink dashboard with your colours, logos, corner radius and menus, and send system email from your own verified domain and sender address.

Solution

TypeScript SDK

The Anythink SDK is an open source React library for sign-in and sessions: an auth client, a provider, a useAuth hook, and a base class for authenticated requests. Data calls go through the REST API directly — there's no hidden query layer to learn.

Solution

Anythink CLI

The open source Anythink CLI runs a whole project from the terminal: entities, fields, data, workflows, roles, users, files, search, secrets and integrations.

Solution

AI & MCP

Build your backend in a conversation, from Claude Code, Cursor or the AI chat in the Anythink dashboard. The same MCP tools reach the whole CLI, from entities and fields to workflows, roles, secrets and payments.

Who it's for

How founders, agencies and enterprise teams use Anythink.

Use Case

For Founders

Anythink gives founders sign-in, a REST API, subscriptions, workflows and an operations dashboard in one project, from first prototype to paying customers.

Use Case

For Enterprise

Anythink gives enterprise teams a managed backend with roles, row-level security and encrypted secrets, on a dedicated Kubernetes cluster if you need one.