Blog

Vercel, display.dev or Spryloom: where should an AI-built app for your team go?

Three places to put what your coding agent made. What each one is for, where each one stops, and how to tell which one your app needs.

Your agent finished something, and it needs to live somewhere other than your laptop. Three names come up often when people ask where: Vercel, display.dev and Spryloom. They are not three versions of the same product. Each was built for a different job, and the right choice depends on what your agent made and who will open it.

We make Spryloom, so read this knowing who wrote it. We have tried to say plainly when each of the other two is the better choice. What we say about display.dev comes from its own site as we read it in early November 2026. Products change quickly in this space, so check their current pages before you decide.

Two questions decide most of it

Who opens it? Anyone on the internet, or a known set of people: your team, a few colleagues, a client.

What is it? A document (a report, a spec, a dashboard of fixed numbers, a slide deck) or an app (something that saves what people enter, runs on a schedule, or shows different things to different people).

A document An app Anyone People you know Vercel: public sites and products display.dev Spryloom Spryloom pages
Where each one starts. Vercel is for anyone. For people you know, display.dev starts from documents and Spryloom from apps.

Vercel: a host for public products

Vercel runs web apps, and developers know it well. It is a general host, like Railway, Render and Fly.

It is the better choice when the thing is public. A marketing site, a product your customers sign up for, a tool that strangers should be able to open without an invitation. Spryloom doesn't do this: everything on Spryloom sits behind sign-in, and our own agent skill tells the agent to say so and use the host the person asked for when they want a public site.

It is also a good choice when a developer will look after the app, adding sign-in, a database and deploys with the most freedom.

For an internal tool, the host runs the code, and most of the rest is yours.Sign-in, the database and the deployment setup are the parts that get stuck.

Where it stops: Vercel can put a deployment behind a Vercel login, which lets in people with Vercel accounts who have access to the project, and its Enterprise plan can put one behind your company's identity provider (it calls this Passport). Otherwise the app needs its own sign-in, database setup and deployment configuration, which is where someone who isn't an engineer gets stuck or quietly goes wrong. How to share a Claude Code app with your team walks through those steps.

display.dev: pages your team reviews

display.dev publishes the HTML and Markdown pages an agent makes (reports, specs, dashboards, slides) at a link only your company can open. Its own description, as of November, is an "AI docs workspace". It works with many agents, including Claude, Codex and Cursor, through an MCP server, a CLI and an API.

What it does well, from its site:

  • A review loop. People comment on the page; the agent reads the comments and publishes the next version at the same address. Paid plans can restore older versions.
  • Many documents, organized. Spaces and folders by team or client, and search across everything a person can open.
  • Unlimited viewers on every plan. One more reviewer never costs a seat.
  • Company sign-in. An emailed one-time code, and on paid plans Google or Microsoft accounts at the company's domain.

It is the better choice when the work is documents that get reviewed. If your team's agents produce reports and specs that people comment on and the agent revises, that loop is its core, and Spryloom has no commenting on pages. If you need Google or Microsoft sign-in today, its paid plans have that and we don't.

Where it stops: its published pages are static. They have no server code, no database and no scheduled jobs. Its site says internal apps and data-source connections are in private beta; we don't know how far along that is.

Spryloom: apps your team uses

Spryloom runs what your agent built for the people you invite, behind sign-in. That can be a page, a page that saves data, or a full app.

  • A full app gets its own microVM, its own Postgres database, scheduled jobs, email to the people who use it, and access to outside services from a fixed list (Stripe, Slack, GitHub, HubSpot, Airtable, Google Sheets and others), with keys held as secrets.
  • Who is who. The app is told each visitor's email and role (admin or user) in headers Spryloom sets, so it can show different things to different people. The app contains no sign-in code.
  • A page is plain files behind the same sign-in. A page that saves data keeps lists of records, each stamped with who saved it and when, and grows into an app at the same address when it needs a schedule or email.
  • The agent writes a spryloom.yaml declaring what the app needs, and Spryloom creates exactly that.

It is the better choice for an app for people you know that saves what people enter, sends a morning reminder, or shows the approver something the requester doesn't see, when nobody wants to run a server.

Side by side

Vercel

Public sites and products

Best when anyone should open it, or a developer will run it.

  • Server code, room to grow
  • Sign-in and database are yours to add
display.dev

Documents a team reviews

Best when people comment and the agent revises.

  • Comments, versions, folders
  • No server code or database
Spryloom

Apps a team uses

Best when it saves data, runs on a schedule, or has roles.

  • Server, Postgres, jobs, sign-in
  • Nothing public, no comments
Vercel display.dev Spryloom
Made for Public sites and products Documents a team reviews Apps a team uses
Who can open it Anyone, unless you turn on Deployment Protection or add sign-in People your company lets in, or anyone if a page is made public People you invite, or your company's domain
Sign-in A Vercel login, Passport on Enterprise, or yours to add Email code; Google and Microsoft on paid plans Email link; no Google or Microsoft
Server code Yes No Yes
Database From its Marketplace, yours to connect No One Postgres database per app
Scheduled jobs Cron jobs in vercel.json that call your functions No Declared in spryloom.yaml
Knows who is who inside the app Through the login you add, or Passport on Enterprise Not applicable to static pages Email and role in headers
Works from Any repository Many agents, by MCP, CLI or API Claude Code, Codex, Cursor, any MCP agent, a terminal

How to choose

Anyone on the internet should open it→Vercel, or another general host
A developer will run it and wants full control→Vercel, or another general host
Agents write reports and specs that people comment on→display.dev
You need Google or Microsoft sign-in today→display.dev, or a host with an identity proxy
It saves data, runs on a schedule, or has roles, for people you know→Spryloom
A finished report for a few people, no comments needed→display.dev or a Spryloom page

What Spryloom doesn't do

  • Nothing public. Everyone who opens an app or page signs in.
  • No comments on pages, and no folders or search across documents.
  • Sign-in is an emailed link. No passwords, no Google or Microsoft sign-in.
  • No file uploads. Apps keep what matters in their database.
  • Outside services come from a list. Anything else is refused until it is added; ask us at hello@spryloom.com.
  • Limits. 10 apps per workspace and 25 invited people per app. Pages don't count toward the 10.

Start here

In Claude Code:

/plugin marketplace add spryloom/claude-plugin
/plugin install spryloom@spryloom

In Codex:

codex mcp add spryloom -- npx -y spryloom mcp

In Cursor or any MCP agent, use npx -y spryloom mcp as the server command. Then ask the agent to publish what it built for the people who should use it.

Spryloom publishes apps and pages built with a coding agent behind sign-in, for the people you invite. This article was written by the people building it.

Get started free