Build
Use npm run build. Commit the lockfile and pin the runtime version so a rebuild installs the same dependency graph.
Review deployment docs →Astro · Deployment guide · Hosting
Deploy Astro with the runtime made explicit.
Content sites, documentation, marketing pages, islands-based interfaces, and static storefront frontends. Darwa AI connects the repository, runs npm run build, deploys the result on static output or adapter-based server, and keeps domains, HTTPS, releases, logs, and billing in the same workspace.
- Static output or adapter-based server
- Deployment model
- npm run build
- Build command
- dist
- Expected output
- Frontend Cloud
- Recommended Darwa product
What a production Astro deployment needs.
These are operational requirements, not a generic framework feature list. Confirm them in the repository before the first release.
Start
Production start: Adapter-specific for SSR. The command must stay in the foreground and report a failed boot with a non-zero exit code.
Explore Frontend Cloud →Artifact
Expected deployable output: dist. Generated artifacts should come from the build rather than being edited after release.
Configure the build →Configuration
Store secrets and environment-specific values in the service environment. Do not commit production credentials or bake them into frontend bundles.
Manage configuration →Health and logs
Expose a lightweight health endpoint, keep startup logs actionable, and verify the public endpoint after every release.
See runtime operations →Known boundary
Static Astro belongs on Frontend Cloud. SSR requires a supported server adapter and should be deployed as a Web Service instead of uploading static output.
Check a workload with Darwa →From Astro repository to a repeatable release.
A successful first deploy is not enough. The release must be reproducible, observable, reversible, and safe to scale.
Connect source01
Select the repository and production branch. Keep preview work isolated from the production service.
Detect and confirm02
Confirm static output or adapter-based server, the build command, output, and production start command instead of relying on a lucky default.
Add environment03
Set secrets and public configuration with the correct build-time or runtime scope.
Deploy and verify04
Watch the build, startup, and health checks; then exercise a real application path rather than only the homepage.
Attach the domain05
Point the domain after the generated endpoint is healthy. Managed HTTPS should complete before traffic is moved.
Plan rollback06
Keep the previous successful release available and make database changes backward-compatible before scaling replicas.
Products, plans, and regional guidance.
Frontend CloudThe recommended Darwa AI product for this Astro deployment.→PricingCompare current plan resources and renewal pricing.→Web ServicesAlways-on APIs and server applications.→Frontend CloudStatic build output on global delivery.→Managed databasesPostgreSQL, MySQL, Redis, and compatible data services.→All frameworksCompare the deployment model for another framework.→
Answers before you deploy.
Can Darwa AI host Astro?+
Yes. Content sites, documentation, marketing pages, islands-based interfaces, and static storefront frontends. The recommended starting product is Frontend Cloud, subject to the runtime boundary described on this page.
What build command should I use for Astro?+
Start with npm run build. Keep the dependency lockfile committed and test the same command in a clean environment before deployment.
What starts Astro in production?+
Use Adapter-specific for SSR. A server deployment must listen on the assigned port, stay in the foreground, and exit when startup fails.
Can I connect a custom domain?+
Yes. Deploy to the generated endpoint first, verify health, then connect the domain and wait for managed HTTPS before moving traffic.
Where should secrets be stored?+
Use the service environment and keep production secrets out of Git, build logs, browser bundles, and image layers.
How do I deploy without downtime?+
Use health checks, backward-compatible data changes, a verified new release, and a retained previous release that can be restored quickly.