What you own
You own the property; Armage owns the method. What happens the day you leave, written down now.
The system
Yours
The data
Yours, exportable
The method
Ours
Lock-in
None by design
01
Who owns what
| Item | Yours | Ours | Never |
|---|---|---|---|
| Source code and repositories | Yes | — | — |
| Design | Yes | — | — |
| Content | Yes | — | Yes |
| Configuration | Yes | — | Yes |
| DataExportable without asking us | Yes | — | Yes |
| Data schemaDocumented, version controlled with the code | Yes | — | — |
| Domain | Yes | — | — |
| Infrastructure accountsIn your name, or transferable to you | Yes | — | — |
| Secrets and documentationHanded over on exit | Yes | — | — |
| ComponentsWidely used open-source database, storage and frameworks | Yes | — | — |
| Hosting and storage providersBehind an interface; replaceable | Yes | — | — |
| IdentifiersThe industry standard where one exists | Yes | — | — |
| Commercial terms | — | — | Yes |
| MethodLibraries, tooling, patterns, reusable components | — | Yes | — |
| Anything built before meeting you | — | Yes | — |
Never: Armage never reuses it for another client. The binding version is in our Customer Terms, or in your signed agreement where one exists.
02
Export is a feature, not a request
- Format
- CSV for tables, JSON for structured documents, the original files otherwise.
- Readable by
- Another vendor, without our involvement.
03
If we stop working together
- Handover. Repositories, accounts, secrets, documentation and a full data export, to whoever you name.
- Transition. An agreed window in which we answer whoever takes over.
- Deletion. On your instruction, confirmed in writing: what and when.
- Exit fee
- None, and no clause that makes leaving dearer than staying.
Questions
Is the software open source?
No. What is built for a client is that client’s private property, on open standards and widely used open-source components so that someone else can maintain it.
Ask for the terms before you need them
Or writehello@arm-age.com