Vendor independence
MIT source and provider choice mean you can leave without rewriting the operating model.
Inspect the evidence01 / ENTERPRISE
OPEN SOURCE.PRODUCTION ACCOUNTABILITY.
For platform and AI engineering teams putting agent automation into governed environments—and the leads accountable for what happens there.
02 / WHY IRONCREW
KEEP YOUR OPTIONS. KEEP YOUR EVIDENCE.
Adopt the runtime without adopting a platform dependency.
Inside your infrastructure
Keep runtime state and tools inside your boundary; use Ollama when prompts must stay on-prem.
Inspect the evidenceAuditable end to end
Run journals, attributed HITL, captured model reasoning, SBOMs, signatures, and source create inspectable evidence.
Inspect the evidenceSmall operational surface
Start with one native binary. Add PostgreSQL only when durable shared coordination needs it.
Inspect the evidence03 / SERVICES
PAY FOR EXPERTISE AND PRIORITY.
Exactly three ways to buy direct maintainer work. No hosted edition. No artificial feature wall.
Support contracts
SLA-backed responses, upgrade and migration guidance, security advisories, and a named technical contact who works on the codebase.
Integration & consulting
Crew design, deployment into Kubernetes or OpenShift, PostgreSQL and provider setup, and human-in-the-loop pattern design.
Sponsored development
You fund a priority feature or fix. It lands in the open-source core, everyone gets it, and you get it first.
04 / HOW ENGAGEMENT WORKS
NO SALES THEATER. THREE STEPS.
Every engagement is scoped. The proposal states the boundary before delivery begins.
TALK
A working session with an engineer, not a qualification script.
SCOPE
A written proposal names the boundary, evidence, schedule, and commercial terms.
DELIVER
Work happens with direct maintainer access and verifiable acceptance criteria.
05 / PROCUREMENT FAQ
THE TERMS ARE PART OF THE SYSTEM.
Answers for the questions that show up after a successful technical evaluation.
What does the MIT license mean for our product?
IronCrew has no copyleft requirement. You can use and modify it inside commercial systems under the MIT license terms.
What are we paying for if the software is free?
The runtime remains free and open source. Commercial work buys maintainer expertise, bounded delivery, response commitments, and priority.
Does our data leave our infrastructure?
Runtime state and tools remain in infrastructure you control. Prompts go only to the model provider you configure; choose Ollama when those prompts must remain on-prem.
Can support include an SLA?
Yes. Response targets and escalation paths are defined in a scoped support contract rather than implied by the public repository.
Can you support our security review?
Yes. Releases include checksums, signatures, and a CycloneDX SBOM, and an engagement can include deployment and posture evidence for your review.
SCOPE THE WORK WITH THE PEOPLE WHO MAINTAIN IT