HaakCo HostingHaakCo Hosting

Interactive demo · no signup

Your environment is a fishtank.

Fixed room, fixed water, no surprises. Stock the tank with WordPress, Moodle, your own Laravel, Node, Python, Go, Rust or .NET code, MariaDB, MySQL or PostgreSQL with replicas, and Valkey, then watch a simulated deployment.

One unit · 4 CPU · 4 GiB · 40 GiB NVMe · 3 engines · 8 stages

Step 1 · stock

One tank. One unit. Stock it.

Each environment is one tank with fixed room. A site brings the engine it lives in, a claim starts at 10 GiB, and every replica claims a full copy of it. Nothing is created or charged.

1 in the stack · draft

Tank 01 · homeStocking
Colours

Click an inhabitant to move it out

Start from a stack

Managed sites

  • WordPress

    The site your visitors land on

    500m CPU · 1 GiB

    Brings MariaDB ×1 · stack after: 1,300m CPU · 2.3 GiB · 10 GiB storage

  • Moodle

    Courses, quizzes and enrolments, with its cron

    700m CPU · 1.3 GiB

    Brings MariaDB ×1 · stack after: 1,500m CPU · 2.5 GiB · 10 GiB storage

Your own code

  • Static site

    Files served as they are

    250m CPU · 256 MiB

  • PHP site

    Apache or php-fpm serving your tree

    500m CPU · 512 MiB

  • Laravel

    PHP app built with Composer

    500m CPU · 512 MiB

  • Node.js

    A Node process and its build

    500m CPU · 512 MiB

  • Python

    A WSGI or ASGI app built with pip

    500m CPU · 512 MiB

  • Ruby

    A Rails or Rack app built with Bundler

    500m CPU · 512 MiB

  • Go

    A compiled Go service

    500m CPU · 512 MiB

  • Rust

    A compiled Rust service

    500m CPU · 512 MiB

  • .NET

    An ASP.NET Core app

    500m CPU · 512 MiB

  • Container image

    An image you publish

    500m CPU · 512 MiB

Database engines

  • MariaDB

    Smallest engine floor

    300m CPU · 768 MiB · 10 GiB storage

  • MySQL

    Same server share as PostgreSQL, plus its Router

    900m CPU · 896 MiB · 10 GiB storage

  • PostgreSQL

    Its own engine, with a WAL archiver

    900m CPU · 896 MiB · 10 GiB storage

Cache

  • Valkey

    Redis-compatible cache

    300m CPU · 256 MiB

Curated components

  • Infisical

    Secret manager, on PostgreSQL and the cache

    500m CPU · 1 GiB

    Brings PostgreSQL ×1 and Valkey ×1 · stack after: 2,200m CPU · 2.6 GiB · 10 GiB storage

  • Supabase Auth

    Sign-up, sign-in and tokens on PostgreSQL

    500m CPU · 768 MiB

    Brings PostgreSQL ×1 · stack after: 1,900m CPU · 2.1 GiB · 10 GiB storage

  • Supabase REST

    A REST API over your PostgreSQL schemas

    500m CPU · 768 MiB

    Brings PostgreSQL ×1 · stack after: 1,900m CPU · 2.1 GiB · 10 GiB storage

Your stack

1 entry
  • Tools

    500m CPU · 512 MiB

    Included

Example resource pool

1 in the stack
CPU500m of 4,000m · 3,500m left
Memory512 MiB of 4 GiB · 3.5 GiB left
Storage0 MiB of 40 GiB · 40 GiB left

You choose how to spend the storage. A replicated service uses its claim once per replica — two replicas use twice the storage — and anything you leave unallocated stays spare.

reconcile · hosting-demo-4f2a

idle · waiting for a deploy

CLI examples · replace the placeholders

$ hostingctl environment create --company YOUR_COMPANY --name demo --dry-run

$ hostingctl environments --company YOUR_COMPANY

$ hostingctl environment show ENVIRONMENT_UUID --company YOUR_COMPANY

$ Simulated deployment log

Add to the stack, then deploy.

The tank is a metaphor. The plumbing is real.

Choose what you need

Pick your applications and services. Hosting checks the whole allocation against your capacity pool before it changes anything.

See what is running

You see each change as it happens, and you know when your site is actually live.

The tank is a demo. The platform is not.

Ready for your own project? We recommend Professional (2×) for most projects, with Premium (3×) offering extra headroom for larger workloads and growth. Compare the sizes and choose the capacity you need.

No card needed to create an account. Prices are published, so there is no quote to wait for.