The Agency plan: client sites under your name, built by your team

Who it's for

Freelancers and studios that build sites for other businesses have two needs a single-person plan doesn't meet. Several people work on the same projects, and the finished site belongs to the client in the client's eyes, so tool credits on it look like someone else's advert. A white label plan for client sites deals with the second; the shared workspace deals with the first. If neither applies to you, Team or Pro is the simpler choice.

What white-label removes

These changes are made as each page is served, from the owner's plan, so moving a workspace onto Agency affects its existing sites within minutes, with nothing republished. The free plan's badge is covered on its own page about the Made with Anticode badge.

Why the hosting line stays

A privacy policy has to say who handles visitors' data. Anticode stores form submissions and serves the pages, and Cloudflare's network carries every request, so the generated policy says so on every plan. That's a statement of fact for the visitor, not marketing, and removing it would make the policy wrong. If you'd rather it named your agency's relationship with the client too, add that in your own words on the site.

Making a site look entirely the client's

1. Connect the client's own domain, so the address is theirs rather than an anticode.dev subdomain.
2. Fill in the client's business name, contact email and country under Legal pages in the Console, so the Privacy Policy and Terms name them.
3. Leave the optional "Security-checked by Anticode" footer link switched off, or switch it on if the client values the public security report.
4. Share drafts through client review links, which open the preview with no account and no Anticode sign-up.

The workspace behind it

Agency builds on Team, so everything a Team workspace does, it does. Projects, sites, files, domains and form data all belong to the subscriber's account, and invited people work inside it.

Owner

The subscriber. Handles billing, and everything an admin can do.

Admins

Invite and remove people, delete projects and take sites down.

Members

Build, edit and publish. They can't delete projects or take sites down.

Agency has its own seat count, separate from Team's, and invitations count against it until they're accepted or cancelled. Its build allowance is larger too, and anyone working in the workspace builds at the more generous of their own plan and the workspace's. Access is checked on every request, so a person you remove loses access at once, and if the subscription lapses, the workspace stops being shared. Because the published sites are the owner's, the owner's two-factor sign-in matters: a site that collects form data can't be published until the account owner and the person publishing have it switched on.

Limits

• No client role. Anyone you invite is an admin or a member of the whole workspace and can work on every project in it. There's no login that lets a client edit only their own site.
• No reselling or client billing. Anticode bills the subscriber. Charging clients is up to you.
• One workspace. Client sites live side by side in it; there are no separate sub-accounts per client.
• The security report stays Anticode's. It's computed by Anticode and says so; it's there for anyone who looks, whatever the plan.

Questions people ask

Will visitors to a client site see Anticode anywhere?

Not as branding. On a client's own domain with Agency, the only mention is the hosting disclosure in the Privacy Policy, plus the security report if someone visits its address.

Can my clients edit their sites themselves?

Only by joining the workspace, which gives them access to every project in it. Many agencies keep clients on review links and make changes for them.

Do I need to republish existing sites after upgrading to Agency?

No. The credits are removed as pages are served, based on the owner's plan.