Deployment and local development

Using the hosted service

Most integrations need only a Console account and an API key. Follow the quick start; you do not need to deploy the platform to embed search.

Running the source repository

For operators with source access, this repository is a pnpm monorepo. The API runs on Cloudflare Workers with D1, storage, queues and other bindings. Marketing, Console and docs are separate Next.js applications. A search engine alone is not the whole platform.

Use the Node version required by the repository and its pinned pnpm version. From the repository root:

pnpm install --frozen-lockfile
pnpm --filter @aacsearch/api db:migrate:local
pnpm --filter @aacsearch/api dev

Before starting the API, copy its example local environment configuration to .dev.vars and configure the engine and required bindings. Keep secrets out of Git. Start the UI applications in separate terminals:

pnpm --filter @aacsearch/console dev
pnpm --filter @aacsearch/marketing dev
pnpm --filter @aacsearch/docs dev

Point each application at the intended API/Console/docs URLs. If ports conflict, pass distinct ports to the Next.js applications. Use test credentials for payment development.

Production is a separate operation

Provision the resources named by the deployment configuration, apply migrations in a reviewed rollout and configure production secrets. Check authentication, collection isolation, queued jobs, callbacks and restore procedures before routing traffic. Never run test-plan grants or development payment behavior in production. Contact the team to agree deployment and support terms; source access is not a promise of a supported self-hosted distribution.