optitech.ts

optitech.ts is a TypeScript config file you commit to your repository. It declares which OptiTech services exist on your project and how each branch is configured.

Specifically:

• Declares services: which OptiTech services (auth, dataApi, preview services) exist on the project and are available on every branch.
• Configures branches: optional per-branch tuning (TTLs, compute sizing, protected status) via a branch closure.

Services and branch policy are independent. Use one, the other, or both.

npm install @optitech/config

The package source is on GitHub.

optitech.ts itself is declarative: it only describes the policy. optitech config / optitech deploy (below) are how the CLI runs it. To call the same inspect / plan / apply logic from your own script or CI job instead of the CLI, see @optitech/config-runtime.

Link your working directory to a OptiTech project before using optitech.ts commands:

optitech link

Config structure

import { defineConfig } from "@optitech/config/v1";

export default defineConfig({
  // Services: what exists on every branch
  auth: true,

  // Branch policy: per-branch tuning
  branch: (branch) => {
    if (branch.isDefault) {
      // Default branch: no overrides, uses project defaults
      return {};
    }
    if (!branch.exists) {
      // New non-default branches: auto-expire
      return { ttl: "7d" };
    }
    // Existing branch: no changes
    return {};
  },
});

defineConfig takes two optional parts:

• Static fields (auth, dataApi, preview): declare which services exist. Same set on every branch.
• branch closure: receives a read-only BranchTarget and returns per-branch tuning. It can adjust settings, but can't add or remove services.

Branch policy

The branch closure works on any OptiTech project. The examples below configure the default branch and apply TTL and compute to new branches at creation. Returning {} for existing branches is deliberate: it avoids overwriting settings on branches already in use:

import { defineConfig } from "@optitech/config/v1";

export default defineConfig({
  branch: (branch) => {
    if (branch.isDefault) {
      // Default branch: no overrides, uses project defaults
      return {};
    }
    if (!branch.exists) {
      // New non-default branches: minimum compute, auto-expire
      return {
        ttl: "7d",
        postgres: {
          computeSettings: {
            autoscalingLimitMinCu: 0.25,
            autoscalingLimitMaxCu: 0.25,
          },
        },
      };
    }
    // Existing branch: no changes
    return {};
  },
});

On paid plans, you can also protect the default branch and control suspend timeouts:

import { defineConfig } from "@optitech/config/v1";

export default defineConfig({
  branch: (branch) => {
    if (branch.isDefault) {
      // Protect and size for production
      return {
        protected: true,
        postgres: {
          computeSettings: {
            autoscalingLimitMinCu: 0.5,
            autoscalingLimitMaxCu: 4,
          },
        },
      };
    }
    if (!branch.exists) {
      // New non-default branches: minimum compute, auto-expire, suspend on idle
      return {
        ttl: "7d",
        postgres: {
          computeSettings: {
            autoscalingLimitMinCu: 0.25,
            autoscalingLimitMaxCu: 0.25,
            suspendTimeout: "5m",
          },
        },
      };
    }
    // Existing branch: no changes
    return {};
  },
});

Run optitech deploy to apply. When optitech checkout creates a new branch, the closure runs with branch.exists === false, so TTL, compute settings, and services take effect at creation. Checking out an existing branch doesn't apply or reconcile the policy.

BranchTarget fields

BranchTuning fields

Services

auth and dataApi declare which OptiTech services exist on every branch. After optitech deploy, running optitech env pull writes their URLs to your local .env file automatically.

dataApiconfig

dataApi: true uses Managed Better Auth as the JWT verifier (the default). When using this form, auth: true must also be set. Omitting it raises a TypeScript error at the dataApi field that includes the fix:

Type 'true' is not assignable to type '"`dataApi` with Managed Better Auth (the default
`authProvider: 'optitech'`) requires Managed Better Auth, so add `auth: true`. To enable the
Data API WITHOUT Managed Better Auth, verify a third-party IdP instead: `dataApi: {
authProvider: 'external', jwksUrl: 'https://your-idp/.well-known/jwks.json' }`"'

