What is Interlace

Interlace is a family of small, focused, TypeScript-native developer tools. Each one solves a single problem really well, and together they share a baseline that makes them feel like the same product:

• Same docs experience — every product site uses the same Fumadocs theme, navigation, components, and brand tokens. Synced from a central baseline so they cannot drift.
• Same evidence contract — every comparative claim ("faster than X", "fewer deps than Y") is backed by a versioned benchmark file. No marketing assertion ships without a result behind it.
• Same primitives — TypeScript-first config, zero ghost runtime dependencies, full IntelliSense everywhere.

What "interlace" means here

The name describes how the products relate. They are not a monolith and they are not unrelated — they interlock. The same brand, the same docs experience, the same evidence contract. A pattern proven in one product (e.g. cleanup-on-removal in @interlace/serverless-api-gateway-caching) becomes the template for the next one.

What it is

Interlace is a community and an ecosystem, built in the open. Independent, MIT-licensed, and accountable to its users — not to investors. The work is funded by the people doing it, the direction is set by the people using it, and every claim is backed by evidence anyone can rerun.

It might grow into a company someday — that's not ruled out. But that decision will follow the work, not lead it. For now, "Interlace" is the shared standards (docs baseline, evidence contract, brand) that the products under it agree to follow.

What it isn't (today)

• A framework. You don't pick "Interlace" — you pick a specific plugin that solves a specific problem.
• A bundle. You install @interlace/eslint-plugin-jwt or @interlace/serverless-api-gateway-caching directly. There is no umbrella package.