Build & Runtime Configuration

Understand how Aureon compiles, builds, and executes your application workloads.

1. Automatic Framework Detection

Aureon automatically detects the framework your project uses by inspecting the repository's configuration files and package manifests:

  • Next.js: Detects next in dependencies. Automatically configures SSR, SSG, image optimization, and App Router settings.
  • React / Vite: Detects vite or react-scripts. Configures static single-page application bundling and client-side routing fallback.
  • Node.js Server: Detects server entrypoints (e.g. server.js, index.js, Express, Fastify) and sets up container runtimes.
  • Static Sites: Detects pure HTML/CSS/JS websites and provisions global edge CDN hosting.

2. Build Settings & Custom Commands

While Aureon auto-detects standard commands, you can customize them in Project Settings:

  • Build Command: The command executed to produce production assets (e.g. npm run build, vite build).
  • Output Directory: The directory containing compiled artifacts (e.g. dist, build, out, or .next).
  • Install Command: The command used to install packages (e.g. npm ci, yarn install --frozen-lockfile, pnpm install).
  • Root Directory: For monorepos, specify the subfolder containing the application (e.g. apps/web).

3. Runtime Configuration

For applications that require server execution (Node.js backend, SSR):

  1. Ensure your package.json contains a valid start script: 
    "scripts": {
  "build": "next build",
  "start": "next start"
}
  2. Aureon injects the standard PORT environment variable. Ensure your web server listens on process.env.PORT and binds to host 0.0.0.0.

4. Build Minutes Explained

Build Minutes measure the amount of CPU compilation time consumed while your deployments are building:

  • Timer starts when the build begins (dependency installation).
  • Timer stops when the build finishes and artifacts are packaged.
  • Aureon plans include generous allocations: Free (300 mins), Pro (2,000 mins), Business (6,000 mins).

5. Runtime Hours Explained

Runtime Hours represent the active computing time consumed by your application containers:

  • If you run 1 active container continuously for 24 hours, that consumes 24 runtime hours.
  • Static sites that do not require containers do not consume runtime hours.
  • Plan allocations: Free (20 runtime hours), Pro (250 runtime hours), Business (1,000 runtime hours).

6. Containers on Aureon

An Aureon container is an isolated, secure Linux micro-container provisioned to execute your backend application code. Containers automatically restart on unhandled crashes and undergo continuous platform health checks.

Explore

Pages
Buy