About Acrosite

Building a simpler way to publish content on Git-backed websites

Acrosite was founded five years ago around a simple belief: modern websites should keep the ownership and performance benefits of Git, while content teams, agencies, and clients shouldn't need GitHub access just to publish, review, or schedule content.

Why we exist

Building is easier than ever. Running content still isn't.

Acrosite started where the friction actually lives — not in launching a site, but in keeping it updated, week after week, with a real team.

01Modern websites are easier than ever to build — but the day-to-day work of keeping them updated still gets messy.
02Agencies juggle content across many client websites, often with a different setup for each one.
03Writers and clients shouldn't need direct GitHub access just to publish or review a post.
04Developers shouldn't become the bottleneck for every small content change.
05Teams need a calm, predictable way to create, review, schedule, publish, and track content.

Mission

Make Git-backed publishing simple, reliable, and accessible.

For agencies, website owners, and content teams — a calm way to manage content on modern websites without GitHub complexity or heavy CMS overhead.

Vision

Continuous content workflows on modern websites — without the overhead.

A world where teams run ongoing content across Git-backed websites without custom admin panels, GitHub complexity, or enterprise CMS weight.

What we're trying to achieve

The goals that shape every release

Make publishing easier

Give modern websites a simpler way to publish content without a custom admin panel for every project.

Help agencies scale content

Let agencies manage client content without handing out GitHub access or rebuilding a CMS each time.

Keep content owned in Git

Preserve the ownership and performance benefits of Git-backed websites while removing the friction.

Support scheduling & review

Make scheduled publishing and review workflows a natural part of everyday content operations.

Make content modeling practical

Keep Posts, Pages, Custom Content Types, and Custom Fields flexible without becoming complicated.

Improve publishing visibility

Give teams clear Publish Logs and status so they always know what happened after a publish.

Product principles

How we decide what to build

Simplicity over complexity

Every feature should reduce work, not add another layer to learn.

Ownership over lock-in

Your content stays in Git, in your repository, under your control.

Practical over bloated

We favour the workflows teams actually use over a long feature checklist.

Client-friendly collaboration

Clients and reviewers get a safe, focused way to take part in publishing.

Developer-respecting architecture

We work with Git-backed setups instead of fighting or replacing them.

Publishing confidence

Clear status and logs so every publish feels predictable, not nerve-wracking.

Who it's for

Build a calmer 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.