A local-first private AI assistant for everyday use. Runs on-device models with encrypted P2P sync, and supports sharing chats publicly on ATProto.
Update README
Updated descriptions to emphasize local-first privacy and clarified the mission and purpose of Tiles.
authored by
Ankesh Bharti
and committed by
GitHub
4dd3dea6
1cd87f9b
+8
-12
+8
-12
README.md
+8
-12
README.md
···
3
3
<p align="center">
4
4
<a href="https://github.com/tilesprivacy/">
5
5
<picture>
6
-
<source media="(prefers-color-scheme: dark)" srcset="https://avatars.githubusercontent.com/u/210493283" />
7
-
<source media="(prefers-color-scheme: light)" srcset="https://github.com/user-attachments/assets/984f9fa7-d097-4d36-bd98-da1a71cf778d" />
6
+
<source media="(prefers-color-scheme: dark)" srcset="https://tiles.run/realdark.png" />
7
+
<source media="(prefers-color-scheme: light)" srcset="https://tiles.run/reallight.png" />
8
8
<img src="https://github.com/user-attachments/assets/1c7848de-33af-47ed-9fb2-a361c096a44d" alt="Tiles Logo" width="128" />
9
9
</picture>
10
10
</a>
···
13
13
<h1 align="center">Tiles</h1>
14
14
15
15
<p align="center">
16
-
Your private and secure AI assistant for everyday use<br />
16
+
Local-first private AI for everyday use.<br />
17
17
<a href="#getting-started">Getting Started</a> ·
18
18
<a href="https://tiles.run/book">Documentation</a> ·
19
19
<a href="#about">About</a> ·
···
29
29
30
30
## Tiles CLI
31
31
32
-
Tiles is the private and secure AI assistant for everyday use. It will feel familiar if you have used tools like Ollama or LM Studio.
32
+
Tiles is the local-first private AI for everyday use.
33
33
34
34
Install the signed macOS package:
35
35
···
43
43
44
44
## Tilekit SDK
45
45
46
-
Tilekit is a Rust-based SDK for customizing local models and agent experiences within Tiles.
46
+
Tilekit is the SDK for developers to build on the infrastructure behind Tiles. It aims to be the app-server interface behind Tiles and future rich client experiences. Developers can embed it into their local clients by bundling or fetching a platform-specific App Server binary, running as a long-lived child process and communicating over bidirectional stdio JSON-RPC.
47
47
48
48
## Documentation
49
49
···
52
52
53
53
## About
54
54
55
-
Our mission is to bring privacy technology to everyone.
56
-
57
-
Tiles Privacy was born from the [User & Agents](https://userandagents.com) community with a simple idea: software should understand you without taking anything from you.
58
-
59
-
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.
55
+
Tiles is built by a small team working on private, local-first software, with a clear mission: to bring privacy technology to everyone.
60
56
61
-
Tiles is built for privacy conscious users who want intelligence without renting their memory to centralized providers.
57
+
This project is part of the [User & Agents](https://userandagents.com) network. The shared goal is to empower people by designing and building software that provides agency, control, and choice in our digital lives. 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.
62
58
63
59
We are seeking design partners for TEE based cloud workloads that align with our goal of a verifiable privacy perimeter. Contact us at [mail@tiles.run](mailto:mail@tiles.run).
64
60
···
77
73
- [MIT License](https://github.com/tilesprivacy/tiles/blob/main/LICENSE-MIT)
78
74
- [Apache License 2.0](https://github.com/tilesprivacy/tiles/blob/main/LICENSE-APACHE)
79
75
80
-
Downstream projects and end users may chose 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.
76
+
Downstream projects and end users may chose 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.