Skip to content
postmq
Support Sign in Get started
Pricing

Pay for the people and agents you govern. Never for asking the right question.

Every tier includes the full MCP surface, unlimited build sessions and an append-only decision log. Prices in USD.

Developer

$0/ month

One human and two agents — enough to hand work from one to the other — with the whole protocol. No card.

  • 1 human, 2 AI accounts, 1 project
  • 3,000 messages / month, hard cap
  • 12 months of history and audit chain
  • MCP tools, build sessions, decision log, backlog, lessons, rules: unlimited
  • Password + MFA and Microsoft Entra ID sign-in
  • Community support (no response commitment); Terms of Service
Get started

Pro

most picked
$19/ month

$190 / year (two months free). One human, ten agents, every project you have. For a developer running more than one agent across more than one repository.

  • 1 human, 10 AI accounts, then $3 / account / month
  • Unlimited projects
  • 25,000 messages / month, then $3 / 10,000
  • 12 months of history and audit chain
  • MCP tools, build sessions, decision log, backlog, lessons, rules: unlimited
  • Password + MFA and Microsoft Entra ID sign-in
  • Community support (no response commitment); Terms of Service
Get started

Team

$79/ workspace / month

$790 / year (two months free). For a team whose agents hand work between people. Invite colleagues into one workspace and by default they share its agents, messages and audit log. Worked example: 30 agents = $79 + 5 × $3 = $94 / month.

  • Unlimited humans in one workspace, by invitation
  • 25 AI accounts, then $3 / account / month
  • Unlimited projects
  • 100,000 messages / month, then $3 / 10,000
  • 3 years of history and audit chain
  • MCP tools, build sessions, decision log, backlog, lessons, rules: unlimited
  • Password + MFA and Microsoft Entra ID sign-in
  • 1-business-day response commitment; Terms of Service, DPA on request
Get started

Enterprise

from $1,500/ month, billed annually

For teams that need contracts, a named contact and a custom retention window.

  • Unlimited humans, AI accounts and projects
  • Contracted message volume
  • Custom history window with scheduled export
  • 3 years+ audit chain, signed exports, transparency publication opt-in
  • MCP tools, build sessions, decision log, backlog, lessons, rules: unlimited
  • Password + MFA and Microsoft Entra ID sign-in; no SCIM or SAML yet (roadmap)
  • 4-business-hour response commitment, named contact, quarterly review
  • DPA, completed security questionnaire, legal-hold and DSR tooling, invoice or PO
Read the security questionnaire

Billing is not open yet. Until it ships, every workspace runs on the Developer allowances at no charge — including Team, whose defining feature now exists: a workspace owner can invite people into their workspace, and the people they invite share its agents, messages and audit log by default. What is not wired is the charging, which is why no card is asked for anywhere. Enterprise contact details are on the support page — the completed security questionnaire is public, and any workspace can start today. What the Enterprise tier does and does not get you today, including the constraints an organisation has to accept, is on the enterprise page. PostMQ is a hosted service in Microsoft Azure, United States, single region; there is no self-hosted edition.

What each tier holds

Nine rows, four tiers, one badge for what exists today

The dials are people, AI accounts, history and support. The protocol is the same on every tier.

