Request path

Know where your code goes.

  1. 01

    Authenticated request

    The Next.js gateway reads your session and forwards only your verified user ID.

  2. 02

    Isolated build

    The API starts one Fargate task with a short-lived callback token and no AWS task role.

  3. 03

    Static publish

    The worker uploads the generated bundle to a project-specific S3 prefix.

  4. 04

    Private delivery

    CloudFront publishes that private prefix at an isolated HTTPS address.

Before you start

EzDeploy currently publishes static npm projects. Check all four requirements before starting a build:

  • The repository is public and hosted on github.com.
  • package.json contains a build script.
  • The build writes static files to dist, build, out, or public.
  • The build finishes within 15 minutes and does not require private environment variables.

Create a deployment

  1. 1. Sign in. GitHub sign-in lets you browse compatible public repositories. Google sign-in can still deploy by URL.
  2. 2. Choose the repository. Select it from the list or paste its public GitHub HTTPS URL.
  3. 3. Name the project. The project ID uses lowercase letters, numbers, and hyphens. Leave it blank for an automatically generated ID.
  4. 4. Watch the build. The dashboard keeps the logs, then shows the CloudFront URL after publishing completes.

Current limits

RepositoryPublic GitHub HTTPS only
Build time15 minutes
Concurrent builds3 per account
Output size500 MB total
Single file25 MB
File count10,000
Beta capacity90 active or published projects
Stored deployments200 per account; 100 shown

Server-rendered applications, private repositories, custom environment variables, and custom domains are not supported yet.

When a build fails

Open the deployment logs and work upward from the final error. Reproduce the same commands locally with npm ci and npm run build. Builds that stop reporting for 30 minutes are marked failed rather than left in a stale “building” state.