Pricing
Clear pricing for urgent support, project work, infrastructure reviews and ongoing technical help.
Get clear, practical pricing for urgent issues, planned project work, reviews, migrations and ongoing technical support. We price by the situation so you can choose the right starting point without open-ended consultancy costs.
Production issue right now?
Emergency support is separate from normal project work.
If a live service is down, unstable or blocking customers, use emergency incident support. We focus on restoring service, identifying the cause and keeping you updated while work is underway.
Main ways to work with us
Pick the option that matches your situation
The same technology can be priced differently depending on urgency and risk. A simple DNS issue is not the same as a production migration, failed database, AWS security review or ongoing support arrangement.
Fixed Technical Fix
Best when there is a defined issue and you want a scoped technical fix with a clear expected outcome before work starts.
- Defined issue with a clear outcome
- Investigation, changes and basic testing included
- Scope confirmed before work starts
- Suitable when price certainty matters
Infrastructure Review
Best when you want risks, performance issues, account setup, backups, security and reliability reviewed.
- Risk-focused review of your setup
- Performance, reliability, backups and security considered
- Clear findings and practical next steps
- Useful before major changes or when ownership is unclear
Migration Project
Best for moving systems where planning, backups, testing, rollback and downtime control matter.
- Planned move with reduced downtime risk
- Pre-migration checks and rollback considerations
- Cutover support for production systems
- Handover notes after completion
Emergency Incident Support
3-hour minimum. Best for urgent production issues, service disruption, failed changes or business-critical systems that need fast attention.
- Urgent investigation and repair work
- Service recovery and stability checks
- Clear updates while work is underway
- Focused on getting business-critical systems stable
Technical Support & Project Work
Best for non-urgent application or infrastructure development, support requests, follow-up work or troubleshooting where the time needed is not known upfront.
- Planned application or infrastructure support
- Useful for development, configuration and follow-up requests
- Good when the time needed is not known upfront
- Billed by time used
Ongoing support
Monthly infrastructure support
For agencies and businesses that need reliable Linux, Docker, AWS, database, backup and web stack support without hiring a full-time platform engineer.
Essential
For light ongoing support, monitoring checks, backup checks, small fixes and advice.
- Suitable for small businesses and lower-change environments
- Monthly support allowance agreed in advance
- Additional work quoted or billed separately
Operations
For regular support, recurring infrastructure tasks and planned improvements across client or business systems.
- Priority response compared with ad-hoc work
- Ongoing improvements, checks and troubleshooting
- Useful for web agencies and businesses with production workloads
Priority
For higher-risk environments that need more hands-on monthly support and faster response expectations.
- More support time and operational involvement
- Suitable for revenue-critical infrastructure
- Scope, hours and response expectations agreed before starting
Typical work examples
Common work examples
These examples show the kind of work we commonly scope. Final pricing depends on access, risk, urgency, data size, production impact and whether the work needs testing or rollback planning.
AWS or cloud review
For account setup, IAM, EC2, S3, RDS, VPC/security groups, backups, cost waste, monitoring and reliability risks.
Docker container issue
For a single container that will not start, keeps restarting, exits immediately, shows health check failures, hits resource limits, has permission issues or needs log-based troubleshooting.
NGINX or Apache issue
For 502/503 errors, reverse proxy issues, redirects, headers, SSL, virtual hosts, upstream timeouts or web server configuration faults.
Backup and restore setup
For database backups, offsite storage, retention, restore testing, monitoring and disaster recovery documentation.
PHP-FPM or Gunicorn support
For worker timeouts, process crashes, high memory usage, socket issues, upstream errors or application server tuning.
MySQL or MariaDB performance tuning
For slow queries, high RAM usage, I/O pressure, configuration review, backup impact, index issues and application bottlenecks affecting production systems.
Migration project
For server moves, website migrations, Docker migrations, database migrations, DNS cutovers, rollback planning and production testing.
CDN or caching issue
For stale assets, cache-control problems, redirect behaviour or edge caching issues where the scope is clearly defined.
Automation or internal tools
For internal tools, scripts, integrations, admin workflows or operational automation where the scope is clearly defined.
Docker Compose troubleshooting
For multi-service Compose stacks with networking, volumes, environment files, reverse proxies, database dependencies or deployment workflow issues.
Security review
For AWS, Linux server, PHP app, Python app, WordPress or Nextcloud security reviews with practical remediation steps.
WordPress or WooCommerce speed fix
For slow checkout, high CPU usage, database load, PHP-FPM pressure, Redis/cache setup, CDN behaviour, plugins, theme complexity and hosting access.
Not sure what you need?
Send the issue and we will recommend the most sensible starting point.
If it is a small fix, we will say so. If it needs a wider review, emergency support or a project plan, we will explain why before work starts.
Something is down now
Use Emergency Incident Support. Best for outages, broken deployments, 502/503 errors, failed services, urgent DNS/SSL issues and production incidents.
You need planned time
Use Technical Support & Project Work. Best for non-urgent application or infrastructure development, support requests, follow-up work or troubleshooting where the time needed is not known upfront.
You know the problem
Use a Fixed Technical Fix. Best when there is a defined issue and you want a scoped technical fix with a clear expected outcome before work starts.
You are unsure what is wrong
Use an Infrastructure Review. Best when you need diagnosis, risk review, prioritised recommendations and a clear plan before implementation.
You are moving systems
Use a Migration Project. Best for server moves, website migrations, Docker migrations, Nextcloud migrations, cloud moves and DNS cutovers.
You need ongoing help
Use Monthly Infrastructure Support. Best for agencies and businesses that need reliable help without hiring a full-time infrastructure engineer.
Billing
How payment usually works
Pricing is kept clear so both sides know whether the work is a quick fix, a defined project, an urgent incident or ongoing support.
New customers
Fixed-scope work is normally paid upfront. Larger projects can be split into staged payments once the scope is agreed.
Emergency work
Emergency support is billed hourly with a 3-hour minimum. The goal is to restore service, reduce immediate risk and explain any recommended follow-up.
Projects
Migrations, infrastructure improvements and multi-service changes are usually quoted as projects with clear deliverables, assumptions and exclusions.
Retainers
Monthly support is paid in advance. Included hours, response expectations and out-of-scope work are agreed before the retainer starts.
Process
How support works
Pricing is clearer when the issue, risk and access requirements are understood before production work starts.
1. Send the issue
Tell us what you need help with, what system is involved, the business impact and any useful context.
2. We confirm the right route
We suggest emergency support, a fixed technical fix, an infrastructure review, a migration project or a retainer.
3. Scope and payment are agreed
Fixed-scope work is agreed before starting. Emergency work starts with the minimum support window.
4. Secure access and handover
We use temporary access where possible, provide progress updates, and send a practical handover note after the work.
Next step
Tell us what is happening.
Send the request, affected system if relevant, business impact, recent changes and any useful context, logs or screenshots. We will recommend the right starting point instead of pushing overlapping packages.