Open Source. Open Journey.
Anyone can put two good words in a footer. This page is what they oblige us to do, written plainly enough that you can hold us to it.
Open Source
We build on open technology wherever it is genuinely the right tool. Postgres rather than a proprietary database you cannot export from. Frappe and ERPNext rather than a licence that reprices when you grow. Linux, containers, open observability, open model tooling.
The reason is not cost. It is leverage. Open foundations mean you can audit what runs your business, hire from a large pool of people who already know it, and change supplier without changing systems.
- Your data in an open schema you can query and export at any time.
- No licence cliff when your user count or revenue crosses a threshold.
- A dependency licence review, so nothing copyleft ends up somewhere it constrains you.
- The ability to hire any competent engineer to continue the work.
Open Journey
Software projects fail quietly. Someone knows in week four that the estimate is wrong, and the client finds out in month four. Open Journey is our attempt to make that impossible.
- Shared repository access from week one, not at handover.
- A backlog and roadmap you can open yourself, any day.
- Architecture decisions written down with the alternatives we rejected and why.
- Demos every two weeks with something you can click, not slides.
- Estimates that change out loud, in the week they change.
- A written handover so any competent team can take over.
The same rule applies to how we teach
Open Journey is not only a client promise. Learners see the real thing too.
Open curriculum
The full syllabus, module by module, is published before you pay anything. No mystery bonus modules, no unlock-at-checkout.
Open code review
Reviews happen in the open where the cohort can read them. Learning from someone else's mistake is cheaper than making it.
Open outcomes
We tell you what a cohort actually achieved, including the people who did not finish and why. Placement claims without denominators are marketing.
Open source, honestly answered
Ask us the awkward questions.
Who owns the repository. What happens if you go quiet. What licence is in dependency 340. We would rather answer those in the first call than in a dispute.