Managed open source hosting in Sweden

Where it runs

OSC's primary infrastructure is Elastx in Stockholm, a Swedish-owned provider, and the applications you deploy and the data they store are hosted in Sweden. Some supporting functions rely on providers that operate outside the EU/EEA, such as payment processing, optional third-party sign-in and our AI features; the current list, and the transfer safeguard we rely on for each, is at www.osaas.io/subprocessors. If your own application or a service you configure calls a third-party API, that data goes wherever that provider operates, and it is your choice whether it does. You can also self-host any of our open source components.

Who operates it

Eyevinn Technology AB, a Swedish company, operates the Open Source Cloud platform. Elastx provides the infrastructure underneath it: compute, storage, networking and managed Kubernetes.

What sits outside the EU/EEA

The answer above names the categories. For the providers themselves, where each one operates and the transfer safeguard we rely on, the sub-processor register is the authority. We link to it instead of copying it here, so this page cannot drift from it. If an entry is still being confirmed, the register says so.

How you leave

• Each service in the catalog is the unmodified open source project. What runs here also runs on your own servers or in another cloud.
• Your data leaves in the formats the projects already use: pg_dump for PostgreSQL, mysqldump or mariadb-dump for MariaDB, any S3 client for MinIO storage.
• Your app is built from your own git repository, so the code was never only here.

PostgreSQL and MariaDB, hosted in Sweden

Both run as managed services on the same Stockholm infrastructure as your app. You set the passwords when you create them.

• PostgreSQL

  Set a superuser password. A default database, a user name and setup SQL are optional.

• MariaDB

  Set a root password. A database, a user and that user's password can be created at setup.

If an AI agent sets this up for you, give it the recipe. The deploy steps come from our recipe for deploying an agent-written app; this one adds the location facts as fields an agent can read, plus MariaDB as an alternative to PostgreSQL.

Building with your own AI tool? How we run AI-built apps

Questions