Private beta · Compute credits included

Buildwithout being owned by your infrastructure.

A managed platform with explicit, portable workload boundaries that can evolve with your application, enterprise, and sovereignty requirements.

Start deployingRead the docs
Live control surfaceBronze workloads · Germany
api-service
main@a1b2c3d
Deploying
Connect
Build
Ship
Live
3 replicas12ms p99Portable spec
01·How it works

Four steps from source to a running service.

Connect a repository, build an image, deploy it, and watch it. Glenr keeps the workflow the same across every app.

01Source
active
Repository intakeconnected
acme / payments-apiprivate
main
commit8f2a19c
score.yamlvalid
Dockerfiledetected
push event accepted

Connect

Repository and workload definition accepted.

02OCI image
active
Build 0112.4s
builder / linux-amd64running
Clone source1.2s
Build image10.7s
Push registry0.5s
Image digestsha256:e7c4…91a

Build

A versioned image is built and stored.

03Runtime
active
Rolling release3 / 3 ready
payments-api:v2.1verified
cell / payments-prod

replica 1

replica 2

replica 3

Ship

The release rolls out inside the target cell.

04Telemetry
active
Service telemetrylive

Requests / minute

1,284

healthy

p95

84ms

errors

0.04%

replicas

3

Observe

Metrics, logs, and events stay attached.

02·What you get

Apps, databases, and observability, wired together.

An account contains a Kubernetes cluster; the cluster contains an isolated namespace; the namespace contains the software you deploy. Glenr names those layers Organisation, Group, cell, and Workload.

Organisationacme

Group · A Kubernetes cluster

hetzner-eu

Shared on Bronze. Dedicated from Silver.

cell · An isolated Kubernetes namespace

default

The Bronze ownership and workload-isolation boundary.

Workloads · An app, database, or function

Apps
Web services
2 replicas
Functions
Event-driven
0 inv
Databases
Managed Postgres
38 q/s
Contact sales
Sandbox
Agent runtimes
sleep
Runtime

Auxiliary infrastructure

Observability
Centralised metrics, logs, and alerts scoped to the Organisation.
Event Stream
An enterprise grade audit trail for every event.
Billing
Usage and invoices roll up to the Organisation under its tier contract.
Network isolation·Usage limits·Per-workload caps·365-day event retention

Cell isolation

Every Bronze Organisation receives a cell that maps 1:1 to a Kubernetes namespace, with network policy enforcing the boundary.

Bronze billing

CPU and memory are metered by the hour on Bronze. Dedicated and customer-owned tiers use different contracts.

Autoscaling

Set minimum and maximum replicas. Glenr adjusts capacity within those bounds as demand changes.

Private networking

Private DNS and service discovery connect apps and databases inside the cell.

03·Why Glenr

One workload spec. A documented exit.

Every app is stored as an open CNCF Score file and built as a standard OCI image on vanilla Kubernetes. Glenr manages the runtime; the workload definition remains portable.

Loading…

In practice

Runtime included

Cluster lifecycle, the deploy pipeline, observability, and the incident path are Glenr's job on managed landing zones. Billing follows the tier contract, not ticket volume.

01

Nothing proprietary

Inspect the exact manifests Kubernetes applies, or hand the same Score file to a different operator. Nothing here depends on Glenr-specific tooling to keep running.

02

Placement stays explicit

Region, infrastructure operator, and ownership boundary are stated plainly per workload. Specific residency requirements can be discussed before deployment.

03
04·Product roadmap

Product roadmap.

Live today, or talk to sales about what's shipping next.

View the full roadmap
Stagev0
Live
Apps
Web services
Databases
Managed Postgres
Observability
Metrics & alerts
Stagev0.1
Contact sales
Functions
Event-driven
Stagev0.2
Contact sales
Sandbox
Agent runtimes
Contact sales
Glenr DB MySQL + Redis
Managed MySQL and Redis added to the Databases primitive.
Contact sales
Glenr Queue
Durable background jobs with retries, dead-letter handling, and per-workspace metrics.
Contact sales
Sandbox GPU
GPU-backed machines for model experiments, evals, and heavy agent workloads.
05·Ownership & pricing

Product tiers

The boundary moves outward.

The ladder runs from an isolated environment to dedicated clusters, a customer cloud account, and customer hardware. The workload format stays the same.

  1. 01Live today

    Bronze

    A cell

    An isolated namespace on a shared cluster

    Billing

    Metered vCPU and memory usage, net of credits

  2. 02Contact sales

    Silver

    One Group

    One dedicated Kubernetes cluster

    Billing

    Fixed monthly base plus metered overage

  3. 03Contact sales

    Gold

    Multiple Groups

    Several dedicated Kubernetes clusters

    Billing

    Custom commercial terms

  4. 04Contact sales

    Diamond

    Groups in your cloud account

    Kubernetes clusters in a cloud account you control

    Billing

    Platform fee; no infrastructure usage invoicing

  5. 05Contact sales

    Platinum

    Groups on your hardware

    Kubernetes clusters on hardware you control

    Billing

    Licence plus support; no usage invoicing

Locate your boundary

Get started

Deploy your first service.

Create an Organisation and deploy into its Bronze cell from a repository or container image. New accounts include deployment credit, with no card required.

Start deployingReview pricing
Open Score spec·Standard OCI images·Documented exit·Bronze usage pricing