Usecase · In-VPC / BYOC

Skip the BYOC roadmap. Ship to your customer's cloud in 30 minutes.

Git push to deploy on your customer's private cloud, or distribute your packages behind license tokens — all from one console.

Sign up for freeSchedule a setup call
No DevOps skillset required
Why

Why companies ask to deploy in their cloud.

When the customer's CTO won't ship data to your SaaS, you need to ship your service to them.

  • Data residency

    Customer data must stay in a specific region, country or their own VPC.

  • Network latency

    Workloads need to sit close to the customer's data or internal services.

  • Data privacy regulations

    GDPR, HIPAA, DORA, regional sovereignty — the data can't leave their cloud.

  • Sensitive data

    Trade secrets, PII or production payloads they can't hand to a SaaS multi-tenant.

CTOs love us
Even if we had diverted all our engineering resources to doing BYOC in-house, it would have easily taken 10–12 man-months of effort — tooling, helm charts, templates, automating deployments. LocalOps has saved all of that for us, and unlocked a lot of enterprise deals for us.
SuprSend logo
Gaurav Verma · CTO / Co-Founder, SuprSend
Read SuprSend case study
Deployment modes

Offer any deployment mode your enterprise customers want.

Mode 1

BYOC, bring your own cloud / In-VPC

Connect your customer's AWS, GCP or Azure account. Deploy your service into their VPC and manage it remotely from LocalOps.

  • AWS logoAWS
  • GCP logoGCP
  • Azure logoAzure
See how BYOC works
Mode 2

Self-hosted, distribute helm charts

Let your customer's IT team deploy your packaged helm charts in their own Kubernetes cluster — with installation docs and instructions you ship alongside.

  • Helm
  • Kubernetes
  • Air-gapped
See how helm distribution works
Mode 1 · BYOC

Start deploying in your customer's cloud, in under 30 minutes.

No Terraform or Pulumi to write

Connect any number of customer cloud accounts. LocalOps wires up an identical environment in each — and rolls out new versions from your repo, continuously.

  • Spin up identical environments in every customer cloud
  • Git push to your byoc branch — deploys roll out continuously to all customer environments
  • Monitor and manage remotely with built-in Prometheus + Loki + Grafana
git push · byoccustomer clouds
branch
byoc
LocalOps build
  • acme-corp
    us-east-1
    AWS logoAWS
  • globex
    eu-west-1
    AWS logoAWS
  • initech
    us-central1
    GCP logoGCP
  • umbrella
    europe-west4
    GCP logoGCP
  • soylent
    eastus2
    Azure logoAzure
  • weyland
    westeurope
    Azure logoAzure
Every push to byoc rolls out to all connected customer environments. No per-customer pipeline to maintain.

See BYOC deployments in our docs

Mode 2 · Helm

Distribute helm charts, for self-hosted deployments.

No need to learn or understand Kubernetes

When the customer's IT team owns the cluster, ship them packaged helm charts behind license tokens. They run helm install — you keep version, install and access control.

byoc.yourdomain.comCustomer install
helm install
$ helm repo add acme https://byoc.yourdomain.com/charts \
    --username acme \
    --password $ACME_LICENSE_TOKEN
$ helm install acme/orders --version 1.4.2
Installs per customer
  • acme-corp
    v1.4.2
    12 installs
  • globex
    v1.4.1
    7 installs
  • initech
    v1.4.2
    3 installs
  • umbrella
    v1.3.9
    21 installs

  • 1-click packaged helm charts

    Generate a versioned helm chart from your service config — ready for your customer's IT team to install.

  • Per-customer license tokens

    Issue a unique token per customer. Distribute charts privately, and track how many times each one installs your chart.

  • Your own BYOC hub

    Host installation docs at byoc.yourdomain.com — generated by LocalOps, served from the same console.

See helm chart distribution in our docs

Get started

Let your team keep pushing to your byoc branch.

Self-serve from the console — or schedule a setup call with our engineers and we'll do it together.

Sign up for freeSchedule a setup call

  1. Sign up

    Create a LocalOps account with your work email — free, no credit card.

  2. Connect a cloud account

    Attach a least-privilege IAM role on AWS, GCP or Azure — yours or your customer's.

  3. Connect your GitHub repo

    Point at the repo you ship to enterprise customers from.

  4. Create services from your byoc branch

    Define your services once. Every push to byoc rolls out to every connected customer.

One console

Manage all your deployments, from one console.

BYOC and helm are two of three delivery modes LocalOps handles — your public SaaS lives in the same console.

Distribution partner

Let us be your BYOC distribution partner.

Our team supports every single delivery — sitting right alongside your engineers in your channel.

Slack logoMS Teams logoMS Teams
FAQs

Questions enterprise teams usually ask.

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

What's the difference between BYOC and self-hosted helm?

With BYOC, you operate the service inside your customer's cloud — LocalOps connects to their AWS/GCP/Azure account and you deploy and manage remotely. With self-hosted helm, the customer's IT team owns the install — you ship a packaged chart and license token, they run helm install in their own Kubernetes cluster.

How many customer cloud accounts can I connect?

There's no hard cap. Teams routinely run dozens of BYOC environments — every push to your byoc branch rolls out to all of them.

Do I need to write Terraform or Pulumi for any of this?

No. LocalOps provisions the cloud primitives — VPC, Kubernetes, observability, secrets, networking — in each customer cloud without you writing IaC.

How does the byoc branch work?

It's just a branch in your repo. Define your services once in LocalOps. Every push to byoc triggers a build and rolls the new version out to every connected customer environment, with zero downtime.

How do license tokens work for helm distribution?

You issue a unique token per customer from LocalOps. The token gates access to your private chart repo (helm install behind basic auth). You can rotate or revoke tokens any time and see install counts per customer.

Can we host the install docs on our own domain?

Yes. Point byoc.yourdomain.com at the LocalOps BYOC hub — the install instructions, license token onboarding and version notes are generated for you and served from your domain.

Where do logs and metrics live for BYOC environments?

Inside the customer's cloud. LocalOps installs Loki, Prometheus and Grafana into each environment. You see them remotely from the LocalOps console — customer data never leaves their cloud.

What if the customer wants air-gapped or sovereign-region deploys?

Helm-mode covers air-gapped. For sovereign regions on AWS/GCP/Azure, BYOC works as long as we can attach an IAM role — talk to us about the specific region and account constraints.

Does this need DevOps skills on my team?

No. The point of LocalOps is that your engineers don't have to learn Kubernetes, helm packaging or per-cloud IaC. They push to byoc; LocalOps handles the rest.

Is there a free plan?

Yes — Starter is free for small teams. BYOC and helm distribution are available on paid plans. Book a setup call to scope your specific deployment.