🚧
Live before Sunday night.
Side project hosting
Most side projects die undeployed. The first evening decides which ones don't.
Built with
Built by
Features
Benefits
Solutions
An idea on a Saturday that should be on a real URL by Sunday evening. It might become something. It probably won't. Both outcomes are fine, and the hosting shouldn't punish either.
The first evening is the whole battle
A side project that isn't deployed the first evening usually never is. The gap between "runs on a laptop" and "has a URL somebody else can open" is where most of them die, and it's rarely the code that killed them.
What a hack needs on day one is small: PHP, a database, and an address. Each new app starts as a free trial — seven days, no credit card — and answers on a test domain with TLS already in place. For a one-person project the stack that reaches a working page fastest wins, and PHP remains hard to beat there: connect the GitHub repo, push, the deploy service runs Composer.
Kill it or grow it
Most of these go nowhere, and the platform is built for that: a trial app with no payment method deletes itself at trial end, and a paid app stops billing the day it's deleted. The few that grow scale a component at a time, on the same host, without a migration.
That asymmetry is the point: the downside is cheap and the upside doesn't require moving.
Trust
An honest account.
