Moving away from Dibbla

How to take your apps, data and configuration off Dibbla — what you get, in which formats, how long you have, and what it costs (nothing).

You can leave Dibbla at any time — to another provider, or to your own infrastructure — and take everything with you. Nothing on the platform is in a format only Dibbla reads: your app is a git repository with a Dockerfile, your databases are PostgreSQL, your buckets are S3-compatible, and your configuration is a dibbla.yaml you wrote yourself.

This page is the procedure. It is what Chapter VI of the EU Data Act (Regulation (EU) 2023/2854) asks a data processing service to publish, and it matches §12 of the Terms.

What you take with you

What you do not get is Dibbla’s own platform software — the build service, the login in front of your app, the custom-domain and TLS handling, the scheduled checks. You do not need any of it to run your app somewhere else; the export says which of those things it stood in for.

How to do it

1. Export each app

   dibbla export my-app

   One directory per app: source/, databases/, buckets/, env/, dibbla.yaml, a docker-compose.yml that runs it all locally, and a README.md that says what is there. Secrets come by name only, with a blank for each value: a secret is write-only on Dibbla, and no export, command or API hands its value out — to you or to anyone else. Each value you set yourself is one you hold where it was issued (the provider’s dashboard, your password manager), and you set it at the new host, ideally as a freshly issued key. The ones Dibbla made for you (DATABASE_URL_*, STORAGE_*) point at Dibbla anyway: the export’s compose file replaces them with local ones, and the new host gives you its own. The app keeps running on Dibbla; the export changes nothing. Full details in the dibbla export reference.

2. Check that it runs without Dibbla

   cd my-app-export
   docker compose up --build

   Postgres restored from the dumps, MinIO seeded from the buckets, your app built from its own Dockerfile and pointed at both. If it works here, it works on any host that runs containers.

3. Move each piece to its new home

   Push source/ to your new git remote, restore the dumps into your new PostgreSQL, sync buckets/ into your new object store, and set the variables from env/ — and your secrets’ values — where the new host keeps configuration. Then point your domain’s DNS at the new host — if it was a custom domain, the CNAME to Dibbla is the only thing to change.

4. Close the account, if you are leaving

   Delete the organization in the account portal, or write to [email protected]. Either one is your notice. Your exports still work during the retrieval period below.

How long you have

• Notice. You can give notice at any time. The notice period is never more than two months, and you pick any earlier date. Fees stop at the end of it.
• Switching. If you tell us you are switching, we complete the switch within 30 days of the end of the notice period, and the service runs as normal in the meantime. If that is technically unfeasible in your specific case, we say so within 14 working days, explain why, and propose an alternative of at most seven months.
• Retrieval. Your data stays exportable for at least 30 days after the switch or after the notice period ends. After that we delete it, except where law requires us to keep it, and confirm the deletion on request.

What it costs

Nothing. There is no fee for giving notice, for switching, for exporting, or for the data leaving the platform. You pay your plan’s ordinary fees for the time you use the service, and then you stop paying.

Where your data is

Dibbla AB is a Swedish company. Your data is stored and processed on infrastructure in the European Union and is not moved outside the EU/EEA without the safeguards in the privacy policy.

Questions

[email protected]. Tell us which apps you are moving and when; if anything in the export is missing or in the wrong shape, we fix it before you need it.