plactl (rhymes with pterodactyl)

Private beta

Docker Compose to a live URL.
In your own AWS account.

You're shipping faster and more. Your platform should keep up. plactl grabs the compose file you already run locally and gets you production infra and ops, with the guardrails and paved roads a platform team would have built.

Platform setup: ~20 minutes.
First deploy: few minutes later.

No platform engineer required.

How it works

  1. Onboard your platform. Once, ~20 minutes.

    Point plactl at your GitHub Org and AWS Organization. plactl bootstraps accounts, environments, clusters, and devops machinery in your org.

    1 · Identity

    Platform name acme Platform email platform@acme.com

    2 · Environments

    Environments dev staging prod Region us-west-2

    3 · AWS accounts

    Member accounts create byo Cost preview ~$350/mo Alert at $500/mo

    4 · Credentials

    Session credentials temporary · they expire Create platform →
  2. Link your repos. The compose file is the contract.

    acme/orderscompose.yaml
    name: orders
    services:
      queue:
        image: softwaremill/elasticmq  ✨ real SQS
        ports:
          - "9324:9324"
      consumer:
        build: .
        deploy:
          replicas: 1
        environment:
          QUEUE_URL: "{{.queue.url}}"  ✨ injected
        x-pl:
          uses:
            .queue: receive  ✨ IAM + network
    acme/webcompose.yaml
    services:
      web:
        build: .
        ports:
          - "8080:8080"
        deploy:
          replicas: 1
        healthcheck:
          test: curl -f http://localhost:8080/healthz
        environment:
          QUEUE_URL: "{{pl.orders.queue.url}}"  ✨ injected
        x-pl:
          expose: true  ✨ public URL
          uses:
            pl.orders.queue: send  ✨ IAM + network
  3. Push.

    • Builds & Deploys: in your own account (no more flaky GitHub Actions runners).
    • Status on your PRs: checks and deployments land in GitHub.
    • Logs one click away: build and runtime logs on your own observability platform (no more Datadog bill).
    • Scoped AWS access: project-scoped VPN, org-scoped platform viewer.
    • Local dev: plactl compose prep to docker compose up.
    • Live URL: every exposed service gets one.

What plactl can and cannot touch

  • Access you can revoke. During bootstrap, plactl grants itself inspectable roles for infrastructure provisioning and operational delivery. Never transactional or customer data. A break-glass support role exists, visible and revocable like the rest.
  • Your runtime data never transits plactl. Logs and metrics stay in your account; plactl deep-links you into your own console.
  • Every infrastructure change is a Git commit in a repo you own.
  • Leave anytime. Clusters, state, DNS stay in your accounts. Nothing is held hostage.
Luke Diliberto

Who is this guy?

I'm Luke Diliberto, a staff platform engineer. Ten years building infrastructure, data, and ML/AI platforms — many of them HIPAA and SOC 2 compliant. I've built this platform inside companies multiple times; plactl is the version with the mistakes already made. It's your shortcut to the platform your team would build itself.

30 minutes.

A conversation about how your team handles infra today. If you're curious, a look at plactl in the last ten.