Skip to Content

Why the stack is fixed

Every manh.run app uses the same stack: antd and pro-components for the UI; Hono, Drizzle and SQLite for the API. So agents write better code, screens look like a product and built-in services work with no setup. The stack has no alternatives.

What the stack includes

UI (.tsx, in the browser) antd · @ant-design/pro-components · @ant-design/x · @ant-design/charts · @ant-design/graphs plus: @xyflow/react · @dnd-kit · @monaco-editor/react · axios · dayjs Tailwind: utility classes in className only API (.ts, on the server) Hono 4 · @hono/zod-openapi · Zod · Drizzle ORM Database SQLite — one database per app Built in manh/email · manh/openai · manh/blob · .cron.ts files

There is no shadcn, MUI, styled-components or CSS files. There is no database other than the app’s SQLite.

Agents write better code on one stack

An agent writes its best code when there is one right way and that way is written down. With a fixed stack, manh.run can do three things an open stack can’t:

  • Deep docs instead of wide ones. Your agent reads the same docs for every app: which ProTable props to use, how to write a handler, how to use app/db.
  • A strict check. Each mistake agents tend to make becomes a check rule, for example the visible prop that antd v6 removed, or an import from drizzle-orm/sqlite-core. The mistake is caught before it reaches the running app.
  • One fix for every app. When manh.run finds a new kind of mistake, the new rule applies to every project at once.

Screens that look like a product

Internal apps are mostly lists, forms, detail pages and dashboards. @ant-design/pro-components ships those screens at product quality: ProTable has search, pagination and multi-row selection; ProForm has layouts, validation and multi-step forms; ProLayout has the menu and the page frame.

Your agent declares columns and how to load data instead of rebuilding a table or a form out of divs. Apps look and behave consistently with each other.

One runtime, services that work at once

Every app runs on the same manh.run runtime, so these services are ready without sign-up or configuration:

  • Email sent through manh/email.
  • AI through manh/openai, with no API key needed.
  • File storage through manh/blob.
  • Scheduled jobs as *.cron.ts files.
  • Rollback: code has checkpoints, and going back to an earlier version takes a few seconds.

The UI and the API deploy together at one address, <id>.manh.run, so there is no CORS setup and no second host.

What this means for you

If a feature can’t be built with this stack, manh.run doesn’t build it. For example:

  • You can’t use another UI kit, Vue or your own CSS files.
  • Sign-in is email/password and Google only (turned on in app/auth.ts). GitHub and other OAuth providers are not available.
  • Server code can’t use packages that need a file system, child processes or native libraries.
  • You can’t use another database as the main store; data lives in the app’s SQLite. Calling outside APIs is fine.

If your app needs any of these, manh.run is not the right fit. The fixed stack is a permanent decision, not a temporary limit.

Good to know

  • Tailwind classes in className are allowed; import "tailwindcss" and Tailwind-based UI kits are not.
  • Server code imports only packages on manh.run’s list; check blocks or warns about others.
  • Take colors and radii from antd tokens (theme.useToken() or classes like bg-surface), so dark mode and the brand color follow.

Next steps

Last updated