@confect/alchemy
Alchemy resources for Convex cloud projects, deployments, deploy keys, environment variables, and code deployments. Confect.Backend runs Confect codegen before deploying an existing application.
import { Confect, Convex } from "@confect/alchemy";
Use Convex.providers() in your Alchemy stack. The integration targets Alchemy 2.0.0-beta.82 and Effect v4; it does not add Alchemy dependencies to Confect's runtime packages. Plain Convex applications can use Convex.Code without the Confect CLI.
See the deployment guide for complete examples, credentials, ownership, and deletion policies.
Projects and deployments are retained by default. Treat your Alchemy state as a secret store: it contains deployment credentials and managed environment values. Code deployment runs on every apply and never deletes data when removed from a stack. Pushes to one deployment from processes that share a user cache directory never overlap.
Under alchemy dev, the same resources run against a local Convex backend that the integration downloads, starts, and stops with the dev session. Its data and credentials live in .alchemy/convex/<stack>/<stage>/<deployment>.
Tests
Unit suites are per-module under test/. Cross-module lifecycle tests live under test/integration/ and exercise Alchemy's engine with controlled API/process boundaries; they do not provision cloud resources. test/integration/RealLocalBackend.test.ts runs the pinned local backend: it downloads the release once into a cache under the OS temp directory, binds ports 3300-3399, and is skipped on Windows.
pnpm exec vitest run --project @confect/alchemy