Do we own what we build?
A fair question, and one worth answering before you build an operation on something rather than after. This page covers your data, your application configuration, and what leaving actually looks like.
"Ownership" usually means three different things at once
They have different answers, and conflating them is how people end up surprised.
Your operational data
The records your operation generates — inspections, work orders, production entries, personnel files. Yours. Exportable in standard formats throughout the relationship, not only at the end of it.
Your application configuration
The data model, screens, roles and automations built for your operation. Built for you, belonging to your organization under the terms of your agreement. The workflows you describe are not absorbed into a product other customers receive.
The platform itself
The Knomatic platform — the data engine, permission model, audit layer and infrastructure — remains Knomatic's, and is licensed to you. This is the part you are not buying, and it is deliberately the part you would not want to maintain.
What Genwright is not
Genwright is not a code generator that hands you a repository you could host yourself. That trade is real and worth naming rather than glossing.
What you give up is the ability to take the running system somewhere else and operate it independently. What you get in exchange is that you never have to: the permission model, audit trail, backups, monitoring and infrastructure are maintained by someone else, and they were maintained before your application existed.
If independent hosting of generated source is a hard requirement for your organization, say so on the first call. It is a legitimate requirement, and it points at a different kind of tool.
Can you get every record out, in a usable format, without asking permission? That is the question that determines whether you are dependent or merely a customer. The answer here is yes, and it is a platform capability rather than a support ticket.
Ownership questions
Who owns the data in a Genwright application?
You own your operational data. Export in standard formats is available throughout the relationship as a platform capability rather than a support request. Retention and deletion after termination are governed by your contract documents.
Who owns the application we build?
Application configuration built for your operation belongs to your organization under the terms of your agreement. Genwright does not claim ownership of the workflows you describe, and does not fold your configuration into a product delivered to other customers.
Can we take the application and host it ourselves?
No. Genwright builds configuration on the Knomatic platform rather than generating a standalone codebase, so there is no independent artifact to rehost. If self-hosting is a hard requirement, raise it on the first call — it points at a different category of tool and we would rather say so early.
What happens if we stop paying?
Termination, wind-down periods, data export windows and deletion timelines are set out in your contract documents. Ask to see those terms during scoping rather than at renewal; a vendor unwilling to show you the exit before you sign is telling you something.
Does Genwright learn from our data?
Your operational records are your data. Any question about model context, training or retention should be answered specifically for your deployment in writing during scoping, alongside the AI boundary described on the security page, rather than by a general assurance on a marketing page.
Ask to see the exit terms before you sign.
It is a reasonable request, we expect it, and the answer is in writing. Bring your counsel to the scoping call if that is easier.