A working system needs a clear plan after launch. Keep NMT involved for upkeep, operations or continued development, or take the agreed handover to your own team. No forced subscriptions.
Choose an arrangement around your team and system. Scope, price, responsibilities and any service levels are agreed in writing.
Keep the essentials in good shape.
For teams that manage their day-to-day operations and want agreed technical upkeep.
We agree the maintenance schedule, backup coverage and support channels.
Put the running of the system in the plan.
For organisations that want NMT to coordinate the agreed hosting and operational support.
Hosting providers, monitoring coverage, support hours and any response commitments are agreed in writing.
Keep building as the business changes.
For teams with an ongoing roadmap of useful improvements, integrations and new workflows.
Development capacity, priorities and release arrangements are agreed for each engagement.
Take the handover. Choose who runs it.
For organisations with their own technical team or a preferred support provider.
We agree the handover requirements and identify which hosting and third-party costs continue.
You retain ownership and control of your business data and the custom deliverables agreed for your project. NMT retains ownership of its pre-existing frameworks, libraries, tools and reusable technology unless otherwise agreed.
We define who manages access, hosting, monitoring, updates, backups and incidents. The agreement also records service dependencies, contact routes, support hours and the process for changing or ending the arrangement.
Recovery objectives, restore checks and escalation commitments depend on the system and agreed service. No universal uptime or response-time promise is implied.
Review the Trust CentreNo forced NMT support subscription is required. Your project agreement defines the custom deliverables, licences and handover. Hosting, domains and other third-party services can still carry their own charges, whether NMT manages them or your team does.
These are support arrangements to scope around your system. Pricing depends on the application, infrastructure, responsibilities and agreed service levels. The proposal records the services, fees and any exclusions before you commit.
Any support hours, response targets, availability commitments, recovery targets and escalation process are set out in the written agreement. This page does not imply a default SLA or round-the-clock support.
Yes. We plan data portability and a documented handover in the project scope. Source-code access, reusable NMT technology, third-party licences, account transfers and transition work are defined in the agreement so the responsibilities are clear.
Tell us what you want to manage yourself and where you need help. We'll define the responsibilities and propose a practical arrangement.