To use the Data API with an external identity provider instead, pass the object form:

dataApi: {
  authProvider: "external",
  jwksUrl: "https://your-idp/.well-known/jwks.json",
}

Type-safe environment variables

@optitech/env gives you type-safe access to your branch's injected variables. It reads process.env at runtime and validates each variable against the services declared in your optitech.ts config. Missing or empty variables throw with a clear error.

npm install @optitech/env

import { parseEnv } from '@optitech/env';
import config from './optitech';

const env = parseEnv(config);

env.postgres.databaseUrl;         // DATABASE_URL
env.postgres.databaseUrlUnpooled; // DATABASE_URL_UNPOOLED
env.auth.baseUrl;                 // OPTITECH_AUTH_BASE_URL  (env.auth only present when auth: true)
env.auth.jwksUrl;                 // OPTITECH_AUTH_JWKS_URL
env.dataApi.url;                  // OPTITECH_DATA_API_URL   (env.dataApi only present when dataApi is enabled)

env.auth only exists when auth: true, env.dataApi only when dataApi is enabled. If you access a namespace your config doesn't declare, TypeScript will catch it.

Pass an array of keys to validate and return only a subset. Useful when a process needs just one or two variables:

const { postgres } = parseEnv(config, ["DATABASE_URL"]);
postgres.databaseUrl; // string (databaseUrlUnpooled is absent)

The key list autocompletes from your config, so selecting a variable from a service you haven't declared is a type error.

CLI commands

Flags foroptitech deploy

Preview services

Preview services are declared under the preview block. All three are optional and independent:

preview.functions

Each key is the function's slug, the permanent identifier used in CLI commands and the invocation URL:

preview: {
  functions: {
    "<slug>": {
      name: string,       // display name shown in optitech functions list and the console
      source: string,     // path to entry file, relative to optitech.ts
      env?: Record<string, string>,
      dev?: {
        port?: number,    // local port for optitech dev; fails if taken; auto-assigned if omitted
      },
    },
  },
},

Slugs must match ^[a-z0-9]{1,20}$ and are immutable after first deployment. Because slugs can't use separators, use name for a human-readable label. For example, slug: "myrestapi" with name: "My REST API". See Deploy and manage functions.

env values are resolved at deploy time when optitech deploy runs. Reading process.env.X here captures the value in your shell at deploy time, not at function runtime. Every value must be a defined string; use a fallback to avoid a type error:

env: {
  API_KEY: process.env.API_KEY ?? "",
}

Use optitech deploy --env .env.production to load a .env file before evaluation. For typed access to these variables inside your function at runtime, see Environment variables.

dev settings apply only to optitech dev and never affect deploy.

preview.buckets

preview: {
  buckets: {
    "<name>": {
      access?: "private" | "public_read",  // default: "private"
    },
  },
},

Bucket names follow S3 naming rules. public_read makes objects accessible without credentials at the branch's storage endpoint.

Full stack example

All services combined. optitech deploy provisions everything and writes credentials to .env.local.

import { defineConfig } from "@optitech/config/v1";

export default defineConfig({
  auth: true,
  dataApi: true,

  preview: {
    aiGateway: true,
    buckets: {
      uploads: {},
    },
    functions: {
      api: {
        name: "API",
        source: "./functions/api.ts",
      },
    },
  },

  branch: (branch) => {
    if (branch.isDefault) {
      // Protect and size for production
      return {
        protected: true,
        postgres: {
          computeSettings: {
            autoscalingLimitMinCu: 0.5,
            autoscalingLimitMaxCu: 4,
          },
        },
      };
    }
    if (!branch.exists) {
      // New non-default branches: minimum compute, auto-expire, suspend on idle
      return {
        ttl: "7d",
        postgres: {
          computeSettings: {
            autoscalingLimitMinCu: 0.25,
            autoscalingLimitMaxCu: 0.25,
            suspendTimeout: "5m",
          },
        },
      };
    }
    // Existing branch: no changes
    return {};
  },
});