Routine care
Updates, configuration changes and health checks are handled before maintenance becomes a crisis.
Managed technical support
Keep it online. Keep it clear. Keep improving.
Ongoing technical support for communities that need routine updates, dependable troubleshooting and planned improvements after launch.
UpdatesHealth checksFixesOptimisationConfigurationDocumentation
Why ongoing support
Small problems stay small when someone owns the technical follow-through.
Support is scoped around an expected workload, so priorities and boundaries remain clear for both sides.
Context retained
Less time is lost explaining the whole setup again whenever a change or issue appears.
Changes controlled
Backups, access, testing and documentation are treated as part of the work rather than an afterthought.
Possible future plans
Compare the levels being considered.
If support opens later, a written agreement would define workload, supported systems, communication channels and response expectations.
Essential Care
Expected monthly budget£50–£100per month
Routine upkeep for a smaller, stable setup.
- Routine plugin or software updates
- Basic bug fixes
- Small configuration changes
- Monthly health check
- Short maintenance summary
Community Care
Expected monthly budget£120–£250per month
More active maintenance for a growing community.
- Everything in Essential
- Weekly maintenance window
- Performance checks
- Agreed feature or configuration work
- Priority over one-off requests
- Monthly recommendations
Managed Operations
Expected monthly budget£300–£650per month
Hands-on technical ownership across multiple community systems.
- Server and Discord maintenance
- Incident investigation
- Ongoing optimisation
- Planned improvements
- Technical coordination
- Custom reporting and scope
Expected monthly budgets are early, non-binding estimates—not quotations. Final workload, response expectations and monthly price would be confirmed in writing before any agreement. Third-party hosting and licences are excluded unless stated. No bookings, contracts or payments are currently accepted.
Clear boundaries
Support works best when the responsibilities are explicit.
Before a plan starts, we agree what is supported, who controls each account, how changes are requested and what sits outside the monthly allowance.
High-volume development, guaranteed round-the-clock emergency cover and substantial new projects require a separate scope.
01Supported systemsThe exact servers, websites, bots or integrations covered.
02Expected workloadA realistic allowance for maintenance and small changes.
03Access and ownershipYou keep ownership; access is limited to what the work requires.
04EscalationUrgent issues and larger work are handled under agreed terms.
Pre-launch: These plan names illustrate possible support levels only. Availability, response expectations, included hours and emergency arrangements have not been opened for booking.
Support FAQ
Set expectations before anything breaks.
Would support cover projects you did not build?
That is being considered, subject to a future technical review. Existing quality, documentation, access and dependencies affect what can be supported safely.
Would a monthly plan guarantee 24/7 availability?
No planned service includes 24/7 coverage by default. Any future response target would need to be defined before a support service opens.
Could a future plan include new features?
That is being researched. Register interest with examples of the maintenance and development mix that would be useful.
Can I cancel a monthly plan?
Cancellation terms will be stated in the service agreement before the plan begins. No long-term commitment should be assumed from this page alone.
Need continuity?
Give the technical work an owner before it becomes urgent.
Describe the systems, current pain points and the level of help you expect each month.