Skip to content
Fransys docs

Leaving Fransys

Fransys doesn't lock you in: your code stays in your repository, your databases run on standard engines, your infrastructure on standard Kubernetes.

Checked against the console on 23 Oct 2026

Your code stays put

Section titled “Your code stays put”

It stays in your GitHub or GitLab repository. Fransys builds and deploys it without changing it: the CI merge request adds its own files without touching yours. If you leave, remove them.

Your data is in standard formats

Section titled “Your data is in standard formats”

PostgreSQL, MariaDB and Redis are the engines you already know. To get your data out:

  1. turn on Allow remote access to the database;
  2. export with the usual tools (pg_dump, mysqldump, redis-cli --rdb);
  3. turn remote access off.

Your configuration can be read back

Section titled “Your configuration can be read back”

Services, images, ports, variables (except protected values), domains, links: everything is readable in the console, and by your agent (the get_project tool). The .env export gives each service’s variables. Enough to recreate everything elsewhere.

Standard Kubernetes

Section titled “Standard Kubernetes”

Your services run on a standard Kubernetes cluster, at a standard hosting provider, with standard Docker images. No proprietary format in your code or your images.

Change hosting provider without leaving

Section titled “Change hosting provider without leaving”

Create a cluster at another provider or in another region, then attach your projects to it (taking them offline first). Database data doesn’t follow: restore it from a backup. See Backups and restore.