ArchyPress Enterprise
Run ArchyPress in your own environment
When your content, data or rules cannot sit on shared infrastructure, ArchyPress Enterprise is self-hosted in your environment. Your data stays fully isolated, and its workflows and integrations are shaped around the way your team publishes.
The enterprise offer
Three commitments for your ArchyPress deployment.
Self-hosted in your environment.
We deploy ArchyPress for you, so your editors work in the same product, in an environment you control.
Full data isolation.
Your posts, pages, media and settings are kept separate from other customers' data.
Customisation.
We adapt workflows, integrations and configuration to how your editorial team works.
ArchyPress subscriptions run for you on the Archy platform; Enterprise runs in your environment instead. Where it runs, how isolation is set up, what we customise and how it is supported are agreed for each deployment.
What you get
What every deployment includes, and what we tailor to you.
The left column is ArchyPress as your teams can use it now. The right column is what we settle with you.
Every enterprise deployment includes
- ArchyPress self-hosted in your environment
- Full data isolation from other customers
- The blog editor and visual page builder, with preview, publish and unpublish
- AI drafts, rewrites, page outlines, images and video, generated in the background
- Workspaces, each with its own posts, pages, media, settings and navigation
- Sign-in with Google for your editors, and platform administration through your own Microsoft Entra ID tenant
- Writer and admin publisher roles, so AI can draft while a person decides what goes live
- An MCP server with OAuth sign-in for AI assistants, and a publisher API with revocable keys
- WordPress import for posts, pages and media
Tailored to your organisation
- The environment and region it runs in
- How isolation is set up for your organisation
- Templates, page sections and house style for your brands
- The OpenAI API-compatible model provider and models you use, and where requests are processed
- How your sites, brands and teams map to workspaces
- Which sign-in methods your people use, and which other Entra tenants you allow
- How roles and editorial review fit your teams
- Which of your systems and AI assistants connect, and how
- How your existing content moves across
- Integration with the Archy AI Platform, so workflows built in the ArchyAgents workflow editor can draft and publish in ArchyPress
- Support model, maintenance, updates and commercial terms
Tailored items are settled in discovery and written into your proposal.
Deployment overview
How an ArchyPress deployment fits together.
Your environment
Your identity provider
Your systems and AI assistants
Through the MCP server and publisher API
ArchyPress
- Editor and admin
- AI writing and media
- MCP server and publisher API
- Your published sites
Content database
Posts, pages, settings
Media storage
Images and video
AI model provider
Depends on your choice
Your readers
Reach your published sites
- ArchyPress runs inside your environment, isolated from other customers.
- Your content and media are stored in your deployment.
- People sign in through the identity setup agreed for your deployment.
- Your systems and AI assistants connect through the MCP server and the publisher API, with the access you grant.
- The AI provider, the models and where they run are agreed with you.
- Your sites are published to your readers from your deployment.
Identity and access
Your people sign in. Your assistants get only what you grant.
ArchyPress separates who works in a workspace from what an AI assistant or integration may do there.
In ArchyPress now
- People sign in with their Google account.
- Platform administration runs through Microsoft Entra ID. In your deployment, your own Entra tenant administers ArchyPress and can allow other tenants.
- The person who creates a workspace owns it.
- Publishers come in two roles. A writer can create and edit drafts; an admin can also publish, take content back to draft and archive pages. Workspace owners and admins decide who gets the admin role.
- AI assistants connect to the MCP server with OAuth sign-in. You choose the publisher and the access, and the assistant never sees your password.
- Access tokens last one hour and ArchyPress stores tokens only in hashed form.
- Disconnect an assistant or revoke a publisher key at any time in Admin → Publishers.
Topics we cover with you
- Which sign-in methods your people use.
- Using your own identity tenant for your people's sign-in.
- How roles map to your editors, reviewers and administrators.
- Which assistants and integrations get writer or admin access.
Data handling
Your content, kept apart and accounted for.
In an enterprise deployment your data is fully isolated from other customers. Here is how ArchyPress handles content, and what we document with you.
In ArchyPress now
- Each workspace keeps its own posts, pages, media and settings.
- Content is stored in a database and media files in separate media storage.
- ArchyPress's AI features run on Azure OpenAI.
- AI drafts, rewrites, images and video use your workspace's tokens; creating, editing and publishing content you wrote elsewhere does not. The balance is visible in Admin → Billing.
- Your systems can read posts and pages back through the publisher API.
Topics we cover with you
- Which data ArchyPress stores in your deployment, where, and for how long.
- How content and media are exported or removed at the end of the engagement.
- Which OpenAI API-compatible model provider and models your deployment uses, and where requests are processed.
- Which activity records your teams need, and where they should go.
Support
A named route to the team that builds ArchyPress.
ArchyPress users reach us through the support page. For an enterprise deployment we agree support contacts, hours, escalation, maintenance and updates as part of your proposal.
Getting started
From first call to your own ArchyPress.
Conversation.
Tell us what you publish, who publishes it and the rules your content must follow.
Discovery.
Together we define the environment, identity, data handling, integrations and customisation.
Proposal.
You receive a written scope covering deployment, customisation, support and commercial terms.
Deployment.
We set up ArchyPress in your environment and maintain and update it as agreed.
Part of the Archy AI Platform
ArchyPress is one product of the Archy AI Platform. A self-hosted ArchyPress can work with the platform: agent workflows your teams design in the ArchyAgents workflow editor draft and publish through its MCP server and publisher API, within the access you grant. If you are planning more than publishing, such as knowledge pipelines or other Archy products in your environment, the platform enterprise page covers the whole picture.
FAQ
Enterprise
Tell us where ArchyPress needs to run.
Share your environment, your publishing workflow and the rules your content must follow. We will come back with the questions that matter for a first scope and price.