Beta
CodeForge generates SDKs from API specs. Today that means OpenAPI → TypeScript. We are being honest about where we are, and transparent about where we are going.
| Spec | Language | Status | |
|---|---|---|---|
| OpenAPI | TypeScript | Live | |
| AsyncAPI | TypeScript | Next up | Request this |
| OpenAPI | Python | Planned | Request this |
| OpenAPI | Go | Planned | Request this |
| OpenAPI | Java | Planned | Request this |
| AsyncAPI | Python | Planned | Request this |
| AsyncAPI | Go | Planned | Request this |
| AsyncAPI | Java | Planned | Request this |
| JSON Schema | TypeScript | Planned | Request this |
| JSON Schema | Python | Planned | Request this |
| EventCatalog | TypeScript | Planned | Request this |
Clicking “Request this” opens your email client with a prefilled subject. Your requests help us prioritise.
We are a two-person team. Shipping one language extremely well — with full type inference, zero runtime dependencies, and automated npm publishing — is more valuable than shipping ten languages badly.
AsyncAPI → TypeScript is next because that community is where our deepest technical credibility lives, and because event-driven API tooling is still genuinely under-served. Every other row in the matrix above is a real intention, not vaporware — but honest sequencing matters more than a long feature list.
If a specific combination is blocking you, use the “Request this” link. It sends a note directly to the founders.