Small team tools, shared through a link

Your coding agent builds the tool; Spryloom puts it in front of your team. Publish from Claude Code, Codex or Cursor, and the people you invite sign in with their email and use it in a browser. Hosting, sign-in, a database and email come built in.

Spryloom is free during the beta, and anyone can sign up with an email address.

What you can publish

	Good for	What it gets
A page	Reports, documents, prototypes	A private address in seconds. No server.
A page that saves data	Checklists, sign-offs, sign-up sheets	Lists Spryloom keeps, each record stamped with who saved it. No server.
An app	Approvals, trackers, anything with rules, reminders or email	Its own server and Postgres database, scheduled jobs, email, outside services.

You don't have to choose up front. Your agent picks the smallest one that does the job and tells you why, and a page becomes an app at the same address when it needs a server, with every saved record moved into its database.

Pick your starting point

I want to publish something: add Spryloom to your agent and ask it to publish. Or use the spry command yourself.
Publishing, step by step: every step from a folder to a link, and what each stage of a publish means.
Using Spryloom from your agent: set up the MCP server in Claude Code, Codex or Cursor, and what you can ask.
I was invited: open the email, sign in, and use it. Nothing to install.
What can I build?: scenarios and the prompts to give your agent.

Who does what

You and your agent build the screens and the rules, and decide who may open it. Spryloom doesn't invent the tool; your agent writes it from what you ask.

Spryloom hosts it, gives it an address, signs people in before they reach it, and keeps its data: lists for a page, a Postgres database for an app.

Your coworkers open an invitation, sign in with that email, and use it. They don't need a terminal, a coding agent or an account anywhere else.

Before you put real work in it

Rolling back an app's code does not undo changes to its records. Keep your own export of anything you can't afford to lose: spry data export for a page's lists, and your app's own export for its database. File uploads and apps anyone can open without signing in aren't available yet.

An app can run on a schedule, email the people who use it, and call outside services from a fixed list: see jobs and email and outside APIs.

Concepts

How Spryloom works: the pieces, what happens when you publish, and how sign-in reaches your app.
Workspaces and sharing: company and personal workspaces, and who sees which apps.

Reference

Your app's manifest: what your page or app needs to run.
Security and access: who can open it, identity, and roles.
Data and secrets: a page's saved lists, an app's database, and secrets.
Commands: every spry command, and the agent tools.
Troubleshooting: failure messages and what to do.

Nobody has to approve you. For questions or feedback, contact hello@spryloom.com.