Registration is coming soon. Acrosite is not open for sign-up yet.Contact us
Git-backed publishingFor agencies and modern website owners

Publish content to GitHub.
Without giving clients
GitHub access.

Acrosite gives agencies and modern website owners one simple dashboard to create, review, schedule, and publish Posts, Pages, and Custom Content Types across Git-backed websites.

Contact UsSee how it works
No public GitHub access for clients. No custom CMS for every project.
GitHub AppMarkdown / MDXDeployment triggersContent stays in your repoMulti-project workflows
THE REAL PROBLEM

Your website is in Git. Your content workflow is everywhere else.

Agencies and website owners often have modern Git-backed sites, but publishing still depends on docs, Slack, reminders, developer time, and manual GitHub updates.

Clients Need Content Access, Not GitHub Access.

Clients should be able to review and approve content without seeing repositories, branches, commits, or deploy settings.

Writers Send Content Everywhere.

Drafts live in Google Docs, Slack, email, spreadsheets, and Notion — then someone still has to move them into the site.

Developers Become the Publishing Queue.

Simple blog posts, service pages, and landing pages keep turning into developer tasks.

Scheduling Is Too Manual.

Without a publishing layer, future content becomes reminders, cron scripts, or early commits that the website must filter.

Every Client Site Needs the Same Admin Work.

Building a custom CMS for every Git-backed project wastes time and creates inconsistent workflows.

HOW ACROSITE WORKS

From draft to GitHub commit in one clean workflow.

Plan content in Acrosite, route it through review, schedule the publish time, then let Acrosite commit the final Markdown/MDX file and trigger the configured deployment trigger profile.

  1. Connect

    Install the Acrosite GitHub App, select a repository, choose a branch, and configure content paths.

  2. Create

    Write Posts, Pages, and Custom Content Type entries with SEO fields, slugs, media references, and Custom Fields.

  3. Review

    Route content to Team Members or Client Reviewers for comments, approval, or requested changes.

  4. Schedule

    Choose the publish date, time, and timezone. Scheduled drafts stay in Acrosite until publish time.

  5. Commit

    At publish time, Acrosite validates the content and commits Markdown/MDX with frontmatter to GitHub.

  6. Trigger

    After the GitHub commit succeeds, Acrosite triggers the configured deployment trigger profile and records the result.

DraftIn ReviewApprovedScheduledPublished
CORE FEATURES

Built around real publishing workflows.

Scheduling, structured content, client review, and multi-project oversight — without an enterprise CMS in the way.

SCHEDULING

Schedule Once. Acrosite Commits and Triggers Deployment.

Drafts stay private in Acrosite until the scheduled time. When the job runs, Acrosite validates the content, generates Markdown/MDX, commits to GitHub, and triggers the configured deployment trigger profile.

  • Timezone-aware scheduling
  • Publish Now or schedule later
  • Publish logs for every attempt
  • Retry failed publishing where safe
  • Manual or automatic deployment trigger options
STRUCTURED CONTENT

Posts, Pages, and Custom Content Types.

Manage recurring editorial content, standalone landing pages, and structured content like Case Studies, FAQs, Services, Authors, Locations, and Testimonials.

  • Posts for blogs, articles, updates, and guides
  • Pages for landing pages, service pages, and location pages
  • Custom Content Types for structured project-specific content
  • Custom Fields without building a custom admin panel
CLIENT REVIEW

Route Reviews to Clients, Not Your Inbox.

Client Reviewers can review assigned content, comment, approve, or request changes — without access to GitHub, billing, team settings, or internal project configuration.

  • Client-friendly review experience
  • Assigned-content-only visibility
  • Approval and request-changes workflow
  • No GitHub or deploy settings exposed
MULTI-WORKSPACE

Workspaces, clients, and projects in one content control center.

Designed for agencies and developers managing multiple Git-backed websites across workspace, client, and project contexts.

  • Workspace → Clients → Projects
  • Multi-project content operations
  • Client Reviewers and Team Members
  • Content Calendar and Publish Logs
  • Built for multi-workspace agency growth
REPO-FIRST PUBLISHING

Who said your CMS has to live outside your repo?

Acrosite gives your team a clean publishing dashboard while keeping your published content inside your GitHub repository. Drafts and workflow live in Acrosite. Published content becomes Markdown/MDX files with frontmatter in your repo.

  • Published content stays in your GitHub repository
  • GitHub App access instead of personal access tokens
  • Markdown/MDX and frontmatter output
  • Configured deployment trigger profile after successful commit
See the workflow
CONTENT OPERATIONS

A complete content operations layer for Git-backed websites.

Acrosite is not just an editor. It gives agencies the operational layer they need around content creation, approvals, scheduling, publishing, and recovery.

Publish Logs

Every publish attempt records commit status, deployment trigger status, failure reason, and retry options.

PUBLISH LOG2026-06-01
Validated content0.4s
Committed to GitHub1.2s
Commit SHA saved0.1s
Deployment triggered0.3s
↻Retry available if needed

GitHub App publishing

Connect repositories with scoped GitHub App access and publish Markdown/MDX files safely.

