kreativan.devStart a project

~/solutions/managed-hosting

in productiondocker · cloudflare edge · ci/cd

Managed Hosting

Your project, kept running.

I’m not a hosting company. I host and manage the projects I build, on the cloud and at the edge, so after launch you still have the person who knows your project inside out.

Where it runsHost my project

what managed means

I take care of it.

Backups, updates, monitoring and fixes keep your project fast, safe and up to date. You don’t have to think about any of it.

  • every night

    Backups

    Databases and files, kept off the server. Restores get tested, not just assumed.

  • all the time

    Monitoring

    Uptime and error alerts come to me, usually before anyone notices.

  • every week

    Updates

    Server, Docker images, packages and the CMS, kept current and tested before they ship.

  • always on

    Security

    SSL, firewall rules and Cloudflare protection in front of every project.

  • when you ask

    Changes

    Small fixes, new pages and improvements, through the same pipeline.

  • when needed

    Scaling

    More resources, caching or a move to the edge as the project grows.

already have a project?

Hosting usually comes with what I build. I also take over existing projects, case by case: I review the code and setup first, then move it to containers or the edge if it makes sense.

how changes ship

Every change takes the same road.

Updates, fixes and new features go through one pipeline. It’s boring on purpose.

  1. 01
    push

    Every change is a commit in Git. Nothing is edited on the server.

  2. 02
    test

    GitHub Actions runs the checks before anything ships.

  3. 03
    build

    A fresh Docker image, or a fresh build for Cloudflare.

  4. 04
    deploy

    Out to production. If something is wrong, the last version is one step away.

  1. git push origin main
  2. ▸ checks · lint, types, tests
  3. ✓ checks passed
  4. ▸ build · docker image
  5. ✓ image pushed
  6. ▸ deploy · production
  7. ✓ health check passed
  8. ● live

where it runs

Two homes for your project.

I pick the setup per project. Often it’s both: the site at the edge, the app and its data in containers behind it.

at the edge

Cloudflare

Sites and light apps run close to every visitor, with no server to patch.

Pages
Static and Astro sites
Workers
APIs, forms and server logic
D1
SQLite databases at the edge
DNS, SSL, CDN, WAF
In front of every project

in the cloud

Docker

Apps that need a server get their own containers, the same in development and production.

PHP apps
ProcessWire, WordPress, business apps
Node services
APIs, workers and queues
Databases
PostgreSQL, MySQL, SQLite; Supabase when it fits
Automation
Self-hosted n8n

honest version

I’m not a hosting company.

I don’t rent out servers. I run the projects I build, and sometimes a project I take over, so the person keeping it online is the person who knows how it works.

a hosting company

  • A server and a control panel
  • A ticket queue
  • “That’s your application, not our problem”
  • Generic plans and add-ons
  • Backups you have to remember

managed by me

  • Your project, running
  • A direct line to the developer who built it
  • The app, the server and the updates are all my job
  • A setup chosen for your project: edge, containers or both
  • Backups and monitoring that are already running

taking on projects

Hand over the keys.

Tell me what you run and where. I’ll tell you how I’d host it and what it takes to keep it running.

Email me