Deploy to your cloud
A shipped project deploys to your own cloud account: AWS, Microsoft Azure or Google Cloud. You see what it will create and what it will cost before anything is made, and your cloud bills you directly.
Connect a cloud
An owner connects the cloud once, in Settings → Connections, under Run your apps: an AWS access key, an Azure service principal, or a Google Cloud service account key. Each is checked when it's saved, and its keys never leave the server. A workspace can connect several accounts of the same cloud, like Production and Staging.
Pick where it runs
On the project's Deploy tab you pick two things, with what it would cost a month on the side:
- 1Account: which connected cloud account it runs in. Each account is its own choice, so two AWS accounts are two cards.
- 2How it runs: One server (everything on one server: the cheapest way, backups are up to you) or Managed (the cloud runs each piece for you, with backups, updates and restarts). The cheapest is tagged Cheapest; Maria decides how each piece runs inside. Then 🚀 Plan.
Plan, then go live
- 1Maria gets it ready: she writes the infrastructure for it, which is checked against your cloud.
- 2You see the plan in plain words: Before it's created, here's the plan, what it creates, changes or removes, and what it costs a month. Anything that would lose data is called out in red.
- 3🚀 Go live. Nothing is created until you do.
Until it's live, Change setup moves it to another account or way. Only owners deploy; everyone can look.
It's getting ready, waiting for you to go live, live, didn't finish, or stopped. ↻ Update deploys the latest version the same way, plan first. ⏹ Stop deletes everything it runs in your cloud, its data included, so it stops costing money; Start over then forgets its setup. The infrastructure is kept in the project's repository, under neotexa/infra/.
The keys of outside services the app uses come from the project's Secrets tab, the same ones the preview uses.
Health once it's live
Once live, it shows its last 7 days: processor, memory, disk, database, visits a minute, errors and the slowest answers, each one 🟢 plenty of room, 🟡 getting tight or 🔴 needs more (⏳ on its first day: the numbers show a day after it's live). When it needs a bigger size, or could do with a smaller one, it says which and what it costs; Apply prepares the update for you to confirm.
Neotexa checks every 6 hours. An app that newly needs more resources shows on the project's Activity and is sent to your alerts.