Pricing
Free to run. Paid, if you want help running it.
Marigold itself costs nothing: clone it, build it, run it on hardware you already have. If you want a second pair of hands -- architecture review, workflow design, or a deployment inside your own AWS or Azure account -- Bay Information Systems does that as separate, paid work.
No seat count, no usage cap, no tier to negotiate -- because there is no product to charge for. The software is free under its open source licence, in full, indefinitely.
Three ways to run it
01
Self-hosted, free
Run it yourself from the public repo. No cost beyond your own hardware and electricity -- our own benchmark runs have come to 5-25p in electricity per full model sweep. No support included; issues go through GitHub.
02
Consultation
Fixed-scope or day-rate work with Bay Information Systems to review or design a Marigold deployment: model selection, workflow structure, hardware sizing. You still run it -- we help you get it right the first time.
03
Managed deployment, your cloud
Bay Information Systems stands the stack up inside your own AWS or Azure account. Still the same open source Marigold, configured for you -- your account, your data, nothing routed through a third party.
What each option costs and controls
| Criterion | Self-hosted | Consultation | Managed deployment |
|---|---|---|---|
| Cost | None -- hardware only | Day-rate or fixed scope | Quoted per engagement |
| Who operates it | You | You | Bay Information Systems, inside your account |
| Support | Community / GitHub issues | Direct, scoped to engagement | Ongoing, per contract |
| Data location | Your hardware | Your hardware | Your own cloud account |
Frequently asked
Is Marigold really free?
Yes. The software costs nothing, under an open source licence. If you run it yourself, you pay for your own hardware and electricity, and nothing else.
What do you actually charge for?
Time, not software. Consultation and managed deployment are Bay Information Systems services built around Marigold, not a fee for the platform itself.
Will you host it for us?
Not as shared infrastructure. A managed deployment runs inside your own AWS or Azure account, so your data stays under your control rather than pooled on infrastructure we operate for multiple customers.
Do I need a support contract to use the open source version?
No. Nothing about the software requires a commercial relationship. Support and deployment work exist for teams who want them, not as a gate on using Marigold at all.