Software by David Celli.
I build things.
Then I take
them apart.
I’m David. Dynamic Delights is where I build and release my software. EnChord is the big one right now. And yeah, I turned the company site into a 3D encryption experiment.
Dynamic Delights, LLC · Home of EnChord
01 What I’m building
Your group.
Your space.
EnChord puts your group’s messages, voice channels and shared boards in one app. Message content is encrypted on your device; the server delivers it without holding the keys to read it.
- Conversation
- End-to-end encrypted direct messages, group DMs and community channels, with threads and pins.
- Voice
- Voice channels beside your text rooms, and screen sharing for working something out together.
- Shared plans
- A project board with 21 widgets, from task boards to timers, viewable as a canvas, a list, or in 3D. Polls and scheduled events, too.
- Community
- Invitations, roles, permissions and moderation tools, with Sentinel for AutoMod.
- Developers
- A bot and integration API (OAuth2, REST and a realtime gateway) with official SDKs for TypeScript, Python and Java.
- Keyweave
- EnChord’s encryption: hybrid post-quantum key agreement, MLS for upgraded DMs, and separate encrypted history recovery.
This is real AES-256-GCM encryption, running in your browser with a key created in this tab. It shows the idea, not the whole protocol: EnChord’s Keyweave adds hybrid post-quantum key agreement, signatures and key management on top.
02 How I build
How I approach the work.
I’ve spent years taking software apart. That changes how I build my own. Here’s what that looks like in EnChord.
-
01
Assume someone will take it apart.
If code runs on someone else’s machine, expect them to inspect it, change it and replay it. I put security checks where they can actually be enforced and make clients verify what they’re talking to.
In EnChord
- Clients verify the release and its cryptographic contract before decrypting anything.
- Links in messages pass look-alike-domain and phishing checks.
- Bots hold their own end-to-end keys like any other device. Nothing server-side reads or posts for them.
-
02
Use established cryptography.
I use established algorithms and spell out which ones. Keyweave is the name for how EnChord combines them. You can check the actual components below.
In EnChord
- X25519 + ML-KEM-768 hybrid post-quantum key agreement.
- MLS, the IETF’s Messaging Layer Security standard (RFC 9420), for upgraded direct messages.
- AES-256-GCM, Ed25519, HKDF, and Argon2id for recovery kits.
-
03
Say what’s protected, and what isn’t.
EnChord encrypts message content end to end. Account metadata, voice and screen sharing are separate. The details matter, so I list those boundaries instead of calling the whole app “encrypted” and leaving it there.
An independent third-party security review is planned. I’ll call it audited when that review is actually done.
In EnChord
- Post-quantum key agreement doesn’t make Ed25519 signatures post-quantum, and the docs say so.
- Recovery kits restore keys, not transcripts. Password resets don’t restore message keys.
- The privacy page spells out the metadata and recovery-key limits in plain language.
-
04
Keep the clients in sync.
Switching devices shouldn’t mean relearning the app. The clients need to agree, and the SDKs need to produce the same bytes.
In EnChord
- Windows, macOS, Linux, Android, iPhone and iPad, and the web.
- Native Apple apps in Swift, with the MLS core written in Rust.
- TypeScript, Python and Java SDKs derive identical keys from the same seed, checked against shared test vectors.
-
05
Have a way back when a release breaks.
I’ve sold thousands of license keys for earlier software. That also meant handling activation, updates and support. For EnChord, I keep release checkpoints so there’s a way back from a bad build.
In EnChord
- Versioned releases with minimum-version enforcement.
- Release checkpoints, so a bad build can be rolled back.
- Updates that download in the background and install on next launch.
03 The founder
Hey, I’m David.
I’ve been writing software for over twenty years. A lot of that has been cryptography, reverse engineering and licensing systems. I work across more than 29 languages, depending on what the project needs.
Before EnChord, I built and sold commercial software with thousands of license keys out there. Dynamic Delights is the company behind what I’m building now.
04 Contact
Let’s talk.
Got an idea, a question, or something I should take a look at? Email me.
- General and pressCompany, partnerships and media
- [email protected]
- EnChord supportAccounts, billing and help with the app
- [email protected]
- PrivacyData and privacy requests
- [email protected]