The runtime-portable TypeScript framework with supply-chain-aware defaults
Secure-by-default runtime. Blocked install scripts. Source-verified lockfiles. Typed end-to-end. Optional hardened GitHub Actions bundle for teams on GitHub.
Contract-first routing, Standard Schema validation, OpenAPI 3.1 with Hey API typed client codegen, streaming and OpenTelemetry tracing, edge-friendly sessions, a security-focused runtime by default, and a supply-chain-hardened release pipeline for the framework itself. One line on the App constructor, docs: true: auto-mounts a Scalar API reference at /docs and the live OpenAPI 3.1 spec at /openapi.json, the same DX as FastAPI.
ᜇᜎᜓᜌ᜔ Daloy means flow in Tagalog, pronounced da-loy. About the name
$ pnpm create daloy@latest my-apiWhy developers pick DaloyJS
The pitch is simple: keep the delightful parts of the modern web framework ecosystem, then move security and supply-chain posture from "later" to "already handled." That is the difference.
Hello, contract
One route, types, validation, OpenAPI, and the typed client all generated from it.
Why DaloyJS
The JS framework that is secure by default at the runtime layer, and ships create-daloy with pnpm install-time hardening and an optional hardened GitHub Actions bundle, so the app-safe pieces of the LLM-era supply-chain defense are on the happy path without giving up OpenAPI ergonomics, runtime portability, typed clients, or Node ops.
Competitor strengths, fewer tradeoffs
DaloyJS is not trying to win one checkbox. It is trying to remove the glue work between the best ideas developers already like.
Ready to ship, secure by default?
Scaffold a project in seconds with pnpm hardening when you choose pnpm, generated CI that blocks install scripts, pinned GitHub Actions, Dependabot, CODEOWNERS, and lockfile source verification. Then keep the contract as the app grows, the same app runs on Node, Bun, Deno, Cloudflare Workers, and Vercel Edge.