Managed private cloud · Prague, Czechia

Your private cloud, operated by engineers who contribute upstream.

We run your private cloud so your team can build on it: OpenStack, Ceph and Kubernetes, plus the databases, messaging and tooling on top. Built new or taken over from your current setup, then operated with contractual response times, 24/7 or 8/5. Pure open source, nothing proprietary in between.

Talk to an engineer The software we operate

2010 Operating since
343 Commits to OpenStack
45 Upstream modules
24/7 Incident response

ultimum — platform status

$ ultimum status --deployment prod-cz

OPENSTACK   healthy   your own build · no proprietary layer
CEPH        healthy   HEALTH_OK · 3 replicas · scrub current
KUBERNETES  healthy   upstream, deployed with Kubespray
OBSERVE     healthy   Prometheus + Grafana + OpenSearch

# patches sent upstream  343
# next maintenance  scheduled, announced

$ _

Software we operate

22 open-source platforms, operated by one team.

Software we already run for customers. Use any part of it: one team operates the whole stack under one contract, so an incident never becomes an argument between three suppliers.

Infrastructure

Compute, network, block, object and file storage

Container platforms

Upstream Kubernetes, K3s and multi-cluster management

Data and messaging

Databases, brokers and streaming, clustered with automatic failover

Search and identity

Logging, search, single sign-on and secrets

Delivery and security

Source, registry, GitOps, error tracking and container security

OpenStack: the sixteen components → Every platform, with deployment options →

Upstream contribution

We contribute to the software we operate.

The figures below are current as of 11 September 2026, taken from Stackalytics — the OpenStack Foundation’s own contribution tracker — and independently verifiable. This is the distinction between a company that installs the software and one that maintains it.

343 commits to OpenStack across 45 modules
126,953 lines of code rank #50 of all companies
712 code reviews on other people’s patches
117 bugs resolved of 156 we reported

#14 of 131 companies, all time

Kolla — the OpenStack deployment toolchain

Kolla and kolla-ansible are the tooling by which OpenStack is deployed in production. Ultimum ranks 14th of 131 contributing companies over the project’s lifetime, with 244 commits and 645 code reviews. Where a deployment issue originates in the deployment tooling itself, the correction is made by our own engineers.

Still current

Contribution is ongoing rather than historical. Recent OpenStack releases, by company rank:

2025.1 Epoxy 35 commits #14
2025.2 Flamingo 22 commits #22
2026.2 Hibiscus 23 commits #18

Where the work goes

kolla-ansible 157
kolla 77
horizon 28
neutron 10
ansible-collection-kolla 9
freezer 5
+ 39 more modules

Source: Stackalytics. Lifetime totals, last updated 11 September 2026. Verify on Stackalytics →

Recognition

Listed in the OpenStack Marketplace.

Ultimum Technologies a.s. is listed in the official OpenStack Marketplace as a consulting and integration provider, and is a supporting organization of the OpenStack Foundation. The listing covers the components we deploy and operate for clients.

Ironic
Nova
Neutron
Cinder
Manila
Keystone
Glance
Horizon
Heat
Octavia
Designate
Barbican
Placement
Kuryr
Searchlight
Rally
Kolla-Ansible

View the Marketplace listing

Region served: Europe
Support languages: English, Czech, Slovak

Reference customers

Companies that trust us with their infrastructure.

Selected customers whose infrastructure we operate. Each logo is shown with that customer’s agreement.

Services

We build it new or take over what you run. Then we operate it.

Two ways to start, one way to run: new build or takeover, then operation under one contract with the same four activities and the same response times. Each cluster is priced on its own, so a contract can cover one database or the whole cloud.

How it starts

A New deployment A new deployment, designed and built by us, accepted by you.
B Takeover of an existing deployment An existing deployment, taken over from your previous provider or your own team.

What you get every month

01 Software Build ManagementOpenStack services only Your own build of the OpenStack source, maintained in your repositories.
02 Software Deployment Management Upgrades that remain upgrades rather than becoming migration projects.
03 Incident Management A service desk staffed by engineers who work at source-code level.
04 Software Operations The platform is watched, tuned and kept safe, not merely kept up.

Our services in detail →

Approach

The decisive question is where modifications end up.

Installing OpenStack is not the difficult part. What determines the cost of the following five years is how the modifications made along the way are handled.

01

Upstream, not a distribution

Deployment is from upstream releases. Where your environment requires a change, we write the patch and submit it upstream, so that the divergence maintained on your behalf diminishes over time rather than accumulating.
02

No vendor lock-in by design

Your platform contains no Ultimum-proprietary layer. Every component is software your organisation could obtain, audit and operate independently. What you procure is expertise, not a licence.
03

One team for the whole stack

Storage, compute, network, containers and observability are operated by the same engineers. There is no arbitration between suppliers while the platform is degraded.

Responsibility model. Everything inside the bracket is ours, including the escalation path between the layers.

Service levels

Response and resolution times, written into the contract.

Two service modes. Incidents are reported through the service desk in one of four categories, and the guaranteed times for each are below. They apply to every platform we operate.

Maximum response and resolution times by incident category and service mode
Incident category	Continuous 24/7		Standard 8/5
Incident category	Response	Resolution	Response	Resolution
A Critical The service is completely inoperable, or cannot fulfil its purpose at all	15 min	1 h	30 min	2 h
B High The service fulfils its purpose only to a limited extent	1 h	4 h	2 h	8 h
C Medium Functionality is reduced, but the service still fulfils its purpose	4 h	16 h	4 h	16 h
D Low Fully functional, or reduced only negligibly	12 h	48 h	12 h	48 h

Response time runs from your report until we start working on it; resolution time until we tell you it is fixed. Both count only during standby hours.
In Continuous mode, critical and high incidents (A and B) are worked around the clock, every calendar day. Medium and low incidents (C and D) are worked 9:00 to 17:00 Central European Time on Czech business days, which is also the standby window for every category in Standard mode.
An incident counts as resolved once a workaround restores the service. We remain obliged to eliminate the root cause.
You categorise the incident when reporting it; we confirm or adjust the category, and every step is recorded in the service desk.

Article 6.11 of the General Terms and Conditions, version 4.6, effective 1 July 2026.

Contact

Tell us about your deployment.

Describe the deployment and the issue. You will receive a reply from an engineer with direct experience of the same stack.

We reply within one business day. Your details are not added to any mailing list.