Skip to content
All Posts
Eyevinn Technology, Open Source Cloud

Open-Source Services You Can Deploy Today, by Category

A tour of the open-source services you can provision on Open Source Cloud, grouped by category, all unmodified open source and yours to move anytime.

open-source
backend
baas
catalog
databases

If you want managed convenience without a proprietary platform underneath it, Open Source Cloud runs a catalog of 180+ services across 8 categories, every one of them unmodified open source. You provision the database, storage, search, analytics, and auth your project needs on demand, the same way you would on any managed cloud, except each piece is a real open-source project you can pick up and move whenever you want. Here is the lay of the land, by category, so you can see what is actually available before you start.

Databases and caches

The foundation of most backends. You can provision a managed PostgreSQL instance, including the pgvector variant for embeddings if you are building anything with AI search, and a Valkey instance for a Redis-compatible cache. These are the same open-source engines you would run anywhere, so the queries, drivers, and migrations you already know all apply.

Storage

For files, media, and backups there is MinIO, an S3-compatible object store. Because it speaks the S3 API, code and tools written for that API work against it unchanged, and moving your objects elsewhere later does not mean rewriting your storage layer.

Search

Meilisearch gives you fast full-text and typo-tolerant search without standing up a heavyweight cluster. It is a drop-in for the kind of instant-search experience most apps need and most teams do not want to operate by hand.

Auth and backend building blocks

You can provision an open-source authentication service to handle sign-in, sessions, and tokens, alongside the other backend primitives in the app-backend category. The point is that the pieces a backend-as-a-service usually bundles into one proprietary product are here as separate, swappable, open-source services.

Analytics

For privacy-respecting product analytics there is Umami, plus other open-source analytics options. You get the usage insight without handing your visitor data to a third-party tag.

Media

This is the largest single category in the catalog. Transcoding, packaging, storage, subtitling, and the rest of a streaming pipeline are all available as open-source services, which is why teams building anything that plays video tend to find an unusually deep bench here.

Developer tooling, office apps, and more

Beyond the core backend categories there are developer and CI/CD tools, office and productivity apps, and a long tail of other services. The full catalog spans 8 categories in total, and it grows as new open-source projects are added.

The thing they all have in common

Every service above is unmodified open source. That is not a detail, it is the whole design. Each piece is individually replaceable, so you are never assembling a stack you cannot take apart. The same services run on a hyperscaler account, on your own Kubernetes cluster, or on your own hardware, and moving any one of them is usually a connection-string change rather than a rewrite. Open Source Cloud is the convenient place to run them, not a place that owns them. You get the managed experience and you keep the exit.

Frequently Asked Questions

What open-source services can I deploy on a managed cloud platform?

On Open Source Cloud you can provision a broad catalog of open-source services across 8 categories, including PostgreSQL and pgvector databases, a Valkey cache, MinIO S3-compatible storage, Meilisearch full-text search, open-source authentication, Umami analytics, and a deep set of media and developer tools. Each is provisioned on demand and runs as unmodified open source.

Is a managed open-source service the same as a proprietary backend-as-a-service?

No. A proprietary backend-as-a-service bundles its components into one platform you cannot leave without a rewrite. On Open Source Cloud the equivalent components are separate, unmodified open-source services that are individually replaceable, so you keep the managed convenience without the lock-in.

Can I move these services off the platform later?

Yes. Because every service is unmodified open source, the same stack runs on a hyperscaler, your own Kubernetes cluster, or on-premise. Moving a single service is typically a connection-string change, not an application rewrite, since nothing depends on a proprietary SDK or export format.

Related Posts