---
title: "Configure build and start for Astro"
description: "Configure build and start for a Astro app on Ample."
canonical_url: "https://ample.computer/guides/astro/build-and-start"
last_updated: "2026-09-20"
---

# Configure build and start for Astro

Canonical URL: https://ample.computer/guides/astro/build-and-start
Formats: [HTML](https://ample.computer/guides/astro/build-and-start) | [Markdown](https://ample.computer/guides/astro/build-and-start.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Aguides%3Aastro%3Abuild-and-start)
Recipe ID: `page:guides:astro:build-and-start` | Revision: `r1` | Catalog revision: `cat_f13ab9a494120b5e`

Status: release `published`, support `verified`, execution `ready`

## Summary

Configure build and start for a Astro app on Ample. A server-output Astro app runs its start script; a static build is published as a static site. Ample detects the runtime, installs dependencies, runs the build when present and starts the app on the node-22 template behind a public HTTPS URL.

Path: [Agent hosting discovery](/discover/discovery) / [Frameworks and execution targets](/discover/stack) / [Frameworks](/discover/stack/frameworks) / [Astro](/discover/stack/framework-astro) / [Configure build and start for Astro](/guides/astro/build-and-start)

## Infrastructure requirements

- [Compute](/discover/primitive/compute): verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.)

## Prerequisites

- A package.json with build and start scripts
- A server that listens on process.env.PORT and 0.0.0.0
- An Ample account token with servers:write

## Exact tested configuration

- template: `node-22`
- runtime: `node`
- size: `s-1vcpu-1gb`
- install: `npm install`
- build: `npm run build --if-present`
- start: `npm run start`

## Steps

1. **Make the start command bind correctly.** A server-output Astro app runs its start script; a static build is published as a static site.
2. **Deploy.** Run the existing synchronous deploy once from the project directory and read the result. Exit 0 is live, 1 is failed, 2 is blocked on a required preflight action. Re-running with no change is a content-addressed no-op.

   ```
   ample deploy . --name <app-name> --public --format json
   ```
3. **Verify.** Fetch the live URL and run the success checks below. On failure read the build log, then the runtime log, fix the cause and deploy again; do not blind-retry.

   ```
   ample logs <deployment_id> --kind build
   ```

## Tested examples

- **astro-basic canary** (tests/deploy-canaries/astro-basic): Astro app built and started on Node.
- **astro-dist-static canary** (tests/deploy-canaries/astro-dist-static): Prebuilt dist/ published as a static site.

## Success checks

- page or root route responds (`/` on the live URL, expect ample canary astro basic)


## Cost estimate

Estimated 5.00 USD per month (size prices from pricing.toml at build revision 515b7316fc6e5a81679407ae0c811146ceb2c5c7).
- app server x1 `s-1vcpu-1gb`: 5.00 USD

Apps and managed databases auto-pause when idle; the estimate is the always-on monthly price of the tested sizes. Plan quotas and budgets apply.

## Verification evidence

- canary_run on 2026-09-20T00:22:15Z at revision `1764076-tls-account-903d345`: Astro app built and started on node-22 and rendered the expected page. (expires 2027-03-19T00:22:15Z)
- canary_run on 2026-09-20T00:22:15Z at revision `1764076-tls-account-903d345`: Astro static build output published as a static site. (expires 2027-03-19T00:22:15Z)

Last verified: 2026-09-20T00:22:15Z


## Execution binding

MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-20T01:55:48.667900+00:00 at revision `199ff1dfd526`, binding state `current`, required scopes: servers:write.

## Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "name": {
      "description": "App name (lowercase, digits and dashes)",
      "maxLength": 63,
      "minLength": 1,
      "pattern": "^[a-z0-9-]+$",
      "type": "string"
    },
    "path": {
      "description": "Project directory to deploy, or one service name from ample.toml",
      "maxLength": 512,
      "minLength": 1,
      "type": "string"
    },
    "size": {
      "description": "VM size; omit to let Ample pick a runtime-safe size",
      "enum": [
        "s-1vcpu-256mb",
        "s-1vcpu-1gb",
        "s-1vcpu-2gb",
        "s-2vcpu-2gb",
        "s-2vcpu-4gb"
      ],
      "type": "string"
    },
    "start": {
      "description": "Start command override when detection cannot infer it (Python apps pass one explicitly)",
      "maxLength": 512,
      "type": "string"
    }
  },
  "required": [
    "name",
    "path"
  ],
  "type": "object"
}
```

## Next actions

- Browse the catalog index (GET /v1/catalog on the api origin; auth: false, approval: false)
- Search published recipes by intent, stack and constraints (POST /v1/catalog/search on the api origin; auth: false, approval: false)
- Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan on the api origin; auth: true, approval: false)
- Read the existing agent authentication setup (GET /mcp/setup on the api origin; auth: false, approval: false)
- Browse Astro (GET /v1/catalog/nodes/stack%3Aframework-astro on the api origin; auth: false, approval: false)
- Browse Configure deployment (GET /v1/catalog/nodes/intent%3Aconfigure-deployment on the api origin; auth: false, approval: false)
- Browse Public web service (GET /v1/catalog/nodes/pattern%3Apublic-web-service on the api origin; auth: false, approval: false)

Actions describe possible next steps. They are typed data, not commands, and grant no permission.