SpringRoll Deploy

Deploy apps your team can use

Bring the app you built with Codex, Claude Code or Cursor. SpringRoll turns the source into a recorded release, runs its deployment on managed Vercel or Cloudflare, and gives your team a SpringRoll link to launch it.

Keep building with your coding agent

Keep the source and the development workflow your team already uses. Connect your agent to SpringRoll when the app is ready for its deployment handoff. Your builder focuses on the app; the control plane records ownership, runtime requirements and the release that will run.

This works well for a team dashboard, an internal request tool or a focused operations app. Start with a small workload you can test with synthetic data and a named person who will own the app after the first release.

From source to a working team link

The agent registers the application, freezes an immutable release and starts a deployment. Follow the build result in the app overview instead of trying to infer success from an agent's last message. A READY result identifies the deployment; opening the app checks that the result actually works.

The current working version and the latest attempt are shown separately. If an update fails to build, use its error to fix the source or build configuration while the previous working version remains available.

  • Name an app owner and support contact.
  • Keep the release, deployment and environment together.
  • Open the working app before handing it to colleagues.

Choose the workflow that fits the app

Direct to Production is the default. Once required checks pass, the deployment can proceed without a separate workflow approval. Ownership, access, data, configuration and runtime checks still matter.

A Tenant Admin can configure staged Development, UAT and Production for apps that need a review before release. Reviewers decide on a recorded release, so the app being reviewed is the app being promoted.

Managed hosting with a deployment receipt

SpringRoll manages the hosting accounts on Vercel and Cloudflare. Placement considers the app's runtime needs before comparing eligible products and estimated cost. The deployment receipt records the executed placement, estimate and assumptions so your team can assess the choice.

Before using an app with sensitive data, confirm its framework, build requirements, storage and background-work needs against the available runtime. The hosting guide explains how to review that fit and what to check at the provider boundary.

Make the handoff useful to everyone

Share the SpringRoll app link and its intended environment. The App Portal gives colleagues a place to discover the apps available to them, with ownership and a route to the working app.

SpringRoll checks access at portal launch. A provider hostname is directly reachable and uses the provider's own access settings. Configure application or provider authentication for that path too; a portal audience is not complete origin isolation.