Welcome to the Lizard blog

The Lizard blog helps developers turn working code into an application they can deploy, check and operate. It covers the decisions that come after the first successful local run: where the process lives, how it reaches its database, what happens to files and how to recover when something fails.

Start with the task you have

If an agent helped write your app, use the Claude Code deployment guide or Google Antigravity guide. Both explain how to check the live application after deployment.

For Python projects, start with hosting Django, Flask and FastAPI. If you prefer to manage a server, the Django VPS walkthrough covers the process, proxy and release setup.

If you are choosing infrastructure, compare PaaS providers, learn what container as a service includes, or assess Kubernetes alternatives.

How to read our comparisons

We build Lizard, so these articles include our product and explain where it fits. They should also help you identify when another option suits your requirements better.

Prices need their billing units, plan terms and sources. A calculation should state its assumptions. A test result should explain what ran and how it was measured. A product feature should not become a promise about your application's performance or bill.

Use the linked documentation to check the details that matter to your deployment. If you find a mistake or a changed product term, contact us with the page and the claim. For the current command reference and setup instructions, go to the Lizard documentation.