Registration
Who controls the asset?
Record the registrant or owner for domains and other critical accounts, and establish the process for authorized changes.
Home
The team.
Your plan.
Your account.
The AI systems and websites we build and run, the plans that keep them running, and the account where you see invoices and manage your plan.
Go to the home pageMore from ORYNX AXIOM
Already a client? Ask us about an invoice, an estimate or your plan.
Contact your account teamWhat we do
AI systems.
From the first idea
to production.
AI products, agents and integrations, with websites as part of the system.
Explore all servicesAlready know what you need?
Not sure where to start? Tell us about your business.
Talk to ORYNX AXIOM
Ownership / Handover
Your domain and your content should always be yours. The code and platform access depend on your agreement. With ORYNX AXIOM, once the build is paid, your content, your domain and the finished site are yours to keep.
The component inventory
Your agreement identifies the delivered work, account control, licenses and exclusions. Our own terms are on the project terms page.
| Component | Control or access | Deliverable or dependency |
|---|---|---|
| Domain | Registrant, administrator, renewal billing and DNS access. | The domain account and its authorization are separate from source files. |
| Hosting | Hosting account, technical access and billing owner. | The server setup, settings, media and backups your site needs. |
| Content and data | Who supplies, approves and has rights to use it. | Export formats, media, structured data and the scope of any migration. |
| Custom implementation | What the project agreement transfers or licenses. | Source, templates, configuration and supporting documentation. |
| CMS / Platform | Accounts, license and supported version. | Content export does not necessarily include the application or the platform. |
| Extensions and media | Third-party terms, accounts and renewal owners. | Plugins, fonts, photography, feeds and other licensed dependencies. |
| Integrations | Authorized accounts, keys and operating owners. | Connection configuration, field mapping, failure handling and provider requirements. |
Account responsibility
A person can have technical access without being the account owner or the person paying for renewal. Make those roles explicit.
Registration
Record the registrant or owner for domains and other critical accounts, and establish the process for authorized changes.
Administration
Identify administrative and technical access, the recovery route and what ordinary editors are permitted to do.
Billing
Document license and service renewal responsibility. An expired subscription can affect a connection even when the website files have not changed.
Portability
Content, media, application code, configuration and third-party services are separate parts of a runnable system.
The information and its structure, in the available format. Review what the export includes and whether images or relationships are separate.
Templates and implementation files may be reusable within a particular platform. Paid themes and plugins stay under their own licenses.
A copy that runs also needs the server setup, settings, data and add-ons. Passwords and API keys are handed over privately, never in a shared file.
Hosted platforms, APIs and provider accounts are not files inside the ZIP. Document what must remain active or be replaced.
The delivery record
List the accounts and authorized roles, with recovery and transfer requirements.
Record source, content, media, configuration and any exports included in delivery.
Identify transferred work, licensed components and continuing subscriptions.
Explain the routine editing or operational tasks that the scope covers.
Identify the backup/restore owner, support route and dependencies that remain.
A checklist to take into any project.
Your ownership check
Ownership is usually a mix, so check each piece rather than assume. If you cannot confirm most of these, it is easier to sort out now than during a move.
The domain is registered in your business name, not a provider's.
You can point the domain wherever you need to.
If the site was custom built, you have the files another developer would need to take it over.
The words, images and video you paid for are yours to reuse.
Access sits under your own account, so the history stays yours.
Your access does not depend on one provider staying involved.
A list covering themes, fonts, plugins, apps and stock media.
No dispute about what you keep if you leave.
You own your content, but the site runs on the platform's system, and export options are limited. Check what you can actually take with you before you rely on it, and keep your domain registered in your own name.
Not automatically. Some agencies keep the files, the hosting or the domain. Ask in writing, before you start, whether you receive the files and whether the domain is registered to you.
No. You might own your content and domain while licensing a theme, or own custom code that runs on a platform you cannot fully export. The goal is knowing which parts you control and which you rent.
Continuity
A move is easier to scope when the current files, accounts, licenses and operating requirements are documented.
That depends on the delivered implementation, access, licenses and documentation. Make those requirements part of the agreement rather than relying on an informal assurance.
Not necessarily. An NXT content export contains content.json. The runtime, templates, media, configuration and license are separate considerations.
The approved project agreement and applicable policies identify your rights and responsibilities. Our privacy and project policy contains project confidentiality and intellectual-property provisions. This guide does not amend them.
Before you sign
Put the important details in writing.