ShippedAgent deployments
Your agent built the app. Let it ship the app, too. Connect Shipped through MCP and take your local project to a live URL.
Ship the code you have right now
Deploy the application in your working folder, including changes you have not committed. The Shipped connector uploads a source snapshot, respects your file exclusions, and filters common secret and cache paths. Review what is being shipped before the build starts. Your folder does not need to be a Git repository.
Give your app the services it needs
Shipped identifies the application’s build and runtime requirements and prepares a deployment plan. Add a web service, database, cache, or storage when your application needs it. Your agent can explain the proposed resources and costs before you authorize them. Shipped then builds the application, connects its services, and checks it before switching traffic.
Keep working from the same conversation
After deployment, ask your agent to inspect logs, check service health, or prepare your next release. Each operation has a recorded result, so closing the conversation does not erase deployment history. The portal gives you another way to inspect the same project, manage access, and review changes made through your agent.
A little more detail
Questions about Agent deployments?
Do I need to push my app to GitHub first?
No. Direct deployment uses a snapshot of your local application files. GitHub is an optional workflow, not a requirement for creating a project or shipping a release.
Can any remote agent read my local folder?
No. Local files are uploaded through the Shipped connector running in your coding environment. A remote agent needs a supported upload connection; sending a folder path alone does not give it access to your computer.
GitHub deployments
Connect GitHub to Shipped for a repository-based deployment workflow with builds, connected services, release history, and compatible rollbacks.
Explore GitHub deploymentsSecrets
Manage application secrets in Shipped, connect them to the right services and environments, and keep credentials out of Git and frontend bundles.
Explore SecretsRollbacks
Restore a recorded application build in Shipped with release history and health checks, while keeping database recovery a separate deliberate operation.
Explore Rollbacks
Next.js
Ship Next.js pages, server routes, and app services together. Deploy from your agent or GitHub with domains, secrets, logs, and rollbacks.
Explore Next.jsFrom your workspace to the web