Choose a workflow

Use the workflow that matches the maturity and integration needs of your project.

Decision table

Choose the prototype workflow when

• you already use OpenAPI as a source or interchange format;
• you need Python and Jinja template packs;
• you need bundled TypeScript, Next.js, Dart, or debug templates;
• you depend on the current normalized inference model;
• production maturity matters more than the final runtime architecture.

Start with Prototype workflow.

Choose codepotx when

• you are developing the official stable rewrite;
• you want a TypeScript runtime that is independent of one frontend;
• you need strict artifact boundaries and dependency-direction rules;
• you want Handlebars template compilation, variable catalogs, generation plans, transactions, and runtime operations in one JavaScript package;
• you are ready to evaluate pre-release workspace packages rather than a completed public release.

Start with codepotx workflow.

Choose Codepot Lang when

• you are contributing to the final language design;
• you need compiler or LSP work rather than a production generator migration;
• you want software intent expressed in a purpose-built strongly typed language;
• you understand that interpreter and code-generation capabilities remain extension points under development.

Start with Codepot Platform.

Do not infer replacement from age

codepot-openapi and codepotg are older than codepotx, but they are not abandoned. They remain supported because they are mature and useful.

codepotx is the official long-term JavaScript rewrite, but its role does not make the prototypes invalid before migration readiness is proven.