Your private AI assistant with offline memory
About
·
Download
·
Tiles Book
·
Contributing
·
Developing
Our mission is to shape the future of software personalization with decentralized memory networks.
Tiles Privacy was born from the User & Agents community with a simple idea: software should understand you without taking anything from you. We strive to deliver the best privacy-focused engineering while also offering unmatched convenience in our consumer products. We believe identity and memory belong together, and Tiles gives you a way to own both through your personal user agent.
Tiles is built for privacy conscious users who want intelligence without renting their memory to centralized providers. Our first product is an on-device memory management system paired with an SDK that lets developers securely access user memory and create deeply personalized agent experiences.
We are seeking design partners for training workloads that align with our goal of ensuring a verifiable privacy perimeter. If you're interested, please reach out to us at [email protected]
See the download page on the Tiles website.
See the Tiles book on the Tiles Book website.
If you have any ideas, issues, etc. regarding Ghostty, or would like to contribute to Ghostty through pull requests, please check out our "Contributing to Tiles" document. Those who would like to get involved with Tiles's development as well should also read the "Developing Tiles" document for more technical details.
The high-level ambitious plan for the project, in order:
| # | Step | Status |
|---|---|---|
| 1 | Working prototype for the memory model | ✅ |
| 2 | Training a better standalone memory model | ❌ |
| 3 | Make Tiles a proxy, with local model as memory module | ❌ |
| 4 | Public key cryptography with private key on device | ❌ |
| 5 | AT Proto integration | ❌ |
| 6 | Cross-platform tilekit SDK for developers |
❌ |
| 7 | Linux support with Flatpaks | ❌ |
| N | Fancy features (to be expanded upon later) | ❌ |
Additional details for each step in the big roadmap is listed as issues in this repository.
This project is dual-licensed under MIT and Apache 2.0 terms:
- MIT license LICENSE-MIT.txt
- Apache License, Version 2.0, LICENSE-APACHE.txt
Downstream projects and end users may choose either license individually, or both together, at their discretion. The motivation for this dual-licensing is the additional software patent assurance provided by Apache 2.0.