We build on it
Our default stack is open source: Next.js, Postgres, Vendure, Payload, n8n. We choose proven tools over proprietary black boxes, so any competent engineer can maintain the result long after we hand over.
Open Source
Code you can inspect before you hire us
Two of our packages are published open source on GitHub. They are not demos: they are production engineering, with tests, documentation and versioned releases. The rest of our products are built to the same standard and documented in the portfolio.
What Oronts publishes as open source, and why it matters
Oronts publishes the engineering behind its commerce and data work as open source: the Pimcore Asset Pilot Bundle and the Vendure Data Hub plugin. These are not demos. They are the same packages we run in production, with tests, documentation and versioned releases on GitHub. Our Vendure Customer Intelligence product is built to the same standard but stays proprietary, not open source. Publishing the two open packages does two things for you. First, it is proof you can inspect before you hire us: read the code, the commit history and the issue tracker, and judge our standard for yourself instead of taking a sales claim on trust. Second, it removes lock-in. Open packages mean the work lives under a license you can keep, fork and run without us, so the relationship stays earned rather than enforced by a wall around your own platform.
- Inspectable proof: real production code on GitHub with tests, docs and versioned releases, not a polished demo
- No lock-in: open licensing means you can keep, fork and self-host the packages without depending on Oronts
- Two packages published: the Pimcore Asset Pilot Bundle for asset work and the Vendure Data Hub plugin for commerce data
- The same standard we sell: client systems are built the way these public packages are built, with full code ownership written into the contract
How we work with open source
Open source is not a marketing badge for us. It is how we keep the systems we build inspectable, maintainable and yours.
We publish what generalizes
When a piece of our work is useful beyond one client and safe to share, it goes on GitHub with tests, documentation and versioned releases. You can read the real engineering before you hire us.
You own what we write
Full code ownership is contractual. The system we build for you lives in your repository, with the quality gates and documentation that keep it healthy once the engagement ends.
No lock-in by design
Open formats, standard APIs and documented architecture mean you are never trapped. You stay because the work is good, not because leaving would be painful.
Published on GitHub
Vendure Data Hub
Enterprise ETL and data integration plugin for Vendure. Visual pipeline builder, 9 extractors, 61 transform operators, 24 entity loaders, and feed generators for Google Merchant and Amazon.
TypeScriptNestJSVendureReactAdmin UI Extension
Pimcore Asset Pilot Bundle
Rule-based digital asset organization for Pimcore: configurable rules, priority ordering and audit logging for libraries that grow faster than teams can sort them.
PHPSymfonyPimcoreGitHub Actions
How to work with our open-source code
You do not have to take our word for the quality. The packages are public, so you can evaluate them on your terms before any commitment.
01
Read the code and the tests
Start on GitHub. The tests and documentation show how each package actually behaves and what it guarantees, not just what a README claims.
02
Try it in a spike
Pull it into a throwaway branch and run it against your real data. Open source means you can prove it fits before you commit a budget.
03
Tell us your context
Most real systems need adaptation. Bring your constraints, your stack and your edge cases, and we scope what it takes to fit your environment honestly.
04
We build the production slice
We extend it into a system you own, in your repository, to the same engineering standard you can already inspect in the public packages.
Built with the same discipline
Proprietary Oronts products, documented case by case in the portfolio.
- OGuardAI
Semantic data protection runtime for AI systems. Policy engine, PII detection and reversible tokenization between your application and any LLM.
PythonFastAPIPydantic - Oronts AI Assistant
The production Mastra agent system answering on this site: five agents, four tools, streaming responses, and a hardened API layer. Try it in the corner of this page.
TypeScriptMastraVercel AI SDK - Vendure Customer Intelligence
Customer engagement plugin for Vendure: wishlists, reviews, loyalty points and cart recovery as one coherent domain instead of four bolted-on apps.
TypeScriptNestJSVendure - PimTx
Transaction and concurrency layer for Pimcore: field ownership, cooperative locks, version guards and an idempotency engine for multi-writer installations.
PHPSymfonyPimcore
Open source at Oronts: common questions
Two packages. The first is the Pimcore Asset Pilot Bundle, covering digital asset workflows that we run on real projects. The second is the Vendure Data Hub, an ETL and integration layer for commerce data. Each lives on GitHub with its source, tests, documentation and tagged releases, so you see the same code we ship, not a marketing fork. Our Vendure Customer Intelligence product is built to the same standard but stays proprietary, not open source.
Because it is the most honest way to prove how we build. Anyone can claim senior engineering on a sales call. Published code lets you read the structure, the tests and the commit history and decide for yourself. Open packages also protect you: the integration layers and bundles your platform depends on stay under a license you can keep and run, so you are never locked into Oronts to operate your own system.
Yes. That is the point of publishing them. The packages are licensed for you to install, run and adapt on your own infrastructure. Your team can clone them, read the docs and put them into a Pimcore or Vendure project without any engagement with us. When you do want help, you are hiring for the work and the support, not for permission to use the code.
The standard is the same; the scope is different. The public packages are reusable building blocks: the Pimcore Asset Pilot Bundle and the Vendure Data Hub plugin, each solving a defined problem. Client work composes those building blocks into a system tailored to your catalog, pricing, ERP and channels. Whatever we build for you is built to the discipline you can already see in the open code, and full code ownership is part of the contract.
Read it the way a senior engineer would. Check the test coverage and whether the tests are meaningful, read the documentation and the README, look at the release tags to see whether versioning is disciplined, and scan the issue tracker and commit history to judge how the code is maintained. Our packages are published precisely so this review is possible. If something is unclear, the repository is the place to ask, in the open.
This is how we build for clients
The same engineering standard, applied to your systems. Full code ownership is contractual.