ZipLoom
Home
PricingSign InGet Your Live URL

own

Self-Host Export

Download Your Dockerfile, Terraform, And .env Template Any Time. Leaving Takes An Afternoon.

Updated

At a glance

ZipLoom generates a Dockerfile, docker-compose.yml, Terraform, .env.template and a SQL file of your project’s records. Leaving takes an afternoon.

  • Standard Portable Formats
  • Your Data Goes With You
  • No Negotiation Required
Sample. Download a Dockerfile, docker-compose, Terraform, an .env template and a README any time. Secret values stay out; their names are listed so you know what to set.

Why it matters

Lock-in is usually discovered at the worst moment: when you want to leave, or when a procurement review asks what happens if the vendor goes away.

Every project page has an export button on every plan. The package holds a Dockerfile, a docker-compose file, a Terraform configuration, an environment template listing every variable your app needs, a SQL file of the project's records in ZipLoom (deployment history and configuration), and a README with deployment steps. Apps you deployed keep running on your own hosting accounts if you cancel. You lose the scanning, monitoring and self-healing, not the app. The export is a file you can open and inspect during the trial, before you commit to anything.

Everything You Need To LeaveIllustration · sample data
exportDockerfiledocker-compose.ymlterraform/.env.templatenames, no valuesdata.sqlproject recordsREADMEdeploy steps

What you get

Standard Portable Formats

The export package contains: a Dockerfile using the official Node.js base image, a docker-compose.yml with Postgres and the app, a Terraform configuration for AWS ECS or similar, and a .env.template documenting every required variable.

Your Data Goes With You

The export includes a plain-SQL file of your project’s records: the project, its deployment history, and its configuration. Environment variable values stay out of the file; their names are listed so you know what to set.

No Negotiation Required

The export is on every project page at any time, on any plan. You don't need to contact support, open a ticket, or give 30 days notice. It's a download button.

How To Export

  1. 1

    Open any project and find the Self-Host Export card.

  2. 2

    Click 'Download export package'.

  3. 3

    You receive a zip file containing: Dockerfile, docker-compose.yml, terraform/, .env.template, data/ziploom-data.sql, and a README with deployment instructions.

  4. 4

    Follow the README to deploy on your own infrastructure.

  5. 5

    Your app runs without any dependency on ZipLoom services.

What this check inspects

  • Your deploy configuration, in a form you can run without ZipLoom.

  • Environment variable structure (names and wiring, not the secret values in plaintext).

  • Build and runtime settings per service.

  • The platform configuration for wherever the app is currently deployed.

What it means when this fails

Lock-in is usually discovered at the worst moment — when you want to leave. Export exists so the answer to 'what happens if we stop paying' is 'we keep running', which is also the honest answer to a procurement question.

What it does not do

  • Secret values are not in the file. Their names are listed so you know what to set.

  • The data file holds the project's records in ZipLoom. It is not a copy of your app's own database.

Questions

What exactly do I get?
The configuration needed to build and deploy your app yourself, on the platforms you already use.
Do my deployed apps die if I cancel?
No. They're on your platform accounts and stay live. You lose the scanning, monitoring, and self-healing, not the app.
Is this a real export or a marketing line?
It's a file you can inspect before you commit to anything. Try it during the trial.

Related features