Real-time · Offline-first · Installable
Type it here. Read it there, a second later.
Kipnot writes each field the moment you stop typing, pushes it to every device you are signed in on through a live Firestore listener, and falls back to a local cache the instant your connection drops.
Free · No card · Export any time
Illustration: a note is typed, auto-saves half a second after the last keystroke, writes only the fields that changed, and appears on every signed-in device.
- Auto-save · 500 ms debounce
- Per-field writes
- Offline cache · multi-tab
- Search with highlight
- Markdown + GFM
- Share by email
- Read or edit permissions
- Public read-only links
- Pin · archive · trash
- 30-day trash recovery
- Export JSON + Markdown
- Installable PWA
- Dark mode follows system
- Delete account and data
01 — Walkthrough
Three things worth seeing before you sign in
These panels mirror the real interface. Switch between them; the offline one is an actual simulation of what the write queue does.
Rewrite the onboarding copy
Cut the second paragraph, move pricing above the FAQ, ship before the Thursday standup.
edited 3s ago
Notes on the offline cache
Firestore keeps a persistent local cache and a multi-tab manager, so two open tabs never fight over the same write.
edited 11m ago
Q3 onboarding review
Nadhira has edit access, Bimasena can read. Both see changes without refreshing.
edited 1h ago
Old pricing experiment
Out of the way, still searchable.
archived Jul 14
Masonry board, client-side search, pin and archive.
Flip the switch. This is the same state machine the editor uses.
- Local cache
- persistent · multi-tab
- Write queue
- empty
- Editor status
- saved
Every change goes straight to Firestore, field by field, and reaches the other devices on the same listener.
02 — Capabilities
Four things Kipnot does without being asked
There is no save button
Editing debounces for half a second, then writes only the field you touched. A Firestore snapshot listener pushes the result to your other devices, so nothing needs refreshing and two people never overwrite each other wholesale.
- Debounce
- 500 ms
- Write scope
- single field
- Transport
- onSnapshot
A dead connection is not an error state
The Firestore persistent cache holds your notes on the device and a multi-tab manager keeps two open windows in agreement. You keep reading, editing, and creating; the queue drains itself when you are back.
- Cache
- persistent local
- Tabs
- multi-tab safe
- Shell
- service worker
Share a note, not your whole account
Invite by email with read or edit rights, or mint a public read-only link. Access lives on the note document itself, so the security rules can enforce it and an invitation to someone without an account activates the moment they sign up.
- Grants
- read · edit
- Links
- public read-only
- Pending invites
- auto-resolve
Leaving is a feature
Export everything to JSON or Markdown whenever you like. Deleted notes wait 30 days in the trash before they go. Delete the account and the data goes with it, in one pass, on the server.
- Export
- JSON · Markdown
- Trash
- 30 days
- Account delete
- data included
03 — How it works
Sign in, write, done
Four steps, and only the first one needs a decision from you.
- 01
Sign in with Google
One provider, no password to invent. Desktop gets a popup, an installed PWA on iOS gets a redirect, and the session survives a reload.
Google Sign-In
- 02
Write
Plain text or Markdown. Pin what matters, tint a note one of eight shades, search across everything with matches highlighted in place.
Markdown · pin · tint · search
- 03
Bring someone in
Send read or edit access to an email address, or hand out a public link that only reads. Everyone watching sees the same paragraph change at once.
Email grants · public link
- 04
Archive, recover, export
Finished notes go to the archive and stay searchable. Deleted ones sit in the trash for 30 days. Your export is one click, in JSON or Markdown.
Archive · 30-day trash · export
04 — Questions
Answered before you ask
What does it cost?
Nothing. Notes, sharing, offline access, and export are all free right now, and there is no card to enter.
What happens to an edit I make with no connection?
It lands in the local cache immediately and the editor tells you it is offline rather than failing. When the connection returns the queued writes replay in order. Because writes are per-field, the resolution is last-write-wins on that one field, not on the whole note.
Can I share with someone who has never used Kipnot?
Yes. The invitation is stored against the note and resolves against their account the first time they sign in with that address, so they see the note waiting for them.
How do I get my notes out again?
Settings has an export that writes every note to JSON or Markdown. You can also delete your account, which removes the notes server-side in the same operation.
Do I have to install anything?
No, it runs in the browser. If you want it on a home screen or in a dock it installs as a PWA with its own window and an offline shell. On iOS, be aware Safari can clear cached site data after about a week of no visits — export if you rely on the offline copy.
Start with one note
Sign in with Google and write something. If you do not like it, export it and go.
Free · No card · Export any time