Usecase · Self-serve deployments

Your internal developer platform. Self-serve your cloud. Ship fast.

Build the golden path once and give your team automated deployment on AWS, GCP or Azure. Engineers spin up environments, ship services and roll back — without waiting on a Jira ticket.

Sign up for freeSee a tour

No credit card required

Works on your cloudAWS logoAWSGCP logoGCPAzure logoAzure
Golden environments

Launch new projects in < 30 mins, not weeks of back-and-forth with DevOps.

Production-grade environments — VPC, Kubernetes, observability, secrets, networking — spun up on your cloud in a few clicks. Setup and tear down on demand. No DevOps personnel or Jira ticket required.

  • Spin up dev / qa / staging / prod on demand
  • Tear down idle environments in one click
  • Every env identical — same primitives, same defaults
Environmentsyour cloud
  • dev
    us-east-1
    running
  • qa
    us-east-1
    running
  • staging
    eu-west-1
    running
  • prod
    eu-west-1
    running
+ New environment · 15–20 mins to ready
CI / CD

Release new services in < 30s, with the golden path to deployments.

Connect a repo. Start deploying services in under 30 seconds. Every service gets its CI/CD on day one — DevOps doesn't have to wire this up service after service.

  1. git push

    developer

  2. webhook

    LocalOps receives

  3. build + push image

    your registry

  4. deploy

    zero-downtime

Out of the box

Auto-deploy on every git push

Devs merge to qa, uat or main — services roll out to the matching environment automatically.

Bring your own

Plug your existing CI into our deployment API

Already standardised on GitHub Actions, GitLab CI or Buildkite? Call our deployment API from your pipeline — keep the build, swap out the deploy.

Safe deploys

Zero-downtime deploys, and rollbacks one click away.

New versions come up before old versions go down. If a deploy goes sideways, re-deploy any past version straight from the deployments screen.

Recent deployments · apiprod
  • v1.42.312 min ago
    live
  • v1.42.22 hr ago
    succeeded
  • v1.42.1yesterday
    succeeded
  • v1.42.02 d ago
    succeeded
Observability

Every service ships with a pre-built monitoring suite.

Loki, Prometheus and Grafana come wired up with every environment — DevOps never has to set logs or metrics up again, service after service.

Logs

Loki

Every service streams logs by default. Search and tail without installing an agent.

Metrics

Prometheus

Per-service request rate, latency, error rate and resource usage — recorded automatically.

Dashboards & alerts

Grafana

Build dashboards and wire Slack / MS Teams alerts in the in-built Grafana — when you need to.

See monitoring in our docs

Cloud resources

Declare it once in ops.json — get production-grade cloud resources.

Declare the cloud dependencies your service needs in ops.json. LocalOps provisions them on your cloud with production-grade defaults — encryption, backups, IAM, networking — from day one.

See ops.json reference in our docs

ops.jsonAWS example
{
  "service": "orders-api",
  "type": "web",
  "resources": {
    "rds": { "engine": "postgres", "version": "16" },
    "sqs": ["orders.fifo"],
    "sns": ["order-events"],
    "s3":  ["orders-attachments"],
    "opensearch": { "version": "2.13" }
  }
}
  • Encrypted at rest
  • Private subnets
  • Least-privilege IAM
  • Backups
  • Tagged
Stacks

Works for your current stack, and any other your team brings.

  • Node.js logoNode.js
  • TypeScript logoTypeScript
  • Python logoPython
  • Go logoGo
  • Java logoJava
  • Ruby logoRuby
  • Rust logoRust
  • .NET logo.NET
Security

Security built-in, from day one.

  • Private networking & subnets

    Services live inside your VPC by default — internal traffic stays off the public internet.

  • Role-based access to cloud resources

    Scoped IAM roles for every service — no broad keys handed around.

  • Encrypted secrets

    Per-service secret store with versioning, encrypted at rest in your cloud's KMS.

  • Tagged resources

    Every resource LocalOps provisions is tagged for ownership, cost and environment.

  • Auto-attached security groups

    Service-to-service traffic is restricted to the security groups LocalOps configures.

  • Auto-renewing SSL certs

    Free TLS certificates for every public endpoint, renewed automatically. No cron jobs.

  • Encrypted data volumes

    Every persistent disk LocalOps provisions for your services is encrypted, all the time.

See all security controls in our docs

Get started

Unleash your engineering team, 4 steps to self-serve.

Self-serve from the console, or schedule a setup call and we'll do it together.

AWS logoAWSGCP logoGCPAzure logoAzure
Sign up for freeSchedule a setup call

  1. Create a LocalOps account

    Sign up with your work email — free, no credit card.

  2. Connect your cloud

    Attach a least-privilege IAM role on your AWS, GCP or Azure account.

  3. Invite your dev team

    Add engineers as members — they can self-serve from day one.

  4. Let them ship

    Spin up projects, environments and services — without a Jira ticket in sight.

FAQs

Questions platform teams usually ask.

Can't find what you're looking for? Email support@localops.co.

What does "self-serve" actually mean here?

Engineers can spin up a new environment, deploy a service, attach a cloud resource (RDS, SQS, S3, OpenSearch) and roll a deploy back — all from the LocalOps console, without filing a ticket with your platform team.

Don't we lose control by letting devs self-serve?

No. Platform/DevOps still owns the golden path — the environment template, IAM role, security defaults, allowed resources. Engineers pick from what's been blessed; they don't write Terraform.

How are rollbacks done?

Every deployment is versioned and listed under the service. Click any previous version → Redeploy. Same zero-downtime path as a forward deploy.

Can we keep our existing CI?

Yes. Either use the LocalOps default (git push → auto-deploy) or call our deployment API from GitHub Actions, GitLab CI, Buildkite or Jenkins — we just take over the deploy step.

What languages and frameworks are supported?

Anything that runs in a container. We have first-class detection for Node.js, TypeScript, Python, Go, Java, Ruby, Rust and .NET — and you can bring your own Dockerfile for anything else.

What cloud resources can devs request via ops.json?

RDS, SQS, SNS, S3, OpenSearch and Elasticsearch are first-class today, with production-grade defaults (encryption, backups, private subnets, IAM). The list grows — check the docs for the current set.

Where do logs, metrics and dashboards live?

Inside your environment, on your cloud. Loki for logs, Prometheus for metrics, Grafana for dashboards and alerts (Slack / MS Teams). No data leaves your cloud account.

How is access controlled across team members?

Members are invited per LocalOps account and scoped per environment. Cloud-side, every service gets its own IAM role — no shared admin keys.

Is there a free plan?

Yes — Starter is free for small teams. No credit card. Upgrade when you outgrow it.