Content Calendar

See upcoming Posts and Pages by date, status, project, and publishing readiness.

Content CalendarJun 1 – 7
M2
T3
W1
T4
F2
S·
S·
12 scheduled · 4 in review

Review Queue

Track content waiting for Team Member review, Client Reviewer approval, or requested changes.

SEO-ready fields

Manage slugs, SEO titles, meta descriptions, target keywords, canonical URLs, noindex controls, and Open Graph fields.

Media-ready workflow

Support SEO-friendly image filenames, WebP conversion, optimized media output, and safe media replacement rules.

BUILT FOR REAL PUBLISHING TEAMS

Built for agencies and modern teams who ship content every week.

Digital Agencies

Manage content across client websites without building a CMS for every project.

  • Client approvals
  • Multi-project publishing
  • GitHub stays internal
  • Affordable Team Member and Client Reviewer structure

SEO and Content Teams

Plan, review, schedule, and publish continuous content from one minimal dashboard.

  • Posts and landing pages
  • Content Calendar
  • SEO fields
  • Scheduled publishing

Developers and Studios

Connect GitHub once and stop being the bottleneck for every content update.

  • GitHub App
  • Markdown / MDX
  • Deployment triggers
  • Clear content paths

Modern Website Owners

Publish content on your Git-backed website without editing Markdown files directly in GitHub.

  • Posts and Pages
  • Scheduled updates
  • SEO-focused fields
  • Simple entry plan
TRUST BY DESIGN

Built to protect your repo, your clients, and your publishing workflow.

Acrosite is designed around least-privilege access, server-side authorization, protected deployment triggers, workspace isolation, and recoverable publishing failures.

GitHub App Access

Use scoped GitHub App access instead of asking users for personal access tokens.

Secrets Stay Server-Side

GitHub tokens, email-delivery keys, database service keys, and deployment trigger secrets never reach the browser.

Client Reviewer Isolation

Client Reviewers only see assigned review content. They do not see billing, GitHub settings, deployment hooks, team management, or unrelated projects.

Deployment triggers keep secrets server-side

Acrosite supports Manual / No Automatic Deployment and automatic Vercel deploy hook triggers, with more providers Coming Soon. Secrets stay server-side and only safe trigger results appear in logs.

Publish Logs and Retry

Publishing attempts are logged, failures are visible, and safe retry paths are available where possible.

Workspace Isolation

Workspace data, project data, content, reviews, and settings are permission-scoped.

DEPLOYMENT TRIGGERTested
Provider
Vercel
Last trigger
Accepted
trigger · ••••••••••••••••
FAQ

Common questions.

Everything else lives in the docs — and the support inbox is staffed by the people building Acrosite.

Open documentation
Not yet. Registration is coming soon. The plans, limits, and 14-day trial described on this site are what Acrosite will offer when registration opens. Contact us if you want to talk about your publishing workflow before then.
Acrosite is a Git-backed content publishing platform. It gives your team a dashboard for creating, reviewing, scheduling, and publishing content, while published content stays in your GitHub repository.
No. Team Members and Client Reviewers can work through Acrosite. Client Reviewers can review assigned content without seeing GitHub, billing, deployment triggers, or internal project settings.
Acrosite commits content to GitHub and triggers the configured deployment trigger profile. Supported trigger options are Manual / No Automatic Deployment and automatic Vercel deploy hook triggers, with more providers Coming Soon. The UI says “Deployment triggered” because Acrosite records the deployment trigger request and the response it receives, not deployment completion.
Drafts live in Acrosite while they are being created, reviewed, or scheduled. Published content is committed to your connected GitHub repository as Markdown/MDX with frontmatter.
Acrosite supports Posts, Pages, and Custom Content Types. You can use Custom Content Types for things like Case Studies, FAQs, Services, Locations, Authors, Testimonials, or Glossary items.
Yes. You can schedule approved content for a future date, time, and timezone. Scheduled content is not committed early.
No by default. Client Reviewers can comment, approve, or request changes. Publishing is controlled by authorized internal roles.
Acrosite supports Manual / No Automatic Deployment and automatic Vercel deploy hook triggers. Netlify, Cloudflare Pages, GitHub Actions, Custom Webhook, Render, DigitalOcean App Platform, AWS Amplify, GitHub Pages, and Firebase Hosting appear as Coming Soon and cannot be configured yet.
Yes, once registration opens. Acrosite includes a 14-day free trial so you can test the core publishing workflow: create content, invite Team Members and Client Reviewers, schedule or publish content, commit to GitHub, and trigger configured deployment trigger profiles. The trial includes one workspace and starter limits for projects, Team Members, Client Reviewers, Custom Content Types, scheduled/published items, and media usage. To start, you choose a plan and add a payment method; no subscription fee is charged during the trial, and unless you cancel before it ends, the plan you chose is charged when it ends.
START HERE

Bring Git-backed publishing under control.

Create content, route it through review, schedule it, commit it to GitHub, and trigger deployment — without turning every update into a developer task.

Contact UsSee how it works
GitHub AppMarkdown / MDXDeployment triggersClient ReviewersPublish Logs