Ship products,
not plumbing.

One config, everything generated

Declare your stack once.

A single .stack/config.nix describes your apps, services, secrets, ports, IDE settings, and deployment. Everything else — the dotfiles, the Caddyfile, the SOPS rules, the type-safe env modules — is build output.

{ pkgs, ... }: {
  stackpanel = {
    enable = true;
    name   = "myapp";
 
    # Apps get sequential ports from the hashed base
    apps = {
      web = { port = 0; };  # → :4200
      api = { port = 1; };  # → :4201
    };
 
    # Background services managed by process-compose
    globalServices = {
      enable = true;
      postgres.enable = true;
      redis.enable    = true;
      minio.enable    = true;
    };
 
    # Real HTTPS for *.myapp.local
    caddy.enable     = true;
    step-ca.enable   = true;
 
    # Editor settings + extensions, generated for the team
    ide = {
      enable        = true;
      vscode.enable = true;
      zed.enable    = true;
    };
 
    # SOPS recipients live in Nix
    secrets.recipients = config.stackpanel.users.allKeys;
 
    # Project commands available on $PATH
    scripts.dev = {
      exec        = "bun run --filter './apps/*' dev";
      description = "Start every app in dev mode";
    };
  };
}

Don't want to write Nix? Open the studio — every option has a form, and changes are written back to this file.

The dotfiles you would have written by hand.

Generated files live where every tool expects them, in formats every teammate already knows. Studio shows you which files are stale, which module wrote them, and what would change if you regenerated.

Local infrastructure

Production-shaped services on your laptop.

Stackpanel runs the same data stores you use in production — Postgres, Redis, MinIO — orchestrated by process-compose with health probes and dependency ordering.

Caddy and an internal Step CA give you real HTTPS at clean hostnames like https://api.myapp.local — so OAuth, secure cookies, and webhooks behave like prod.