Amoxi builds pages, APIs, dependency injection and AI agents with the TypeScript compiler, the way Micronaut does for Java. Agents run as durable background work, stream every token and show your own components. Nothing is scanned at start-up, so a server with 1,000 services is ready in about 11 milliseconds.
npx create-amoxi-app@latest my-appcd my-appnpm run devMedian of 7 runs of npm run bench on Node 22, measured from the start of the framework to the server accepting requests. Node.js loading your compiled code comes on top and grows with the size of the app. Run the benchmark on your own hardware to compare.
Each advantage below is used by at least one of the sector examples, so you can read the code behind it before adopting anything.
What teams usually assemble from five libraries and a job queue is part of the framework.
The speed comes from doing the work at build time, not from tuning.
Problems that other frameworks find at runtime, Amoxi finds while it builds.
What operations teams usually add by hand is already there.
Familiar tools, and room for the code you already have.
Four complete example apps live in the repository, each with tests and a README that maps every framework feature to the business need it serves. Company names and data are fictional.
Finance and banking
A banking assistant that answers from the customer's real accounts and moves money only with their approval.
Healthcare
A patient assistant that books appointments, answers policy questions and screens urgency safely, without ever diagnosing.
Retail and e-commerce
A shopping assistant that sells through product cards and comparisons, remembers sizes, and is open to shopping agents.
Logistics and operations
A dispatch agent that plans routes for minutes in the background and reacts to vehicle events on its own.
Decorators are markers. The compiler turns them into plain TypeScript that you can read, debug and step through.
Tools are ordinary methods with typed inputs; agents list the tools, components and knowledge they may use.
@Singleton()
export class BankingTools {
/** Transfer money between two of the customer's own accounts.
Runs only after the customer approves it. */
@Tool({ approval: true, idempotent: true, expose: false })
async transferBetweenAccounts(input: {
/** Account to take the money from, e.g. CHQ-4417 */
fromAccountId: string;
toAccountId: string;
/** Amount in cents @integer @minimum 1 */
amountCents: number;
}, ctx: ToolContext): Promise<TransferSummary> {
const receipt = await ctx.step('post-transfer', () =>
this.money.transfer({ customerId: customerOf(ctx), ...input }));
ctx.ui('TransferReceipt', { ...receipt });
return summary(receipt);
}
}
@Agent({ tools: [BankingTools], ui: ['SpendingChart', 'TransferReceipt'],
knowledge: ['fees'], memory: true })
export class BankingAssistant { instructions(ctx: AgentRunContext) { ... } }The TypeScript compiler checks the whole graph, from services to agents, and generates the wiring, the tool schemas the model sees and the validators its arguments must pass. Mistakes stop the build, not production.
> amoxi build
Amoxi found 1 problem(s):
error AMOXI: src/agent/banking-assistant.ts:18
@Agent 'BankingAssistant': ui component
'BalanceSparkline' is not an island in src/islands/At start-up there's nothing left to discover: the server listens in milliseconds, and agents run as durable background work that streams to the browser.
tools.push({
name: "transfer_between_accounts",
inputSchema: {"type":"object","properties":{
"fromAccountId":{"type":"string",
"description":"Account to take the money from, e.g. CHQ-4417"},
"amountCents":{"type":"integer","minimum":1}, ...},
"required":["fromAccountId","toAccountId","amountCents"]},
validate: (x) => $validate(x ?? {}, _V18),
invoke: (b: C6, i, t) => b.transferBetweenAccounts(i, t),
approval: true,
idempotent: true,
expose: false,
});Amoxi follows Next.js conventions where it can, so the commands and project structure feel familiar. These are the differences that matter when you choose.
| Need | Next.js | Amoxi |
|---|---|---|
| Server-rendered pages | React Server Components | JSX pages rendered to HTML on the server |
| Interactive parts | Client components, hydrated | Islands, with signals or React, loaded only where used |
| API endpoints | Route handlers | Controllers with typed routes |
| Dependency injection | Not included | Built in, resolved and checked at build time |
| Request validation | A library such as Zod | Generated from your TypeScript types |
| Page caching | ISR and revalidatePath | @Cached and revalidatePath |
| Sessions | cookies() plus an auth library | Encrypted cookie sessions built in |
| WebSockets | Needs a custom server | Built in |
| OpenAPI document | A separate library | Generated from your types |
| Static export | output: 'export' | amoxi export |
| AI agents | Vercel AI SDK; long tasks hit function time limits on serverless hosts | Built in: durable background runs that survive restarts |
| Agent UI | AI SDK generative UI (React) | Your islands, with props validated against their types |
| Tool schemas | Zod | Generated from your TypeScript types |
| MCP and A2A servers | Separate libraries | Built in, off by default |
| Pages for AI agents | Add yourself | Markdown and JSON for every page, /llms.txt |
| Image optimisation | next/image | Not included; serve pre-sized images |
| Track record | Large ecosystem, widely deployed | New: fully tested |
You need Node.js 22 or newer. No environment variables or accounts are required: the app runs at http://localhost:8080.
npx create-amoxi-app@latest my-appcd my-appnpm run devAmoxi is free to use in commercial products under the Apache License 2.0, which includes a patent grant. The documentation covers every feature, from the first page to deploying in production.