# How to host client apps as a freelancer or small agency.

URL: https://antideploy.com/blog/host-client-apps-as-a-freelancer-or-small-agency

Static client sites are free. Apps with a server count against your plan: 3, 9 or 20 live apps. Here is how it works and what to tell your clients.

## At a glance

- **Static sites are free**: Unlimited, on every plan
- **Live apps by plan**: 3 on Go, 9 on Pro, 20 on Scale
- **Client domains**: Unlimited on Pro and Scale
- **No team accounts**: The apps live in your account

Published 7 October 2026. Facts checked 7 October 2026. 2 min read.

## The short answer

You can host client websites and apps on one Antideploy account. Static sites, such as a brochure site or a portfolio, are free and unlimited. Apps with a server count as live apps: Go is ₹399 a month for 3 live apps, Pro is ₹1,999 for 9 and Scale is ₹6,999 for 20. Your clients' own domains are included from Go, with HTTPS. There are no team accounts today, so the apps live in your account.

## What counts against your plan

- A static site never counts, on any plan. As many client sites as you like
- An app with a server counts as one live app: 1 on Free, 3 on Go, 9 on Pro, 20 on Scale
- A Postgres database counts toward the plan's databases: 1 on Free and Go, 3 on Pro, 5 on Scale
- Failed deploys are free, so fixing a client's build costs nothing

## Client domains

Each client's own domain is added in the console, on the app's Domains tab, with one DNS record at their registrar. Go includes 3 custom domains. Pro and Scale include as many as you need. HTTPS is included on all of them. A client can keep their domain at their own registrar and point it to the app.

## What to tell your client

- **The app sleeps when idle.** The first visit after a quiet spell takes a few seconds. After that it is fast.
- **It runs in Singapore.** That is close to India and Southeast Asia, and slower for visitors far from Asia.
- **It is one instance.** There is no autoscaling and no preview deployments.
- **Files go in a bucket, not on disk.** Anything saved to the app's disk is lost on the next deploy.

## Running costs for you

Email from client apps is for their own users: 20 addresses a day on Free, 100 on Go, 500 on Pro and 2,000 on Scale, per app. AI usage is paid from a prepaid wallet in your account, shared across your apps. Read [what Antideploy cannot run](https://antideploy.com/blog/what-antideploy-cannot-run) before you promise a client something it does not do.

## Here's where it stops.

A platform that only tells you what it is good at is one you find the edges of in production. These are the ones to know before your first deploy.

### Apps sleep when idle

On every plan, an app nobody is using goes to sleep and the next visit wakes it. The first request took 2.9 to 13.9 seconds in our measurements, depending on the stack. There are no always-on workers, so use a cron job or a webhook for background work.

### One region

Everything runs in Singapore, with the database beside the app. Users far from Asia will see slower responses.

### One instance, no previews

Each app is one instance with 1 shared vCPU and 1 GB of memory, and a Java app gets 1 dedicated vCPU and 2 GB. There are no preview deployments and no per-branch URLs.

## Freelancer questions, answered.

Anything else? Write to us and a person answers.

[support@antideploy.com](mailto:support@antideploy.com)

### Can I invite my clients to see their app?

Not as users. There are no team accounts today. You can share the app's address, and you can show logs and numbers from your own console.

### Can I move an app to my client's account later?

This page does not describe a transfer feature. Ask support@antideploy.com before you plan around it.

### Which plan fits ten client apps?

Ten apps with a server need Scale, which holds 20 live apps. Any number of static sites is free.

### Does every client app get its own database?

Databases are counted per account: 1 on Free and Go, 3 on Pro and 5 on Scale. Pro holds 9 live apps but 3 databases, so not every app on Pro can have an Antideploy database. An app can use a database from another provider by setting its own `DATABASE_URL`.

## More guides, and the platform.

Each platform page covers one part of Antideploy: what it does, where it stops and the questions people ask. [See the whole platform](https://antideploy.com/platform), or [all the guides](https://antideploy.com/blog).

- [Is Antideploy free? What happens at the limit?](https://antideploy.com/blog/is-antideploy-free): Yes, there is a Free plan. What it includes, what happens at each limit, and what paid plans cost.
- [How to connect your own domain](https://antideploy.com/blog/how-to-connect-your-own-domain): One CNAME record, HTTPS included. Available from the Go plan. Root domains versus www.
- [What can't Antideploy run?](https://antideploy.com/blog/what-antideploy-cannot-run): The honest list: one region, sleeping apps, no Redis or MongoDB, no background workers, and what is refused.

- [Static sites](https://antideploy.com/platform/static-sites)
- [Custom domains](https://antideploy.com/platform/custom-domains)
- [Hosting](https://antideploy.com/platform/hosting)
- [AI models](https://antideploy.com/platform/ai-models)

Facts on this page were checked against the live platform on 7 October 2026.

## Deploy something. Start with one sentence.

Paste one sentence into your coding agent, click Approve once, and get a live link. No card, no trial clock.

To set this up, give your coding agent this sentence:

```text
Set this project up to deploy on Antideploy. Fetch https://antideploy.com/agent.md and follow it.
```