Services

Three ways we are usually brought in.

Most clients arrive through the first and stay for the third. They are the same work at different speeds.

Rescue

Rescue for systems that have become difficult to trust.

Something is broken, or nobody is confident it will keep working. We start by understanding it, not by changing it.

What that covers

  • Production failures and sites that are down
  • Broken upgrades and deployments
  • Compromised sites
  • Linux and server problems
  • Forum and community platform failures
  • PHP application failures
  • DNS and Cloudflare problems
  • Database and performance issues
  • Abandoned or poorly documented systems
  • Emergency takeover when a developer or administrator disappears
  • Recovery after a migration or provider change goes wrong

How it goes

  1. Understand the symptoms and the business impact.
  2. Stabilize the system.
  3. Identify root causes and immediate risks.
  4. Repair, or provide a safe recovery path.
  5. Document what matters.
  6. Recommend what should happen next.

Tell us what happened

Migration

Move the system without losing what made it valuable.

Copying the files is the easy part. The work is in everything that accumulated around the old system: URLs, redirects, integrations, and the assumptions other software makes about how it behaves.

What that covers

  • vBulletin → XenForo, and other forum platform moves
  • Forum and community migration, including data conversion
  • Attachments and media
  • URL and redirect preservation
  • Server-to-server and hosting provider migration
  • PHP application migration
  • WordPress estates
  • E-commerce platform moves, for example Magento → Shopify
  • SEO-sensitive moves
  • DNS and Cloudflare cutovers
  • Staged migration and rollback planning
  • Post-cutover monitoring

How it goes

  1. Inventory.
  2. Risk and dependency mapping.
  3. Dry run on staging.
  4. Data conversion.
  5. URL and integration checks.
  6. Cutover.
  7. Verification.
  8. Post-migration monitoring.

Discuss a migration

Infrastructure Care

Technical stewardship for systems that need more than automated monitoring.

What you are buying is continuity, and an experienced person who already understands the system.

What that covers

  • Linux administration
  • Uptime and service monitoring
  • Backup monitoring and restore verification
  • Security updates
  • Forum and community platform maintenance
  • Application maintenance
  • Cloudflare and DNS
  • Domain and TLS certificate expiry monitoring
  • Performance
  • Incident response
  • WordPress estates
  • PHP and Laravel application support
  • Inherited legacy frameworks — maintenance and stabilization only
  • Documentation and vendor coordination
  • Planned maintenance

Talk about ongoing care

The stack

What we work in day to day. Listed so a technical reader can scan it and stop guessing.

Communities

XenForo · Discourse · vBulletin, including vBulletin 3 · phpBB · legacy forum platforms

Migration and data conversion between any of them, including databases that arrive incomplete.

Infrastructure

Linux · nginx · Apache · CloudPanel · Hestia · Cloudflare · DNS · MySQL / MariaDB · backups · monitoring

Applications

WordPress · Laravel · custom PHP applications

Development and automation

PHP · Python · shell · APIs and integrations

Including the reconstruction and database-merge tooling written for recovery work.

Inherited and legacy

Magento · older PHP frameworks

Maintained, stabilised or migrated away from. Not taken on as new build work.

Don't see your stack? Ask us. Understanding unfamiliar systems is part of the job.

Specialism

Still running vBulletin 3?

We are one of very few teams still working on it. Keeping old boards running, making them safer, and moving them when the time comes.

vBulletin 3 support