Skip to content
AppwriteAgencies

Ship client work on the same stack._

Each client gets a project with auth, data, files, functions, and hosting. Your team keeps one Console and one way of working. When the engagement ends, the client can run it.

Get startedContact sales

studio · Clients

3 projects active

  • acme

    acme.example.com

    Live

  • northwind

    northwind.example.com

    In progress

  • luma

    client@luma.com

    Handoff

Your teamThe client

The client can run the project

A project per client

Handoff included

Stack for every client
1
Pricing on the organization
Pro
Invite the client at handoff
Teams
Host the product you ship
Sites
The client can leave with it
OSS

Customers_

Client products that stay on Appwrite_

Agencies ship on the same platform the client keeps after launch. The handoff is the project.

  • DevKind
  • LangX

Why Appwrite_

Stop inventing a stack for every brief_

The brief changes. Auth, a database, files, and hosting usually do not. Appwrite is that stack on every project, so the second client is faster than the first.

  • A repeatable project

    Same services, same SDKs, same Console. A new engagement starts from a pattern the team already knows.

  • One project per client

    Each client has its own project, with its own users, keys, and data.

  • A handoff the client can run

    Invite them into the organization, or give them the project. They are not stuck on a tool only your team can operate.

  • Hosting in the same project

    Ship the site on Appwrite Sites, next to the API the product calls.

One platform_

The stack you stop reassembling_

Every engagement starts with the same backend list. Appwrite covers it, so the hours go into the product.

Without a platform

  • Identity providerSeparate contract
  • Database serviceSeparate contract
  • File storageSeparate contract
  • Function hostingSeparate contract
  • Messaging providerSeparate contract
  • Web hostingSeparate contract
  • Firewall and DDoSSeparate contract

Appwrite

  • Auth
  • Databases
  • PostgreSQL
  • Storage
  • Functions
  • Realtime
  • Messaging
  • Sites
  • Domains
  • Firewall
  • One stack
  • One Console
  • A project per client
  • A real handoff

How agencies use it_

From the first commit to the handoff_

Build in your organization. Leave the client with a project they can operate.

Client work

  • Project per client

    Users, data, and files stay inside that project.

  • API keys

    Server keys scoped to the project you are shipping.

  • Team permissions

    Your developers and the client team, with different access.

The product

  • Auth through functions

    Sign-in, data, files, and custom logic in one project.

  • Sites

    Host the web app you were hired to ship.

  • Messaging

    Email, SMS, and push when the product sends them.

After launch

  • They can stay on Cloud

    The client keeps the project on the Free or Pro plan.

  • Open source

    They can self-host if their policy requires it.

  • Enterprise

    SSO, SLAs, and a self-hosted edition when the client needs that contract.

Agencies FAQ_

Clients, billing, and what happens when you hand the project over.

Yes. Create a project per client. Keep the projects in your organization while you build, and move or share a project when you hand it over.

They can. Invite them as members, or have them create an organization and take the project. They use the same Console you do.

You pay for the plan on the organization that owns the projects. What you charge the client is between you and them.

View pricing

The project does not need a rewrite. Contact sales with them, or send them to the Enterprise page, when they need SSO, an SLA, or a self-hosted edition.

Enterprise

Start the next client project_

Create an account, open a project, and use the same stack on the next engagement.

Get startedContact sales