Spryloom

You built something. Your coworkers should be able to use it.

Spryloom takes the folder your app is in and runs it for your team, behind your company's sign-in, at an address you can send someone. There is no server to choose, no database to set up, no certificate to buy, and no login screen to build. One command, or one sentence to your coding agent.

npm install -g spryloom
spry publish .

https://expense-notes.acme-com.spryloom.app

  ✓ Runtime created
  ✓ Database created
  ✓ Sign-in enabled for acme.com
  ✓ HTTPS enabled

Start here

Getting started — from a folder on your machine to a coworker using it. About five minutes.

Then

• Your app's manifest — spryloom.yaml, field by field. It is the contract: Spryloom builds exactly what it declares.
• Who can use your app — how people get in, how your app knows who they are, and why it needs no sign-in code of its own.
• Data and secrets — the database your app gets, and the values only it should see.
• Commands — every one of them.
• When something goes wrong — what each failure means and what to do about it.

What Spryloom is not

It runs small software for teams: internal tools, admin pages, dashboards, the thing somebody built on a Friday that turned out to matter. It is not a place to run a public product, and it will not pretend to be.

There are things it does not do yet, and they are named where you would look for them rather than hidden. If a page here describes something, it exists.