Grep less.Understand more.
One logger for Bun and Node.js TypeScript apps. Plain logs, structured events, browser and Expo ingestion, AI traces, and connectors, with a local Studio to read all of it.
For Next.js, Hono, Express, Elysia, Nuxt, Workers, Expo, and more.
A preview of Studio with sample data. Run bunx @blyp/cli studio to open yours at localhost:3003.
17
framework & runtime adapters
6
observability connectors
15
bundled agent skills
1
package to install
What ships in the box
The boring parts of logging, done properly.
Errors, AI calls, files, databases, and the browser all land in the same stream, with the same shape.
AI tracing
See every model call inside the request.
Wrap a Vercel AI SDK, OpenAI, Anthropic, or Better Agent client and get ai_trace records with usage, finish reason, and timing.
Hover the timeline to scrub. Hover a span to find its fields.
{
- type: "ai_trace",
}
Sample trace. Prompts and outputs stay out unless you opt in.
Errors
Errors with a status code.
createError builds a BlypError you can log, return, and parse back on the client.
throw createError({ status: 402, message: "Payment failed" })
Payment failed
// on the client
throw await parseError(response)
402same status, same message
File logging
NDJSON that rotates itself.
Active streams plus gzip archives, five kept per stream by default.
logs/
archive/
Databases
Logs as rows.
Prisma, Drizzle, or MongoDB adapters. For SQL, the CLI scaffolds the schema and migration.
Prisma
Drizzle
MongoDB- In progress:
blyp db:init - Pending:
blyp db:migrate - Pending:
blyp db:generate
Browser & Expo
Client logs, routed through your server.
Browser and Expo loggers post to Blyp ingestion first. Your server decides what gets forwarded.
Agent skills
Your agent reads the docs first.
Fifteen bundled skills install into .agents/skills so coding agents follow the documented setup. Click a logo to copy its install command.
MCP
These docs speak MCP.
Point Cursor, Claude Code, Codex, or any MCP client at the docs server and let it list, search, and read Blyp pages.
Claude Codeclaude mcp add
Codexcodex mcp add
blyp-docsblyp.dev/mcp- list_docs
- search_docs
- read_page
cursor → list_docs()
← navigation graph · every page
Questions
Before you swap your logger.
Something else on your mind? The docs are searchable, and so is the MCP server.
Does Blyp run on Node.js or only Bun?
Both. Blyp is Bun-first and Node-compatible. Framework adapters cover Next.js, Hono, Express, Fastify, NestJS, Elysia, SvelteKit, Nuxt, Astro, and more, plus Workers, Convex, the browser, and Expo.
Where does Studio send my logs?
Nowhere. Studio is a local UI started by the CLI with bunx @blyp/cli studio. It runs at localhost:3003 against the project on your machine.
Can I migrate from pino or winston?
Yes. The migration guides map pino and winston setups to Blyp loggers, levels, and transports step by step.
Do I need a database?
No. The default destination is NDJSON files with rotation. Prisma, Drizzle, and MongoDB adapters are there when you want logs as rows.
What are agent skills?
Portable instruction folders that teach coding agents the documented Blyp setup for a framework or connector. Install them with bunx @blyp/cli skills install; they land in .agents/skills.
One logger, every runtime
Less grepping. More prompting.
Install the package, open Studio, and give your agent the skill. You will be reading structured logs before your coffee cools.