Projects at a glance, and databases made for your app

The top bar says where you are, a project opens on what it holds, and the database your code needs is made and connected before your first deploy.

Updated 27 Oct 20261 min read

You always know where you are, and an app gets the database it needs without you opening another page.

What's new

Account / project / service in the top bar: on an app's page it reads Asha's account / Shop / shop, with a menu at each step. One click on Shop goes up to the project.
A project opens on what it holds: one app or site opens straight on it, and so does a project with just a database. Two or more apps open on a map of the project's services.
The services map: apps and sites on the left, databases, caches and storage on the right, with a line from each app to what it uses. On a phone, each app says what it uses. A database says who uses it: "Shared with web and api".
Projects has its own page: every project in the account at Projects, and New project beside it.
Databases that make themselves: add a Laravel app from GitHub and, before you deploy, the page says "This is Laravel and uses MySQL", with the price a month first. Keep the switch on, and the database is made and connected before your first version starts, its migrations run on deploy, and PHP gets its database extension. Laravel's default sqlite becomes MySQL, so your data isn't lost at the next deploy. Prisma, Drizzle, Django, Rails, WordPress code and Node.js and Python drivers are read too, and a Valkey cache is offered when your code uses Redis.
Make one and connect it: an app that expects a database it hasn't got gets the same button on its page, beside Connect an existing one.