Prove the idea on a real backend._
Labs and incubation teams can stand up auth, data, files, and hosting on Appwrite Cloud without waiting on a platform build. If the pilot sticks, the same APIs run on an Enterprise plan, including a self-hosted edition.
lab · Pilot
Pilot in progressAuth
18
users
Databases
240
rows
Storage
12
files
Functions
node-22
Deployed
Messaging
Email
From the pilot
Sites
Live
pilot.example.com
Including a self-hosted edition
Start on Cloud
Self-host later
- No infra ticket to start
- Cloud
- Stack for the pilot
- 1
- APIs if it reaches production
- API
- When the pilot is a product
- Enterprise
- Self-host if policy requires it
- OSS
Customers_
A pilot on the platform production uses_
The demo is an Appwrite project, with users, permissions, and a path onto Enterprise.
Why Appwrite_
A pilot should not wait on a platform project_
Innovation teams get stuck between a slide and a six-month build. Appwrite lets the team ship a working product on Cloud, then hand over a platform that already exists.
A working pilot
Auth, a database, storage, and hosting are already there. The team builds the product.
Something IT can take
The pilot has users, permissions, and logs. Enterprise adds SSO, SLAs, and a self-hosted edition.
A region you can name
Pick a Cloud region for the pilot. If policy requires your own environment, the self-hosted edition is the same platform.
Handoff to the product org
The team that owns the product can take the project. They do not rebuild it on another stack.
One platform_
What a pilot usually bolts together_
Identity, a database, files, a place to run code, and somewhere to host the UI. Appwrite is that list, in one project.
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 project
- One Console
- Same APIs later
- A path to Enterprise
From pilot to production_
Start small. Keep the APIs._
Build on Cloud. Move to Enterprise terms when the company is ready to own the product.
Pilot
Auth
Sign-in for the first users, without a separate identity project.
Databases
A database in the project, without an infra ticket.
Storage
Files for the demo, with permissions.
Functions
The logic that is not plain CRUD.
Show it
Sites
Host the demo next to the API.
Realtime
Live updates when the demo needs them.
Messaging
The emails and notifications the pilot sends.
If it sticks
Enterprise plan
SSO, SLAs, and custom limits when procurement starts.
Self-hosted edition
The same platform, in your environment.
Same SDKs
The pilot code keeps calling the same APIs.
Innovation teams FAQ_
Pilots, procurement, and self-hosting.
Internal innovation, R&D, and incubation teams that need a working product and do not want to wait for a central platform build.
Yes. A team can create an Appwrite Cloud account and build on the Free or Pro plan. Procurement matters when you need Enterprise terms.
The Enterprise self-hosted edition is the same platform, in your environment. Talk to sales when that requirement is real. You do not throw the pilot away.
Cloud Enterprise can include SOC 2 and HIPAA support, plus SSO and activity logs. Start the pilot on Cloud, and bring the Enterprise page into the review when the pilot is worth a contract.
Start the pilot on Cloud_
Build on the Free or Pro plan. Talk to sales when the pilot needs Enterprise terms or a self-hosted edition.