The mastra build
command bundles your Mastra project into a production-ready Hono server. Hono is a lightweight web framework that provides type-safe routing and middleware support, making it ideal for deploying Mastra agents as HTTP endpoints.
Usage
mastra build [options]
Options
--dir <path>
: Directory containing your Mastra project (default: current directory)
Advanced usage
Limit parallelism
For CI or when running in resource constrained environments you can cap
how many expensive tasks run at once by setting MASTRA_CONCURRENCY
.
MASTRA_CONCURRENCY=2 mastra build
Unset it to allow the CLI to base concurrency on the host capabilities.
Disable telemetry
To opt out of anonymous build analytics set:
MASTRA_TELEMETRY_DISABLED=1 mastra build
Custom provider endpoints
Build time respects the same OPENAI_BASE_URL
and ANTHROPIC_BASE_URL
variables that mastra dev
does. They are forwarded by the AI SDK to
any workflows or tools that call the providers.
What It Does
- Locates your Mastra entry file (either
src/mastra/index.ts
orsrc/mastra/index.js
) - Creates a
.mastra
output directory - Bundles your code using Rollup with:
- Tree shaking for optimal bundle size
- Node.js environment targeting
- Source map generation for debugging
Example
# Build from current directory
mastra build
# Build from specific directory
mastra build --dir ./my-mastra-project
Output
The command generates a production bundle in the .mastra
directory, which includes:
- A Hono-based HTTP server with your Mastra agents exposed as endpoints
- Bundled JavaScript files optimized for production
- Source maps for debugging
- Required dependencies
This output is suitable for:
- Deploying to cloud servers (EC2, Digital Ocean)
- Running in containerized environments
- Using with container orchestration systems
Deployers
When a Deployer is used, the build output is automatically prepared for the target platform e.g