Ownership & Licensing
Goldstone builds both custom software and reusable software platforms. Your agreement identifies which parts are yours, which parts are licensed, how your data is handled, and what happens if the relationship ends — before development begins.
Always yours
None of this is conditional on staying with us, being on a plan, or being up to date on an invoice.
Everything the system holds about how you operate. Exportable on request, in a usable format, whether or not the relationship continues.
Any customer or client data you are entitled to control. It is yours, and it leaves with you.
Registered in your name from day one, in your own registrar account. Never in ours, and never as leverage.
Logos, marks, colours, and anything produced as your identity.
Copy, images, video, and documents you wrote or paid to have written.
Photography, footage, and material you supply for the build.
Analytics, Search Console, Business Profile, payment processing — created under your login, with Goldstone added as a delegated user rather than as the owner.
The distinction
Almost every serious build is a mix. Knowing which parts are which is the difference between owning a system and assuming you do.
Software written specifically for you, from nothing, solving a problem particular to your operation. Ownership of that work can be assigned to you as the project agreement defines. If that matters to your business, say so before the build rather than after — it changes how the system is put together, and it is far cheaper to plan for than to retrofit.
Some of what Goldstone sells already exists — platforms built once and licensed to the businesses that need them. Using an engine that already runs in production is usually faster and materially cheaper than commissioning the same thing again. You license its use under the agreement; Goldstone continues to own and maintain it.
Not every client has a licence. A build made entirely from scratch carries none.
Every build stands on things Goldstone brings with it: frameworks, libraries, engines, shared schemas, agent frameworks, automation logic, and platform components developed before your project existed and used across many. These remain the intellectual property of Goldstone Enterprises LLC unless an agreement explicitly says otherwise.
This is the part most often glossed over elsewhere. An agency promising you own "all the code" either does not reuse anything — which makes your build slower and more expensive than it needed to be — or has not read its own contract.
Leaving
Your data can be exported in a usable format whenever you ask, and the agreement says how. Domains are already in your name. Accounts opened on your behalf are opened under your login, not ours.
Goldstone does not use ambiguity around domains, credentials, or business data as a retention tactic. If leaving is ever difficult, that is a failure on our part rather than a feature of the arrangement.
Where a build is handed over entirely, that has its own procedure — repository, hosting, and any transferable services move to accounts you control, and we help you do it rather than handing you a password and wishing you luck.
If you need more
We can quote a custom-ownership structure when the project requires it. The price depends on how much reusable Goldstone technology must be replaced, separated, or assigned — which is a real engineering cost rather than a negotiating position.
Sometimes. Full IP transfer or exclusivity is available only when the underlying technology is eligible for sale and the economics make sense for both sides. Some Goldstone platform components are not available for transfer. We identify that before the project begins.
In short
Your data, content, brand assets, and domain are always yours. For custom-from-scratch work, ownership can be transferred as defined in the project agreement. Goldstone-owned platforms, reusable engines, frameworks, templates, agents, and libraries remain the intellectual property of Goldstone Enterprises LLC and are licensed to you. If full code ownership or exclusivity matters to your business, we can quote that option before work begins.
No. Your agreement identifies what you own, what is licensed, how your data can be exported, and what happens if the relationship ends. Goldstone does not use ambiguity around domains, credentials, or business data as a retention strategy.
This page explains the policy in plain terms. The signed agreement is the controlling document, and where the two differ, the agreement governs.
Your business and customer data, your domain, your brand assets, your original content and any accounts in your name are yours throughout, and none of it is conditional on continuing to pay. Custom-from-scratch work can be assigned to you as the agreement defines. Reusable Goldstone platforms, engines, frameworks, templates and libraries remain Goldstone Enterprises LLC property and are licensed to you rather than sold. Which parts are which is identified before work begins.
No. Your data and domain are yours and exportable, hosting moves to your own account whenever you ask, and there is no fee for leaving. What you cannot take with you is the reusable Goldstone technology your system may run on, because that is licensed rather than sold. Which components those are is stated before work begins, so it is never a surprise at the end.
Yes. Custom work is written with that in mind: standard tools, a version-controlled repository, and documentation intended for whoever comes next rather than for us. Where your system uses licensed Goldstone components, the agreement sets out what transfers and what stays licensed. If full ownership of the client-specific source matters to your business, it can be quoted before the build rather than negotiated after it.
Tell us what the system needs to do and who needs to own it. We will tell you which parts can be assigned, which are licensed, and what each option costs — before anyone signs anything.