Your data, your devices,
your insights.
shenas brings together what you already track -- your sleep, your company's decisions, your boat's engine hours, your journaling, your finances. Everything stays in one picture on your own home mesh. The patterns it finds are yours alone, and nothing is sent off your device for someone else to see.
What we put first, in order
When two pull apart, the earlier one wins.
1 · Privacy
What stays on your devices, and where the protection ends
Stays on your devices
In the desktop release, both local DuckDB databases — the device-wide registry and your per-user data — are encrypted on disk with AES-256-GCM. The encryption key is applied when the database is opened, so plaintext records are never written to durable storage.
Source:plugins/core/shenas_plugins/core/db.py (ENCRYPTION_KEY), app/persistence/manager.py (key=self.get_db_key()) at commit 4489ecef3e; the source at this commit is not yet published.
In the desktop release, setup creates a recovery key that only you hold, unless you choose to skip it; shenas keeps no copy of your recovery key, your device-wide key, or your per-user key — there is no key escrow, no key-recovery service, and no server route that receives any of them.
Source:shenas-core/src/keyslot/recovery.rs (pub struct RecoverySecret {), shenas-core/src/keyslot.rs (the recovery secret in any encoding (clause 3)), app/persistence/manager.py (class RecoveryKeySetup:), server/api/shenas_ai_api/peers.py (A record carries no ``root_public_key``.) at commit c29340519a; the source at this commit is not yet published.
Where the protection ends
Source API credentials — OAuth tokens and API keys for the services you connect — are stored in your local database. That database's encryption key is their only protection; a successful attack on an unlocked device can expose them.
Source:plugins/sources/core/shenas_sources/core/base_auth.py (class SourceAuth(SingletonTable)) at commit 4489ecef3e; the source at this commit is not yet published.
Private even from yourself.
Inside shenas, every table carries a sensitivity level: Public, Internal, Sensitive or Restricted. The catalog shows only what your current level allows, and says that something is hidden without saying what. You raise the level when you choose to look, and lower it when someone is looking over your shoulder.
Your devices will share data over sovm, an open protocol in which you, not a server, hold the keys. It is not released yet.
2 · Wisdom
Built around what matters
Every feature helps you understand the parts of life that matter to you, on your terms and on your own devices.
- Plan your day
- Your calendar and tasks in one view, so the day fits the person living it.
- Keep your habits
- See which habits are holding, day by day.
- Your rituals
- Mornings and evenings, shaped the way you want them.
- How you feel
- Mood over time, kept Restricted by default and only on your devices.
An example of a pattern you could look into
On nights under six hours of sleep, the next day’s decisions were more often among the month’s hardest.
Sleep tracker and decision journal · a pattern to weigh, not a conclusion
The company that builds shenas runs on shenas. If the architecture cannot run a company, it cannot run a person.
3 · Science
Patterns you can check
- Where it came from
- Each table shows what it was made from, back to the source that recorded it.
- How complete it is
- Gaps and failed checks are shown in words, not hidden behind a chart.
- Ordinary tables underneath
- You can query the data yourself, so any pattern can be rechecked.
4 · Fun
Yours to shape
Swap surfaces, add new ones, change the theme. The interface adapts to what you care about, not the other way around.
Connects tofitness tracker · calendar · email · notes · finance · music · language app · data exports · add your own
The community version is open source.
The shenas you run today -- local pipeline, source plugins, transforms, surfaces -- is free and open source. The code is public so anyone can read it, extend it with new sources, and verify what their machine is running.
Developers and the technically curious can find the architecture, the engineering principles, and the plugin documentation atshenas.ai/oss. Source: shenas-org/shenas Public mirror (shenas-org/shenas): Last updated 2026-05-23. Treat it as frozen; do not rely on it for current releases.
The community version stays free. The local pipeline, the on-device models and the privacy primitives stay in the community version.
shenas is open-core. What is sold is the operation of a service: either it needs a party who is not you, or it is a convenience over something the community version already does for free.
Nothing on this list is for sale yet.
Account services
- Identity / namespaceNot yet for sale
Needs someone other than you: the namespace and identity operator; a name has to be issued and kept unique by whoever runs the namespace
If you leave: the community version runs with no account; keys and data are untouched; the name lapses
- RelayNot yet for sale
Needs someone other than you: two devices behind NATs cannot both be the relay between them
If you leave: direct paths keep working; anyone can run the same upstream relay
- MailboxNot yet for sale
Needs someone other than you: someone holds ciphertext for a peer that is offline
If you leave: live and relayed delivery continue; only store-and-forward for offline peers stops
- Push relayNot yet for sale
Needs someone other than you: the holder of the app's push credential at the platforms; a push sender is the app's publisher, not its user
If you leave: the app fetches when opened
- RecoveryNot yet for sale
Needs someone other than you: a witness holding a recovery shard; a user who has lost every device cannot be their own witness
If you leave: the user's own copy of their key material, kept where they choose
- InheritanceNot yet for sale
Needs someone other than you: custody that outlives the user; someone holds the instruction and acts when the user no longer can
If you leave: the user hands the key to a person themselves
- Signed plugin channelNot yet for sale
Needs someone other than you: a vouch is someone else's statement; the company reviews and signs as one signer among those the user trusts
If you leave: the trust store and every plugin stay; only the company's signature stops being renewed
Hosted compute and storage
- LLM proxy → mixnetNot yet for sale
Needs someone other than you: the account holder at the model provider is the company, so the provider sees the company's account, not the user's, though prompt content can still identify the person; later, the anonymity set of the other users
If you leave: the community version calls a provider with the user's own key, or a local model
- BackupNot yet for sale
Needs someone other than you: storage the user's own devices do not provide, holding ciphertext the operator cannot read
If you leave: export to a place the user holds and replication across their own devices; the company's copy is never the only copy
- Cloud workersNot yet for sale
Already free: the same worker runs on the user's own always-on machine
If you leave: the user runs the worker themselves; a hosted worker holds only a cache and its configuration