Who this policy covers
Customers with an active advisory retainer, a deployment engagement, or the twelve months of retainer that come with a deployment. It is part of every statement of work. If your statement of work says something different, the statement of work wins.
- Business days
- Monday to Friday, Arizona time (UTC−7, no daylight saving), excluding US federal holidays
- First reply
- In writing, by the end of the next business day, at every severity
- Channels
- Private email or a private issue tracker; scheduled calls on deployments
- Named contacts
- Up to three people on your side
- 24/7 or on-call
- Not offered
Severity levels
You set the severity when you write to us. We may suggest a different one, and we'll say why.
| Level | What it means | For example | After the first reply |
|---|---|---|---|
| 1 · Critical | Mail is down or data is at risk for most of your users, and there's no workaround | The server won't start after an upgrade; mail isn't being delivered; you suspect a compromise | Goes ahead of all other work. A written update every business day until it's fixed or worked around |
| 2 · High | An important feature is broken or badly degraded for many users, or a workaround is hard to live with | Calendars stop syncing; one node of a cluster keeps failing; a migration batch stalls | A written update at least every two business days |
| 3 · Normal | A question, a problem affecting a few users, or a review you've asked for | A configuration question; one mailbox misbehaving; the monthly architecture review | Worked in the order it arrived |
| 4 · Low | A feature request or a documentation gap | "Could inbuxa do X?" | An honest answer on whether and when, and an issue on the public roadmap |
There is no on-call or after-hours response. A Severity 1 problem that starts on a Friday night is answered on Monday. A deployment's runbook says what your team can do first, and inbuxa's undelete and backups are there for the worst case.
Escalation
If a reply misses its target, or you think we've got the severity wrong, reply on the same thread and ask for it to be escalated, or write to hello@coffeylabs.com with "Escalation" in the subject. Escalations go to the founder, who answers in writing by the end of the next business day.
What's covered
The software. inbuxa server, inbuxa Admin, inbuxa Webmail, the inbuxa installer, the CLI and inbuxa-migrate.
The versions. Every inbuxa release line that's still inside its security window, as set out in Versions and upgrades: the current series, and the series before it for three months after a new one ships. The 2026 line is covered until three months after 27.1 ships. Questions about release candidates are answered, but fixes land in the next candidate or release. If you're on a line that's past its window, we help you plan the upgrade.
Around the software. Your operating system, proxy, DNS, directory and mail clients where they meet inbuxa. We don't run them for you.
Not covered. ihasmail, ihasvpn and Cairn OBS, for now. Builds you've modified yourself get answers, but fixes target the public release.
Bugs and fixes
When a problem turns out to be a bug in inbuxa, we fix it in the public project. Fixes ship in the weekly release, and we tell you which release carries yours. Until then we give you a workaround when there is one.
Security problems are handled privately and published as security advisories with the release that fixes them. Retainer customers hear about a scheduled security release before the public announcement, under embargo. See Security.
What we need from you
- The inbuxa version you run and what changed before the problem started.
- Logs and configuration, with passwords, keys and other secrets removed.
- Names and addresses of up to three contacts, kept current.
- For a deployment: the remote access the statement of work describes, and someone on your side who can make decisions.
Service credits and refunds
There are no service credits. If we can't continue the service, you get a pro-rated refund for the whole months left, as the statement of work says.
Changes to this policy
We may improve this policy. A change never reduces what a signed statement of work gives you during its term.
Last updated 21 November 2026.