A foundation preview built on open protocols
Your work,
in your hands.
Atelier is becoming a thoughtful suite for notes, mail, calendars, and tasks—planned to be native on every device, portable by design, and powered by your ATProto identity.
- Web preview
- Planned: iPhone & iPad
- Planned: macOS
- Planned: Android
Project Atlas.md
ATELIER NOTES
Ideas need
room to breathe.
Markdown-first writing; shared editing across devices is the release target.
Turn raw thoughts into connected work.
SCJD2 sample collaborators
Unified Inbox
Calendar
MONTUEWEDTHU
Design sync · 10:00
Today
Five focused tools, one shared foundation
Five focused products.
One shared direction.
Each planned product stands on its own. The shared contracts are designed to turn a message into a task or an event into a note without inventing a second copy of your data.
01
Atelier
Your day, composedPreview the planned Today, Inbox, Projects, search, and cross-app actions in one calm workspace.
Open Atelier preview 02Atelier Notes
Markdown without lock-inTry the in-memory Markdown editor and inspect the planned local-file, versioning, and collaboration model.
Open Notes preview 03Atelier Mail
Your inbox, not the provider'sExplore a fixture of the Gmail-first interface; accounts, provider sync, compose, and send are not live.
Open Mail preview 04Atelier Calendar
Open schedules, faithfully keptInspect the planned lossless ICS and provider model; parsing, feeds, sync, and writeback are not live.
Open Calendar preview 05Atelier Tasks
Shared work that stays yoursExplore a local board fixture for planned projects, recurrence, offline edits, and collaboration.
Open Tasks previewHonest about the protocol
Your PDS records will be public.
We’ll say so before any write.
Standard ATProto repositories are readable. Under Atelier’s interim model, connected first-party work records will use that public substrate with explicit disclosure and user-scoped discovery. The provider boundary is designed to keep credentials, Gmail content, and private calendar mirrors off the PDS by default.
Read the public-data modelPUBLIC PDSdiy.atelier.notes.note
{
"title": "Project Atlas brief",
"markdown": { "$type": "at.markpub.markdown" },
"checkpoint": { "uri": "at://did:plc:…/…", "cid": "bafy…" },
"schemaVersion": 1,
"createdAt": "2026-08-30T20:00:00Z",
"updatedAt": "2026-08-30T20:00:00Z"
}Planned records are readable by anyone who finds themThis is an illustrative fixture. Permissioned Spaces migration remains capability-gated future work.
Collaboration without surrender
Local-first writing.
Peer-aware sync.
The planned Notes architecture keeps your Markdown file as source. Automerge will track collaborative intent; Iroh transport and the trusted sync anchor are not connected yet.
Portable source on your device
Convergent edits and versions
Authenticated peer transport
Reliable rendezvous and durability
One workspace, every screen
Native where it matters.
Web when it helps.
The repository now includes foundations for five universal SwiftUI apps, five Compose apps, and five focused web previews. Native release builds and cross-platform feature parity are still future gates.
Today
Your exit is a feature
Open formats, all the way down.
Markdown
The Notes release target keeps notes and rich bodies readable in ordinary tools.
Calendar
The Calendar release target round-trips schedules without discarding RFC 5545 detail.
ATProto
Checked-in contracts cover identity, records, relationships, and public publishing.
Agent access
The backplane foundation fails closed; authenticated domain tools are not live yet.
Questions, answered plainly
Before beta.
Will my Atelier content be private?
Not during the standard-PDS phase. When writes are connected, first-party Notes, Tasks, Calendar, Projects, Captures, and relationships will be readable public records with disclosure before every affected write. Provider mail and calendar content is designed to remain protected server-side.
Will I be able to leave?
That is a release requirement. Notes are designed to remain Markdown, calendars to round-trip through ICS, and ATProto records to stay in your repository. These export paths are not all implemented yet.
Where will collaboration happen?
The Notes architecture targets a shared Rust Automerge-over-Iroh protocol with a trusted Railway anchor and opportunistic direct peers. The checked-in protocol foundation is not a live collaborative service yet.
What can I use today?
The published surfaces are transparent foundation previews. The Notes editor and some local interactions work in memory; accounts, persistence, provider connections, collaboration, and the public beta are not open.
The public beta is not open
Follow the work.
Know the boundary.
There is no signup or waitlist yet. The coordinated beta opens only after all five products clear accessibility, security, provider, and reliability gates.