Registration is coming soon. Acrosite is not open for sign-up yet.Contact us
For Agencies

CMS for agencies: a multi-project publishing workflow

Agencies manage content across many client websites. Acrosite is built for that — multi-project publishing with Team Members and Client Reviewers, review and scheduling, and Publish Logs — without building a custom CMS for every project.

Contact UsView Features
Per-project setups

May fit agencies that build or configure a separate content workflow for each client website.

Acrosite

May fit agencies that want one consistent publishing workflow across many client projects.

How to decide

The right choice depends on whether you want per-project setups or one shared multi-project workflow.

Side by side

Per-project setups and Acrosite, compared

Approaches differ by team and setup — verify current specifics against each tool's documentation.

Feature / workflow
Per-project setupsCustom CMS or mixed tools
AcrositeGit-backed publishing platform
Primary use case
Per-project setupsA separate setup per client website
AcrositeDesigned for content publishing operations across projects
Content model
Per-project setupsVaries per project
AcrositePosts, Pages, and Custom Content Types
Posts
Per-project setupsDepends on the setup
AcrositeAvailable
Pages
Per-project setupsDepends on the setup
AcrositeAvailable
Custom Content Types
Per-project setupsDepends on the setup
AcrositeAvailable
Custom Fields
Per-project setupsDepends on the setup
AcrositeAvailable
Git-backed publishing
Per-project setupsDepends on the setup
AcrositeAvailable
Access for non-technical users
Per-project setupsDepends on the setup
AcrositeNot required for writers or Client Reviewers
Team Members
Per-project setupsDepends on the setup
AcrositeAvailable
Client Reviewers
Per-project setupsOften handled ad hoc
AcrositeAvailable
Review & approval workflow
Per-project setupsDepends on the setup
AcrositeBuilt-in review and approval
Scheduled publishing
Per-project setupsDepends on the setup
AcrositeDesigned for this workflow
Content Calendar
Per-project setupsOften not consistent across projects
AcrositeAvailable
Publish Logs
Per-project setupsDepends on the setup
AcrositeAvailable
Multi-project agency workflow
Per-project setupsInconsistent across separate setups
AcrositeDesigned for multi-project workflows
Deployment trigger visibility
Per-project setupsDepends on the setup
AcrositeVisible in Publish Logs
SEO-focused publishing workflow
Per-project setupsDepends on the setup
AcrositeStructured fields support SEO workflows
Best-fit team
Per-project setupsAgencies comfortable maintaining many setups
AcrositeAgencies, website owners, and content teams

This is a high-level workflow comparison. The right fit depends on your website setup, team workflow, and publishing requirements.

What changes

What changes in the workflow?

With per-project setups
  • 01Each client website gets its own content workflow.
  • 02Tooling and process can differ between projects.
  • 03Consistency and client access depend on each setup.
With Acrosite
  • 01The team creates Posts, Pages, and Custom Content Types.
  • 02Writers and editors work without GitHub access.
  • 03Client Reviewers can review their assigned content.
  • 04Approved content can be scheduled.
  • 05Acrosite commits to GitHub and records Publish Logs.
Decision guide

When should you choose which?

If your priority is…
Better fit may be…
Why
One consistent workflow across clients
Better fitAcrosite
WhyMulti-project publishing with shared Team Members and Client Reviewers
Client review without GitHub access
Better fitAcrosite
WhyClient Reviewers approve assigned content without repository access
Scheduled publishing across projects
Better fitAcrosite
WhyApproved content can be scheduled and committed for you
Highly bespoke per-client editing
Better fitA custom or per-project setup
WhyEach project needs a fully tailored workflow
Git-backed ownership with a publishing workflow
Better fitAcrosite
WhyContent lives in Git with review, scheduling, and Publish Logs
What Acrosite includes

Publishing operations, built in

Review workflow

Move content through review and approval before publishing.

Scheduled publishing

Schedule approved content with date, time, and timezone.

GitHub publishing

Acrosite commits content to your connected repository.

Publish Logs

See trigger results and recovery context for each publish.

Client Reviewers

Clients review assigned content without GitHub access.

Posts, Pages & Custom Content Types

Model the content you publish across projects.

Custom Fields

Add the fields each content type needs.

Team Members

Give your team publishing roles without repository access.

FAQ

Common questions

Yes. Acrosite is designed for agencies and teams managing content across multiple client websites with Team Members and Client Reviewers.

No. Acrosite lets you run a consistent publishing workflow across projects without building a custom CMS for each one.

Yes. Client Reviewers can review and approve assigned content without needing access to the repository.

If a client needs a fully bespoke workflow that a shared tool can't cover, a custom per-project setup may fit better.

Try a simpler Git-backed publishing workflow.

Registration is coming soon. Contact us to talk through your publishing workflow, or read the docs to see how Acrosite works.

Contact UsRead Docs