A Linux server on your own computer, in a tab.
Sonda Virtual Machine, in the title bar: as many small Linux servers as you want, each with a name, its processors, its memory and its disk, each a tab with a console. Install what an API needs from a menu — a language, a database set up and reachable, a web server — run the API there, and call it from any request at the machine's address. Nothing is downloaded to make a machine: the Linux is inside Sonda.
At a glance
A lab, not a cloud.
Where an API under development used to run on your own system, or on a server reached through a tunnel, it can run here: a small Linux of its own, a few megabytes on the disk, started and stopped from the tab. An API in one machine, a database in another, each in its own tab.
Each machine has a network card on the computer's private network: an address this computer reaches and nothing outside it does. A request to it works like one to localhost, and every port something listens on in the machine is a button above the console — New request in a project, Open in the browser, Copy the address. A machine belongs to the computer: it is in no workspace, no account owns it, and nothing of it is ever published or shared.
Made in a dialog, kept until you remove it.
What a machine is between its first start and its last: the console, the address, the files, and what Sonda believes of it.
Made in a dialog, started in seconds.
A name, processors and memory on sliders, the disk's size. Create — nothing starts, no disk is made until the first start, and the first start takes seconds. A machine that exists keeps everything installed in it from one start to the next, until Reset gives it a new disk or Remove takes it from the computer.
The console is the machine's own.
In the tab, the same terminal Sonda uses for its shell. Leave the tab and come back: what the machine said meanwhile is there, once, nothing drawn twice. A stopped machine shows its name and its three verbs where the console would be.
An address this computer reaches and nothing outside it does.
Each machine has a network card on the computer's private network. A request to it works like one to localhost. Every port something listens on in the machine is a button above the console — New request in a project, Open in the browser, Copy the address.
Nothing is fetched to make the machine.
The kernel, the first file system and the disk a machine starts from are inside the build, made from Alpine's own release files — every sum and every package's license written down beside them. What the machine itself reaches out to, when you install something in it, is what you asked for.
Files go either way.
On a Mac, a sheet with a folder of this computer beside a folder of the machine: copy a project in, copy a log out, make a folder, delete in the machine. What the machine sends back is unpacked under the folder you chose and nowhere else.
Read as a stranger.
Everything that comes from inside a machine — its address, what it can install, what listens — is held to a shape before Sonda believes it. A machine is a computer you run programs on; the window treats it as one.
What an API needs, from a menu.
One command of the machine's own is typed in the console for each — sonda install postgres — and the console shows every step it takes. Nothing is installed out of sight, and the machine says in seconds when it cannot reach out, with the VPN and the firewall named as the usual reasons.
Beside this, PostgreSQL going in: installed, its database made, started, opened to the computer and given a password of its own — twenty characters made in the machine, kept in the machine and nowhere else. How to connect says it in the console, with the connection string.
A whole deployment, one click, with its project.
Under Samples in the Install menu: a small shop, deployed the way an API is deployed on a server, and the project in Sonda that calls it.
The dialog
Samples, in the Install menu. A dialog says what will be done; Install does it, and the console shows every step.
In the machine
A Node.js API with a SQLite database — Node's own, nothing from npm — a website that calls it, and nginx in front, serving the site on port 80 and passing /api to the API. Products, orders, stock that goes down with an order in one transaction and comes back when it is cancelled, stats. The API is one file to read and change, the website another.
In Sonda
A project in the workspace, this computer's own: a variable baseUrl for the machine's address and a request for every route — health, stats, the website, products listed, searched, added, changed and removed, orders listed, placed and cancelled — the bodies filled in. Send one from Sonda while the page is open in a browser and watch the stock move.
As a service
The API and nginx are services like the others: Start, Stop, How to connect, and a start with the machine. Stop the service, edit server.js, start it: the change is live. Install the sample again and the files are laid out anew; the database is not touched.
Two systems, the same tab.
What differs between them, the tab says.