1 
Create an account.
Your profile and data live in 'rooms' you can provision access to.
Menu
Own Your Own Data
A homestead for your data.
Your data is not their moat.
The flock follows the platform. Ewe don't have to.
EweserDB is a personal data layer rooted on your device. Apps and AI agents connect to it with your permission. They do not store your data, they read and write through scoped access you can revoke. Local-first, synced across your devices, and self-hostable any time.
Apps and AI agents orbit the user's data layer. They do not own it.
Illustrated pastoral valley with a sheep, solar homestead, wind turbines, and dotted permission paths.
# 00 // A note from the maker
Why I built EweserDB.
I lost my notes one too many times. Evernote ate years of work. Quizlet wouldn't let my flashcards out. Anki I trusted, but it was a chore to onboard anyone else to it. I wanted to build small, focused apps that synced reliably and worked offline — and every time, the foundation got in the way. So I built the foundation.
EweserDB is what I wish I had when I started making educational and map-based apps: a database the user actually owns, that works offline, syncs across devices, and lets independent apps build on the same data without asking each other's permission.
Read the rest
The flip
Today, you ask the app to see your data. "Facebook, can I see my friends list?" In EweserDB, the app asks you. That sounds small. It isn't. It means you can leave at any time and take everything with you. It means a new app can start with your data already loaded — no onboarding, no import, no "we don't support that format." It means apps have to compete on experience instead of captivity.
Beyond notes
I started with knowledge apps because that's the pain I felt. But the pattern goes further. Personal finance trackers you'd actually feel safe using. Lifestyle and health apps that don't profile you. Social tools where the network effect belongs to people, not platforms. Most of these apps aren't computationally complicated. Their giant infrastructure exists to hoard data and serve ads, not to do the thing the user came for.
Small apps, real lives
Because there's no backend to build, a developer can ship a useful tool in an afternoon. A focused flashcard app without ten years of feature creep. A reading tracker for a friend. A quiz tool for a class. Try it for ten minutes, decide if you like it, swap to another one tomorrow — your data stays with you the whole time.
The bigger picture
Walled gardens stifle innovation, harvest behavior, and concentrate power in a handful of companies. I don't think that arrangement is permanent. I think the substrate can be flipped — quietly, app by app — until owning your own data feels as obvious as owning your own files.
Standing on other people's shoulders
EweserDB is a direct answer to Martin Kleppmann's Local-First Software essay — the question "how do you own your own data in spite of the cloud?" has been rattling around my head ever since I read it. Federated networks like Mastodon and Matrix showed that you can break the platform monopoly without losing the network. And Yjs and CRDTs already solved half the hard part: making local edits sync without a central referee. EweserDB adds the layer on top — shared schemas, room-scoped permissions, and an app ecosystem so users can actually move between tools that read and write the same data.
That's the bet. Thanks for being here.
— Jacob
00 // How it works
Three steps to owning your data.
2 
Connect your tools.
Sign in to Ewe Note, connect an AI client, or install an app. Each one asks for scoped access, not the whole database.
3 
Your data stays yours.
Switch apps. Revoke access. Take your data anywhere. The database belongs to you, not the platform.
01 // The Problem
Apps became landlords.
Modern software treats your notes, documents, decisions, relationships, and learning work like platform property. You spend years building context, then a bug, shutdown, bad export, or bloated product roadmap can put that work out of reach.
The old enclosure
- The app owns the database.
- Your context stays trapped in one product.
- Collaboration requires everyone to use the same platform.
- AI agents only help if you copy your life into them.
- Trying something new means starting from zero.
- Export is an escape hatch, not a workflow.
Own the substrate. Swap the interface.
The open field
- You own the database.
- Apps compete on experience, not captivity.
- Collaboration can happen over shared user-owned data.
- AI agents get scoped, reviewable access.
- New apps can begin with the user's existing data.
- The cloud can sync without becoming the owner.
# 2 / The Reversal
Switch apps. Keep your work.
EweserDB separates the data layer from the app layer. Your notes, bookmarks, tasks, projects, and media live in your own data layer. Apps come, use what you allow, and leave. You stay in charge of your data, from anywhere, in the app you want.
the old problem
App-owned data
- When apps own your data, you lose.
- Switching apps means rework, manual exporting, and format guessing.
- Every vendor lock-in delays better tools.
- Friction adds up and leaves you less productive at scale.
DocumentsBookmarksTasks
the reversal
User-owned data
- Your data stays yours.
- Move to any app, anytime, and switch without data loss.
- Choose tools that respect your data.
- Invest in features, not vendors.
- Upgrade apps with seamless sync everywhere.
# 3 / Ecosystem
One sheep. All your data. With you anywhere.
Notes are one proof point. The bigger story is yours: owned tools, shared layers, collaboration, study tools, and personal knowledge workflows that all work from the same data.
AI + MCP
Connect the AI clients you choose to the same user-owned data layer. Ask questions, automate tasks, and verify changes under scoped access.
Notice: We never collect your content. Your data is yours.
Collaborative notes
Co-write notes, share links, and grant view or edit access without moving the work into another silo.
Private spaces and public work, with room-scoped permissions.
Knowledge base
Index notes, references, and documents by theme, then let compatible tools read the same context.
Organize by projects, conversations, and study workflows.
Study tools
Turn notes, docs, bookmarks, quizzes, flashcards, and summaries into review workflows.
Spaced repetition, feedback, and concept maps can share one source.
Micro apps
Tiny focused apps for tasks, prompts, quick-share tools, and personal workflows.
Minimal apps, maximum utility, with sync and backup when needed.
Personal sharing
Publish rooms with versions, fine-grained permissions, and time-limited links.
All yours, visible only where you choose to share.# 4 / Apps
Apps that work with your data, not against it.
Every app built for EweserDB talks to the same data-rich living layer. You grant it, you revoke it, and you keep your work without lock-in.
Ewe Note
A writing and knowledge app that stores your notes on your device. Works offline. Syncs across devices when you are connected. Your first app built on EweserDB.
Open Ewe Note
More apps coming
Flashcards, publishing tools, AI memory review, personal knowledge bases, and more, all built on the same data layer.
Explore the ecosystem
Build your own
EweserDB is open. Build a focused app that works with the user's existing data instead of starting another silo.
Read the developer docs04 / AI
Give your AI a memory it can't take with it.
Codex, Claude, ChatGPT, GitHub Copilot, OpenClaw, and the apps you choose need context while they work with you. EweserDB keeps memory and access policy together, so each client reads from scoped rooms you can inspect and revoke.
Connect my AI Modern API access. Ready for dev and AI tools.- Codex · CLI token-backed MCP config
- Claude · Desktop local stdio MCP
- Claude · Web OAuth remote MCP
- ChatGPT · Web OAuth remote MCP
- GitHub Copilot · IDE token-backed setup
- OpenClaw · Agent streamable-http MCP
MCP endpoint Permissioned access to rooms and schemas.
Memory rooms Scoped context across devices and sessions.
Audit trail Room, grant, and log IDs stay reviewable.
05 // Developers
Build the app. Not the enclosure.
EweserDB gives developers a lock-in-free local-first database. Indexed schemas, revocable grants, and MCP-ready access patterns let you build useful apps without herding users into another proprietary backend.
npm install @eweser/dbThen use the EweserDB SDK, MCP server, and portal access from the dev menu below.
Typed schemaBuilt-in grant APIsShard anywhereSelf-hostable PostgresOpen MCP accessLocal AI off-rampExisting user dataMicro-app friendly
Open for schema Full control.
Built on room grants User access by design.
Sovereign storage Balance cost, performance, locale, and compliance.
Cost controls Self-host, private cloud, or managed EweserDB.
Scoped PII access Room-scoped permissions instead of platform-wide access.
On your server, or theirs, yours. Dev picks environment: self-host, private cloud, or EweserDB.
Bring it home
Bring it home.
Connect your AI tools. Try Ewe Note. Keep the database under your control.