Skip to content
LazyFrog
Start free
Menu

Changelog

What's new

  1. Free is for building and trying

    • · Free is now for building and trying things out: your AI builds the project and shows it in a preview at its own random address, which anyone with the link can open while it's awake.
    • · Going live, at name.lazyfrog.app or your own domain, needs a paid plan, Hobby or above.
    • · Free sites that were live before today keep running for 30 days, and their owners get an email about it. After that they show a short paused page until the owner upgrades, and nothing is deleted.

  2. Platform version 20261026.15

    • · Archiving a project takes its live site offline until you unarchive it; visitors, on custom domains too, see that it's archived.
    • · A plan's new memory no longer restarts the sandbox while a command is running, and a running command is never blamed on memory for it.
    • · A crashed live site shows on your project's page and sends a notification, and a page that crashed the site isn't reloaded by itself.
    • · Publishing brings it to your live site, with a restart of a few seconds.

  3. Platform version 20261026.14

    • · A page that makes your site restart no longer reloads itself over and over: visitors see that the site is restarting, and a crashed live site tries again by itself every few minutes.
    • · A plan change now applies to your running preview's memory, straight away when it can and otherwise at its next quiet restart.
    • · When the host stops a service for memory, its restart note names the process.
    • · Publishing brings it to your live site, with a restart of a few seconds.

  4. Platform version 20261026.13

    • · A service killed at the memory limit says so ("killed at 768 of 768 MB, likely for memory"), naming the process.
    • · While your database recovers after a crash, it stays shown as recovering until it is really back, and no restart is needed.
    • · When the sandbox is full, your AI is told what the biggest service and the database each hold.
    • · Publishing brings it to your live site, with a restart of a few seconds.

  5. Platform version 20261026.12

    • · Reading each service's memory for the status no longer takes room from your own commands, so a type check beside a running Next.js dev server fits again.
    • · Publishing brings it to your live site, with a restart of a few seconds.

  6. Platform version 20261026.11

    • · If your preview stops because it ran out of memory, it is shown as stopped, with the reason, instead of asleep.
    • · A service that restarted by itself says when and why, for example when it was killed at the memory limit.
    • · Each service's memory in the status is its own, not an even share.
    • · Publishing brings it to your live site, with a restart of a few seconds.

  7. Platform version 20261026.10

    • · While your database recovers by itself after a crash, it is shown as recovering, and your AI is told it will be back without a restart.
    • · When the sandbox is out of memory because of your app's own services, your AI is always told which service to restart.
    • · Each service's memory in the status now adds up to what the sandbox uses.
    • · Publishing brings it to your live site, with a restart of a few seconds.

  8. Platform version 20261026.9

    • · A publish or rollback is in force for every visitor the moment it says so.
    • · If your app's development server fills the sandbox's memory, your AI is told which service to restart, and the service status shows each service's memory.
    • · While your database starts again after a crash, it is shown as down until it is really back.
    • · Publishing brings it to your live site, with a restart of a few seconds.

  9. Platform version 20261026.8

    • · A commit is saved only after its check for secrets has finished: if the check can't run (for example when the sandbox is out of memory), nothing is committed and you're told to try again.
    • · Publishing brings it to your live site, with a restart of a few seconds.

  10. Platform version 20261026.7

    • · If your database stops because the disk was full, it starts again by itself once there is room, and your AI can restart it.
    • · When your plan runs fewer services than your project defines, your site's own service always runs first.
    • · A command stopped for using too much memory keeps the output it had written.
    • · Publishing brings it to your live site, with a restart of a few seconds.

  11. Platform version 20261026.6

    • · Type checks and installs beside your app's development server fit again: a command is stopped only when the sandbox is really about to run out. A production build still needs about as much memory again as the development server, so your AI checks it with a preflight, which builds in a sandbox of its own.
    • · The design check and screenshots see pages that load their content in the browser, including while your app runs its development server.
    • · A row of short links, such as booking times, is no longer reported as a lone item.
    • · If the disk fills up, your services' latest log lines are kept until there is room again.
    • · npm's and bun's downloads are kept with your project, so installs after a wake are faster.
    • · Publishing brings it to your live site, with a restart of a few seconds.

  12. Platform version 20261026.2

    • · Commands next to a busy app get the memory they need again: saving your work and publishing no longer stop for memory when your app's own memory is shared between its processes.
    • · Publishing brings it to your live site, with a restart of a few seconds.

  13. Platform version 20261026.1

    • · A command that uses too much memory is stopped on its own, with a plain message; your site and its database keep running.
    • · If the disk fills up, deleting files frees the space straight away, and your AI can still work on the project while it does.
    • · The design check notices a page that crashed or is still loading, and counts every kind of placeholder your site still has.
    • · Publishing brings it to your live site, with a restart of a few seconds.

  14. Platform version 20261025.24

    • · The design check no longer reports text over a photo, a gradient or a drawing as unreadable; only text the same colour as its background counts.
    • · Publishing brings it to your live site, with a restart of a few seconds.

  15. Platform version 20261025.23

    • · Stock photos from Unsplash, credited on the site and listed under Photos on your site.
    • · Link buttons keep their label colour, and serif headings fall back to a serif font while the site's own font loads.

  16. Platform version 20261025.22

    • · The design check says when a page answers “not found”, instead of reporting it as a page without a title.

  17. Platform version 20261025.21

    • · What your site still needs from you (your photos, prices, address) is outlined on the preview, counted at every publish and listed on the Overview under Needed from you.
    • · Design checks at phone, tablet and wide screen sizes.

  18. Off-site backups, and any stack your way

    • · Encrypted backups to a second location, with restore tests.
    • · Build with the framework you prefer, including Laravel, Rails, Django, Phoenix, SvelteKit and Go, set up the way that framework expects.
    • · PHP, Go and Rust projects run more smoothly, and the security scan now checks PHP, Ruby and Go dependencies.
    • · Publishing an update now moves your live site to the newest platform version, with a restart of a few seconds.

  19. Share, remix and start from a blueprint

    • · Make a project remixable or public, so others can copy it into their account. Its secrets and live data never go with it.
    • · Share links with a picture of your live site, offered right after a publish.
    • · Twelve blueprints, each built and checked on LazyFrog before it's listed.
    • · Invite a friend. When they keep a site live for 30 days or start paying, you each earn a month of Hobby.
    • · In AI apps that support it, such as Claude and ChatGPT, a card in the chat shows your project's live preview and a Publish button.

  20. Launch

    • · Publish with no downtime. Database changes are rehearsed on a copy first, and rolling back takes seconds.
    • · Connect your own domain, with HTTPS ready before the switch.
    • · Your app can send email, such as sign-up confirmations and receipts.
    • · Apps can use AI with your provider key kept out of the app, under a monthly cap.
    • · Apps can render PDFs and images of their own pages.
    • · A security and quality scan that suggests a fix for each finding.
    • · The live site is checked against what you published, and you get a notice if its files change outside a publish.
    • · When your AI needs a key, it sends you a link to paste it into, so it never passes through the chat.
    • · Import an app from Lovable, Bolt, v0, Replit, Vercel or any repository. Your AI adapts it and starts the preview.
    • · Export everything, including the code with its history, both databases, your files and a moving-out guide.
    • · Clone your code read-only with a personal token, or browse it under Project › Code in the portal.
    • · On Pro, invite up to three people per project, each with their own AI. They see only that project.
    • · Transfer a project, with its live site, to someone else's account.
    • · Deleted projects wait in the Trash for seven days, one click from coming back.
    • · Delete your account yourself, with 30 days to change your mind.