About Sarvalekha

Useful work begins with a shared purpose.

An idea can become a design, a document, a system, or a conversation. Sarvalekha is building a family of software for the different kinds of work along that journey.

The Sarvalekha umbrella emblem, with a personal lotus above an interwoven ribbon

Distinct capabilities. Considered connections.

A family, with room
for individual character.

Design Studio explores the form an idea can take. Diagnostics examines what an application can tell us. Database and Platform are being designed for structured information, shared identity and deliberate access.

The independent Serializer framework contributes schema and structured-state foundations. Each project keeps its own purpose, boundaries and release responsibilities.

The smaller lotus is Rohit Jairaj Singh's personal emblem. The woven ribbon gives Sarvalekha its family identity: distinct passages contributing to a larger undertaking.

Meet the developer

Principles behind the work

Make the connections
worth understanding.

Shared technology can help products work together. Clear roles and current permissions are what make those relationships meaningful.

Purpose before breadth

Each product addresses a particular kind of work. A family identity should help people understand its role, without blurring different responsibilities.

Ownership stays explicit

Identity, membership, billing and resource access are distinct concerns. A shared subscription or organization role must not imply permission to read private content.

Claims follow evidence

Working development code is different from a qualified release. Design goals, possible extensions and measured results need their own descriptions.

Where the family stands

A clear view of
work in progress.

Diagnostics and Design Studio have working development capabilities and remain unreleased. Database and Platform are in design. Office and Account have design-stage directions; Finance, Support, Messaging and Payments remain on the roadmap.

Serializer is released within its documented component and language profiles. That status does not automatically qualify its consumers or every published package.