Services
Your applications, your registry, your hardware.
Marigold is free and open source, and everything in it works without a commercial relationship. Bay Information Systems builds and maintains it, and takes on paid work around it: applications built for your workload, registries that deliver them to your machines, and deployments on servers or cloud accounts you control.
The software is free under the MIT licence, in full. Paid work buys time from the people who build the platform.
What we do
01
Application development
Applications designed and built for your workload, from one model behind Open WebUI to pipelines across several model types. Existing AI tools moved onto Marigold, so they share one model cache and one GPU queue. You receive the source and a registry to install from. Porting an application →
02
Registries and distribution
An internal registry on your own network for your own applications. A mirror of vetted application versions, listed first on your machines so they install what your security team approved. The registry files carried onto an air-gapped network. Publishing a registry →
03
Platform deployment
Hardware sizing and model selection, then Marigold deployed on your own servers or inside your AWS or Azure account: a managed Postgres, GPU instances as workers, outputs in your own object storage. The fixed-price AI roadmap is the usual starting point.
Design partners
We are working with a small number of organisations that run Marigold on their own infrastructure and want a say in what the platform does next.
01
What you get
Hands-on help deploying, a direct line to the people building the platform, and priority on the features your workloads need: storage backends, registries, scheduling across applications, worker sizing.
02
What we ask
Real workloads, regular feedback on what works and what does not, and permission to describe the deployment, anonymised if you prefer, once it is running.
03
Who it suits
Teams that need AI applications on data that stays on their own infrastructure, and want to shape an open platform. Get in touch →
What each option costs and controls
| Criterion | Self-hosted | Applications and registries | 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 |
| What you receive | The open source platform | Application source and a registry you own | A running deployment and its configuration |
| Support | GitHub issues | Direct, scoped to the engagement | Ongoing, per contract |
| Data location | Your hardware | Your hardware | Your own cloud account |
Frequently asked
Is Marigold free?
Yes, under the MIT licence. If you run it yourself, you pay for your own hardware and electricity. Our benchmark runs have come to 5-25p in electricity per full model sweep.
What do you charge for?
Time: application development, registry setup and deployment work. The platform carries no licence fee.
Can we build and distribute applications ourselves?
Yes. Building and publishing are documented in full, and a registry is static files on GitHub Pages or any web server. See Building an application and Publishing a registry.
Will you host it for us?
A managed deployment runs inside your own AWS or Azure account, or on your own servers. Your data stays on infrastructure you control, and nothing is pooled with other customers.
What does a design partnership cost?
It depends on how much help you need, and it is agreed per partner. A partnership buys time and influence; the software stays free and open source either way.
Do I need a support contract to use Marigold?
No. The software works in full without one. Issues and questions go through GitHub.