What you own when we build on our own platform
Your code is yours; the platform is licensed. The application code, specs, behavior catalog, and tests Greenfield Production Systems delivers are yours to keep, read, and change. The platform they run on — greenfield-ts and greenfield-wasm — is licensed proprietary technology, not open source today, with source-code escrow available as an add-on on premium plans and included with Enterprise, so you can recover the platform source if we ever cannot support it.
Updated
Building on a proprietary platform raises a fair question: if the platform is yours, what stops us from being trapped on it? The honest answer is to separate the two things that get conflated. Your software and the platform underneath it are owned differently, and both should be spelled out before you sign anything.
Your code is yours
The application code we write for you, the specs and architecture decisions, the behavior catalog, the tests, and the gate transcripts are delivered to you to keep, read, and change. That record is the deliverable as much as the running system is. It exists precisely so the next team can read what was built instead of guessing, and so you are not dependent on us to understand your own product.
The platform is licensed, with a recovery path
The platform your software runs on — greenfield-ts and greenfield-wasm — is licensed proprietary technology, not open source today. What protects you against the worst case is escrow: source-code escrow for the platform is available as an add-on on premium plans and included with Enterprise. A third party holds the platform source and releases it to you under defined conditions, such as our ceasing to support it, so the software stays runnable even if we are not around to run it with you.
If lock-in is the concern, the platform page lays out what the platform is and what you own, and a short call settles the licensing and escrow specifics for your situation before anyone commits.
Questions this answers
- If we stop working with you, can we keep running our software?
- You keep the application code, the specs, the behavior catalog, and the tests, so the system itself is yours. It runs on our platform, which is licensed; while the engagement is active you run on it under that license. For continuity beyond that, source-code escrow is available as an add-on on premium plans and is included with Enterprise. A third party holds the platform source and releases it to you under defined conditions, such as our ceasing to support it, so the software does not become unrunnable if we are not around.
- Are greenfield-ts and greenfield-wasm open source?
- Not today. They are proprietary platforms we build and maintain. We are weighing an open-core model but have not committed to one, and we will not claim a license we have not shipped. What we can offer now instead of open source is escrow: a contractual path to the platform source if we can no longer support it.
- What exactly do we own at the end of a build?
- The application code we write for you, the journey and API specs, the behavior catalog, the architecture decision records, the tests, and the gate transcripts. That record is yours to read, change, and hand to another team, which is the difference between owning a product and renting one from the only people who understand it.
- Why build on your own platform instead of a standard framework?
- Because the guarantees we make depend on it. Event sourcing, typed contracts, observability, and authorization are part of the runtime, so the audit trail and the discipline the gates enforce during the build are present in production by default rather than reassembled per project. The platform is what makes that consistency cheap to keep.
- Do you offer code escrow for the platform?
- Yes. Source-code escrow for greenfield-ts and greenfield-wasm is available as an add-on on premium plans and is included with Enterprise plans. A neutral third party holds the platform source and releases it to you under defined trigger conditions, so you have a recovery path that does not depend on us staying in business.
- We are in a regulated industry and need a real audit trail. How does that work?
- That is what greenfield-wasm is built for. Each handler runs in a sandbox with capability-scoped access, and every external call is written to an immutable log stamped with the caller's identity by the host, so actions cannot be forged after the fact and the history can be replayed for review. Both platforms are production-grade; we will still state plainly what is covered for your specific deployment before it touches anything you depend on.