blitz.cloud changelog

The newest release of blitz.cloud, from 14 September 2026, can build any public GitHub project from its source and put it online. The release before that added cookieless visitor statistics and a cookie consent banner. Every change that affects what you can do is listed here, newest first.

For the current state in one list, see what's live.

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.
• Connecting a GitHub account, which is what private projects and redeploy-on-push need, is not switched on yet.

14 September 2026 - Visitor statistics and cookie consent

• Visits to blitz.cloud and the dashboard are counted with BlitzWorks' own Matomo in Germany, 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.