Ollama
Run a compatible local model. Performance depends on your hardware and the model you install.
Explore Ollama ↗︎Under the surfaceA local foundation.
A local foundation.
An open choice of models.
ntndOS is a desktop workspace with a local engine, company knowledge and operational state. Connect the tools and models your work needs.
How it fits togetherA company workspace.
A company workspace.
With a clear foundation.
The diagram describes the main boundaries. A cloud provider or connected service has its own data handling; local-first does not mean every action stays on the device.
Your workspace
Agents · conversations · workflows · decisions
Local engine
Orchestration · tool calls · permissions · records
company knowledge
Sources, admitted facts and skills
operational state
Runs, decisions and application state
models + tools
Local resources and configured services
Choose the model for the jobLocal when you need it.
Local when you need it.
Cloud when you choose it.
Use your own provider credentials. Model availability and capability depend on your setup and the provider.
Cloud providers
Supported adapters include OpenAI, Anthropic, Google and Hugging Face. The request sends the context included in it to your chosen provider.
Cloud spend is estimated. Price coverage is incomplete, and pre-call checks can allow a call to cross the limit. A local fallback needs an available local model. See the controls.
Connected, with specific capabilitiesKnow what
Know what
each connection does.
| Connection | Useful for | Boundary to know |
|---|---|---|
| GitHub | Reading repository and issue context | Current connector is read-only. |
| Gmail | Preparing email drafts | Draft-only. Do not expect autonomous sending. |
| Slack | Working within connected conversations | Replies and new posts have different rules. Unprompted posts require approval unless the room is explicitly armed. |
| Notion | Finding pages and databases shared with your integration | Read-only search returns titles and links. It does not import full page contents. |
| Google Drive | Finding files in your connected Drive | Read-only search returns metadata and links. No file-writing or full-content import. |
| Google Calendar | Mirroring Google events and adding new events you create | New operator-created events can be pushed. Full edit/delete synchronization and reminder delivery are not established. |
| Obsidian | Searching Markdown notes in a local vault | Reads filenames and contents, returns snippets, and does not modify the vault. |
| Local files & commands | Working with material on your machine | Actions follow their relevant access and permission checks. |
| MCP tools | Adding tools through configured servers | Capabilities and behavior depend on the server and granted authority. |
Google connections require your own OAuth client setup. These are compatibility descriptions, not partnership announcements.
Ownership in practical termsKeep track of
Keep track of
what you need to keep.
Back up deliberately.
Back up the whole data folder, including the keyring. Database files alone can restore as unreadable data. Stop the local engine before copying it unless using a supported backup procedure.
Understand your setup.
Model calls use your configured credentials. The provider account and its billing remain your responsibility.
Read each release.
The alpha is evolving. Follow the invite’s installation instructions and release notes for supported builds, migration steps and known limitations.
See platform availability ↗︎Bring your stack.
Build your company.
Start with one model, one useful role and one real task.
Request alpha access