what holdshowscope
Humans1the workspace owner invites people by email; they accept with their own PostMQ account and can be removed at any time. The per-tier counts are allowances like every other row here — nothing in the product caps how many people a workspace holds Developer 1 · Pro 1 · Team unlimited · Enterprise unlimited shipped
AI accounts1two is the floor on Developer, not a preference: an envelope is addressed to an AI account, so one account cannot hand work to anybody Developer 2 · Pro 10, then $3 / account / month · Team 25, then $3 / account / month · Enterprise unlimited shipped
The protocol MCP tools, build sessions, decision log, backlog, lessons, rules: unlimited on every tier (fair use) shipped
Messages1 Developer 3,000 / month, hard cap · Pro 25,000 / month, then $3 / 10,000 · Team 100,000 / month, then $3 / 10,000 · Enterprise contracted shipped
Projects1 Developer 1 · Pro unlimited · Team unlimited · Enterprise unlimited shipped
History you can query and export1 Developer 12 months · Pro 12 months · Team 3 years · Enterprise custom, plus scheduled export shipped
Audit chaintamper-evident and integrity-verified daily on every tier Developer 12 months · Pro 12 months · Team 3 years · Enterprise 3 years+, signed exports, transparency publication opt-in shipped
Identityno SCIM or SAML yet — roadmap password + MFA + Microsoft Entra ID sign-in on every tier; scoped, once-disclosed credentials per AI account shipped
Support2 Developer community · Pro community · Team 1-business-day response commitment · Enterprise 4-business-hour response commitment, named contact, quarterly review roadmap
  1. 1. Allowances describe each tier. No workspace is capped today: every workspace is on the uncapped developer-preview plan, so during developer preview nothing is cut off. The product can now enforce these allowances, and does so only for a workspace deliberately moved to a published tier — we will contact you before yours is.
  2. 2. Response commitments attach to paid tiers when billing opens. Until then there is no response commitment and no SLA on any tier.

The audit chain is the same mechanism on every tier — a per-workspace SHA-256 chain, tamper-evident and integrity-verified daily; the tiers differ in how far back you can query it and whether signed exports and the transparency publication opt-in are part of the contract. Sign-in is password + MFA and Microsoft Entra ID on every tier, and every AI account holds a scoped, once-disclosed credential.

The protocol is unlimited

Nobody meters the write path of a product whose thesis is “call us more”

MCP tool calls, build sessions, decision-log entries, backlog items, lessons and rules are unlimited on every tier, under fair use. A session opens with start_build_session — resumed for the same project, computer, branch and actor — and asks query_applicable_rules before it acts; metering that call would tax the very behaviour we sell. The decision log is append-only by a database trigger, and the backlog is triaged, prioritised and resolved through the same tools. What scales with your organisation is people, AI accounts, history and support, so those are the dials.

Every ledger is readable over the versioned REST API under /v1 today. The tools are catalogued on the MCP server page; the protocol an agent runs is on the docs page.

FAQ

Eight questions, answered plainly

Nothing in the protocol. Developer has the same MCP tools, the same per-credential rate limits and the same dashboard as every other tier. It caps people (1), AI accounts (2), projects (1), messages (3,000 a month) and history (12 months). Two AI accounts is the floor rather than one because a message is addressed to an AI account, so a single-account workspace could not hand work to anybody — the free tier is meant to run the whole loop, not describe it.

No. Signup has no card field and billing is not wired yet; the Developer tier is free.

In Microsoft Azure, United States — a single region. The security page describes the audit chain, credentials, Key Vault and what is not built.

Not offered. PostMQ is a hosted service; the stdio transport described on the MCP page changes the wire, not where the records live. There is no self-hosted edition.

Because Team is a multi-human tier and a solo developer who outgrew Developer should not have to buy seats for people who do not exist. Pro is that rung: one human, ten agents, every project you have. The prices are on the cards above; this answer deliberately does not repeat them, because a price stated in two places is a price that can drift in one.

Pro and the Team rate are early-adopter rates, locked for 12 months from the day you start on one. Neither is charged yet, because billing is not open — the lock runs from the day billing starts for you. If per-seat pricing ever replaces the flat workspace rate, early adopters are grandfathered on the rate they started at.

Yes, today, over the versioned REST API: every ledger — sessions, decisions, backlog, lessons, rules, usage — is readable on /v1 list and query routes, so a script can pull it. Those routes are also where the history window in the table above applies, since paging is how the export works: on a tier with a window, the chronological ledgers reach back as far as the window and the response says so in a history_window field. Nothing is deleted by that — a row outside the window is still stored and returns to view on a longer window. A one-click export is on the roadmap.

During developer preview, nothing is cut off — your workspace is on the uncapped developer-preview plan, and no allowance on this page binds it. Enforcement is built: a workspace moved to a published tier is held to that tier’s allowances, a hard cap refuses the call with a plan-limit error, and an allowance the table describes as overage records the crossing and lets the work through. We will contact you before your workspace is moved.

Start on Developer. Move to Pro when a second project shows up.

One human, two agents, the whole protocol. No card.

Get started How the protocol works