Introduction

Welcome to the developer docs for Legit.
These docs are not just a manual — they are an open workspace where we invite developers to explore, test, and share feedback on the SDK.

Why This Documentation Exists

We are sharing our work early because we believe infrastructure like this only gets better when shaped by real developer input.
You will find:

• Early API sketches
• Concepts that may still change
• Missing sections that are coming soon

This is intentional. We want to understand what feels clear, what feels confusing, and what could be improved.

What Is Legit?

Legit makes app data behave more like code:

• Every change is versioned
• History and rollback are built in
• Collaboration is natural
• Syncing just works

At the same time, using Legit is as simple as reading and writing files. No schemas, no migrations, no hidden sync logic. Just files that carry their own history.

Feedback

If you are testing the SDK and something feels off, unclear, or incomplete, we would love to hear about it.
In particular, feedback on API design, naming, and developer experience is very valuable at this stage.

What’s Next

The core idea is already usable:

Read and write files — Legit takes care of history, sync, and collaboration automatically.

The rest of the documentation is still in progress. More guides, deep dives, and references will follow soon.