Two tiers
Advisory retainer
$6,000 / year
12 months · one invoice · in writing
- Next-business-day written reply on every request
- 2 hours a month of architecture and configuration review
- Advance notice of scheduled security releases
- Help with up to 2 vendor security questionnaires a year
- Upgrade planning for each major release, including inbuxa 27.1
- Covers inbuxa: the mail server, Admin and Webmail
Architecture and deployment
Standard
$15,000 / deployment
4 to 6 weeks · half at signing, half at handover
- inbuxa on one to three servers, at one site
- A staging copy if you want one
- Up to about 500 users
- One straightforward migration, rehearsed first
High availability
from $25,000 / deployment
8 to 12 weeks · 40% signing, 30% design, 30% handover
- inbuxa on a cluster of four to nine nodes, or across two sites
- Failover designed, then tested with your team
- Backups and restores proven across nodes or sites
- Up to about 5,000 users
- Migration with cutover in batches
Kubernetes or large
Quoted usually $40,000 or more
Fixed quote after scoping · 40% signing, 30% design, 30% handover
- inbuxa on your Kubernetes cluster, installed with its Helm chart
- Or several sites, or more than 5,000 users
- Sizing, storage and chart settings designed for your cluster
- A phased migration and rollout
- Kubernetes starts once inbuxa's Helm chart reaches its first release candidate
Every size includes
- A written architecture you sign off before anything is built
- We deploy it with you, through remote access you control
- Up to 3 scheduled video or phone calls
- Runbook, and 30 days of hands-on fixes after handover
- Then 12 months of the advisory retainer
The advisory retainer is taking two founding customers at this rate, and the founding rate holds when you renew. Deployments are scheduled one at a time, so ask early if you have a date in mind.
Service levels
| What | Advisory retainer | Architecture and deployment |
|---|---|---|
| First reply | By the end of the next business day | By the end of the next business day |
| Business days | Monday to Friday, Arizona time (UTC−7, no daylight saving), excluding US federal holidays | |
| Channel | Private email or a private issue tracker | The same, plus scheduled calls |
| Architecture | 2 hours a month of written review. Unused hours don't carry over | A full written design for your environment, then the monthly review for a year |
| Security releases | Notice before public announcement, under embargo | |
| Vendor security questionnaires | Up to 2 a year (SIG Lite, CAIQ or your own form) | |
| Phone or video calls | Not included | Up to 3, scheduled in advance |
| 24/7 or on-call response | Not included | Not included |
| Access to your systems | None; we work from what you send us | Remote access you grant and revoke |
Severity levels, escalation, covered versions and what we need from you are in the support policy.
A next-business-day reply means a considered, written answer from a maintainer: a diagnosis, a fix, a workaround, or the specific information we need from you next. It is a response time, not a promise that every problem is solved in a day.
The advisory retainer
Written answers from the maintainers
Ask about configuration, an error in your logs, a migration, a performance question or a design decision. The person who answers wrote or reviewed the code in question. If it turns out to be a bug, we fix it in the public project and tell you which release carries the fix.
Monthly architecture and configuration review
Send us your configuration, topology or deployment plan (with secrets removed) and get back a written review: what's risky, what we'd change, and why. Two hours of our time each month.
Security release notice
When a security release is scheduled for software you run, you hear from us before the public announcement, with what's affected and how to upgrade. This is advance notice, never a delay: we don't hold back a public fix to create a head start, and you agree to keep the details confidential until the public release.
Vendor security questionnaires
Your security team needs answers about the software you're running. We fill in the parts about our code and our release process: how we build, sign and publish releases, how we handle vulnerability reports, what our software stores and where. Honest answers, including where the answer is "no".
Upgrade planning
Before each major release we review your setup against the upgrade notes and tell you what to expect. inbuxa 27.1 is the first one in scope. Reviews of Kubernetes deployments start once inbuxa's Helm chart reaches its first release candidate.
Architecture and deployment
For teams putting inbuxa into production for the first time, or rebuilding a deployment that grew without a plan. We design it, deploy it with you, hand it over, and then stay on as your advisors for a year.
Scope first, in writing
It starts with the scoping form: what you're deploying, where, for how many people and what it replaces. We follow up in writing with anything else we need. From that we send a statement of work that names the deployment: how many servers, sites and environments, and what's being migrated, with a fixed price for it. The price comes from the effort the job takes, so a one-server deployment and a multi-site cluster aren't charged the same.
Pricing by size
Every size includes the design, the deployment, the runbook, 30 days of hands-on fixes and 12 months of the advisory retainer.
| Size | Typical shape | Price |
|---|---|---|
| Standard | inbuxa on one to three servers at one site, a staging copy if you want one, up to about 500 users, one straightforward migration | $15,000 |
| High availability | inbuxa on a cluster of four to nine nodes or across two sites, with failover tested, up to about 5,000 users, cutover in batches | From $25,000 |
| Kubernetes or large | inbuxa on your Kubernetes cluster with its Helm chart, several sites, or more than 5,000 users | Quoted; usually $40,000 or more |
Kubernetes deployments start once inbuxa's Helm chart reaches its first release candidate.
On any size:
- Each environment beyond production and staging: $2,500
- Directory or single sign-on integration (LDAP, SAML, OIDC): $2,500
- Migration beyond the size's mailbox count: $1,500 per 1,000 mailboxes
- Archiving or legal hold set up: $3,000
- Calls beyond the three included: $750 each
Work outside the statement of work is agreed in writing first, at $1,500 a day.
Design
A written architecture for your environment: topology, sizing, high availability, backups and restores, DNS and mail authentication where it applies, TLS, monitoring and the security settings we'd choose. You review it, we revise it, and nothing is built until you sign it off.
Deployment, with you
We do the work hands-on through remote access that you set up and control: a named account for us on your VPN or bastion host, with multi-factor authentication, logged by your systems and removed at handover. Your people can watch or work alongside. We don't take copies of your data, and we only touch the systems the statement of work names.
Migration and cutover
If you're moving from another system, we plan the migration, run a test migration first, and supervise the cutover with your team at a time you choose.
Calls
Up to three video or phone calls, scheduled at least two business days ahead: usually a kickoff, a design review and the handover. More can be added at $750 each. Everything else stays in writing, so there's a record of every decision.
Handover and after
You get a runbook written for your deployment: how it's built, how to back it up and restore it, how to upgrade it, and what to watch. For 30 days after handover we fix anything in our work hands-on. Then the advisory retainer runs for 12 months, included in the fee.
Timing and payment
A standard deployment takes four to six weeks from the signed-off design; high-availability and larger ones eight to twelve, depending on how quickly access and decisions come through on your side.
For a standard deployment, half the price is invoiced when the statement of work is signed and half at handover. For larger ones, 40% at signing, 30% when you sign off the design and 30% at handover.
What neither tier includes
- 24/7, on-call or emergency response. Replies come on business days.
- Running it for you. After handover your team operates the deployment; we advise. We don't offer managed hosting.
- Calls and hands-on access on the retainer alone. Those come with architecture and deployment.
- Servers, cloud accounts and third-party licenses. You provide and pay for the infrastructure.
- Paid features. There aren't any. Feature requests go on the public roadmap like everyone else's; we'll tell you honestly whether and when.
- ihasmail, ihasvpn and Cairn OBS. For now, both tiers cover inbuxa only.
- Software we don't maintain. Your operating system, proxy, DNS or directory server, except where they meet ours.
- Legal or compliance sign-off. We describe what the software does; your auditors and counsel decide what it means for you.
How to start
Use the contact form or email hello@coffeylabs.com with your company name, the software you run and roughly how many users it serves. For the retainer you can pay by card and it starts that day, with the statement of work emailed within a business day; or ask, and we reply with the statement of work and an invoice, and it starts the day the invoice is paid. For a deployment, start with the scoping form. The full terms are in vendor information and the support policy.