Welcome to Laika

Laika is a unified abstraction for accessing files, API's and other content. It takes care of all the complexities like pagination, batching, concurrency, streaming and discovery. Along with that Laika provides easy to use integrations for common web frameworks and a ton of premade opinionated adapters.

Why Laika

Laika is the transport, you provide the domain

The reason to use Laika is that you don't want to model your domain around your CMS or storage implementation. The goal of Laika is to get you 90% there. Laika attempts to not hide any details from you, or to be opinionated about how you model your data and data retrieval. You can read more about the architecture of Laika here.

Built for AI

Laika is also extremely useful as a homogeneous data access layer in the age of LLMs. Laika provides a built-in MCP server which it feeds with the OpenAPI spec of the JSON:API. Unlike EmDash CMS, it only has one 'request' tool.

What Laika offers

Out of the box
40+ official adapters	Real-time updates
Pagination and filtering	Batch operations
Streaming listings	Change feeds and sync tokens
Capability discovery	Any file format
Drafts and publishing	Revision history
Linked assets and image variants	Conflict detection and locks
OAuth2, passkeys and 2FA	Upload sanitization
Astro, Vite and Decap integrations	Starters and CLI bootstrapping

Laika's core sits on top of Effect.ts. It provides the primitives that Laika uses, along with some custom primitives like LaikaTask and LaikaStream.

Architecture Overview

Layer	Packages
API	storage-api, documents-api, assets-api, catalog-api
Domain	storage, documents, assets, catalog
Implementation	storage-r2, storage-fs, documents-drizzle, assets-r2
Shared	core, auth, crypto, sanitizer, i18n, json-api

Each layer depends only on the layers below it.

Getting Help

• GitHub Issues — For bugs and feature requests
• GitHub Discussions — For questions and discussions
• Contributing — See CONTRIBUTING.md

License

Laika is MIT licensed.