Company details
- Legal name
- Coffey Labs LLC
- Entity
- Limited liability company, organized in Arizona (Maricopa County), 2026
- Tax forms
- W-9 on request
- Currency
- US dollars
- Sales and billing
- hello@coffeylabs.com
- Security reports
- security@coffeylabs.com
- Privacy
- privacy@coffeylabs.com
Statement of work, in plain English
Every engagement is one page. This is what it says.
- Parties. Coffey Labs LLC and your company.
- Service. The advisory retainer, an architecture and deployment engagement, or the corporate team plan, as described on this site on the day you sign, with the software, systems or seat count named.
- Term. Retainers and team plans run twelve months from the day the invoice is paid, and don't renew on their own: we send a renewal invoice 30 days before the end, and you decide. A deployment runs until handover, then its included retainer runs twelve months.
- Delivery. In writing, by private email or a private issue tracker, with no on-call duty. Deployments add up to three scheduled calls and hands-on work through remote access you grant, on the systems the statement of work names.
- Response time. A written reply by the end of the next business day (Monday to Friday, Arizona time, excluding US federal holidays).
- Your part. You name up to three contacts and send what we need to answer (configuration, logs, versions, with secrets removed). On the retainer you run changes in your own systems; for a deployment you provide the servers and the remote access, and remove our access at handover.
- Confidentiality. What you send us stays private and is used only to help you. Security release notice is confidential until the public release.
- The software. Open source under its own license, unchanged by this agreement. Fixes we make go into the public project.
- Ending early. If we can't continue, you get a pro-rated refund for the whole months left. If you end it, the fee isn't refunded.
- Liability. Limited to the fees you paid in the twelve months before a claim. No liability for indirect or consequential losses.
- Law. Arizona law; courts in Maricopa County.
We'll review your own paper if your company requires it.
Billing
- Retainers and team plans: one annual invoice, due 15 days after it's issued (Net 15).
- Deployments: a fixed price in the statement of work. Standard deployments are invoiced half at signing and half at handover; larger ones 40% at signing, 30% at design sign-off and 30% at handover. Each invoice is Net 15.
- Changes in scope are agreed in writing before the work, at $1,500 a day.
- Payment by ACH bank transfer or card, through a Stripe invoice. Card details go to Stripe and never reach us.
- Or pay by card now. The advisory retainer and the corporate team plan can be bought directly through Stripe. You get a paid invoice at once, and the statement of work by email within one business day.
- Purchase orders are welcome; send the PO number and we put it on the invoice.
- W-9 sent on request with the quote.
- Services start the day payment arrives.
Documents we can send
| Document | How you get it |
|---|---|
| Quote | By email, after the contact or scoping form |
| Statement of work | With the quote; the terms are above |
| W-9 | With the quote, or on request |
| Support policy | Published: severity levels, escalation, covered versions |
| Security overview and subprocessors | Published: security |
| Your security questionnaire | Completed on request (SIG Lite, CAIQ or your own form) |
| Your NDA, MSA or data processing agreement | Reviewed and signed where reasonable |
| Invoice and receipt | From Stripe, as PDFs, by email |
Security answers
We'll complete your questionnaire, and we'd rather tell you plainly what we don't have than make you dig for it. The security page has the full detail, including subprocessors.
- Certifications. We don't hold SOC 2 or ISO 27001.
- Your data. We don't host your systems or your users' data. The retainer works from what you choose to send, and we ask you to remove secrets first.
- Remote access (deployments only). Through a named account you create on your VPN or bastion host, with multi-factor authentication, logged by your systems and removed at handover. We work only on the systems the statement of work names and don't take copies of your data. We'll sign your data processing agreement if you need one.
- Our releases. Built by CI from the public source. inbuxa's release images are signed and carry a software bill of materials.
- Vulnerabilities. Reported privately to security@coffeylabs.com, fixed in private, published as security advisories with the release.
- Services we run. LINUXexpert keeps account and study-progress data; payments go through Stripe. Details are in its privacy notice.
Open-source licensing, for legal teams
Do we need a commercial license to use the software?
No. inbuxa, ihasmail, ihasvpn and Cairn OBS are licensed under the GNU Affero General Public License (AGPL-3.0). Nothing is sold as a separate commercial license, and buying a retainer doesn't change the license you're using.
What does the AGPL ask of us?
Running the software unmodified, for your own staff or customers, asks nothing of you. If you modify it and let people use your modified version over a network, you must offer them the source code of your changes under the same license. Keeping your configuration private is fine; configuration isn't a modification.
Is there a paid edition with more features?
No. There is no paid tier, no locked feature and no license key. Every feature is in the public release.
What about the GPL-3.0 tools?
A few smaller tools are GPL-3.0. Running them internally asks nothing of you; the obligations only apply if you distribute copies.
Who owns the code?
Coffey Labs LLC holds the copyright in its projects. inbuxa-migrate keeps its upstream's Apache-2.0 or MIT license. The full table is on coffeylabs.org/licensing.
Contact
Use the contact form or email hello@coffeylabs.com with what you'd like to buy and who should get the invoice. You'll have a written reply by the end of the next business day.