edgeContinuum vs Fleio, in one line: Fleio helps you sell OpenStack resources and invoice for them. edgeContinuum turns the same infrastructure into managed Kubernetes, PostgreSQL, VMs and applications, with the lifecycle handled instead of handed over. Different halves of the same business, and most providers need to know which one is their bottleneck.
It is a mature billing system and portal, and it is very good at that job. What it does not do is operate the services above the infrastructure: clusters whose control planes you upgrade on request, node pools that autoscale, failed nodes remediated automatically, databases with high availability and in-place upgrades. That is the work that stops you selling anything beyond virtual machines, and it is what edgeContinuum automates. Start a free trial or book a call.
Selling plain IaaS today? You can still sell exactly that here, and add managed services to the same customers when you want to. That is a shorter journey than adding a service platform later.
Kubernetes as a product. Clusters through Cluster API with the OpenStack provider, dedicated or hosted control planes, control plane upgrades, node pools that scale and autoscale, and failed nodes remediated by health checks. Fleio exposes OpenStack Magnum, where the documented actions are resize, upgrade, get configuration, get certificate and delete.
PostgreSQL your customers do not operate. Instances under an operator with high availability, in-place version upgrades and storage growth, inside the same quotas and roles as everything else.
An application catalog. Helm and container applications, versioned, private to a project or published platform-wide, with your own registry credentials.
Authorization deeper than a portal login. Roles composed from individual permissions, granted to a user or a group at organization or project scope, so a client's own administrator delegates internally without involving you. See identity and access.
A portal hands the customer a primitive. They pick an instance, a volume, a network or a cluster, it is provisioned and metered, and from that moment it is theirs to operate. Everything after handover, patching, upgrading, scaling, recovering, becomes their problem or your support team's.
A managed service moves that line. The customer asks for a capability and the platform keeps it in the state they asked for, continuously. That is the difference between a support burden that grows with every customer and one that does not, and it is the whole reason to sell services rather than infrastructure. The architecture guide works through what that costs to build yourself.
Open a row for the detail behind it. Both products ship regularly, and where their documentation is silent we say that rather than claiming absence.
Sources: Fleio documentation 2026.08, their pricing page and release blog, checked September 2026.
Fleio is built around one business: selling OpenStack resources with the commercial machinery attached. If that is exactly your business and you never intend to widen it, that focus is a genuine strength.
Which makes the choice simpler than it looks. If you only ever want to sell OpenStack resources, both products can do that. Only one of them also lets you sell managed Kubernetes, managed databases and applications on the same infrastructure, to the same customers, without a second platform. Selling more per customer is the whole argument for the layer, and it is easier to add commercial tooling around a service platform than to add a service platform to a billing portal.
Running both is also perfectly coherent: Fleio keeps the invoices and the payment relationship, edgeContinuum runs the managed services and exports per-tenant usage into it. The one thing to decide deliberately is which portal your customers log into, because two front doors is a worse experience than one.
Tell us what you sell today and what you want to sell next year, and we will map what you could add to the same infrastructure and the same customers.
