Your product stays yours.
Handing your product to an outside engineer is a real risk, and the usual answer is a clause buried on page nine. Here is our position up front, so you can argue with it before you engage rather than after.
The firmware, schematics, layouts, mechanical files and documentation we create for your project are assigned to you as they are paid for. Assigned — not licensed back to you.
The specifics go into your agreement and are settled before work starts. If your own terms differ, better to sort it now than at handover.
What transfers to you
Ownership of the deliverables we create for your project is assigned to you as they are paid for. Defined per project, but normally:
Sources, not binaries
A deliverable you cannot rebuild is not much use. You get the repository, the toolchain versions, build instructions and the configuration to reproduce it — enough for another engineer to pick it up. Where something depends on a third-party tool or licence outside our control, we name it rather than leave you to find it.
What stays with us
Two things, said up front. General engineering knowledge stays ours — that is what you are hiring. Any pre-existing Volvix Systems tooling we bring stays ours too, licensed to you perpetually and royalty-free as part of your product. We name anything in this category before using it, so it is a decision rather than a discovery.
Third-party and open-source components
Components used in your product are recorded with their licences as part of delivery. If a licence could affect how you ship or sell the product, we raise it before relying on it. How a licence applies to your business is a question for your own advisers — we surface the facts, we do not advise on them.
When it happens
Rights pass as the work is paid for, not at the end of the engagement. Stop a project early and you keep what you have already paid for, in the state it has reached. The mechanism is whatever your signed agreement sets out.
Your product is not our portfolio
We do not publish your name, your images, technical detail, or the fact that we worked together, without your written permission. Every case study on this site is published with the client’s agreement. Our default is silence.
Scope of this page
This describes how we normally work, so you know what to expect. It is not a contract, an offer or a warranty. Your signed agreement governs the project and takes precedence over anything here.