byoc.yourcompany.com - Generate Private Kubernetes Helm Charts with 1-click

BYOC (Bring your own cloud) distribution means serious big enterprise revenue for our customers. And LocalOps unlocks and streamlines this distribution so they can multiply revenue quickly.

SaaS companies often miss big value enterprise deals because they can’t fulfil all deployment needs of the enterprise. Enterprises in Fintech, Insuretech, Healthcare often ask vendors to deploy software on their own cloud environments / on-prem environments for data residency, security compliance and regulatory needs. And the modern means of distributing software privately is through Docker Images or Kuberentes Helm charts.

Docker Images vs Helm charts:

Docker images work very well for trivial applications with monolith architectures and single server setups. When you cross that even by a little - say add new services or scale individual services independently or cheaply, docker images cannot work. This also pose a serious restriction for software vendors when they scale their capabilities. Docker Images are not a future proof solution here.

On the other hand, Helm charts can capture all the services that make up your application. With options to configure and scale each individual component/service, charts can be installed/managed/scaled by enterprise IT teams in their Kubernetes clusters. Software vendors can remotely manage the installation or support them with documentation.

Challenge with Helm charts:

The most scalable packaging "Helm charts" is however not trivial to do.

Engineers need to learn/understand Kubernetes in great depth to prepare, test and release helm charts. It takes weeks for even seasoned Kubernetes pros to build & release charts that are production ready.

To host Charts safely, they have to store them in private registries (say AWS ECR) and somehow hand over keys for their customers to safely download and install them. Plus, they need an environment to test new versions and have to put together a continuous build, package and distribution pipeline in place to keep charts up-to-date with their growing code/architecture/services.

All of this takes huge amount of time, expertise and effort. This is why teams resort to Docker image distribution and somehow manage them in adhoc ways.

Our mission is to make BYOC / On-prem distribution super easy for everyone.

We have done all the heavy lifting in LocalOps so that your teams don't have to build any tooling or pipeline to package their Private Helm charts and make them ready for distribution. They can focus on building their product.

Generate Private Helm charts with 1-click:

Starting today, teams using LocalOps can generate Helm charts with 1-click that comprises of all their services and components and host them privately. They can release new versions any time and their enterprise customers can adopt them as they wish.

Connect a cloud account and create a new environment in LocalOps. This will create a Kubernetes cluster in the connected cloud account, ready to add and deploy new services. Then connect a Github account and deploy any code repository to run as service(s). After all services are deployed, generate a new versioned helm chart in 1-click and distribute it to your customers.

There is no limit on services you can add inside.

1. Github repos

2. Docker images

3. 3rd party Helm charts - say Clickhouse.

BYOC branch and Continuous releases:

In all your Github repos, you can dedicate a byoc branch that can have code you want to send to enterprise customer environments. This way, you can merge new changes to the byoc branch from your prod branch as and when you want to keep your enterprise customers updated.

After you merge, all services added in your LocalOps environment will get auto-updated. Your teams can then continuously test changes in this environment. And when it is time, they can just generate a new Helm chart version and release.

Generate License Tokens:

Charts are privately hosted by LocalOps. How would your enterprise customers then pull and install them?

Enter License tokens.

You can generate any number of License tokens from inside LocalOps account. And distribute them to your customers. They will have to use them when adding helm repo and installing the chart. Like this:

$ helm repo add your-awesome-app \
  "https://byoc.yourdomain.com/charts/your-awesome-app"
  --username license \
  --password replace_with_license_token
$ helm install my-app your-awesome-app/your-awesome-app —set "license.token=replace_with_license_token"

Without valid license tokens, your customers cannot pull chart updates.

Wait, but how would your customers find your Helm repo url or instructions to install charts?

Get your "byoc.yourcompany.com":

In LocalOps, you can set a custom domain called byoc.yourcompany.com and that will begin to show a neat Helm chart Installation guide for your enterprise customers to access and follow.

Like this:

Just go to your account settings and enter your custom domain “byoc.yourcompany.com” to start your BYOC distribution.

Just like shipping SaaS, but 2-4x more revenue:

Here is the fun part. This will all feel like SaaS for your engineering team. They can continue shipping code to github (in their byoc branch). And your environment in LocalOps will receive those commits and keep services up-to-date. You can then visit the console anytime and generate new chart versions as you see fit.

End customers can receive those updates in their own cadence.

Unlock enterprise revenue in days. Say YES to those $50K/$100K deals now:

With this, your teams can open up Bring your own cloud (BYOC) distribution in days and unlock those high value enterprise deals.

Have enterprise leads in flight? Talk to us.

Get in touch with us for a demo and we will get you started on the same day.