Pass the security review. Keep the open core.
Hatamoto Enterprise will be the same Go binary with SAML, SCIM, scoped roles, review chains and an audit trail your security team can export. The Apache-2.0 core stays complete and free.
Planned for Enterprise
- SAML
- SCIM
- Scoped roles
- Review chains
- Audit export
- LTS
Shipped today, in the free core
Much of the checklist is already ticked.
- 01
Passkeys and two-factor
Authenticator apps, passkeys and recovery codes, with rate limits on every sign-in.
webauthn · totp - 02
Audit logs
Admin actions and every AI agent tool call, allowed or refused, are recorded with who and when.
admin · mcp - 03
Sandboxed plugins
Plugins run in WebAssembly with their own database role and only the permissions an owner grants.
extism · wazero - 04
Signed, reversible updates
Releases are checked against keys in your binary and roll back on their own if a health check fails.
canary · edge · stable - 05
Backups off the box
Scheduled backups with retention, copied to S3 or another off-site store.
s3 · off-site - 06
A private admin address
No /wp-admin for scanners to find. The admin lives at an address unique to your install.
hatamoto admin-url
Roadmap
What we are building, in order.
Free items land in the Apache-2.0 core for everyone. Each one links to its docs the day it ships.
- Next
More roles and one-step review
Author, Contributor, Reviewer and Read-only, enforced in the admin, the REST API and the MCP server. Any edit can be sent for review, approved or sent back with a comment.
OIDC sign-in
Sign in with Entra ID, Okta or Google Workspace. Accounts are created on first sign-in.
One audit log for everything
Every write, sign-in, permission and settings change in one searchable log, from people, API keys and agents alike.
- After that
SAML, SCIM and enforced SSO
Directory groups map to roles. When your identity provider disables someone, their sessions and API keys end at the same moment.
Custom roles and review chains
Roles scoped to a content type, locale or section. Review chains such as legal, then brand, then publish, with reminders.
Audit you can hand to an auditor
Hash-chained entries, retention rules, signed exports and streaming to Splunk, Datadog or any syslog target.
AI agent governance
A publishing policy per agent, required human sign-off for agent drafts and a report of everything agents changed.
- Later
Staging sites
Copy live to a named staging site with email, webhooks and backups switched off, test an update or theme, then promote it.
More than one server
Cache clearing across servers, scheduled jobs that run once and CDN purge hooks, for a site behind a load balancer.
Long-term support and a security pack
An LTS line with 18 months of security fixes, a software bill of materials, an outside penetration test and a data processing agreement.
Free and Enterprise
Where the line is, and why.
Today: passwords, passkeys, two-factor. Next: OIDC single sign-on.
SAML, SCIM provisioning, group to role mapping, enforced SSO.
Today: Owner and Editor. Next: Author, Contributor, Reviewer, Read-only.
Custom roles scoped to a content type, locale or section.
Next: one review step for any edit.
Review chains with several stages, reviewer groups and reminders.
Today: admin and agent audit logs. Next: one log for everything.
Tamper-evident log, retention rules, signed export, streaming to your security tools.
Today: scoped keys and a full audit of every tool call.
Per-agent publishing policy and required human sign-off.
Today: canary, edge and stable, with six months of security fixes for the previous major.
An LTS line with 18 months of security fixes.
Today: GitHub issues and private security reporting.
A support contract with response times and a security pack for procurement.
How Enterprise will ship
One binary. No call home.
- Build
The enterprise build
The same single binary, same version, same update channels, released the same day as core. Switching edition is swapping one file. Your database does not change.
hatamoto-enterprise - Licence
A signed file, checked offline
One licence per production install per year, staging sites included. Nothing is sent to us and the update check stays anonymous.
license.json - Add-ons
Signed connectors
Audit forwarders, DAM and translation connectors as sandboxed plugins, installed and granted like any other.
.hmp · sandboxed
Being straight with you
When we are not ready for you yet.
Enterprise is not released. If one of these is a hard requirement this quarter, tell us and we will tell you honestly whether and when it lands.
- SAML or SCIM in production today
- Several brands or sites run from one install
- A SOC 2 report or a recent third-party penetration test
- A headless content API for an app or mobile front end
What buyers ask first.
Will free features move into Enterprise later?
No. Anything that ships in the Apache-2.0 core stays there.
Is Enterprise a different product?
No. It is the same binary, version and database with extra modules compiled in. You can switch in either direction by swapping one file.
What happens when a licence lapses?
You get 30 days of grace with reminders. After that the install runs as the free core. Nobody is locked out: SAML users are sent a link to set a password first. Nothing is deleted, and renewing turns everything back on.
Does Enterprise send anything to you?
No. The licence is a signed file on your server, checked offline, and the update check stays anonymous.
How will it be priced?
Per production install per year, with staging sites included in the licence. Early-access teams get pricing directly.
When will it ship?
We do not give dates we cannot keep. The roadmap above is in build order, and early-access teams hear first and help set that order.
Tell us what your review needs.
Send your security questionnaire or a list of must-haves. A person reads every one.