# blitz.cloud compared with Vercel, Render, Railway, Fly.io and EU hosts URL: https://blitz.cloud/compare/ Updated: 2026-09-26 Free plan, Docker support and data location for blitz.cloud against Heroku, Render, Railway, Vercel, Fly.io and EU platforms, dated and sourced. blitz.cloud is a small European hosting platform with a free plan that doesn't expire, one managed database on that plan, and two ways to bring your own code: a public Docker image, or a GitHub repository that goes online on every push. The big US platforms offer far more: global regions, preview environments, private registries and years of production use. The EU platforms keep your data with a European company but mostly ask for a credit card or charge from the first app. Which one fits depends on whether you need those features today or care more about a free setup in the EU. ## All providers side by side | Provider | EU company, no US parent | EU-only compute possible | Free tier | Run a finished Docker image | Git push deploys | Managed database on the free tier | |---|---|---|---|---|---|---| | blitz.cloud | Yes (Germany) | Yes, one region today | Doesn't expire, no card. Apps sleep after 30 minutes without visitors | Yes, public images from Docker Hub, ghcr.io, Quay and other registries, amd64 | Yes, after you connect GitHub | Yes, one (PostgreSQL, MariaDB or Redis) | | Vercel | No | Functions in EU regions, CDN is global | Hobby, non-commercial use only | Not documented, only a `Dockerfile.vercel` it builds | Yes | No own database, partners via Marketplace | | Netlify | No | Function region change is Pro and up | 300 credits a month, sites pause when used up | Not verified | Yes | Netlify Database uses credits | | Heroku | No | "eu" region without a named city; Dublin, Frankfurt, London with Private Spaces | None, Eco from $5 a month, card required | Via Heroku's own registry | Yes | No, Postgres from $5 a month | | Render | No | Frankfurt | No, services sleep after 15 minutes, free Postgres expires after 30 days | Yes | Yes | Yes, but it expires | | Railway | No | Amsterdam, region choice not on Free | $1 a month Free plan after a one-time trial | Yes | Yes | Allowed on the trial | | Fly.io | No | Yes, several EU regions | No free tier, trial only | Yes | No built-in, GitHub Actions | Not verified | | DigitalOcean App Platform | No | Amsterdam, Frankfurt | Static sites only, payment method required | Yes | Yes | No | | Cloudflare | No | Containers can be pinned to the EU; Workers EU-only is Enterprise | Workers Free and Pages, containers need a paid plan | Paid plan only | Yes | D1 (SQLite), no managed Postgres or MySQL found | | Scaleway Serverless Containers | Yes (France) | Yes, all regions are in the EU | Free allowance, credit card required | Yes, public images | No built-in | No | | Clever Cloud | Yes (France) | Yes | Sign-up credits, no permanent free app | Via git push with a Dockerfile | Yes | Free DEV databases without backups | | Koyeb | Yes (France, owned by Mistral AI) | Frankfurt, Paris | Removed for new sign-ups | Yes | Yes | No for new sign-ups | | Northflank | UK company, no US parent | Frankfurt, Netherlands, Zurich | Developer Sandbox, card required | Yes | Yes | Yes, one | ## What an app that stays awake with a database costs The price question most people bring: one app that answers at any hour, with its own database, per month. Prices are as each provider lists them, on the date in the last column. | Provider | One always-on app with a database, a month | Checked | |---|---|---| | blitz.cloud | Pro, 7 EUR for your whole account: all your apps can stay awake, with up to 5 databases | Our price, VAT included | | Heroku | $12: Basic dyno $7 plus Essential-0 Postgres $5 | 25 September 2026 | | Render | $13: Starter instance $7 plus Postgres from $6 | 14 September 2026 | | DigitalOcean App Platform | $12: container $5 plus dev database $7 | 14 September 2026 | | Railway | Hobby $5 including $5 of usage; memory and CPU beyond that are billed by use | 14 September 2026 | | Fly.io | About $40: smallest machine about $2.02 plus managed Postgres from $38 | 14 September 2026 | On Heroku, Render and DigitalOcean each app and each database has its own memory, and a second app costs a second fee. On blitz.cloud Pro's 4 GB is shared by all your apps. The other providers in the table above bill differently or aren't built for this, so we don't put a number next to them. ## What blitz.cloud doesn't do yet Being honest about the gaps saves you a wasted afternoon. Today blitz.cloud has no preview deployments, no private images, no arm64 images and no SSH access to apps. Everything runs in one region, and you can't choose it. Custom domains need Pro, which costs 7 EUR a month. The full list is on [what's live](/whats-live/). ## How we compiled this Every competitor fact comes from the provider's own pricing page, documentation or terms, fetched on 14 September 2026. Each comparison page lists its sources. Where we couldn't confirm something from a primary source, the table says "not verified" instead of guessing. Plans change often, and Netlify, Railway, Fly.io and Koyeb all changed their free offers in 2025 or 2026. If something here is out of date, tell us at hallo@blitzworks.io and we'll fix it. --- # blitz.cloud docs URL: https://blitz.cloud/docs/ Updated: 2026-09-26 How to deploy Docker images, GitHub projects, one-click apps and managed databases on blitz.cloud, the European hosting platform run by BlitzWorks. blitz.cloud hosts apps under an address you own, like `photos.lena.blitz.cloud`. Today you can install one of the apps in the App Store, run any public Docker image from Docker Hub or another public registry, or build a project from GitHub. Any public project builds from its link. Connect GitHub and your own projects build too, private ones included, with a new version online on every push. Each app can have a managed database and gets HTTPS without you setting anything up. To follow an app once it runs, read [app status and logs](/docs/app-status-and-logs/): the Activity tab with earlier versions to put back, uptime and traffic, and the mails we send when something happens. New here? Start with [getting started](/docs/getting-started/). If you want to know whether something works yet, [what's live](/whats-live/) is the honest list. --- # blitz.cloud guides URL: https://blitz.cloud/guides/ Updated: 2026-09-26 Step-by-step guides to host Docker containers, Node.js and Python APIs, static sites and databases on blitz.cloud, with real files and commands. The docs explain what each part of blitz.cloud does. These guides go the other way round: they start from something you want to get online and walk through it with files and commands that have been run, not just written. Not sure it is even free? [Is there free Docker hosting in the EU?](/guides/free-docker-hosting-eu/) answers that in one paragraph. Wondering what an app actually costs? [n8n pricing in 2026](/guides/n8n-pricing/) compares n8n Cloud, self-hosting and blitz.cloud with our own numbers. The example code lives in a public repository, [blitzworks-io/blitz-cloud-examples](https://github.com/blitzworks-io/blitz-cloud-examples). Every image in it was built for amd64 and tested as user 1000 with all Linux capabilities dropped, which is how blitz.cloud runs apps. A word on scope before you pick one. For your own code the quickest route is usually GitHub: connect your GitHub account, pick a repository, private ones included, and every push to the branch goes online. A public repository also builds from a pasted link. See [deploy a GitHub project](/docs/deploy-from-github/). The guides below show the Docker image route, which works with any public registry and lets you test the image on your own machine before it goes online. --- # blitz.cloud pricing - free plan, Pro at 7 EUR and Power at 19 EUR a month URL: https://blitz.cloud/pricing/ Updated: 2026-10-14 See what's free and what Pro and Power add. No credit card for the free plan. Pro is 7 EUR a month per account, Power 19 EUR. Yearly saves two months. blitz.cloud has three plans. Free costs nothing and has no time limit: up to 5 apps, 512 MB of reserved memory, 10 GB of storage and one managed database, with no credit card. Pro costs 7 EUR a month including VAT, for your whole account rather than per app, or 70 EUR a year, which makes 2 months free. Power costs 19 EUR a month or 190 EUR a year and has everything in Pro with more room. You can try Pro free for 14 days; you add payment details only if you decide to keep it. A monthly plan can be cancelled any month. A yearly plan runs for its first year, and after that you can cancel it with one month's notice. [See the plans](#plans) ## Who Pro is for Most accounts on blitz.cloud use the free plan, and nothing pushes you off it. Pro is for three situations. If none of them is yours yet, stay on free. ### An app has to answer at any hour A free app sleeps after 30 minutes without visitors and wakes when a person opens it in a browser. For a blog or a password manager that's fine. For n8n it isn't: schedule triggers don't fire while it sleeps, and webhooks from other services don't wake it, so they get a "try again later" answer and never reach your workflow. On Pro you keep an app awake, so schedules run on time and every webhook is answered. You can try this free for 14 days; payment details are only needed if you keep it. ### You need a second database The free plan has one managed database. Say Nextcloud already uses it, and now you want n8n or a small API with a PostgreSQL database of its own. Pro has 5 databases, and each one is backed up every night and kept for 30 nights instead of 7. ### You want your own domain On the free plan every app has an address under yours, like `photos.lena.blitz.cloud`, with HTTPS. On Pro you can connect a domain you bought somewhere else, like `example.com`, to any app. HTTPS is set up for it as well. You can try this free for 14 days; payment details are only needed if you keep it. ### And when Pro gets tight Power has everything in Pro and more room: 8 GB of memory, 80 GB of storage, 10 databases and up to 100 apps. It is for accounts that run several busy apps, each with its own database, and have filled Pro's 4 GB. If you aren't sure, start with Pro. You can move up later. ### Or just one app If only one app needs to stay awake, carry its own domain or get more room, you don't have to move your whole account to Pro. You can make that one app a Pro app instead, for 2 EUR a month or 15 EUR a year. It keeps that app awake, lets it carry a domain you own, lets search engines list it, and its memory and storage stop counting against your plan's room. The rest of your account stays as it is. Turn it on from the app's own page in the dashboard, or when a limit stops you from doing one of these three things. ## Everything in each plan Prices are per month for your whole account, VAT included. The rows start with what people run into first. | | Free | Pro, 7 EUR | Power, 19 EUR | |---|---|---|---| | Apps can stay awake at any hour | No, they sleep after 30 minutes without visitors | Yes | Yes | | Bots and workers that run in the background | 1 at a time, stops after 2 days without a sign-in | As many as you like | As many as you like | | Domains you own | No | As many as you like | As many as you like | | Google and other search engines can list your apps | No, free apps ask them not to | Yes | Yes | | Databases (PostgreSQL, MariaDB, Redis) | 1 | 5 | 10 | | Database backups kept | 7 nights | 30 nights | 30 nights | | Copies of your apps' files | No | 30 nights, [restore with undo](/docs/backups/) | 30 nights, [restore with undo](/docs/backups/) | | Ads in your dashboard | None at present | None | None | | "Made with blitz.cloud" link on your apps' pages | Yes, small, in a bottom corner | Off, you can turn it on | Off, you can turn it on | | Memory, shared by all apps | 512 MB | 4 GB | 8 GB | | Storage | 10 GB | 50 GB | 80 GB | | Apps | 5 | 50 | 100 | | Builds at once | 1 | 3, ahead of the queue | 3, ahead of the queue | | Builds from GitHub, private repositories, a new version on every push | Yes | Yes | Yes | | Pushes in quick succession build together, the newest commit at most every | 15 minutes | 5 minutes | 5 minutes | | Uptime checks, activity and "Put this version back" | Yes | Yes | Yes | | AI assistants over MCP | Yes | Yes | Yes | | Outgoing traffic speed per app | 50 Mbit/s | 200 Mbit/s | 200 Mbit/s | | [Private networks](/docs/private-networks/) | 1 | Up to 5 | Up to 10 | | Subdomains under your address | One per app | One per app | One per app | | Your own DNS records under your address | Up to 10 | Up to 10 | Up to 10 | | Automatic HTTPS | Yes | Yes | Yes | | Paid yearly | - | 70 EUR a year | 190 EUR a year | | Payment details needed | No | Yes, but not to start the 14-day trial | Yes | How memory and storage are counted, per app and per database, is on the [limits](/docs/limits/) page. Bots and background workers without an address never sleep, on any plan. On the free plan they stop after 2 days with no sign-in, no deploy and no visit to the dashboard. We email you one day before, and one click on Start runs them again. A database sleeps when every app linked to it sleeps or is paused, and starts again before the app does. A database without a linked app keeps running. ## What the same setup costs elsewhere Take two apps that each have their own PostgreSQL database and answer at any hour, like n8n and a small API. - On Heroku that is two Basic dynos at $7 a month each and two Essential-0 databases at $5 each: $24 a month. - On Render it is two Starter instances at $7 a month each and two Postgres databases from $6 each: $26 a month. - On blitz.cloud both fit in Pro for 7 EUR a month, with three databases to spare. To be fair about the difference: a Heroku dyno or a Render instance has its own memory, while Pro's 4 GB is shared by all your apps. Both also run in more than one region, and blitz.cloud has one data centre in the EU and a much shorter track record. Prices are in US dollars as the two companies list them, from [heroku.com/pricing](https://www.heroku.com/pricing/) (checked 25 September 2026) and [render.com/pricing](https://render.com/pricing) (checked 14 September 2026). The full comparisons are on the [Heroku](/compare/heroku/) and [Render](/compare/render/) pages. ## Try Pro free for 14 days When you want to keep an app awake or connect a domain of your own, the dashboard offers Pro free for 14 days first, once per person. If you already had a trial on another account, there is no second one, but you can buy Pro straight away. Starting the trial doesn't need payment details. If you add them before the 14 days are up, Pro carries on as a monthly subscription, and on the day the trial ends the first month is charged at 7 EUR. We remind you by email three days before. If you don't add payment details, the trial just ends, your account goes back to the free plan, and nothing is charged. Whatever is over the free plan's limits keeps running for another 14 days before it is paused, and nothing is deleted. ## Your first month back if Pro isn't for you If you take Pro or Power and find it isn't what you needed, write to hallo@blitzworks.io within 30 days of your first payment and we refund that first month in full. You don't have to give a reason. This works once per account, and it comes on top of your legal right of withdrawal. ## Three setups, and what each one needs These are ordinary setups on blitz.cloud, described as the platform runs them. They aren't customer stories. ### n8n with webhooks n8n comes from the App Store with an HTTPS address, a webhook URL that already points at the right place and an encryption key. On the free plan it runs well for workflows you start by hand. Once other services send it webhooks, or a workflow runs on a schedule, it needs to stay awake, which is Pro. If you'd rather keep its workflows in PostgreSQL than on disk, that's a database of its own. The details are in the [n8n guide](/guides/self-host-n8n/). ### Nextcloud with its database Nextcloud comes from the App Store with a MariaDB database, set up and connected, and 5 GB for its files. On the free plan that is your one database, and the files Nextcloud keeps on disk aren't copied at night. Pro gives you room for four more databases and copies your apps' files every night, 30 nights back. ### A bot and its dashboard A bot for Discord or Telegram runs without an address, so it never sleeps, even on the free plan. There it only stops if you don't sign in for 2 days, and we email you one day before. Its dashboard is a second app from the same repository, with an address, and it sleeps when nobody looks at it. Both can use the free database. You need Pro once the dashboard should open without a wait, should live on your own domain, or the bot needs a second database. See [several services in one repository](/docs/deploy-from-github/#several-services-in-one-repository). ## Where your apps run Your apps, their databases and the nightly backups are in data centres in the European Union, on both plans. blitz.cloud is run by BlitzWorks UG, a German company, and is subject to the GDPR. If your business needs a data processing agreement, [download it as a PDF](https://dashboard.blitz.cloud/account/dpa?lang=en) once you are signed in. More on [data and GDPR](/eu-data/). ## Buying Pro or Power You buy Pro or Power in the dashboard under Settings, in the Plan and usage section, and choose there whether you pay monthly or yearly. Payment goes through Stripe. Businesses can enter their VAT ID at checkout, and it goes on the invoice. A business in another EU country is billed without VAT under the reverse-charge rule. Invoices, your card and your billing address are in the same place. ## Cancelling You can cancel any time, in Settings or on the [cancel page](/cancel/), which works without signing in. A monthly plan runs until the end of the month you have paid for and isn't renewed. A yearly plan runs until the end of its first year; after that it ends one month after you cancel, and the paid days after that are refunded pro rata by day. Until 31 March 2027 we can also cancel any plan with 14 days' notice and without giving a reason. You then get back the whole month or year you are in and have paid for. See the [terms](/terms/), section 6a. After that your account is on the free plan. If it uses more than the free plan includes, nothing changes for 14 days. Then the newest apps and databases over the limit are paused, your own domains stop pointing at your apps, and apps kept awake go back to sleeping when idle. Nothing is deleted, and taking Pro again starts them. The details are in the [terms](/terms/). As a consumer in the EU you also have a [right of withdrawal](/withdrawal/). ## Questions about pricing ### Is the free plan really free? Yes. There's no credit card on file and no usage bill, and the free plan has no end date. When you hit a limit, the action that would exceed it is refused with a sentence explaining which limit. Nothing is charged and nothing already running is stopped. ### Will I be moved to a paid plan automatically? Only if you add payment details before the trial ends. Starting the trial doesn't need them. If you add payment details and don't cancel before the 14 days are up, Pro carries on as a monthly subscription, and we remind you by email three days before the first charge. If you don't add payment details, the trial just ends, your account goes back to the free plan, and nothing is charged. The free plan never turns into a paid one by itself. ### Can I try Pro before paying? Yes, free for 14 days and once per person. The dashboard offers it when you want to keep an app awake or connect a domain of your own. Starting the trial doesn't need payment details. If you add them before the end, Pro carries on as a monthly subscription, and the first month is charged on the day the trial ends. If you don't add payment details, the trial just ends, your account goes back to the free plan, and nothing is charged. Anything over the free plan's limits keeps running for another 14 days before it is paused, and nothing is deleted. ### Is Pro per app or per account? Per account. One Pro subscription covers all your apps, up to 50, and they share 4 GB of memory. Heroku and Render charge per dyno or instance instead, so a second always-on app costs a second fee there. ### Pro or Power? Pro, unless you already know you need more. Power has the same features with more memory, storage, databases and apps, for 19 EUR a month. If Pro gets tight, you can move up later. ### Can I pay for just one app instead of the whole account? Yes. Make that app a Pro app instead, for 2 EUR a month or 15 EUR a year. It keeps that one app awake, lets it carry a domain you own, lets search engines list it, and takes its memory and storage out of your plan's room. You turn it on from the app's own page. The rest of your account, and its other apps, stay on the plan they're on. ### What happens to my apps if I stop paying for Pro? Your account goes back to the free plan at the end of the month you paid for, and for 14 days nothing changes. After that, whatever is over the free plan's limits is paused, not deleted: the newest apps and databases, your own domains and apps kept awake. Taking Pro again starts them. ### Can I get my money back? Yes, for the first month. Write to hallo@blitzworks.io within 30 days of your first payment and we refund it in full, once per account. Later months aren't refunded pro rata, but you can cancel a monthly plan any month. A yearly plan runs for its first year. After that it ends one month after you cancel, and we refund the paid days after that, pro rata by day. ### Am I locked in? Not by the things you run. Apps are ordinary Docker images and your databases are ordinary PostgreSQL, MariaDB or Redis, so they run anywhere else too. There's no export button for databases and files yet; until there is, write to hallo@blitzworks.io and we help you get your data out. ### Where is my data? In data centres in the European Union, with the database backups on separate storage, also in the EU. blitz.cloud is operated by BlitzWorks UG (haftungsbeschränkt) in Regensburg, Germany. The [data processing agreement as a PDF](https://dashboard.blitz.cloud/account/dpa?lang=en) is there to download once you are signed in, in the dashboard under Settings, Privacy. ### Do I need to be technical? Not for the App Store. You pick an app like Nextcloud, Vaultwarden or n8n, choose a name, and it installs itself with its database and HTTPS. Running your own Docker image or GitHub project helps if you know what a port and an environment variable are, and the docs explain both. ### Is there a yearly price? Yes. Pro is 70 EUR a year and Power 190 EUR a year, which is 2 months free compared with paying monthly. Yearly is the default; switch to monthly if you'd rather pay less up front. ### Does the price include VAT? Yes. Consumers pay 7 EUR a month for Pro and 19 EUR for Power. Businesses with a VAT ID from another EU country pay the net amount and account for VAT themselves. ### Do you charge for bandwidth? No. There's no bandwidth meter and no traffic bill. Outgoing traffic is limited in speed instead, to 50 Mbit/s per app on the free plan and 200 Mbit/s on Pro and Power. ### Is there a discount for students or open-source projects? Not at the moment. You can earn Pro months by inviting people, though: when somebody who signed up through your link has had an app online for a week, you both get a month of Pro, up to six times a year. Your link is in Settings under Invite people. --- # blitz.cloud vs Heroku: a Heroku alternative in the EU with a free plan URL: https://blitz.cloud/compare/heroku/ Updated: 2026-09-26 Heroku against blitz.cloud on free plans, sleeping dynos, EU regions, Docker images and Postgres prices, with sources checked 25 September 2026. Heroku is the better choice when your team already runs on it, deploys with `git push` and uses its add-on marketplace. blitz.cloud fits when you want a free plan in the EU without a credit card, or a small app with a database for less than Heroku's cheapest dyno and database together. Heroku has had no free plan since 2022: the cheapest option is Eco at $5 a month, and Eco web dynos sleep after 30 minutes without traffic. In February 2026 Heroku said it is moving to a "sustaining engineering model focused on stability, security, reliability, and support" and no longer offers Enterprise contracts to new customers. Customers who pay by card keep the same pricing and service, according to the same announcement. If that news is why you're looking around, the table below is what matters day to day. ## At a glance | | blitz.cloud | Heroku | |---|---|---| | Company | BlitzWorks UG, Regensburg, Germany. No US parent | Heroku, part of Salesforce, San Francisco, US | | EU regions | One region in the EU today, more planned | Common Runtime region "eu" (no city named). Dublin, Frankfurt and London only with Private Spaces | | Free plan | 5 apps, 512 MB memory, 10 GB storage, one database. Apps sleep after 30 minutes without visitors and wake on the next one. No expiry, no card | None | | Cheapest paid plan | Pro, 7 EUR a month including VAT | Eco, $5 a month for 1,000 dyno hours shared by all Eco dynos. Web dynos sleep after 30 minutes without traffic | | An app that stays awake, with a database | Pro, 7 EUR a month for your whole account, up to 5 databases | $12 a month: Basic dyno $7 plus Essential-0 Postgres $5 (checked 25 September 2026) | | An app that stays awake | Pro, 7 EUR a month, for all your apps | Basic dyno, $7 a month per dyno (0.5 GB) | | Postgres | One database on the free plan, five on Pro, backed up every night | Essential-0 from $5 a month (1 GB) | | Credit card to start | No | Yes, account verification is needed to create apps | | Run a finished Docker image | Yes, public Docker Hub images, amd64 | Yes, after you push it to Heroku's own registry | | Git push deploys | Yes, after you connect GitHub, private repositories included | Yes | | Custom domains | On Pro | Yes | ## Where Heroku is the better choice Heroku deploys on every `git push`, has pipelines with review apps and a large add-on marketplace for logging, monitoring, queues and search. Its buildpacks turn many projects into a running app without a Dockerfile, and it has years of production use behind it. If your team depends on those workflows, staying is cheaper than rebuilding them. Heroku also offers US regions and, with Private Spaces, named locations in Dublin, Frankfurt and London. blitz.cloud has one data centre in the EU and a much shorter track record. ## Where blitz.cloud fits better - You want to try something without a card. Heroku needs one before you can create an app, blitz.cloud doesn't. - A side project with a database. On Heroku an Eco dyno plus the smallest Postgres is $10 a month. On blitz.cloud both are on the free plan, and Pro is 7 EUR a month if you need more. - Apps that answer without a cold start. An Eco web dyno sleeps after 30 minutes, and so does a free blitz.cloud app; on Pro all your apps stay awake for the same 7 EUR. - You want a European operator with the data in the EU, without paying for a Private Space to pick the location. ## Moving from Heroku to blitz.cloud 1. If your app has a Dockerfile, build the image for amd64, push it to a public registry such as Docker Hub or ghcr.io and deploy it from the dashboard. Heroku's container registry isn't needed any more. See [deploy a Docker image](/docs/deploy-docker-image/). 2. If Heroku builds your app with a buildpack, connect your GitHub account on blitz.cloud and pick the repository, private ones included. blitz.cloud reads the project, writes a Dockerfile if it has none, and puts every push to the branch online. A public repository also builds from a pasted link without connecting anything. See [deploy a GitHub project](/docs/deploy-from-github/). 3. Copy your config vars into the app's Environment tab. Your app should read its port from `PORT`, as it already does on Heroku. 4. Add a PostgreSQL database to the app, then move your data with `pg_dump` from Heroku and `pg_restore` into the new database. `DATABASE_URL` is set for you, the same name Heroku uses. See [databases](/docs/databases/). 5. On Pro, connect your own domain and point it at the new app. ## Sources - https://www.heroku.com/pricing/ - https://devcenter.heroku.com/articles/eco-dyno-hours - https://devcenter.heroku.com/articles/regions - https://devcenter.heroku.com/articles/account-verification - https://devcenter.heroku.com/articles/container-registry-and-runtime - https://www.heroku.com/blog/an-update-on-heroku/ Facts checked on 25 September 2026. Prices and plans change; tell us at hallo@blitzworks.io if something here is out of date. --- # blitz.cloud vs Vercel: EU hosting, free plan and Docker compared URL: https://blitz.cloud/compare/vercel/ Updated: 2026-10-08 Vercel against blitz.cloud on data location, free plan rules, Docker images, databases and git deploys, with sources checked on 8 October 2026. Vercel is the better choice for Next.js and frontend teams that want preview URLs for every branch and a global CDN. blitz.cloud fits people who want a free place in the EU that doesn't expire, for containers, self-hosted apps and a database, run by a company without a US parent. If your project is commercial and small, note that Vercel's free Hobby plan is for personal, non-commercial use only. ## At a glance | | blitz.cloud | Vercel | |---|---|---| | Company | BlitzWorks UG, Regensburg, Germany. No US parent | Vercel Inc., California, US | | EU regions | One region in the EU today, more planned | Functions in Stockholm, Paris, Dublin, Frankfurt (plus London). Default is Washington. CDN is always global | | Free tier | 5 apps, 512 MB memory, 10 GB storage, one database. Apps sleep after 30 minutes without visitors and wake on the next one. No expiry, no card | Hobby: personal, non-commercial use only. 4 CPU-hours, 1M function calls, 100 GB transfer. One function region | | Cheapest paid plan | Pro, 7 EUR a month including VAT | Pro, $20 per developer seat a month | | Run a finished Docker image | Yes, public Docker Hub images, amd64 | Not documented. What is documented: a `Dockerfile.vercel` is built on deploy and runs as a Function that scales down after 5 minutes without traffic | | Git push deploys | Yes, after you connect GitHub, private repositories included | Yes | | Managed databases | PostgreSQL 17, MariaDB 11.4, Redis (Valkey 8), with nightly backups | No own database apart from Blob storage. Postgres via Marketplace partners such as Neon and Supabase | | Custom domains and HTTPS on free | HTTPS on your blitz.cloud subdomains. Custom domains on Pro | Yes, 50 domains per project | ## Where Vercel is the better choice Vercel is built around Next.js, and it shows. Server components, ISR, image optimisation and middleware work without configuration, and new Next.js features land there first. Every pull request gets a preview URL, which is hard to give up once your team is used to it. The CDN is global. If your visitors are spread across continents, pages load faster from Vercel than from a single data centre in the EU. The platform is mature, well documented and runs very large sites, and paid plans come with the support and team features a company expects. None of that exists on blitz.cloud today. ## Where blitz.cloud fits better - You want your app and its data in the EU with a German operator, and don't want to configure regions to get there. - You run a container or a self-hosted app, not a frontend. Ghost, Vaultwarden, n8n or your own API in a Docker image run as long-lived processes, not functions. - You need a real database next to the app, included in the free plan, backed up every night. ## Moving from Vercel to blitz.cloud A Next.js app moves if it can run as a Docker image, for example with `output: "standalone"` or a static export. Put the Dockerfile in your repository, connect your GitHub account on blitz.cloud and pick the repository, and every push to the branch goes online. Without a Dockerfile, blitz.cloud writes one. You can also build the image yourself and deploy it from a public registry. Features tied to Vercel's platform, such as preview deployments and its image optimisation service, don't come along. The steps are in [migrate from Vercel to an EU host](/guides/migrate-from-vercel-to-eu/) and [deploy a GitHub project](/docs/deploy-from-github/). ## Sources - https://vercel.com/legal/terms - https://vercel.com/docs/regions - https://vercel.com/docs/functions/configuring-functions/region - https://vercel.com/docs/plans/hobby - https://vercel.com/docs/limits/fair-use-guidelines - https://vercel.com/pricing - https://vercel.com/docs/functions/container-images - https://vercel.com/docs/marketplace-storage - https://neon.com/docs/guides/vercel-postgres-transition-guide Facts checked on 8 October 2026. Prices and plans change; tell us at hallo@blitzworks.io if something here is out of date. --- # Getting started with blitz.cloud URL: https://blitz.cloud/docs/getting-started/ Updated: 2026-09-26 Create a free blitz.cloud account, claim your address, connect GitHub if you like, and put your first app, Docker image or project online. No credit card, no terminal needed. To get started, create a free account at [dashboard.blitz.cloud](https://dashboard.blitz.cloud/auth/login?register=1), confirm your email address, claim a name like `lena.blitz.cloud`, and click "Host something new". Your first app can be online a few minutes later. There is no credit card step and no waiting list. ## Create an account Sign up with an email address and a password of at least 10 characters, or with GitHub or Google. If you use email, we send a confirmation link. You can look around before you click it, but creating apps and databases only works once the address is confirmed. Throwaway mailbox providers are turned away at signup. That's one of the ways we keep a free platform usable for the people on it. ## Claim your address The first thing the dashboard asks for is your address. It becomes `.blitz.cloud`, and every app you host lives under it. - 3 to 30 characters: lowercase letters, digits and hyphens - no hyphen at the start or end, and no two hyphens in a row - some names are reserved (platform words, brand names and a few you can guess) The field checks availability while you type. You can rename the address later, but only once every 14 days. The details are in [addresses and HTTPS](/docs/addresses-and-https/). ## Connect GitHub, or skip it Next the onboarding offers to connect GitHub. If you keep code there, connect it: we can then build your projects, private ones included, and put a new version online every time you push. At GitHub you choose which repositories blitz.cloud may read. No code on GitHub? Click "Skip for now". You can connect later from Settings, and public projects build from a pasted link without connecting at all. More in [deploy a GitHub project](/docs/deploy-from-github/). ## Put your first app online Click "Host something new" in the dashboard. You get three choices: 1. A ready-made app from the [App Store](/docs/app-store/), such as Vaultwarden, Ghost or Uptime Kuma. 2. My own code: a [project from GitHub](/docs/deploy-from-github/), picked from your list once GitHub is connected, or any public repository by its link. 3. An app from Docker Hub: a public [Docker image](/docs/deploy-docker-image/) from Docker Hub or another public registry. Next you pick a short name for the app. It becomes a subdomain of your address, so `uptime` turns into `uptime.lena.blitz.cloud`. One app can also sit on your main address itself. Then click "Put it online" ("Build it and put it online" for your own code). The progress list reports what the cluster is actually doing, step by step. When it's done you get a working HTTPS link. ## What to read next - [Deploy a Docker image](/docs/deploy-docker-image/) if you have your own image - [Deploy a GitHub project](/docs/deploy-from-github/) if your code is on GitHub - [Databases](/docs/databases/) if your app needs PostgreSQL, MariaDB or Redis - [Limits](/docs/limits/) to see how many apps fit in the free plan - [App status and logs](/docs/app-status-and-logs/) if something doesn't come online --- # How to deploy a Docker container for free URL: https://blitz.cloud/guides/deploy-docker-container-free/ Updated: 2026-09-26 Run a public Docker image online for free with HTTPS and no credit card. Tested steps for blitz.cloud, the image requirements, and what the free plan covers. You can deploy a Docker container for free on blitz.cloud: create an account without a credit card, click Host something new, search Docker Hub for the image, pick a version and a name, and it runs under an HTTPS address like `whoami.yourname.blitz.cloud`. The free plan has no time limit. An app nobody visits for 30 minutes goes to sleep and wakes on the next visit. The catch is that the image has to be public on Docker Hub, built for amd64, and able to run without root. ## What you need - A blitz.cloud account. Sign up at [dashboard.blitz.cloud](https://dashboard.blitz.cloud/auth/login?register=1) with email, GitHub or Google, and confirm your email address. Until it is confirmed you can't create apps. - A public image. The wizard searches Docker Hub as you type. For ghcr.io, Quay or another public registry, type the full name, such as `ghcr.io/owner/image`. Private images need a login blitz.cloud doesn't have. ## Will my image run? Most failed first attempts come down to two things. You can check both on your own machine in a minute. Root is not one of them: an image that starts as root runs as root inside its own sandbox here. 1. Architecture. blitz.cloud runs on amd64 servers. Images built on an Apple Silicon Mac with a plain `docker build` are arm64-only and will not start. Build with `--platform linux/amd64`. 2. A declared port. Listen on something like 8080 and declare it with `EXPOSE 8080` in the Dockerfile, so blitz.cloud picks it up without you typing it. This command runs an image roughly the way blitz.cloud does: ```bash docker run --rm --platform linux/amd64 --security-opt no-new-privileges \ -p 8080:8080 yourname/your-image:1.0.0 ``` If `curl http://localhost:8080` answers, you are in good shape. ## Deploy the container 1. Sign in at [dashboard.blitz.cloud](https://dashboard.blitz.cloud/). The first time, you claim your address, for example `lena`. Your apps will live under `lena.blitz.cloud`. 2. Click Host something new and choose "An app from Docker Hub". 3. Type the image name into Which app? and pick it from the list. Official images are marked. A repository you pushed a few minutes ago can take a while to appear in Docker Hub's search. 4. Choose a Version. Tags like `latest` are marked "follows new releases"; a fixed tag like `1.0.0` never changes. Click Continue. 5. The next screen shows What this app needs: the port it will be reached on, whether it needs a database, and which folders survive a restart. blitz.cloud works these out by reading the image. If the port is wrong, you can change it under Advanced settings. 6. Give the app a Name and an address, then click Put it online. You watch it go through its steps, and when it is done you get a link like `https://whoami.lena.blitz.cloud`. The certificate for your address is issued automatically; until it is ready, a browser can briefly show a certificate warning on a brand new account. If nothing is ready yet, the app page says so in a sentence and shows the last lines the container printed. [App status and logs](/docs/app-status-and-logs/) explains each message. ## Try it with a ready-made example The [blitz-cloud-examples](https://github.com/blitzworks-io/blitz-cloud-examples) repository has three small apps that follow the rules above: a Node.js API, an Astro site behind nginx, and a FastAPI app. Build one, push it to your Docker Hub account, and deploy it with the steps above: ```bash git clone https://github.com/blitzworks-io/blitz-cloud-examples.git cd blitz-cloud-examples/python-api docker build --platform linux/amd64 -t yourname/blitz-example-python-api:1.0.0 -t yourname/blitz-example-python-api:latest . docker push --all-tags yourname/blitz-example-python-api ``` ## What the free plan includes | | Free plan | | --- | --- | | Apps | Up to 5 | | Memory | 512 MB shared across your apps and databases | | Storage | 10 GB | | Databases | 1 | | HTTPS | Automatic on every address | | Sleep when idle | After 30 minutes without visitors, wakes on the next visit | | Credit card | Not needed | A pasted image gets the small size: 128 MB of memory reserved and up to 512 MB when it needs more. That fits most APIs and small web apps. A JVM app with a big heap or anything that needs several GB of RAM is a bad fit for the free plan today. The full rules are on [Limits](/docs/limits/). ## Free Docker hosting compared Most platforms that run Docker images have dropped their free plans or turned them into trials. This is what each one gives you for nothing today, from the providers' own pricing pages and docs, checked on 25 September 2026. | | Free for how long | What sleeps, and when | Free database | Card to start | |---|---|---|---|---| | blitz.cloud | No time limit. 5 apps, 512 MB memory, 10 GB storage | Apps after 30 minutes without visitors, woken by the next visit | One, backed up nightly, doesn't expire | No | | Render | 750 instance hours a month, 512 MB per service | Web services after 15 minutes without traffic | Postgres, 1 GB, expires after 30 days | No | | Railway | $5 trial credit for 30 days, then a Free plan with $1 of usage a month | Only if you switch sleeping on | Paid from the usage credit | No | | Fly.io | Trial of 2 machine hours or 7 days | Trial machines stop after 5 minutes | No free database | No, adding one ends the trial | | Heroku | No free plan. Eco costs $5 a month | Eco web dynos after 30 minutes | No, Postgres from $5 a month | Yes | | Google Cloud Run | Monthly free allowance of CPU, memory and 2 million requests | Scales to zero between requests | No, Cloud SQL is paid | Yes, a billing account | The detailed comparisons are on [Render](/compare/render/), [Railway](/compare/railway/), [Fly.io](/compare/fly-io/) and [Heroku](/compare/heroku/). Sources: render.com/docs/free, railway.com/pricing, docs.fly.io/about/free-trial, heroku.com/pricing, cloud.google.com/run/pricing. ## When blitz.cloud is the wrong choice If you need servers outside Europe, GPU access, private images or arm64, pick something else for now. If you want a container online in the EU for nothing, it fits well. And if the code is yours and lives on GitHub, you can skip the image: connect GitHub, pick the repository, and blitz.cloud builds every push. See [deploy a GitHub project](/docs/deploy-from-github/). --- # blitz.cloud vs Render: free tier, sleeping services and EU hosting URL: https://blitz.cloud/compare/render/ Updated: 2026-10-08 Render against blitz.cloud on free tier sleep and expiry, Frankfurt region, Docker images, Postgres and git deploys, with sources checked 8 October 2026. Render is the better choice when you need private registries, custom domains on the free tier or a platform that grows into paid production services with a known track record. blitz.cloud fits when you want free apps that sleep after 30 minutes without visitors and a free database that doesn't expire, hosted by a German company. On Render's free tier, web services sleep after 15 minutes and the free Postgres database expires after 30 days. ## At a glance | | blitz.cloud | Render | |---|---|---| | Company | BlitzWorks UG, Regensburg, Germany. No US parent | Render Services, Inc., San Francisco, US | | EU regions | One region in the EU today, more planned | Frankfurt (others: Oregon, Ohio, Virginia, Singapore) | | Free tier | 5 apps, 512 MB memory, 10 GB storage, one database. Apps sleep after 30 minutes without visitors and wake on the next one. No expiry, no card | Web services sleep after 15 minutes without traffic, 750 hours a month. Free Postgres (1 GB) expires after 30 days plus 14 days' grace. Files are lost on redeploy. No card needed | | Cheapest paid plan | Pro, 7 EUR a month including VAT | Starter instance $7 a month, Postgres from $6 a month | | An app that stays awake, with a database | Pro, 7 EUR a month for your whole account, up to 5 databases | $13 a month: Starter instance $7 plus Postgres from $6 (checked 8 October 2026) | | Run a finished Docker image | Yes, public Docker Hub images, amd64 | Yes, public images from any registry, private ones from Docker Hub, GHCR, GitLab, Google Artifact Registry and ECR | | Git push deploys | Yes, after you connect GitHub, private repositories included | Yes | | Managed databases | PostgreSQL 17, MariaDB 11.4, Redis (Valkey 8), with nightly backups | Postgres and Key Value (Redis-compatible), both with limited free versions | | Custom domains and HTTPS on free | HTTPS on your blitz.cloud subdomains. Custom domains on Pro | Yes. Hobby includes 2 domains, then $0.25 each a month | ## Where Render is the better choice Render pulls images from private registries, so you don't need to make your image public. blitz.cloud only runs public images; private code reaches it through a connected GitHub account instead. Custom domains work on Render's free tier. Render also has more regions, including the US and Singapore, and paid instances that scale well beyond a hobby project. If you already know your app will grow into a paid production service, Render's paid plans are a proven path. blitz.cloud has one data centre and a much shorter track record. ## Where blitz.cloud fits better - Several apps that stay awake. Two apps with their own PostgreSQL cost $26 a month on Render and fit in Pro for 7 EUR. A Render instance has its own memory, while Pro's 4 GB is shared by all your apps. - Your app should answer the first request of the day without waiting. On Pro a blitz.cloud app can stay awake, and on the free plan it sleeps after 30 minutes without visitors. - You want a free database for a long-running personal project. Render's free Postgres expires, blitz.cloud's doesn't, and it's backed up every night. - Files your app writes should survive a restart. On Render's free tier they are lost on redeploy; on blitz.cloud, folders an app writes to stay. - You want a German operator and a single EU data centre, without choosing a region. ## Moving from Render to blitz.cloud If your Render service already runs from a Docker image, push that image to Docker Hub as a public repository and deploy it on blitz.cloud. Make sure it listens on a port such as 8080. If Render builds your code from git, add a Dockerfile first. See [deploy a Docker image](/docs/deploy-docker-image/) and [deploy a Node.js API](/guides/deploy-nodejs-api/). If Render builds your code from git, you don't need to add a Dockerfile yourself: connect your GitHub account on blitz.cloud and pick the repository. blitz.cloud uses your Dockerfile or writes one, and puts every push to the branch online. A public image can also come from ghcr.io, Quay or another public registry instead of Docker Hub. See [deploy a GitHub project](/docs/deploy-from-github/). ## Sources - https://render.com/terms - https://render.com/docs/regions - https://render.com/docs/free - https://render.com/pricing - https://render.com/docs/deploying-an-image Facts checked on 8 October 2026. Prices and plans change; tell us at hallo@blitzworks.io if something here is out of date. --- # Deploy a Docker image on blitz.cloud URL: https://blitz.cloud/docs/deploy-docker-image/ Updated: 2026-09-26 Run any public Docker image on blitz.cloud, from Docker Hub, ghcr.io or Quay, with HTTPS, environment variables and persistent storage built in. You can deploy any public Docker image that is built for amd64, from Docker Hub, GitHub's registry (`ghcr.io`), Quay or another public registry. In the dashboard, click "Host something new", choose "An app from Docker Hub", search for the image by name or type its full name, pick a tag and a subdomain, and blitz.cloud works out the port and runs the container with HTTPS in front of it. ## Requirements for the image | Requirement | Why | |---|---| | A public image | Docker Hub, ghcr.io, Quay and other public registries work. Private images, and images on private network addresses, can't be used. | | Built for `linux/amd64` | Our servers are x86. An arm64-only image will not start. | | Serves HTTP on one TCP port | Visitors reach that port through HTTPS on your address. | Root is fine. Every app runs in its own gVisor sandbox, so an image that starts as root, like the official `nginx`, runs as root inside that sandbox and nowhere else. An image that names a user runs as that user. The wizard tells you when an image runs as root. An app you deployed before 25 September 2026 keeps running as uid 1000 until it restarts. Restart it once from its page and it starts as its image expects. ## Step by step 1. Open [dashboard.blitz.cloud](https://dashboard.blitz.cloud/) and click "Host something new". 2. Choose "An app from Docker Hub" and type part of the name, for example `uptime-kuma` or `yourname/yourapp`. The wizard searches Docker Hub as you type, and official images are marked. For another registry, type the full name, such as `ghcr.io/yourname/yourapp`. 3. Pick a tag. The wizard lists the image's real tags and preselects the one that follows new releases, like `latest` or a major version. 4. Give the app a short name. That becomes the subdomain: `backend` turns into `backend..blitz.cloud`. 5. Check what blitz.cloud detected, then click "Put it online". A repository you pushed a few minutes ago may not show up in Docker Hub search right away. Docker Hub indexes new repositories with some delay. ## What blitz.cloud detects When you pick an image, we read what the image declares about itself: exposed ports, volumes and environment variable names. A language model then fills in what metadata can't tell, such as "WordPress wants MariaDB and reads `WORDPRESS_DB_HOST`". The image stays the authority on its own ports. If the model suggests a port the image doesn't expose, the image wins. The port is chosen in this order: 1. A port the image declares with `EXPOSE` 2. If it declares several: 80, 8080, 3000, 8000, 5000, otherwise the lowest 3. If it declares none, the model's suggestion 4. If nothing is known, 80 You can override the port, the database and the kept folders under "Advanced settings" in the wizard. It's closed by default because most images don't need it. ## Environment variables Set environment variables on the app's Environment tab. They are encrypted before they are stored, and each app can have up to 64. Changes apply the next time the app restarts, and the restart button is right next to that sentence. See [settings and files](/docs/settings-and-files/). ## Databases If the image needs a database, blitz.cloud can create one and inject the connection details as environment variables. Where the variable names are known, they are filled in for you and shown before anything is applied. If they aren't known, the app gets `DATABASE_URL`. See [databases](/docs/databases/). ## Persistent storage Folders the image declares as volumes, plus any the detection adds, survive restarts. An app from a pasted image can keep up to 6 folders and reserves 1 GB of your storage. On Pro these folders are copied every night. On the free plan only databases are. ## Health checks For a Docker image we check whether the port accepts connections before sending traffic to it. There's no automatic restart for pasted images, because restarting an app nobody has vetted can break something that was working. Apps from the App Store get a proper HTTP check and are restarted if they stop answering. ## Automatic updates With automatic updates switched on (the default for a moving tag such as `latest` or `alpine`), we look every night around 4:00 UTC at where the tag points. The first night only records it. From then on, when the tag has moved to a newer build, we put that exact version online, pinned by its digest, so what runs is what was checked. If the new version does not start within ten minutes, we put the version before back, say so on the Activity tab, and switch automatic updates off for that app until you turn them on again. While the new version starts, the app shows Updating and the version before keeps running. We send you a mail after each overnight update. You can switch that off under Settings > Notifications. The check works for images on Docker Hub, GitHub's registry (`ghcr.io`), Quay, lscr.io, GitLab, and the public registries of Amazon and Microsoft. The app's Settings tab says so when an image is somewhere else. ## Common problems - The app stays on "Starting": it is probably listening on a different port than the one chosen. Change it under Port on the app's Settings tab. - "This app wants to run as root": the app was set up before root was allowed. Restart it and it starts as root, inside its sandbox. - "Needs attention" with a crash loop: read the last log lines shown on the page. Missing environment variables and writes to read-protected folders are the usual causes. - "There is no room on blitz.cloud for this app right now": the cluster is full. We add servers when this happens, so try again later. More in [app status and logs](/docs/app-status-and-logs/). ## Can I deploy from GitHub instead? Yes. Paste the link of a public repository and we build the code and put it online. Connect your GitHub account and your private repositories work too, with a new version online on every push. See [deploy a GitHub project](/docs/deploy-from-github/). --- # Deploy a Node.js API without managing servers URL: https://blitz.cloud/guides/deploy-nodejs-api/ Updated: 2026-09-26 Package a Node.js API as a Docker image that runs without root on port 8080, push it to Docker Hub and host it on blitz.cloud with HTTPS, for free. To deploy a Node.js API without managing a server on blitz.cloud, you put it in a small Docker image that listens on port 8080 and runs as a normal user, push that image to Docker Hub, and pick it in the blitz.cloud dashboard. blitz.cloud runs it in its own sandbox under an HTTPS address and restarts it if the process dies. No VM, no nginx config, no certificates to renew. The code in this guide is the [node-api example](https://github.com/blitzworks-io/blitz-cloud-examples/tree/main/node-api). It uses Node's built-in `http` module so there is nothing to learn beyond Node itself. An Express or Fastify app works the same way. ## The server Two details make a Node app behave well on blitz.cloud. It reads its port from the environment with 8080 as the default, and it stops cleanly when it receives `SIGTERM`, which is how a container is asked to shut down during a restart. ```javascript import http from "node:http"; const port = Number(process.env.PORT ?? 8080); const server = http.createServer((req, res) => { if (req.url === "/healthz") { res.writeHead(200, { "content-type": "application/json" }); return res.end(JSON.stringify({ ok: true })); } res.writeHead(200, { "content-type": "application/json" }); res.end(JSON.stringify({ hello: "from blitz.cloud" })); }); server.listen(port, () => console.log(`listening on :${port}`)); process.on("SIGTERM", () => server.close(() => process.exit(0))); ``` The full version in the repository also talks to PostgreSQL when `DATABASE_URL` is set. That part is covered in [Deploy an app with a PostgreSQL database](/guides/deploy-app-with-postgres/). ## The Dockerfile ```dockerfile # Install dependencies in a throwaway stage so the final image has no npm cache. FROM node:22.23.2-alpine3.24 AS deps WORKDIR /app COPY package.json package-lock.json ./ RUN npm ci --omit=dev FROM node:22.23.2-alpine3.24 ENV NODE_ENV=production PORT=8080 WORKDIR /app COPY --from=deps /app/node_modules ./node_modules COPY package.json ./ COPY src ./src # The official Node image ships a "node" user with uid 1000, the same uid # blitz.cloud runs every app as. USER node EXPOSE 8080 CMD ["node", "src/server.js"] ``` `EXPOSE 8080` is not decoration here. blitz.cloud reads the ports an image declares and uses that one, so you don't have to type a port anywhere. Starting with `node` directly rather than `npm start` matters too: npm doesn't pass `SIGTERM` on reliably, so your shutdown handler would never run. ## Test it like blitz.cloud would run it ```bash docker build --platform linux/amd64 -t blitz-example-node-api . docker run --rm --user 1000:1000 --cap-drop ALL --security-opt no-new-privileges \ -p 8080:8080 blitz-example-node-api ``` ```bash curl http://localhost:8080/ # {"hello":"from blitz.cloud","database":"none"} ``` When we ran exactly this, `/` and `/healthz` answered `200`. If your own app fails at this step, it will fail on blitz.cloud too, and the error is easier to read on your laptop. ## Push to Docker Hub ```bash docker build --platform linux/amd64 -t yourname/blitz-example-node-api:1.0.0 -t yourname/blitz-example-node-api:latest . docker login docker push --all-tags yourname/blitz-example-node-api ``` The repository has to be public. Docker Hub is what the wizard searches; a public image on ghcr.io or Quay works too if you type its full name. Tag every build twice, with a version like `1.0.0` and with `latest`: the version tells you which build is which, and `latest` is what the Restart route further down relies on. If you'd rather not push from your laptop, the examples repository has a [GitHub Actions workflow](https://github.com/blitzworks-io/blitz-cloud-examples/blob/main/.github/workflows/docker-publish.yml) that builds for amd64 and pushes on every commit to `main`, once you add `DOCKERHUB_USERNAME` and `DOCKERHUB_TOKEN` as secrets in your fork. ## Deploy on blitz.cloud 1. In the [dashboard](https://dashboard.blitz.cloud/), click Host something new and choose "An app from Docker Hub". 2. Search for `yourname/blitz-example-node-api`, pick `latest` and click Continue (the section on shipping new versions below explains why). A repository you just pushed can take a while to show up in Docker Hub's search. 3. What this app needs should say port 8080, "the one the app itself declares". 4. Name it, give it an address such as `notes`, and click Put it online. Your API is then at `https://notes.yourname.blitz.cloud`. ## Configuration and secrets Settings go on the app's Environment tab. Values are stored encrypted, masked on screen, and reach the app the next time it restarts, so change a value, then restart. Up to 64 settings per app. ## Shipping a new version Deploy the `latest` tag and push a new `latest` when you release. Automatic updates are on by default for a tag that moves: every night around 4:00 UTC blitz.cloud checks where `latest` points and puts a newer build online. If the new version doesn't start within ten minutes, the one before comes back. To ship right away, press Restart on the app. A tag named `latest` is fetched again every time the app starts, so the restart picks up the new build. The tag won't tell you which build is running; the app's Activity tab lists each version that went live. If your code is on GitHub, you can skip Docker Hub altogether. Connect your GitHub account in blitz.cloud, pick the repository, private ones included, and the branch. Every push then builds the Dockerfile above and puts the new version online. See [deploy a GitHub project](/docs/deploy-from-github/). ## Is this a good fit? For a small JSON API, a webhook receiver or a Discord bot with an HTTP endpoint, yes. Each app gets 128 MB of memory reserved and up to 512 MB, and a share of a CPU. For a busy API that needs several cores, or for serverless functions that scale to zero and bill per request, it isn't what blitz.cloud does. --- # What's live on blitz.cloud - features available today and coming next URL: https://blitz.cloud/whats-live/ Updated: 2026-10-19 The current list of what works on blitz.cloud today, and the features still in development in the order they are being built. Updated with every release. Since 26 September 2026 blitz.cloud is out of beta. Today you can host 96 ready-made apps from the App Store, any public Docker image, and your own code from GitHub, public or private, with a new version online every time you push. Each app gets an address under your own name with HTTPS. Add PostgreSQL, MariaDB or Redis databases with nightly backups, watch uptime and traffic on each app's page, and go back to an earlier version with one click. Apps can also be private, reachable only from your own devices through Tailscale or WireGuard, and an AI assistant such as Claude or Cursor can manage all of it for you over MCP. Pro costs 7 EUR a month and adds domains you own, apps that stay awake, more room, and nightly copies of your apps' files. This page is updated with each release. If something here and somewhere else on the site disagree, this page is right. ## Live today | Feature | Since | Docs | |---|---|---| | Open signup with email, GitHub or Google | 12 September 2026 | [Account security](/docs/account-security/) | | Passkeys, two-step verification, session management | 12 September 2026 | [Account security](/docs/account-security/) | | Your own address `.blitz.cloud` | 12 September 2026 | [Addresses and HTTPS](/docs/addresses-and-https/) | | Deploy public Docker images from Docker Hub, ghcr.io, Quay and other public registries | 12 September 2026 | [Deploy a Docker image](/docs/deploy-docker-image/) | | A subdomain per app with automatic HTTPS | 12 September 2026 | [Addresses and HTTPS](/docs/addresses-and-https/) | | Live logs, restart, pause, resume, delete | 12 September 2026 | [App status and logs](/docs/app-status-and-logs/) | | Every app sandboxed with gVisor | 12 September 2026 | [Data and GDPR](/eu-data/) | | Encrypted environment variables | 13 September 2026 | [Settings and files](/docs/settings-and-files/) | | Files that survive restarts | 13 September 2026 | [Settings and files](/docs/settings-and-files/) | | Managed PostgreSQL 17, MariaDB 11.4, Redis (Valkey 8) | 13 September 2026 | [Databases](/docs/databases/) | | Nightly off-site database backups with one-click restore, and an undo for the restore | 13 September 2026 | [Backups](/docs/backups/) | | Cookieless visitor statistics on blitz.cloud itself | 14 September 2026 | [Data and GDPR](/eu-data/) | | Build any public GitHub project from a link, with or without a Dockerfile | 14 September 2026 | [Deploy a GitHub project](/docs/deploy-from-github/) | | Connect your GitHub account: private repositories, a repository picker, and a new version online on every push | 14 September 2026 | [Deploy a GitHub project](/docs/deploy-from-github/) | | A Dockerfile written for projects that have none, repaired when the build fails | 17 September 2026 | [Deploy a GitHub project](/docs/deploy-from-github/) | | Automatic overnight updates with rollback if the new version does not start | 17 September 2026 | [Deploy a Docker image](/docs/deploy-docker-image/) | | Free apps sleep after 30 minutes without visitors, apps on Pro after two hours unless you keep them awake, and the first visit wakes them in about ten seconds | 17 September 2026 | [Limits](/docs/limits/#sleeping-apps) | | An app that keeps crashing is stopped after 15 restarts, and the page says why | 17 September 2026 | [App status and logs](/docs/app-status-and-logs/) | | Choose which Dockerfile an app is built with, and give it a start command | 18 September 2026 | [Several services in one repository](/docs/deploy-from-github/#several-services-in-one-repository) | | Bots and background workers without an address, which never sleep (on the free plan they stop after 2 idle days) | 18 September 2026 | [Bots and background workers](/docs/deploy-from-github/#bots-and-background-workers) | | Your own DNS records (A, AAAA, CNAME, TXT, MX) under your address | 18 September 2026 | [Advanced DNS records](/docs/addresses-and-https/#advanced-dns-records) | | After a rename, the old address sends visitors to the new one for 14 days | 18 September 2026 | [Renaming your main address](/docs/addresses-and-https/#renaming-your-main-address) | | The Activity tab: everything that happened to an app, and "Put this version back" for the last 10 versions | 18 September 2026 | [App status and logs](/docs/app-status-and-logs/) | | A failed build or start says what went wrong in one sentence and lists the steps that fix it | 19 September 2026 | [Deploy a GitHub project](/docs/deploy-from-github/) | | A project of several services (a web front end, an API, a worker) runs as one app with one address | 19 September 2026 | [Deploy a GitHub project](/docs/deploy-from-github/) | | Delete your account, change your sign-in email and download your data, all from Settings | 19 September 2026 | [Account security](/docs/account-security/) | | The Pro plan at 7 EUR per month: domains you own, apps kept awake, more room | 25 September 2026 | [Pricing](/pricing/) | | An MCP server for AI assistants, which sign in with your blitz.cloud account or use an API key | 25 September 2026 | [Connect an AI assistant](/docs/ai-assistants/) | | Private apps, reachable only from your own devices through Tailscale or WireGuard, at their usual address | 25 September 2026 | [Private apps](/docs/private-networks/) | | Connect a phone or laptop to your private apps with the WireGuard app, without a router or server of your own | 10 October 2026 | [Private apps](/docs/private-networks/) | | App Store with 42 open-source apps, and "Needs Pro" shown before you install | 25 September 2026 | [App Store](/docs/app-store/) | | Images that expect root run as root inside their own sandbox, and every App Store app runs here | 26 September 2026 | [App Store](/docs/app-store/) | | Immich on Pro, with up to 2 GB of memory | 26 September 2026 | [App Store](/docs/app-store/) | | Emails when a deploy fails or succeeds, an app is stopped or a restore is done, each switchable in Settings | 25 September 2026 | [App status and logs](/docs/app-status-and-logs/) | | Uptime, requests and data served this week on each app's Overview | 25 September 2026 | [App status and logs](/docs/app-status-and-logs/) | | Everything you, your AI assistant, GitHub and we changed on your account, listed in Settings | 25 September 2026 | [Account security](/docs/account-security/) | | Build one folder of a repository, for monorepos | 25 September 2026 | [Deploy a GitHub project](/docs/deploy-from-github/) | | An app's own error pages reach its visitors; our page only shows when the app is asleep, paused, starting or building | 25 September 2026 | [App status and logs](/docs/app-status-and-logs/) | | 12 more store apps, among them WordPress, Open WebUI, OmniRoute and LibreTranslate, and the category AI & chat | 26 September 2026 | [App Store](/docs/app-store/) | | On Pro, nightly copies of the files apps keep, 30 nights, restored from the app's Settings tab with an undo | 26 September 2026 | [Settings and files](/docs/settings-and-files/#backups) | | A public status page for the platform at [status.blitz.cloud](https://status.blitz.cloud/) | 26 September 2026 | [Status](https://status.blitz.cloud/) | | The `blitz` command: list, deploy, restart, pause and resume apps, read their logs and change their settings from a terminal | 27 September 2026 | [The blitz command](/docs/cli/) | | A push while a version is being built stops that build and builds the newer code instead | 28 September 2026 | [Deploy a GitHub project](/docs/deploy-from-github/) | | Pushes made by bots and GitHub workflows, and commits marked [skip ci], start no build unless you switch that on for the app | 29 September 2026 | [Deploy a GitHub project](/docs/deploy-from-github/#when-your-code-changes) | | The free plan holds 5 apps, 512 MB of memory, 10 GB of storage and one database, one of them running in the background | 30 September 2026 | [Pricing](/pricing/) | | Sign-up and sign-in link to the terms and the privacy policy | 30 September 2026 | [Terms](/terms/) | | The Logs tab shows open log windows and frees a place when one closes | 30 September 2026 | [App status and logs](/docs/app-status-and-logs/) | | An expired sign-in or verification link explains what to do next | 30 September 2026 | [Account security](/docs/account-security/) | | The dashboard speaks German and French, with a language switcher that remembers your choice | 1 October 2026 | [Account security](/docs/account-security/) | | Sign-in and sign-up fit a phone screen | 1 October 2026 | [Account security](/docs/account-security/) | | A small "Made with blitz.cloud" link on the pages of free apps (accounts from 2 October 2026; older ones after an email), off on Pro and Power unless switched on per app | 2 October 2026 | [Pricing](/pricing/) | | A domain you add belongs to your account and survives deleting the app it pointed at | 2 October 2026 | [Addresses and HTTPS](/docs/addresses-and-https/) | | Try Pro free for 14 days, once per person, no card needed to start; add one anytime to keep Pro, or do nothing and it just ends | 11 October 2026 | [Pricing](/pricing/) | | Run one read-only SQL query on PostgreSQL or MariaDB from the Data tab, and see tables and results in a proper grid with each column's type | 10 October 2026 | [Databases](/docs/databases/) | | Choose an app's memory and storage size inside your plan's room | 3 October 2026 | [Limits](/docs/limits/) | | 2 more App Store apps: FileBrowser Quantum and SillyTavern | 3 October 2026 | [App Store](/docs/app-store/) | | Make one app a Pro app on any plan: stays awake, can carry your own domain, counted outside your plan's room, for 2 EUR a month or 15 EUR a year | 4 October 2026 | [Pricing](/pricing/) | | Checkout opens in a dialog and offers every payment method you turned on in Stripe | 4 October 2026 | [Pricing](/pricing/) | | Build from any public git address - GitLab, Codeberg, your own server - with a Dockerfile at the root | 6 October 2026 | [Deploy a GitHub project](/docs/deploy-from-github/) | | A failed GitHub connection says why and what to do next | 5 October 2026 | [Deploy a GitHub project](/docs/deploy-from-github/) | | A prompt to pick up an unfinished Pro checkout | 5 October 2026 | [Pricing](/pricing/) | | Connect a GitLab, Codeberg, Gitea or Forgejo account: private repositories, and a push deploys the app automatically | 9 October 2026 | [Deploy a GitHub project](/docs/deploy-from-github/) | | Build minutes per month: 300 on the free plan, 2000 on Pro, no limit on Power. Builds that failed because of us don't count | 10 October 2026 | [Limits](/docs/limits/) | | Install page shows before the button if your plan is full or you already have the app, with the ways out: remove an app, make it a Pro app, or try Pro | 15 October 2026 | [App Store](/docs/app-store/) | | The public cancel form also ends your Pro apps, not only your plan | 15 October 2026 | [Cancel your contract](/cancel/) | | The free 14-day Pro trial is once per person, even from a new account | 15 October 2026 | [Pricing](/pricing/) | | Report illegal content on a dedicated page, and a mail that pauses an app or suspends an account says which rule it rests on | 15 October 2026 | [Report illegal content](/report/) | | Upload a PostgreSQL dump from your computer into an empty database | 16 October 2026 | [Databases](/docs/databases/#bring-your-data) | | Download a copy of a PostgreSQL, MariaDB or Redis database as one file | 16 October 2026 | [Databases](/docs/databases/#download-a-copy) | | Run one command inside an app from the blitz command or an AI assistant | 16 October 2026 | [The blitz command](/docs/cli/) | | Every App Store app shows its logo | 15 October 2026 | [App Store](/docs/app-store/) | | Seven App Store apps offer "Sign in with blitz.cloud" for their owner only | 16 October 2026 | [App Store](/docs/app-store/) | | Your AI assistant can move files into and out of an app's kept folders | 17 October 2026 | [Settings and files](/docs/settings-and-files/) | | Pricing, docs, guides, comparison and app pages also answer in plain Markdown, for AI assistants | 18 October 2026 | [AI assistants](/docs/ai-assistants/) | | Build an app from GitHub on your own GitHub Actions, with the workflow and our Dockerfile committed to your repository | 19 October 2026 | [Deploy a GitHub project](/docs/deploy-from-github/) | | Buy a domain for your account; we register it in your name and point it at your app | 19 October 2026 | [Addresses and HTTPS](/docs/addresses-and-https/) | | The App Store suggests apps that people who run your apps also run | 19 October 2026 | [App Store](/docs/app-store/) | | When you cancel your plan, you can keep your busiest app on Pro instead of losing it | 19 October 2026 | [Cancel your contract](/cancel/) | ## Known limits today - Docker images must be public and built for amd64. Private images aren't supported. - Overnight updates look at Docker Hub, GitHub's registry, Quay, lscr.io, GitLab, Amazon's and Microsoft's public registries. An image elsewhere is not checked. - One database per app, and only one on the free plan. Some App Store apps bring a small cache next to it, which doesn't count as a database. - On Pro, app files are copied every night too. On the free plan only databases are. - Redis restores are done by hand on request. - "Download my data" in Settings gives you one file with your apps, their settings, databases, domains and history. What your apps keep on disk and what is inside your databases is not in it. - A single request to an app can be up to 100 MB. Larger uploads are refused before they reach the app. - Outgoing traffic is limited to 50 Mbit/s per app on the free plan and 200 Mbit/s on Pro. There is no traffic meter and no traffic bill. - Apps can't be reached over SSH, so Forgejo is used over HTTPS. - Everything runs in one region in the EU, and you can't choose a region. More regions in Europe are planned. --- # blitz.cloud data location and GDPR - hosted in the EU URL: https://blitz.cloud/eu-data/ Updated: 2026-10-19 Where blitz.cloud stores your apps and data (data centres in the European Union), who operates it, which service providers are involved and how privacy is handled. blitz.cloud runs on servers in a data centre in the European Union and is operated by BlitzWorks UG (haftungsbeschränkt), a German company in Regensburg. Your apps, their files and their databases are stored there, and backups go to separate storage, also in the EU. Neither BlitzWorks nor the company that runs the data centre has a US parent. This page describes how the platform is set up. It isn't legal advice, and it doesn't replace the [privacy policy](/privacy/). ## Where your data is | Data | Where | |---|---| | Your apps, their files and databases | A data centre in the EU, run by a German infrastructure provider. One region today, more planned at other European locations. Files that no app has needed for two days are moved, encrypted, to separate storage with the same provider | | Nightly backups of databases, and on Pro of your apps' files | Storage in the EU, separate from the app servers, encrypted before they leave | | Your account, sign-in and sessions | Our own Keycloak server, same data centre | | Statistics about visits to blitz.cloud | Our own Matomo server at matomo.blitzworks.io, on the same infrastructure | | Built images of your GitHub projects | Our own registry. The images sit in the same provider's object storage in the EU, apart from the app servers. We keep the last ten versions that went live, so you can put one back | All servers are rented and operated by BlitzWorks. There is no US hyperscaler underneath. Requests on their way to these servers do pass through Cloudflare, see below. ## Service providers These are the companies involved, what each one is for and what it sees. GitHub, Tailscale and Google for sign-in only come in when you choose to use them, and then under their own terms. Google AdSense shows ads only on the articles of this website; its script also loads on the other pages and in the dashboard, for Google's consent dialog, and asks for no ads there. Neither runs in your apps. | Provider | What for | What they see | |---|---|---| | Our infrastructure provider, a German company | Servers, network, backup storage | Everything stored on the servers, as the infrastructure provider | | Cloudflare | Every request to blitz.cloud, the dashboard, sign-in, the API, the MCP server and your apps' blitz.cloud addresses passes through Cloudflare, which delivers it, protects against attacks, runs our DNS and issues the HTTPS certificates for these addresses. Domains you connect yourself don't go through Cloudflare. Cloudflare Turnstile in the sign-up form and the report form also checks whether a human is sending it | Your IP address, the address you requested, browser details and the content of the request | | Google Workspace | Sending our emails from `noreply@blitz.cloud`, such as the address confirmation link or a note that a deploy failed | Your email address and the email's content | | Anthropic | Working out what a Docker image needs, writing or repairing a Dockerfile, explaining why a build or start failed, and helping us answer messages, check for abuse and fix incidents | See the next section | | Let's Encrypt | HTTPS certificates for domains you connect and for private apps | The domain or address name, which appears in public certificate logs like every certificate does | | Stripe | Taking payment for Pro, only if you buy it or start the 14-day trial | Your name, email address, billing address, VAT ID if you give one, and payment details. Card details go straight to Stripe and never reach our servers | | Docker Hub and other public registries | Searching and downloading public images | Which public images are looked up and pulled, not who you are | | GitHub, Google | Only if you sign in with them, or connect GitHub to build your repositories | What you allow during sign-in, and for GitHub which repositories blitz.cloud may read | | Google AdSense | Ads on the articles of this website: docs, guides and comparisons. None in the dashboard at present, and none in your apps | Your IP address, the page requested and browser details. Advertising cookies only if you agree in the consent dialog | | Google consent dialog | The consent dialog on the website and in the dashboard | Your IP address, to tell whether the dialog applies in your country, and your choice | | Tailscale | Only if you connect it for private apps. Tailscale is your own provider | What it learns about every device on your tailnet: its name, addresses and connection times | Cloudflare, Google, Anthropic, Stripe, GitHub and Tailscale are US companies or part of one, Let's Encrypt is run by a US non-profit, and all of them may process data in the USA. ### What Anthropic receives For the build steps it never receives your account details, your email address or the values of your apps' settings. We use Anthropic's model Claude for some of these steps. What it does receive depends on the step: - When you pick a Docker image: the image's name and version, the ports and folders it declares, and the names of its environment variables. - When we write a Dockerfile for a project that has none, or repair it after a failed build: the repository's name and commit, the list of files, manifest files such as `package.json`, the start of the README and of the file the program starts in, and after a failure the Dockerfile used and the end of the build output. - When a build or start fails and we explain why: the same project details and the end of the output, plus the app's name and address, the names (not the values) of its settings and the names of your other apps. This also happens for projects that bring their own Dockerfile. - When a project has several Dockerfiles and we work out which one is the app: those Dockerfiles. For a private repository that means parts of code you have not published. When Claude helps us run the operation, it sees the data a given task needs, such as your message to us, your email address, your plan and the details of your apps. More on this in section 16 of the [privacy policy](/privacy/). Every HTTPS certificate is listed in public certificate logs, as everywhere on the internet. For blitz.cloud addresses that shows your main address name, like `lena.blitz.cloud`, and for a domain you connect, that domain. ## How the platform protects data - Every app runs in its own gVisor sandbox. It runs as root only inside that sandbox and only when its image asks for it, and privileged containers are refused. - Network rules deny everything by default. Apps can't reach other accounts, the platform's internal services, or private networks. The one exception is a device on your own network that you forward to one of your apps in the infrastructure designer, and only that app reaches it. - Databases have no public address and are only reachable from the owner's apps. - Environment variables are encrypted before they're stored. - Backups are encrypted before they leave the cluster. - Sign-in supports passkeys and two-step verification. The admin console of the sign-in server is not reachable from the internet. - Outgoing traffic per app is limited in speed, and apps that mine crypto are paused before they run. - Settings lists every change to your account, including those made by your AI assistant, by GitHub and by us. ## Statistics and cookies on blitz.cloud We count visits to blitz.cloud and the dashboard with our own Matomo, without cookies, with a shortened IP address and without passing anything on. From our server it also counts, per account and under a random number, four steps from sign-up to a paid plan, without email address or name. One cookie, which recognises a returning visitor, is only set if you allow it in the consent dialog. The dashboard reports routes like `/apps/:id` rather than which app you opened. This website shows ads from Google AdSense on its articles only: the docs, the guides and the comparisons. The home page, pricing, the legal pages and contact have none, and the dashboard shows no ads at present. Google's own consent dialog asks for your consent. Without it, Google and its partners set no advertising cookies. Third-party vendors, including Google, use cookies to serve ads based on your earlier visits to this or other websites. [How Google uses data on its partners' sites](https://policies.google.com/technologies/partner-sites) is explained there, and you can turn personalised ads off in [Google's Ads Settings](https://adssettings.google.com). You can change your choice at any time under "Cookie settings" at the bottom of the website, or under Settings in the dashboard. There are no ads at sign-in or in your apps. Your hosted apps are not tracked by us. What your app does with its visitors' data is up to you. ## GDPR BlitzWorks is subject to the GDPR as a German company, and the data stays in the EU. When you host an app that processes other people's personal data, you are the controller and BlitzWorks processes it on your behalf. You can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) (Auftragsverarbeitungsvertrag, AVV) as a PDF once you are signed in. It includes the technical and organisational measures and the list of sub-processors. For any other question about data protection, write to hallo@blitzworks.io. ## Your rights You can ask what we store about you, have it corrected or deleted, and get a copy. You can delete your account and download your data yourself, under Settings. For anything else, write to hallo@blitzworks.io from the account's email address. Details are in the [privacy policy](/privacy/). --- # blitz.cloud vs Railway: free plan, EU region and Docker compared URL: https://blitz.cloud/compare/railway/ Updated: 2026-09-26 blitz.cloud vs Railway, compared 14 September 2026: free plan limits, EU region, Docker images, databases and custom domains, and where each fits better. Railway is the better choice when you want database templates including MySQL and MongoDB, regions in the US and Asia, and usage-based pricing that starts at $5 a month. blitz.cloud fits when you want a free plan with room for 5 apps, a managed database and hosting in the EU by a German company. Railway's Free plan gives $1 a month of usage, no custom domains and no choice of region. ## At a glance | | blitz.cloud | Railway | |---|---|---| | Company | BlitzWorks UG, Regensburg, Germany. No US parent | Railway Corporation, San Francisco, US | | EU regions | One region in the EU today, more planned | EU West, Amsterdam (others: California, Virginia, Singapore). Choosing a region is not available on the Free plan | | Free tier | 5 apps, 512 MB memory, 10 GB storage, one database. Apps sleep after 30 minutes without visitors and wake on the next one. No expiry, no card | One-time $5 trial for 30 days without a card, then a Free plan with $1 a month, 0.5 GB RAM and 1 vCPU per service, 0.5 GB volume | | Cheapest paid plan | Pro, 7 EUR a month including VAT | Hobby, $5 a month including $5 of usage | | An app that stays awake, with a database | Pro, 7 EUR a month for your whole account, up to 5 databases | Hobby, $5 a month including $5 of usage; memory and CPU beyond that are billed by use (checked 14 September 2026) | | Run a finished Docker image | Yes, public Docker Hub images, amd64 | Yes, from Docker Hub, GHCR, Quay and GitLab | | Git push deploys | Yes, after you connect GitHub, private repositories included | Yes | | Managed databases | PostgreSQL 17, MariaDB 11.4, Redis (Valkey 8), with nightly backups | Postgres, MySQL, Redis and MongoDB as templates | | Custom domains and HTTPS on free | HTTPS on your blitz.cloud subdomains. Custom domains on Pro | Custom domains: 1 during the trial, 0 on Free, 2 on Hobby | ## Where Railway is the better choice Railway's developer experience is its strength. Connect a repository, and services, databases and environment variables show up on one canvas that redeploys on push. blitz.cloud redeploys on push too once you connect GitHub, but Railway offers MongoDB and MySQL, which blitz.cloud doesn't. Usage-based billing also suits apps with uneven traffic, and the Hobby plan is cheap for what it includes. Railway has regions in the US and Asia too. If you need any of these today, Railway is the more complete product. ## Where blitz.cloud fits better - You want to stay on a free plan for months: 5 apps and 512 MB of memory shared between them, not $1 of usage. - You want your data in the EU. On Railway's Free plan you can't pick the Amsterdam region. - You want store apps like Ghost, Vaultwarden or n8n installed in a few clicks, each under its own subdomain with HTTPS. - Your project is a web front end, an API and a worker in one repository with a compose file. On blitz.cloud they run as one app with one address, and a push builds them together. - You prefer a German operator without a US parent. ## Moving from Railway to blitz.cloud Services that run from a Docker image move directly: make the image public on Docker Hub, check it listens on a port such as 8080, and deploy it. For a Postgres database, create one on blitz.cloud and import a dump. Railway's MongoDB templates have no equivalent here. See [deploy a Docker image](/docs/deploy-docker-image/) and [deploy an app with PostgreSQL](/guides/deploy-app-with-postgres/). Services that Railway builds from a GitHub repository build here from the same repository once you connect GitHub. If there's no Dockerfile, blitz.cloud writes one. A public image can also come from ghcr.io, Quay or another public registry instead of Docker Hub. See [deploy a GitHub project](/docs/deploy-from-github/). ## Sources - https://railway.com/legal/terms - https://docs.railway.com/reference/regions - https://railway.com/pricing - https://docs.railway.com/reference/pricing/free-trial - https://docs.railway.com/reference/pricing/plans - https://docs.railway.com/services - https://docs.railway.com/databases Facts checked on 14 September 2026. Prices and plans change; tell us at hallo@blitzworks.io if something here is out of date. --- # Deploy a GitHub project on blitz.cloud URL: https://blitz.cloud/docs/deploy-from-github/ Updated: 2026-10-19 Connect GitHub or paste a link to a public repository, and blitz.cloud builds the code and puts it online with HTTPS, with a new version on every push. How the build works, which port is used and what fails. Connect your GitHub account and blitz.cloud builds your projects, private ones included, and puts a new version online every time you push. You can also skip connecting and paste a link to any public GitHub repository. It does not have to be your repository. We clone it, build it and run the result under your address with HTTPS. If the project has a Dockerfile we use it; if it does not, we write one from what is in the repo, and rewrite it if the build fails. ## Connect GitHub Click "Connect GitHub" during onboarding or on the Settings page. GitHub then asks which repositories blitz.cloud may read: all of them, or only the ones you pick. You can change that choice on GitHub at any time. Once it is connected: - "My own code" lists your projects with a search field. Private ones are marked Private. A project that is missing is one blitz.cloud may not read yet, and "Choose which projects on GitHub" takes you to the list at GitHub. - Every push to the app's branch is built and put online by itself. With or without a connection, you pick the branch from a list, in the wizard under "Advanced settings" and later on the app's Settings tab. ## Step by step 1. Open [dashboard.blitz.cloud](https://dashboard.blitz.cloud/) and click "Host something new". 2. Choose "My own code". 3. Pick one of your projects, or paste a link, for example `github.com/docker/welcome-to-docker`, and click Continue. 4. Give the app a short name. That becomes the subdomain: `demo` turns into `demo..blitz.cloud`. 5. Click "Build it and put it online" and watch it happen. The first build takes a few minutes, because everything the project needs is downloaded from scratch. Later builds of the same project reuse the layers that did not change. While it builds, the app's Overview shows each step as it happens, and your place in the queue if builds are waiting. Builds run on their own build servers. The free plan builds one project at a time, Pro builds three at once and goes ahead of the queue. ## How the build works | Your project has | What we do | |---|---| | A `Dockerfile` in the root, or in `docker/` | We build it | | Other Dockerfiles, such as `bot.Dockerfile` or `api/Dockerfile` | We look through the whole project and pick the one that is the app, or build the one you pick under "Advanced settings" | | No Dockerfile | We write one. A language model reads the file listing and the manifests (package.json, requirements.txt, go.mod and the like), writes a Dockerfile, and the build is what decides whether it was right | Both run in a sandbox with no access to anything of ours or anyone else's. A build can reach the internet to download dependencies, and nothing on the private network. A build gets the size the project needs: small (1 core, 2 GB, up to 4 cores), medium (2 cores, 5 GB, up to 6 cores) or large (4 cores, 10 GB, up to 7 cores). The memory of each size is fixed; the cores can grow when the build server has some to spare. The first build is sized by what kind of project it is. After that, every build measures how much memory it used, and the next one is sized from that. The build log says which size it got and why. When a written Dockerfile does not build, the model reads the end of the log and rewrites it, up to three times. The Dockerfile we wrote is shown under the log of every such build. Copy it into your project as `Dockerfile` if you want the build to be the same every time, and we use yours from then on. A recipe that worked is kept. The next commit builds with it, and we only write a new one when that build fails. The recipe is also remembered against that exact code, by commit and by content. If somebody else deploys the same public project at the same commit, or the same content under another name, their build starts from what we already worked out and nobody asks a model again. Plans from private repositories are never shared. Content of your repository is treated as data when we write a Dockerfile: a README that tries to give the model instructions is a README. The recipe is checked before it is built, and the build runs in the same sandbox as everything else. ## When a build fails When a build or the first start fails and our own retries are used up, the app page says what went wrong in one sentence and lists the steps that fix it, each with its own button. Paste a key (with a note on where to find it), set up a database, use another Dockerfile, or let us write one. What blitz.cloud can do safely, it does by itself and ticks off. It never makes up a key or an address that belongs to somebody else. Some problems are named exactly. When the code asks for `9O6A5180.jpg` and the repository has `9O6A5180.JPG`, the page says so, with the file and the line that asks. Windows and macOS ignore capital letters in file names, our servers do not. The full build log is on the app's Overview while it builds, and on the Activity tab afterwards. ## Which port your app listens on We tell your app to listen on `8080` through the `PORT` environment variable, which is what a Dockerfile we write uses. If your Dockerfile declares a different port with `EXPOSE`, we read that from the image after the first build and use it instead. Your app runs as the user your Dockerfile names. Without a `USER` line that is root, inside the app's own gVisor sandbox, so an image that expects root works as it would on your machine. ## When your code changes With GitHub connected, every push to the app's branch builds a new version and puts it online. Without it, click "Get the newest code" on the app's Settings tab. It builds whatever is newest on the branch and puts it online. Either way, the version currently running stays up until the new one works, so a build that fails changes nothing. If you push again while a version is being built, that build stops and the newest code is built instead. The version that is online keeps running until the new one is ready. If the new version builds but does not start within ten minutes, we put the version before back and say so on the Activity tab. Any of the last 10 versions that went live can be put back from there with "Put this version back". Pushes that come in quickly are built together as one build of the newest commit. On the free plan a push waits until 3 minutes go by without another one, and an app is built from pushes at most every 15 minutes. On Pro, at most every five minutes. A push whose commits all come from a bot or a GitHub workflow builds nothing, and neither does a commit whose message says [skip ci] or [skip blitz]. If one of your workflows is meant to put new versions online, switch on "Build pushes made by bots and workflows" on the app's Settings tab. An app that gets more than 12 pushes in an hour is built from pushes at most every 30 minutes until an hour goes by with fewer. "Get the newest code" always builds at once. With automatic updates switched on (the default), we also look every night around 4:00 UTC whether the branch has moved, and build and put the newest commit online if it has. ## Build on your own GitHub Actions Builds normally run on blitz.cloud's build servers, one at a time per account on the free plan. You can also let GitHub build the app with your own Actions minutes: switch on "Build on your own GitHub Actions" on the app's Settings tab, or tick "Also build my new apps on my own GitHub Actions" when you connect GitHub. The same switch shows up under a build that is waiting for a build server. Switching it on adds one file to the repository, `.github/workflows/blitz-cloud.yml`, in a commit by blitz-cloud-app on the branch the app follows. If we wrote the project's Dockerfile, we add that too once it has put the app online, so you can read and change it with the rest of your code. When the app needs a new version, blitz.cloud starts the workflow. It asks GitHub for a signed token, gets the build from us with a credential for this app's images only, builds the image on GitHub's machine and stores it on blitz.cloud. From there it goes online exactly like a build of ours, with the same checks and the same way back if it does not start. The build log is on the app's Overview, with a link to the run on GitHub. Builds on GitHub Actions don't count toward your blitz.cloud build minutes. Public repositories build on GitHub Actions for free; a private one uses your GitHub minutes, and GitHub's free plan includes 2,000 a month. If GitHub does not start the build within ten minutes, we build it on our own servers instead and say why in the log. This needs our GitHub App to be allowed to write to the repository and to start workflows. An older connection may only allow reading. Then GitHub asks the owner to accept the new permissions first, and the switch links to that page. To go back, switch it off. The workflow file stays in your repository and does nothing until blitz.cloud starts it, so delete it whenever you like. ## Private repositories Connect GitHub and allow blitz.cloud to read the repository there. It then shows up under "My own code", marked Private, and builds like any other project. We only see the repositories you allowed. To write or repair a Dockerfile, the language model reads parts of the project, and for a private repository that means parts of code you have not published. What it reads is listed on [Data and GDPR](/eu-data/). ## A public address that isn't GitHub Paste any public `https://` git address instead of connecting an account: GitLab, Codeberg, a self-hosted Gitea or git server, anything that answers plain git-over-HTTPS. Pick "My own code" and paste the address where you would paste a GitHub link. This works like a public GitHub link, but with two limits. The project needs a `Dockerfile` in its root. We don't write one for it and we don't look in subfolders. There is also no connected account, so nothing builds automatically when the code changes. Click "Build again" on the app's page, and we read the branch you picked again from the same address and build its newest commit. ## Environment variables and databases Set environment variables on the app's Environment tab after the first deploy. They are encrypted before they are stored and applied on the next restart. See [settings and files](/docs/settings-and-files/). A managed database is created from the Databases page and connected to the app there. When a build begins, we also look in the project for a database driver and the setting the code reads its address from. If the project cannot start without a database, we set one up, connect it before the app starts and say so in the build log. That happens once per app, never over a setting you made and never past your plan. See [databases](/docs/databases/). ## Common problems - **"This project has no Dockerfile, and we could not write one for it right now"**: the model was unavailable or the account's AI allowance for the day is used up. Adding a Dockerfile to the repository is the reliable fix, and works without any model. - **"We couldn't build this project" followed by a reason**: the written Dockerfile was rewritten up to three times and still failed, and the sentence says what the model saw. The full log is underneath. - **The build fails while installing dependencies**: the log below the failure has what the installer said. A lockfile that does not match the manifest is the usual cause. - **The build ran out of memory**: it is built again once with the next bigger builder. A large build that still runs out says it needs more memory than a build can have. Get in touch and we will look at it. - **The app is "Starting" and never answers**: it is listening somewhere other than the port we are sending traffic to. Make it read `PORT`, or add `EXPOSE` to the Dockerfile and deploy again. - **"Part of this project is built for a different kind of processor"**: our servers are x86. A base image that only exists for arm64 will not run. ## Several services in one repository A web front end, an API and a worker that share one repository go online as one app with one address. If the project has a compose file, the wizard reads it and proposes the parts it found: the front end at `/`, the API on its own path such as `/api`, the worker in the background. Databases and development tools in the compose file are left out, each with a reason. You can still put only one of the services online instead. - Parts find each other by name. A setting like `BACKEND_SERVICE` is filled in with that part's address inside your account, the way it worked in compose. - A part can have a Dockerfile of its own. All parts are built in one build, update together and go back together. - A step can run before each new version, like a database migration. If it fails, the version you had keeps running and the Activity tab shows what the step printed. - Each part that keeps running counts as one of your plan's apps. The step before each new version does not, and neither does a part you switched off. - Only the parts people visit go to sleep. A bot keeps running while its dashboard sleeps. The app's Settings tab has a Parts section for start commands, paths and switching a part off. The Logs tab switches between parts. For an app of one part, you choose two things under "Advanced settings" in the wizard, and later on the app's Settings tab: - **Dockerfile**: any Dockerfile we find on the branch (`Dockerfile`, `Dockerfile.bot`, `api.Dockerfile`, `Containerfile`, in any folder), or "Write one for me" to have us write one even though the project has its own. Every app can use a different one. - **Start command**: replaces the image's `CMD` and keeps its `ENTRYPOINT`, the same as `docker run image `. With `ENTRYPOINT ["/bin/sh", "/app/entrypoint.sh"]`, a start command of `bot` runs `/bin/sh /app/entrypoint.sh bot`. For more than one step, write `sh -c "npm run migrate && npm start"`. The settings show what the Dockerfile starts with and what your command turns it into. A different Dockerfile builds the app again, and the running version stays online until the new one works. A different start command restarts the app. You often don't have to type the start command. If the project's ENTRYPOINT is a script with a `case "$1" in` that lists what it accepts, or you put only one service of a compose file online, the wizard shows the services and asks which one the app is. If an app stops because nobody chose, its page offers the services as buttons. When the project doesn't say, and the first start stops without a start command, our assistant reads the project and what the app printed, and either starts it with the one service it found or offers the ones it found. ## Bots and background workers A Discord bot, a queue consumer or a scheduler connects out and is never visited. Switch on "Runs in the background" when you name the app. It then gets no address and no port, we do not wait for it to answer on one, and it never goes to sleep. On the free plan it stops when nothing has happened in your account for 2 days: no sign-in, no deploy and no visit to the dashboard. We email you one day before. Press Start on the app's page and it runs again without a new build, for another 2 days. It counts as running once it has stayed up for 20 seconds, and if it keeps crashing the app page shows the last lines it printed, the same as for any other app. Its output is on the Logs tab. An app that is already online can be switched on its Settings tab with "Run it in the background", which frees its address. A background app gets an address back with "Give it one". ## Monorepos To build one folder of a repository, such as `apps/web`, name it under "Folder to build" in the wizard's advanced settings, or later under Settings > Where new versions come from. We build that folder as if it were the whole project. The wizard suggests folders that look like a project. Without a folder, the build starts from the top folder of the repository. --- # Host a static site (Astro, Hugo, Next.js) with its own subdomain URL: https://blitz.cloud/guides/host-static-site/ Updated: 2026-09-26 Build an Astro, Hugo, Vite or Next.js static export into a non-root nginx image on port 8080 and host it on blitz.cloud with HTTPS on your own subdomain. To host a static site on blitz.cloud, you build it into plain files, copy them into the unprivileged nginx image, push that image to Docker Hub, and deploy it. The site gets its own subdomain like `blog.yourname.blitz.cloud` with HTTPS. This works for any generator that outputs a folder of HTML: Astro, Hugo, Eleventy, a Vite app, or Next.js with `output: "export"`. Honest comparison first. Netlify, Cloudflare Pages and GitHub Pages build static sites from a Git repository and serve them from a global CDN, and for a plain website that is less work than this guide. blitz.cloud builds from a repository too once you connect GitHub, but it serves from one location, not a CDN. It is worth it if you want the site next to your other apps under one address, run by a German company on servers in the EU. ## The Dockerfile This is the [static-site example](https://github.com/blitzworks-io/blitz-cloud-examples/tree/main/static-site), an Astro site. Two stages: Node builds the site, nginx serves it. ```dockerfile # Build stage: turn the Astro project into plain files in dist/. FROM node:22.23.2-alpine3.24 AS build WORKDIR /app COPY package.json package-lock.json ./ RUN npm ci COPY . . RUN npm run build # Serve stage: nginx without root, listening on 8080. FROM nginxinc/nginx-unprivileged:1.30.4-alpine3.24 COPY nginx.conf /etc/nginx/conf.d/default.conf COPY --from=build /app/dist /usr/share/nginx/html # blitz.cloud runs every app as uid 1000. nginx-unprivileged keeps its pid # file and temp folders in /tmp, which any uid can write to. USER 1000 EXPOSE 8080 ``` The regular `nginx` image listens on port 80 and starts as root. That works on blitz.cloud too, inside the app's own sandbox. We still use `nginxinc/nginx-unprivileged`, the official variant without root, because it doesn't ask for rights it never uses. ## The nginx config ```nginx server { # The unprivileged nginx image listens on 8080 instead of 80, so it runs # without root. listen 8080; server_name _; root /usr/share/nginx/html; # Behind blitz.cloud's HTTPS proxy nginx only sees plain HTTP on 8080. # Relative redirects keep /about -> /about/ on the address the visitor used. absolute_redirect off; location / { try_files $uri $uri/ $uri.html =404; } # Astro puts fingerprinted assets in /_astro/, safe to cache for a year. location /_astro/ { expires 1y; add_header Cache-Control "public, immutable"; } error_page 404 /404.html; gzip on; gzip_types text/css application/javascript application/json image/svg+xml; } ``` `absolute_redirect off` is the line people miss. Without it, a visit to `/about` gets redirected to `http://blog.yourname.blitz.cloud:8080/about/`, because nginx builds the redirect from what it sees, and behind the HTTPS proxy it sees plain HTTP on port 8080. We hit this while testing the example. ## Other generators Only the build stage changes. Point the `COPY --from=build` line at the generator's output folder. | Generator | Build command | Output folder | | --- | --- | --- | | Astro | `npm run build` | `dist` | | Vite (React, Vue, Svelte) | `npm run build` | `dist` | | Next.js with `output: "export"` | `npm run build` | `out` | | Hugo | `hugo --minify` | `public` | For Next.js, a static export only covers pages that don't need a server. If your app uses server components that fetch per request, API routes or middleware, use the standalone setup from [Move an app from Vercel to an EU host](/guides/migrate-from-vercel-to-eu/) instead. For a single-page app with client-side routing, replace `=404` in `try_files` with `/index.html` so deep links load the app. ## Build, test and push ```bash docker build --platform linux/amd64 -t yourname/blitz-example-static-site:1.0.0 -t yourname/blitz-example-static-site:latest . docker run --rm --user 1000:1000 --cap-drop ALL --security-opt no-new-privileges \ -p 8080:8080 yourname/blitz-example-static-site:1.0.0 ``` In our run, `/` and `/about/` returned `200`, `/about` returned a `301` to `/about/`, and a missing page returned a real `404`. Then push: ```bash docker push --all-tags yourname/blitz-example-static-site ``` ## Put it online with your subdomain 1. In the [dashboard](https://dashboard.blitz.cloud/), click Host something new and choose "An app from Docker Hub". 2. Search for your image, pick the version, click Continue. 3. Give it an address. Type `blog` and the site is at `https://blog.yourname.blitz.cloud`. You can also put one app on your main address itself, `https://yourname.blitz.cloud`, which suits a personal homepage. 4. Click Put it online. You can also skip the push. Keep the Dockerfile and `nginx.conf` in your GitHub repository, connect your GitHub account, choose "My own code" and pick the repository. Every push to the branch then rebuilds the site and puts it online. The certificate covers your main address and every subdomain under it, and renews on its own. See [Addresses and HTTPS](/docs/addresses-and-https/). ## Can I use my own domain? Yes, on Pro. Connecting a domain you own, like `example.com`, is part of the Pro plan at 7 EUR per month. On the free plan the site lives under `yourname.blitz.cloud`. --- # About blitz.cloud and BlitzWorks URL: https://blitz.cloud/about/ Updated: 2026-09-26 blitz.cloud is an EU hosting platform for apps and databases, built by BlitzWorks UG in Germany. How it differs from Blitz.js, blitz.dev and StackBlitz. blitz.cloud is a hosting platform for apps, Docker images and databases, built and operated by BlitzWorks UG (haftungsbeschränkt), a software company in Regensburg, Germany. It went live with open signup in September 2026 and runs on servers BlitzWorks operates in a data centre in the EU. ## Why we built it Putting a small app online should not mean renting a server, learning Kubernetes or handing your data to a US cloud. We wanted a place where a person can claim an address, pick an app or an image, and have it running with HTTPS and a database a few minutes later, in the EU, without paying anything to start. The free plan is real: no trial expiry, no surprise credit card charge, no waiting list. Today that covers your own code from GitHub, public Docker images, an App Store of 96 open-source apps that run here, databases with nightly backups, and private apps that only open on your own devices. We'd also rather be plain about what isn't finished. The [what's live](/whats-live/) page says exactly what works today. ## The company | | | |---|---| | Company | BlitzWorks UG (haftungsbeschränkt) | | Address | Graßer Weg 73, 93053 Regensburg, Germany | | Register | Amtsgericht Regensburg, HRB 21609 | | Managing director | Simon Gloël | | Email | hallo@blitzworks.io | | Website | [blitzworks.io](https://blitzworks.io) | BlitzWorks also builds custom software for businesses. blitz.cloud is its own product. The full [imprint](/imprint/) is on blitz.cloud. ## How it runs Every app runs in its own gVisor sandbox isolated from other accounts. Databases are backed up every night, and on Pro your app files are backed up too. A GitHub-built app is back online within seconds of a push. The platform's own uptime is public at [status.blitz.cloud](https://status.blitz.cloud). An AI assistant such as Claude or Cursor can manage an account over MCP. Private apps are reachable only from your own devices via Tailscale or WireGuard, so you can keep internal tools out of the public internet. Signup is open and there is no waiting list. Some apps in the store show "Needs Pro" because they need features the free plan doesn't have, like keeping an app awake or using a custom domain. ## Not to be confused with Quite a few things share the name "Blitz". blitz.cloud is none of these, and isn't affiliated with any of them: - Blitz.js, the full-stack React framework built on Next.js, at blitzjs.com - blitz.dev, an unrelated developer service - StackBlitz and its Bolt products, the in-browser development environment and AI app builder - Blitz-Host, Blitz-Hosting and HostingBlitz, other hosting companies - Blitz, the load-testing service that shut down in 2018 If an answer mentions serverless functions, edge functions or preview deployments on blitz.cloud, it's describing something else. blitz.cloud runs containers and databases. Its paid plans are Pro at 7 EUR and Power at 19 EUR per month, each for a whole account. ## Contact Questions, bug reports and data requests go to hallo@blitzworks.io. --- # App Store - one-click open-source apps on blitz.cloud URL: https://blitz.cloud/docs/app-store/ Updated: 2026-10-19 The blitz.cloud App Store has 96 open-source apps. What they need in memory, space and databases, and how installing works. The blitz.cloud App Store has 96 open-source apps, and all of them run here. Pick one, give it a name, and it installs with the settings, storage and database it needs. Before you install, the store says how much memory and space the app takes, whether it uses your free database or brings a small cache, and whether it fits your plan. Every app has [a page of its own](/apps/) that says what it replaces and what it needs. We run every entry under the same rules a real install gets before we list it: in its own sandbox, inside the memory limit. Where an app can't do something here, its card says so. ## The apps The store sorts them into ten categories, named after what people want to do: Files & documents, Photos & media, Websites & blogs, Passwords & security, Money & home, Monitoring & automation, Notes & knowledge, Productivity, Developer tools and AI & chat. | App | What it is for | Memory | Storage it reserves | Database | Runs on blitz.cloud today | |---|---|---|---|---|---| | FileBrowser Quantum | Upload, download and sort the files your apps keep, from your browser | 128 MB | 1 GB | none | Yes | | Nextcloud | Your own Dropbox: files, calendar and contacts in one place | 128 MB | 5 GB | MariaDB | Yes | | Syncthing | Keep a folder in step across your computers and phone, with no cloud in between | 128 MB | 5 GB | none | Yes | | Paperless-ngx | Scan your paper mail once and find any letter in seconds | 256 MB | 5 GB | PostgreSQL and a cache | Yes | | OpenCloud | Your own Dropbox for files and folders, with desktop and phone apps that sync | 256 MB | 5 GB | none | Yes | | Stirling PDF | Merge, split, sign and shrink PDFs without uploading them to a stranger | 256 MB | 1 GB | none | Yes | | Immich | Back up every photo from your phone automatically, like Google Photos | 768 MB | 5 GB | PostgreSQL and a cache | Yes, on Pro | | Jellyfin | Your movies and music, streamed to any screen in the house | 128 MB | 5 GB | none | Yes | | Audiobookshelf | Audiobooks and podcasts on every phone, and it remembers where you stopped | 128 MB | 5 GB | none | Yes | | Ghost | A blog and newsletter, ready to write in | 128 MB | 2 GB | none | Yes | | Umami | See how many people visit your website, without cookies or banners | 128 MB | none | PostgreSQL | Yes | | Vaultwarden | A password manager the whole family can use, works with the Bitwarden apps | 128 MB | 1 GB | none | Yes | | Actual Budget | A budget app that shows where your money goes | 128 MB | 1 GB | none | Yes | | Mealie | Save recipes, plan the week's meals and build the shopping list | 128 MB | 1 GB | none | Yes | | Firefly III | Every account, bill and budget in one place, with reports | 128 MB | 1 GB | PostgreSQL | Yes | | Home Assistant | Control lights, heating and more, all local | 256 MB | 1 GB | none | Yes | | n8n | Connect your apps and automate chores without code | 256 MB | 1 GB | none | Yes | | Uptime Kuma | Get a ping when any of your sites goes down | 128 MB | 1 GB | none | Yes | | Linkding | A fast, private place for every link you meant to read later | 128 MB | 1 GB | none | Yes | | Memos | A quick place to write things down | 128 MB | 1 GB | none | Yes | | Joplin Server | Keeps your Joplin notes in sync across phone and computers | 128 MB | none | PostgreSQL | Yes | | Linkwarden | Save links with a full copy of each page, so they still open after the site is gone | 256 MB | 2 GB | PostgreSQL | Yes | | Wiki.js | A wiki for your team or club, with an editor and search | 128 MB | none | PostgreSQL | Yes | | Docmost | Shared pages and a wiki for your team, with an editor that feels like Notion | 256 MB | 2 GB | PostgreSQL and a cache | Yes | | SilverBullet | A notebook in your browser where pages link to each other, kept as plain text files | 128 MB | 1 GB | none | Yes | | FreshRSS | All your news feeds in one calm, ad-free reader | 128 MB | 1 GB | none | Yes | | Vikunja | To-do lists and projects as lists, boards or a calendar | 128 MB | 1 GB | none | Yes | | HedgeDoc | Write notes together in real time, in the browser | 128 MB | 1 GB | none | Yes | | Planka | Boards and cards for planning anything together, like Trello | 128 MB | 1 GB | PostgreSQL | Yes | | Forgejo | Your own place for Git repositories, issues and pull requests, like a small GitHub | 128 MB | 2 GB | none | Yes | | Wakapi | See how much time you spend coding, per project and language | 128 MB | 1 GB | none | Yes | | WordPress | Build a website or a blog, with thousands of free themes and plugins | 128 MB | 2 GB | MariaDB | Yes | | WAHA | A WhatsApp API you run yourself: connect a number, then send and receive messages over HTTP | 256 MB | 1 GB | none | Yes | | Evolution API | Send and receive WhatsApp messages from your own code | 128 MB | 1 GB | PostgreSQL and a cache | Yes | | Activepieces | Connect your apps and automate chores by clicking steps together | 256 MB | none | PostgreSQL and a cache | Yes | | NocoBase | Build your own internal tools and databases by clicking | 256 MB | 1 GB | PostgreSQL | Yes | | Open WebUI | A chat page like ChatGPT for the AI models you choose | 256 MB | 2 GB | none | Yes | | OmniRoute | One address for all your AI providers, which switches to another one when a provider fails | 256 MB | 1 GB | none | Yes | | 9router | Send your AI coding tools through one address and switch providers when one fails | 128 MB | 1 GB | none | Yes | | LibreTranslate | Translate text on your own server, without sending it to Google or DeepL | 256 MB | 1 GB | none | Yes | | OpenClaw | A personal AI assistant you talk to from a web page or your chat apps | 256 MB | 1 GB | none | Yes | | Hermes Agent | An AI agent your own apps talk to through an OpenAI-style API | 256 MB | 1 GB | none | Yes, as an API | | SillyTavern | Chat and write stories with AI characters, through the AI provider you choose | 128 MB | 1 GB | none | Yes | | Miniflux | All your news feeds in one fast, no-frills reader | 128 MB | none | PostgreSQL | Yes | | ntfy | Send push notifications to your phone or desktop from a script or any app | 128 MB | 1 GB | none | Yes | | Gotify | A simple server for push notifications from your own scripts and services | 128 MB | 1 GB | none | Yes | | Excalidraw | A virtual whiteboard for sketches and diagrams that look hand-drawn | 128 MB | none | none | Yes | | PrivateBin | Paste text or code that only the person with the link can read | 128 MB | 1 GB | none | Yes | | Navidrome | Stream your own music library from any device, like your own Spotify | 128 MB | 2 GB | none | Yes | | Wallabag | Save articles from the web and read them later, without ads or trackers | 128 MB | 1 GB | none | Yes | | Etherpad | Write a document together with other people, watching edits appear live | 128 MB | 1 GB | none | Yes | | code-server | VS Code running in your browser, so you can code from any device | 256 MB | 5 GB | none | Yes | | Gitea | Your own place for Git repositories, issues and pull requests, like a small GitHub | 256 MB | 2 GB | none | Yes | | Dashy | A start page for all the apps and sites you use, with status checks and widgets | 128 MB | 1 GB | none | Yes | | BookStack | A wiki organized like a library, with books, chapters and pages | 128 MB | 2 GB | MariaDB | Yes | | DokuWiki | A wiki that keeps every page as a plain text file, no database needed | 128 MB | 1 GB | none | Yes | | Calibre-Web | Browse and read your ebook collection in the browser | 128 MB | 5 GB | none | Yes | | Kavita | Read your comics, manga and ebooks from one library | 256 MB | 5 GB | none | Yes | | Komga | A server for your comics and manga, with its own reader | 256 MB | 5 GB | none | Yes | | Shiori | Save web pages with one click and keep a readable copy | 128 MB | 1 GB | none | Yes | | flatnotes | Write quick notes as plain markdown files | 128 MB | 1 GB | none | Yes | | Homer | A start page with a tile for every app and site you use | 128 MB | 1 GB | none | Yes | | Fider | Collect feedback and feature requests from your users | 128 MB | none | PostgreSQL | Yes | | Beszel | Watch CPU, memory, disk and network for your own servers | 128 MB | 1 GB | none | Yes | | Readeck | Save articles from the web and read them later, without ads | 128 MB | 1 GB | none | Yes | | Changedetection.io | Get a message when a website you watch changes | 128 MB | 1 GB | none | Yes | | Listmonk | Send newsletters and announcements to your own mailing lists | 128 MB | none | PostgreSQL | Yes | | Shlink | Shorten links and keep the click numbers on a server that's only yours | 256 MB | 1 GB | none | Yes | | The Lounge | Stay connected to IRC from any device | 128 MB | 1 GB | none | Yes | | Traggo | Track your time with tags instead of projects | 128 MB | 1 GB | none | Yes | | TriliumNext | Keep notes in a tree you shape yourself | 128 MB | 2 GB | none | Yes | | Tududi | Organise tasks, projects and notes in one place | 128 MB | 1 GB | none | Yes | | HomeBox | Keep an inventory of everything you own, and what it's worth | 128 MB | 1 GB | none | Yes | | MicroBin | Share a snippet, a file or a link with a short address | 128 MB | 1 GB | none | Yes | | Gokapi | Share a file with a link that expires when you decide it should | 128 MB | 1 GB | none | Yes | | Gonic | Stream your own music and podcasts to any Subsonic app | 128 MB | 5 GB | none | Yes | | Fusion | Follow RSS feeds from one clean inbox | 128 MB | 1 GB | none | Yes | | ByteStash | Save and search the code snippets you keep reusing | 128 MB | 1 GB | none | Yes | | CommaFeed | Read your RSS feeds in a fast, familiar reader | 256 MB | none | PostgreSQL | Yes | | Homarr | A home screen for every app and server you run | 256 MB | 1 GB | none | Yes | | Rallly | Find a date that works for everyone, without the back and forth | 256 MB | none | PostgreSQL | Yes | | PdfDing | Keep your PDFs, read them and pick up where you left off | 128 MB | 2 GB | none | Yes | | Poznote | Write and organise notes with tags, folders and search | 128 MB | 2 GB | none | Yes | | Ocular | Plan your budget with charts that make it clear where your money goes | 128 MB | 1 GB | none | Yes | | Paisa | Track your money in a plain text ledger, with charts to make sense of it | 128 MB | 1 GB | none | Yes | | Grocy | Track groceries, chores and household items, with reminders before anything runs out | 128 MB | 1 GB | none | Yes | | Snipe-IT | Track who has which laptop, licence or asset, with a tag and history for every item | 256 MB | 2 GB | MariaDB | Yes | | Monica | Keep notes on the people in your life, birthdays, calls and conversations included | 256 MB | 1 GB | MariaDB | Yes | | Easy!Appointments | Let people book a slot on your calendar, with reminders and no back and forth by mail | 128 MB | 1 GB | MariaDB | Yes | | Chevereto | Run your own image and video host, with albums, galleries and links to share | 128 MB | 5 GB | MariaDB | Yes | | Lychee | A photo gallery you host yourself, with albums, maps and a slideshow for every trip | 256 MB | 5 GB | MariaDB | Yes | | Matomo | See who visits your site and what they do, on your own server instead of someone else's | 256 MB | 2 GB | MariaDB | Yes | | MediaWiki | Run your own wiki, the same software behind Wikipedia, with pages, history and search | 128 MB | 1 GB | none | Yes | | Roundcube | A web mail client for an inbox you already have, with search, folders and a contact list | 128 MB | 512 MB | none | Yes | | RSS-Bridge | Turn a website with no feed of its own into an RSS or Atom feed your reader can follow | 128 MB | none | none | Yes | Memory is what the app reserves from your plan. A database or cache adds its own, see [storage and memory](#storage-and-memory) below. ## Apps that run as root Home Assistant, FreshRSS, Stirling PDF, NocoBase, Excalidraw, Wallabag, Etherpad, BookStack, DokuWiki, Calibre-Web, Homarr, Poznote, Ocular, Grocy, Snipe-IT, Monica, Lychee, MediaWiki and RSS-Bridge have to start as root: they set up their own system files before they begin. Until 26 September 2026 that stopped them here. Now they run as root inside their own sandbox, which keeps them apart from the server and from other people's apps, like any image you deploy yourself that needs root. Immich needed more memory than an app got here. It now uses a larger size that comes with Pro: 768 MB reserved and up to 2 GB, enough for its first start, when it loads its map data. Face and object search stay off for now. ## How installing works 1. In the [dashboard](https://dashboard.blitz.cloud/), open the App Store or click "Host something new" and choose "A ready-made app". 2. Search by what you want ("photos", "blog", "passwords") or by what you'd like to replace ("Dropbox", "Google Photos"), or browse the categories. Each app also has a page of its own in the store. 3. Pick a name for the app. It becomes the subdomain, like `vault..blitz.cloud`. 4. Click "Put it online". The last step lists everything that gets created first, each database and cache included, and how much of your plan it uses. The store entry brings the rest: the version, the port, the folders to keep, the settings the app reads, and a health check that knows what "working" looks like for that app. If the app needs a database, one is created and connected, and the settings it will fill in are listed before anything is applied. Store apps are restarted automatically if they stop answering their health check. After install, the Environment tab shows every setting and lets you change it. Most store apps follow a version line, like Nextcloud 34, and get new versions within it overnight. If a new version doesn't start, the one before it keeps running. ## First steps after installing The app page lists what to do next for that app: where to sign in, and which setting to change once everyone has an account. Passwords and admin tokens that were made for you, like Vaultwarden's admin token, sit behind Show and Copy on that page, never in the text. Do the first step soon. Many apps make the first person who opens them the admin, so until you have signed up, anyone who finds the address could. Mealie, Joplin Server and Umami start with a password everyone who knows the app knows, and their first steps tell you to change it right away. ## Needs Pro The store works out whether an app fits the free plan before you install it. If it doesn't, the card says "Needs Pro" and why, and the install is refused on the free plan. Every app except Immich fits an empty free account. Whether it fits yours depends on what you already run: the free plan has one database, so a second app that needs a database asks you to make room or move to Pro. The card names the limit it would hit. Immich needs Pro for its memory. ## Apps that only work while they're awake On the free plan an app sleeps after 30 minutes without visitors. For most apps that doesn't matter, because the next visit wakes it. A few do their job with nobody visiting, and the store card says what stops while they sleep: - n8n only runs its schedules while it is awake, and on the free plan webhooks don't wake it. - Uptime Kuma only checks your sites while it is awake. - Syncthing only syncs while it is awake. - Paperless-ngx only fetches documents from your mailbox while it is awake. - Home Assistant only runs its automations while it is awake. - FreshRSS only fetches new articles while it is awake. - Umami only counts visits while it is awake. A visit wakes it, but that first one may be missed. - Activepieces only runs its schedules while it is awake, and on the free plan webhooks don't wake it. - WordPress only runs scheduled posts and plugin jobs while it is awake. - WAHA and Evolution API are only connected to WhatsApp while they are awake, so messages and webhooks wait until then. - OmniRoute and 9router only answer your tools while they are awake, and on the free plan a request from a tool doesn't wake them. - OpenClaw only answers your chat apps and runs its reminders while it is awake, and Hermes Agent only answers and runs its scheduled tasks while it is awake. - ntfy only delivers notifications published while it is awake; a sleeping ntfy misses them. - Changedetection.io only checks the pages it watches while it is awake. - Matomo only counts visits while it is awake. A visit wakes it, but that first one may be missed. On Pro, installing one of these keeps it awake for you. ## Things some apps can't do here - Immich: face and object search are off, because they need more memory than an app gets here. - Home Assistant can't see devices on your home network from here, so it works with devices and services you reach over the internet. - Stirling PDF: very large PDFs can be more than it has memory for. - Forgejo: Git over SSH doesn't reach apps here, so you push and pull over HTTPS with a password or an access token. - Linkwarden: anyone who can open it can make an account, and that can't be switched off reliably, so it starts private. Keep it that way. Saving a copy of a page takes most of its memory for a moment, so add links a few at a time. - OpenCloud sends uploads to itself through its public address, so it only works while that address is public. - Firefly III: recurring transactions and bill reminders need a daily job to call the app, and nothing here does that for you yet. - Open WebUI, OpenClaw, Hermes Agent and SillyTavern run no AI model themselves. You bring an API key from a provider, and Open WebUI needs an embedding key as well to search your own documents. - Hermes Agent is an API here, without its dashboard and terminal chat, which need to run as the machine's owner. - WAHA and Evolution API: WhatsApp can block a number that is used with a third-party client, so use one you could do without. WAHA's free edition connects one number. - Activepieces uses most of its memory before it does anything, so large flows may make it restart. - SillyTavern asks for a user name and password before it opens. The user is admin, and the password is on the app's page after you install it. - FileBrowser Quantum shows the folders your other apps keep, not their databases. It asks for a password too, made the same way as SillyTavern's. - Excalidraw is the editor only: nothing you draw is saved to the server, and there is no live collaboration here. - ntfy has no accounts by default, so anyone who learns a topic name can publish or subscribe to it; keep topic names hard to guess. - Wallabag reinstalls part of itself on every start, so it wakes more slowly than other apps here, about four minutes rather than a few seconds. - Etherpad has no per-pad access control: anyone who knows or guesses a pad's name can open and edit it. - Gitea: Git over SSH doesn't reach apps here, so you push and pull over HTTPS with a password or an access token. - Dashy has no login on the dashboard page itself by default, so anyone with the address can see and edit it; add users under its own config for a real login. - Calibre-Web reads an existing Calibre library, it does not create one; upload a library folder with FileBrowser Quantum before it has anything to show. - Homer has no login and nothing to click to edit: change its config.yml under the app's storage with FileBrowser Quantum to add or edit tiles. - Fider needs a real mail server before anyone can sign in, since sign-in works by mail link; set EMAIL_SMTP_* under Environment to your own provider. - Beszel is only the hub: it shows nothing until an agent you install on another machine connects and reports its numbers to it. - Changedetection.io: nobody is asked for a password until you set one in its Settings, so until then anyone who finds the address can see and change your watches. - Shlink is the API and the redirects only, not a web dashboard: use its initial API key with a Shlink web client to create and manage links. - The Lounge runs in private mode with the one account it makes for you; there is no sign-up page. - Homarr can't see containers running elsewhere from here, so you add tiles by address instead of through its Docker integration. - Rallly can't send sign-in mail until you add your own SMTP settings under Environment; until then, share a poll's own link and guests can still vote on it without signing in. - Paisa has no sign-in of its own, so it starts private and only opens on your own devices; keep it that way. - Roundcube is a mail client for an inbox you already have elsewhere, not a mail server of its own. - Easy!Appointments: booking confirmations and reminders need SMTP settings of your own mail provider, added after setup. - Snipe-IT's mail needs SMTP settings of your own mail provider, added after setup. - Monica: the first account to sign up owns it; after that, turn off new registrations in Settings so nobody else can join. - RSS-Bridge has no accounts of its own beyond the one password, so without it anyone who finds the address could use it to fetch pages; it is on by default. ## Storage and memory An app reserves the storage the table gives for it from your plan's 10 GB, whether or not it fills it. Nextcloud plus its MariaDB takes 6 of the 10 GB, for example. Most apps use the small size (128 MB reserved, up to 512 MB). n8n, Paperless-ngx, Home Assistant, Stirling PDF, Linkwarden, Docmost, OpenCloud, Activepieces, NocoBase, Open WebUI, OmniRoute, LibreTranslate, OpenClaw, Hermes Agent, WAHA, code-server, Gitea, Kavita, Komga, CommaFeed, Homarr, Rallly, Snipe-IT, Monica, Lychee and Matomo use medium (256 MB reserved, up to 1 GB). Immich uses large (768 MB reserved, up to 2 GB), which comes with Pro. An app with a database uses your plan's database, and the database reserves its own memory and 1 GB of storage. See [limits](/docs/limits/) for how that adds up. ## Apps that bring a cache Paperless-ngx, Docmost, Evolution API and Activepieces bring a small cache (Valkey, which speaks Redis) next to their database, for their background jobs. The cache is part of its app: it sleeps and wakes with it and is deleted with it. It keeps nothing and has no backup, and it doesn't count as one of your plan's databases. Its memory, 48 MB, does count. ## Can I install an app that isn't in the store? Yes, if there is a public image for it on Docker Hub, ghcr.io, Quay or another public registry, or if you can build it from its code on GitHub. See [deploy a Docker image](/docs/deploy-docker-image/) and [deploy from GitHub](/docs/deploy-from-github/). The store is the list we have tested; those two paths are for everything else. --- # blitz.cloud vs Fly.io: free hosting, EU regions and Docker compared URL: https://blitz.cloud/compare/fly-io/ Updated: 2026-09-26 Fly.io against blitz.cloud on free tier versus trial, EU regions, Docker deploys, managed Postgres and certificates, with sources checked 14 September 2026. Fly.io is the better choice when you need your containers in many regions close to users, arm64 or fine-grained control over machines, and you're happy to pay per use from the start. blitz.cloud fits when you want to host containers and a database for free in the EU without a credit card. Fly.io has no free tier: the trial ends after 2 machine hours or 7 days. ## At a glance | | blitz.cloud | Fly.io | |---|---|---| | Company | BlitzWorks UG, Regensburg, Germany. No US parent | Fly.io, Inc., San Francisco, US | | EU regions | One region in the EU today, more planned | Amsterdam, Stockholm, Paris, Frankfurt (plus London) | | Free tier | 5 apps, 512 MB memory, 10 GB storage, one database. Apps sleep after 30 minutes without visitors and wake on the next one. No expiry, no card | No free tier. Trial of 2 machine hours or 7 days without a card, machines stop after 5 minutes. Adding a card ends the trial | | Cheapest paid plan | Pro, 7 EUR a month including VAT | Pay per use. Smallest machine (shared CPU, 256 MB) about $2.02 a month in Amsterdam | | An app that stays awake, with a database | Pro, 7 EUR a month for your whole account, up to 5 databases | About $40 a month: smallest machine about $2.02 plus managed Postgres from $38 (checked 14 September 2026) | | Run a finished Docker image | Yes, public Docker Hub images, amd64 | Yes, with `fly deploy --image` | | Git push deploys | Yes, after you connect GitHub, private repositories included | No built-in, GitHub Actions instead | | Managed databases | PostgreSQL 17, MariaDB 11.4, Redis (Valkey 8), with nightly backups | Managed Postgres from $38 a month | | Custom domains and HTTPS | HTTPS on your blitz.cloud subdomains. Custom domains on Pro | First 10 certificates per organisation free, then $0.10 a month each | ## Where Fly.io is the better choice Fly.io runs your container in the regions you choose, and moving it closer to users is a command. If latency outside Europe matters, a single data centre in the EU can't compete. You get direct control over machines, volumes and networking through `flyctl`, with private images and a mature CLI workflow. Custom domains and certificates work now. The pay-per-use model gets cheap at small sizes once you're paying anyway, and it scales well past what a free plan offers. ## Where blitz.cloud fits better - You want to run something without entering a card, and keep it running after a week. - You want a database included. A managed Postgres on Fly.io starts at $38 a month; on blitz.cloud one database is part of the free plan. - You'd rather click through a dashboard than learn a CLI, or install a store app like Uptime Kuma or Linkding in a few clicks. - You want every push to GitHub to go online without writing a CI workflow for it. - A German operator and an EU data centre matter more to you than a choice of regions. ## Moving from Fly.io to blitz.cloud Fly.io apps already run from images, so the move is mostly about the registry. Push the image to Docker Hub as a public amd64 image, make sure it listens on a port such as 8080, and deploy it. Volumes don't copy over automatically; move the data yourself. See [deploy a Docker image](/docs/deploy-docker-image/). If the image is built from a GitHub repository, you can instead connect GitHub and let blitz.cloud build every push. The image can also stay on any public registry, such as ghcr.io, rather than Docker Hub. See [deploy a GitHub project](/docs/deploy-from-github/). ## Sources - https://fly.io/legal/terms-of-service/ - https://fly.io/docs/reference/regions/ - https://fly.io/docs/about/free-trial/ - https://fly.io/pricing/ - https://fly.io/docs/about/pricing/ - https://fly.io/docs/flyctl/deploy/ - https://fly.io/docs/launch/continuous-deployment-with-github-actions/ - https://fly.io/docs/mpg/ Facts checked on 14 September 2026. Prices and plans change; tell us at hallo@blitzworks.io if something here is out of date. --- # Contact blitz.cloud URL: https://blitz.cloud/contact/ Updated: 2026-10-02 How to reach the people behind blitz.cloud. One email address for questions, bug reports, billing and requests about your data, answered in English or German. Write to [hallo@blitzworks.io](mailto:hallo@blitzworks.io). We answer in English or German. The one address is for everything: a question before you sign up, an app that won't start, a bill that looks wrong, a request about your data. ## What helps us answer - the email address of your blitz.cloud account, if you have one - the address of the app it is about, for example `notes.sam.blitz.cloud` - what you did, what you expected and what happened instead ## Before you write Some things go faster without us: - If something looks down, [status.blitz.cloud](https://status.blitz.cloud) shows whether the platform has a problem right now. - The [FAQ](/faq/) and the [docs](/docs/) answer most questions about plans, sleeping apps, domains and databases. - To end a paid plan, use [Cancel your contract](/cancel/). You don't need to write to us for that. - You can download your data and delete your account yourself in the dashboard, under Settings. ## Reporting illegal content or a copyright infringement If an app hosted on blitz.cloud shows something you think is illegal or that infringes your rights, for example your text, photo or software used without your permission, write to the same address. The [imprint](/imprint/#reporting-illegal-content) lists what we need to look into it. We confirm that we received your report and tell you what we decided. Content that breaks the law or infringes other people's rights is not allowed on blitz.cloud ([terms](/terms/), section 8), and we may pause an app that shows it. ## By post BlitzWorks UG (haftungsbeschränkt)\ Graßer Weg 73\ 93053 Regensburg\ Germany blitz.cloud is built and run by BlitzWorks. The [about page](/about/) says more about the company. --- # Deploy an app with a PostgreSQL database URL: https://blitz.cloud/guides/deploy-app-with-postgres/ Updated: 2026-09-26 Host an app with a managed PostgreSQL 17 database on blitz.cloud. DATABASE_URL is set for you, the database is private to your apps and backed up nightly. On blitz.cloud, a database gets created for you while you put the app online. You switch on Needs a database, pick PostgreSQL, and blitz.cloud starts a PostgreSQL 17 database, fills in `DATABASE_URL` for your app, and copies the database off-site every night. The database has no public address; only your own apps can reach it. This guide uses the [node-api example](https://github.com/blitzworks-io/blitz-cloud-examples/tree/main/node-api), a small API that stores notes in PostgreSQL. The same steps apply to any image that reads a connection string from an environment variable. ## How the app finds the database For an image you bring yourself, blitz.cloud looks at the image to guess which settings it expects. When it recognises database variables, the wizard names them before anything is applied. When it doesn't, and you ask for a database, it sets a single `DATABASE_URL`: ```text postgresql://:@:5432/ ``` The host is a short internal name that only resolves inside your own space on blitz.cloud. Your app code needs nothing more than this: ```javascript import pg from "pg"; const pool = process.env.DATABASE_URL ? new pg.Pool({ connectionString: process.env.DATABASE_URL, max: 5 }) : null; ``` No TLS options are needed: the connection never leaves blitz.cloud's internal network, and network rules keep other accounts out of it. ## Test with a local database first ```bash docker network create notes-net docker run -d --name notes-db --network notes-net \ -e POSTGRES_USER=app -e POSTGRES_PASSWORD=secret -e POSTGRES_DB=app \ postgres:17-alpine docker build --platform linux/amd64 -t blitz-example-node-api . docker run --rm --network notes-net --user 1000:1000 --cap-drop ALL \ --security-opt no-new-privileges -p 8080:8080 \ -e DATABASE_URL=postgresql://app:secret@notes-db:5432/app \ blitz-example-node-api ``` ```bash curl -X POST -H 'content-type: application/json' -d '{"text":"first note"}' http://localhost:8080/notes # {"id":1,"text":"first note","created_at":"..."} curl http://localhost:8080/notes ``` In our test the `POST` returned `201` and the `GET` returned the note. The app creates its table on first start, which is the pattern to copy: run migrations when the process starts. That works for any image. A project built from GitHub with a compose file can also run a step like this before each new version goes live; if the step fails, the old version keeps running. Clean up with `docker rm -f notes-db && docker network rm notes-net`. ## Deploy with the database 1. Push the image to Docker Hub as described in [Deploy a Node.js API](/guides/deploy-nodejs-api/). 2. In the [dashboard](https://dashboard.blitz.cloud/), click Host something new, choose "An app from Docker Hub", find your image and pick the version. 3. On the next screen, look at What this app needs. If the Database row already says PostgreSQL, blitz.cloud spotted it. If it says Not needed, open Advanced settings, switch on Needs a database and leave Which one on PostgreSQL. 4. Name the app, choose an address and click Put it online. The database appears on the Databases page with the app it belongs to. Its connection string is masked there until you click to show it. ## Things to know before you rely on it One app, one database. A database belongs to exactly one app, so two apps can't share one. The free plan includes one database; it also takes 128 MB from your 512 MB memory pool and reserves 1 GB of your storage. Nightly backups. Every night the database is dumped and copied to separate storage, outside the machines your apps run on. The free plan keeps 7 nights. Going back to a night is a button on the Databases page, and it replaces the whole database with that night's copy. The database as it is right now is copied first, so you can undo the restore. Details in [Backups](/docs/backups/). No outside access. You can't connect to the database from your laptop with `psql` or a GUI client today. If you need to look inside, add a small admin tool as a second app, or build the query into your own app. Deleting the app asks about the data. When you delete the app you are asked, with no default, whether to keep the database or delete it along with all its nightly copies. MariaDB 11.4 and Redis (served by Valkey 8) are also available. MongoDB is not. More in [Databases](/docs/databases/). --- # Infrastructure designer: your apps and home network on one canvas URL: https://blitz.cloud/infrastructure-designer/ Updated: 2026-10-15 Your apps, databases, domains and home devices on one canvas. Let Home Assistant reach your Hue Bridge or give your NAS a private address, even behind CGNAT. The infrastructure designer is a page in the blitz.cloud dashboard that draws everything in your account on one canvas: apps, databases, addresses, private networks and the devices on them. You connect two things by drawing a line between them. That's how Home Assistant on blitz.cloud reaches the Hue Bridge in your living room, and how your NAS at home gets an address like `nas.lena.blitz.cloud` that only opens on your own devices. Nothing gets opened on your router, so it works behind carrier-grade NAT and DS-Lite too. ## What a line on the canvas does Every line is a real connection, made the same way as on the other pages of the dashboard. Delete the line and the connection goes, after one sentence telling you what stops working. ### Link two apps Draw a line from one app to another and give the link a name, for example `api`. The first app then gets the other's internal address as a setting, `API_URL`, and can call it without a detour through the internet. While the first app is awake, the one it links to stays awake as well, so a call never lands on a sleeping app. ### Connect a database A line from an app to a database connects them, just like on the Databases page. The app gets `DATABASE_URL` and the other connection settings. ### Reach a device at home Draw a line from Home Assistant, or any other app, to a device on your home network and give it a name such as `hue-bridge`. The app now reaches the device under that name, over TCP and UDP, on the ports you choose. Only the apps you drew a line from can reach it. Your other apps can't, and nobody on the internet can. ### Give a home device an address A NAS, a camera or the box Home Assistant runs on at home can get an address like `nas.lena.blitz.cloud`, with HTTPS. It is private by default: it opens on your phone and laptop when they're on your private network, and nowhere else. If you want to open it from any browser, switch it to public. A sign-in page then comes first, and only you and the email addresses you add get past it. You can switch that page off, after a warning about what it means. ## How your home network joins The designer works with the private networks you can already connect on blitz.cloud: your Tailscale tailnet, a WireGuard network you run yourself, for example on a FRITZ!Box, or the WireGuard network blitz.cloud hosts for you. See [private networks](/docs/private-networks/) for how to connect each one. Behind carrier-grade NAT or DS-Lite your router can't take connections from outside, so most remote access setups fail there. The hosted network turns this around: a small Linux machine in your home, like a Raspberry Pi or the server Home Assistant used to run on, connects out to blitz.cloud and carries your home range, for example `192.168.178.0/24`. You don't open or forward a port anywhere. ## Devices show up by themselves Phones, laptops and other devices on your private network appear on the canvas as soon as they're connected. Devices on your home network, like a printer or a smart plug, show up when you click "Scan my network". The scan looks at your home range for the ports such devices use (web interfaces, NAS, cameras, Home Assistant, MQTT, Sonos, Plex, printers) and reads the title of each web page it finds. It never runs on a schedule or by itself. You can also add a device by hand with its address. ## One thing to know about Home Assistant Home Assistant usually finds devices on its own through broadcasts on the local network. Those don't travel through a tunnel, so on blitz.cloud nothing pops up by itself. You add the integration and type the name you gave the device, `hue-bridge`, where it asks for a host. [Connect Home Assistant to devices at home](/docs/home-assistant-home-devices/) has every step. ## What stays closed - A device is only reachable from the apps you connected it to, never from other apps, other accounts or the internet. - Connections from blitz.cloud go only to the devices you forwarded or gave an address, not to the rest of your network. - A device address is private until you switch it to public, and a public one asks for a sign-in first. - The network scan runs only when you click the button. ## What it costs The canvas and links between apps come with every plan, the free one included. The free plan has 3 device forwards and 1 device address. Pro has as many as you need, for 7 EUR a month for your whole account. See [pricing](/pricing/) for the rest. ## Questions ### How do I reach Home Assistant from outside my home without port forwarding? Give the Home Assistant box at home an address in the designer. As a private address it opens on your phone and laptop through your private network, with nothing opened on your router. Made public, it opens in any browser after the sign-in page. Or run Home Assistant on blitz.cloud itself and let it reach your devices at home through forwards. ### Does it work behind CGNAT or DS-Lite? Yes, with the hosted WireGuard network or Tailscale. In both, the machine at home connects out, which works on any connection that can browse the web. A WireGuard config from your own router only works when that router can be reached from the internet, which CGNAT and DS-Lite prevent. ### Can Home Assistant on blitz.cloud find my devices automatically? No. Discovery uses broadcasts (mDNS and similar) that stay inside your home network. Add the integration by hand and enter the device's forward name as the host. "Scan my network" helps you find the device's address first. ### Which devices can an app reach? Anything on your home network that talks TCP or UDP on a fixed port: a Hue Bridge, Shelly plugs, ESPHome boards, an MQTT broker, a NAS, an IP camera's video stream, a printer. Protocols that depend on broadcasts across the network don't work through a forward. ### Is my home network open to the internet then? No. Your router stays closed. Apps reach only the devices you forwarded to them, and a device address only opens to everyone if you make it public, and then behind a sign-in page unless you switch that off. ### Do I need Pro for this? No. The canvas and app links are free, and the free plan includes 3 device forwards and 1 device address. Pro removes those limits. --- # blitz.cloud changelog URL: https://blitz.cloud/changelog/ Updated: 2026-10-19 What changed on blitz.cloud, release by release: Pro, private apps, AI assistants, the App Store, builds from GitHub, databases and backups. Newest first. The newest release, from 19 October 2026, lets you buy a domain on blitz.cloud and lets an app from GitHub build on its owner's own GitHub Actions. The App Store now suggests apps that people who run your apps also run, and offers to keep your busiest app on Pro when you cancel. The cookie dialog is now Google's instead of Clickio. Several fixes round out the day: a free plan limit always shows the Pro offer, the Apps page keeps its layout with no apps yet, a build our side cut off no longer blames your code, and more. Every change that affects what you can do is listed here, newest first. For the current state in one list, see [what's live](/whats-live/). ## 19 October 2026 - Domains are on sale, and apps can build on your own GitHub Actions - You can now buy a domain on blitz.cloud: search a name under Domains, pay, and we register it in your name and point it at your app. [Addresses and HTTPS](/docs/addresses-and-https/) - An app from a connected GitHub project can now build on its owner's own GitHub Actions instead of waiting for one of our build servers. Switch it on in the app's Settings, or when you connect GitHub. [Deploy a GitHub project](/docs/deploy-from-github/) - The App Store now suggests apps that people who run your apps also run, in a "Because you run..." row. [App Store](/docs/app-store/) - When you cancel your plan, you can keep your busiest app on Pro or buy it a Pro app place instead of losing it. [Cancel your contract](/cancel/) - The Domains page suggests names from your own apps. - The cookie dialog is now Google's own, instead of Clickio. - Eight more App Store apps show their own screenshot now, among them WordPress, Immich and Umami. [App Store](/docs/app-store/) - You now get one weekly email about what went live on blitz.cloud; object at any time with one click in any issue. - Fixed: a build our side cut off, for example while fetching your code, no longer blames your code and runs again by itself. - Fixed: hitting a free plan limit always shows the Pro offer now, even when it happened outside the Apps page. - Fixed: the Apps page keeps its heading, "Host something new" and the search field when you have no apps yet. - Fixed: the morning mail about an overnight update comes only when the update failed; the rest are listed in your weekly note. - Fixed: a crashed app's Settings link now opens at the part that's in trouble, and its message no longer promises log lines it doesn't have. - Fixed: a sleeping store app's wake message now names the app and links to its install page. - Fixed: in the last two days of a card-free Pro trial, the trial card now asks plainly whether you want to keep Pro or let it end. ## 18 October 2026 - Pages for AI assistants, and private apps wake on a visit - Pricing, docs, guides, comparisons and app pages now also answer in plain Markdown, for an AI assistant that can't run JavaScript: add `.md` to the address, or ask for `text/markdown`. [AI assistants](/docs/ai-assistants/) - Fixed: a private app on your Tailscale or WireGuard network now wakes up when you visit it while it sleeps. [Private apps](/docs/private-networks/) - More App Store apps show their own screenshot now. [App Store](/docs/app-store/) - Fixed: a store app's logo no longer shows its old initial behind it. - Fixed: emails about a suspended or paused account no longer mention court action. ## 17 October 2026 - Faster builds, and your AI assistant can move files - Fixed: forms, uploads and calls to your app's own API now work when the app is protected by sign-in. They used to fail while the page itself still loaded. - Fixed: Home Assistant stays reachable after it asks you to confirm its October update; the connection used to drop after five minutes. [Home Assistant](/docs/home-assistant-home-devices/) - Your AI assistant can now move a file into or out of an app's kept folder. [Settings and files](/docs/settings-and-files/) - Fixed: an AI assistant's network tool answered with an error for every account; it works again. - Fixed: a confirmation question that never reaches your AI assistant no longer blocks the command it asked about. - A build of a large image now finishes up to 90 seconds sooner, and the steps most pushes repeat are cached between builds. - The time left on a build is now based on your own app's past builds, not everyone's average. - Fixed: a project's declared data folder is kept, and the app starts on the port it declares. - Fixed: a long app name no longer overflows the card when you pick your first app. ## 16 October 2026 - A welcome tour, and sign-in for seven store apps - The welcome tour now asks what you want to put online, then takes you straight there, and a "Make it yours" card helps you finish your first app. - Paperless-ngx, Open WebUI, Mealie, Vikunja, Linkwarden, HedgeDoc and Vaultwarden now offer a "Sign in with blitz.cloud" button that only lets the app's owner in. [App Store](/docs/app-store/) - Fixed: starting the Pro trial with a card, and the Pro plan checkout, now go through instead of failing. - Fixed: a person mistaken for a program now gets a "Wake it up" button instead of a blank answer, and pressing it stays on https. - Fixed: the report form can be sent again. ## 14-15 October 2026 - Know before you install, and a way to report illegal content - If you are signed in and your plan is full, the install page for a store app now says so before the button, with the ways out: remove an app, make it a Pro app, or try Pro. If you already have the app, it says that too. [App Store](/docs/app-store/) - The public cancel form now ends your Pro apps too, not only your plan. [Cancel your contract](/cancel/) - The free 14-day Pro trial is now once per person, even from a new account. [Pricing](/pricing/) - Fixed: a card-trial order step that hangs now says so after 15 seconds and offers a retry. - A domain's price in your account now updates within the hour after a price change, not the next day. - Fixed: Codex CLI can now sign in as an AI assistant; its sign-in used to fail partway through. [Connect an AI assistant](/docs/ai-assistants/) - Fixed: an app with a database that wakes up now waits for the database before it answers, instead of failing once. - Fixed: confirming your sign-up on a different device than you started on now works. - Anyone can now report illegal content on a new page, and a mail that pauses an app or suspends an account says which rule it rests on and that you can ask a person to look again. [Report illegal content](/report/) - Fixed: OpenClaw's control panel now opens directly instead of asking you to pair a device. - The `blitz` command and your AI assistant can now run one command inside an app. [The blitz command](/docs/cli/) - Every App Store app now shows its real logo, on its card and on the install page. [App Store](/docs/app-store/) ## 13 October 2026 - ChatGPT sign-in fixed, and two fixes - Connecting ChatGPT as an AI assistant now works. Sign-in used to stop partway through; that's fixed. [Connect an AI assistant](/docs/ai-assistants/) - The App Store list now shows the apps most people installed in the last 30 days first. A search that finds nothing offers to look on Docker Hub instead, with what you typed carried over. [App Store](/docs/app-store/) - Settings opens again for accounts with a Pro app. It had stopped with an error since Pro apps arrived on 4 October. ## 11 October 2026 - The Pro trial needs no card to start again, and six fixes - Try Pro free for 14 days starts without a card again. Add one anytime during the trial to keep Pro, or do nothing and it ends with nothing charged. [Pricing](/pricing/) - The Pro app add-on page now says what it already does: it lifts the free plan's block on search engines and lets the app use your own domain. [Pricing](/pricing/) - If you leave a Pro-app checkout unfinished, the app's page now offers to pick it back up. - A free app stuck on "Starting" for 3 hours is now stopped instead of held forever. - Passkeys work again in Firefox. [Account security](/docs/account-security/) - Under "Connect GitHub", a line now says GitHub will ask which projects we may read, all or only the ones you pick, and that you can change that or disconnect later. [Deploy a GitHub project](/docs/deploy-from-github/) - Connecting a device to your private network over WireGuard no longer fails to start. [Private apps](/docs/private-networks/) ## 10 October 2026 - Add a device to your private network without a router - The Private network page now has a WireGuard app card: add a device, scan its QR code or download its config file, and open your private apps from your phone or laptop without running a router or VPN server yourself. [Private apps](/docs/private-networks/) ## 9 October 2026 - Connect Codeberg, Gitea or Forgejo, and free background workers stop after 2 idle days - On the free plan, an app without an address that runs in the background now stops when nothing has happened in your account for 2 days (no sign-in, deploy or dashboard visit), instead of 7. We email you one day before, and one click on Start runs it again. Pro and Power are unaffected. [Limits](/docs/limits/) - You can now connect a Codeberg, Gitea or Forgejo account, not only GitLab: private repositories list, and a push deploys the app automatically. [Deploy a GitHub project](/docs/deploy-from-github/) - When the free plan's one background-worker slot is taken, "Put it online" now offers to put the new app online as a visited app instead, or to upgrade to Pro. ## 8 October 2026 - Dockerfile port fix, and a polished git-address step - An app whose Dockerfile moves its web server to another port now starts on that port instead of getting stuck on "Starting". [Deploy a GitHub project](/docs/deploy-from-github/) - The "any git address" step in the wizard now looks like the other options instead of plain text. - Pushing to a connected GitLab project now deploys the app automatically. [Deploy a GitHub project](/docs/deploy-from-github/) - The live log on an app's page no longer fails with "too many open files" on a busy server. [App status and logs](/docs/app-status-and-logs/) - After a Pro trial ends without a card, the Apps page shows what changed for each app, with Pro's payment step already open if you want it back. [Pricing](/pricing/) ## 6-8 October 2026 - Build from any public git address - You can now paste any public git address (GitLab, Codeberg, your own server) in the wizard and build it. Root Dockerfile only; private repositories and deploy-on-push are GitHub-only for now. [Deploy a GitHub project](/docs/deploy-from-github/) - A restart caused by our own node maintenance no longer counts toward an app's 15-restart stop and doesn't show as a crash. - In the "Put your first app online" wizard, the Docker Hub option is now "An app from Docker Hub" and the App Store option says "No code needed." - A new account can't claim an address that uses a well-known brand name or an explicit-content word. Existing addresses are unaffected. [Addresses and HTTPS](/docs/addresses-and-https/) - Free apps' `.blitz.cloud` pages now send a noindex header and don't show up in Google or other search results. Pro apps and your own domain stay searchable. ## 5 October 2026 - Finish an unfinished Pro checkout, and a more reliable GitHub connection - Settings now offers to pick up where you left off if you started getting Pro and did not finish. - Connecting GitHub no longer fails after a few minutes on the page, and a failed connection says why and what to do next. - More of the dashboard, among them the Pro-upgrade messages, the grace notice and the plan-switch comparison, now reads in German and French. ## 4 October 2026 - Payments open in a dialog, and a Pro app for one app on any plan - Checkout now opens in a dialog instead of inside the card, and offers every payment method you turned on in Stripe, not only card and Link. - You can now make one app a Pro app, on any plan: it stays awake, can carry your own domain, and its memory and storage don't count against your plan's room. It costs 1 EUR a month or 10 EUR a year. - The fix wizard's refusal messages now read in German and French too, finishing the dashboard's translation. ## 3 October 2026 - Choose an app's memory and storage size - Settings > Advanced now lets you choose an app's memory and storage size inside your plan's room, instead of one fixed size per app. [Limits](/docs/limits/) - An app's kept files can now grow past the 1 GB they started with. - A setting's value can now hold line breaks, so a whole config file pasted into the Environment tab reaches the app intact. - You can change a Docker app's image version from Settings without losing its address or other settings. - FileBrowser Quantum and SillyTavern joined the App Store. [App Store](/docs/app-store/) - A Python app whose `.python-version` names a patch version now builds on that version, and a Python app with a Flutter folder is no longer mistaken for a Java project. - A crashed app's diagnosis now shows what we found even when no fix step applies. - More of the dashboard's messages, from build errors to refusals, now read in German and French. ## 2 October 2026 - A card at the start of your Pro trial, and domains that outlive their app - The dashboard's address is now dashboard.blitz.cloud. The old beta.blitz.cloud link still gets you there. - Starting a Pro trial now asks for a card; the trial stays optional when a card is offered, and names the day and price it first charges, with a cancel link. [Pricing](/pricing/) - Free background workers now stop after 7 idle days instead of 7 days without a sign-in. Accounts open before today keep the old rule for 42 more days and get a mail first. [Bots and background workers](/docs/deploy-from-github/#bots-and-background-workers) - An app with an open connection to it now counts as visited and stays awake. - A domain you add now belongs to your account and survives if you delete the app it pointed at. [Addresses and HTTPS](/docs/addresses-and-https/) - Pasting a ghcr.io or quay.io image now works the same as a Docker Hub one. - A crashed app's notice now leads straight to the Settings tab where the port is set. - The fix wizard now also appears for Docker and App Store apps, not only GitHub projects. - The onboarding wizard tells your picks apart on the welcome screen, and its last screen puts a ready-made store app one click away. - The Overview now tells you when a bot or background worker also runs in another one of your apps, and offers to turn it off. - Fixed a sign-in page that could load without its stylesheet. - A sign-in tab left open now starts fresh instead of showing a stale "expired" error. - A new cookie policy page is linked in every footer. - More of the dashboard's mails and screens, among them security, app health, plan, referral and lifecycle mails, the Pro-upgrade card and App Store listings, now read in German and French too. ## 1 October 2026 - The dashboard speaks German and French too - The dashboard now speaks German and French too, not only the site. A language switcher names your current language and remembers your choice. - A private or deleted GitHub repository is read as the project's own failure, explained, and not retried. [Deploy a GitHub project](/docs/deploy-from-github/) - Before a build starts on a project too big for any builder, you are warned instead of watching it fail. [Deploy a GitHub project](/docs/deploy-from-github/) - Sign-in and sign-up now fit a phone screen. - Starting a Pro trial says plainly that no card is charged yet. [Pricing](/pricing/) - No ad shows next to the Tailscale connect screen, account settings or the host wizard. - The status page no longer calls one server down an outage when it is only degraded, and a hung server or a database still starting no longer drags the whole status page down with it. [Status](https://status.blitz.cloud/) ## 30 September 2026 - The free plan holds 5 apps, 512 MB and one background app - The free plan now holds 5 apps, 512 MB of memory, 10 GB of storage, one database and one of them running in the background; Pro and Power are unchanged. [Pricing](/pricing/) - Sign-up and sign-in now link to the terms and the privacy policy. - The Logs tab shows which log windows are open and closes the oldest one once the two places are taken; closing a window frees its place right away. [App status and logs](/docs/app-status-and-logs/) - Pasting an image that cannot run as a web server, or is already in the App Store, is told so before it starts. [App Store](/docs/app-store/) - A docker app that crashes because it cannot write to its data path is told the path, not just "restart it and it works". [Settings and files](/docs/settings-and-files/) - The first getting-started email, with three one-click store apps, now arrives two hours after sign-up. [Getting started](/docs/getting-started/) - A build's log fills in while it runs, so a build machine that dies still leaves what it managed to print. [Deploy a GitHub project](/docs/deploy-from-github/) - A failed build always tells you it failed. [App status and logs](/docs/app-status-and-logs/) - A build stopped because it tried to start too many processes at once says so, instead of blaming your code. [Limits](/docs/limits/) - An expired sign-in or verification link explains what to do next. [Account security](/docs/account-security/) - Build logs older than 90 days (for versions no longer live) and the AI's working notes on old diagnoses are deleted on a schedule; your account's audit history is kept 3 years. - Closing your own account now also erases its stored price answers, invites, trial state and usage history. [Account security](/docs/account-security/) ## 29 September 2026 - Programs no longer wake a sleeping free app - A program - an uptime monitor, a webhook, a script - no longer wakes a sleeping app on the free plan. Opening the app in a browser still does. [Pro](/pricing/) keeps an app awake for programs too. ## 26 September 2026 - every App Store app runs here - Home Assistant, FreshRSS, Stirling PDF and NocoBase run here now. They have to start as root, and apps can now do that inside their own sandbox. - Immich runs on Pro, with up to 2 GB of memory. Face and object search are off for now. - Stirling PDF and NocoBase start with a password made for your install instead of one everyone knows. It is on the app page after you install. ## 26 September 2026 - 12 more apps, among them WordPress and AI tools - New apps, among them WordPress, Open WebUI, OmniRoute, 9router, LibreTranslate, OpenClaw, Hermes Agent, WAHA, Evolution API and Activepieces, run here. NocoBase is listed under "Not running here yet", with the reason. Each one was started on the platform before it went in. - A new category, AI & chat, for chat pages, AI routers, agents and translation. - Some apps now start differently from how their image says, because the image's own start needs root. 9router, Hermes Agent, OpenClaw, WordPress and Evolution API install and start without you setting anything. ## 26 September 2026 - Out of beta, and copies of your apps' files on Pro - blitz.cloud is out of beta. - On Pro, the files your apps keep on disk are copied off our servers every night, and 30 nights are kept. You put a night back from the app's Settings tab, and the restore can be undone. [See Pro](/pricing/) ## 25 September 2026 - Uptime, error pages that stay yours, and monorepos - Each app's Overview shows how often it answered this week, like "99.8% this week" or "Down 12 minutes this week". We check every awake app once a minute. A sleeping or paused app doesn't count as down, and a check never wakes it. - Settings lists what you, your AI assistant, GitHub and we changed on your account, newest first. - When your app answers with its own error page, like a 503 during maintenance, visitors now see that page. Ours only shows when there is no running app behind the address: asleep, paused, starting, crashed or being built. If you prefer ours for your app's errors too, switch on "Our page for its errors" in the app's Settings. - The page at a paused app's address says whether its owner paused it or we did. - Build one folder of a repository: name it, like `apps/web`, under advanced settings in the wizard or in Settings. A push that changes nothing in that folder doesn't start a new build. - A sub-address with no app on it shows "Nothing here yet" instead of an error. - Outgoing traffic is limited to 50 Mbit/s per app on the free plan and 200 Mbit/s on Pro. There is still no traffic bill. - An app that mines crypto is paused before it runs, and its owner gets an email that names what we found. ## 25 September 2026 - 30 apps in the App Store - 17 new apps: Paperless-ngx, Actual Budget, Audiobookshelf, Mealie, Vikunja, Joplin Server, Forgejo, Linkwarden, Umami, Wiki.js, HedgeDoc, Planka, Docmost, OpenCloud, Wakapi, SilverBullet and Firefly III. Each was started on the platform before it went in. - Before you install, the store says how much memory and space an app takes, whether it uses your database, and "Needs Pro" with the reason when it doesn't fit the free plan. - Search finds apps by what they replace, so "Dropbox" or "Google Photos" turn up an answer. - Some apps bring a small cache next to their database. It comes and goes with its app and doesn't count as one of your databases. - After an install, the app page shows the first steps: where to sign in, and settings like Vaultwarden's admin token. - Apps that don't run here yet sit in their own section with the reason, instead of an Install button that fails. - The nine categories are named after what people want to do, like "Passwords & security". ## 25 September 2026 - Emails about your apps - We email you when a deploy fails or goes online, when we stop an app, when a restore is done, and when an overnight update ran. - Each topic can be switched off under Settings > Notifications, or with one click from the email itself. Emails about your account, security and billing always arrive. - News about blitz.cloud only comes if you switch it on. ## 25 September 2026 - AI assistants - blitz.cloud has an MCP server at `https://mcp.blitz.cloud/`. Claude, ChatGPT, Cursor, VS Code and other MCP clients can put apps online, create databases, change settings, read logs and add DNS records, with your plan's limits. - Most assistants sign in with your blitz.cloud account in a browser window, so there is no key to copy. Scripts and clients that can't sign in use an API key from the AI tools page. - Deleting, restarting and pausing ask you before they happen, not the assistant, when the client can show a question. - The AI tools page lists every app you connected, with Disconnect. - New page: [connect an AI assistant](/docs/ai-assistants/). ## 25 September 2026 - Private apps - An app can be private: it loses its public address and only devices on your own network can open it. Switch it in the app's Settings tab. - Connect Tailscale by signing in with your Tailscale account, or upload a WireGuard config from your router or VPN server. - A private app keeps its own address, like `https://immich.lena.blitz.cloud`, with HTTPS. It then opens only on the devices in your tailnet, so bookmarks keep working. - The free plan connects one network, Pro up to five, each with as many private apps as you like. Private apps don't sleep. - New page: [private apps](/docs/private-networks/). ## 25 September 2026 - The Pro plan - Pro can be bought in Settings, under Plan and usage: 5 EUR per month including VAT, renewed monthly, cancellable any time. Payment goes through Stripe. - Pro includes 50 apps, 4 GB of memory, 50 GB of storage, five databases with 30 nights of backups, domains you own, apps kept awake, three builds at once that go ahead of the queue, and up to five private networks. - Businesses can enter a VAT ID at checkout. Invoices, card and billing address are managed from Settings. - Cancelling works in Settings or on the [cancel page](/cancel/), without signing in. Pro runs to the end of the paid month. - When Pro ends and an account uses more than the free plan includes, nothing changes for 14 days. After that the newest apps and databases over the limit are paused, never deleted, and they start again when Pro comes back. - When a limit is reached, the message now says what Pro costs. - New pages: [terms](/terms/), [right of withdrawal](/withdrawal/) and [cancel your contract](/cancel/). ## 19 September 2026 - One app of several parts, and a way out of every failed build - A project that runs as several services, like a dashboard, an API and a bot, goes online as one app with one address. The API answers at `/api`, the bot runs in the background, and the parts update and roll back together. - A step can run before each new version, such as database migrations. If it fails, the version you had keeps running. - When a build or a start fails and our own retries are used up, the app page says what went wrong in one sentence and lists the steps that fix it, one button each: paste a key, set up a database, use another Dockerfile, or let us write one. It never makes up a key that belongs to someone else. - A build that can't find a file names it, capital letters and all, with the line that asks for it. - Builds come in three sizes, picked from what the project is, and run on build servers of their own. Pro builds go first. - Rename an app from its page heading. - Putting a database back to an earlier night can be undone. - Delete your account yourself in Settings, change the email you sign in with, and download everything we hold about your account as one file. - The Domains page reads where your domain's DNS is run and shows the records with that provider's field names. ## 18 September 2026 - The Activity tab, and putting a version back - The Deployments tab is now Activity: builds, versions going live, restarts, sleeps and wakes and setting changes, grouped by day, with filters for versions, problems and changes. - "Put this version back" works on the last 10 versions that went live, and the confirmation says what stays. - While a build runs, the Overview shows its steps as sentences, how long each took, and your place in the queue. - An app can be built with any of the project's Dockerfiles and started with its own command. - Bots and background workers run without an address, and never sleep. - A single request to an app can now be up to 100 MB, so larger uploads reach it. ## 18 September 2026 - DNS records, and renames that keep links working - The Domains page has a DNS records panel, marked advanced. Add A, AAAA, CNAME, TXT and MX records under your address, up to 10 per account. A record that would take one of your apps offline is refused, and the message names the app. - After you rename your main address, the old one sends visitors to the same page under the new one for 14 days. Nobody else can take the old name in that time. It used to stop answering straight away and stay reserved for 30 days. - Settings in your apps that contain the old address, like Ghost's `url`, are changed to the new one when you rename, and those apps restart. The same happens when you move one app to a different subdomain. - Connecting a domain you own is built and part of the Pro plan, which isn't on sale yet. ## 17 September 2026 - Sleeping apps, and Dockerfiles written for you - An app nobody visits for two hours goes to sleep and wakes on the next visit. The first request waits for it, about ten seconds, and then gets the app's own answer, forms included. Keeping an app awake is part of Pro. - A project without a Dockerfile gets one written for it. When that Dockerfile doesn't build, it's rewritten from the end of the build log, up to three times. - Apps update themselves overnight. When a new version doesn't start, the one before goes back online and the Activity tab says why. - An app that crashes 15 times in a row is stopped, and its page says so. - Typing a free `.blitz.cloud` shows that it's free, with a button to claim it. - Each app's Overview shows requests and data served over the last week, hour by hour. ## 14 September 2026 - Build your own code from GitHub - Paste a link to any public GitHub repository in "Host something new" and blitz.cloud clones it, builds it and runs the result under your address with HTTPS. It does not have to be your repository. - A project with a Dockerfile is built with it. A project without one is detected and built anyway. - The build log sits under the Deployments tab, under the line it belongs to, and stays readable afterwards. A failure gets a sentence you can act on, with the raw log underneath. - The version running stays up until a new build works, so a failed build changes nothing. - The port comes from what the built image declares, and your app is told to listen on it. - Builds run in a sandbox with no access to anything of ours or anyone else's. - Connect your GitHub account to pick from your repositories, build private ones, and put a new version online every time you push. ## 14 September 2026 - Visitor statistics and cookie consent - Visits to blitz.cloud and the dashboard are counted with BlitzWorks' own Matomo in the EU, without cookies, with a shortened IP address and nothing passed on. - One cookie that recognises a return visit is only set after a yes. Allowing and declining are the same size and one click each, and the choice can be changed from the footer or in Settings. - The dashboard reports routes, not what's in them: Matomo sees `/apps/:id`, not which app. - Hosted apps can't send numbers into the statistics. ## 13 September 2026 - Databases and nightly backups - Create PostgreSQL, MariaDB or Redis databases in one click. They are usually ready in under a minute. - Apps that need a database get one set up and connected, with the settings they read filled in and shown before anything is applied. - Every database is copied off our servers every night. The free plan keeps 7 nights, and PostgreSQL and MariaDB restore with one button. - Databases are reachable from your own apps and from nowhere else. - Deleting an app asks what should happen to its database, with no preselected answer. - Each app keeps its own database, so two apps can't overwrite each other's tables. - MongoDB is not offered, and apps that need it say so before you install them. - Fixed: signing in could fail for a minute or two during a release. ## 13 September 2026 - App Store, settings and files that stay - An App Store with 13 open-source apps, searchable and grouped by purpose. Each card says what the app needs, and whether something about it doesn't work here, before the install button. - Encrypted environment variables per app, hidden until revealed, applied on restart. - Files that survive restarts. Each account has one disk and each app its own folder on it. - "Needs attention" shows why an app is unhappy, with its last log lines on the same page. - A deployment history for every app. - App Store apps get health checks that know what "working" means for them, and are restarted when they stop answering. ## 12 September 2026 - Hosting goes live - Put any public Docker image online under your own address. The wizard searches Docker Hub as you type and lists the real tags. - blitz.cloud works out the port, a needed database and the folders to keep from the image itself, with a language model filling the gaps. - A subdomain per app under your address, created, renamed and deleted freely. - A wildcard HTTPS certificate for every account. - Live logs, restart, pause and delete. - Plan meters in Settings that show the limits the platform actually enforces. - Every app runs in a gVisor sandbox as a non-root user. ## 12 September 2026 - Accounts and addresses - Open signup, no waiting list and no invite codes. - Sign in with email and password, GitHub or Google. Passkeys and two-step verification with an authenticator app. - Settings shows every signed-in device, with sign-out per device. - Claim your address with a live availability check. Rename it once every 14 days; old names are held for 30 days. - Signup is protected with rate limits and a block on throwaway email providers. - Fixed: account emails were not being delivered on the first day. ## 12 September 2026 - First version - The blitz.cloud landing page, the platform's control plane and its database went online, with wildcard HTTPS for blitz.cloud. --- # blitz.cloud vs Netlify: credits, containers and EU hosting compared URL: https://blitz.cloud/compare/netlify/ Updated: 2026-09-26 Netlify against blitz.cloud on credit-based free plans, function regions, containers, databases and custom domains, with sources checked 14 September 2026. Netlify is the better choice for static sites and frontend projects that want preview links for every branch, custom domains on the free plan and a global CDN. blitz.cloud fits when you need to run a container, a self-hosted app or a traditional database in the EU. Netlify's free plan has 300 credits a month, and sites pause when those are used up. ## At a glance | | blitz.cloud | Netlify | |---|---|---| | Company | BlitzWorks UG, Regensburg, Germany. No US parent | Netlify, Inc., San Francisco, US | | EU regions | One region in the EU today, more planned | Function regions Frankfurt, Dublin, London self-serve, Paris and Milan through support. Default is Ohio. Changing the region is Pro and Enterprise only | | Free tier | 5 apps, 512 MB memory, 10 GB storage, one database. Apps sleep after 30 minutes without visitors and wake on the next one. No expiry, no card | 300 credits a month, hard limit, sites pause when used up. No card needed | | Cheapest paid plan | Pro, 7 EUR a month including VAT | Personal, $9 a month (1,000 credits) | | Run a finished Docker image | Yes, public Docker Hub images, amd64 | Not verified | | Git push deploys | Yes, after you connect GitHub, private repositories included | Yes | | Managed databases | PostgreSQL 17, MariaDB 11.4, Redis (Valkey 8), with nightly backups | Netlify Database, serverless Postgres, on credit-based plans | | Custom domains and HTTPS on free | HTTPS on your blitz.cloud subdomains. Custom domains on Pro | Yes | ## Where Netlify is the better choice For a static site or a Jamstack frontend, Netlify is hard to beat. Push to a branch and the site builds, deploys and gets a preview link. Your own domain with HTTPS works on the free plan, and the CDN serves visitors worldwide. Netlify has spent years polishing forms, redirects, functions and build plugins around that workflow. If your project is a website rather than a server process, you'll get more from Netlify today. ## Where blitz.cloud fits better - Your app is a long-running server in a container: an API, a Discord bot's web dashboard, or a self-hosted tool like n8n. - You need MariaDB or Redis, or a Postgres database that lives next to your app. - You want the app and its data in the EU by default, without a paid plan to change the region. - You'd rather know your app keeps running than track credits. ## Moving from Netlify to blitz.cloud A static site moves if you serve the build output from a small web server image, for example `nginxinc/nginx-unprivileged` listening on 8080, pushed to Docker Hub. Netlify Functions, forms and redirects rules don't translate one to one and need to become part of your own server. See [host a static site](/guides/host-static-site/) and [deploy a Docker image](/docs/deploy-docker-image/). Keep that Dockerfile in your GitHub repository, connect GitHub on blitz.cloud, and every push rebuilds the site. See [deploy a GitHub project](/docs/deploy-from-github/). ## Sources - https://www.netlify.com/legal/terms-of-use/ - https://docs.netlify.com/build/functions/optional-configuration/ - https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/ - https://www.netlify.com/pricing/ - https://www.netlify.com/changelog/2026-04-28-netlify-database/ Facts checked on 14 September 2026. Prices and plans change; tell us at hallo@blitzworks.io if something here is out of date. --- # Managed databases on blitz.cloud - PostgreSQL, MariaDB, Redis URL: https://blitz.cloud/docs/databases/ Updated: 2026-10-16 Create managed PostgreSQL 17, MariaDB 11.4 or Redis (Valkey 8) databases on blitz.cloud, connected to your app automatically and backed up every night. blitz.cloud offers managed PostgreSQL 17, MariaDB 11.4 and Redis, served by Valkey 8. A database is created for you when an app needs one, or from the Databases page, and its connection details are injected into the app as environment variables. Databases are only reachable from your own apps and are backed up every night. ## Engines | Engine | Version | Port | Connection string | |---|---|---|---| | PostgreSQL | 17 | 5432 | `postgresql://user:password@host:5432/name` | | MariaDB | 11.4 | 3306 | `mysql://user:password@host:3306/name` | | Redis (Valkey) | 8 | 6379 | `redis://:password@host:6379/0` | Redis is served by Valkey, the open-source fork. It speaks the same protocol, so Redis clients and `redis://` URLs work unchanged. MongoDB is not offered. Its licence, the SSPL, is written to stop exactly the kind of hosted offering blitz.cloud would be. An app that needs MongoDB says so before you install it. Not sure which one to pick? PostgreSQL is the right answer for almost everything. ## Creating a database There are four ways a database gets created: 1. You install an App Store app that needs one. Nextcloud gets MariaDB, for example. 2. You deploy a Docker image and blitz.cloud detects that it needs one, or you turn on "Needs a database" under Advanced settings in the wizard. 3. On an app's page, "Give it a database" opens the same form with that app already chosen. 4. You create one on the [Databases page](https://dashboard.blitz.cloud/databases) by choosing an engine and a name, then connect it to an app. A new database is usually ready in under a minute. It only reports ready once the database server really answers. The card shows the engine, how much data it holds and which app uses it. The connection details are separate rows, each with a Copy button: connection string, host, port, database name, user and password. The password and the connection string stay hidden until you click Show. ## How the app gets the connection details When an app's variable names are known, blitz.cloud fills them in. Nextcloud gets `MYSQL_HOST`, `MYSQL_DATABASE`, `MYSQL_USER` and `MYSQL_PASSWORD`, for example. The wizard lists these before it applies anything. Connecting a database to an app always leaves the app with a `DATABASE_URL` holding the full connection string, and the page says which settings it filled in. Many tools read that name by convention, among them Rails, Prisma schemas and Django with dj-database-url. The host in the connection string is a short internal name. It resolves inside your account and nowhere else. ## One database per app Each database belongs to one app, and each app has at most one database. Two apps sharing a database would overwrite each other's tables; two WordPress sites on one database destroy each other's posts. The database is named after the app and renamed along with it. ## Caches that come with store apps Some App Store apps bring a small cache next to their database: Paperless-ngx and Docmost do. It is Valkey, like the Redis above, but it belongs to the app. It sleeps and wakes with the app, is deleted with it, keeps nothing and has no backup. It doesn't count as one of your plan's databases, but its 48 MB of memory does count. The store lists the cache before you install. ## Sleeping with your apps A database that holds data sleeps once every app linked to it is asleep or paused, and starts again before the app does on the next wake. The database's page says "Sleeping" while this is happening. A database with no app linked to it keeps running. After a full day asleep, your account's disk is put away too, so the first wake after that can take a minute or two longer, the same as for an app that keeps its own files. Nothing changes while a database sleeps, and nobody but your own apps could reach it anyway. ## Network access Databases have no public address and no open port on the internet. Only apps in your own account can connect to them. That also means you can't connect from your laptop with `psql` or a GUI client today. ## Deleting A database that an app uses can't be deleted on its own. It goes when the app goes. When you delete the app, after typing its name, you are asked what to do with the database: keep it for another app, or delete it together with every nightly copy. There is no default answer. ## Backups Every running database is copied off our servers every night: 7 nights are kept on the free plan, 30 on Pro. Restoring a PostgreSQL or MariaDB database to a night is one button, and the restore can be undone: before anything is replaced, we copy the database as it is right now, and Undo puts that copy back. Details in [backups](/docs/backups/). A sleeping database isn't copied every night, since its data can't change while it sleeps. Its last copy was taken just before it went to sleep. "Download my data" in Settings doesn't include what is inside your databases. To take the data itself with you, use [Download a copy](#download-a-copy). ## Bring your data Moving from another host? You can upload a PostgreSQL dump into an empty database. 1. Make a dump with `pg_dump -Fc --no-owner -d "" -f app.dump` (pg_dump 17 or older). 2. On Databases, open Upload a dump on the database. 3. Drop the file onto the panel, or choose it from your computer. The file goes from your browser straight to our storage, and the panel shows how far it got. Keep the page open until it says the import has started. Once the upload is done, we check that the database has no tables and import the file in one go. If anything fails, nothing is kept. Owners, grants and subscriptions in the dump are left out, and we delete the file once the import is done. Files that work: the pg_dump custom format (`.dump`), tar, plain `.sql` and `.sql.gz`. Limits: PostgreSQL only, an empty database only, and a file up to the database's storage (1 GB today), never more than 2 GB. ## Download a copy Open Download a copy on a database and press Make a copy. It takes a few minutes. When it's ready, the download starts by itself, and the panel keeps a Download button for 24 hours. After that we delete the copy, and you can make a new one. You can make 10 copies of a database a day. What you get depends on the database: - PostgreSQL: a `.dump` file in pg_dump's custom format. Put it back with `pg_restore --no-owner -d "" app.dump`, or upload it into an empty database here. - MariaDB: a `.sql.gz` file. Load it with `gunzip -c app.sql.gz | mariadb -h -u -p `. - Redis: a `.rdb` file, which Redis and Valkey read when they start. ## Limits The free plan includes one database, Pro five. Each database reserves 1 GB of storage (Redis: 0.5 GB) and some memory from your pool: 128 MB for PostgreSQL, 192 MB for MariaDB, 64 MB for Redis. See [limits](/docs/limits/). Database versions are fixed at the versions above. There are no automatic major-version upgrades. --- # Move an app from Vercel to an EU host URL: https://blitz.cloud/guides/migrate-from-vercel-to-eu/ Updated: 2026-09-26 How to migrate a Next.js app from Vercel to blitz.cloud in the EU: standalone Docker build, environment variables, database, and what doesn't carry over yet. To move a Next.js app from Vercel to blitz.cloud, you build it with `output: "standalone"` into a Docker image that runs on port 8080 without root, push the image to Docker Hub, deploy it on blitz.cloud, and copy your environment variables across. The app then runs on servers in the EU, operated by a German company. Whether that is a good trade depends on how much of Vercel's platform your app uses, so read the next section before you start. ## What moves cleanly, and what doesn't yet What carries over today: - Next.js apps that run as a Node server: server components, server actions, route handlers in `app/api`, and middleware (called proxy since Next.js 16) running in the Node server. - Fully static sites, including `output: "export"` builds. - Environment variables and secrets. - A PostgreSQL, MySQL/MariaDB or Redis database, as long as your data can be loaded by the app itself (see below). What you give up, at least for now: - Preview deployments per pull request. Deploys on `git push` do carry over once you connect GitHub, but every push goes to the one app, not to a preview. - Your own domain on the free plan. Connecting one needs Pro at 7 EUR per month; without it apps live under `yourname.blitz.cloud`. - A global edge network. blitz.cloud serves from one data centre in the EU. Visitors in Europe won't notice; visitors in Australia will. - Edge functions and Vercel-specific services such as Vercel Blob, Edge Config, KV, Cron Jobs and Web Analytics. - Automatic image optimisation as a managed service. `next/image` still works in standalone mode, but the resizing runs inside your app and uses its memory. - Scale to zero and per-request billing. An app on blitz.cloud is a long-running process with 128 MB of memory reserved and a ceiling of 512 MB. If the second list is where your app lives, stay on Vercel or look at a host that has those features today. If your app is a normal Next.js server with a database and the reason to move is EU hosting, keep going. ## Step 1: build a standalone image Turn on standalone output in `next.config.mjs`: ```javascript /** @type {import('next').NextConfig} */ const nextConfig = { output: "standalone", }; export default nextConfig; ``` Add a `Dockerfile` next to `package.json`: ```dockerfile FROM node:22.23.2-alpine3.24 AS deps WORKDIR /app COPY package.json package-lock.json ./ RUN npm ci FROM node:22.23.2-alpine3.24 AS build WORKDIR /app COPY --from=deps /app/node_modules ./node_modules COPY . . ENV NEXT_TELEMETRY_DISABLED=1 RUN npm run build FROM node:22.23.2-alpine3.24 WORKDIR /app ENV NODE_ENV=production NEXT_TELEMETRY_DISABLED=1 PORT=8080 HOSTNAME=0.0.0.0 # standalone/ holds server.js and the node_modules it needs; static files and # public/ are not copied into it by Next, so they are added here. COPY --from=build --chown=1000:1000 /app/.next/standalone ./ COPY --from=build --chown=1000:1000 /app/.next/static ./.next/static COPY --from=build --chown=1000:1000 /app/public ./public USER 1000 EXPOSE 8080 CMD ["node", "server.js"] ``` And a `.dockerignore`, so your local build output doesn't end up in the image: ```text node_modules .next .git ``` `HOSTNAME=0.0.0.0` makes the server listen on every interface instead of only inside the container. The `--chown` flags let the app write its cache as user 1000. We tested this Dockerfile with Next.js 16.3.5: a page, a route handler and a file from `public/` all answered `200` when run as user 1000 with every capability dropped. If you use pnpm or yarn, swap the install command and lockfile name. ## Step 2: test it locally the way blitz.cloud runs it ```bash docker build --platform linux/amd64 -t yourname/my-next-app:1.0.0 -t yourname/my-next-app:latest . docker run --rm --user 1000:1000 --cap-drop ALL --security-opt no-new-privileges \ -p 8080:8080 --env-file .env.production.local yourname/my-next-app:1.0.0 ``` Click through the app at http://localhost:8080 before you go further. Anything that breaks here, like a missing variable or a write to a folder user 1000 may not touch, would break the same way on blitz.cloud. ## Step 3: move the environment variables Pull the production variables from Vercel with the CLI: ```bash vercel env pull .env.production.local --environment=production ``` There is one trap. Variables starting with `NEXT_PUBLIC_` are baked into the JavaScript at build time. Setting them on blitz.cloud afterwards changes nothing in the browser. Pass them to `docker build` instead, for example with `ARG NEXT_PUBLIC_API_URL` and `ENV NEXT_PUBLIC_API_URL=$NEXT_PUBLIC_API_URL` in the build stage. Server-only variables are read when the app runs, so those go on blitz.cloud's Environment tab. Remove anything Vercel-specific, like `VERCEL_URL`, and replace code that relies on it with your new address. ## Step 4: push and deploy The quickest way is to let blitz.cloud build from your repository. Commit the Dockerfile and `.dockerignore`, connect your GitHub account on blitz.cloud, choose "My own code" and pick the repository and branch. Every push then builds and goes online. Because the build runs on blitz.cloud, put `NEXT_PUBLIC_` values that aren't secret straight into the build stage with `ENV`. Then add your server-side variables on the app's Environment tab and restart the app. To push the image yourself instead: ```bash docker push --all-tags yourname/my-next-app ``` The Docker Hub repository must be public. Your image contains your built app, so anyone can pull it; keep secrets out of the image and in environment variables. 1. In the [blitz.cloud dashboard](https://dashboard.blitz.cloud/), click Host something new and choose "An app from Docker Hub". 2. Search for `yourname/my-next-app` and pick `1.0.0`. 3. Check What this app needs says port 8080. If the app uses a database, open Advanced settings and switch on Needs a database. 4. Pick an address and click Put it online. 5. Open the app's Environment tab, add your server-side variables and restart the app. ## Step 5: the database If your database is Vercel Postgres, Neon or Supabase, the least disruptive option is to leave it where it is for now and point `DATABASE_URL` at it. Apps on blitz.cloud can make outgoing connections. Note that this keeps your data outside the EU if that database is outside the EU, which may be the very thing you are trying to fix. To bring the data into blitz.cloud, create the app with a PostgreSQL database, then load a dump from inside your app. There is no way to connect `psql` to a blitz.cloud database from your laptop today, so a one-off import has to run as part of the app, for example a migration script that restores seed data on first start. For a large database that is awkward, and it is worth waiting until outside access exists. ## Checklist - [ ] `output: "standalone"` set and the image builds for `linux/amd64` - [ ] Image runs locally with `--user 1000:1000 --cap-drop ALL` - [ ] `NEXT_PUBLIC_` variables passed at build time - [ ] Server-side variables added on the Environment tab, app restarted - [ ] No Vercel-only APIs left (Blob, KV, Edge Config, `VERCEL_URL`) - [ ] Database either reachable from blitz.cloud or migrated - [ ] Links and OAuth callback URLs updated to the new `*.blitz.cloud` address - [ ] Old Vercel project kept running until the new one has served real traffic ## Why move at all? Vercel is a US company, so data it handles falls under US law, including the CLOUD Act, whatever region it sits in. blitz.cloud is run by BlitzWorks UG (haftungsbeschränkt) in Regensburg on servers in the EU, and neither BlitzWorks nor its data centre provider has a US parent. Requests to blitz.cloud addresses do pass through Cloudflare, a US company, on the way in; custom domains don't. For some teams that settles a GDPR question, for others the Cloudflare part matters. Every provider involved is listed on [Data location and GDPR](/eu-data/). A side-by-side feature comparison is on [blitz.cloud vs Vercel](/compare/vercel/). --- # Backups and restore on blitz.cloud URL: https://blitz.cloud/docs/backups/ Updated: 2026-10-03 blitz.cloud copies every database off-site every night, and on Pro the files your apps keep too. How long copies are kept, how restore works, and what is not backed up. blitz.cloud backs up every running database every night to separate storage, away from the servers your apps run on. The free plan keeps the last 7 nights, Pro the last 30. On Pro the files your apps keep on disk are copied every night too. PostgreSQL, MariaDB and app files can be put back to any of those nights with one button, and each restore can be undone. A database that sleeps with its apps is copied once just before it goes to sleep and not again until it wakes, and its last copies are kept until newer ones replace them. ## What is backed up | Data | Free | Pro | |---|---|---| | PostgreSQL databases | Every night, 7 nights | Every night, 30 nights | | MariaDB databases | Every night, 7 nights | Every night, 30 nights | | Redis (Valkey) databases | Every night, 7 nights | Every night, 30 nights | | Files your apps keep on disk | No | Every night, 30 nights | | Your account and settings | Every night, as part of the platform's own backup, 30 nights | The same | A database or app that is not running at night, for example while it moves to another server, is copied later that day, once it runs again. The small cache some App Store apps bring next to their database, like Paperless-ngx and Docmost, is not backed up. It writes nothing to disk, so there is nothing to copy. ## Where the copies go Backups are streamed to storage in the EU that is separate from the servers running your apps, so a problem with those servers doesn't take the copies with it. They are encrypted by the backup tool (restic) before they leave the cluster. Each Pro account's file copies sit in a repository of their own that the app itself can add to but never delete from. ## Restoring a database Open the database on the [Databases page](https://dashboard.blitz.cloud/databases). Each night is listed by date, like "the night of Friday 12 September". Pick one and confirm. A restore replaces the database with that night's copy. It does not merge. Anything written since that night is gone afterwards, and the confirmation says so before you press the button. We copy the database as it is right now first, so you can undo the restore. Redis restores are not a button yet. The copies are taken like any other, but putting one back needs the engine stopped and a file replaced. Write to hallo@blitzworks.io and we do it by hand. ## Restoring an app's files (Pro) Open the app, then Settings, then Backups. Each night is listed with its size. Pick one and confirm. The app stops for a few minutes, every folder it keeps is put back to that night, and it starts again by itself. Files added or changed since then are gone afterwards. We copy the folders as they are right now first, and that copy is kept for 7 days, so you can undo the restore from the same list. Databases are not touched; each has copies of its own. If a file could not be read when the copy was taken, the list says how many. ## Deleting deletes the backups When you delete a database, every nightly copy of it goes too. When you delete your account, every copy of its databases and app files goes within a day. That's where a click destroys data that can't be brought back, so the dialogs say it in those words. ## On the free plan Folders an app keeps on disk survive restarts, but on the free plan they are not copied anywhere. If your app stores uploads or a SQLite file on disk, keep your own copy of anything you can't lose, or use a managed database. ## Size How much a database holds is measured with the first nightly copy. Until then the card says "size known after tonight's copy" instead of showing zero. --- # blitz.cloud FAQ - hosting, Docker, databases, pricing and GDPR URL: https://blitz.cloud/faq/ Updated: 2026-10-11 Yes, the free plan needs no credit card. Answers on pricing, Docker, databases, backups, domains and GDPR. blitz.cloud is a European hosting platform run by BlitzWorks, a German company. You can put open-source apps, public Docker images and your own code from GitHub online under your own free address, with managed databases and automatic HTTPS. Below are short answers to the questions people ask most; each links to the page with the details. ## About blitz.cloud ### What is blitz.cloud? blitz.cloud is a hosting platform where you claim an address like `lena.blitz.cloud` and run apps under it. That can be one of 96 open-source apps from the App Store, any public Docker image, or your own code from GitHub, which we build and put online again every time you push. Managed PostgreSQL, MariaDB and Redis databases, automatic HTTPS and nightly database backups come with it. It is built and operated by BlitzWorks UG in Regensburg, Germany. ### Is blitz.cloud related to Blitz.js, blitz.dev or StackBlitz? No. blitz.cloud is an independent product of BlitzWorks UG and has no connection to Blitz.js, blitz.dev, StackBlitz or Bolt. See [about](/about/). ### Who is blitz.cloud for? People who want their own apps online without running a server: developers with a side project or a small API, self-hosters who want Vaultwarden or Uptime Kuma without a home server, and anyone who prefers their data in the EU. ### Is blitz.cloud production ready? It's out of beta since 26 September 2026. Hosting, builds from GitHub, databases, backups and the paid plan run for real, and each app's page shows its uptime. Some things are still missing, like private Docker images or a choice of region. Check [what's live](/whats-live/) before you put something important on it. Until 31 March 2027 blitz.cloud is in its start phase. During that time we may cancel plans and accounts with 14 days' notice and without giving a reason. You then get back the whole running month or year you have paid for. See the [terms](/terms/), section 6a. ### How do I get help? Click "Give feedback" at the top of the dashboard, or write to hallo@blitzworks.io. We read every message and answer by email. ### Can I sign up with a throwaway email address? No. Throwaway addresses are not accepted, also not through GitHub or Google sign-in. Use an address that stays yours, because we send password resets and notices about your account and apps there. Privacy-friendly addresses, such as forwarding addresses, are fine as long as mail reaches you. The rule is in section 2 of the [terms](/terms/). ### Can I have more than one account? No, each person has one account. Addresses that land in the same mailbox, such as name+test@gmail.com and name@gmail.com, count as the same account. We refuse a second one at signup. If you already have several, the one you used last stays active and we suspend the others. Nothing is deleted. The rule is in section 2 of the [terms](/terms/). ## Pricing ### Is blitz.cloud free? Yes. The free plan costs 0 EUR, needs no credit card and has no time limit. It includes 5 apps, 512 MB of reserved memory, 10 GB of storage and one managed database. See [pricing](/pricing/). ### Is there a paid plan? Yes, two. Pro costs 7 EUR a month including VAT, for your whole account, with 50 apps, 4 GB of memory, 50 GB of storage, 5 databases, your own domains and apps that stay awake. Power costs 19 EUR a month and has everything in Pro with more room. Both renew monthly, or yearly at 70 EUR and 190 EUR, and you can cancel any time. You buy them in the dashboard under Settings. You can try Pro free for 14 days; you add payment details only if you decide to keep it. Nothing is charged if you don't. The first month is refunded if you ask within 30 days. See [pricing](/pricing/). ### Can my business get an invoice with its VAT ID? Yes. Enter the VAT ID at checkout and it goes on every invoice. A business in another EU country is billed without VAT under the reverse-charge rule. Invoices are under Settings. ### How do I cancel Pro? In Settings, under Plan and usage, or on the [cancel page](/cancel/), which works without signing in. Pro runs until the end of the month you have paid for. If your account then uses more than the free plan includes, nothing changes for 14 days, and nothing is ever deleted. See the [terms](/terms/). ### Do free apps go to sleep? Yes. An app nobody has visited for 30 minutes goes to sleep. It wakes when a person opens it in a browser, which takes a few seconds. Requests from programs, such as uptime monitors, scripts or webhooks, don't wake it. On Pro an app sleeps after two hours, and you can keep it awake. Bots and background workers without an address never sleep. A database sleeps when every app linked to it sleeps or is paused, and starts again before the app wakes. One without a linked app keeps running. ### Why does my free app show "Made with blitz.cloud"? On the free plan, the HTML pages your apps serve show a small "Made with blitz.cloud" link in a bottom corner. It loads nothing from other servers, sets no cookie and tracks nobody. Visitors can hide it, and pages whose Content-Security-Policy does not allow it don't get it. JSON, images and downloads are never changed. On Pro and Power it is off, and you can turn it on in an app's Settings. See the [terms](/terms/), section 9. ### Is there a bandwidth limit? There's no bandwidth quota and no traffic bill. Outgoing traffic is limited in speed instead: 50 Mbit/s per app on the free plan, 200 Mbit/s on Pro. ## Deploying ### Can I deploy any Docker image? You can deploy public images from Docker Hub, ghcr.io, Quay and other public registries that are built for amd64, including images that run as root. Private images aren't supported yet. See [deploy a Docker image](/docs/deploy-docker-image/). ### Why does my Docker image not start? The usual reasons: it is only built for arm64, it listens on a different port than the one chosen, or it is missing a setting it needs. The app page says which in a sentence and shows the last log lines. See [app status and logs](/docs/app-status-and-logs/). ### My app has been starting for a long time. What can I do? The first start downloads the app, and a large image can take a few minutes. If it stays on Starting much longer, the app usually runs but nothing answers on the port you chose. Look in its logs for the port it listens on and set that port on the app's Settings tab. If the page says there is no room on blitz.cloud right now, that one is on us: we add servers, and the app starts by itself once there is room. See [app status and logs](/docs/app-status-and-logs/). ### Can I deploy from GitHub with git push? Yes. Connect your GitHub account, pick a repository, public or private, and every push to its branch is built and put online; pushes in quick succession become one build of the newest commit (on the free plan at most every 15 minutes). The version running stays up until the new one works. Without connecting, you can still paste a link to any public project and fetch the newest code with a button. A project without a Dockerfile gets one written for it. See [deploy from GitHub](/docs/deploy-from-github/). ### Can I host a Node.js, Python or Go app? Yes. Push the code to GitHub and let us build it, with your Dockerfile or one we write. Or package the app in an image that listens on a port such as 8080, push it to a public registry, and deploy it from the dashboard. ### Can I host a static website? Yes, inside a small web server image such as `nginxinc/nginx-unprivileged`, which runs without root and listens on port 8080. Put your built files into the image and deploy it like any other. ### Does blitz.cloud support serverless functions? No. blitz.cloud runs long-running containers, not functions. An app sleeps after 30 minutes without visitors and wakes when a person opens it in a browser. On Pro you can keep it awake so there is no wait at all. ### Can I run a project with several services, like a docker-compose setup? Yes. A project whose compose file describes a web front end, an API and a worker goes online as one app with one address. The API can answer at `/api`, the worker runs in the background, and a step like database migrations can run before each new version. Each part that keeps running counts as one of your plan's apps. For a monorepo you can also build just one folder, like `apps/web`. See [deploy from GitHub](/docs/deploy-from-github/). ### What happens when a build fails? The version that's running stays online. The app page says in one sentence what went wrong and lists the steps that fix it, each with a button: add a missing key, set up a database, use another Dockerfile. What blitz.cloud can fix safely, it fixes by itself. ### A message says the problem is on our side. Do I need to do anything? No. When a build fails because of us, for example because we ran out of room to store it, the app page says so and we build it again by itself. The version that's running stays online. If it still hasn't gone through later that day, tell us with "Give feedback" in the dashboard. ### Can I go back to an earlier version? Yes. The Activity tab lists everything that happened to an app, and "Put this version back" works on the last 10 versions that went live. ### How do I delete an app? Open the app, go to its Settings tab and use "Delete this app". You type the app's name to confirm. If it has a database, you choose whether to keep it. The app's files on disk are deleted, and that can't be undone. ### Can I run tasks on a schedule, like a cron job? There's no built-in scheduler yet. You can run your own: a small project from GitHub with a scheduler inside, switched to "Runs in the background". Background apps never sleep, so the schedule keeps running. On the free plan a background app stops after 2 days with no sign-in, no deploy and no visit to the dashboard, with an email one day before. Apps like n8n that run their own schedules only do so while they are awake, which on the free plan means within 30 minutes of the last visit. See [bots and background workers](/docs/deploy-from-github/). ### Is there a command-line tool? Not yet. Besides the dashboard, scripts and AI assistants can manage your apps through our MCP server, using an API key from the dashboard. See [connect an AI assistant](/docs/ai-assistants/). ### How do I know my app is up? Each app's Overview shows how often it answered this week, from a check once a minute, next to its requests and the data it served. You also get an email when a deploy fails or we have to stop an app. You choose which emails you want under Settings > Notifications. ### Can an app be private? Yes. Connect Tailscale by signing in, upload a WireGuard config, or add a device in the dashboard and scan its QR code with the WireGuard app. Then switch the app to private. It keeps its address and HTTPS but only opens on your own devices. See [private apps](/docs/private-networks/). ### Can I connect an AI assistant like Claude? Yes. blitz.cloud has an MCP server, so Claude, ChatGPT, Cursor, VS Code and other MCP clients can deploy and manage your apps. Most of them sign in with your blitz.cloud account; scripts can use an API key from the dashboard. See [connect an AI assistant](/docs/ai-assistants/). ## Databases and backups ### Which databases does blitz.cloud offer? PostgreSQL 17, MariaDB 11.4 and Redis, served by Valkey 8. MongoDB is not offered. See [databases](/docs/databases/). ### Can I connect to my database from my computer? No. Databases have no public address and only accept connections from apps in your own account. ### Are my databases backed up? Yes. Every running database is copied off our servers every night, and the free plan keeps 7 nights. PostgreSQL and MariaDB can be restored with one button. See [backups](/docs/backups/). ### Are my app's files backed up? [On Pro](/pricing/#everything-in-each-plan), yes. Every night the files your app keeps on disk are copied off our servers, and 30 nights are kept. You put one back from the app's Settings tab, and the restore can be undone. On the free plan only databases are copied, so keep your own copy of anything important. ### Is there a file manager for my app's files? Not yet. An app keeps its files in its kept folders, and you work with them through the app itself, like uploads in Ghost or WordPress. One app can't see another app's files, so a file manager app from the store can't open them either. If you need files out, write to hallo@blitzworks.io and we help. See [environment variables and files](/docs/settings-and-files/). ## Addresses and domains ### Do I get HTTPS? Yes. Every address and every app subdomain gets HTTPS from certificates that are issued and renewed automatically. ### Can I use my own domain? Yes, [on Pro](/pricing/#you-want-your-own-domain). Connect a domain you own to any app, with HTTPS, in three steps on the Domains page. On the free plan every app gets a subdomain under your address, like `blog.lena.blitz.cloud`, and you can add your own DNS records under that address. ### Can I change my address? Yes, once every 14 days. Your apps move to the new name, and for 14 days the old name sends visitors on to the new one. See [addresses and HTTPS](/docs/addresses-and-https/). ## Data and privacy ### Where is my data stored? In a data centre in the European Union. Today that is one region, and more regions in Europe are planned. Database backups are stored separately, also in the EU. See [data and GDPR](/eu-data/). ### Is blitz.cloud GDPR compliant? blitz.cloud is operated by a German company, keeps your apps and data in the EU and uses no US cloud provider for hosting. Requests to blitz.cloud addresses pass through Cloudflare, emails are sent through Google Workspace, and some build steps use Anthropic's Claude; what each of them sees is listed under [data and GDPR](/eu-data/). The [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) is a PDF you can download once you are signed in. ### Can hosted apps run as root or access the server? An app may run as root inside its own gVisor sandbox if its image asks for that, but it never gets access to the server. gVisor stands between the app and the server's kernel, privileged containers are refused, and network rules between accounts block everything by default. ### How do I delete my account? In Settings, under Delete account. The page lists what goes before you confirm. If you have Pro, it ends with the account and you aren't charged again. ### How do I move my apps away from blitz.cloud? Your code stays on GitHub and your images on their registry. "Download my data" in Settings gives you one file with your apps, their settings, databases, domains and history. The contents of your databases and your apps' files aren't in it yet, so write to hallo@blitzworks.io and we help you get them out. --- # blitz.cloud vs DigitalOcean App Platform: free containers and EU hosting URL: https://blitz.cloud/compare/digitalocean-app-platform/ Updated: 2026-09-26 DigitalOcean App Platform against blitz.cloud on free containers, payment method, EU regions, Docker images and managed databases, checked 14 September 2026. DigitalOcean App Platform is the better choice when you're ready to pay from the first container and want more database engines and a large provider with droplets, storage and networking in the same account. blitz.cloud fits when you want to run containers and a database for free in the EU. On App Platform the free tier covers three static sites only, with no free containers, and sign-up needs a payment method. ## At a glance | | blitz.cloud | DigitalOcean App Platform | |---|---|---| | Company | BlitzWorks UG, Regensburg, Germany. No US parent | DigitalOcean, LLC, Colorado, US | | EU regions | One region in the EU today, more planned | Amsterdam, Frankfurt (plus London) | | Free tier | 5 apps, 512 MB memory, 10 GB storage, one database. Apps sleep after 30 minutes without visitors and wake on the next one. No expiry, no card | 3 static sites, no free containers, 1 GiB transfer per app. A payment method is required at sign-up | | Cheapest paid plan | Pro, 7 EUR a month including VAT | Container $5 a month (1 vCPU, 512 MiB). Dev database $7 a month (Postgres only) | | An app that stays awake, with a database | Pro, 7 EUR a month for your whole account, up to 5 databases | $12 a month: container $5 plus dev database $7 (checked 14 September 2026) | | Run a finished Docker image | Yes, public Docker Hub images, amd64 | Yes, from DigitalOcean's registry, Docker Hub and GHCR. Automatic redeploy only from DigitalOcean's registry | | Git push deploys | Yes, after you connect GitHub, private repositories included | Yes | | Managed databases | PostgreSQL 17, MariaDB 11.4, Redis (Valkey 8), with nightly backups | PostgreSQL, MySQL, MongoDB, Valkey, Kafka, OpenSearch from $15 a month. None free | | Custom domains and HTTPS on free | HTTPS on your blitz.cloud subdomains. Custom domains on Pro | Yes | ## Where DigitalOcean is the better choice DigitalOcean is a full cloud. When App Platform stops being enough, droplets, Kubernetes, object storage and load balancers are in the same account and on the same bill. Its managed databases cover more engines, including MySQL, MongoDB and Kafka. App Platform deploys from git, pulls images from GHCR as well as Docker Hub, and custom domains work on every tier. The company has run production workloads for a long time and publishes detailed documentation for all of it. ## Where blitz.cloud fits better - You want to run a container without paying for it. App Platform's free tier doesn't include containers. - You don't want to enter a payment method to try something. - You want a database included rather than starting at $7 or $15 a month. - You prefer a German operator and your data in the EU. ## Moving from DigitalOcean App Platform to blitz.cloud If your app runs from an image on Docker Hub, deploy the same image on blitz.cloud, provided it's public, built for amd64 and listens on a port such as 8080. Images in DigitalOcean's own registry need to be pushed to Docker Hub first. For a Postgres or MySQL database, create a PostgreSQL or MariaDB database on blitz.cloud and import a dump. See [deploy a Docker image](/docs/deploy-docker-image/) and [databases](/docs/databases/). If App Platform builds your app from GitHub, connect GitHub on blitz.cloud and pick the same repository. blitz.cloud uses your Dockerfile or writes one, and puts every push to the branch online. Images from DigitalOcean's registry can also go to another public registry, such as ghcr.io, instead of Docker Hub. See [deploy a GitHub project](/docs/deploy-from-github/). ## Sources - https://www.digitalocean.com/legal/terms-of-service-agreement - https://docs.digitalocean.com/products/app-platform/details/availability/ - https://www.digitalocean.com/pricing/app-platform - https://docs.digitalocean.com/support/why-do-i-need-to-enter-a-payment-method/ - https://docs.digitalocean.com/products/app-platform/how-to/deploy-from-container-images/ - https://www.digitalocean.com/products/managed-databases Facts checked on 14 September 2026. Prices and plans change; tell us at hallo@blitzworks.io if something here is out of date. --- # Self-host a password manager with Vaultwarden URL: https://blitz.cloud/guides/self-host-password-manager/ Updated: 2026-10-14 Run Vaultwarden, the Bitwarden-compatible password manager, on blitz.cloud in the EU with one click. Setup, locking down signups, clients, and backups. You can self-host a password manager on blitz.cloud by installing Vaultwarden from the App Store. It takes one click: blitz.cloud sets the port, the address and an admin token for you, gives it 1 GB of space for its data, and puts it online with HTTPS. Vaultwarden speaks the Bitwarden protocol, so the official Bitwarden apps and browser extensions work with it. On the free plan there is one thing you have to do yourself, and it is important: keep your own backup, because only Pro copies app files. ## Install it 1. In the [dashboard](https://dashboard.blitz.cloud/), open the App Store and pick Vaultwarden, or click Host something new and choose "A ready-made app". 2. What this app needs says it keeps your files between restarts, using part of your plan's space. It needs no database: Vaultwarden keeps everything in a SQLite file in its `/data` folder. 3. Give it an address, for example `vault`, and click Put it online. Your vault is then at `https://vault.yourname.blitz.cloud`. The App Store entry already sets `DOMAIN` to that address and moves Vaultwarden from port 80 to 8080, since apps on blitz.cloud don't run as root. ## Create your account, then close the door Open the address and create your account. Pick a long master password; nobody, including us, can reset it. Vaultwarden lets anyone who finds the page register, and your address is public. Once you and your family have accounts, turn that off: 1. Open the app in the dashboard and go to the Environment tab. 2. Add `SIGNUPS_ALLOWED` with the value `false`. 3. Restart the app. Settings reach the app when it restarts. There is a stricter option. Make Vaultwarden a private app: connect Tailscale or WireGuard on blitz.cloud, and the vault keeps its address and HTTPS but only opens on your own devices in that network. The Bitwarden apps work the same way on those devices. Private apps never go to sleep. See [private apps](/docs/private-networks/). To add someone later, use the admin page at `https://vault.yourname.blitz.cloud/admin`. The token for it, `ADMIN_TOKEN`, was generated when you installed the app. It is on the Environment tab, masked until you click Show. ## Connect the Bitwarden apps In any Bitwarden client, before logging in, choose the self-hosted option and enter your address as the server URL: ```text https://vault.yourname.blitz.cloud ``` This works in the browser extensions, the desktop apps and the iOS and Android apps. ## Backups: do this part On Pro, blitz.cloud copies `/data` off-site every night and keeps 30 nights, so your vault can be put back from the app's Settings tab. On the free plan only databases are copied, not the files apps keep in their folders. Vaultwarden's data is a file in `/data`, so there it is not in any backup. If the disk it lives on were lost, your vault would be gone. [Backups](/docs/settings-and-files/#backups) in the docs says the same thing. Either way, an export of your own doesn't hurt. The Bitwarden clients keep a copy of the vault on each logged-in device, which helps, but it is not a backup. Export one: 1. Open the web vault at your address. 2. Go to Tools, then Export vault. 3. Choose the encrypted JSON format with a password you'll remember, and store the file somewhere that isn't blitz.cloud. Do it after you add anything important, or set a monthly reminder. If that sounds like too much for a password manager, you're right to hesitate, and [Pro](/pricing/) or a hosted Bitwarden account may suit you better. ## Limits worth knowing Email doesn't work out of the box. blitz.cloud blocks the usual outgoing mail ports 25, 465 and 587 for every app, so Vaultwarden can't send invitation or verification mails through a mail server on those ports. If your mail provider accepts SMTP on port 2525, set Vaultwarden's `SMTP_*` settings on the Environment tab to use it. Vaultwarden uses little memory. It runs in the small size, 128 MB reserved and up to 512 MB, which is plenty for a family. Updates come overnight. With automatic updates on, blitz.cloud checks every night around 4:00 UTC whether a newer Vaultwarden is out for the version the App Store installed, and puts it online. If the new version doesn't start within ten minutes, the one before comes back, and the app's Activity tab says so. --- # Addresses, subdomains and HTTPS on blitz.cloud URL: https://blitz.cloud/docs/addresses-and-https/ Updated: 2026-10-11 How your blitz.cloud address and app subdomains work, the naming and rename rules, automatic HTTPS, your own DNS records, and connecting a domain you own. Every blitz.cloud account gets one free main address, `.blitz.cloud`, and each app gets a subdomain under it, like `blog..blitz.cloud`. HTTPS is automatic: certificates for your address and all its subdomains are set up when you claim the address and renewed without you doing anything. You can add your own DNS records under your address. Connecting a domain you own is part of Pro, for 7 EUR per month. ## Your main address You claim it once, during onboarding. | Rule | Value | |---|---| | Length | 3 to 30 characters | | Allowed characters | `a-z`, `0-9` and `-` | | Hyphens | Not at the start or end, never two in a row | | Reserved | Platform, mail and DNS words, brand names and some profanity | | Per account | One | The field checks availability as you type. ## Subdomains for apps Each app lives on its own subdomain: `..blitz.cloud`. You can have as many as you have apps, and one app can use the main address itself instead. Subdomain names are 1 to 30 characters: lowercase letters, digits and hyphens, not starting or ending with a hyphen and never two in a row. A short list is reserved because we may serve something there for you later or because it would look official: `www`, `api`, `mcp`, `admin`, `login`, `auth`, `status`, `mail`, `db`, `database` and a few more. The dashboard tells you when you pick one. You can rename or move an app's subdomain on the app page. The old one stops leading to the app right away. A subdomain with no app on it, like one you just freed or whose app you deleted, shows a short page that says "Nothing here yet". ## Renaming your main address You can rename your main address at most once every 14 days, counted from when you claimed it or last renamed it. So the earliest first rename is 14 days after signup. When you rename: - Your apps move to the new name automatically. A certificate for the new name is ordered at the same time and, like the first one, takes a little while to be ready. - For 14 days the old name sends visitors to the same page under the new one, so links people saved keep working. `blog.oldname.blitz.cloud/post/1` goes to `blog.newname.blitz.cloud/post/1`. - Nobody else can claim the old name in those 14 days. After that it stops answering and is free again. - App settings that contain the old address, like Ghost's `url`, are changed to the new one, and those apps restart to pick it up. ## HTTPS and certificates Your address and every subdomain under it get certificates when you claim the address, and they renew before they expire. - All HTTP requests are redirected to HTTPS. - Getting the first certificate takes a few minutes after you claim the address. Until it is ready, an app's page says the secure connection is still being set up, and offers Visit once browsers will open it. - You don't upload or configure anything. There's also no way to bring your own certificate. ## Custom domains You can connect a domain you own, like `www.example.com`, to any of your apps. It's part of the Pro plan at 7 EUR per month ([what Pro includes](/pricing/#you-want-your-own-domain)), so the free plan can't use it. On the free plan, a common workaround is a redirect from your own domain to the blitz.cloud address at your DNS provider or registrar. On Pro, the Domains page walks you through a checklist of three steps, with the time each one usually takes. Only the step that needs you is open, and each record comes with its value ready to copy: 1. Show it's yours: a TXT record at `_blitz-verify.`. 2. Point it at blitz.cloud: a CNAME from your domain to `edge.blitz.cloud`. A bare domain like `example.com` needs the same CNAME on `@`. Many providers allow that and call it ALIAS, ANAME or CNAME flattening. If yours doesn't, connect `www.example.com` and forward the bare domain to it at your provider. 3. Secure it: once the name points at us, we get a certificate for it, usually within a few minutes. Until then, browsers show a warning at your domain. From then on HTTP redirects to HTTPS. The page reads your domain's nameservers to see which DNS provider runs it, and names the fields the way that provider does. Record names are shown the way most providers want them, like `_blitz-verify.www`, with the full name underneath. If your provider added the domain a second time, as in `www.example.com.example.com`, the check says so. We check the DNS every minute, and there's a "Check now" button for when you've just saved a record. If your domain is on Cloudflare, set the record to DNS only (the grey cloud), or we see Cloudflare's addresses instead of yours. Once a domain is connected, you can make it the app's main address: visitors to its blitz.cloud address are then sent to your domain, and links the app writes use it too. If Pro ends, your own domains stop leading to your apps after the 14 days of grace, and the apps stay reachable at their blitz.cloud addresses. Taking Pro again brings the domains back. ## Search engines Apps on the free plan ask search engines not to list them: their blitz.cloud address answers with an `X-Robots-Tag: noindex` header. Apps of a Pro or Power account, and any app you made a Pro app (2 EUR a month), don't send it, so Google and other search engines can list them. The same goes for a domain you own on such an app. If your app sends an `X-Robots-Tag` of its own, we leave it as it is. To see what an app sends: `curl -sI https://..blitz.cloud | grep -i x-robots-tag`. ## When the app can't answer When nothing is running behind an address, visitors see our page instead, and it says why: the app is asleep and waking up, paused, starting, building, or crashed. A page for a paused app says who paused it. When the app itself answers with an error, like its own 500 or 503, the visitor gets that answer as the app sent it. If you'd rather show our page for those too, switch on "Our page for its errors" in the app's Settings tab. ## Advanced DNS records You can add A, AAAA, CNAME, TXT and MX records under your address on the Domains page, for example an MX record to receive mail at your blitz.cloud address, or a TXT record a service asks you to add to prove you own it. Most people never need this. Up to 10 records per account. A few names are kept for your apps. You can't point your address itself, or a subdomain an app is using, somewhere else with an A, AAAA or CNAME record, because that would take the app offline. TXT and MX records are fine anywhere. The dashboard says which app is in the way when it refuses a record. --- # EU PaaS alternatives: blitz.cloud, Scaleway, Clever Cloud, Koyeb, Northflank URL: https://blitz.cloud/compare/eu-paas-alternatives/ Updated: 2026-10-08 blitz.cloud, Scaleway, Clever Cloud, Koyeb and Northflank compared on EU company location, free tier and card requirement, checked 8 October 2026. If you want a platform run by a European company, Scaleway and Clever Cloud (both France) are the established options with many products and paid databases, Northflank (UK) has a free sandbox with a database but asks for a card, and Koyeb no longer offers a free plan to new sign-ups. blitz.cloud is the smallest of these: one data centre in the EU, a free plan without a card that includes a database, and fewer features than the others. Pick by what you need today, not by the flag. If you're leaving Heroku or Render, their own pages compare them line by line: [Heroku](/compare/heroku/), [Render](/compare/render/), [Railway](/compare/railway/). ## At a glance | | blitz.cloud | Scaleway Serverless Containers | Clever Cloud | Koyeb | Northflank | |---|---|---|---|---|---| | Company | BlitzWorks UG, Regensburg, Germany | Scaleway SAS, Paris, France | Nantes, France | Paris, owned by Mistral AI since 17 February 2026 | Northflank Ltd, London, UK | | US parent | No | No | No | No | No US parent found | | EU regions | One region in the EU today, more planned | Paris, Amsterdam, Warsaw, Milan | Paris, Roubaix, Gravelines, Warsaw (plus regions outside Europe) | Frankfurt, Paris (plus regions outside Europe) | europe-west, Frankfurt, Netherlands, Zurich | | Free tier | 5 apps, 512 MB memory, 10 GB storage, one database. Apps sleep after 30 minutes without visitors. No card | Monthly free allowance, scales to zero. Credit card and ID check required | Sign-up credits, no card. No permanent free app tier | Removed for new sign-ups | Developer Sandbox: 2 always-on services, 1 database. Card required | | Cheapest paid | Pro, 7 EUR a month including VAT | Usage-based: 0.20 EUR per 100k GB-s, 1.00 EUR per 100k vCPU-s | App "pico" about 4.50 EUR per 30 days | Pro, $29 a month plus compute | Pay as you go, smallest size $2.70 a month | | Run a finished Docker image | Yes, public images from Docker Hub, ghcr.io, Quay and other registries, amd64 | Yes, public external registries | Via git push with a Dockerfile | Yes | Yes | | Git push deploys | Yes, after you connect GitHub | No built-in, CI only | Yes | Yes | Yes | | Managed databases | PostgreSQL 17, MariaDB 11.4, Redis (Valkey 8), one free | PostgreSQL, MySQL, Redis, MongoDB, Serverless SQL. No free tier | PostgreSQL, MySQL, MongoDB, Redis and more. Free DEV databases have no backups since 1 October 2025 | Postgres 14-17 | PostgreSQL, MySQL, MongoDB, Redis and more, one free in the sandbox | ## Scaleway Serverless Containers Scaleway runs containers that scale to zero and bills by the second, which is cheap for bursty traffic. Every region is in the EU and the company is French. It fits if you're comfortable with a card on file and a larger cloud around your containers. Private external registries aren't supported, and there's no built-in git deploy. ## Clever Cloud Clever Cloud is the veteran EU PaaS: git push deploys, many runtimes, and a long list of managed databases. There's no permanent free app tier, and its free DEV databases have had no backups since October 2025. Note that its pricing page lists Oracle Cloud, a US company, among its infrastructure providers. ## Koyeb Koyeb has git and Docker deploys and Postgres, and since February 2026 it belongs to Mistral AI. New sign-ups can't get the free Starter plan anymore; the cheapest plan is Pro at $29 a month plus compute. It fits teams that want a French-owned platform with serverless scaling and are ready to pay. ## Northflank Northflank is a capable platform with git and Docker deploys, many database engines and the option to run inside your own cloud account. Its free sandbox gives two services that don't sleep and one database, but asks for a card. The company is British, so it's European but outside the EU. ## sota.io sota.io is a Berlin company with a platform in Falkenstein, Germany. It's invite-only early access for now and hasn't published pricing, so we left it out of the table. ## Where blitz.cloud fits blitz.cloud makes sense if you want to start without a card, keep a few apps and a database running for free in the EU, and deploy from GitHub or from a public image. If you need private images, several regions or a larger company behind the service, one of the platforms above fits better. See [what's live](/whats-live/) for what blitz.cloud does and doesn't do. ## Sources - https://www.scaleway.com/en/legal-notice/ - https://www.scaleway.com/en/developers/api/serverless-containers - https://www.scaleway.com/en/serverless-containers/ - https://www.scaleway.com/en/pricing/serverless/ - https://www.scaleway.com/en/docs/billing/faq/ - https://www.scaleway.com/en/docs/serverless-containers/how-to/deploy-container/ - https://www.scaleway.com/en/pricing/managed-databases/ - https://www.clever.cloud/developers/doc/find-help/faq/ - https://www.clever.cloud/pricing/ - https://api.clever-cloud.com/v4/billing/price-system?zone_id=par¤cy=EUR - https://www.clever.cloud/developers/doc/deploy/applications/docker/ - https://www.clever.cloud/developers/changelog/2025/09-01-backups-dev-db/ - https://techcrunch.com/2026/02/17/mistral-ai-buys-koyeb-in-first-acquisition-to-back-its-cloud-ambitions/ - https://www.koyeb.com/docs/reference/regions - https://www.koyeb.com/docs/reference/instances - https://www.koyeb.com/blog/koyeb-is-joining-mistral-ai-to-build-the-future-of-ai-infrastructure - https://www.koyeb.com/docs/faqs/pricing - https://www.koyeb.com/pricing - https://www.koyeb.com/docs/databases - https://northflank.com/legal/terms - https://northflank.com/cloud/northflank/regions - https://northflank.com/pricing - https://northflank.com/docs/v1/application/databases-and-persistence/deploy-a-database - https://sota.io/legal - https://sota.io/ - https://sota.io/pricing Facts checked on 8 October 2026. Prices and plans change; tell us at hallo@blitzworks.io if something here is out of date. --- # Self-host n8n for workflow automation URL: https://blitz.cloud/guides/self-host-n8n/ Updated: 2026-09-26 Install n8n on blitz.cloud in one click, hosted in the EU with HTTPS and public webhooks. Memory, encryption key, email, and how to keep your workflows safe. To self-host n8n on blitz.cloud, install it from the App Store: pick n8n, choose an address and click Put it online. blitz.cloud sets up the HTTPS address, the webhook URL, an encryption key and 1 GB of space for n8n's data, and gives it more memory than a typical app because n8n needs it. On the free plan n8n sleeps after 30 minutes without a visit, and schedule triggers don't fire while it sleeps. Webhooks don't wake it either: while it sleeps, a webhook call gets an answer that n8n is asleep and never reaches your workflow. Opening n8n in your browser wakes it. On Pro you can keep n8n awake, so schedules fire on time and every webhook is answered straight away. ## Install it 1. In the [dashboard](https://dashboard.blitz.cloud/), open the App Store and pick n8n, or click Host something new and choose "A ready-made app". 2. Give it an address such as `n8n` and click Put it online. 3. Open `https://n8n.yourname.blitz.cloud` and create the owner account. The first person to open a fresh n8n becomes its owner, so do this right after the install. What the App Store entry sets for you: | Setting | Value | | --- | --- | | `N8N_HOST` | your app's address | | `N8N_PROTOCOL` | `https` | | `WEBHOOK_URL` | `https://n8n.yourname.blitz.cloud` | | `N8N_SECURE_COOKIE` | `true` | | `N8N_ENCRYPTION_KEY` | a random key generated at install | You can see and change all of them on the app's Environment tab. ## Why n8n gets the medium size We ran n8n in the small size first. Its editor looked healthy for a minute and then died with "JavaScript heap out of memory". So the App Store installs it in the medium size: 256 MB of memory reserved from your plan's 512 MB, with room to grow to 1 GB, and up to one CPU. That handles a personal set of workflows. Workflows that load big files or thousands of items at once can still hit the ceiling. ## Webhooks Webhook nodes get public URLs under your address, for example: ```text https://n8n.yourname.blitz.cloud/webhook/ ``` They work from GitHub, Stripe, a form service or anything else on the internet, because `WEBHOOK_URL` already points at the right place. ## Keep a copy of the encryption key n8n encrypts the credentials you save (API keys, OAuth tokens) with `N8N_ENCRYPTION_KEY`. Open the Environment tab, click Show next to it and store the value in your password manager. Without it, a copy of your n8n data is useless, because the credentials in it can't be decrypted. ## Backups: on Pro, not on the free plan n8n stores workflows, credentials and execution history in a SQLite file in `/home/node/.n8n`. On the free plan blitz.cloud backs up databases every night, but not files kept by apps, so that folder is in no backup. On Pro the files apps keep are copied every night and kept for 30 nights, and you can put them back from the app's Settings tab. Either way, export your workflows regularly. In the n8n editor, open a workflow and use Download from its menu to save it as JSON. Keep the files in a Git repository and you get history for free. Credentials don't export in readable form, so write down which accounts each workflow uses. ## Sending email The Send Email node won't reach a mail server on the standard ports: blitz.cloud blocks outgoing ports 25, 465 and 587 for every app, to keep the platform from being used for spam. Some mail providers also accept SMTP on port 2525, which is not blocked. The other way is a provider with an HTTP API, called from the HTTP Request node or the provider's own n8n node. ## When n8n Cloud is the better choice If you need many workflows running in parallel, several team members with roles, or queue mode with workers, a self-hosted n8n in 1 GB of memory is the wrong tool. For one person or a small team automating their own chores, it's a good fit, and the data stays in the EU. --- # App status, logs and troubleshooting on blitz.cloud URL: https://blitz.cloud/docs/app-status-and-logs/ Updated: 2026-09-26 What an app's status means on blitz.cloud, what the five tabs show, how to restore an earlier version, and how to fix why an app won't start. Every app on blitz.cloud shows one status: Starting, Online, Needs attention, or Paused. When something is wrong, the app page explains it in one sentence and shows the last lines the app printed. Most problems with Docker images come from three things: the image needs root, it is built only for arm64, or it listens on a different port than the one chosen. ## The app's page Every app has a page with five tabs: - Overview has the status, what to do when something is wrong, and this week's numbers. While a new version builds, you watch the build here step by step. - Activity lists everything that happened to the app, with earlier versions to put back. - Logs shows what the app prints, live. - Environment holds the app's environment variables. - Settings has the address, domains, port, where new versions come from, and switches like "Our page for its errors". To rename an app, click its name at the top of the page. Only the name changes. The address stays the same. ## Statuses | Status | What it means | |---|---| | Building | A new version is being built. A version that is already running stays online meanwhile. | | Starting | The container is being pulled or started, or it hasn't passed its readiness check yet. | | Online | The app is running and answering on its port. | | Sleeping | Nobody visited for 30 minutes. The next visitor wakes it in about ten seconds. See [sleeping apps](/docs/limits/#sleeping-apps). | | Updating | An overnight update is on its way. The version before keeps running until the new one answers. | | Needs attention | The app keeps crashing, has restarted itself 3 or more times while still answering, can't be scheduled, or can't be downloaded. | | Stopped | The app crashed again and again, so we stopped it after 15 restarts. Nothing is lost. "Start it again" on its page starts it, and so does a new version. | | Paused | You paused it, or we did, and the page says which. The address, settings and files are kept, and its memory goes back to your pool. An app we paused says why and asks you to write to us. | ## Uptime and traffic The Overview shows how many requests the app answered this week and how much data it served. For every app that is awake we check once a minute whether it answers, and the Overview shows the result, like "99.8% this week" or "Down 12 minutes this week". A sleeping or paused app is not counted as down, and a check never keeps an app awake. ## When a build or start fails When a build or a start fails and our own retries are used up, the Overview says what went wrong in one sentence and lists the steps that fix it, each with its own button: paste a key, set up a database, use another Dockerfile, or let us write one. What blitz.cloud can do safely, it does by itself. It never makes up a key or an address. More on this in [deploy a GitHub project](/docs/deploy-from-github/). ## Messages you might see "The app starts and then stops again straight away." The container starts and exits in a loop. The last log lines are right under the message and usually say why: a missing environment variable, a database it can't reach, or a permission error when writing a file. "This app wants to run as root, the machine's administrator." The image expects root, and the app was set up before root was allowed. Restart it and it starts as root, inside its own gVisor sandbox. An app built from your code does the same after its next build. "We couldn't download this app. Check the name is spelled right and that it is public." The image name or tag is wrong, or the repository is private. Private images aren't supported yet. "Your plan's memory is fully used, so this app has nowhere to start." Pause or delete another app, or delete a database you don't use. See [limits](/docs/limits/). "There is no room on blitz.cloud for this app right now." The cluster itself is full. We get alerted and add servers; the app starts on its own once there is room. An app that needs a database but has none connected says so and names the engine. Give it one from the Databases page. ## How long starting takes Starting is usually a matter of a few minutes, and the first start is the slowest. Here is what we measured in September 2026: - An app from the App Store: half of the installs were online within about four minutes. Small apps like Memos need about a minute. Bigger ones like Nextcloud set themselves up on their first start and take several minutes. Later starts skip that setup. - A GitHub project builds first. Half of all builds finish in about two minutes, and nine in ten within about six. A build sometimes waits a few minutes for a build server of its own before it begins. - A Docker image is downloaded first. A small image takes seconds, a large one up to about a minute. - A sleeping app wakes for its next visitor in a few seconds. - An app whose files nobody used for 7 days gets them back first, which adds a minute or two. The longest waits come from "There is no room on blitz.cloud for this app right now". We add a server when that happens and the app starts on its own, usually within a few minutes. There is nothing to do on your side. What helps: - Give the first start at least five minutes before you change anything. Deleting the app and installing it again starts over from the beginning and makes the wait longer. - Look at the Logs tab. When the app is printing lines, it is starting and just not ready yet. - For your own image or project, keep the image small and open the app's port as early as you can. An app counts as Online once it answers on its port, so a long migration before that shows as Starting until it is done. - An app that people should never wait for can stay awake. "Keep it awake" on the Settings tab is part of Pro. ## The app stays on "Starting" forever This almost always means the container runs, but nothing answers on the chosen port. There is no timeout that turns this into an error, so it just keeps waiting. Check the logs for the port the app actually listens on, then enter it under Port on the app's Settings tab. The app restarts once. Also check that the app listens on all interfaces (`0.0.0.0`), not only on `localhost` or `127.0.0.1`. Traffic reaches the container from outside it. ## arm64-only images Our servers are x86 (amd64). An image published only for arm64, which is common for images built on an Apple Silicon Mac without `--platform`, will stop on startup. Rebuild with: ```bash docker buildx build --platform linux/amd64 -t yourname/yourapp:1.0 --push . ``` ## Live logs The Logs tab streams output from the app as it happens, starting with the last 500 lines. You don't configure anything. - Each account can have 2 log streams open at a time. - A stream closes after 5 minutes without new output or after 30 minutes in total. The output says so, and one button reconnects. ## Restart, pause, resume and delete - Restart starts the app fresh. Use it after changing environment variables. - Pause stops the app but keeps its address, settings and files. Its memory goes back to your plan. - Resume starts it again. It counts against your limits like a new app, so it only works if there is room in your plan. - Delete asks you to type the app's name. If it has a database, you choose whether to keep or delete it. The app's files on disk are deleted. ## Activity and earlier versions The Activity tab lists everything that happened to the app, newest first and grouped by day: builds, versions going live, restarts, sleeps and wakes, stops, setting changes and domains. The version running now is pinned on top. The filters Everything, Versions, Problems and Changes narrow the list. Changes shows every change to how the app is built or started, with who made it and why. Settings appear by name, never with their values. Each of the last 10 versions that went live has a "Put this version back" button. The build log of a version opens right there. ## What visitors see when the app isn't running When no app is running behind the address, visitors see a blitz.cloud page that says why: the app is asleep, paused (and by whom), starting, stopped after crashing, or building. A sleeping app rarely gets that far: the first visit waits for it to wake up and then gets the app's own answer, forms included. The waking page only shows if waking takes more than about five seconds. Error pages the app sends itself, such as its own 500 or 503, reach visitors exactly as the app wrote them. To show our page for those too, switch on "Our page for its errors" on the app's Settings tab. Leave it off for an API, because programs that call it expect its own answers. ## Mail when something happens We send you a mail when a new version fails or goes online, when we stop an app, when a restore finishes and when an overnight update ran. Each of these can be switched off under Settings > Notifications, or with one click in the mail. Mails about your account, security and billing are always sent. ## Automatic restarts Apps from the App Store have a health check that knows what "working" means for that app, and are restarted if they stop answering. Apps from your own Docker image are not restarted when they stop answering, only when they crash. An app that crashes is started again each time, with longer waits in between. After 15 restarts we stop it, mark it Stopped and send you a mail. ## Is it your app or blitz.cloud? If several of your apps stop answering at once, or the dashboard won't load, look at [status.blitz.cloud](https://status.blitz.cloud/) before you change anything. It says whether a part of blitz.cloud has a problem right now, and it runs on its own server outside the platform, so it still answers when blitz.cloud doesn't. Still stuck? Write to hallo@blitzworks.io with your app's address. --- # Is there free Docker hosting in the EU? URL: https://blitz.cloud/guides/free-docker-hosting-eu/ Updated: 2026-09-30 Yes, free Docker hosting in the EU with no credit card. blitz.cloud's free plan: 5 apps, 512 MB memory, 10 GB storage, one database. Yes. blitz.cloud has a free plan that runs a public Docker image online with no credit card and no time limit. You get 5 apps, 512 MB memory, and 10 GB storage, with one managed database and automatic HTTPS. Sign up, search Docker Hub for an image, pick a version and a name, and it goes online under an HTTPS address like `myapp.yourname.blitz.cloud`. ## What you get free Your apps sleep after 30 minutes without visitors and wake on the next visit. The free plan includes one database that is backed up every night. No credit card is needed to start, and there is no time limit. Most platforms have dropped their free Docker tiers in the last year, but blitz.cloud still has one. You get 5 apps, 512 MB memory, and 10 GB storage. Apps run in the EU on hardware that multiple free accounts share safely through gVisor sandboxes. For the full dated comparison of what Render, Railway, Fly.io and Heroku offer today, see [How to deploy a Docker container for free](/guides/deploy-docker-container-free/). ## The limits The image has to be public and built for amd64 (not arm64). It needs an EXPOSE statement for the port it listens on. Free-plan apps have no file backups; only the database is backed up every night. An app at rest uses about 128 MB of memory. You cannot connect from outside to your database with a client tool like psql. More details are in [Limits](/docs/limits/). ## What's not included Custom domains come with Pro: an app on the free plan answers at `.blitz.cloud` only. Apps don't stay awake by themselves; they sleep after 30 minutes without visitors and wake up in seconds on the next visit. That is why free apps cost less to run and why that cost stays low. On Pro at 7 EUR/month you get both kept-awake apps and custom domains. Free-plan database backups are kept for 7 days. Pro keeps them for 30 days and adds automatic nightly backups of your app files too, so you can keep a longer history if something goes wrong. ## Is it really free, forever? No trial clock, no credit card to avoid a surprise charge later. It stays free as long as you use it inside the free plan's limits. There is no waiting list either. ## Why it's free Every app runs in its own gVisor sandbox so free apps can share hardware safely. That is part of why they sleep after 30 minutes without visitors: it keeps shared capacity for apps people are actually using. The same sandbox isolation means free and paid apps sit next to each other on the same servers without risk. Because the cost of running a free app is just the sleep-time baseline resource use, the free plan stays sustainable. ## Ready to go [How to deploy a Docker container for free](/guides/deploy-docker-container-free/) walks you through the steps with a real example. [Deploy a Docker image](/docs/deploy-docker-image/) has the technical details. --- # Private apps with Tailscale or WireGuard on blitz.cloud URL: https://blitz.cloud/docs/private-networks/ Updated: 2026-10-15 Make an app private on blitz.cloud so only your own devices can open it, through your Tailscale tailnet or your WireGuard network. How to connect, and what changes. A private app on blitz.cloud is off the public internet. It keeps its address, like `https://immich.lena.blitz.cloud`, but only devices on your own network can open it: your Tailscale tailnet, a WireGuard network you already run, for example on your router, or a device added straight in the dashboard, with no router of your own needed. Connect a network on the Private network page in the dashboard, then switch an app to private in its Settings tab. The free plan connects one network with as many private apps as you like, Pro up to five. ## When a private app makes sense Some apps should never face the internet: a password manager only your family uses, a photo library, an admin panel, a database tool. Making them private takes them off the internet, so nobody else can reach them to guess a login or try an exploit against them. ## Connect Tailscale 1. Open Private network in the dashboard and click Connect Tailscale. Tailscale's sign-in page opens in a new tab. 2. Sign in with your Tailscale account. The card says Connected a moment later. 3. Install Tailscale on your phone or laptop and sign in with the same account, if you haven't already. There's nothing to create in Tailscale's console and nothing to paste. Your private apps share one device on your tailnet, `blitz-`, and `http://blitz-` lists them all. You can rename that device on the Private network page. The card also says when Tailscale will ask you to sign in again, and how to switch that off for this device. ## Connect WireGuard If you already run a WireGuard server or a router with WireGuard, such as a FRITZ!Box: 1. Add a new device (a "peer") on your router or VPN server and download its config. Use it only for blitz.cloud, because two devices can't share one config. 2. On Private network, click Upload config and choose the file. blitz.cloud joins your network as that device. The config holds a private key; it is stored encrypted and used only to join your network. A config whose router can't be reached from the internet is refused when you upload it, with the reason. That happens behind carrier-grade NAT, which many home connections use, and with IPv6-only connections. Once connected, open the address shown on the card from a device in your network. It lists all your private apps. ## Without a router of your own No VPN or router with WireGuard? blitz.cloud can run the WireGuard server for you. 1. On Private network, connect the WireGuard app card, then click Add a device. 2. Scan the QR code with the WireGuard app on your phone, or download the config file for a laptop. The key is shown once; we don't keep it, so save it now. 3. Open the WireGuard app's tunnel. Your private apps are reachable from that device straight away. Only your private apps' addresses go through the tunnel, so your phone's own internet connection does not. Removing a device disconnects it within a minute; removing the last one first names which private apps become unreachable, so nothing is cut off by surprise. ## Make an app private Open the app, go to Settings and switch it to private. What changes: - The app keeps its address, with HTTPS and without a port, but it only opens on devices in your network. Bookmarks and links you already have keep working there. From anywhere else it doesn't open. - The app no longer sleeps, so it answers straight away when you open it from your network. - On WireGuard the address works the same way where your router lets it. The app also gets a fixed port on the address blitz.cloud has in your network, and that way always works. Switching it back to public opens the address to everyone again. ## Disconnect a network Disconnecting asks what should happen to the apps that depend on the network: make them public again or pause them. Nothing is deleted. ## Reach devices on your network from your apps A private app works in one direction: your devices open your apps. The [infrastructure designer](/infrastructure-designer/) adds the other one. An app such as Home Assistant can reach a device on your network, like a Hue Bridge, under a name you choose, and a device at home such as a NAS can get its own address, private by default. Devices on the network show up on the Designer page by themselves, and "Scan my network" finds the ones on your home network when you click it. For Home Assistant, [connect Home Assistant to devices at home](/docs/home-assistant-home-devices/) goes through it step by step. ## Limits | | Free | Pro | |---|---|---| | Networks you can connect | 1 | Up to 5 | | Private apps per network | As many as you like | As many as you like | You need to confirm your email address before you can connect a network. An AI assistant connected over MCP can list your networks and make an app private or public, but connecting a network stays in the dashboard, because it needs a secret or a config file. See [connect an AI assistant](/docs/ai-assistants/). --- # blitz.cloud vs PikaPods: hosted open-source apps in the EU URL: https://blitz.cloud/compare/pikapods/ Updated: 2026-10-14 PikaPods against blitz.cloud for hosted open-source apps like Nextcloud, n8n and Immich - free plan, pricing per app or per account, your own code, sources checked 14 October 2026. PikaPods and blitz.cloud both run open-source apps for you, so you don't rent a server and keep it patched yourself. PikaPods is the better choice when the app you want is only in its larger catalogue, when you want every app running around the clock for a few dollars, or when you need a US region. blitz.cloud fits when you want to start without paying or adding credit, run several apps for one account price, or put your own code next to the store apps, hosted by a German company. ## At a glance | | blitz.cloud | PikaPods | |---|---|---| | Company | BlitzWorks UG, Regensburg, Germany | Peakford Ltd, Malta (the team behind BorgBase) | | Regions | One region in the EU | EU and US locations | | How you pay | A plan for the whole account: free, or Pro at 7 EUR a month including VAT. One app can also be made a [Pro app](/pricing/) on its own | Prepaid credit, billed by the hour per app ("pod") for the CPU, memory and storage you pick, prices in USD plus VAT | | Start without paying | Free plan with 5 apps and 512 MB memory, no card, no end date. Apps sleep after 30 minutes without visitors | $5 welcome credit, no permanent free tier | | Cheapest app that runs all the time | Pro for the whole account, or one Pro app | From $1.80 a month per app at the smallest size | | Apps | 5 on free, 50 on Pro, from 96 store apps | A larger catalogue of open-source apps | | Your own code | Yes: public Docker images, and GitHub repositories that go online on every push | No, only apps from the catalogue | | Managed databases | PostgreSQL, MariaDB and Redis, with nightly backups | Set up inside the app where it needs one | | Backups | Databases every night (7 nights on free, 30 on Pro), app files every night on Pro | Daily backups, and you can download your data over SFTP | | Own domain | On Pro or a Pro app | Yes | ## Where PikaPods is the better choice PikaPods has been running hosted apps longer and lists more of them. If the app you want isn't among blitz.cloud's 96, that settles it. Its pods don't sleep: you pay by the hour for what each one uses, so a small app that has to answer at any time costs a few dollars a month. You can also give one app far more room than a blitz.cloud plan has, up to 16 GB of memory, and choose a US location. PikaPods shares revenue with the authors of the apps it hosts, which some people care about when they pick a host. ## Where blitz.cloud fits better - You want to try an app before paying anything. The free plan needs no card and no credit, and apps wake up on the next visit. - You run several apps. Pro is one price for the account, so five apps that stay awake cost 7 EUR a month, not five pods. - You want your own project next to the store apps: a Docker image, or a GitHub repository that goes online on every push. - You want the database managed for you, with nightly backups you can restore from the dashboard. - You want a German company and one EU data centre, and support in German or English. ## Moving an app from PikaPods Install the same app from the blitz.cloud [App Store](/apps/), then move its data over: download the files over SFTP from PikaPods and upload them in the app, or use the app's own export and import (Nextcloud, Vaultwarden, n8n and most others have one). Keep the PikaPods pod until the new one works. ## Sources - https://www.pikapods.com/ - https://docs.pikapods.com/ Facts checked on 14 October 2026. Prices and plans change; tell us at hallo@blitzworks.io if something here is out of date. --- # Connect Home Assistant to devices at home URL: https://blitz.cloud/docs/home-assistant-home-devices/ Updated: 2026-10-15 Run Home Assistant on blitz.cloud and let it control the Hue Bridge, Shelly plugs or MQTT broker on your home network, without opening a port on your router. Home Assistant on blitz.cloud can control devices on your home network once your home network is connected and each device is forwarded to it under a name, such as `hue-bridge`. You need a small Linux machine at home that stays on, like a Raspberry Pi. Your router stays closed, so this works behind carrier-grade NAT and DS-Lite as well. ## What you need - Home Assistant installed from the [App Store](/apps/home-assistant/). - A Linux machine on your home network that runs all the time: a Raspberry Pi, a home server, or the box Home Assistant ran on before. It connects your home network to blitz.cloud. - Your home network's range. On a FRITZ!Box it's usually `192.168.178.0/24`, on many other routers `192.168.0.0/24` or `192.168.1.0/24`. Your router's network settings show it. ## 1. Connect the hosted network Open Private network in the dashboard and connect the WireGuard app card, if you haven't already. This is the WireGuard network blitz.cloud runs for you, described in [private networks](/docs/private-networks/#without-a-router-of-your-own). If you already use Tailscale or your own WireGuard, you can use that network instead and skip to step 4 for devices that are on it directly. ## 2. Add the home machine as a device 1. On the WireGuard card, click Add a device and name it, for example `home`. 2. Enter your home network's range, such as `192.168.178.0/24`, as the range this device carries. 3. Download the config file. The key in it is shown once and we don't keep it, so save the file now. ## 3. Set up the home machine On the Linux machine, install WireGuard and start the config as a service. With the file saved as `home.conf`, on Debian, Ubuntu or Raspberry Pi OS: ```sh sudo apt install wireguard sudo cp home.conf /etc/wireguard/blitz.conf sudo systemctl enable --now wg-quick@blitz ``` The dashboard shows a few more lines under the config that let the machine pass traffic on to the other devices on your network. Run those as well. A moment later the machine shows as online on the Designer page. The machine connects out to blitz.cloud, so there's nothing to set up on your router. ## 4. Find the device Open Designer in the dashboard, select your network and click Scan my network. The scan checks your home range for the ports devices like a Hue Bridge, a NAS, a camera or an MQTT broker use and lists what answers, with the title of its web page where there is one. It runs only when you click. A device the scan doesn't find can be added by hand on the canvas with its address, for example `192.168.178.20`. ## 5. Connect Home Assistant to the device 1. On the canvas, draw a line from Home Assistant to the device. 2. Give the connection a name. Home Assistant will reach the device under this name, so keep it short: `hue-bridge`, `shelly-kitchen`, `mqtt`. 3. Choose the ports and whether each is TCP or UDP. Common ones: | Device | Ports | |---|---| | Philips Hue Bridge | TCP 80 and 443 | | Shelly | TCP 80 | | ESPHome | TCP 6053 | | MQTT broker | TCP 1883 | | Sonos | TCP 1400 | Save. The connection is ready a few seconds later. Only Home Assistant can use it; your other apps can't reach the device unless you draw a line from them too. ## 6. Add the device in Home Assistant Home Assistant normally finds devices on its own by listening for broadcasts on the local network. Those don't travel through the tunnel, so you add each integration by hand: 1. In Home Assistant, open Settings, Devices & services, and click Add integration. 2. Pick the integration, for example Philips Hue. 3. Where it asks for a host or IP address, enter the name from step 5: `hue-bridge`. For ESPHome and MQTT, also enter the port. For the Hue Bridge, press the button on the bridge when Home Assistant asks. Your lights then appear as usual. ## Limits | | Free | Pro | |---|---|---| | Device forwards | 3 | As many as you need | | Addresses for home devices | 1 | As many as you need | Home Assistant runs its automations only while it's awake. On the free plan an app sleeps after 30 minutes without visitors, so automations that should run around the clock need Home Assistant kept awake, on Pro or by making it a [Pro app](/pricing/). ## Questions ### Why doesn't Home Assistant discover my devices by itself? Discovery uses mDNS and similar broadcasts that only travel inside your home network. Home Assistant on blitz.cloud reaches a device through its forward, under the name you gave it, so you enter that name when you add the integration. ### Home Assistant can't connect to the device. What should I check? Check that the home machine shows as online on the Designer page, that the forward has the port the integration uses, and that the device answers at its address from another device at home. A device that changed its address needs the new one entered on the canvas; giving it a fixed address in your router avoids that. ### Do I need to open a port on my router? No. The home machine connects out to blitz.cloud, and everything goes through that connection. --- # Environment variables and persistent files on blitz.cloud URL: https://blitz.cloud/docs/settings-and-files/ Updated: 2026-10-03 Set encrypted environment variables for your apps on blitz.cloud and keep files across restarts with persistent storage. Limits and what isn't backed up. On blitz.cloud, environment variables are set on each app's Environment tab, stored encrypted, and applied the next time the app restarts. Files survive restarts when the app writes them to one of its kept folders. On Pro those folders are copied every night. On the free plan they are not, so keep a copy of anything you can't lose. ## Environment variables Open an app in the [dashboard](https://dashboard.blitz.cloud/) and go to Environment. You can add, change and delete variables there. - Up to 64 variables per app. - Values are hidden by default and shown one at a time when you click to reveal them. - Values are encrypted before they're stored and only decrypted on the way into the app. - You can paste a whole `.env` file instead of adding variables one by one. - A removed variable can be brought back with Undo, right after you remove it. - Changes apply on the next restart. The page says "Restart needed" until then and has a restart button next to that note. Variables that connect an app to its database are filled in by blitz.cloud and marked as such. See [databases](/docs/databases/). For App Store apps, the Environment tab starts with the settings the store entry provides, generated secrets included. ## Persistent files A container's filesystem is thrown away when it restarts. Only the app's kept folders survive. - App Store apps keep the folders their entry names, like Ghost's content folder. - Docker images keep the folders they declare with `VOLUME`, plus any the detection suggests. You can edit the list under Advanced settings in the wizard. - An app can keep up to 6 folders. - You can keep another folder later, from the app's Settings tab under Files. It's empty until the app writes something there; nothing from before is carried over. Behind the scenes, all apps in your account share one disk, and each app gets its own folder on it. An app running on blitz.cloud can't see another app's files, but you can: the Files section of each app's Settings links into FileBrowser Quantum from the App Store, which uploads, downloads and sorts what is in the kept folders of every app in your account. ## Storage reservations Each app that keeps files reserves part of your plan's storage: | App type | Reserved | |---|---| | Docker image with kept folders | 1 GB | | App Store app | What the store lists, up to 5 GB | | Database | 1 GB (Redis: 0.5 GB) | The meter in Settings shows what is reserved, not what is actually written. The free plan has 10 GB. See [limits](/docs/limits/). ## Backups Databases are copied every night on both plans. Kept folders are copied every night on Pro, and 30 nights are kept. You can put one back from the app's Settings tab, under Backups, and undo the restore if it wasn't the right night. On the free plan kept folders are not backed up. If your app stores uploads or a SQLite database on disk, download your own copies regularly, or use a managed database instead of SQLite. Deleting an app deletes its files. There is no undo. ## Exporting your data "Download my data" in Settings gives you one file with everything we hold about your account: your apps and their settings, databases, domains, builds and history. What is inside your databases is not in it, and there's no download button for that yet. The files your apps keep on disk can be downloaded through FileBrowser Quantum from the App Store. If you want to move somewhere else, write to hallo@blitzworks.io and we'll help you get your data out. --- # Host n8n free in the EU URL: https://blitz.cloud/guides/n8n-hosting-eu/ Updated: 2026-10-09 Run n8n in the EU for free, no credit card. Install it from the blitz.cloud App Store in one click and it is online in about two minutes. Yes, n8n runs free on blitz.cloud in the EU. Sign up, install it from the App Store in one click, and it is online in about two minutes with no credit card. Your workflows run in a sandbox, get a public webhook URL for free, and the app sleeps when nobody is using it so it costs almost nothing. ## What you get free n8n gets its own gVisor-isolated box, 512 MB memory, and 10 GB storage. It sleeps after 30 minutes without a visit, and you can wake it by opening it in your browser. While it sleeps, incoming webhooks get an answer that n8n is asleep and never reach your workflows. The address is a free `n8n.yourname.blitz.cloud` domain with automatic HTTPS. ## Install it 1. [Install n8n](https://dashboard.blitz.cloud/new?app=n8n&from=store) from the App Store 2. Give it an address like `n8n` and click Put it online 3. Open the address in your browser and create the owner account Or, if you are already signed in to blitz.cloud, open the dashboard, go to the App Store, pick n8n, choose an address, and click Put it online. ## What this skips n8n's own self-hosting docs list the big clouds, a droplet host, and a PaaS. All of them ask you to size a server, configure a container, or put a credit card on file first. blitz.cloud does none of that: the app installs itself and is ready to use. ## For the full picture For environment variables, backups, email limits, and how to keep n8n awake so schedules fire while you sleep, see [Self-host n8n for workflow automation](/guides/self-host-n8n/). On Pro you can keep n8n awake, so schedules fire on time and every webhook is answered straight away. --- # Self-host Ghost on blitz.cloud URL: https://blitz.cloud/guides/self-host-ghost/ Updated: 2026-10-09 Install Ghost on blitz.cloud in one click, hosted in the EU with HTTPS. Custom domain, backups, newsletter email, and moving an existing blog over. To self-host Ghost on blitz.cloud, install it from the App Store: pick Ghost, choose an address and click Put it online. blitz.cloud sets the address Ghost uses for every link it prints, puts its content in a SQLite file on 2 GB of storage, and gives it HTTPS. On the free plan Ghost sleeps after 30 minutes without a visit, and the first visit after that takes a few seconds to wake it. On Pro you can keep it awake, so a reader who opens a link right after you publish never waits. ## Install it 1. In the [dashboard](https://dashboard.blitz.cloud/), open the App Store and pick Ghost, or click Host something new and choose "A ready-made app". 2. Give it an address such as `blog` and click Put it online. 3. Open `https://blog.yourname.blitz.cloud/ghost` and create your account. The first person to open that page becomes the owner, so do this right after the install: until then, anyone who finds the address could. What the App Store entry sets for you: | Setting | Value | | --- | --- | | `url` | your app's address | | `database__client` | `sqlite3` | | `database__connection__filename` | a file inside Ghost's own storage | Ghost needs no managed database. It keeps its own SQLite file in the storage the install reserves. ## Your own domain Ghost writes every link in your posts and newsletter from whatever address it is told to run on, so they read `blog.yourname.blitz.cloud` until you connect a domain you own. Connecting a domain, like `www.yourblog.com`, is part of Pro at 7 EUR a month: add it on the Domains page, and once it is verified, make it the app's main address. Ghost's `url` setting updates to the new domain and the app restarts to pick it up, so every link it writes from then on uses it. See [Addresses and HTTPS](/docs/addresses-and-https/) for the steps. ## Backups: on Pro, not on the free plan Ghost keeps its posts, members and uploaded images in `/var/lib/ghost/content`: a SQLite database file plus an images folder. On the free plan blitz.cloud backs up databases every night, but Ghost doesn't use a managed database, so none of that applies: on the free plan, nothing about your blog is backed up. On Pro the files apps keep are copied every night and kept for 30 nights, and you can put them back from the app's Settings tab. Either way, export your content regularly: in Ghost, go to Settings, then Labs, and use Export under "Migration options" to download a JSON file of your posts, pages and settings (not the images). Keep a copy of your images too, for example by downloading them through a file manager app like FileBrowser Quantum from the App Store. ## Moving an existing Ghost blog over If you already run Ghost somewhere else, move the content without redoing the writing: 1. On the old site, go to Settings, then Labs, and use Export under "Migration options" to download the JSON file. 2. On the new blitz.cloud install, open the same Labs page and use Import to upload it. Posts, pages, tags and members come across; the export is content only, so theme and images don't. 3. Copy your theme's files into Ghost's content folder, or reinstall it from Ghost's theme marketplace if you used a stock one, and re-upload the images your posts reference. 4. Point your domain at blitz.cloud last, once the new site looks right. See [your own domain](#your-own-domain) above, or keep the blitz.cloud address if you don't have one yet. ## Sending newsletters Ghost sends its newsletter through an email provider's HTTP API, not through a mail server on the usual SMTP ports, so blitz.cloud's block on outgoing ports 25, 465 and 587 doesn't get in the way. Set this up under Settings, then Email newsletter, with a provider Ghost supports. ## Size Ghost runs in the small size: 128 MB of memory reserved from your plan's 512 MB, with room to grow to 512 MB. That covers a personal or small team blog. A blog with heavy traffic or a large back catalog of images may want more; write to hallo@blitzworks.io if Ghost is running out of room. --- # blitz.cloud plan limits - apps, memory, storage and databases URL: https://blitz.cloud/docs/limits/ Updated: 2026-10-18 Exact limits of the blitz.cloud free plan: apps, memory, storage and databases. How memory is reserved per app, CPU, and what is not limited. The blitz.cloud free plan allows up to 5 apps, 512 MB of reserved memory shared across them, 10 GB of storage and one managed database, with database backups kept for 7 nights. An app nobody visits for 30 minutes goes to sleep and wakes on the next visit. Pro raises these limits for 7 EUR per month. ## Plan limits | | Free | Pro | |---|---|---| | Apps | 5 | 50 | | Reserved memory pool | 512 MB | 4 GB | | Storage | 10 GB | 50 GB | | Managed databases | 1 | 5 | | Database backups kept | 7 nights | 30 nights | | Burst ceiling, memory | 9 GB | 20 GB | | Burst ceiling, CPU | 16 cores | 35 cores | | Outgoing traffic speed, per app | 50 Mbit/s | 200 Mbit/s | | Builds at once | 1 | 3, ahead of the queue | | Build minutes per month | 300 | 2000 | | Private networks | 1 | Up to 5 | | Nightly copies of app files | No | 30 nights | | Price | 0 EUR | 7 EUR per month, VAT included | Hitting a limit blocks that one action, with a sentence naming the limit and what would free up room. Apps that are already running are never stopped because of it. An app made of several parts, like a web part, an API and a worker from one compose file, counts each part that keeps running as one of the plan's apps. When Pro ends and you use more than the free plan includes, everything keeps running for 14 days. After that the newest apps and databases over the limit are paused. Nothing is deleted, and it all comes back when you take Pro again. ## How memory is counted The memory pool counts memory that is reserved, not memory that is in use. Each app reserves a fixed amount depending on its size, and may use more than that up to its own ceiling when the server has room. | Size | Reserved memory | Memory ceiling | Reserved CPU | CPU ceiling | |---|---|---|---|---| | Small | 128 MB | 512 MB | 0.05 cores | 0.5 cores | | Medium | 256 MB | 1 GB | 0.1 cores | 1 core | | Large, Pro only | 768 MB | 2 GB | 0.2 cores | 2 cores | Apps from Docker images start at the small size, and App Store apps start at the size their entry says (the [App Store page](/docs/app-store/#storage-and-memory) lists which ones are medium; Immich is the only large one, which is why it needs Pro). You can change an app's size yourself in Settings, Advanced, as long as it isn't made of several parts and there's room in your plan's memory pool. When an app runs out of memory twice within six hours at its size, we give it the next size by ourselves, as long as your plan's memory pool has room. Its Activity tab says when we did. If there's no room, the app's page and its Activity tab say so and what frees some. A size we raised goes back down one step after two weeks in which the app used well under the smaller size's ceiling. A size you chose yourself stays as you set it. Databases reserve memory from the same pool: | Database | Reserved memory | Reserved storage | |---|---|---| | PostgreSQL | 128 MB | 1 GB | | MariaDB | 192 MB | 1 GB | | Redis (Valkey) | 64 MB | 0.5 GB | | Cache that comes with a store app | 48 MB | none | A cache belongs to its app and doesn't count as one of the plan's databases, only its memory counts. See [apps that bring a cache](/docs/app-store/#apps-that-bring-a-cache). So each small app takes 128 MB of the free plan's 512 MB, and an app plus a PostgreSQL database takes 256 MB. The app count and the memory pool are both limits, and you reach whichever runs out first. ## How storage is counted Storage also counts reservations. A Docker image with kept folders reserves 1 GB, an App Store app reserves up to 5 GB (a few keep everything in their database and reserve none), and databases reserve as listed above. Nextcloud and its MariaDB together reserve 6 of the free plan's 10 GB. The meters in Settings count sizes the way the plans are sold, so a full 10 GB plan reads "10 of 10 GB". ## Sleeping apps An app with an address that nobody has visited for 30 minutes is scaled to zero. It wakes when a person opens it in a browser. Requests from programs, such as uptime monitors, scripts, webhooks or API clients, don't wake it: they get an answer that the app is asleep, and it stays asleep. It holds no memory while it sleeps. On Pro an app you don't keep awake sleeps after two hours. You can keep it awake, and then programs reach it at any time. Bots and background workers without an address never sleep, and neither do private apps. On the free plan a background worker stops after 2 days with no sign-in, no deploy and no visit to the dashboard. We email you one day before, and Start runs it again. In an app made of several parts, only the parts with an address sleep. A database sleeps when every app linked to it sleeps or is paused, and starts again before the app does. A database without a linked app keeps running. More in [databases](/docs/databases/). The first visit to a sleeping app waits while it wakes, about 10 seconds, and then gets the app's own answer. That includes forms and other POST requests sent from the browser, so a form sent to a sleeping app arrives as it was sent. A browser only sees our waking page if the wake takes longer than 5 seconds, and the page reloads by itself once the app is ready. ## Build minutes Every build counts from the moment it starts until it ends, whether it works or not. Builds that failed because of us don't count, and neither do the overnight updates we start ourselves. The count starts again on the first day of each month (UTC). The free plan has 300 build minutes a month, Pro has 2000, and Power has no limit. When the month's minutes are used up, nothing new is built until the next month, pushes included, and the reason shows where you started the build and in the app's Activity. A build that is already running finishes, and running apps keep running. Settings shows how many minutes you've used this month. ## Outgoing traffic Each app can send at up to 50 Mbit/s on the free plan and 200 Mbit/s on Pro. That is a speed limit, not a quota: there's no monthly allowance and no bill for traffic. ## What is not limited - There's no traffic quota and no request counter today. ## What is blocked - Outgoing mail on ports 25, 465 and 587 is blocked for every app, to stop spam. Use an email API over HTTPS instead. - Apps can't reach other accounts' apps or databases, the platform's internal services, or private IP ranges. - Crypto miners are paused before they run, and the owner gets a mail naming what we found. ## Other limits | Limit | Value | |---|---| | Kept folders per app | 6 | | Environment variables per app | 64 | | Open log streams per account | 2 | | Main address renames | Once every 14 days | | Restarts before a crashing app is stopped | 15 | | Architecture | amd64 only | --- # Self-host Uptime Kuma on blitz.cloud URL: https://blitz.cloud/guides/self-host-uptime-kuma/ Updated: 2026-10-13 Install Uptime Kuma on blitz.cloud in one click, hosted in the EU with HTTPS. Setup, notifications, keeping it awake, and a private option. To self-host Uptime Kuma on blitz.cloud, install it from the App Store: pick Uptime Kuma, choose an address and click Put it online. blitz.cloud sets the address, gives it 1 GB of storage for monitoring data, and puts it online with HTTPS. No database needed. It is free to run. On the free plan Uptime Kuma sleeps after 30 minutes without a visit, and stops checking your sites while asleep. Someone has to open it to wake it and resume checks. On Pro you can keep it awake, so checks run 24/7. ## Install it 1. In the [dashboard](https://dashboard.blitz.cloud/), open the App Store and pick Uptime Kuma, or click Host something new and choose "A ready-made app". 2. Give it an address such as `status` and click Put it online. 3. Open `https://status.yourname.blitz.cloud` and create the admin account. The first person to open it becomes the admin, so do this right after the install: until then, anyone who finds the address could. ## Keep it checking: the Pro case The core of Uptime Kuma is checking things without you watching. But on the free plan, when it sleeps, it stops. If you want reliable monitoring, this is what Pro gives you: turn on keep-awake in Settings on Pro (7 EUR/month) and checks run 24/7. On the free plan, Uptime Kuma is fine for checking things by hand or for short stretches but not for serious monitoring. ## Notifications Uptime Kuma can send alerts over many channels: Discord, Telegram, email, webhooks and more. Email doesn't work out of the box. blitz.cloud blocks outgoing ports 25, 465 and 587 for every app, to keep the platform from being used for spam. If your mail provider accepts SMTP on port 2525, you can use it. The other way is a provider with an HTTP API. ## Backups Uptime Kuma stores monitors, notifications and history in SQLite inside `/app/data`. On the free plan nothing is backed up. On Pro, app files are copied every night and kept for 30 nights, and you can put them back from the app's Settings tab. Either way, keep a note of which sites and notification channels you set up. If you need to set Uptime Kuma up again, this list is what you need. ## Keeping the dashboard private The dashboard with your sites' status probably doesn't need to be public. You can make Uptime Kuma a private app via Tailscale or WireGuard on blitz.cloud, and the dashboard keeps its address and HTTPS but only opens on your own devices in that network. See [private apps](/docs/private-networks/). ## Size Uptime Kuma uses little memory. It runs in the small size: 128 MB reserved from your plan's 512 MB, with room to grow to 512 MB. That is plenty for monitoring dozens of sites. --- # Account security on blitz.cloud - passkeys, 2FA and sessions URL: https://blitz.cloud/docs/account-security/ Updated: 2026-09-26 Sign in to blitz.cloud with email, GitHub or Google, protect the account with passkeys, authenticator app codes and per-device sign-out, and change your email, download your data or delete the account yourself. You can sign in to blitz.cloud with an email address and password, with GitHub, or with Google. From Settings you can add passkeys, turn on two-step verification with an authenticator app, and sign out any device the account is signed in on. ## Signing up and in Sign-in runs on `login.blitz.cloud`, our own Keycloak server in the same EU data centre as everything else. No third-party login service sits in between unless you choose GitHub or Google. - Passwords must be at least 10 characters. - Email signups have to confirm their address before creating apps or databases. - Repeated failed sign-ins slow down and then lock the account for a while, to stop password guessing. - Throwaway email providers are refused at signup. ## Passkeys Add a passkey in Settings under sign-in and security, and give it a name so you can tell them apart later. The sign-in page offers the passkey your browser or phone already has, so you don't type anything. ## Two-step verification Turn on two-step verification in Settings and scan the code with an authenticator app that supports TOTP, such as Aegis, 2FAS, 1Password or Google Authenticator. From then on, signing in with a password also asks for the six-digit code. ## Sessions Settings lists every device the account is signed in on. You can sign out a single device, or every device except the one you're using. ## Linking GitHub or Google You can add GitHub or Google as another way to sign in to an existing account. If the account has no password, linking asks you to confirm with the provider you already use. ## Changing your sign-in email Settings sends you to the same form as a password change. Nothing changes until you click the link we send to the new address, and the old address gets a note that it was changed. ## Your activity Settings lists what happened on your account, newest first: what you changed, what your AI assistant or GitHub changed, and what we changed. If something looks wrong there, write to hallo@blitzworks.io. ## Notifications We send mail from noreply@blitz.cloud when a deploy fails or succeeds, when an app is stopped, when a restore has finished and when an app got an overnight update. You can switch each topic off under Settings > Notifications, or with one click in the mail itself. Mail about your account, its security and billing always comes. News only comes if you switch it on. ## What we don't see Password changes, passkey setup and two-step verification happen on the sign-in server's own pages. The dashboard never handles your password or your authenticator secret. ## Downloading your data "Download my data" in Settings gives you one file with everything we hold about the account: your apps and their settings, databases, domains, builds and history. The files your apps keep on disk and what is inside your databases are not in it. For those, write to hallo@blitzworks.io. ## Deleting your account You can delete the account yourself, in Settings. Before you confirm, it lists what goes: your apps by name, your databases and their nightly copies, the domains that stop working here, and how long your blitz.cloud address is held before someone else can take it. You type your email address to confirm. If you have Pro, it ends at once, so nothing is charged again. The apps, the data and every copy are gone within a day. You can sign up again with the same email address whenever you like. --- # Deploy an app by asking Claude URL: https://blitz.cloud/guides/deploy-with-claude/ Updated: 2026-10-17 Install the blitz.cloud plugin in Claude Code and deploy an app by asking for it in plain language, from connecting to a live address. You can put an app online without opening the dashboard, just by asking Claude Code. Install the blitz.cloud plugin and Claude will look up apps in the store, deploy them, wait for them to come up, and give you the live address. ## Connect once Install the plugin in Claude Code: ``` /plugin marketplace add blitzworks-io/blitz-cloud-mcp /plugin install blitz-cloud@blitz-cloud-mcp ``` Then type `/mcp` in Claude Code, pick blitz, and sign in with your blitz.cloud account. If you don't have one yet, sign up free at blitz.cloud. The plugin also installs a skill that knows how to deploy, so you don't need to tell Claude which tools to use. ## Ask for an app Try a prompt like this: > Put Uptime Kuma online on blitz.cloud at an address called status. Claude looks it up in the App Store, deploys it, waits for it to be ready, and tells you the live address. You can then open it and set it up. The same works for your own code: > Deploy the GitHub repository my-org/my-api to blitz.cloud. If the build fails, Claude reads the reason from the build log and tells you what went wrong in plain language instead of guessing a fix. ## What stays free, what needs Pro On the free plan, apps sleep after a while without a visit and stop running while asleep. On Pro (7 EUR/month), you can keep them awake and running 24/7. You can ask Claude what plan you're on and it will check your real usage. ## Confirmations stay with you Claude can restart, pause, or delete an app, and change DNS records and settings. But it always asks you first. For things that destroy data or change how your app works, you need to say yes. Claude won't answer those on its own. ## Codex and other assistants The same blitz.cloud MCP server works from Codex, VS Code, Cursor, and other MCP clients. See [Connect an AI assistant to blitz.cloud](/docs/ai-assistants/) to set up your client. --- # n8n pricing in 2026 URL: https://blitz.cloud/guides/n8n-pricing/ Updated: 2026-10-17 What n8n Cloud costs in 2026, what self-hosting it yourself costs, and what it costs free or always-on on blitz.cloud, with a dated price table. n8n Cloud starts at 20 EUR a month, billed annually. Self-hosting n8n yourself is free software, but it costs a server, your time to maintain it, and the risk of forgetting a backup. On blitz.cloud you can run n8n free, with the usual free-plan limits, or keep it awake on Pro so its schedules always fire on time. ## n8n Cloud plans Checked on n8n.io/pricing, 2026-10-17: | Plan | Price | Executions/mo | Concurrency | | --- | --- | --- | --- | | Starter | 20 EUR/mo, billed annually | 2,500 | 5 | | Pro | 50 EUR/mo, billed annually | 10,000 | up to 50 | | Enterprise | contact sales | custom | 200+ | n8n also sells a Business plan outside n8n Cloud, self-hosted only: 667 EUR/mo, billed annually, 40,000 executions/mo. The prices above are with annual billing. n8n also offers monthly billing at a higher price. ## Self-hosting n8n yourself n8n's source is public under its Sustainable Use License, which lets you run it for your own internal business or personal use without a licence fee. What it does cost: a server you pick and pay for whether you use it or not, installing Docker, setting up HTTPS yourself, and keeping backups and updates current. None of that is hard, but it's work. ## Running your own n8n on blitz.cloud You can run n8n on blitz.cloud free of charge. The App Store installs it with its own HTTPS address, a webhook URL and an encryption key already set. On the free plan n8n sleeps after 30 minutes without a visit, and while it sleeps its schedules don't run and a webhook call doesn't wake it (see [self-host n8n](/guides/self-host-n8n/) for the detail). It shares your plan's 512 MB memory and 10 GB storage pool with your other apps. On Pro, 7 EUR a month, you can keep n8n awake so its schedules fire on time and every webhook is answered right away. Our own numbers, measured 2026-10-17: n8n installs and comes online in about 106 seconds at the median, 34 seconds at the fastest. It runs in the medium resource size, 256 MB of memory reserved with room to grow to 1 GB, because the small size ran out of memory inside a minute. Your instance runs under n8n's own licence; blitz.cloud is not affiliated with n8n. ## Is it free / does it run 24/7 / do I need a card **Is n8n free?** The software is free either way, for your own use. n8n Cloud's cheapest plan is 20 EUR a month. Running it yourself on blitz.cloud's free plan costs nothing, with the limits above. **Does it run 24/7?** n8n Cloud does. Self-hosting it yourself does, if your server stays up. On blitz.cloud's free plan it sleeps when nobody visits; on Pro it stays awake. **Do I need a card?** n8n Cloud's free trial needs no card, and neither does blitz.cloud's free plan. --- # Self-host Nextcloud on blitz.cloud URL: https://blitz.cloud/guides/self-host-nextcloud/ Updated: 2026-10-17 Install Nextcloud on blitz.cloud in one click, in the EU. The MariaDB database it needs, the one-database limit, and what the free plan backs up. You can self-host Nextcloud on blitz.cloud without running a server of your own. Install it from the App Store: one click sets up the address, HTTPS and the MariaDB database Nextcloud needs for its file list, calendar and contacts. It comes free on the free plan, using your plan's one included database. ## Install it 1. In the [dashboard](https://dashboard.blitz.cloud/), open the App Store and pick Nextcloud, or click Host something new and choose "A ready-made app". 2. What this app needs says it keeps files between restarts and uses a MariaDB database, both set up for you. 3. Give it an address, for example `cloud`, and click Put it online. Your Nextcloud is then at `https://cloud.yourname.blitz.cloud`, with a MariaDB database connected and `NEXTCLOUD_TRUSTED_DOMAINS` already set to that address. ## Create the admin account first Open the address as soon as the app is online and create the admin account. Until you do, anyone who finds the address could create it instead and lock you out of your own install. After that, invite the people you want from Nextcloud's own Users page. ## The database it uses Nextcloud needs one database, and the App Store gives it a MariaDB one from your plan. The free plan includes one database; Pro gives you five. If you also want a second app that needs its own database, such as a second Nextcloud install or another app that isn't database-free, you need Pro for the extra slot. See [databases](/docs/databases/) for how a database is created and [limits](/docs/limits/) for the full table. Storage adds up the same way: Nextcloud reserves 5 GB and its MariaDB database another 1 GB, so one install already takes 6 of the free plan's 10 GB before you upload a single file. ## Backups: the database, not your files blitz.cloud backs up every database every night, free plan included: 7 nights on free, 30 on Pro. That covers Nextcloud's file list, calendar entries and contacts, because they live in the database. The files themselves, photos and documents you upload, are kept in Nextcloud's own data folder on disk, and on the free plan folders apps keep on disk are not backed up at all. Only Pro copies those every night and keeps 30 nights, restorable from the app's Settings tab. On the free plan, a lost disk would take your uploaded files, not the database, so Nextcloud itself would come back empty rather than gone. If you keep anything in Nextcloud you can't lose and you're on the free plan, also sync it somewhere else, for example a desktop folder with the Nextcloud client, or move to [Pro](/pricing/) for the nightly file copies. ## Size and memory Nextcloud installs in the small size: 128 MB of memory reserved, up to 512 MB when the server has room. That's enough for a person or a family looking at files, calendar and contacts. If the web interface feels slow with several people uploading large files at once, you can move it to a bigger size yourself in Settings, Advanced, as long as there's room left in your plan's memory pool. ## Updates With automatic updates on, blitz.cloud checks every night around 4:00 UTC for a newer Nextcloud build and puts it online. If the new version doesn't start within ten minutes, the one before it comes back, and the app's Activity tab says so. --- # Connect an AI assistant to blitz.cloud over MCP URL: https://blitz.cloud/docs/ai-assistants/ Updated: 2026-10-17 Let Claude, ChatGPT, Cursor, VS Code or any MCP client deploy and manage your apps on blitz.cloud. Sign in with your blitz.cloud account or use an API key. Setup, what an assistant can do, and the limits. blitz.cloud runs an MCP server at `https://mcp.blitz.cloud/`. Connect an AI assistant to it and the assistant can do what you can do in the dashboard: put apps online, create databases, change settings, read logs and add DNS records. You can then ask it things like "put Uptime Kuma online at uptime" or "why did my app stop?". There are two ways to connect. Most assistants sign in with your blitz.cloud account, the same way you connect them to other services: you add the address, a browser window opens, you sign in and allow it. Scripts and clients that can't sign in use an API key instead. Your server address is on the [AI tools](https://dashboard.blitz.cloud/ai) page in the dashboard. ## Sign in (recommended) **Claude (web and desktop)**: Settings, Connectors, Add custom connector. Paste your server address, click Connect and sign in. **Claude Code** ``` claude mcp add --transport http blitz https://mcp.blitz.cloud/ ``` Then type `/mcp` in Claude Code, pick blitz and sign in. A plugin does the same in one step and adds a skill that knows how to deploy an app for you: ``` /plugin marketplace add blitzworks-io/blitz-cloud-mcp /plugin install blitz-cloud@blitz-cloud-mcp ``` **Cursor** (`~/.cursor/mcp.json`) ```json { "mcpServers": { "blitz": { "url": "https://mcp.blitz.cloud/" } } } ``` **VS Code** (`.vscode/mcp.json`) ```json { "servers": { "blitz": { "type": "http", "url": "https://mcp.blitz.cloud/" } } } ``` **ChatGPT and other clients**: add a connector or MCP server with your server address and sign in when asked. When you sign in, blitz.cloud shows which app is asking before you allow it. If the app's address belongs to a publisher blitz.cloud recognises (Claude Code and VS Code), the page names that domain. Any other app registered itself, and the page says its name is its own claim. Only allow an app you just connected yourself. blitz.cloud never asks you to do this from an email or a message. Each app you sign in appears under Connected apps on the AI tools page. Disconnect stops it immediately, not when its sign-in would have run out. Signing it in again later works. ## With an API key On the AI tools page, give the key a name (the computer or tool that will use it) and click Make a key. - The key is shown once, right after you make it. Copy it then. blitz.cloud only keeps a hash of it and can't show it again. - You can have up to 5 keys. Make one per computer or tool, so you can take one back without touching the others. - Rotate gives a key a new value under the same name. The old value stops working at once. - Revoke deletes a key. Anything still using it is refused from then on. Send the key with every request in the `Authorization: Bearer ` header. For Claude Code: ``` claude mcp add --transport http blitz https://mcp.blitz.cloud/ --header "Authorization: Bearer " ``` The AI tools page has the same setup for Cursor and VS Code, with a new key already filled in. Treat a key like a password. Anyone who has it can manage your apps. A key also works with [the blitz command](/docs/cli/), for managing your apps from a terminal without an assistant. ## What an assistant can do The full list, with a description of each tool, is on the AI tools page and comes straight from the server. In short: | Tools | What they do | |---|---| | `apps_*` | List apps, show one, deploy from the App Store, a Docker image or a GitHub project, change name, address, port or nightly updates, restart, pause, resume, run one command, delete | | `store_*` | Search the App Store and Docker Hub, and say whether an app needs Pro | | `builds_*` | Build a GitHub project again, list its builds and why one failed | | `dbs_*` | List, create, connect to an app, restart and delete databases | | `env_*` | List, read, set and remove an app's environment variables | | `domains_*` | List, add and remove DNS records under your address | | `network_*` | See your private networks and make an app private or public | | `logs_tail` | The last lines an app printed, or what it printed before its last restart | | `usage_get` | Your plan and how much of it is used | | `platform_status` | Whether blitz.cloud itself has a problem right now, from [status.blitz.cloud](https://status.blitz.cloud/) | Restarting, pausing, running a command, deleting and removing ask you first. If your client can show a question from the server (VS Code can, for example), blitz.cloud asks you there directly, and the assistant can't answer for you. Other clients have to call again with `confirm: true`, so the assistant should check with you before it does. Connecting a Tailscale or WireGuard network is not a tool. It takes a secret or a config file, and those belong in the dashboard rather than in a chat. ## Limits - Each key or connected app can make 120 calls a minute, and 20 of those can change something. A call over the limit is refused with how many seconds to wait. - Your plan's limits are the same as in the dashboard. An assistant can't put more apps online than you could. - Changes need a confirmed email address, just like in the dashboard. - A key or a sign-in for the MCP server works only there. It doesn't open the dashboard or its API. ## Keeping track Everything an assistant changes is recorded under the key or app that did it. You can read it in your account's activity in Settings, next to what you changed yourself. On an app's Activity tab it appears as done by you. --- # Nextcloud pricing in 2026 URL: https://blitz.cloud/guides/nextcloud-pricing/ Updated: 2026-10-17 What Nextcloud GmbH's own plans cost, what self-hosting Nextcloud yourself costs, and what it costs free or always-on on blitz.cloud, with a dated overview. Nextcloud GmbH's own plans start at 100 users and are priced per user per year, so they don't fit one person. Self-hosting Nextcloud yourself is free software, but it needs a database and a server you maintain. On blitz.cloud you can run Nextcloud free, with blitz.cloud setting up its database for you, or keep it always on with Pro. ## Nextcloud GmbH's own plans Checked on nextcloud.com/pricing, 2026-10-17: Nextcloud GmbH sells Standard, Premium and Ultimate plans starting at 71.29 EUR per user per year, with a minimum of 100 users, aimed at organisations rather than individuals. For fewer than 100 users, Nextcloud GmbH points to Nextcloud One, a separate managed offering with no published price. ## Self-hosting Nextcloud yourself Nextcloud is free, open-source software (AGPL-3.0). Running your own copy costs no licence fee, but it needs a server, a database (Nextcloud recommends MariaDB or PostgreSQL over SQLite for more than a handful of files), HTTPS you set up yourself, and your own backups and updates. ## Nextcloud on blitz.cloud You can run Nextcloud on blitz.cloud free of charge. The App Store installs it with its own HTTPS address and sets up a MariaDB database for you automatically, which saves the step of installing and configuring one yourself. On the free plan it sleeps after 30 minutes without a visit, and shares your plan's 512 MB memory and 10 GB storage with your other apps; Nextcloud itself uses 5 GB of storage. On Pro, 7 EUR a month, you can keep it awake so it answers the moment you or your phone's auto-upload opens it. Our own numbers, measured 2026-10-17: Nextcloud installs and comes online in about 263 seconds (4 to 5 minutes) at the median, 131 seconds at the fastest, including setting up its database. It runs in the small resource size, 128 MB of memory reserved with room to grow to 512 MB. ## Is it free / does it run 24/7 / do I need a card **Is Nextcloud free?** The software is free either way. Nextcloud GmbH's own plans are enterprise pricing from 100 users up. Running it yourself on blitz.cloud's free plan costs nothing, with the limits above. **Does it run 24/7?** Self-hosting it yourself does, if your server stays up. On blitz.cloud's free plan it sleeps when nobody visits; on Pro it stays awake. **Do I need a card?** blitz.cloud's free plan does not. --- # Manage your apps from a terminal with the blitz command URL: https://blitz.cloud/docs/cli/ Updated: 2026-10-15 The blitz command lists your apps, puts new ones online from the App Store, a Docker image or GitHub, restarts and pauses them, runs a command inside one, shows their logs and changes their settings. One file, Node.js 18 or newer, an API key. `blitz` is a small command for your terminal. It does the everyday things you would otherwise click in the dashboard: list your apps, put a new one online, restart it, read its logs, change a setting. It is one file and needs Node.js 18 or newer, nothing else. It talks to the same server AI assistants use, with an API key, so it can do what they can do and has the same limits. See [connect an AI assistant](/docs/ai-assistants/) for how keys work. ## Install On macOS and Linux: ``` curl -fsSL https://blitz.cloud/cli/blitz.js -o ~/.local/bin/blitz chmod +x ~/.local/bin/blitz ``` `~/.local/bin` must be on your `PATH`; any folder that is works too. On Windows, save the file and run it with `node blitz.js`. ## Sign in Make a key on the [AI tools](https://dashboard.blitz.cloud/ai) page, then: ``` blitz login ``` Paste the key when asked. `blitz` tries it once and saves it in `~/.config/blitz/config.json`, readable only by you. On a server or in CI, set `BLITZ_API_KEY` instead. `blitz logout` removes the saved key from this computer; revoke it on the AI tools page to stop it working everywhere. ## Commands ``` blitz apps your apps, their status and address blitz app blog everything about one app blitz deploy store uptime-kuma --address status blitz deploy image nginx --tag 1.29 --port 8080 --address web blitz deploy github lena/blog --branch main --address blog blitz rebuild blog build it again from the newest commit blitz builds blog its builds and why one failed blitz logs blog --lines 200 the last lines it printed blitz logs blog --previous what it printed before its last restart blitz run blog -- ls -la /data run one command inside the app blitz restart blog blitz pause blog blitz resume blog blitz env blog its settings, values hidden blitz env set blog SMTP_HOST=mail.example.com blitz env unset blog SMTP_HOST blitz usage your plan and how much of it is used blitz status whether blitz.cloud itself has a problem ``` An app can be named by its name, its address label or its id. `blitz help` lists every command and option. Restart, pause, `run` and `env unset` ask before they do anything. Add `--yes` to skip the question in scripts. `--json` prints the server's answer as JSON, for `jq` and the like. Everything the AI tools page lists is reachable too: `blitz tools` shows the tools, and `blitz call` runs one with JSON arguments, for example databases: ``` blitz call dbs_list blitz call dbs_create '{"engine": "postgresql", "name": "blog-db"}' ``` ## Good to know - Every change `blitz` makes shows up in your account's history with the name of the key it used. - A command that is refused says why in one sentence and exits with code 1, so a script can stop there. - There is no live log stream yet. `blitz logs` shows the last lines, up to 500. - `blitz run` sends each word after `--` to the app exactly as you typed it. For a pipe or anything a shell would need to read as one piece, wrap it in quotes: `blitz run blog -- sh -c 'ls | wc -l'`. - A run has no input after it starts, stops listening after 60 seconds, keeps up to 64 KB of output, and allows 20 commands a minute. An image with no `sh` cannot run one. The command text stays in your history with passwords masked. --- # Vaultwarden pricing in 2026 URL: https://blitz.cloud/guides/vaultwarden-pricing/ Updated: 2026-10-17 What Bitwarden's own paid plans cost, what self-hosting Vaultwarden yourself costs, and what it costs free or always-on on blitz.cloud, with a dated overview. Bitwarden's own Premium plan costs 1.65 USD a month, billed annually. Vaultwarden, the self-hosted server that speaks the same protocol, is free software, but self-hosting it yourself still costs a server and a backup plan. On blitz.cloud you can run Vaultwarden free, with the usual free-plan limits, or get its files backed up every night on Pro. ## Bitwarden's own plans Checked on bitwarden.com/pricing, 2026-10-17: | Plan | Price | | --- | --- | | Premium | 1.65 USD/mo, billed annually at 19.80 USD/year | | Families | 3.99 USD/mo, billed annually at 47.88 USD/year, up to 6 users | Bitwarden also has a free tier with core features; Vaultwarden is a separate, community-run server that implements the same protocol, not a Bitwarden product. ## Self-hosting Vaultwarden yourself Vaultwarden is free, open-source software (AGPL-3.0). Running it yourself costs no licence fee, but it's still a server you pick and pay for, HTTPS you set up, and backups and updates you keep current. A password vault is also the one app where losing your own backup really hurts, since there's no password reset that doesn't involve the master password itself. ## Vaultwarden on blitz.cloud You can run Vaultwarden on blitz.cloud free of charge. The App Store installs it with its own HTTPS address, port and an admin token already set, and the official Bitwarden apps and browser extensions work with it (see [self-host a password manager](/guides/self-host-password-manager/)). On the free plan it sleeps after 30 minutes without a visit, and shares your plan's 512 MB memory and 10 GB storage with your other apps. On the free plan only its database is backed up, not the data file Vaultwarden keeps in its own folder; on Pro, 7 EUR a month, app files are copied every night and kept for 30 nights, and the app can stay awake. Our own numbers, measured 2026-10-17: Vaultwarden installs and comes online in about 62 seconds at the median, 14 seconds at the fastest. It runs in the small resource size, 128 MB of memory reserved with room to grow to 512 MB, which is plenty for a family's vault. ## Is it free / does it run 24/7 / do I need a card **Is Vaultwarden free?** The software is free either way. Bitwarden's own Premium plan is 1.65 USD a month. Running Vaultwarden yourself on blitz.cloud's free plan costs nothing, with the limits above. **Does it run 24/7?** Bitwarden's own service does. Self-hosting Vaultwarden yourself does too, if your server stays up. On blitz.cloud's free plan it sleeps when nobody visits; on Pro it stays awake. **Do I need a card?** Bitwarden's paid plans need one. blitz.cloud's free plan does not. --- # Ghost pricing in 2026 URL: https://blitz.cloud/guides/ghost-pricing/ Updated: 2026-10-17 What Ghost(Pro) costs in 2026, what self-hosting Ghost yourself costs, and what it costs free or always-on on blitz.cloud, with a dated price table. Ghost(Pro), the official hosted version, starts at 18 USD a month, billed yearly. Self-hosting Ghost yourself is free software, but it costs a server and your own backups. On blitz.cloud you can run Ghost free, with the usual free-plan limits, or connect your own domain and keep it always on with Pro. ## Ghost(Pro) plans Checked on ghost.org/pricing, 2026-10-17: | Plan | Price | Members | | --- | --- | --- | | Starter | 18 USD/mo, billed yearly | 1,000 | | Publisher | 29 USD/mo, billed yearly | 1,000 | | Business | 199 USD/mo, billed yearly | 10,000 | | Custom | contact sales | unlimited | All plans offer a free trial. ## Self-hosting Ghost yourself Ghost is free, open-source software (MIT licence). Running it yourself costs no licence fee, but it's a server you pick and pay for, Docker or Node.js to install, HTTPS to set up, and backups and updates to keep current. ## Ghost on blitz.cloud You can run Ghost on blitz.cloud free of charge. The App Store installs it with its own HTTPS address and a SQLite database already set up, so there's no separate database to manage. On the free plan it sleeps after 30 minutes without a visit, and shares your plan's 512 MB memory and 10 GB storage with your other apps; Ghost itself uses 2 GB of storage. On Pro, 7 EUR a month, you can connect your own domain and keep Ghost awake, so a reader who opens a link right after you publish never waits (see [self-host Ghost](/guides/self-host-ghost/)). Our own numbers, measured 2026-10-17: Ghost installs and comes online in about 94 seconds at the median, 34 seconds at the fastest. It runs in the small resource size, 128 MB of memory reserved with room to grow to 512 MB. ## Is it free / does it run 24/7 / do I need a card **Is Ghost free?** The software is free either way. Ghost(Pro)'s cheapest plan is 18 USD a month. Running it yourself on blitz.cloud's free plan costs nothing, with the limits above. **Does it run 24/7?** Ghost(Pro) does. Self-hosting it yourself does, if your server stays up. On blitz.cloud's free plan it sleeps when nobody visits; on Pro it stays awake. **Do I need a card?** Ghost(Pro)'s trial needs one eventually. blitz.cloud's free plan does not. --- # Uptime Kuma pricing in 2026 URL: https://blitz.cloud/guides/uptime-kuma-pricing/ Updated: 2026-10-18 What paid uptime monitors like UptimeRobot cost in 2026, what self-hosting Uptime Kuma yourself costs, and what it costs free or always-on on blitz.cloud. Uptime Kuma itself is free, open-source monitoring software; there's no official "Uptime Kuma Cloud". The services people compare it to are paid uptime monitors that check your sites for you without you hosting anything, like UptimeRobot. On blitz.cloud you can run Uptime Kuma itself free, with the usual free-plan limits, or keep it awake on Pro so it never stops checking. ## UptimeRobot's paid plans Checked on uptimerobot.com/pricing, 2026-10-18: | Plan | Price | Monitors | Check interval | | --- | --- | --- | --- | | Solo | 10 EUR/mo, 9 EUR/mo billed annually | 10 | 60 s | | Team | 41 EUR/mo, 35 EUR/mo billed annually | 100 | 30 s | | Scale | 77 EUR/mo, 65 EUR/mo billed annually | 200 | 15 s | UptimeRobot also has a free plan with a 5-minute check interval, and an Enterprise plan with custom pricing and faster intervals. ## Self-hosting Uptime Kuma yourself Uptime Kuma's source is public under the MIT licence, free for any use including commercial. What it costs instead: a server you pick and pay for whether you use it or not, installing Docker, setting up HTTPS yourself, and keeping backups and updates current. ## Running your own Uptime Kuma on blitz.cloud You can run Uptime Kuma on blitz.cloud free of charge. The App Store installs it with its own HTTPS address and 1 GB of storage for monitoring data; it needs no database. On the free plan it sleeps after 30 minutes without a visit, and while it sleeps it stops checking your sites (see [self-host Uptime Kuma](/guides/self-host-uptime-kuma/) for the detail). On Pro, 7 EUR a month, you can keep it awake so checks run around the clock. It runs in the small resource size, 128 MB of memory reserved with room to grow to 512 MB. We don't have a timed install figure for Uptime Kuma yet; it has no database to wait on, which is why it runs in the lightest size the store offers. ## Is it free / does it run 24/7 / do I need a card **Is Uptime Kuma free?** The software is free either way. UptimeRobot's cheapest paid plan is 10 EUR a month, 9 EUR billed annually; it also has a free plan with a 5-minute check interval. Running Uptime Kuma yourself on blitz.cloud's free plan costs nothing. **Does it run 24/7?** UptimeRobot does. On blitz.cloud's free plan Uptime Kuma sleeps when nobody visits and stops checking; on Pro it stays awake and checks keep running. **Do I need a card?** UptimeRobot's free plan needs no card, and neither does blitz.cloud's free plan. --- # Paperless-ngx pricing in 2026 URL: https://blitz.cloud/guides/paperless-ngx-pricing/ Updated: 2026-10-18 What self-hosting Paperless-ngx yourself costs, and what it costs free or always-on on blitz.cloud, with our own measured numbers. There's no official hosted version of Paperless-ngx; it's a project you run yourself, not a product someone sells as a service. Document scanners like Evernote or Google Drive do a different job: they store files, but they don't read and file a scanned letter for you the way Paperless-ngx does. On blitz.cloud you can run Paperless-ngx free, with the usual free-plan limits, or keep it awake on Pro so it keeps fetching your scans. ## Self-hosting Paperless-ngx yourself Paperless-ngx's source is public under the GPL-3.0 licence, free to run for any purpose. What it costs instead: a server you pick and pay for whether you use it or not, a Postgres database and a Redis cache to set up alongside it, HTTPS, and keeping backups and updates current yourself. Losing your backup here means losing your scanned archive, not just a config file. ## Running your own Paperless-ngx on blitz.cloud You can run Paperless-ngx on blitz.cloud free of charge. The App Store installs it with its own HTTPS address, 5 GB of storage for your documents, and a Postgres database and Redis cache already created and connected. On the free plan it sleeps after 30 minutes without a visit, and while it sleeps it stops fetching documents from your mailbox. It shares your plan's 512 MB memory and 10 GB storage pool with your other apps. On Pro, 7 EUR a month, you can keep Paperless-ngx awake so it keeps fetching and filing documents without you opening it first. Our own numbers, measured 2026-09-25, v3.2.1: Paperless-ngx runs in the medium resource size, 256 MB of memory reserved with room to grow to 1 GB. Sitting idle after sign-in it used 694 MiB; a PDF posted to it was read and filed in 5 seconds, peaking at 939 MiB during that work. ## Is it free / does it run 24/7 / do I need a card **Is Paperless-ngx free?** The software is free either way, for your own use. There's no paid hosted version to compare it to. Running it yourself on blitz.cloud's free plan costs nothing, with the limits above. **Does it run 24/7?** Self-hosting it yourself does, if your server stays up. On blitz.cloud's free plan it sleeps when nobody visits and stops fetching your mailbox; on Pro it stays awake. **Do I need a card?** blitz.cloud's free plan needs no card. --- # OpenClaw pricing in 2026 URL: https://blitz.cloud/guides/openclaw-pricing/ Updated: 2026-10-18 What self-hosting OpenClaw yourself costs, and what it costs free or always-on on blitz.cloud, with our own measured numbers. There's no official hosted "OpenClaw Cloud"; it's a gateway you run yourself and connect to your own chat apps. ChatGPT and Claude do a different job: they are chat products with their own models behind them, not a gateway you point at your own tools. On blitz.cloud you can run OpenClaw free, with the usual free-plan limits, or keep it awake on Pro so it keeps answering and running its reminders. ## Self-hosting OpenClaw yourself OpenClaw's source is public under the MIT licence, free for any use including commercial. What it costs instead: a server you pick and pay for whether you use it or not, installing Docker, setting up HTTPS yourself, and keeping backups and updates current. ## Running your own OpenClaw on blitz.cloud You can run OpenClaw on blitz.cloud free of charge. The App Store installs it with its own HTTPS address and 1 GB of storage; it needs no database. On the free plan it sleeps after 30 minutes without a visit, and while it sleeps it stops answering your chat apps and stops running its reminders. It shares your plan's 512 MB memory and 10 GB storage pool with your other apps. On Pro, 7 EUR a month, you can keep OpenClaw awake so it keeps answering and its reminders fire on time. Our own numbers, measured 2026-09-26, 2026.7.35: OpenClaw runs in the medium resource size, 256 MB of memory reserved with room to grow to 1 GB. Its gateway was ready in about 8 seconds, and it used 350 MiB idle with no restart in the three minutes after. ## Is it free / does it run 24/7 / do I need a card **Is OpenClaw free?** The software is free either way, for your own use. There's no paid hosted version to compare it to. Running it yourself on blitz.cloud's free plan costs nothing, with the limits above. **Does it run 24/7?** Self-hosting it yourself does, if your server stays up. On blitz.cloud's free plan it sleeps when nobody visits and stops answering; on Pro it stays awake. **Do I need a card?** blitz.cloud's free plan needs no card. --- # Immich pricing in 2026 URL: https://blitz.cloud/guides/immich-pricing/ Updated: 2026-10-18 What self-hosting Immich yourself costs, and what it costs on blitz.cloud's Pro plan, with our own measured numbers. There's no official hosted "Immich Cloud"; FUTO ships only the software you run yourself. Google Photos, iCloud Photos and Amazon Photos are a different kind of product: photo storage bundled into a bigger subscription you don't control, not your own copy of Immich. Immich needs more memory than the free plan has, so it runs on blitz.cloud's Pro plan (7 EUR a month, 14-day trial without a card). ## Self-hosting Immich yourself Immich's source is public under the AGPL-3.0 licence, free to run for any purpose. What it costs instead: a server with enough memory for photo and face search, a Postgres database with vector search and a Redis cache to set up alongside it, HTTPS, and keeping backups and updates current yourself. Losing your backup here means losing your photo library, not just a config file. ## Running your own Immich on blitz.cloud You can run Immich on blitz.cloud on the Pro plan. The App Store installs it with its own HTTPS address, 5 GB of storage for your photos and videos, and a Postgres database with vector search plus a Redis cache already created and connected. Face and object search are off for now, because they need more memory than an app gets here; photos, albums, the map and sharing all work. Our own numbers, measured 2026-09-26, v3.2.2, at the large resource size (768 MB of memory reserved, room to grow to 2 GB): importing 228,294 photo records took 19 seconds, peaking at 1.2 GiB with the database using 528 MiB; sitting idle afterwards it used 730-760 MiB, with no restart in the 10 minutes we watched it. A smaller, 1 GiB size was tried first and was OOM-killed during that same import, which is why Immich needs the large size and Pro. ## Is it free / does it run 24/7 / do I need a card **Is Immich free?** No. Immich needs blitz.cloud's Pro plan, 7 EUR a month with a 14-day trial that needs no card, because it needs more memory than the free plan has. The software itself is free if you host it yourself. **Does it run 24/7?** Self-hosting it yourself does, if your server stays up. On blitz.cloud it runs on Pro, which keeps it awake. **Do I need a card?** blitz.cloud's Pro trial needs no card; the first charge comes after the 14 days unless you cancel. --- # Self-host Hermes Agent on blitz.cloud URL: https://blitz.cloud/guides/self-host-hermes-agent/ Updated: 2026-10-18 Install Hermes Agent on blitz.cloud in one click, hosted in the EU with HTTPS. The API key, keeping it awake, and what it doesn't do. To self-host Hermes Agent on blitz.cloud, install it from the App Store: pick Hermes Agent, choose an address and click Put it online. blitz.cloud sets the address, gives it 1 GB of storage and puts it online with HTTPS. No database needed. It is free to run. On the free plan Hermes Agent sleeps after 30 minutes without a visit, and while it sleeps it stops answering your chat apps and stops running its scheduled tasks. On Pro you can keep it awake, so it answers around the clock. ## Install it 1. In the [dashboard](https://dashboard.blitz.cloud/), open the App Store and pick Hermes Agent, or click Host something new and choose "A ready-made app". 2. Give it an address such as `hermes` and click Put it online. 3. Open the app's Environment tab and find `API_SERVER_KEY`. blitz.cloud generates this key for you; it is what every request to the agent must send. ## Connect it to a model Hermes Agent runs no AI model itself. Add your model provider's API key in Environment, for example `OPENROUTER_API_KEY`, then point an OpenAI-compatible app or script at `https://hermes.yourname.blitz.cloud/v1` and send the `API_SERVER_KEY` value as its API key. From there it looks like any OpenAI-style endpoint to the app on the other end. ## What it doesn't give you here Hermes Agent also ships a dashboard and a terminal chat, but both need to run as the machine's owner, and apps on blitz.cloud never do. So on blitz.cloud, Hermes Agent is the API only: no web dashboard, no built-in chat window. If you want to talk to it directly, point a chat client that speaks the OpenAI API at it. ## Keep it answering: the Pro case On the free plan, Hermes Agent sleeps after 30 minutes without a visit, and a sleeping agent doesn't answer your apps or run its scheduled tasks. On Pro (7 EUR/month), turn on keep-awake in Settings and it stays up, so your own tools can call it any time and its scheduled tasks run on time. ## Size Hermes Agent runs in the medium resource size: 256 MB reserved from your plan's 512 MB, with room to grow to 1 GB. Measured idle use was under 256 MB with no restarts. --- # blitz.cloud terms of service URL: https://blitz.cloud/terms/ Updated: 2026-10-18 The terms for blitz.cloud, the free plan, Pro, Power, Pro apps and domains: how the contract is made, price, cancelling, what happens when Pro ends, acceptable use and liability. These terms apply to using blitz.cloud on the free plan, on Pro and Power, for Pro apps and for domains bought on blitz.cloud. They exist in German and in English. If the two versions differ, the German one applies. ## 1. Provider and scope blitz.cloud is operated by BlitzWorks UG (haftungsbeschränkt), Graßer Weg 73, 93053 Regensburg, Germany, represented by its managing director Simon Gloël, registered at the Amtsgericht Regensburg under HRB 21609, VAT ID DE455125901, email hallo@blitzworks.io ("we"). These terms apply to every contract about blitz.cloud between us and consumers or businesses ("you"). Terms of your own only apply if we agree to them in writing. ## 2. Account and contract When you sign up and confirm your email address, you make a contract with us for the free plan. Signup is open and there is no waiting list. You must be at least 16 to sign up. Each person may have one account. Accounts with the same mailbox count as accounts of the same person, even when the address is written differently: in upper or lower case, with an addition after a plus sign (such as name+test@example.com), or, for Gmail, with dots in the name. For Gmail, gmail.com and googlemail.com count as the same address. If a mailbox already has an account, we refuse another one at signup, also through GitHub or Google and also when the first account is suspended. A further account of the same person gets no free Pro trial (section 5a). If you have several accounts, the one you used last stays active. We may suspend the others under section 10 at once and without a warning. Nothing is deleted: you can still sign in to a suspended account, download your data and delete it. If you think we wrongly counted your accounts together, write to hallo@blitzworks.io. You buy Pro in the dashboard under Settings. You are sent to the payment page of our payment provider Stripe. Clicking the payment button there is a binding offer, which we accept once the payment is confirmed and your account is switched to Pro. Only adults, or people acting for a business, can buy Pro. Your details must be correct. Keep your login details secret, and tell us if you think someone else knows them. Sign up with an email address that stays yours and where our mail reaches you. We don't accept addresses from throwaway mail services, which hand out an inbox for a short time or to anyone. This also applies when you sign up through GitHub or Google and when you change your address later. We decide which services count as throwaway using a public list of such services and our own additions. Addresses from mail services that protect your privacy, such as forwarding addresses, are fine as long as our mail reaches you there. If you think we wrongly treat your address as throwaway, write to hallo@blitzworks.io. If your account uses a throwaway address, we ask you by email to change it and give you at least 14 days to do so. If you don't, we may suspend the account and pause its apps until you change the address. Nothing is deleted. Section 10 is not affected. ## 3. What blitz.cloud provides blitz.cloud puts apps, containers and managed databases online under an address that belongs to your account. What is included and which limits apply is on the [pricing](/pricing/) and [limits](/docs/limits/) pages, in their current version. Which features are live is on [what's live](/whats-live/). We keep developing blitz.cloud and may change features, as long as the essential parts of your plan stay and the change is reasonable for you. ## 4. The free plan The free plan costs nothing and doesn't expire. Its limits apply: 5 apps, 512 MB of reserved memory, 10 GB of storage, one managed database, and one app or part of an app that runs in the background. An app nobody has visited for 30 minutes goes to sleep. It wakes again when a person opens it in a browser. Requests from programs, such as uptime monitors, scripts or webhooks, don't wake it and don't keep it awake. On Pro and Power you can keep an app awake. An app on Pro or Power that you don't keep awake goes to sleep after two hours without a visitor. On every plan, a database sleeps while every app linked to it sleeps or is paused, and starts again before the app wakes. A database without a linked app keeps running. When you reach a limit, only the action that would exceed it is refused. An app or part without an address that runs in the background stops on the free plan when nothing has happened in your account for 2 days: no sign-in, no deploy and no visit to the dashboard. We email you one day before. One click on Start in the dashboard runs it again without a new build, and the 2 days start over. Files, settings and data are kept. This rule does not apply on Pro and Power. We may end the free plan with six weeks' notice by email. We may change its limits with effect from the day we tell you by email. If you don't agree, you can delete your account at any time. Until 31 March 2027 section 6a applies as well. The right to end the contract without notice under section 10 is not affected. ## 5. Pro and Power: price and payment Pro and Power cost the price shown on the [pricing](/pricing/) page when you buy, including VAT. You choose monthly or yearly payment. The amount is charged in advance for each month or year through Stripe, with one of the payment methods offered on the payment page. With monthly payment the plan renews for another month each time, until you or we cancel it. With yearly payment the first year is fixed. After that the plan continues for an indefinite period and is still charged yearly in advance, until you or we cancel it. Section 6 says how you cancel it then. What applies to Pro in these terms applies to Power as well. Businesses can enter their VAT ID when paying. Businesses based in another EU member state are billed net under the reverse-charge rule, and the customer accounts for the VAT. You get invoices electronically, and you find them in Settings. If a payment fails, Stripe tries again over the following days, and Pro keeps running in the meantime. If the payment still doesn't go through, Pro ends and section 7 applies. ## 5a. Trying Pro for free When you want to keep an app awake or connect a domain of your own, we may offer you Pro free of charge for 14 days. The offer is once per person. If you already had a free trial on another account, you get no further one. You can still order Pro, and it is then charged from the day of the order. We count accounts as accounts of the same person if they share the mailbox (section 2), the GitHub or Google account used to sign in, or the payment card, or if they have the same name and also share one of these: an IP address used to sign up or sign in, own domains under the same parent domain, or the GitHub account the apps' repositories come from. We don't tell you which account matched. If you think we got this wrong, write to hallo@blitzworks.io. At the start of the trial you add a card at Stripe. Pro is only ordered when you then click the button in the dashboard that places the order with an obligation to pay. Right above it we show what Pro costs after the trial and the day of the first charge. We confirm the order by email. The 14 days cost nothing. If you don't cancel before they end, Pro carries on with monthly payment: on the day the trial ends we charge the first month at the price shown above the button, and then every month in advance. From then on sections 5 and 6 apply as for any Pro subscription. Three days before the first charge we remind you by email, with the amount and the date. You can cancel during the trial at any time, in any of the ways in section 6. Pro then runs until the 14 days are over, nothing is charged, and after that section 7 applies as if Pro had ended. The withdrawal period under section 13 starts with the order. If you started a trial without a card, it ends by itself after 14 days. It does not turn into a paid subscription, and nothing is charged. ## 5b. Pro apps While your account is on the free plan, you can make single apps Pro apps. Each Pro app is paid for by itself. What a Pro app gets is on the [pricing](/pricing/) page. It costs the price shown there when you buy, including VAT, and is paid monthly or yearly in advance through Stripe. Section 5 applies to payment. The price you pay when you buy stays the same for that Pro app at every renewal, monthly or yearly. If we change the price on the [pricing](/pricing/) page, the new price only applies to Pro apps bought after that. We only change the price of a running Pro app under section 12. With monthly payment a Pro app renews for another month each time. You can end it any time, effective at the end of the month you have paid for. With yearly payment the first year is fixed, and you can end it at the end of that year. After that it continues for an indefinite period, and you can end it any time with one month's notice. We then refund the money for the time after it ends, pro rata by day. You end a Pro app in the app's settings, on the [cancel page](/cancel/) without signing in, or in the other ways in section 6. If you buy Pro or Power, your Pro apps end once the plan is paid for. A free Pro trial does not end them. The paid time left over is credited to you at Stripe and set against your next payments. When a Pro app ends, the app counts against your plan again. If it fits within the plan's limits together with its database, it keeps running and sleeps like your other apps. If it doesn't, we pause it and its database until there is room again. Nothing is deleted. A domain of your own then stops pointing at the app. We can cancel a Pro app the same way as Pro (sections 6 and 6a). ## 5c. Domains You can buy a domain on blitz.cloud. We register it for you through our registrar, netcup GmbH, in your name: you are its owner, and the registry's terms for the domain ending apply too (for .de those of DENIC eG). For that we pass the owner's details you give us to netcup and the registry. They have to be correct and up to date, otherwise the registry can take the domain away. A domain is paid yearly in advance through Stripe, at the price shown when you buy it, including VAT. Some endings also have a one-time setup fee in the first year. While your account is on the free plan, a domain comes with a Pro app, paid together with it; section 5b applies to that Pro app, except that it starts and ends with the domain. On Pro or Power you buy the domain alone. We register the domain as soon as you have paid. If the registry doesn't register it (someone else got the name first, or the registry refuses it), we refund everything you paid for it. Your right of withdrawal for the domain ends once it is registered, since a registered domain can't be given back (details in the [withdrawal notice](/withdrawal/)). After that it only ends by cancelling. Its DNS runs at Cloudflare through our account. You can change every record yourself on the domain's page, also the ones that send visitors to blitz.cloud, and put those back at any time. Certificates for the domain and for names directly in front of it are included. A domain renews for a year at a time. You can cancel it in the first year, effective at the end of that year. After the first year you can cancel it any time with one month's notice, and we refund the money for the time after that, pro rata by day. You cancel on the domain's page, on the [cancel page](/cancel/) or in the other ways in section 6. A cancellation can be taken back on the domain's page until we pass it to the registry, about 40 days before the registry year ends. After the end, the domain no longer shows your apps; the registry keeps it in your name until its year is over. You can move a domain to another provider at any time. On its page you get the transfer code. Some registries only allow a move 60 days after registration. Once the move is done, the contract ends with it and nothing more is charged; time already paid is not refunded. If the payment for a renewal fails and Stripe gives up, the domain ends like a cancelled one. We can end a domain contract with notice to the end of its paid year, or for good cause. Section 6a does not apply to domains. ## 6. Term and cancellation With monthly payment Pro has no minimum term, and you can cancel any time, effective at the end of the month you have paid for. With yearly payment you can cancel in the first year, effective at the end of that year. After the first year you can cancel any time with one month's notice. We then refund the money for the time after the contract ends, pro rata by day. How to cancel: - in Settings, under Plan and usage, - on the [cancel page](/cancel/), without signing in, - by email to hallo@blitzworks.io or by letter to the address above. You get a confirmation by email. Apart from the yearly plan after its first year, time already paid is not refunded pro rata, unless you withdraw from the contract (section 13) or the law says otherwise. In addition, we refund your first month of Pro in full if you ask for it by email to hallo@blitzworks.io within 30 days of your first payment. This applies once per account and does not limit your right of withdrawal. We can cancel Pro with one month's notice to the end of a billing month. We send the notice by email. If you pay yearly, billing months are counted from the day the paid year began. If you paid yearly, we refund the money for the time after the contract ends, pro rata by day. You can end the free plan and your account any time by deleting the account in Settings. If you still have Pro then, it ends with the account straight away and nothing more is charged. Until 31 March 2027 we can also cancel under section 6a. Both sides keep the right to end the contract for good cause. ## 6a. Cancellation by us in the start phase Until 31 March 2027 blitz.cloud is in its start phase. During this time we are still finding out which plans and which use we can offer for the long run. So until that day the following applies in addition to sections 4 and 6: We can cancel the free plan, Pro and Power with 14 days' notice by email, without giving a reason. In the same way we can end the whole contract and close your account. If only a paid plan ends, your account moves to the free plan and section 7 applies. If we close your account, you can sign in until the notice period ends and download your apps, files and databases. After that we delete them. If you have already paid for the running month or year, we refund the whole amount for that period, including the days on which you already used the plan. The money goes back to the payment method you paid with. This section only applies to contracts made after it was added to these terms, and to Pro and Power if you buy them after that. If we remove content or suspend an account because of a breach, sections 8 and 10 apply, not this section. Both sides keep the right to end the contract for good cause. ## 7. When Pro ends When Pro ends, for whatever reason, your account moves to the free plan. If it uses no more than the free plan includes, nothing else changes. If it uses more, nothing changes for 14 days, and we tell you by email what is over the limits. During that time your apps keep running as before; only new things are measured against the free plan. After the 14 days: - the newest apps are paused until the rest fit the free plan, - the newest databases are paused until one is left, - your own domains stop pointing at your apps, - apps you kept awake go back to sleeping when nobody visits. Nothing is deleted. Addresses, settings, files and data stay. If you take Pro again, paused apps and databases start by themselves. ## 8. What is not allowed on blitz.cloud You may not use blitz.cloud to - offer content that breaks the law or infringes other people's rights, - make films, series, TV channels, music or other copyrighted works available without the right holder's permission, including IPTV relays, stream proxies and download services for such works, - offer pornographic or sexually explicit content, - pass an app or an account name off as another company or brand, or run phishing pages, - mine cryptocurrency, - send spam or unsolicited mass email, - attack, spy on or overload other systems or people, including phishing and malware, - run a VPN, proxy or tunnel server that forwards internet traffic, such as Xray, V2Ray, sing-box or an open web proxy, - get around the limits of your plan, the isolation between accounts or our security measures. A reverse proxy in front of your own apps is allowed, and so is a private network between your apps and your own devices with Tailscale or WireGuard. If an app breaks these rules, we may pause it at once, without warning you first. If our automated check finds a known VPN, proxy or tunnel program in an app, it pauses the app at once, without a person checking first. Unless you have a paid plan or a trial with a card, it also suspends your account (section 10). We tell you why by email, unless the law or averting a danger prevents it. If you disagree, reply to the email or write to hallo@blitzworks.io, and a person looks at the decision again. If you find an app on blitz.cloud that breaks these rules, write to hallo@blitzworks.io. The [imprint](/imprint/#reporting-illegal-content) lists what we need to look into it. ## 9. Your content and your data You are responsible for the apps, content and data you run on blitz.cloud. You grant us the rights we need to store and serve them for you and, on the free plan, to add the link described in the next paragraph, and no more. On the free plan we add a small "Made with blitz.cloud" link to the HTML pages your apps serve. It sits in a bottom corner, leads to blitz.cloud, loads nothing from other servers, sets no cookie and stores nothing on your visitors' devices. A visitor can hide it on the page they are looking at. Where your page's Content-Security-Policy does not allow it, we leave it out. Other responses, such as JSON, images and files, stay unchanged. On Pro and Power the link is off, and you can turn it on in an app's Settings. If your account existed before this paragraph applied, the link appears no earlier than six weeks after we told you about it by email. We back up managed databases every night and keep the backups for 7 nights on the free plan and 30 nights on Pro. On Pro we also back up the files your apps keep on disk every night and keep them for 30 nights; on the free plan they are not backed up. We can't guarantee that a backup is complete or can be restored. Keep your own copy of anything that matters to you. If your apps process other people's personal data, you are responsible for that. You can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF once you are signed in. How we handle your own data is in the [privacy policy](/privacy/). ## 10. Availability, suspension and termination without notice We run blitz.cloud with the care you can expect from a hosting provider, but we don't promise a particular availability. Maintenance, updates and security measures can interrupt the service briefly. We announce larger maintenance in advance when we can. If you seriously break these terms, in particular section 8, or your account endangers others, we may suspend your account and end the contract without notice. Where it is reasonable, we warn you first. If you have already paid for time after the termination, we refund that part, unless you caused the termination by a deliberate breach. ## 11. Liability We are liable without limit for intent and gross negligence, for injury to life, body or health, under the German Product Liability Act, and where we have given a guarantee. For slight negligence we are only liable if we breach an essential contractual obligation, meaning an obligation that makes the contract possible in the first place and that you may normally rely on. In that case liability is limited to the damage typical for this kind of contract and foreseeable. For lost data we are then only liable up to the amount that would have arisen if you had kept regular backups yourself. These rules also apply to our employees, representatives and agents. ## 12. Changes to these terms and to prices We can change these terms when laws, court decisions or the service change. We email you the changes at least six weeks before they are meant to apply. Changes to the price or the scope of the service only apply if you expressly agree. If you don't agree, Pro ends at the end of the billing month in which the change was meant to apply. This applies to Pro, Power and Pro apps. For the free plan, section 4 applies. For any other change you can object or cancel the contract until the day it is meant to apply. The email says so. ## 13. Right of withdrawal As a consumer you have a statutory right of withdrawal for Pro, Power, Pro apps and domains. For a domain it ends once the domain is registered. The details are in the [withdrawal notice](/withdrawal/). ## 14. Dispute resolution We are neither willing nor obliged to take part in dispute resolution proceedings before a consumer arbitration board. ## 15. Applicable law and jurisdiction German law applies, excluding the UN Convention on Contracts for the International Sale of Goods. If you are a consumer whose habitual residence is in another country, you keep the protection of that country's mandatory consumer law. If you are a merchant, a legal entity under public law or a special fund under public law, the place of jurisdiction is Regensburg. ## 16. Final provisions If a provision of these terms is invalid, the others remain valid. The invalid provision is replaced by the statutory rule. --- # blitz.cloud cookie policy URL: https://blitz.cloud/cookies/ Updated: 2026-10-19 Which cookies blitz.cloud sets, which of them need your consent, how long they last and how to change your choice. This page lists the cookies and the browser storage blitz.cloud uses: on the website blitz.cloud, in the dashboard at dashboard.blitz.cloud and at sign-in on login.blitz.cloud. It is the short version of sections 3 and 4 of the [privacy policy](/privacy/), which names the legal bases and the providers. If the two differ, the privacy policy applies. ## What a cookie is A cookie is a small text file a website stores in your browser. With it the site recognises the browser again, for example to keep you signed in. Local storage does a similar job for settings that stay on your device. ## Your choice Most cookies here are needed for blitz.cloud to work and are set without asking. Two kinds are only set if you agree in the consent dialog: the statistics cookies and the advertising cookies. You can change or withdraw your choice at any time with effect for the future: on the website through "Cookie settings" in the footer, in the dashboard under Settings. ## Cookies that need your consent ### Statistics We count visits to blitz.cloud and the dashboard with Matomo, which we run ourselves. The count works without cookies and without access to your device. Only if you allow statistics cookies in the consent dialog does Matomo also set the cookies `_pk_id` (13 months) and `_pk_ses` (30 minutes) to recognise returning visits. They are deleted when you withdraw your consent. ### Advertising The blitz.cloud website shows ads through Google AdSense, and only on articles: the pages of our docs, our guides and our comparisons. No other page shows ads. Google's ad script still loads on every page of the website and in the dashboard, because it also shows the consent dialog; there it asks for no ads. Sign-in and our customers' apps don't load it. The dashboard shows no ads at present. Third party vendors, including Google, use cookies to serve ads based on a user's prior visits to this website or other websites. Google and its partners only set or read such cookies and similar identifiers on blitz.cloud if you agree in the consent dialog. Which providers these are, what they use the data for and how long they keep their cookies is listed in the consent dialog. If you do not agree, we tell Google so. Google then shows, where it can, only non-personalised or limited ads and sets no advertising cookies for them. How Google uses data on its partners' sites is explained at [policies.google.com/technologies/partner-sites](https://policies.google.com/technologies/partner-sites). You can also turn off personalised advertising from Google in [Google's Ads Settings](https://adssettings.google.com), and from many other providers at [www.aboutads.info](https://www.aboutads.info/choices/) and [www.youronlinechoices.eu](https://www.youronlinechoices.eu). ## Cookies that are needed These are technically necessary and are set without consent: | Where | Name | What for | How long | |---|---|---|---| | dashboard.blitz.cloud | `__Host-blitz_session` (split across numbered cookies when needed) | Keeps you signed in | until you close the browser or sign out | | dashboard.blitz.cloud | `blitz_state`, `blitz_verifier`, `blitz_next` | Secure the sign-in and remember where to go afterwards | 10 minutes | | dashboard.blitz.cloud | `gh_return` | Remembers which page to return to when you connect GitHub | 30 minutes | | dashboard.blitz.cloud | `blitz_ref` | Remembers the invite code when you arrive through another customer's invite link, until your account is created | 7 days | | login.blitz.cloud | Cookies of the sign-in software Keycloak, such as `AUTH_SESSION_ID`, `KEYCLOAK_IDENTITY`, `KEYCLOAK_SESSION` | Sign-in and session | the session, at most as long as the sign-in | | all addresses | Cookies of Cloudflare, whose network every request passes through | Protection from automated traffic | short, as stated by Cloudflare | | blitz.cloud and every address under it | `FCCDCF` from Google | Stores your choice in the consent dialog | 13 months | Your choice in the consent dialog applies to every address under blitz.cloud. Our customers' apps run under those addresses too and can therefore read this cookie. It holds only your choice. ## Browser storage In your browser's local storage we also keep: whether you want a light or dark look, an unsent draft in the wizard for new apps, small notes such as "this tip was already seen", whether you are signed in to the dashboard, and the code from an invite link. These entries stay on your device. Except for the invite code, which goes to us with sign-up, they are not sent to us, and you can delete them in your browser's settings. ## Cookies in our customers' apps The apps that customers run on blitz.cloud set their own cookies, and this page does not cover them. We do not measure these apps with Matomo and show no ads from us in them. ## Questions Write to hallo@blitzworks.io. More ways to reach us are on the [contact page](/contact/). --- # blitz.cloud privacy policy URL: https://blitz.cloud/privacy/ Updated: 2026-10-19 Which personal data blitz.cloud processes, what for, on which legal basis, who receives it and how long we keep it. This privacy policy applies to blitz.cloud: the website blitz.cloud, the dashboard at dashboard.blitz.cloud, sign-in at login.blitz.cloud and the interfaces api.blitz.cloud and mcp.blitz.cloud. It explains which personal data we process, what for, on which legal basis, who we pass it to and when we delete it. It exists in German and in English. If the two versions differ, the German one applies. ## 1. Controller BlitzWorks UG (haftungsbeschränkt), represented by its managing director Simon Gloël, Graßer Weg 73, 93053 Regensburg, Germany, registered at the Amtsgericht Regensburg under HRB 21609, email hallo@blitzworks.io. We have not appointed a data protection officer, because we are not required to. Please send questions about data protection to hallo@blitzworks.io or to the address above. ## 2. Where your data is blitz.cloud runs on servers we rent from our data centre operator in Germany and operate ourselves. Your account, your apps, their files and their databases are stored there. Backup copies and the built images of your apps are kept separately, with the same operator, in the EU (Finland). Files of an account that no app has needed for two days are moved, encrypted, to separate storage with the same operator in Germany, and brought back as soon as an app needs them again. Some service providers process data on our behalf or receive it because you use their service. Each is named in the sections below. Where data goes to a country outside the EU, the section also says on which basis. ## 3. When you visit blitz.cloud ### Cloudflare Every request to blitz.cloud, dashboard.blitz.cloud, login.blitz.cloud, api.blitz.cloud and mcp.blitz.cloud passes through the network of Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. Cloudflare delivers the pages, protects them from attacks and runs our name resolution (DNS). In doing so Cloudflare processes your IP address, the address requested, date and time, browser and device details and the content of the request, because Cloudflare accepts the encrypted connection and passes it on to our servers. Cloudflare may set a technically necessary cookie to recognise automated traffic (for example `__cf_bm`). Cloudflare acts as our processor. The legal basis is our legitimate interest in secure and fast delivery (Art. 6(1)(f) GDPR). Cloudflare also processes data in the USA and at locations outside the EU that are closest to you. The transfer is based on the European Commission's adequacy decision for the EU-US Data Privacy Framework, under which Cloudflare is certified, and on standard contractual clauses. More at [cloudflare.com/privacypolicy](https://www.cloudflare.com/privacypolicy/). ### Server log files With every request our servers process the technically necessary data (IP address, date and time, page requested, browser) to answer it and to detect faults and attacks (Art. 6(1)(f) GDPR). The log files are not collected in a central place and are overwritten continuously. For requests to our own addresses (blitz.cloud, dashboard, login, api and mcp) we keep the page requested without its parameters, the status code, the response time, the browser and the time in our database for 24 hours, without the IP address. This lets us trace faults afterwards. ### Fonts We serve the Geist and Geist Mono fonts from our own servers. No fonts are loaded from Google Fonts or any other provider. ### Visitor statistics with Matomo We count visits to blitz.cloud and the dashboard with the open-source software Matomo, which we run ourselves at matomo.blitzworks.io, on our servers in Germany. No data goes to the makers of Matomo or to anyone else. The statistics work without cookies and without access to your device. We process the shortened IP address (the last two blocks are removed before it is stored), the pages visited, the page you came from, date and time, browser and device type and your approximate region. In the dashboard we only record which kind of page was opened, such as "an app's overview", without names or identifiers of apps, without addresses and without account data. We respect "Do Not Track" and similar browser settings. The legal basis is our legitimate interest in measuring use of our own service with as little data as possible (Art. 6(1)(f) GDPR). Only if you allow statistics cookies in the consent dialog does Matomo also set the cookies `_pk_id` (13 months) and `_pk_ses` (30 minutes) to recognise returning visits. The legal basis is then your consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG). You can withdraw it at any time with effect for the future: on blitz.cloud through "Cookie settings" in the footer, in the dashboard under Settings. The cookies are deleted when you do. Matomo deletes the raw data of single visits after 13 months; what stays are totals that relate to no one. We do not measure the apps that customers run on blitz.cloud with Matomo. ### Measuring sign-ups and upgrades We also want to know how many accounts get from sign-up to a running app and to a paid plan, and which way they came. For this our server, not your browser, sends up to four events per account to our Matomo: sign-up finished, first app online, trial started, paid plan started. Each account gets a random number for this, which we store with the account and delete with it. The events carry that number, the page or the store app the sign-up came from, the kind of source of the first app (such as a store app or a GitHub repository), how many seconds it took until it was online, the moment the trial started, and the plan and billing interval. They carry no email address, no name, no account identifier, no IP address of yours and no app name. Nothing is stored on or read from your device. We only send events for accounts created since 16 October 2026. The legal basis is our legitimate interest in understanding which parts of blitz.cloud lead people to a working app and to a paid plan (Art. 6(1)(f) GDPR). You can object at any time by writing to hallo@blitzworks.io (Art. 21 GDPR); we then send no more events for your account and delete those already sent. Matomo deletes the events after 13 months. ### Consent dialog by Google We ask for your consent on the blitz.cloud website and in the dashboard with Google's own consent dialog ("Privacy & messaging"), a consent management platform under IAB Europe's Transparency and Consent Framework (TCF). The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. For this every page of the website and the dashboard loads Google's AdSense script (pagead2.googlesyndication.com), which brings the dialog from fundingchoicesmessages.google.com. Outside the articles it requests no ads. Google processes your IP address, to work out whether the dialog applies in your country, and details about your browser and device. Google stores your choice in your browser, in the cookie `FCCDCF` for every address under blitz.cloud (13 months), so it applies on the website and in the dashboard, and passes it on to the providers you allowed or refused. The legal basis is our obligation to be able to prove consent (Art. 6(1)(c) together with Art. 7(1) GDPR). Storing your choice is technically necessary (Section 25(2) no. 2 TDDDG). Google may also process this data in the USA; see the section on AdSense below for the safeguard. You can change or withdraw your choice at any time with effect for the future: on the website through "Cookie settings" in the footer, in the dashboard under Settings. Until 19 October 2026 the dialog came from Clickio (ALZ Software Limited, London). The cookies Clickio left in your browser (`__lxG__consent__v2` and similar) are no longer read; you can delete them in your browser's settings. ### Advertising with Google AdSense On the blitz.cloud website we show ads through Google AdSense, and only on articles: the pages of our docs, our guides and our comparisons. The ads help pay for the free plan. Google's ad script loads on every page of the website and in the dashboard, because it also shows the consent dialog (see above). Outside the articles it is told not to ask for ads, so no other page shows any: not the home page, the pricing page, the legal pages, the contact page or the dashboard. Sign-in, the interfaces and our customers' apps don't load the script at all. The dashboard shows no ads at present. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland ("Google"). When the AdSense script loads, Google processes your IP address, the page requested, the page you came from, date and time, and details about your browser and device. On articles Google uses this to deliver the ads, count views and clicks, settle payment with us and detect fraud. We do not pass account data, your email address or the content of your apps to Google. Third party vendors, including Google, use cookies to serve ads based on a user's prior visits to this website or other websites. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visits to this site and/or other sites on the Internet. Google and its partners only set or read such cookies and similar identifiers (such as web beacons) on blitz.cloud if you agree in the consent dialog. Which providers these are, what they use the data for and how long they keep their cookies is listed in the consent dialog. The legal basis is then your consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG). If you do not agree, we tell Google so through Consent Mode. Google then shows, where it can, only non-personalised or limited ads and sets no advertising cookies for them. Google still processes your IP address and the other details above to deliver the ad and detect fraud. The legal basis for that is our legitimate interest in paying for the free plan through advertising (Art. 6(1)(f) GDPR). Google processes this data as a controller in its own right, also in the USA. The transfer is based on the European Commission's adequacy decision for the EU-US Data Privacy Framework, under which Google LLC is certified. How Google uses data on its partners' sites is explained at [policies.google.com/technologies/partner-sites](https://policies.google.com/technologies/partner-sites). You can also turn off personalised advertising from Google in [Google's Ads Settings](https://adssettings.google.com), and from many other providers at [www.aboutads.info](https://www.aboutads.info/choices/) and [www.youronlinechoices.eu](https://www.youronlinechoices.eu). ## 4. Cookies and browser storage The following are technically necessary and allowed without consent (Section 25(2) no. 2 TDDDG): | Where | Name | What for | How long | |---|---|---|---| | dashboard.blitz.cloud | `__Host-blitz_session` (split across numbered cookies when needed) | Keeps you signed in. Holds your sign-in tokens, encrypted and unreadable to scripts on the page | until you close the browser or sign out | | dashboard.blitz.cloud | `blitz_state`, `blitz_verifier`, `blitz_next` | Secure the sign-in and remember where to go afterwards | 10 minutes | | dashboard.blitz.cloud | `gh_return` | Remembers which page to return to when you connect GitHub | 30 minutes | | dashboard.blitz.cloud | `blitz_ref` | Remembers the invite code when you arrive through another customer's invite link, until your account is created | 7 days | | login.blitz.cloud | Cookies of the sign-in software Keycloak, such as `AUTH_SESSION_ID`, `KEYCLOAK_IDENTITY`, `KEYCLOAK_SESSION` | Sign-in and session | the session, at most as long as the sign-in (section 5) | | all | Cloudflare, see section 3 | Protection from automated traffic | short, as stated by Cloudflare | | blitz.cloud and every address under it | `FCCDCF` from Google | Stores your choice in the consent dialog | 13 months | In your browser's local storage (Local Storage and Session Storage) we also keep: whether you want a light or dark look, an unsent draft in the wizard for new apps, small notes such as "this tip was already seen", whether you are signed in to the dashboard (so the website shows the right button), and the code from an invite link. These entries stay on your device. Except for the invite code, which goes to us with sign-up, these entries are not sent to us and can be deleted in your browser's settings. Your choice in the consent dialog applies to every address under blitz.cloud. Our customers' apps run under those addresses too and can therefore read these cookies. They hold only your choice. Only Matomo's statistics cookie and the cookies and identifiers for advertising on the blitz.cloud website need your consent. Both are described in section 3. ## 5. Your account ### Signing up and signing in For sign-up and sign-in we run the software Keycloak ourselves, at login.blitz.cloud on our servers in Germany. When you sign up we process your email address and your password (only a hash is stored), and your name if you give it. If you set up a second step, we store what it needs: the secret for one-time codes or the public key of your passkey. We send you an email with a confirmation link. The contract for the free plan is made once you confirm. blitz.cloud is for people aged 16 and over (terms section 2). We do not knowingly process data of younger children. The legal basis is performing the contract for blitz.cloud and the steps before it (Art. 6(1)(b) GDPR). If you sign up to install an app from the store, we store the store page you came from (for example `/store/n8n`, with the source of the link) and the time on your account, so the dashboard can open that app once you are set up. We remove both once you have chosen your blitz.cloud address, at the latest after seven days. The legal basis is performing the contract (Art. 6(1)(b) GDPR). We also check whether the email address of an account belongs to a throwaway mail service. That check runs against a list on our own server; nothing is sent anywhere. The list comes from a public source and our own additions. If an account uses such an address, we may refuse it or suspend the account, as section 2 of the terms describes. We also check whether the mailbox already has an account. For that we turn the address into one standard form: lower case, without an addition after a plus sign and, for Gmail, without dots. We store that form with the account and remove it together with the address. If a mailbox already has an account, we refuse another one; if a mailbox has several accounts, we suspend all but the one used last, as section 2 of the terms describes. The legal basis for these checks is performing the contract (Art. 6(1)(b) GDPR) and our legitimate interest in being able to reach every account and in preventing several accounts per person (Art. 6(1)(f) GDPR). ### Protecting sign-up and the report form with Cloudflare Turnstile The sign-up form and the form for reporting illegal content carry a Cloudflare Turnstile check, so accounts and reports come from people and not from scripts. For this your browser loads a script from Cloudflare when the form opens. Cloudflare processes your IP address and details about your browser and device and gives us a result, which we have Cloudflare confirm together with the IP address. The legal basis is our legitimate interest in preventing abuse, automatically created accounts and automated reports (Art. 6(1)(f) GDPR). For the transfer to the USA, what section 3 says about Cloudflare applies. There is no such check when you sign in, or when you sign up with GitHub or Google. ### Signing in with GitHub or Google Instead of a password you can sign up and sign in with your GitHub or Google account. We then send you to GitHub (GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107, USA) or Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). At the first sign-in we take your email address from there and, from Google, your first and last name. From GitHub we only ask for permission to read your email address, from Google for "openid email profile". We also store which GitHub or Google account belongs to your blitz.cloud account. The legal basis is performing the contract (Art. 6(1)(b) GDPR), since you choose this way yourself. GitHub and Google process the sign-in under their own responsibility and their own privacy notices. GitHub processes data in the USA, based on the EU-US Data Privacy Framework. ### Sign-in log and sessions Keycloak logs sign-ins, failed sign-in attempts, changes to your password, passkeys and second step, and the sending of sign-in emails, each with the time and IP address. We use this to send you security notices, for example when your password was changed, and to detect attacks on accounts. We also use the same entries to detect whether several accounts were created or signed in to from the same IP address (section 14). After eight wrong passwords in a row Keycloak blocks sign-in for a while. The entries are deleted automatically after 30 days. The legal basis is our legitimate interest in keeping accounts secure (Art. 6(1)(f) GDPR). A session ends after one hour without activity and after ten hours at the latest. Under Settings you can see where you are signed in (browser and operating system, IP address, start and last activity) and end single sessions. An AI assistant you connect over MCP gets its own access. It stays connected as long as the assistant uses it, and expires after at most 30 days without use. Under Settings you disconnect it at any time. ### One free Pro trial per person The free 14-day Pro trial is once per person (terms section 5a). When you start a trial, we check whether you already had one on another account. For that we compare data we already hold for other reasons: the standard form of your mailbox (above), the GitHub or Google account you sign in with, the name on the account together with the IP addresses from the sign-in log, the parent domain of your own domains and the GitHub account your apps' repositories come from. When you add a card during the trial, we also compare the fingerprint Stripe makes of the card (section 9). If the check matches an account that already had a trial, you get no free trial and can buy Pro straight away. We note the refusal and the kind of match, not the other account, in the account's log (section 6). The legal basis is our legitimate interest in giving the free offer to each person once and in limiting the cost of trials (Art. 6(1)(f) GDPR). The data is removed together with your account, as section 13 describes. ## 6. When you use blitz.cloud ### What we store To provide the service we store for your account: - your email address, your name, your blitz.cloud address (such as `lena.blitz.cloud`) and your plan, - your apps with their settings, addresses and versions, your databases, custom domains and DNS records, - your apps' settings (environment variables, including passwords and connection details). We encrypt these before storing them, - build logs, meaning what was printed while an app was built, and for apps from GitHub the message of each commit, - an app's activity (deployed, restarted, went to sleep, restored) and a log of every change to your account: who (you, an AI assistant over MCP, one of our staff, or the system) did what and when, - traffic numbers per app (requests, data volume, errors), aggregated without IP addresses, - API keys (only as a hash) and the AI assistants you connected over MCP, - how you use blitz.cloud: every night, how many apps, databases, storage and builds your account has, and when you hit a limit of your plan, click a button for Pro, open the payment page, leave it without paying or cancel, with the reason if you give one (when you leave the payment page, you can pick one from a short list), - when you last signed in, deployed an app or opened the dashboard. On the free plan this decides when a background app stops (terms, section 4). We show your apps' running output (logs) live. We do not store it in a database of our own. It stays on the server only until newer output overwrites it or the app restarts. The legal basis is performing the contract (Art. 6(1)(b) GDPR). We keep the change log also out of legitimate interest, to be able to clear up errors, abuse and disputes (Art. 6(1)(f) GDPR). ### Addresses and certificates Addresses on blitz.cloud are public. HTTPS certificates are issued for them, and every certificate is listed in public logs (Certificate Transparency), as everywhere on the internet. Those logs show your main address and, for custom domains, their names. So don't pick an address name that says more about you than you want to make public. ### Domains you buy on blitz.cloud When you buy a domain on blitz.cloud, the registry needs to know who owns it. For that we store the owner's details you enter: name, organisation if any, postal address, phone number and email address. We pass them to our registrar, netcup GmbH, Daimlerstraße 25, 76185 Karlsruhe, Germany, which creates a contact record from them and registers the domain with the registry for its ending (for .de DENIC eG, Frankfurt am Main; for other endings the registry named on the domain's page at netcup). Registries keep the owner's details as long as the domain is registered, and for most endings they don't publish them; a few registries outside the EU may show them in their public WHOIS. The domain's DNS records are kept at Cloudflare (section 3). The legal basis is performing the contract (Art. 6(1)(b) GDPR). We delete the details with your account, unless a domain is still registered in your name; then we keep them until its registry year ends. ### How we plan plans and prices From this usage data we sort each account into a group, such as "runs finished apps" or "builds their own code", and calculate a score from usage, limits and activity that shows how well Pro might fit the account. Only we see this classification. It changes nothing about what you get or pay. We use it to decide which plans, prices and features we offer. The legal basis is our legitimate interest in running and developing blitz.cloud economically (Art. 6(1)(f) GDPR). You can object (section 17). We delete this data after 400 days and with your account. In the dashboard we ask some customers once two short questions: who uses their app (just them, people they know, the public or customers, or a bot) and how they would pay for hosting (card, PayPal, Google Pay or Apple Pay, or not online). The answer is voluntary. We store it as part of your usage history and delete it after 400 days and with your account. Answers to our earlier question about four prices, with the note and the permission to contact you if you gave them, stay until you delete your account. We only write to you about them if you ticked that we may (Art. 6(1)(a) GDPR). You can withdraw this consent at any time by email to hallo@blitzworks.io. ### Recommendations in the App Store To suggest apps in the App Store, we count every night which store apps are installed together on the same accounts, including apps that were deleted again. From this we keep only a score per pair of apps, such as "accounts with Paperless often also run n8n". A pair only counts once at least three accounts share it. The scores contain no account. When you are signed in, we compare them with the apps your account runs and show you apps you don't run yet. We record which recommendations we showed you and which you clicked, to find out which way of recommending works better. We delete that record after 90 days and with your account. The legal basis is our legitimate interest in showing you apps that fit (Art. 6(1)(f) GDPR). You can object (section 17). ### Invites Under Settings you find an invite link with a code for your account. If someone signs up through this link, we store who invited whom and whether the invite counts. You only see numbers about this: how many signed up, how many counted, and how many months of Pro you earned. An invite counts once the new account has had an app online for seven days. It doesn't count if both accounts share the same mailbox or the same custom domain, the new account has a disposable address, or both accounts were created or signed in to from the same IP address (section 5). We credit the reward as balance at Stripe or as a free month of Pro. The legal basis is performing the contract (Art. 6(1)(b) GDPR), and for checking abuse our legitimate interest (Art. 6(1)(f) GDPR). We delete the data with your account. ### How long we keep it | Data | Kept for | |---|---| | Account data, apps, databases, settings | until you delete them or your account | | Build logs, versions and activity of an app | as long as the app exists. The log of a build that is not the live version is replaced by a short note after 90 days. | | AI answers about your projects (section 8) | 90 days. We keep the answer the live version of your app was built from for as long as that version runs. Of the explanation of a failed build, only the cause and the summary stay after 90 days. We keep the cost of each call without the text. | | Shown and clicked recommendations | 90 days | | Your account's change log | three years after the entry, also after the account is deleted, see section 13 | | Traffic numbers per app | 35 days | | Sign-in log (Keycloak) | 30 days | | Log of the emails we send you | content 30 days, recipient, subject and time 180 days | | Your address after a rename or deletion | blocked for others for 14 days, so nobody takes it over at once | | Backup copies | see section 11 | | Usage history and classification for plan planning | 400 days | | Answers to the earlier four-price question, invites | until you delete your account | | The random number for measuring sign-ups (section 3) | until you delete your account; the events in Matomo 13 months | | Store page a sign-up came for (section 5) | until you choose your address, at most seven days | | Invoices and accounting records | eight years, see section 9 | ## 7. Builds from GitHub and other git hosts When you deploy a project from GitHub, blitz.cloud fetches the code of the chosen commit, builds an image from it and stores it in our own registry. The images are stored in our data centre operator's object storage in the EU (Finland). For each project we keep the last ten versions that were online, so you can go back to an earlier one. Images of deleted apps are removed in the nightly clean-up. Public projects are fetched without signing in to anything. For private projects and for automatic updates on every push you connect our GitHub App to your GitHub account. You decide at GitHub which repositories the app may access. For this we store the installation's identifier, the GitHub account's name and profile picture, and whether the app may access all or selected repositories. GitHub sends us a message on every push. You can disconnect the app at any time in your settings at GitHub. You can choose that an app builds on your own GitHub Actions instead of on our build servers, for each app or for every new app. Our GitHub App then commits the file `.github/workflows/blitz-cloud.yml` to that app's repository, and the Dockerfile we wrote for the project once it has put the app online, if the project has none. When the app needs a new version, we start that workflow. GitHub runs it on its own machines under its own terms and counts it toward your Actions minutes. The run sends us a token signed by GitHub that names the repository, the workflow and the run; we answer with what to build and a credential that can only store this app's images and expires with the build. Afterwards the run sends us the end of what the build printed, which we keep like any other build log (section 6). We store whether and when you made this choice, the commit our files went in with, and the run's address on GitHub. Switching it off stops this; the files stay in your repository until you delete them. You can also enter the address of any public git repository, for example on GitLab or Codeberg. We then read its branches without signing in and fetch the code of the chosen branch from that address. We store the address with the app. If you connect an account on GitLab, Gitea, Forgejo or Codeberg, you paste an access token from that server. We store it encrypted together with the server's address and your user name there, and never show it again. We use it only with that one server: to read your projects and their branches, fetch their code, and set up, renew and remove the push hook that tells us about a new push. You remove the connection under Settings, and you can also revoke the token on that server. When you delete your account, we delete the connection too. The legal basis is performing the contract (Art. 6(1)(b) GDPR). GitHub, GitLab or any other git host is responsible for what it does with your data itself. ## 8. AI assistance from Anthropic (Claude) For some steps we use the language model Claude by Anthropic. Anthropic never receives account data, your email address or the values of your apps' settings. What Anthropic receives depends on the step: - When you set up an image from Docker Hub: the image's name and version, the ports and folders it declares, and the names of its environment variables. - When we write a Dockerfile for a project that has none, or improve it after a failed build: the repository's name and commit, the list of files, the content of project files such as `package.json` or `requirements.txt`, the start of the README and of the file the program starts in, and after a failure the Dockerfile that was used and the end of the build output. - When we explain why a build or start failed and suggest steps to fix it: the same project details, the end of the output, and also the app's name and address, the names (not the values) of its settings and the names of your other apps. This also applies to projects that bring their own Dockerfile. - When a project has several Dockerfiles and we work out which one is for what: the same project details and the project's Dockerfiles. For a private repository this means parts of code you have not published. We keep the model's answers for 90 days, but not the questions. We keep the answer the live version of your app was built from for longer, see section 6. A Dockerfile written for a public repository is reused for the same repository for other customers too. The legal basis is performing the contract (Art. 6(1)(b) GDPR), since these steps are part of what blitz.cloud does for you. The provider is Anthropic PBC, 548 Market Street, PMB 90375, San Francisco, CA 94104, USA. Anthropic processes the data in the USA. The transfer is necessary to perform the contract with you (Art. 49(1)(b) GDPR). We use no other AI providers for blitz.cloud. What data Claude sees when it helps us run the operation is in section 16. ## 9. Paying for Pro through Stripe When you buy Pro, we handle the payment through Stripe. The provider is Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin 2, Ireland. When you go to the payment page we create a customer record at Stripe with your email address, your name and your blitz.cloud account's identifier. You enter your payment details directly at Stripe; card and bank details never reach our servers. Even when you try Pro free for 14 days, we create a customer record and a subscription in trial at Stripe, and Stripe keeps the card you add. Stripe processes your name, your email address, your billing address (for some purchases, such as a Pro app, only country and postcode), for businesses the VAT ID, the payment details and information about subscription, invoices and payments. From Stripe we only receive whether and until when your subscription runs, invoices and payment status, and for a trial a fingerprint of the card. The fingerprint identifies the card without showing its number. We use it only to check that each person gets one free trial (section 5). The legal basis is performing the contract for Pro (Art. 6(1)(b) GDPR). We keep invoices and accounting records for eight years, and books and annual accounts for ten years, as tax and commercial law require (Art. 6(1)(c) GDPR together with Section 147(1) and (3) AO, Section 257 HGB and Section 14b UStG). Stripe may also transfer data to the USA. The transfer is based on the European Commission's adequacy decision for the EU-US Data Privacy Framework, under which Stripe is certified, and on standard contractual clauses. More at [stripe.com/privacy](https://stripe.com/privacy). You can also cancel Pro without signing in, on the cancel page. For that we process the email address and name you enter there, and the reason if you give one, and send you a confirmation (Art. 6(1)(c) GDPR together with Section 312k BGB). ## 10. Emails We send our emails from noreply@blitz.cloud through Google Workspace's mail relay. Google processes your email address and the email's content for this as our processor. The provider is Google Cloud EMEA Limited, 70 Sir John Rogerson's Quay, Dublin 2, Ireland. Google may also process data in the USA, based on the EU-US Data Privacy Framework and standard contractual clauses. We email you about these topics: - Account, security, plan and billing, and service notices (maintenance, incidents, changes to the terms). You can't unsubscribe from these while you have an account, because they are part of the contract (Art. 6(1)(b) GDPR). - Notices about your apps: failed and successful deploys, stopped apps, finished restores, overnight updates, and, in the first week after sign-up, up to two reminders if no app is online yet. They are on by default, and you can switch off each topic under Settings or with one click on the link in the email (Art. 6(1)(b) and (f) GDPR). - A weekly newsletter about what went live on blitz.cloud that week. We send it to every account that has not objected. The legal basis is our legitimate interest in telling you about our own service (Art. 6(1)(f) GDPR). New accounts see this notice when they sign up, and every issue repeats it. You can object at any time, free of charge (Art. 21(2) GDPR): with one click on the link in every newsletter or with the switch under Settings > Notifications. We then send you no more newsletters and keep a note of when and how you objected. - News about blitz.cloud, a few times a year at most, only if you switch it on under Settings (Art. 6(1)(a) GDPR). You can switch it off again at any time. We keep a log of which email went to whom, so we can answer questions about delivery (Art. 6(1)(f) GDPR). We delete the content after 30 days and the entry after 180 days. ## 11. Backup copies Every night we back up: - managed databases. We keep the copies of the last 7 nights on which a database was copied on the free plan, and of the last 30 on Pro. A database that sleeps with its apps is copied once just before it goes to sleep and not again while it sleeps, so its last copies stay until newer ones replace them after it wakes. Before every restore we save the current state, and that copy is kept for the same time. - on Pro, the files your apps keep. We keep these copies for 30 nights, the copy taken before a restore for 7 days. - the platform's own database, with all accounts and sign-in data. We keep these copies for 30 days, and an extra copy on our servers in Germany for 14 days. If you delete a database, we delete its backup copies with it. All backups are encrypted before they leave our servers and are stored separately from them, with our data centre operator in the EU (Finland). The legal basis is performing the contract (Art. 6(1)(b) GDPR) and our legitimate interest in being able to restore the service after a failure (Art. 6(1)(f) GDPR). ## 12. Private networks with Tailscale or WireGuard You can set apps to be reachable only from your own private network. With Tailscale you sign in at Tailscale and so add a blitz.cloud device to your Tailscale network. The device is named after your address (such as `blitz-lena`), and your private apps show up in it under their names. Tailscale learns what it learns for every device on your network: the device's name, addresses and connection times. The connections themselves are end-to-end encrypted. Tailscale is your own provider and processes this data under its own responsibility and privacy notice. We store your Tailscale network's name, the name of our device in it, when its key expires and, if you connected Tailscale with an OAuth client, that client's secret, encrypted. With WireGuard you upload a configuration file. We store it encrypted and only decrypt it to connect to your router. Nothing goes to third parties. You can also connect devices to our own WireGuard gateway, without a router or server of your own. For each device you add in the dashboard we store the name you give it, its public key, the tunnel address we assign it and when you added it. The private key is in the configuration file and the QR code we show you once. We do not keep it. While a device is connected, the gateway knows its current internet address and when it last connected. That stays in the gateway's memory and is not written to a log. Only traffic to your own private apps goes through the gateway. Everything else your device sends, such as visits to other websites, does not pass through us. The gateway decrypts the tunnel and passes the traffic on to your app inside our network in the EU. We do not record or read that traffic. Nothing goes to third parties. The legal basis is performing the contract (Art. 6(1)(b) GDPR). We delete the data when you disconnect the network or delete your account, and a device's data as soon as you remove the device. ## 13. Deleting your account and downloading your data Under Settings you can download everything we hold about your account as one JSON file. It includes the values of your apps' settings, which is why it asks for a sign-in within the last hour. The file does not contain your apps' files or what your databases hold. You can copy those yourself with your databases' connection details. Under Settings you can also delete your account. We then: - remove your sign-in, which ends every session, - end a running Pro subscription at once, - delete all apps, databases, custom domains, DNS records, settings, build logs, traffic numbers and the AI's answers about your projects, and your apps' files together with the storage they were on, - delete your API keys, connected AI assistants, private networks and email settings, your usage history, your answers to the price questions, your invites and the random number for measuring sign-ups, - delete the backup copies of your databases within a day and the backup copies of your app files the following night, - delete the archived copy of your account's files (section 2), - release your address again after 14 days. What stays is a record without email address and without name that only carries the account's internal identifier, the account's change log for three years after each entry, and, if you paid for Pro, the identifiers of your customer and subscription record at Stripe, so invoices stay assignable. Its entries hold that identifier and, where an action concerned one, the name of an app, a database or a custom domain. We keep it so we can still trace later what happened to an account, for example in a case of abuse or a complaint (Art. 6(1)(f) GDPR). We keep invoices as long as the law requires (section 9). Your account data remains in the platform database's backup for up to 30 more days, until those copies are deleted as scheduled. If we close an account because of a serious breach of our terms, we keep its email address for three years after the closure so that nobody can sign up with it again (Art. 6(1)(f) GDPR). After that we remove it as if you had deleted the account yourself. ## 14. The content of your apps: us as processor For personal data your apps process, such as your users' data in a database or the IP addresses of your app's visitors, you are the controller. We store and process it only on your behalf and on your instructions, as a processor under Art. 28 GDPR. You can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF once you are signed in, in the dashboard under Settings, Privacy. Requests to your apps also pass through Cloudflare (section 3), except on custom domains. Your apps' files and databases are stored on our servers in Germany, the backup copies in the EU (Finland). As section 8 describes, parts of your code may go to Anthropic during builds and troubleshooting. How we detect abuse is below. If someone reports content of an app to us as illegal, we look at the reported content (Art. 6(1)(c) GDPR together with Art. 16 DSA). Beyond that we do not analyse the content of your apps. ### Detecting abuse To detect abuse (terms section 8), we watch for these signs: - An automated check searches the Dockerfile, the build output and the start command of your apps for clear signs of cryptocurrency mining. - We compare how much computing time, memory, builds, requests and AI steps an account needs against other accounts. - We see whether an app runs a known VPN or proxy program, or runs a long time without anyone calling it. - We see whether the names of an app's environment variables match the key names of known proxy-pool providers. We look at the names only, not the values. - We see whether an account uses a disposable address or the address of a privacy-focused mail provider and recreates its first app within an hour, and whether several accounts were created or signed in to from the same IP address (section 5). - We see whether several accounts sign up with the same custom mail domain on the same day or choose the same display name with the same mail domain, and whether several accounts create apps from repositories of the same GitHub account or from images by the same author. - We see whether an app comes from a known image or repository used to resell access to an AI subscription to others. We look more closely at accounts with such signs. AI tools help us with this (section 16). The legal basis is our legitimate interest in protecting the platform and every customer from abuse (Art. 6(1)(f) GDPR). What can follow from this is in section 19. ### The "Made with blitz.cloud" link On the free plan, and on Pro and Power when the app's owner turns it on, the HTML pages of an app show a small "Made with blitz.cloud" link (terms, section 9). It is part of the page the app delivers. It loads nothing from blitz.cloud or any other server, sets no cookie, stores nothing in the browser and sends us nothing. If a visitor hides it, that only applies to the page they are on. We only learn about a visitor if they click the link and come to blitz.cloud. From then on this policy applies as for any visit (section 3), and the browser may tell us the address of the page they came from. ## 15. Feedback and failure reports When you write to us through "Give feedback" or "Missing a feature?" in the dashboard, your message goes by email to our inbox feedback@blitzworks.io, with your email address, your plan and the page you were on. When a build or deploy fails for good, we send ourselves a failure report to the same inbox. It contains your email address, your name, your address and your plan, details about the app and the repository, the build logs and the AI's answers. We use both to answer you and to improve blitz.cloud (Art. 6(1)(b) and (f) GDPR). The inbox is hosted by Google Workspace (section 10). ### Reports of illegal content If you report content to us as illegal (see the imprint), we process your name, your email address and what your report says. We need them to look into the report, confirm that we received it and tell you our decision (Art. 6(1)(c) GDPR together with Art. 16 DSA). We do not give your name and email address to the customer whose app is affected, unless you agree or a law obliges us to. If there is a suspicion of a criminal offence that threatens people's life or safety, we pass the report on to the competent authorities (Art. 18 DSA). We keep reports until claims arising from our decision are time-barred (Sections 195 and 199 BGB). The inbox hallo@blitzworks.io is also hosted by Google Workspace. The form carries a Cloudflare Turnstile check (section 5). ## 16. Who else sees your data Within BlitzWorks, only the people who run blitz.cloud and help you see your data. We use AI tools for this: Claude by Anthropic (section 8) helps us answer your messages, check accounts for abuse and fix incidents. For this it sees the data a given task needs, such as your message, your email address, your plan and the details of your apps and builds. Anthropic processes this data in the USA. The legal basis is performing the contract (Art. 6(1)(b) GDPR) and our legitimate interest in a secure and efficient operation (Art. 6(1)(f) GDPR). Our data centre operator in Germany provides servers, network and the storage for backup copies and images and acts as our processor. We do not sell data. For advertising, data only goes to Google and its partners when you visit the blitz.cloud website, or the dashboard on the free plan, as section 3 describes. We never pass on data from your account or your apps for advertising. We only give data to authorities where the law obliges us to. ## 17. Your rights You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20). You can withdraw consent at any time with effect for the future (Art. 7(3)). You can do much of this yourself in the dashboard: change your name and email address, download your data, delete your account. For everything else write to hallo@blitzworks.io. ### Right to object Where we process data on the basis of our legitimate interest (Art. 6(1)(f) GDPR), you can object at any time on grounds relating to your particular situation (Art. 21 GDPR). We then stop processing the data, unless we can show compelling legitimate grounds that override your interests, or we need it to establish, exercise or defend legal claims. You can also complain to a data protection supervisory authority. The one responsible for us is the Bayerisches Landesamt für Datenschutzaufsicht, Promenade 18, 91522 Ansbach, Germany, [www.lda.bayern.de](https://www.lda.bayern.de). ## 18. Data you have to provide For an account we need your email address, and for Pro also the details Stripe asks for to take the payment. Without them we cannot make a contract with you. Everything else is voluntary. ## 19. Automated decisions Technical rules described in our terms and on our pages run automatically, for example that an app on the free plan goes to sleep after 30 minutes without visits or is stopped after 15 failed starts. The classification for plan planning (section 6) has no such effect. Some decisions we make without a human. If our automated check finds clear signs that an app mines cryptocurrency (terms section 8), it pauses the app at once. This protects the servers all customers share, and with them the performance of our contracts with you and everyone else (Art. 22(2)(a) GDPR). You get an email about it. If you reply, a human reviews the decision. You can state your point of view and contest the decision (Art. 22(3) GDPR). An app that stands out in the abuse check (section 14) can also be paused without a human reviewing the decision first, because AI tools carry out that check. You get an email about it. A human reviews the decision once you reply. If our automated check finds a known VPN, proxy or tunnel program in an app (terms section 8), it pauses the app at once and, unless the account has a paid plan or a trial with a card, also suspends the account. A list of programs we have confirmed as abuse decides this, without a person checking first. This protects the servers and the network all customers share, and with them the performance of our contracts with you and everyone else (Art. 22(2)(a) GDPR). You get an email with the reason. If you reply, a human reviews the decision, and you can state your point of view and contest it (Art. 22(3) GDPR). In every other case we suspend or close an account only after a human decides. Whether we offer you the free Pro trial is also decided automatically (section 5). You can still buy Pro. If you write to us, a human looks at the decision. We make no other decisions based solely on automated processing that have legal effects on you or affect you in a similarly significant way. ## 20. Changes We update this privacy policy when blitz.cloud or the law changes. The version published here applies. We tell you about significant changes by email. --- # Right of withdrawal for blitz.cloud URL: https://blitz.cloud/withdrawal/ Updated: 2026-10-18 The right of withdrawal for consumers who buy blitz.cloud Pro, Power, a Pro app or a domain, with the model withdrawal form. The right of withdrawal applies to consumers who buy a paid plan (Pro or Power, monthly or yearly) or a Pro app, or buy a domain. The free plan costs nothing; you can end it any time by deleting your account. This is a translation of the German withdrawal notice, which follows the statutory model. If the two differ, the German version applies. ## Right of withdrawal You have the right to withdraw from this contract within fourteen days without giving any reason. The withdrawal period is fourteen days from the day the contract is concluded. To exercise your right of withdrawal, you must inform us (BlitzWorks UG (haftungsbeschränkt), Graßer Weg 73, 93053 Regensburg, Germany, email: hallo@blitzworks.io) of your decision to withdraw from this contract by a clear statement (for example a letter sent by post or an email). You can use the model withdrawal form below, but you don't have to. To meet the withdrawal deadline, it is enough that you send your notice of withdrawal before the withdrawal period has expired. ## Effects of withdrawal If you withdraw from this contract, we will refund all payments we have received from you, including delivery costs (except for any extra costs from choosing a type of delivery other than the cheapest standard delivery we offer), without undue delay and no later than fourteen days from the day we receive your notice of withdrawal. We will use the same means of payment you used for the original transaction, unless you have expressly agreed otherwise; in no case will you be charged any fees for this refund. If you asked for the services to begin during the withdrawal period, you must pay us a reasonable amount in proportion to the services already provided up to the time you inform us that you are withdrawing from this contract, compared with the full scope of the services in the contract. ## Model withdrawal form (Complete and return this form only if you wish to withdraw from the contract.) To BlitzWorks UG (haftungsbeschränkt), Graßer Weg 73, 93053 Regensburg, Germany, email: hallo@blitzworks.io: I/We (\*) hereby give notice that I/We (\*) withdraw from my/our (\*) contract of sale of the following goods (\*)/for the provision of the following service (\*) Ordered on (\*)/received on (\*) Name of consumer(s) Address of consumer(s) Signature of consumer(s) (only if this form is sent on paper) Date (\*) Delete as appropriate. ## Starting Pro straight away Pro starts right after you pay, which is inside the withdrawal period. That is why you confirm before paying that you want Pro to start straight away. If you withdraw, we refund the amount minus the share for the days you already had Pro. With the free trial with a card (section 5a of the [terms](/terms/)), the withdrawal period starts with the order at the start of the trial. If you withdraw before the first charge, you pay nothing. If we have charged already, we refund the amount minus the share for the days after the trial on which you had Pro. If you only want Pro not to renew, [cancelling](/cancel/) is the simpler way: Pro then runs to the end of the month you have paid for. ## Domains: the right of withdrawal ends with the registration We register a domain right after you pay, which is inside the withdrawal period. With the registration we have done everything the contract asks of us: the domain is then held by the registry in your name and can't be given back. That is why, before paying, you expressly ask us to register it right away and confirm that you know your right of withdrawal ends once it is registered (section 356 (4) BGB). We confirm both in the mail about the registration. If you withdraw before the registration has gone through, we refund everything. If the registry doesn't register the domain, we refund everything as well. Once it is registered, you can only cancel it (section 5c of the [terms](/terms/)). For the Pro app that comes with a domain on the free plan, the right of withdrawal above applies unchanged. --- # blitz.cloud imprint URL: https://blitz.cloud/imprint/ Updated: 2026-10-03 Legal notice for blitz.cloud under Section 5 DDG - who runs blitz.cloud and how to reach us. This is the English version of the German imprint (Impressum), which German law requires. If the two differ, the German one applies. ## Information under Section 5 DDG BlitzWorks UG (haftungsbeschränkt)\ Graßer Weg 73\ 93053 Regensburg\ Germany Represented by its managing director Simon Gloël Register court: Amtsgericht Regensburg\ Register number: HRB 21609 ## Contact Email: hallo@blitzworks.io ## Contact points under the Digital Services Act Authorities of the Member States, the European Commission and the European Board for Digital Services can reach our single point of contact under Art. 11 of Regulation (EU) 2022/2065 (Digital Services Act, DSA) at hallo@blitzworks.io. Users of blitz.cloud can reach us under Art. 12 DSA at the same address. A human answers you there, not only an automated system. You can write to us in German or English. ## Reporting illegal content If you find content in an app on blitz.cloud that you think is illegal, write to hallo@blitzworks.io (Art. 16 DSA). So that we can look into it, please give us: - the exact address (URL) of the content, - why you think the content is illegal, - your name and email address, - and a statement that what you tell us is correct and complete to the best of your knowledge. If the report is about the sexual abuse of children, you do not have to give your name and email address. We confirm that we received your report and look into it. Then we tell you what we decided, whether automated means were involved, and what you can do if you disagree. What is not allowed on blitz.cloud is in section 8 of the [terms](/terms/). ## VAT ID VAT identification number under Section 27a UStG: DE455125901 ## Professional liability insurance Information under Section 2(1) No. 11 DL-InfoV: Insurer: Hiscox SA, Niederlassung für Deutschland, Bernhard-Wicki-Straße 3, 80636 München, Germany\ Type of insurance: IT liability insurance covering professional indemnity (financial loss) and general business liability\ Sums insured: 125,000 EUR for financial loss, 3,000,000 EUR for personal injury and property damage including environmental damage, each capped at three times that amount per year\ Territorial scope: worldwide; for general liability excluding claims brought before courts in the USA or Canada or under their law ## Responsible for content under Section 18(2) MStV Simon Gloël, address as above. ## Consumer dispute resolution We are neither willing nor obliged to take part in dispute resolution proceedings before a consumer arbitration board. --- # Cancel your contract URL: https://blitz.cloud/cancel/ Updated: 2026-10-01 Cancel blitz.cloud Pro or Power without signing in. It takes effect at once, and you get a confirmation by email with the day your plan ends. Here you cancel your paid plan on blitz.cloud, Pro or Power, and your Pro apps, even without signing in. Enter the email address you sign in to blitz.cloud with. The cancellation takes effect as soon as you send the form. If you pay monthly, your plan runs to the end of the month you have paid for and isn't renewed after that. If you pay yearly, it ends at the end of the first year while you are in it. After the first year it ends one month after you cancel, and we refund the rest by day. A yearly Pro app follows the same rule. By email you get a confirmation with the date and time of your cancellation and the day your plan ends. Because anyone can fill in this form, we also tell the account's owner by email, with a button to keep the plan if it wasn't them. If you are signed in, you can also cancel in the dashboard under Settings, in the Plan and usage section. To end the free plan, delete your account in Settings. ## What happens after you cancel Nothing is deleted. Your account moves to the free plan. If it uses no more than the free plan includes, that is all that changes. If your account uses more than the free plan allows, nothing happens for 14 days. You will be told by email what is over the limit. Your apps keep running as before during that time. After 14 days, the newest apps are paused until the rest fit inside the free plan's limits. The newest databases are paused until only one is left. Your own domains stop pointing at your apps. Apps you kept awake go back to sleeping when no one visits. Everything stays in place: addresses, settings, files and data. If you take Pro again, paused apps and databases restart by themselves. ## Refunds Time you have already paid for is not refunded, except for the yearly plan or a yearly Pro app after its first year, or if you use your right of withdrawal. Within 30 days of your first Pro payment, you can ask for that first month back in full. Send an email to hallo@blitzworks.io and we will refund it. This applies once per account. --- # Report illegal content URL: https://blitz.cloud/report/ Updated: 2026-09-27 Report illegal content hosted on blitz.cloud. No account needed. We confirm receipt by email and tell you what we decided. If you believe an app or a page on blitz.cloud carries illegal content, tell us here. You do not need an account. Give the exact address of the content and say why you believe it is illegal; your name and email are optional, but without an email we cannot confirm receipt or tell you what we decided. Fraud and support read every report. We confirm we received it as soon as it arrives, and write back once we have decided what to do. This is for illegal content: something that breaks the law, such as fraud, counterfeit goods, hate speech or content that infringes somebody's rights. For content that breaks our own [terms](/terms/#8-what-is-not-allowed-on-blitz-cloud) but is not illegal, write to hallo@blitzworks.io instead. --- # 9router hosting in the EU URL: https://blitz.cloud/apps/9router/ Updated: 2026-10-14 Run your own 9router, an alternative to OpenRouter and LiteLLM. One-click install, HTTPS, servers in the EU. Free plan, no card. 9router: send your AI coding tools through one address and switch to another provider when one runs out. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to OpenRouter and LiteLLM 9router does the job of OpenRouter or LiteLLM, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | 9router | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of 9router](/get/9router/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `9router.yourname.blitz.cloud`. 4. Open the app's address and sign in with this password. 5. Connect the AI providers you use, then create an API key for your tools. ## While it sleeps 9router only answers your tools while it is awake. On the free plan a request from a tool doesn't wake it. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing 9router keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Deploy button for your README Do you maintain 9router or write about it? Put this button in a README or a post. A click opens 9router in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host 9router for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my 9router data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for 9router? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is 9router backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does 9router get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Activepieces hosting in the EU URL: https://blitz.cloud/apps/activepieces/ Updated: 2026-10-14 Run your own Activepieces, an alternative to Zapier and Make. One-click install, HTTPS, servers in the EU. Free plan, no card. Activepieces: connect your apps and automate chores by clicking steps together, no code needed. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS and the PostgreSQL and Redis it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Zapier, Make, n8n and IFTTT Activepieces does the job of Zapier, Make, n8n or IFTTT, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Activepieces | |---|---| | Memory | 256 MB reserved from your plan | | Storage | none | | Database | PostgreSQL and Redis, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Activepieces](/get/activepieces/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `activepieces.yourname.blitz.cloud`. 4. Open the app's address and sign up. The first account becomes the admin. 5. Build a flow from a trigger, like a new email or a schedule, and add the steps it should run. ## While it sleeps Activepieces only runs its schedules while it is awake. On the free plan webhooks don't wake it. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing Activepieces keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Good to know It uses most of its memory before it does anything, so large flows may make it restart. ## Deploy button for your README Do you maintain Activepieces or write about it? Put this button in a README or a post. A click opens Activepieces in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Activepieces for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Activepieces data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Activepieces? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Activepieces backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Activepieces get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Actual Budget hosting in the EU URL: https://blitz.cloud/apps/actual-budget/ Updated: 2026-10-14 Run your own Actual Budget, an alternative to YNAB and Mint. One-click install, HTTPS, servers in the EU. Free plan, no card. Actual Budget: A budget app that shows where your money goes, without selling what it learns. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to YNAB, Mint and Quicken Actual Budget does the job of YNAB, Mint or Quicken, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Actual Budget | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Actual Budget](/get/actual-budget/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `actual.yourname.blitz.cloud`. 4. Open the app's address and choose a password. Until you do, anyone who finds the address could. 5. Start a new budget, or import one from YNAB or another app on the same screen. ## Deploy button for your README Do you maintain Actual Budget or write about it? Put this button in a README or a post. A click opens Actual Budget in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Actual Budget for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Actual Budget data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Actual Budget? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Actual Budget backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Actual Budget get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Audiobookshelf hosting in the EU URL: https://blitz.cloud/apps/audiobookshelf/ Updated: 2026-10-14 Run your own Audiobookshelf, an alternative to Audible and Apple Books. One-click install, HTTPS, servers in the EU. Free plan, no card. Audiobookshelf: your audiobooks and podcasts on every phone, and it remembers where you stopped. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 5 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Audible, Apple Books and Pocket Casts Audiobookshelf does the job of Audible, Apple Books or Pocket Casts, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Audiobookshelf | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 5 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Audiobookshelf](/get/audiobookshelf/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `audiobookshelf.yourname.blitz.cloud`. 4. Open the app's address and create the root account. Until you do, anyone who finds the address could. 5. Add a library for /audiobooks or /podcasts, then upload books from the Upload page. ## Deploy button for your README Do you maintain Audiobookshelf or write about it? Put this button in a README or a post. A click opens Audiobookshelf in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Audiobookshelf for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Audiobookshelf data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Audiobookshelf? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Audiobookshelf backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Audiobookshelf get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Beszel hosting in the EU URL: https://blitz.cloud/apps/beszel/ Updated: 2026-10-14 Run your own Beszel, an alternative to Netdata and Uptime Kuma. One-click install, HTTPS, servers in the EU. Free plan, no card. Beszel: watch CPU, memory, disk and network for your own servers from one lightweight dashboard. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Netdata and Uptime Kuma Beszel does the job of Netdata or Uptime Kuma, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Beszel | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Beszel](/get/beszel/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `beszel.yourname.blitz.cloud`. 4. Open the app's address and create the first account. It becomes the admin. 5. Install a Beszel agent on the machine you want to watch and point it at the app's address. ## Good to know Only the hub: it shows nothing until an agent running on another machine connects and reports its numbers to it. ## Deploy button for your README Do you maintain Beszel or write about it? Put this button in a README or a post. A click opens Beszel in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Beszel for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Beszel data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Beszel? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Beszel backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Beszel get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # BookStack hosting in the EU URL: https://blitz.cloud/apps/bookstack/ Updated: 2026-10-14 Run your own BookStack, an alternative to Confluence and Notion. One-click install, HTTPS, servers in the EU. Free plan, no card. BookStack: A wiki built like a library, with books, chapters and pages for everything your team writes down. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 2 GB of storage and the MariaDB it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Confluence, Notion and GitBook BookStack does the job of Confluence, Notion or GitBook, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | BookStack | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 2 GB | | Database | MariaDB, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of BookStack](/get/bookstack/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `bookstack.yourname.blitz.cloud`. 4. Open the app's address and sign in with admin@admin.com / password, the default login. Change it at once under your profile. 5. Books hold chapters and pages; start by creating your first book from the dashboard. ## Deploy button for your README Do you maintain BookStack or write about it? Put this button in a README or a post. A click opens BookStack in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host BookStack for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my BookStack data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for BookStack? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is BookStack backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does BookStack get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # ByteStash hosting in the EU URL: https://blitz.cloud/apps/bytestash/ Updated: 2026-10-14 Run your own ByteStash, an alternative to GitHub Gist and Pastebin. One-click install, HTTPS, servers in the EU. Free plan, no card. ByteStash: save and search the code snippets you keep reusing. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to GitHub Gist and Pastebin ByteStash does the job of GitHub Gist or Pastebin, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | ByteStash | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of ByteStash](/get/bytestash/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `bytestash.yourname.blitz.cloud`. 4. Open the app's address and make your own account first. 5. Then turn ALLOW_NEW_ACCOUNTS off in Settings so nobody else can sign up. ## Deploy button for your README Do you maintain ByteStash or write about it? Put this button in a README or a post. A click opens ByteStash in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host ByteStash for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my ByteStash data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for ByteStash? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is ByteStash backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does ByteStash get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Calibre-Web hosting in the EU URL: https://blitz.cloud/apps/calibre-web/ Updated: 2026-10-14 Run your own Calibre-Web, an alternative to Calibre and Kindle library. One-click install, HTTPS, servers in the EU. Free plan, no card. Calibre-Web: browse and read your ebook collection in the browser, with covers, search and an online reader. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 5 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Calibre and Kindle library Calibre-Web does the job of Calibre or Kindle library, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Calibre-Web | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 5 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Calibre-Web](/get/calibre-web/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `calibre.yourname.blitz.cloud`. 4. Open the app's address and sign in with admin / admin123, the default login. Change it at once under Admin. 5. Upload a Calibre library folder into the app's storage with FileBrowser Quantum, then set its path on the setup page. ## Good to know Reads an existing Calibre library, it does not create one. Upload a library folder (with its metadata.db) into the app's storage with FileBrowser Quantum, then point Calibre-Web at it from the setup page. ## Deploy button for your README Do you maintain Calibre-Web or write about it? Put this button in a README or a post. A click opens Calibre-Web in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Calibre-Web for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Calibre-Web data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Calibre-Web? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Calibre-Web backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Calibre-Web get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Changedetection.io hosting in the EU URL: https://blitz.cloud/apps/changedetection/ Updated: 2026-10-14 Run your own Changedetection.io, an alternative to Visualping and Distill.io. One-click install, HTTPS, servers in the EU. Free plan, no card. Changedetection.io: watch any website for changes and get a message the moment something you care about is updated. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Visualping and Distill.io Changedetection.io does the job of Visualping or Distill.io, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Changedetection.io | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Changedetection.io](/get/changedetection/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `changedetection.yourname.blitz.cloud`. 4. Open the app's address and add the pages you want to watch. 5. Set a password under Settings > General so only you can open it. ## Good to know Nobody is asked for a password until you set one in Settings: until then, anyone who finds the address can see and change your watches. It only checks pages while it is awake. ## Deploy button for your README Do you maintain Changedetection.io or write about it? Put this button in a README or a post. A click opens Changedetection.io in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Changedetection.io for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Changedetection.io data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Changedetection.io? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Changedetection.io backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Changedetection.io get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Chevereto hosting in the EU URL: https://blitz.cloud/apps/chevereto/ Updated: 2026-10-14 Run your own Chevereto, an alternative to Imgur and ImageShack. One-click install, HTTPS, servers in the EU. Free plan, no card. Chevereto: run your own image and video host, with albums, galleries and links to share. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 5 GB of storage and the MariaDB it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Imgur and ImageShack Chevereto does the job of Imgur or ImageShack, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Chevereto | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 5 GB | | Database | MariaDB, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Chevereto](/get/chevereto/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `chevereto.yourname.blitz.cloud`. 4. Open the app's address and run the install wizard; it makes your admin account. ## Deploy button for your README Do you maintain Chevereto or write about it? Put this button in a README or a post. A click opens Chevereto in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Chevereto for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Chevereto data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Chevereto? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Chevereto backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Chevereto get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # cobalt hosting in the EU URL: https://blitz.cloud/apps/cobalt/ Updated: 2026-10-14 Run your own cobalt, an alternative to y2mate and SaveFrom. One-click install, HTTPS, servers in the EU. Free plan, no card. cobalt: save videos and music from sites like TikTok and SoundCloud through your own download API. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to y2mate, SaveFrom and yt-dlp cobalt does the job of y2mate, SaveFrom or yt-dlp, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | cobalt | |---|---| | Memory | 128 MB reserved from your plan | | Storage | none | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of cobalt](/get/cobalt/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `cobalt.yourname.blitz.cloud`. 4. Send a POST to the app's address from your private network with a JSON body like {"url":"..."} and the header Accept application/json. ## Good to know This is the download API without the cobalt website. YouTube and some other sites refuse downloads from servers like ours. ## Deploy button for your README Do you maintain cobalt or write about it? Put this button in a README or a post. A click opens cobalt in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host cobalt for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my cobalt data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for cobalt? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is cobalt backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does cobalt get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # code-server hosting in the EU URL: https://blitz.cloud/apps/code-server/ Updated: 2026-10-14 Run your own code-server, an alternative to VS Code and Gitpod. One-click install, HTTPS, servers in the EU. Free plan, no card. code-server: VS Code running in your browser, so you can code from any device with your own files. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 5 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to VS Code, Gitpod and GitHub Codespaces code-server does the job of VS Code, Gitpod or GitHub Codespaces, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | code-server | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 5 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of code-server](/get/code-server/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `code.yourname.blitz.cloud`. 4. Open the app's address and sign in with this password. 5. Open a folder under /home/coder and start editing; your files stay on the app's storage. ## Deploy button for your README Do you maintain code-server or write about it? Put this button in a README or a post. A click opens code-server in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host code-server for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my code-server data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for code-server? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is code-server backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does code-server get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # CommaFeed hosting in the EU URL: https://blitz.cloud/apps/commafeed/ Updated: 2026-10-14 Run your own CommaFeed, an alternative to Feedly and Google Reader. One-click install, HTTPS, servers in the EU. Free plan, no card. CommaFeed: read your RSS feeds in a fast, familiar reader. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS and the PostgreSQL it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Feedly and Google Reader CommaFeed does the job of Feedly or Google Reader, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | CommaFeed | |---|---| | Memory | 256 MB reserved from your plan | | Storage | none | | Database | PostgreSQL, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of CommaFeed](/get/commafeed/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `commafeed.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin / admin, then change the password. 5. Add the feeds you want to follow, grouped into categories on the left. ## Deploy button for your README Do you maintain CommaFeed or write about it? Put this button in a README or a post. A click opens CommaFeed in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host CommaFeed for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my CommaFeed data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for CommaFeed? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is CommaFeed backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does CommaFeed get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Dashy hosting in the EU URL: https://blitz.cloud/apps/dashy/ Updated: 2026-10-14 Run your own Dashy, an alternative to Heimdall and Homepage. One-click install, HTTPS, servers in the EU. Free plan, no card. Dashy: A start page for all the apps and sites you use, with status checks and widgets. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Heimdall, Homepage and Homarr Dashy does the job of Heimdall, Homepage or Homarr, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Dashy | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Dashy](/get/dashy/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `dashy.yourname.blitz.cloud`. 4. Open the app's address and add your first links through the UI, or edit conf.yml directly under the app's storage. ## Good to know No login on the dashboard page itself by default, so anyone with the address can see and edit it; this password only guards its status and config-saving endpoints. Add users under Dashy's own config for a real login. ## Deploy button for your README Do you maintain Dashy or write about it? Put this button in a README or a post. A click opens Dashy in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Dashy for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Dashy data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Dashy? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Dashy backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Dashy get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Docmost hosting in the EU URL: https://blitz.cloud/apps/docmost/ Updated: 2026-10-14 Run your own Docmost, an alternative to Notion and Confluence. One-click install, HTTPS, servers in the EU. Free plan, no card. Docmost: shared pages and a wiki for your team, with an editor that feels like Notion. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 2 GB of storage and the PostgreSQL and Redis it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Notion, Confluence and Outline Docmost does the job of Notion, Confluence or Outline, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Docmost | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 2 GB | | Database | PostgreSQL and Redis, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Docmost](/get/docmost/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `docmost.yourname.blitz.cloud`. 4. Open the app's address and create your workspace. Whoever does it first becomes its owner. 5. Invite your team from the workspace settings. Invitations are links you copy and send yourself. ## Deploy button for your README Do you maintain Docmost or write about it? Put this button in a README or a post. A click opens Docmost in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Docmost for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Docmost data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Docmost? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Docmost backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Docmost get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # DokuWiki hosting in the EU URL: https://blitz.cloud/apps/dokuwiki/ Updated: 2026-10-14 Run your own DokuWiki, an alternative to MediaWiki and Confluence. One-click install, HTTPS, servers in the EU. Free plan, no card. DokuWiki: A simple wiki that keeps every page as a plain text file, with no database to break. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to MediaWiki and Confluence DokuWiki does the job of MediaWiki or Confluence, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | DokuWiki | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of DokuWiki](/get/dokuwiki/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `dokuwiki.yourname.blitz.cloud`. 4. Open the app's address/install.php and create the admin account; it removes the install page itself when done. ## Deploy button for your README Do you maintain DokuWiki or write about it? Put this button in a README or a post. A click opens DokuWiki in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host DokuWiki for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my DokuWiki data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for DokuWiki? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is DokuWiki backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does DokuWiki get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Easy!Appointments hosting in the EU URL: https://blitz.cloud/apps/easy-appointments/ Updated: 2026-10-14 Run your own Easy!Appointments, an alternative to Calendly and Acuity Scheduling. One-click install, HTTPS, servers in the EU. Free plan, no card. Easy!Appointments: let people book a slot on your calendar, with reminders and no back and forth by mail. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage and the MariaDB it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Calendly and Acuity Scheduling Easy!Appointments does the job of Calendly or Acuity Scheduling, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Easy!Appointments | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | MariaDB, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Easy!Appointments](/get/easy-appointments/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `easy.yourname.blitz.cloud`. 4. Open the app's address; the installer makes your admin account and the first service. ## Good to know Booking confirmations and reminders need SMTP settings of your own mail provider, added after setup. ## Deploy button for your README Do you maintain Easy!Appointments or write about it? Put this button in a README or a post. A click opens Easy!Appointments in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Easy!Appointments for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Easy!Appointments data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Easy!Appointments? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Easy!Appointments backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Easy!Appointments get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Etherpad hosting in the EU URL: https://blitz.cloud/apps/etherpad/ Updated: 2026-10-14 Run your own Etherpad, an alternative to Google Docs and HedgeDoc. One-click install, HTTPS, servers in the EU. Free plan, no card. Etherpad: write a document together with other people, watching each other's edits appear live. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Google Docs, HedgeDoc and Notion Etherpad does the job of Google Docs, HedgeDoc or Notion, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Etherpad | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Etherpad](/get/etherpad/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `etherpad.yourname.blitz.cloud`. 4. Open the app's address/admin and sign in as admin with this password. 5. Create a pad at the app's address/p/yourpadname and share that address with the people you write with. ## Good to know Anyone who knows or guesses a pad's name can open and edit it; there is no per-pad access control here. ## Deploy button for your README Do you maintain Etherpad or write about it? Put this button in a README or a post. A click opens Etherpad in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Etherpad for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Etherpad data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Etherpad? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Etherpad backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Etherpad get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Evolution API hosting in the EU URL: https://blitz.cloud/apps/evolution-api/ Updated: 2026-10-14 Run your own Evolution API, an alternative to Twilio and WhatsApp Business API. One-click install, HTTPS, servers in the EU. Free plan, no card. Evolution API: send and receive WhatsApp messages from your own code through a simple API. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage and the PostgreSQL and Redis it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Twilio, WhatsApp Business API, Z-API and WAHA Evolution API does the job of Twilio, WhatsApp Business API, Z-API or WAHA, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Evolution API | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | PostgreSQL and Redis, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Evolution API](/get/evolution-api/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `evolution.yourname.blitz.cloud`. 4. Open the app's address/manager and sign in with this API key. 5. Create an instance, then scan its QR code with WhatsApp on your phone. ## While it sleeps Evolution API only connected to WhatsApp while it is awake, so messages and webhooks wait until then. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing Evolution API keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Good to know WhatsApp does not allow unofficial clients, so a number used this way can be banned. ## Deploy button for your README Do you maintain Evolution API or write about it? Put this button in a README or a post. A click opens Evolution API in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Evolution API for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Evolution API data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Evolution API? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Evolution API backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Evolution API get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Excalidraw hosting in the EU URL: https://blitz.cloud/apps/excalidraw/ Updated: 2026-10-14 Run your own Excalidraw, an alternative to Miro and FigJam. One-click install, HTTPS, servers in the EU. Free plan, no card. Excalidraw: A virtual whiteboard for sketches and diagrams that look hand-drawn. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Miro, FigJam and Google Jamboard Excalidraw does the job of Miro, FigJam or Google Jamboard, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Excalidraw | |---|---| | Memory | 128 MB reserved from your plan | | Storage | none | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Excalidraw](/get/excalidraw/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `excalidraw.yourname.blitz.cloud`. ## Good to know The editor only: nothing you draw is saved to the server, and there is no live collaboration here. Export your file before you close the tab. ## Deploy button for your README Do you maintain Excalidraw or write about it? Put this button in a README or a post. A click opens Excalidraw in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Excalidraw for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Excalidraw data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Excalidraw? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Excalidraw backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Excalidraw get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Fider hosting in the EU URL: https://blitz.cloud/apps/fider/ Updated: 2026-10-14 Run your own Fider, an alternative to Canny and UserVoice. One-click install, HTTPS, servers in the EU. Free plan, no card. Fider: collect feedback and feature requests from your users, and let them vote on what matters. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS and the PostgreSQL it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Canny and UserVoice Fider does the job of Canny or UserVoice, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Fider | |---|---| | Memory | 128 MB reserved from your plan | | Storage | none | | Database | PostgreSQL, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Fider](/get/fider/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `fider.yourname.blitz.cloud`. 4. Set EMAIL_SMTP_HOST, EMAIL_SMTP_PORT, EMAIL_SMTP_USERNAME and EMAIL_SMTP_PASSWORD under Environment to your mail provider before anyone tries to sign in. 5. Once mail works, open the app's address and sign in with your email. The first account becomes the admin. ## Good to know Sign-in works by mail link, so it needs a real mail server. It starts with placeholder EMAIL_SMTP_* settings that let it come up, but nobody can sign in until you set real ones under Environment. ## Deploy button for your README Do you maintain Fider or write about it? Put this button in a README or a post. A click opens Fider in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Fider for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Fider data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Fider? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Fider backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Fider get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # FileBrowser Quantum hosting in the EU URL: https://blitz.cloud/apps/filebrowser/ Updated: 2026-10-19 Run your own FileBrowser Quantum, an alternative to cPanel File Manager and FileZilla. One-click install, HTTPS, servers in the EU. Free plan, no card. FileBrowser Quantum: upload, download and sort the files your apps keep, from your browser. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to cPanel File Manager and FileZilla FileBrowser Quantum does the job of cPanel File Manager or FileZilla, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | FileBrowser Quantum | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## On blitz.cloud | Measured | FileBrowser Quantum | |---|---| | Installs on blitz.cloud | 25 or more | | Online after installing | about 15 seconds | | Waking up after a sleep | about 15 seconds | | Memory while awake | about 70 MB | | Version | 1.5-stable, on blitz.cloud since 5 October 2026 | Measured on 19 October 2026 across the FileBrowser Quantum apps on blitz.cloud. Times and memory are medians, installs a band, and nothing here comes from fewer than 5 installs. ## Install it 1. [Start the install of FileBrowser Quantum](/get/filebrowser/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `filebrowser.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with this password. 5. Each of your apps that keeps files has a folder here, named after the app, with the folders it keeps inside. ## Good to know It shows the folders your apps keep, not your databases. ## Deploy button for your README Do you maintain FileBrowser Quantum or write about it? Put this button in a README or a post. A click opens FileBrowser Quantum in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host FileBrowser Quantum for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my FileBrowser Quantum data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for FileBrowser Quantum? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is FileBrowser Quantum backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does FileBrowser Quantum get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Firefly III hosting in the EU URL: https://blitz.cloud/apps/firefly-iii/ Updated: 2026-10-14 Run your own Firefly III, an alternative to Mint and YNAB. One-click install, HTTPS, servers in the EU. Free plan, no card. Firefly III: keep track of every account, bill and budget in one place, with reports that show where it all went. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage and the PostgreSQL it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Mint, YNAB, Quicken and Moneydance Firefly III does the job of Mint, YNAB, Quicken or Moneydance, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Firefly III | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | PostgreSQL, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Firefly III](/get/firefly-iii/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `firefly.yourname.blitz.cloud`. 4. Open the app's address and register. The first account is the owner. 5. Add your bank accounts, then import a statement or enter your first transactions. ## Good to know Recurring transactions and bill reminders need a daily job to call the app, and nothing here does that for you yet. ## Deploy button for your README Do you maintain Firefly III or write about it? Put this button in a README or a post. A click opens Firefly III in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Firefly III for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Firefly III data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Firefly III? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Firefly III backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Firefly III get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # flatnotes hosting in the EU URL: https://blitz.cloud/apps/flatnotes/ Updated: 2026-10-14 Run your own flatnotes, an alternative to Obsidian and Notion. One-click install, HTTPS, servers in the EU. Free plan, no card. flatnotes: write quick notes as plain markdown files, searchable the moment you save them. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Obsidian and Notion flatnotes does the job of Obsidian or Notion, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | flatnotes | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of flatnotes](/get/flatnotes/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `flatnotes.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with this password. ## Deploy button for your README Do you maintain flatnotes or write about it? Put this button in a README or a post. A click opens flatnotes in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host flatnotes for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my flatnotes data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for flatnotes? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is flatnotes backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does flatnotes get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Forgejo hosting in the EU URL: https://blitz.cloud/apps/forgejo/ Updated: 2026-10-14 Run your own Forgejo, an alternative to GitHub and GitLab. One-click install, HTTPS, servers in the EU. Free plan, no card. Forgejo: your own place for Git repositories, issues and pull requests, like a small GitHub. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 2 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to GitHub, GitLab, Bitbucket and Gitea Forgejo does the job of GitHub, GitLab, Bitbucket or Gitea, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Forgejo | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 2 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Forgejo](/get/forgejo/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `forgejo.yourname.blitz.cloud`. 4. Open the app's address and register. The first account becomes the admin. 5. Then set FORGEJO__service__DISABLE_REGISTRATION to true in Environment so nobody else can sign up. ## Good to know Git over SSH does not reach apps here, so you push and pull over HTTPS with a password or an access token. ## Deploy button for your README Do you maintain Forgejo or write about it? Put this button in a README or a post. A click opens Forgejo in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Forgejo for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Forgejo data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Forgejo? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Forgejo backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Forgejo get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # FreshRSS hosting in the EU URL: https://blitz.cloud/apps/freshrss/ Updated: 2026-10-14 Run your own FreshRSS, an alternative to Feedly and Inoreader. One-click install, HTTPS, servers in the EU. Free plan, no card. FreshRSS: all your news feeds in one calm, ad-free reader. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Feedly, Inoreader and Google Reader FreshRSS does the job of Feedly, Inoreader or Google Reader, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | FreshRSS | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of FreshRSS](/get/freshrss/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `freshrss.yourname.blitz.cloud`. 4. Open the app's address and go through the short setup. The account you create there is the admin. 5. Add the feeds of the sites you read, or import an OPML file from your old reader. ## While it sleeps FreshRSS only fetches new articles while it is awake. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing FreshRSS keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Deploy button for your README Do you maintain FreshRSS or write about it? Put this button in a README or a post. A click opens FreshRSS in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host FreshRSS for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my FreshRSS data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for FreshRSS? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is FreshRSS backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does FreshRSS get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Fusion hosting in the EU URL: https://blitz.cloud/apps/fusion/ Updated: 2026-10-14 Run your own Fusion, an alternative to Feedly and Inoreader. One-click install, HTTPS, servers in the EU. Free plan, no card. Fusion: follow RSS feeds from one clean inbox. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Feedly and Inoreader Fusion does the job of Feedly or Inoreader, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Fusion | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Fusion](/get/fusion/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `fusion.yourname.blitz.cloud`. 4. Open the app's address and sign in with this password. 5. Add the feeds you want to follow from the + button. ## Deploy button for your README Do you maintain Fusion or write about it? Put this button in a README or a post. A click opens Fusion in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Fusion for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Fusion data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Fusion? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Fusion backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Fusion get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Ghost hosting in the EU URL: https://blitz.cloud/apps/ghost/ Updated: 2026-10-19 Run your own Ghost, an alternative to Substack and Medium. One-click install, HTTPS, servers in the EU. Free plan, no card. Ghost: A beautiful blog and newsletter, ready to write in. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 2 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Substack, Medium and WordPress.com Ghost does the job of Substack, Medium or WordPress.com, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Ghost | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 2 GB | | Database | none | | Plan | Free or Pro | ## On blitz.cloud | Measured | Ghost | |---|---| | Installs on blitz.cloud | 10 or more | | Online after installing | about 35 seconds | | Waking up after a sleep | about 60 seconds | | Memory while awake | about 150 MB | | Version | 6-alpine, on blitz.cloud since 16 October 2026 | Measured on 19 October 2026 across the Ghost apps on blitz.cloud. Times and memory are medians, installs a band, and nothing here comes from fewer than 5 installs. ## Install it 1. [Start the install of Ghost](/get/ghost/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `ghost.yourname.blitz.cloud`. 4. Open the app's address/ghost and set up your account. Until you do, anyone who finds that page could. ## Deploy button for your README Do you maintain Ghost or write about it? Put this button in a README or a post. A click opens Ghost in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Ghost for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Ghost data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Ghost? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Ghost backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Ghost get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Gitea hosting in the EU URL: https://blitz.cloud/apps/gitea/ Updated: 2026-10-14 Run your own Gitea, an alternative to GitHub and GitLab. One-click install, HTTPS, servers in the EU. Free plan, no card. Gitea: your own place for Git repositories, issues and pull requests, like a small GitHub. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 2 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to GitHub, GitLab and Forgejo Gitea does the job of GitHub, GitLab or Forgejo, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Gitea | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 2 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Gitea](/get/gitea/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `gitea.yourname.blitz.cloud`. 4. Open the app's address and register. The first account becomes the admin. 5. Push and pull over HTTPS with the app's address in the address. ## Good to know Git over SSH does not reach apps here, so you push and pull over HTTPS with a password or an access token. ## Deploy button for your README Do you maintain Gitea or write about it? Put this button in a README or a post. A click opens Gitea in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Gitea for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Gitea data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Gitea? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Gitea backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Gitea get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Gokapi hosting in the EU URL: https://blitz.cloud/apps/gokapi/ Updated: 2026-10-14 Run your own Gokapi, an alternative to WeTransfer and Firefox Send. One-click install, HTTPS, servers in the EU. Free plan, no card. Gokapi: share a file with a link that expires when you decide it should. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to WeTransfer and Firefox Send Gokapi does the job of WeTransfer or Firefox Send, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Gokapi | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Gokapi](/get/gokapi/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `gokapi.yourname.blitz.cloud`. 4. Open the app's address/setup, choose your admin login, and give the app's address as the public address. 5. Anyone with a share link can download the file until it expires or you delete it. ## Deploy button for your README Do you maintain Gokapi or write about it? Put this button in a README or a post. A click opens Gokapi in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Gokapi for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Gokapi data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Gokapi? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Gokapi backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Gokapi get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Gonic hosting in the EU URL: https://blitz.cloud/apps/gonic/ Updated: 2026-10-14 Run your own Gonic, an alternative to Spotify and Plex. One-click install, HTTPS, servers in the EU. Free plan, no card. Gonic: stream your own music and podcasts to any Subsonic app. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 5 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Spotify and Plex Gonic does the job of Spotify or Plex, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Gonic | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 5 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Gonic](/get/gonic/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `gonic.yourname.blitz.cloud`. 4. Sign in at the app's address as admin / admin and change the password straight away. 5. Add music to the account's files with FileBrowser Quantum, then point a Subsonic app at the app's address. ## Deploy button for your README Do you maintain Gonic or write about it? Put this button in a README or a post. A click opens Gonic in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Gonic for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Gonic data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Gonic? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Gonic backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Gonic get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Gotify hosting in the EU URL: https://blitz.cloud/apps/gotify/ Updated: 2026-10-14 Run your own Gotify, an alternative to Pushover and ntfy. One-click install, HTTPS, servers in the EU. Free plan, no card. Gotify: A simple server for push notifications from your own scripts and services. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Pushover and ntfy Gotify does the job of Pushover or ntfy, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Gotify | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Gotify](/get/gotify/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `gotify.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with this password. Change it under the user menu. 5. Create an application under Apps to get a token, then send a message to it with curl. ## Deploy button for your README Do you maintain Gotify or write about it? Put this button in a README or a post. A click opens Gotify in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Gotify for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Gotify data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Gotify? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Gotify backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Gotify get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Grocy hosting in the EU URL: https://blitz.cloud/apps/grocy/ Updated: 2026-10-14 Run your own Grocy, an alternative to AnyList and Out of Milk. One-click install, HTTPS, servers in the EU. Free plan, no card. Grocy: track groceries, chores and household items, with reminders before anything runs out or expires. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to AnyList and Out of Milk Grocy does the job of AnyList or Out of Milk, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Grocy | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Grocy](/get/grocy/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `grocy.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with password admin, the default login. Change it at once under your user settings. 5. After an update, open the start page once so Grocy can update its database. ## Deploy button for your README Do you maintain Grocy or write about it? Put this button in a README or a post. A click opens Grocy in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Grocy for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Grocy data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Grocy? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Grocy backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Grocy get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # HedgeDoc hosting in the EU URL: https://blitz.cloud/apps/hedgedoc/ Updated: 2026-10-14 Run your own HedgeDoc, an alternative to Google Docs and HackMD. One-click install, HTTPS, servers in the EU. Free plan, no card. HedgeDoc: write notes together in real time, in the browser, like a shared Google Doc. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Google Docs, HackMD and Etherpad HedgeDoc does the job of Google Docs, HackMD or Etherpad, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | HedgeDoc | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of HedgeDoc](/get/hedgedoc/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `hedgedoc.yourname.blitz.cloud`. 4. Open the app's address and register with your email and a password. 5. When everyone has an account, set CMD_ALLOW_EMAIL_REGISTER to false in Environment so nobody else can sign up. ## Deploy button for your README Do you maintain HedgeDoc or write about it? Put this button in a README or a post. A click opens HedgeDoc in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host HedgeDoc for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my HedgeDoc data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for HedgeDoc? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is HedgeDoc backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does HedgeDoc get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Hermes Agent hosting in the EU URL: https://blitz.cloud/apps/hermes-agent/ Updated: 2026-10-14 Run your own Hermes Agent, an alternative to ChatGPT and Claude. One-click install, HTTPS, servers in the EU. Free plan, no card. Hermes Agent: an AI agent from Nous Research that your own apps and chat tools talk to through an OpenAI-style API. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to ChatGPT, Claude and OpenAI API Hermes Agent does the job of ChatGPT, Claude or OpenAI API, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Hermes Agent | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Hermes Agent](/get/hermes-agent/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `hermes.yourname.blitz.cloud`. 4. Add your model provider's API key in Environment, for example OPENROUTER_API_KEY. 5. Point an OpenAI-compatible app at the app's address/v1 and use this key. ## While it sleeps Hermes Agent only answers and runs its scheduled tasks while it is awake. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing Hermes Agent keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Good to know Here Hermes is an API only. Its dashboard and terminal chat need to run as the machine's owner, which apps here never do. ## Deploy button for your README Do you maintain Hermes Agent or write about it? Put this button in a README or a post. A click opens Hermes Agent in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Hermes Agent for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Hermes Agent data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Hermes Agent? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Hermes Agent backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Hermes Agent get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Homarr hosting in the EU URL: https://blitz.cloud/apps/homarr/ Updated: 2026-10-14 Run your own Homarr, an alternative to Heimdall and Start.me. One-click install, HTTPS, servers in the EU. Free plan, no card. Homarr: A home screen for every app and server you run. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Heimdall and Start.me Homarr does the job of Heimdall or Start.me, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Homarr | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Homarr](/get/homarr/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `homarr.yourname.blitz.cloud`. 4. Open the app's address to onboard as its first user and build your board. ## Good to know The Docker integration cannot see containers here, so add tiles by address instead. ## Deploy button for your README Do you maintain Homarr or write about it? Put this button in a README or a post. A click opens Homarr in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Homarr for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Homarr data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Homarr? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Homarr backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Homarr get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Home Assistant hosting in the EU URL: https://blitz.cloud/apps/home-assistant/ Updated: 2026-10-14 Run your own Home Assistant, an alternative to Google Home and Amazon Alexa. One-click install, HTTPS, servers in the EU. Free plan, no card. Home Assistant: control lights, heating and more - everything local, nothing in someone else's cloud. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Google Home, Amazon Alexa and SmartThings Home Assistant does the job of Google Home, Amazon Alexa or SmartThings, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Home Assistant | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Home Assistant](/get/home-assistant/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `home.yourname.blitz.cloud`. 4. Open the app's address and create your account. The first account made is the owner. 5. Add the services you use online, like weather or your smart plugs' cloud, under Settings, Devices and services. ## While it sleeps Home Assistant only runs its automations while it is awake. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing Home Assistant keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Good to know It doesn't discover devices on your home network by itself. Connect your home network, forward a device to it in the Designer and add it in Home Assistant by that name. ## Deploy button for your README Do you maintain Home Assistant or write about it? Put this button in a README or a post. A click opens Home Assistant in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Home Assistant for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Home Assistant data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Home Assistant? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Home Assistant backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Home Assistant get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # HomeBox hosting in the EU URL: https://blitz.cloud/apps/homebox/ Updated: 2026-10-14 Run your own HomeBox, an alternative to Sortly. One-click install, HTTPS, servers in the EU. Free plan, no card. HomeBox: keep an inventory of everything you own, where it is and what it is worth, without a spreadsheet. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Sortly HomeBox does the job of Sortly, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | HomeBox | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of HomeBox](/get/homebox/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `homebox.yourname.blitz.cloud`. 4. Open the app's address and make the first account yourself. Registration turns off after that, so nobody else can sign up. ## Deploy button for your README Do you maintain HomeBox or write about it? Put this button in a README or a post. A click opens HomeBox in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host HomeBox for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my HomeBox data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for HomeBox? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is HomeBox backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does HomeBox get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Homer hosting in the EU URL: https://blitz.cloud/apps/homer/ Updated: 2026-10-14 Run your own Homer, an alternative to Heimdall and Dashy. One-click install, HTTPS, servers in the EU. Free plan, no card. Homer: A start page with one tile for every app and site you use, with live status checks. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Heimdall, Dashy and Homarr Homer does the job of Heimdall, Dashy or Homarr, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Homer | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Homer](/get/homer/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `homer.yourname.blitz.cloud`. 4. Open the app's address to see the example page, then edit config.yml under the app's storage with FileBrowser Quantum to add your own links. ## Good to know No login and nothing to click to edit here. Change config.yml under the app's storage with FileBrowser Quantum to add or edit tiles. ## Deploy button for your README Do you maintain Homer or write about it? Put this button in a README or a post. A click opens Homer in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Homer for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Homer data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Homer? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Homer backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Homer get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Immich hosting in the EU URL: https://blitz.cloud/apps/immich/ Updated: 2026-10-14 Run your own Immich, an alternative to Google Photos and iCloud Photos. One-click install, HTTPS, servers in the EU. On Pro, 14 days free. Immich: back up every photo from your phone, automatically. Like Google Photos, but yours. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 5 GB of storage and the PostgreSQL and Redis it needs, and it runs on servers in the EU. Immich needs more memory than the free plan has, so it runs on Pro (7 EUR a month, 14-day trial without a card). ## A self-hosted alternative to Google Photos, iCloud Photos and Amazon Photos Immich does the job of Google Photos, iCloud Photos or Amazon Photos, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Immich | |---|---| | Memory | 768 MB reserved from your plan | | Storage | 5 GB | | Database | PostgreSQL and Redis, created and connected for you | | Plan | Pro | ## Install it 1. [Start the install of Immich](/get/immich/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install (on a free account, start the 14-day Pro trial there first). It lists what gets created, the database included, and is online about a minute later, at an address like `immich.yourname.blitz.cloud`. 4. Open the app's address and create the admin account. The first account made is the one in charge. 5. Install the Immich app on your phone, enter the app's address as the server and turn on backup. ## Good to know Face and object search are off for now, because they need more memory than an app gets here. Photos, albums, the map and sharing all work. ## Deploy button for your README Do you maintain Immich or write about it? Put this button in a README or a post. A click opens Immich in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Immich for free? Not on the free plan: Immich needs a larger size than it has. Pro costs 7 EUR a month and starts with a 14-day trial that needs no card. ### Where is my Immich data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Immich? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Immich backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Immich get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Jellyfin hosting in the EU URL: https://blitz.cloud/apps/jellyfin/ Updated: 2026-10-14 Run your own Jellyfin, an alternative to Plex and Netflix. One-click install, HTTPS, servers in the EU. Free plan, no card. Jellyfin: your movies and music, streamable to any screen in the house. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 5 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Plex, Netflix and Emby Jellyfin does the job of Plex, Netflix or Emby, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Jellyfin | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 5 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Jellyfin](/get/jellyfin/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `jellyfin.yourname.blitz.cloud`. 4. Open the app's address and finish the setup there. The first account you make is the admin. ## Deploy button for your README Do you maintain Jellyfin or write about it? Put this button in a README or a post. A click opens Jellyfin in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Jellyfin for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Jellyfin data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Jellyfin? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Jellyfin backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Jellyfin get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Joplin Server hosting in the EU URL: https://blitz.cloud/apps/joplin-server/ Updated: 2026-10-14 Run your own Joplin Server, an alternative to Evernote and OneNote. One-click install, HTTPS, servers in the EU. Free plan, no card. Joplin Server: keeps your Joplin notes in sync across your phone and computers, on a server that is yours. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS and the PostgreSQL it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Evernote, OneNote and Notion Joplin Server does the job of Evernote, OneNote or Notion, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Joplin Server | |---|---| | Memory | 128 MB reserved from your plan | | Storage | none | | Database | PostgreSQL, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Joplin Server](/get/joplin-server/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `joplin.yourname.blitz.cloud`. 4. Open the app's address and sign in with admin@localhost and the password admin. 5. Change both right away under your profile. Anyone who knows Joplin knows the default. ## Deploy button for your README Do you maintain Joplin Server or write about it? Put this button in a README or a post. A click opens Joplin Server in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Joplin Server for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Joplin Server data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Joplin Server? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Joplin Server backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Joplin Server get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Kavita hosting in the EU URL: https://blitz.cloud/apps/kavita/ Updated: 2026-10-14 Run your own Kavita, an alternative to Komga and Plex. One-click install, HTTPS, servers in the EU. Free plan, no card. Kavita: read your comics, manga and ebooks from one library that remembers where you stopped. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 5 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Komga, Plex and Calibre Kavita does the job of Komga, Plex or Calibre, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Kavita | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 5 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Kavita](/get/kavita/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `kavita.yourname.blitz.cloud`. 4. Open the app's address and create the first account. It becomes the admin. 5. Upload your files into the app's storage with FileBrowser Quantum, then add a library from Settings. ## Good to know Starts with no library. Upload your comics, manga or ebooks into the app's storage with FileBrowser Quantum, then add a library pointing at that folder. ## Deploy button for your README Do you maintain Kavita or write about it? Put this button in a README or a post. A click opens Kavita in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Kavita for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Kavita data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Kavita? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Kavita backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Kavita get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Komga hosting in the EU URL: https://blitz.cloud/apps/komga/ Updated: 2026-10-14 Run your own Komga, an alternative to Kavita and Plex. One-click install, HTTPS, servers in the EU. Free plan, no card. Komga: A server for your comics and manga, with a reader that tracks your progress across devices. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 5 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Kavita and Plex Komga does the job of Kavita or Plex, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Komga | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 5 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Komga](/get/komga/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `komga.yourname.blitz.cloud`. 4. Open the app's address and create the first account. It becomes the admin. 5. Upload your files into the app's storage with FileBrowser Quantum, then add a library from Settings. ## Good to know Starts with no library. Upload your comics or manga into the app's storage with FileBrowser Quantum, then add a library pointing at that folder. ## Deploy button for your README Do you maintain Komga or write about it? Put this button in a README or a post. A click opens Komga in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Komga for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Komga data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Komga? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Komga backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Komga get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # LibreTranslate hosting in the EU URL: https://blitz.cloud/apps/libretranslate/ Updated: 2026-10-14 Run your own LibreTranslate, an alternative to Google Translate and DeepL. One-click install, HTTPS, servers in the EU. Free plan, no card. LibreTranslate: translate text and documents on your own server, without sending them to Google or DeepL. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Google Translate and DeepL LibreTranslate does the job of Google Translate or DeepL, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | LibreTranslate | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of LibreTranslate](/get/libretranslate/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `libretranslate.yourname.blitz.cloud`. 4. Open the app's address from your private network and translate a sentence. English, German, Spanish and French are ready. 5. To add a language, put its code in LT_LOAD_ONLY in Environment. Each one needs more memory. ## Deploy button for your README Do you maintain LibreTranslate or write about it? Put this button in a README or a post. A click opens LibreTranslate in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host LibreTranslate for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my LibreTranslate data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for LibreTranslate? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is LibreTranslate backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does LibreTranslate get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Linkding hosting in the EU URL: https://blitz.cloud/apps/linkding/ Updated: 2026-10-14 Run your own Linkding, an alternative to Pocket and Raindrop.io. One-click install, HTTPS, servers in the EU. Free plan, no card. Linkding: A fast, private place to keep every link you meant to read later. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Pocket, Raindrop.io and Pinboard Linkding does the job of Pocket, Raindrop.io or Pinboard, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Linkding | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Linkding](/get/linkding/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `linkding.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with this password. 5. Add the browser extension so saving a page takes one click. ## Deploy button for your README Do you maintain Linkding or write about it? Put this button in a README or a post. A click opens Linkding in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Linkding for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Linkding data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Linkding? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Linkding backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Linkding get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Linkwarden hosting in the EU URL: https://blitz.cloud/apps/linkwarden/ Updated: 2026-10-14 Run your own Linkwarden, an alternative to Pocket and Raindrop.io. One-click install, HTTPS, servers in the EU. Free plan, no card. Linkwarden: save links with a full copy of each page, so they still open after the site is gone. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 2 GB of storage and the PostgreSQL it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Pocket, Raindrop.io and Instapaper Linkwarden does the job of Pocket, Raindrop.io or Instapaper, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Linkwarden | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 2 GB | | Database | PostgreSQL, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Linkwarden](/get/linkwarden/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `linkwarden.yourname.blitz.cloud`. 4. Open it from your private network and make your account. 5. Add the browser extension so saving a page takes one click. ## Good to know Anyone who can open it can make an account, and it cannot be switched off reliably, so it starts private. Keep it that way. Saving a copy of a page takes most of its memory for a moment, so add links a few at a time. ## Deploy button for your README Do you maintain Linkwarden or write about it? Put this button in a README or a post. A click opens Linkwarden in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Linkwarden for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Linkwarden data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Linkwarden? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Linkwarden backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Linkwarden get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Listmonk hosting in the EU URL: https://blitz.cloud/apps/listmonk/ Updated: 2026-10-14 Run your own Listmonk, an alternative to Mailchimp and Sendy. One-click install, HTTPS, servers in the EU. Free plan, no card. Listmonk: send newsletters and announcements to your own mailing lists without handing your subscriber data to anyone else. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS and the PostgreSQL it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Mailchimp and Sendy Listmonk does the job of Mailchimp or Sendy, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Listmonk | |---|---| | Memory | 128 MB reserved from your plan | | Storage | none | | Database | PostgreSQL, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Listmonk](/get/listmonk/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `listmonk.yourname.blitz.cloud`. 4. Open the app's address/admin and sign in as admin with this password. 5. Sending mail needs your own SMTP server, set under Settings > SMTP. ## Deploy button for your README Do you maintain Listmonk or write about it? Put this button in a README or a post. A click opens Listmonk in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Listmonk for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Listmonk data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Listmonk? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Listmonk backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Listmonk get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Lychee hosting in the EU URL: https://blitz.cloud/apps/lychee/ Updated: 2026-10-14 Run your own Lychee, an alternative to Google Photos and PhotoPrism. One-click install, HTTPS, servers in the EU. Free plan, no card. Lychee: A photo gallery you host yourself, with albums, maps and a slideshow for every trip. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 5 GB of storage and the MariaDB it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Google Photos and PhotoPrism Lychee does the job of Google Photos or PhotoPrism, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Lychee | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 5 GB | | Database | MariaDB, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Lychee](/get/lychee/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `lychee.yourname.blitz.cloud`. 4. Open the app's address and sign in with admin / password, the default login. Change it at once under Settings. ## Deploy button for your README Do you maintain Lychee or write about it? Put this button in a README or a post. A click opens Lychee in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Lychee for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Lychee data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Lychee? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Lychee backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Lychee get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Matomo hosting in the EU URL: https://blitz.cloud/apps/matomo/ Updated: 2026-10-14 Run your own Matomo, an alternative to Google Analytics and Fathom. One-click install, HTTPS, servers in the EU. Free plan, no card. Matomo: see who visits your site and what they do, on your own server instead of someone else's. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 2 GB of storage and the MariaDB it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Google Analytics and Fathom Matomo does the job of Google Analytics or Fathom, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Matomo | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 2 GB | | Database | MariaDB, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Matomo](/get/matomo/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `matomo.yourname.blitz.cloud`. 4. Open the app's address and run the install wizard; it makes your admin account and the first site to track. 5. In the wizard, set the trusted host to your app's address and leave "force SSL" on, since blitz.cloud always serves it over https. ## While it sleeps Matomo only counts visits while it is awake. A visit wakes it, but that first one may be missed. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing Matomo keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Deploy button for your README Do you maintain Matomo or write about it? Put this button in a README or a post. A click opens Matomo in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Matomo for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Matomo data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Matomo? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Matomo backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Matomo get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Mealie hosting in the EU URL: https://blitz.cloud/apps/mealie/ Updated: 2026-10-14 Run your own Mealie, an alternative to Paprika and Plan to Eat. One-click install, HTTPS, servers in the EU. Free plan, no card. Mealie: save recipes from any website, plan the week's meals and build the shopping list. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Paprika, Plan to Eat and AnyList Mealie does the job of Paprika, Plan to Eat or AnyList, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Mealie | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Mealie](/get/mealie/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `mealie.yourname.blitz.cloud`. 4. Open the app's address and sign in with changeme@example.com and the password MyPassword. 5. Change that email and password right away under your profile. Anyone who knows Mealie knows the default. ## Deploy button for your README Do you maintain Mealie or write about it? Put this button in a README or a post. A click opens Mealie in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Mealie for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Mealie data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Mealie? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Mealie backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Mealie get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # MediaWiki hosting in the EU URL: https://blitz.cloud/apps/mediawiki/ Updated: 2026-10-14 Run your own MediaWiki, an alternative to Notion and Confluence. One-click install, HTTPS, servers in the EU. Free plan, no card. MediaWiki: run your own wiki, the same software behind Wikipedia, with pages, history and search. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Notion and Confluence MediaWiki does the job of Notion or Confluence, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | MediaWiki | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of MediaWiki](/get/mediawiki/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `mediawiki.yourname.blitz.cloud`. 4. Open the app's address and sign in as Admin with the password you set below. ## Deploy button for your README Do you maintain MediaWiki or write about it? Put this button in a README or a post. A click opens MediaWiki in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host MediaWiki for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my MediaWiki data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for MediaWiki? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is MediaWiki backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does MediaWiki get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Memos hosting in the EU URL: https://blitz.cloud/apps/memos/ Updated: 2026-10-14 Run your own Memos, an alternative to Google Keep and Apple Notes. One-click install, HTTPS, servers in the EU. Free plan, no card. Memos: A quick place to write things down, that stays yours. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Google Keep and Apple Notes Memos does the job of Google Keep or Apple Notes, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Memos | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Memos](/get/memos/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `memos.yourname.blitz.cloud`. 4. Open the app's address and make your account. The first one becomes the admin. ## Deploy button for your README Do you maintain Memos or write about it? Put this button in a README or a post. A click opens Memos in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Memos for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Memos data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Memos? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Memos backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Memos get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # MicroBin hosting in the EU URL: https://blitz.cloud/apps/microbin/ Updated: 2026-10-14 Run your own MicroBin, an alternative to Pastebin and 0bin. One-click install, HTTPS, servers in the EU. Free plan, no card. MicroBin: share a snippet, a file or a link with a short address that only works as long as you let it. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Pastebin and 0bin MicroBin does the job of Pastebin or 0bin, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | MicroBin | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of MicroBin](/get/microbin/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `microbin.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with this password to manage every paste. 5. Anyone you send a paste's address to can open it without signing in, until it expires or you remove it. ## Deploy button for your README Do you maintain MicroBin or write about it? Put this button in a README or a post. A click opens MicroBin in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host MicroBin for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my MicroBin data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for MicroBin? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is MicroBin backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does MicroBin get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Miniflux hosting in the EU URL: https://blitz.cloud/apps/miniflux/ Updated: 2026-10-14 Run your own Miniflux, an alternative to Feedly and Inoreader. One-click install, HTTPS, servers in the EU. Free plan, no card. Miniflux: all your news feeds in one fast, no-frills reader. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS and the PostgreSQL it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Feedly, Inoreader and FreshRSS Miniflux does the job of Feedly, Inoreader or FreshRSS, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Miniflux | |---|---| | Memory | 128 MB reserved from your plan | | Storage | none | | Database | PostgreSQL, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Miniflux](/get/miniflux/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `miniflux.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with this password. Change it under Settings. 5. Add the feeds of the sites you read, or import an OPML file from your old reader. ## Deploy button for your README Do you maintain Miniflux or write about it? Put this button in a README or a post. A click opens Miniflux in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Miniflux for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Miniflux data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Miniflux? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Miniflux backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Miniflux get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Monica hosting in the EU URL: https://blitz.cloud/apps/monica/ Updated: 2026-10-14 Run your own Monica, an alternative to Clay and Dex. One-click install, HTTPS, servers in the EU. Free plan, no card. Monica: keep notes on the people in your life, birthdays, calls and conversations included. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage and the MariaDB it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Clay and Dex Monica does the job of Clay or Dex, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Monica | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 1 GB | | Database | MariaDB, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Monica](/get/monica/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `monica.yourname.blitz.cloud`. 4. Open the app's address and register the first account; it becomes the owner. 5. In Settings, turn off new registrations once you are the only one who should sign up. ## Good to know The first account to sign up owns it; after that, turn signups off in Settings so nobody else can join. ## Deploy button for your README Do you maintain Monica or write about it? Put this button in a README or a post. A click opens Monica in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Monica for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Monica data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Monica? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Monica backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Monica get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # n8n hosting in the EU URL: https://blitz.cloud/apps/n8n/ Updated: 2026-10-19 Run your own n8n, an alternative to Zapier and Make. One-click install, HTTPS, servers in the EU. Free plan, no card. n8n: connect your apps and automate chores - no code needed. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Zapier, Make and IFTTT n8n does the job of Zapier, Make or IFTTT, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | n8n | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## On blitz.cloud | Measured | n8n | |---|---| | Installs on blitz.cloud | 50 or more | | Online after installing | about 50 seconds | | Waking up after a sleep | about 45 seconds | | Memory while awake | about 410 MB | | Version | 2.39.4, on blitz.cloud since 16 September 2026 | Measured on 19 October 2026 across the n8n apps on blitz.cloud. Times and memory are medians, installs a band, and nothing here comes from fewer than 5 installs. ## Install it 1. [Start the install of n8n](/get/n8n/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `n8n.yourname.blitz.cloud`. 4. Open the app's address and create the owner account. Until you do, anyone who finds the address could. ## While it sleeps n8n only runs its schedules while it is awake. On the free plan webhooks don't wake it. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing n8n keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Deploy button for your README Do you maintain n8n or write about it? Put this button in a README or a post. A click opens n8n in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host n8n for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my n8n data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for n8n? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is n8n backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does n8n get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Navidrome hosting in the EU URL: https://blitz.cloud/apps/navidrome/ Updated: 2026-10-14 Run your own Navidrome, an alternative to Spotify and Plex. One-click install, HTTPS, servers in the EU. Free plan, no card. Navidrome: stream your own music library from any device, like your own Spotify. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 2 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Spotify, Plex and Subsonic Navidrome does the job of Spotify, Plex or Subsonic, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Navidrome | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 2 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Navidrome](/get/navidrome/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `navidrome.yourname.blitz.cloud`. 4. Open the app's address and create the first account. It becomes the admin. 5. Upload music into the app's storage with FileBrowser Quantum, then scan the library from Navidrome's Settings. ## Deploy button for your README Do you maintain Navidrome or write about it? Put this button in a README or a post. A click opens Navidrome in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Navidrome for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Navidrome data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Navidrome? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Navidrome backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Navidrome get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Nextcloud hosting in the EU URL: https://blitz.cloud/apps/nextcloud/ Updated: 2026-10-14 Run your own Nextcloud, an alternative to Dropbox and Google Drive. One-click install, HTTPS, servers in the EU. Free plan, no card. Nextcloud: your own Dropbox - files, calendar, contacts, all in one place. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 5 GB of storage and the MariaDB it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Dropbox, Google Drive, iCloud Drive and OneDrive Nextcloud does the job of Dropbox, Google Drive, iCloud Drive or OneDrive, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Nextcloud | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 5 GB | | Database | MariaDB, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Nextcloud](/get/nextcloud/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `nextcloud.yourname.blitz.cloud`. 4. Open the app's address and create the admin account. Until you do, anyone who finds the address could. ## Deploy button for your README Do you maintain Nextcloud or write about it? Put this button in a README or a post. A click opens Nextcloud in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Nextcloud for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Nextcloud data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Nextcloud? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Nextcloud backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Nextcloud get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # NocoBase hosting in the EU URL: https://blitz.cloud/apps/nocobase/ Updated: 2026-10-14 Run your own NocoBase, an alternative to Airtable and Retool. One-click install, HTTPS, servers in the EU. Free plan, no card. NocoBase: build your own internal tools and databases by clicking, not coding. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage and the PostgreSQL it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Airtable, Retool and Budibase NocoBase does the job of Airtable, Retool or Budibase, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | NocoBase | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 1 GB | | Database | PostgreSQL, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of NocoBase](/get/nocobase/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `nocobase.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with this password. Change the email and password under your profile. 5. Create a table for what you keep track of, then add a page that shows it as a list, a board or a form. ## Deploy button for your README Do you maintain NocoBase or write about it? Put this button in a README or a post. A click opens NocoBase in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host NocoBase for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my NocoBase data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for NocoBase? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is NocoBase backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does NocoBase get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # ntfy hosting in the EU URL: https://blitz.cloud/apps/ntfy/ Updated: 2026-10-14 Run your own ntfy, an alternative to Pushover and Pushbullet. One-click install, HTTPS, servers in the EU. Free plan, no card. ntfy: send push notifications to your phone or desktop from a script, a cron job or any app. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Pushover, Pushbullet and Gotify ntfy does the job of Pushover, Pushbullet or Gotify, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | ntfy | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of ntfy](/get/ntfy/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `ntfy.yourname.blitz.cloud`. 4. Publish a test message with curl -d "hello" the app's address/mytopic, then subscribe to mytopic in the ntfy app or at the app's address/mytopic. ## While it sleeps ntfy only delivers notifications published while it is awake; a sleeping ntfy misses them. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing ntfy keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Good to know Anyone who learns a topic name can publish or subscribe to it, since ntfy has no accounts by default; keep topic names hard to guess, or put a reverse-proxy login in front if that is not enough. ## Deploy button for your README Do you maintain ntfy or write about it? Put this button in a README or a post. A click opens ntfy in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host ntfy for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my ntfy data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for ntfy? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is ntfy backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does ntfy get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Ocular hosting in the EU URL: https://blitz.cloud/apps/ocular/ Updated: 2026-10-14 Run your own Ocular, an alternative to YNAB and Excel. One-click install, HTTPS, servers in the EU. Free plan, no card. Ocular: plan your budget with charts that make it clear where your money goes. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to YNAB and Excel Ocular does the job of YNAB or Excel, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Ocular | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Ocular](/get/ocular/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `ocular.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with this password. 5. Add your accounts and categories, then import a Google Sheet budget or start from scratch. ## Deploy button for your README Do you maintain Ocular or write about it? Put this button in a README or a post. A click opens Ocular in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Ocular for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Ocular data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Ocular? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Ocular backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Ocular get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # OmniRoute hosting in the EU URL: https://blitz.cloud/apps/omniroute/ Updated: 2026-10-14 Run your own OmniRoute, an alternative to OpenRouter and LiteLLM. One-click install, HTTPS, servers in the EU. Free plan, no card. OmniRoute: one address for all your AI model providers, which switches to another one when a provider fails or runs out. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to OpenRouter, LiteLLM and Portkey OmniRoute does the job of OpenRouter, LiteLLM or Portkey, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | OmniRoute | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of OmniRoute](/get/omniroute/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `omniroute.yourname.blitz.cloud`. 4. Open the app's address and sign in with this password. 5. Add the API keys of the AI providers you use, then create an API key for your own tools. ## While it sleeps OmniRoute only answers your tools while it is awake. On the free plan a request from a tool doesn't wake it. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing OmniRoute keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Deploy button for your README Do you maintain OmniRoute or write about it? Put this button in a README or a post. A click opens OmniRoute in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host OmniRoute for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my OmniRoute data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for OmniRoute? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is OmniRoute backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does OmniRoute get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Open WebUI hosting in the EU URL: https://blitz.cloud/apps/open-webui/ Updated: 2026-10-14 Run your own Open WebUI, an alternative to ChatGPT and Claude. One-click install, HTTPS, servers in the EU. Free plan, no card. Open WebUI: A chat page like ChatGPT for the AI models you choose, with your chats kept on your own server. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 2 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to ChatGPT, Claude, Gemini and LibreChat Open WebUI does the job of ChatGPT, Claude, Gemini or LibreChat, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Open WebUI | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 2 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Open WebUI](/get/open-webui/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `open.yourname.blitz.cloud`. 4. Open the app's address and create your account. The first account becomes the admin. 5. Under Admin Panel, Settings, Connections, add the API key of OpenAI or another compatible provider. ## Good to know It runs no AI model itself. You bring an API key from a provider, and searching your own documents needs an embedding key as well. ## Deploy button for your README Do you maintain Open WebUI or write about it? Put this button in a README or a post. A click opens Open WebUI in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Open WebUI for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Open WebUI data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Open WebUI? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Open WebUI backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Open WebUI get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Open-source apps you can host in one click URL: https://blitz.cloud/apps/ Updated: 2026-10-14 96 open-source apps from the blitz.cloud App Store: what each one replaces, what it needs, and how to install it. Servers in the EU, free plan without a card. Every app below runs on blitz.cloud today. Pick one in the App Store, give it a name, and it installs with the storage and database it needs. Each page says what the app replaces, how much of your plan it takes, and what to do first after installing. ## Files & documents - [Nextcloud](/apps/nextcloud/): Your own Dropbox - files, calendar, contacts, all in one place. - [Syncthing](/apps/syncthing/): Keep a folder in step across your computers and phone, with no cloud in between. - [Stirling PDF](/apps/stirling-pdf/): Merge, split, sign and shrink PDFs, without uploading them to a stranger. - [Paperless-ngx](/apps/paperless-ngx/): Scan your paper mail once, find any letter in seconds, and throw the paper away. - [FileBrowser Quantum](/apps/filebrowser/): Upload, download and sort the files your apps keep, from your browser. - [OpenCloud](/apps/opencloud/): Your own Dropbox for files and folders, with desktop and phone apps that sync. - [PrivateBin](/apps/privatebin/): Paste text or code that only the person with the link can read, even we cannot see it. - [MicroBin](/apps/microbin/): Share a snippet, a file or a link with a short address that only works as long as you let it. - [Gokapi](/apps/gokapi/): Share a file with a link that expires when you decide it should. - [PdfDing](/apps/pdfding/): Keep your PDFs, read them and pick up where you left off. ## Photos & media - [Immich](/apps/immich/): Back up every photo from your phone, automatically. Like Google Photos, but yours. - [Jellyfin](/apps/jellyfin/): Your movies and music, streamable to any screen in the house. - [Audiobookshelf](/apps/audiobookshelf/): Your audiobooks and podcasts on every phone, and it remembers where you stopped. - [cobalt](/apps/cobalt/): Save videos and music from sites like TikTok and SoundCloud through your own download API. - [Navidrome](/apps/navidrome/): Stream your own music library from any device, like your own Spotify. - [Calibre-Web](/apps/calibre-web/): Browse and read your ebook collection in the browser, with covers, search and an online reader. - [Kavita](/apps/kavita/): Read your comics, manga and ebooks from one library that remembers where you stopped. - [Komga](/apps/komga/): A server for your comics and manga, with a reader that tracks your progress across devices. - [Gonic](/apps/gonic/): Stream your own music and podcasts to any Subsonic app. - [Chevereto](/apps/chevereto/): Run your own image and video host, with albums, galleries and links to share. - [Lychee](/apps/lychee/): A photo gallery you host yourself, with albums, maps and a slideshow for every trip. ## Websites & blogs - [Ghost](/apps/ghost/): A beautiful blog and newsletter, ready to write in. - [Umami](/apps/umami/): See how many people visit your website and where they come from, without cookies or banners. - [WordPress](/apps/wordpress/): Build a website or a blog, with thousands of free themes and plugins to pick from. ## Passwords & security - [Vaultwarden](/apps/vaultwarden/): A password manager the whole family can use, hosted by you. ## Money & home - [Home Assistant](/apps/home-assistant/): Control lights, heating and more - everything local, nothing in someone else's cloud. - [Actual Budget](/apps/actual-budget/): A budget app that shows where your money goes, without selling what it learns. - [Mealie](/apps/mealie/): Save recipes from any website, plan the week's meals and build the shopping list. - [Firefly III](/apps/firefly-iii/): Keep track of every account, bill and budget in one place, with reports that show where it all went. - [HomeBox](/apps/homebox/): Keep an inventory of everything you own, where it is and what it is worth, without a spreadsheet. - [Ocular](/apps/ocular/): Plan your budget with charts that make it clear where your money goes. - [Paisa](/apps/paisa/): Track your money in a plain text ledger, with charts to make sense of it. - [Grocy](/apps/grocy/): Track groceries, chores and household items, with reminders before anything runs out or expires. ## Monitoring & automation - [n8n](/apps/n8n/): Connect your apps and automate chores - no code needed. - [Uptime Kuma](/apps/uptime-kuma/): Get a ping when any of your sites goes down. - [Activepieces](/apps/activepieces/): Connect your apps and automate chores by clicking steps together, no code needed. - [ntfy](/apps/ntfy/): Send push notifications to your phone or desktop from a script, a cron job or any app. - [Gotify](/apps/gotify/): A simple server for push notifications from your own scripts and services. - [Beszel](/apps/beszel/): Watch CPU, memory, disk and network for your own servers from one lightweight dashboard. - [Changedetection.io](/apps/changedetection/): Watch any website for changes and get a message the moment something you care about is updated. - [Matomo](/apps/matomo/): See who visits your site and what they do, on your own server instead of someone else's. ## Notes & knowledge - [FreshRSS](/apps/freshrss/): All your news feeds in one calm, ad-free reader. - [Linkding](/apps/linkding/): A fast, private place to keep every link you meant to read later. - [Memos](/apps/memos/): A quick place to write things down, that stays yours. - [Joplin Server](/apps/joplin-server/): Keeps your Joplin notes in sync across your phone and computers, on a server that is yours. - [Linkwarden](/apps/linkwarden/): Save links with a full copy of each page, so they still open after the site is gone. - [Wiki.js](/apps/wikijs/): A wiki for your team or club, with a friendly editor and search. - [Docmost](/apps/docmost/): Shared pages and a wiki for your team, with an editor that feels like Notion. - [SilverBullet](/apps/silverbullet/): A notebook in your browser where pages link to each other, kept as plain text files. - [Miniflux](/apps/miniflux/): All your news feeds in one fast, no-frills reader. - [Wallabag](/apps/wallabag/): Save articles from the web and read them later, without ads or trackers. - [BookStack](/apps/bookstack/): A wiki built like a library, with books, chapters and pages for everything your team writes down. - [DokuWiki](/apps/dokuwiki/): A simple wiki that keeps every page as a plain text file, with no database to break. - [Shiori](/apps/shiori/): Save web pages with one click and keep a readable copy even after the original disappears. - [flatnotes](/apps/flatnotes/): Write quick notes as plain markdown files, searchable the moment you save them. - [Readeck](/apps/readeck/): Save articles from the web, strip the clutter and read them later without ads or trackers. - [TriliumNext](/apps/trilium/): Keep notes in a tree you shape yourself, with checklists, tables and your own encryption for the private ones. - [Fusion](/apps/fusion/): Follow RSS feeds from one clean inbox. - [CommaFeed](/apps/commafeed/): Read your RSS feeds in a fast, familiar reader. - [Poznote](/apps/poznote/): Write and organise notes with tags, folders and search. - [MediaWiki](/apps/mediawiki/): Run your own wiki, the same software behind Wikipedia, with pages, history and search. - [RSS-Bridge](/apps/rss-bridge/): Turn a website with no feed of its own into an RSS or Atom feed your reader can follow. ## Productivity - [Vikunja](/apps/vikunja/): To-do lists and projects for you or the whole household, as lists, boards or a calendar. - [HedgeDoc](/apps/hedgedoc/): Write notes together in real time, in the browser, like a shared Google Doc. - [Planka](/apps/planka/): Boards and cards for planning anything together, like Trello. - [NocoBase](/apps/nocobase/): Build your own internal tools and databases by clicking, not coding. - [Excalidraw](/apps/excalidraw/): A virtual whiteboard for sketches and diagrams that look hand-drawn. - [Etherpad](/apps/etherpad/): Write a document together with other people, watching each other's edits appear live. - [Dashy](/apps/dashy/): A start page for all the apps and sites you use, with status checks and widgets. - [Homer](/apps/homer/): A start page with one tile for every app and site you use, with live status checks. - [Fider](/apps/fider/): Collect feedback and feature requests from your users, and let them vote on what matters. - [Listmonk](/apps/listmonk/): Send newsletters and announcements to your own mailing lists without handing your subscriber data to anyone else. - [The Lounge](/apps/thelounge/): Stay connected to IRC from any device, with your chat history kept on your own server. - [Traggo](/apps/traggo/): Track your time with tags instead of projects and see where your hours actually went. - [Tududi](/apps/tududi/): Organise tasks, projects and notes in one place and keep every bit of it on your own server. - [Homarr](/apps/homarr/): A home screen for every app and server you run. - [Rallly](/apps/rallly/): Find a date that works for everyone, without the back and forth. - [Snipe-IT](/apps/snipe-it/): Track who has which laptop, licence or asset, with a tag and history for every item. - [Monica](/apps/monica/): Keep notes on the people in your life, birthdays, calls and conversations included. - [Easy!Appointments](/apps/easy-appointments/): Let people book a slot on your calendar, with reminders and no back and forth by mail. - [Roundcube](/apps/roundcube/): A web mail client for an inbox you already have, with search, folders and a contact list. ## Developer tools - [Forgejo](/apps/forgejo/): Your own place for Git repositories, issues and pull requests, like a small GitHub. - [Wakapi](/apps/wakapi/): See how much time you spend coding, per project and language, from your editor's plugin. - [WAHA](/apps/waha/): A WhatsApp API you run yourself. Connect a number, then send and receive messages over HTTP. - [Evolution API](/apps/evolution-api/): Send and receive WhatsApp messages from your own code through a simple API. - [code-server](/apps/code-server/): VS Code running in your browser, so you can code from any device with your own files. - [Gitea](/apps/gitea/): Your own place for Git repositories, issues and pull requests, like a small GitHub. - [Shlink](/apps/shlink/): Shorten links and keep the click numbers on a server that is only yours. - [ByteStash](/apps/bytestash/): Save and search the code snippets you keep reusing. ## AI & chat - [OmniRoute](/apps/omniroute/): One address for all your AI model providers, which switches to another one when a provider fails or runs out. - [9router](/apps/9router/): Send your AI coding tools through one address and switch to another provider when one runs out. - [Open WebUI](/apps/open-webui/): A chat page like ChatGPT for the AI models you choose, with your chats kept on your own server. - [LibreTranslate](/apps/libretranslate/): Translate text and documents on your own server, without sending them to Google or DeepL. - [OpenClaw](/apps/openclaw/): A personal AI assistant you run yourself and talk to from a web page or your chat apps. - [Hermes Agent](/apps/hermes-agent/): An AI agent from Nous Research that your own apps and chat tools talk to through an OpenAI-style API. - [SillyTavern](/apps/sillytavern/): Chat and write stories with AI characters you create, through the AI provider you choose. --- # OpenClaw hosting in the EU URL: https://blitz.cloud/apps/openclaw/ Updated: 2026-10-14 Run your own OpenClaw, an alternative to ChatGPT and Claude. One-click install, HTTPS, servers in the EU. Free plan, no card. OpenClaw: A personal AI assistant you run yourself and talk to from a web page or your chat apps. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to ChatGPT and Claude OpenClaw does the job of ChatGPT or Claude, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | OpenClaw | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of OpenClaw](/get/openclaw/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `openclaw.yourname.blitz.cloud`. 4. Open the app's address and connect with this gateway token. 5. Add your model provider's API key in Environment, for example OPENAI_API_KEY. ## While it sleeps OpenClaw only answers your chat apps and runs its reminders while it is awake. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing OpenClaw keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Good to know It runs no AI model itself, so you need an API key from a provider. ## Deploy button for your README Do you maintain OpenClaw or write about it? Put this button in a README or a post. A click opens OpenClaw in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host OpenClaw for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my OpenClaw data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for OpenClaw? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is OpenClaw backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does OpenClaw get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # OpenCloud hosting in the EU URL: https://blitz.cloud/apps/opencloud/ Updated: 2026-10-14 Run your own OpenCloud, an alternative to Dropbox and Google Drive. One-click install, HTTPS, servers in the EU. Free plan, no card. OpenCloud: your own Dropbox for files and folders, with desktop and phone apps that sync. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 5 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Dropbox, Google Drive and OneDrive OpenCloud does the job of Dropbox, Google Drive or OneDrive, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | OpenCloud | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 5 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of OpenCloud](/get/opencloud/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `opencloud.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with this password. 5. Add the people you share with under Users, then install the OpenCloud app on your computer and phone. ## Good to know OpenCloud sends uploads to itself through its public address, so it only works while that address is public. ## Deploy button for your README Do you maintain OpenCloud or write about it? Put this button in a README or a post. A click opens OpenCloud in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host OpenCloud for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my OpenCloud data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for OpenCloud? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is OpenCloud backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does OpenCloud get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Paisa hosting in the EU URL: https://blitz.cloud/apps/paisa/ Updated: 2026-10-14 Run your own Paisa, an alternative to Mint and Quicken. One-click install, HTTPS, servers in the EU. Free plan, no card. Paisa: track your money in a plain text ledger, with charts to make sense of it. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Mint and Quicken Paisa does the job of Mint or Quicken, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Paisa | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Paisa](/get/paisa/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `paisa.yourname.blitz.cloud`. 4. Open the app's address; it generates its ledger files under Documents/paisa on first use. ## Good to know It has no sign-in of its own, so it starts private and only opens on your own devices; keep it that way. ## Deploy button for your README Do you maintain Paisa or write about it? Put this button in a README or a post. A click opens Paisa in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Paisa for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Paisa data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Paisa? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Paisa backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Paisa get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Paperless-ngx hosting in the EU URL: https://blitz.cloud/apps/paperless-ngx/ Updated: 2026-10-14 Run your own Paperless-ngx, an alternative to Evernote and Adobe Scan. One-click install, HTTPS, servers in the EU. Free plan, no card. Paperless-ngx: scan your paper mail once, find any letter in seconds, and throw the paper away. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 5 GB of storage and the PostgreSQL and Redis it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Evernote, Adobe Scan and Google Drive Paperless-ngx does the job of Evernote, Adobe Scan or Google Drive, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Paperless-ngx | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 5 GB | | Database | PostgreSQL and Redis, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Paperless-ngx](/get/paperless-ngx/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `paperless.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with this password. 5. Drag a scan or a PDF onto the page. Paperless reads the text so you can search for any word in it later. ## While it sleeps Paperless-ngx only fetches documents from your mailbox while it is awake. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing Paperless-ngx keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Deploy button for your README Do you maintain Paperless-ngx or write about it? Put this button in a README or a post. A click opens Paperless-ngx in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Paperless-ngx for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Paperless-ngx data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Paperless-ngx? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Paperless-ngx backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Paperless-ngx get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # PdfDing hosting in the EU URL: https://blitz.cloud/apps/pdfding/ Updated: 2026-10-14 Run your own PdfDing, an alternative to Adobe Acrobat and Google Drive. One-click install, HTTPS, servers in the EU. Free plan, no card. PdfDing: keep your PDFs, read them and pick up where you left off. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 2 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Adobe Acrobat and Google Drive PdfDing does the job of Adobe Acrobat or Google Drive, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | PdfDing | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 2 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of PdfDing](/get/pdfding/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `pdfding.yourname.blitz.cloud`. 4. Open the app's address and make your own account. 5. Then set DISABLE_USER_SIGNUP in Settings so nobody else can sign up. ## Deploy button for your README Do you maintain PdfDing or write about it? Put this button in a README or a post. A click opens PdfDing in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host PdfDing for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my PdfDing data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for PdfDing? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is PdfDing backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does PdfDing get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Planka hosting in the EU URL: https://blitz.cloud/apps/planka/ Updated: 2026-10-14 Run your own Planka, an alternative to Trello and Asana. One-click install, HTTPS, servers in the EU. Free plan, no card. Planka: boards and cards for planning anything together, like Trello. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage and the PostgreSQL it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Trello, Asana and Jira Planka does the job of Trello, Asana or Jira, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Planka | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | PostgreSQL, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Planka](/get/planka/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `planka.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with this password. 5. Add the people you plan with under Users, then make your first board. ## Deploy button for your README Do you maintain Planka or write about it? Put this button in a README or a post. A click opens Planka in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Planka for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Planka data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Planka? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Planka backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Planka get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Poznote hosting in the EU URL: https://blitz.cloud/apps/poznote/ Updated: 2026-10-14 Run your own Poznote, an alternative to Evernote and Notion. One-click install, HTTPS, servers in the EU. Free plan, no card. Poznote: write and organise notes with tags, folders and search. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 2 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Evernote and Notion Poznote does the job of Evernote or Notion, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Poznote | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 2 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Poznote](/get/poznote/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `poznote.yourname.blitz.cloud`. 4. Sign in at the app's address with admin_change_me / admin, then rename the account and change the password. ## Deploy button for your README Do you maintain Poznote or write about it? Put this button in a README or a post. A click opens Poznote in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Poznote for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Poznote data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Poznote? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Poznote backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Poznote get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # PrivateBin hosting in the EU URL: https://blitz.cloud/apps/privatebin/ Updated: 2026-10-14 Run your own PrivateBin, an alternative to Pastebin and Hastebin. One-click install, HTTPS, servers in the EU. Free plan, no card. PrivateBin: paste text or code that only the person with the link can read, even we cannot see it. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Pastebin and Hastebin PrivateBin does the job of Pastebin or Hastebin, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | PrivateBin | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of PrivateBin](/get/privatebin/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `privatebin.yourname.blitz.cloud`. ## Deploy button for your README Do you maintain PrivateBin or write about it? Put this button in a README or a post. A click opens PrivateBin in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host PrivateBin for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my PrivateBin data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for PrivateBin? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is PrivateBin backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does PrivateBin get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Rallly hosting in the EU URL: https://blitz.cloud/apps/rallly/ Updated: 2026-10-14 Run your own Rallly, an alternative to Doodle and When2meet. One-click install, HTTPS, servers in the EU. Free plan, no card. Rallly: find a date that works for everyone, without the back and forth. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS and the PostgreSQL it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Doodle and When2meet Rallly does the job of Doodle or When2meet, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Rallly | |---|---| | Memory | 256 MB reserved from your plan | | Storage | none | | Database | PostgreSQL, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Rallly](/get/rallly/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `rallly.yourname.blitz.cloud`. 4. Open the app's address and create your first poll; guests can vote from its link without signing in. 5. Add SMTP_HOST, SMTP_PORT, SMTP_USER and SMTP_PWD in Settings so people can sign in by mail code. ## Good to know Nobody can sign in by mail until you add SMTP_HOST, SMTP_PORT, SMTP_USER and SMTP_PWD in Settings; until then, share a poll's own link and voters can still answer it as guests. ## Deploy button for your README Do you maintain Rallly or write about it? Put this button in a README or a post. A click opens Rallly in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Rallly for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Rallly data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Rallly? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Rallly backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Rallly get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Readeck hosting in the EU URL: https://blitz.cloud/apps/readeck/ Updated: 2026-10-14 Run your own Readeck, an alternative to Pocket and Wallabag. One-click install, HTTPS, servers in the EU. Free plan, no card. Readeck: save articles from the web, strip the clutter and read them later without ads or trackers. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Pocket, Wallabag and Instapaper Readeck does the job of Pocket, Wallabag or Instapaper, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Readeck | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Readeck](/get/readeck/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `readeck.yourname.blitz.cloud`. 4. Open the app's address and run the short setup wizard to create the admin account. ## Deploy button for your README Do you maintain Readeck or write about it? Put this button in a README or a post. A click opens Readeck in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Readeck for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Readeck data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Readeck? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Readeck backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Readeck get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Roundcube hosting in the EU URL: https://blitz.cloud/apps/roundcube/ Updated: 2026-10-14 Run your own Roundcube, an alternative to Gmail web client and Outlook on the web. One-click install, HTTPS, servers in the EU. Free plan, no card. Roundcube: A web mail client for an inbox you already have, with search, folders and a contact list. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 512 MB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Gmail web client and Outlook on the web Roundcube does the job of Gmail web client or Outlook on the web, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Roundcube | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 512 MB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Roundcube](/get/roundcube/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `roundcube.yourname.blitz.cloud`. 4. In Settings, add your mail provider's IMAP and SMTP server so Roundcube can sign in to your inbox. ## Good to know It is a mail client for an inbox you already have elsewhere, not a mail server of its own. ## Deploy button for your README Do you maintain Roundcube or write about it? Put this button in a README or a post. A click opens Roundcube in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Roundcube for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Roundcube data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Roundcube? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Roundcube backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Roundcube get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # RSS-Bridge hosting in the EU URL: https://blitz.cloud/apps/rss-bridge/ Updated: 2026-10-14 Run your own RSS-Bridge, an alternative to RSS Hub and FetchRSS. One-click install, HTTPS, servers in the EU. Free plan, no card. RSS-Bridge: turn a website with no feed of its own into an RSS or Atom feed your reader can follow. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to RSS Hub and FetchRSS RSS-Bridge does the job of RSS Hub or FetchRSS, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | RSS-Bridge | |---|---| | Memory | 128 MB reserved from your plan | | Storage | none | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of RSS-Bridge](/get/rss-bridge/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `rss.yourname.blitz.cloud`. 4. Your feed reader needs the password below along with the username admin to fetch a feed. ## Deploy button for your README Do you maintain RSS-Bridge or write about it? Put this button in a README or a post. A click opens RSS-Bridge in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host RSS-Bridge for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my RSS-Bridge data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for RSS-Bridge? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is RSS-Bridge backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does RSS-Bridge get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Shiori hosting in the EU URL: https://blitz.cloud/apps/shiori/ Updated: 2026-10-14 Run your own Shiori, an alternative to Pocket and Wallabag. One-click install, HTTPS, servers in the EU. Free plan, no card. Shiori: save web pages with one click and keep a readable copy even after the original disappears. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Pocket, Wallabag and Raindrop Shiori does the job of Pocket, Wallabag or Raindrop, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Shiori | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Shiori](/get/shiori/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `shiori.yourname.blitz.cloud`. 4. Open the app's address and sign in with shiori / gopher, the default login. Change the password at once under Settings. ## Deploy button for your README Do you maintain Shiori or write about it? Put this button in a README or a post. A click opens Shiori in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Shiori for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Shiori data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Shiori? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Shiori backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Shiori get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Shlink hosting in the EU URL: https://blitz.cloud/apps/shlink/ Updated: 2026-10-14 Run your own Shlink, an alternative to Bitly and YOURLS. One-click install, HTTPS, servers in the EU. Free plan, no card. Shlink: shorten links and keep the click numbers on a server that is only yours. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Bitly and YOURLS Shlink does the job of Bitly or YOURLS, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Shlink | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Shlink](/get/shlink/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `shlink.yourname.blitz.cloud`. 4. Add your address and this API key to a Shlink web client to create and manage short links. ## Good to know This is the API and the redirects, not a web dashboard: use the initial API key with a Shlink web client (for example app.shlink.io, pointed at your own address) to manage links. ## Deploy button for your README Do you maintain Shlink or write about it? Put this button in a README or a post. A click opens Shlink in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Shlink for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Shlink data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Shlink? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Shlink backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Shlink get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # SillyTavern hosting in the EU URL: https://blitz.cloud/apps/sillytavern/ Updated: 2026-10-14 Run your own SillyTavern, an alternative to Character.AI and Janitor AI. One-click install, HTTPS, servers in the EU. Free plan, no card. SillyTavern: chat and write stories with AI characters you create, through the AI provider you choose. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Character.AI, Janitor AI and ChatGPT SillyTavern does the job of Character.AI, Janitor AI or ChatGPT, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | SillyTavern | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of SillyTavern](/get/sillytavern/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `sillytavern.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with this password. 5. Under API Connections, pick your AI provider and paste its API key. ## Good to know It runs no AI model itself, so you need an API key from a provider. ## Deploy button for your README Do you maintain SillyTavern or write about it? Put this button in a README or a post. A click opens SillyTavern in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host SillyTavern for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my SillyTavern data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for SillyTavern? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is SillyTavern backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does SillyTavern get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # SilverBullet hosting in the EU URL: https://blitz.cloud/apps/silverbullet/ Updated: 2026-10-14 Run your own SilverBullet, an alternative to Obsidian and Notion. One-click install, HTTPS, servers in the EU. Free plan, no card. SilverBullet: A notebook in your browser where pages link to each other, kept as plain text files. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Obsidian, Notion and Roam Research SilverBullet does the job of Obsidian, Notion or Roam Research, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | SilverBullet | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of SilverBullet](/get/silverbullet/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `silverbullet.yourname.blitz.cloud`. 4. Open the app's address and sign in. The user name is admin, and the password is everything after the colon in this setting. ## Deploy button for your README Do you maintain SilverBullet or write about it? Put this button in a README or a post. A click opens SilverBullet in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host SilverBullet for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my SilverBullet data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for SilverBullet? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is SilverBullet backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does SilverBullet get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Snipe-IT hosting in the EU URL: https://blitz.cloud/apps/snipe-it/ Updated: 2026-10-14 Run your own Snipe-IT, an alternative to Asset Panda and Lansweeper. One-click install, HTTPS, servers in the EU. Free plan, no card. Snipe-IT: track who has which laptop, licence or asset, with a tag and history for every item. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 2 GB of storage and the MariaDB it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Asset Panda and Lansweeper Snipe-IT does the job of Asset Panda or Lansweeper, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Snipe-IT | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 2 GB | | Database | MariaDB, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Snipe-IT](/get/snipe-it/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `snipe.yourname.blitz.cloud`. 4. Open the app's address; the pre-flight check runs first, then the setup wizard makes your admin account. ## Deploy button for your README Do you maintain Snipe-IT or write about it? Put this button in a README or a post. A click opens Snipe-IT in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Snipe-IT for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Snipe-IT data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Snipe-IT? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Snipe-IT backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Snipe-IT get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Stirling PDF hosting in the EU URL: https://blitz.cloud/apps/stirling-pdf/ Updated: 2026-10-14 Run your own Stirling PDF, an alternative to Adobe Acrobat and iLovePDF. One-click install, HTTPS, servers in the EU. Free plan, no card. Stirling PDF: merge, split, sign and shrink PDFs, without uploading them to a stranger. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Adobe Acrobat, iLovePDF and Smallpdf Stirling PDF does the job of Adobe Acrobat, iLovePDF or Smallpdf, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Stirling PDF | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Stirling PDF](/get/stirling-pdf/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `stirling.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with this password. 5. Pick a tool, like merge or compress, and drop your PDFs on it. The files stay on your app. ## Good to know Very large PDFs can be more than it has memory for here. ## Deploy button for your README Do you maintain Stirling PDF or write about it? Put this button in a README or a post. A click opens Stirling PDF in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Stirling PDF for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Stirling PDF data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Stirling PDF? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Stirling PDF backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Stirling PDF get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Syncthing hosting in the EU URL: https://blitz.cloud/apps/syncthing/ Updated: 2026-10-14 Run your own Syncthing, an alternative to Dropbox and Resilio Sync. One-click install, HTTPS, servers in the EU. Free plan, no card. Syncthing: keep a folder in step across your computers and phone, with no cloud in between. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 5 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Dropbox and Resilio Sync Syncthing does the job of Dropbox or Resilio Sync, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Syncthing | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 5 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Syncthing](/get/syncthing/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `syncthing.yourname.blitz.cloud`. 4. Open the app's address and set a user name and password under Actions, Settings, GUI. Until you do, anyone with the address can open it. ## While it sleeps Syncthing only syncs while it is awake. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing Syncthing keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Deploy button for your README Do you maintain Syncthing or write about it? Put this button in a README or a post. A click opens Syncthing in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Syncthing for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Syncthing data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Syncthing? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Syncthing backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Syncthing get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # The Lounge hosting in the EU URL: https://blitz.cloud/apps/thelounge/ Updated: 2026-10-14 Run your own The Lounge, an alternative to IRCCloud. One-click install, HTTPS, servers in the EU. Free plan, no card. The Lounge: stay connected to IRC from any device, with your chat history kept on your own server. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to IRCCloud The Lounge does the job of IRCCloud, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | The Lounge | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of The Lounge](/get/thelounge/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `thelounge.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with this password. 5. Add an IRC network and channel from the connect screen. ## Deploy button for your README Do you maintain The Lounge or write about it? Put this button in a README or a post. A click opens The Lounge in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host The Lounge for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my The Lounge data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for The Lounge? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is The Lounge backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does The Lounge get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Traggo hosting in the EU URL: https://blitz.cloud/apps/traggo/ Updated: 2026-10-14 Run your own Traggo, an alternative to Toggl and Clockify. One-click install, HTTPS, servers in the EU. Free plan, no card. Traggo: track your time with tags instead of projects and see where your hours actually went. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Toggl and Clockify Traggo does the job of Toggl or Clockify, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Traggo | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Traggo](/get/traggo/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `traggo.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with this password. ## Deploy button for your README Do you maintain Traggo or write about it? Put this button in a README or a post. A click opens Traggo in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Traggo for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Traggo data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Traggo? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Traggo backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Traggo get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # TriliumNext hosting in the EU URL: https://blitz.cloud/apps/trilium/ Updated: 2026-10-14 Run your own TriliumNext, an alternative to Notion and Obsidian. One-click install, HTTPS, servers in the EU. Free plan, no card. TriliumNext: keep notes in a tree you shape yourself, with checklists, tables and your own encryption for the private ones. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 2 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Notion and Obsidian TriliumNext does the job of Notion or Obsidian, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | TriliumNext | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 2 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of TriliumNext](/get/trilium/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `trilium.yourname.blitz.cloud`. 4. Open the app's address and set a password on first visit. That becomes the only way in. ## Deploy button for your README Do you maintain TriliumNext or write about it? Put this button in a README or a post. A click opens TriliumNext in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host TriliumNext for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my TriliumNext data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for TriliumNext? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is TriliumNext backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does TriliumNext get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Tududi hosting in the EU URL: https://blitz.cloud/apps/tududi/ Updated: 2026-10-14 Run your own Tududi, an alternative to Todoist and TickTick. One-click install, HTTPS, servers in the EU. Free plan, no card. Tududi: organise tasks, projects and notes in one place and keep every bit of it on your own server. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Todoist and TickTick Tududi does the job of Todoist or TickTick, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Tududi | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Tududi](/get/tududi/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `tududi.yourname.blitz.cloud`. 4. Open the app's address and sign in with this password. ## Deploy button for your README Do you maintain Tududi or write about it? Put this button in a README or a post. A click opens Tududi in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Tududi for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Tududi data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Tududi? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Tududi backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Tududi get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Umami hosting in the EU URL: https://blitz.cloud/apps/umami/ Updated: 2026-10-14 Run your own Umami, an alternative to Google Analytics and Plausible. One-click install, HTTPS, servers in the EU. Free plan, no card. Umami: see how many people visit your website and where they come from, without cookies or banners. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS and the PostgreSQL it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Google Analytics, Plausible and Fathom Umami does the job of Google Analytics, Plausible or Fathom, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Umami | |---|---| | Memory | 128 MB reserved from your plan | | Storage | none | | Database | PostgreSQL, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Umami](/get/umami/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `umami.yourname.blitz.cloud`. 4. Open the app's address and sign in as admin with the password umami. 5. Change that password right away under Settings. Anyone who knows Umami knows the default. ## While it sleeps Umami only counts visits while it is awake. A visit wakes it, but that first one may be missed. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing Umami keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Deploy button for your README Do you maintain Umami or write about it? Put this button in a README or a post. A click opens Umami in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Umami for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Umami data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Umami? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Umami backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Umami get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Uptime Kuma hosting in the EU URL: https://blitz.cloud/apps/uptime-kuma/ Updated: 2026-10-19 Run your own Uptime Kuma, an alternative to UptimeRobot and Pingdom. One-click install, HTTPS, servers in the EU. Free plan, no card. Uptime Kuma: get a ping when any of your sites goes down. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to UptimeRobot, Pingdom and Better Stack Uptime Kuma does the job of UptimeRobot, Pingdom or Better Stack, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Uptime Kuma | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## On blitz.cloud | Measured | Uptime Kuma | |---|---| | Installs on blitz.cloud | 10 or more | | Online after installing | about 50 seconds | | Waking up after a sleep | about 45 seconds | | Memory while awake | about 190 MB | | Version | 2, on blitz.cloud since 10 October 2026 | Measured on 19 October 2026 across the Uptime Kuma apps on blitz.cloud. Times and memory are medians, installs a band, and nothing here comes from fewer than 5 installs. ## Install it 1. [Start the install of Uptime Kuma](/get/uptime-kuma/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `uptime.yourname.blitz.cloud`. 4. Open the app's address and create the admin account. Until you do, anyone who finds the address could. ## While it sleeps Uptime Kuma only checks your sites while it is awake. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing Uptime Kuma keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Deploy button for your README Do you maintain Uptime Kuma or write about it? Put this button in a README or a post. A click opens Uptime Kuma in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Uptime Kuma for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Uptime Kuma data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Uptime Kuma? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Uptime Kuma backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Uptime Kuma get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Vaultwarden hosting in the EU URL: https://blitz.cloud/apps/vaultwarden/ Updated: 2026-10-19 Run your own Vaultwarden, an alternative to 1Password and Bitwarden. One-click install, HTTPS, servers in the EU. Free plan, no card. Vaultwarden: A password manager the whole family can use, hosted by you. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to 1Password, Bitwarden, LastPass and Dashlane Vaultwarden does the job of 1Password, Bitwarden, LastPass or Dashlane, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Vaultwarden | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## On blitz.cloud | Measured | Vaultwarden | |---|---| | Installs on blitz.cloud | 10 or more | | Online after installing | about 30 seconds | | Memory while awake | about 50 MB | | Version | 1.37.2, on blitz.cloud since 22 September 2026 | Measured on 19 October 2026 across the Vaultwarden apps on blitz.cloud. Times and memory are medians, installs a band, and nothing here comes from fewer than 5 installs. ## Install it 1. [Start the install of Vaultwarden](/get/vaultwarden/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `vaultwarden.yourname.blitz.cloud`. 4. Open the app's address/admin and sign in with your admin token. 5. Make your own account at the app's address, then sign in there or in any Bitwarden app. ## Deploy button for your README Do you maintain Vaultwarden or write about it? Put this button in a README or a post. A click opens Vaultwarden in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Vaultwarden for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Vaultwarden data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Vaultwarden? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Vaultwarden backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Vaultwarden get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Vikunja hosting in the EU URL: https://blitz.cloud/apps/vikunja/ Updated: 2026-10-14 Run your own Vikunja, an alternative to Todoist and Trello. One-click install, HTTPS, servers in the EU. Free plan, no card. Vikunja: to-do lists and projects for you or the whole household, as lists, boards or a calendar. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Todoist, Trello and Microsoft To Do Vikunja does the job of Todoist, Trello or Microsoft To Do, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Vikunja | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Vikunja](/get/vikunja/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `vikunja.yourname.blitz.cloud`. 4. Open the app's address and register. Everyone who needs an account makes one the same way. 5. When everyone has one, set VIKUNJA_SERVICE_ENABLEREGISTRATION to false in Environment so nobody else can sign up. ## Deploy button for your README Do you maintain Vikunja or write about it? Put this button in a README or a post. A click opens Vikunja in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Vikunja for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Vikunja data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Vikunja? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Vikunja backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Vikunja get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # WAHA hosting in the EU URL: https://blitz.cloud/apps/waha/ Updated: 2026-10-14 Run your own WAHA, an alternative to Twilio and WhatsApp Business API. One-click install, HTTPS, servers in the EU. Free plan, no card. WAHA: A WhatsApp API you run yourself. Connect a number, then send and receive messages over HTTP. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Twilio, WhatsApp Business API and Evolution API WAHA does the job of Twilio, WhatsApp Business API or Evolution API, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | WAHA | |---|---| | Memory | 256 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of WAHA](/get/waha/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `waha.yourname.blitz.cloud`. 4. Open the app's address/dashboard and sign in as admin with this password. 5. Start the session called default and scan its QR code with WhatsApp on your phone. ## While it sleeps WAHA only connected to WhatsApp while it is awake, so messages and webhooks wait until then. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing WAHA keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Good to know The free edition connects one WhatsApp number. WhatsApp does not allow unofficial clients, so a number used this way can be banned. ## Deploy button for your README Do you maintain WAHA or write about it? Put this button in a README or a post. A click opens WAHA in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host WAHA for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my WAHA data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for WAHA? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is WAHA backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does WAHA get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Wakapi hosting in the EU URL: https://blitz.cloud/apps/wakapi/ Updated: 2026-10-14 Run your own Wakapi, an alternative to WakaTime and Code::Stats. One-click install, HTTPS, servers in the EU. Free plan, no card. Wakapi: see how much time you spend coding, per project and language, from your editor's plugin. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to WakaTime and Code::Stats Wakapi does the job of WakaTime or Code::Stats, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Wakapi | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Wakapi](/get/wakapi/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `wakapi.yourname.blitz.cloud`. 4. Open the app's address and sign up, then copy your API key from Settings. 5. In your editor's WakaTime plugin, set the API address to the app's address/api and paste that key. ## Deploy button for your README Do you maintain Wakapi or write about it? Put this button in a README or a post. A click opens Wakapi in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Wakapi for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Wakapi data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Wakapi? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Wakapi backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Wakapi get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Wallabag hosting in the EU URL: https://blitz.cloud/apps/wallabag/ Updated: 2026-10-14 Run your own Wallabag, an alternative to Pocket and Instapaper. One-click install, HTTPS, servers in the EU. Free plan, no card. Wallabag: save articles from the web and read them later, without ads or trackers. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 1 GB of storage, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Pocket and Instapaper Wallabag does the job of Pocket or Instapaper, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Wallabag | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 1 GB | | Database | none | | Plan | Free or Pro | ## Install it 1. [Start the install of Wallabag](/get/wallabag/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created and is online about a minute later, at an address like `wallabag.yourname.blitz.cloud`. 4. Open the app's address and sign in with wallabag / wallabag, the default login. Change the password at once under your account. 5. Install the browser extension or bookmarklet from the Wallabag site to save pages with one click. ## Good to know Reinstalls part of itself on every start, so it wakes more slowly than other apps here, about four minutes rather than a few seconds. ## Deploy button for your README Do you maintain Wallabag or write about it? Put this button in a README or a post. A click opens Wallabag in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Wallabag for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Wallabag data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Wallabag? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Wallabag backed up? On Pro its files are copied every night and kept for 30 nights, and you can put them back from the app's page. On the free plan they are not copied, so keep an export of what matters. ### How does Wallabag get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # Wiki.js hosting in the EU URL: https://blitz.cloud/apps/wikijs/ Updated: 2026-10-14 Run your own Wiki.js, an alternative to Confluence and Notion. One-click install, HTTPS, servers in the EU. Free plan, no card. Wiki.js: A wiki for your team or club, with a friendly editor and search. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS and the PostgreSQL it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Confluence, Notion and Google Sites Wiki.js does the job of Confluence, Notion or Google Sites, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | Wiki.js | |---|---| | Memory | 128 MB reserved from your plan | | Storage | none | | Database | PostgreSQL, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of Wiki.js](/get/wikijs/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `wikijs.yourname.blitz.cloud`. 4. Open the app's address and finish the setup page. Whoever fills it in becomes the admin. 5. Enter the app's address as the site address when it asks. ## Deploy button for your README Do you maintain Wiki.js or write about it? Put this button in a README or a post. A click opens Wiki.js in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host Wiki.js for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my Wiki.js data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for Wiki.js? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is Wiki.js backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does Wiki.js get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running. --- # WordPress hosting in the EU URL: https://blitz.cloud/apps/wordpress/ Updated: 2026-10-14 Run your own WordPress, an alternative to Wix and Squarespace. One-click install, HTTPS, servers in the EU. Free plan, no card. WordPress: build a website or a blog, with thousands of free themes and plugins to pick from. On blitz.cloud you install it from the App Store in one click. It gets its own address with HTTPS, 2 GB of storage and the MariaDB it needs, and it runs on servers in the EU. You can run it on the free plan, without a credit card. ## A self-hosted alternative to Wix, Squarespace, WordPress.com and Webflow WordPress does the job of Wix, Squarespace, WordPress.com or Webflow, but it is your own copy: your data sits in your app, not in somebody else's account, and nobody changes the price or the rules on you. Self-hosting usually means renting a server and keeping it patched. Here the App Store sets it up and keeps it running. ## What it needs | Need | WordPress | |---|---| | Memory | 128 MB reserved from your plan | | Storage | 2 GB | | Database | MariaDB, created and connected for you | | Plan | Free or Pro | ## Install it 1. [Start the install of WordPress](/get/wordpress/). Without an account you create one with Google, GitHub or your email. 2. Pick your address, like `yourname.blitz.cloud`. The app's page in the App Store opens right after. 3. Click Install. It lists what gets created, the database included, and is online about a minute later, at an address like `wordpress.yourname.blitz.cloud`. 4. Open the app's address and pick a language, a site title and your admin account. Until you do, anyone who finds the address could. ## While it sleeps Scheduled posts and plugin jobs only run while it is awake. On the free plan an app sleeps after 30 minutes without visitors. On Pro, installing WordPress keeps it awake. If only this one app has to stay awake, you can make it a [Pro app](/pricing/) instead of moving your whole account. ## Deploy button for your README Do you maintain WordPress or write about it? Put this button in a README or a post. A click opens WordPress in the blitz.cloud App Store, ready to install; someone without an account signs up for free first. ## Questions ### Can I host WordPress for free? Yes. The free plan runs it without a card and without an end date. The app sleeps after 30 minutes without visitors, and the next visit wakes it. ### Where is my WordPress data stored? On blitz.cloud's servers in the EU, run by BlitzWorks, a company in Germany. Once signed in, you can download the [data processing agreement](https://dashboard.blitz.cloud/account/dpa?lang=en) as a PDF. ### Can I use my own domain for WordPress? Yes, on Pro, or on the free plan by making this one app a Pro app. HTTPS for the domain is set up for you. ### Is WordPress backed up? Its database is backed up every night: 7 nights are kept on the free plan, 30 on Pro. On Pro the app's files are copied every night too. ### How does WordPress get updates? With automatic updates on, it gets new versions of its version line overnight. If a new version doesn't start, the one before it keeps running.