Skip to content

Ametnes Platform#

Ametnes Platform is a control plane for operating open-source software in your own environment. It deploys production-configured services into Kubernetes clusters that you control - your cloud account or your data centre - and keeps them running: endpoints and certificates, authentication, capacity, and version upgrades, all visible from one console.

Your services run in your infrastructure: your data, credentials, and traffic stay there.

Why Ametnes#

Getting an open-source service running for a demo is easy. Running it in production is where the work starts. Every service has its own configuration model, its own security requirements, and its own upgrade path, and each one has to be wired into your network, certificate, identity, and monitoring infrastructure.

Doing that by hand usually means:

  • Reading through helm charts and undocumented values to work out what a production configuration looks like.
  • Enforcing authentication and issuing, then rotating, TLS certificates for every service.
  • Exposing services safely through load balancers and DNS.
  • Tracking new releases, applying security patches, and repeating the configuration work for every new service and every new environment.

Each of these is a few hours on its own, and the effort repeats for every service you add and every location you operate. Ametnes packages the pattern once and applies it consistently.

What Ametnes handles for you#

  • Provisioning. Pick a service, version, capacity, and architecture tier. Ametnes renders the production configuration and deploys it.
  • Secure endpoints. Every service gets an FQDN endpoint published through a load balancer, with a certificate that is issued and renewed automatically. See Network Access.
  • Authentication. Services are protected by a username and password or an API key, with SSO integrations where the service supports them. See Service Resources.
  • Capacity management. Storage is sized per service and compute is selected through the service's architecture tier, so the same pattern applies across the catalogue.
  • Version upgrades. Move a service to a new version by selecting it; the platform performs the upgrade in place.
  • One console for every location. All services across all of your clusters are visible in a single view.
  • Automation. Everything the console does is available through the API and the Terraform provider, so deployments can be scripted and repeated en masse.
  • Consumption-based pricing. Usage is billed in ACUs (Ametnes Capacity Units) with no per-user licensing. See pricing.

What you can deploy#

The catalogue spans data services, AI infrastructure, developer tooling, observability, and business applications. Highlights:

Browse the full list in the solutions catalogue or the resource reference.

Where it runs#

Ametnes runs on standard, conformant Kubernetes, so you can use the cluster you already operate:

  • Public cloud - EKS on AWS, AKS on Azure, GKE on Google Cloud, ACK on Alibaba Cloud.
  • On-premises - RKE2/RKE, kubeadm, and similar distributions.
  • Evaluation - a single VM or a KinD cluster for a proof of concept.

For production, see the production Kubernetes cluster guide and RKE2 requirements.

How it works#

  1. Register a location. Install the Ametnes Cloud Agent into a Kubernetes cluster and register it as a location.
  2. Create a service. Choose the service, version, capacity, and networking from the console, the API, or Terraform.
  3. Connect. Use the endpoint Ametnes provisions, with the credentials or SSO integration configured for the service.

A complete end-to-end example is available in the cloud agent example.

Next steps#