Happy birthday! Your joy is contagious.
Marisol · textIndependent scan · checked August 7, 2026
Every good way to gather a roomful of love.
We went beyond the obvious names to compare group cards, video montages, audio keepsakes, and QR guestbooks—using official product evidence and attributed public reviews.
22-second video
Devon · video✦ ☻ ✦
Best year yet!
Priya · GIFListen to a memory
Jordan · audioservices
40+live services
—purpose-built
—attributed reviews
—source links
Not a scraped listicle: every card exposes its evidence and caveats.
Start here
Four jobs, four likely winners
These are editorial shortcuts, not paid placements. Use the filters below for your exact media mix.
The full field
Find the right collector
No exact match
Try one fewer media requirement or clear the guest-account filter.
What we learned
The market is busy. The guest experience is not solved.
Most services optimize the finished artifact or team-admin controls. Far fewer make editing effortless for accountless guests.
Cards are abundant
Group-card products cover text and imagery well, but video, audio, and guest editing are inconsistent.
Video adds friction
Montage makers often add upload rules, rendering steps, price tiers, or app prompts that interrupt a quick message.
QR tools skew event-first
Guestbooks excel at event-day uploads, yet can feel oversized for a private birthday assembled by friends.
The opening
One host account, one guest link, one local edit capability, and one recipient page. Nothing else unless evidence demands it.
Evidence before vibes
How this atlas was researched
We searched across three non-overlapping lanes, expanded from discovered competitors, verified live official pages, then paired claims with public user-review evidence where available.
- Discover broadly.Group cards, recorded-message collectors, QR guestbooks, and adaptable tools.
- Verify the workflow.A service must actually collect contributions—not merely send a prewritten e-card.
- Separate evidence.Official pages support features; attributed public reviews support user sentiment.
- Expose uncertainty.Blocked, snippet-only, outdated, or quote-based facts stay visibly labeled.
Open audit data ↗
38 discovery queries + verification passes
Review excerpts are brief and shown for research/commentary with direct attribution. Product names and imagery belong to their respective owners. No service paid for inclusion.
Jam draft · v0.1 Built from the market gap
One host account.
Zero guest accounts.
A radically simple collector for text, photos, GIFs, and short video. Guests follow one link, leave one message, and keep a private edit capability on their own device.
Host creates→Guest contributes→Recipient opens
For Nina’s birthday•••
LEAVE A MESSAGE
Send message →
No account. You can edit from this device.
01 / NORTH STAR
Make the loving part easy.
A host creates a private collection link. Anyone with it can add a message or media without an account. The host publishes one clean gift page when it is ready.
One account, not forty
Only the person organizing the gift signs in.
Link → message → done
Median guest completion should stay under one minute.
Editing is a capability
An unguessable token—not a guessed ID or ordinary cookie—authorizes changes.
The collection is the product
No social network, design suite, marketplace, or app install.
SUCCESS SIGNAL0
guest-account prompts, from first open through edit
02 / CORE FLOWS
Three people. Three tiny jobs.
Create & share
- Magic-link sign in
- Name the recipient
- Copy contributor link
- Moderate and close
- Publish recipient link
Leave a message
- Open the link
- Add name + message
- Optional media
- Submit
- Edit from this device
Open the gift
- Open private link
- Read and play
- Swipe or scroll
- Feel extremely loved
03 / GUEST EDITING
Local convenience, server-side authority.
The browser remembers a private capability. The server still verifies every edit and delete.
1Guest submitsPOST contribution
→
2Server returns256-bit edit token
→
3Browser storeslocalStorage + private link
→
4Server verifieshashed token on every change
Stored on this device
giftboard:edit:v1:<collection>:<message> → <random-token>
Why not “just a cookie”?
A readable cookie has similar XSS exposure and adds automatic request behavior. An HttpOnly cookie is safer but awkward for many separate message capabilities and cannot power a portable private edit link. A scoped bearer token in local storage is explicit and simpler.
- Store only a salted/peppered token hash server-side.
- Scope each token to one contribution and edit/delete only.
- Also offer a copyable URL with the token in the
#fragment, then strip it from visible history. - If storage and the private link are both lost, the host—not an identity-recovery maze—handles the change.
04 / MVP SCOPE
A small product with sharp edges.
✓ In the first release
- Host magic-link account
- Private contributor link
- Text up to 1,000 characters
- One photo, GIF, or 90-second video
- Same-device guest edit/delete
- Host hide/delete and close/reopen
- Private recipient page
- Independent link rotation
× Deliberately not now
- Guest accounts or email recovery
- Contacts, invitations, or SMS sending
- Freeform card designer
- AI-written messages
- Automatic montage rendering
- Physical print fulfillment
- Multi-host roles
- Public discovery or SEO pages
05 / DATA & PERMISSIONS
Four tables. Four roles. No mystery.
users
id · email · created_at
collections
host · recipient · title · status · link hashes · media policy
contributions
collection · name · text · asset · edit hash · moderation
media_assets
provider key · MIME · bytes · duration · processing status
06 / SAFETY & PRIVACY
Private by default is a feature.
Unguessable, rotatable links
Contributor and recipient links use separate random tokens. Rotating either does not erase valid guest edit capabilities.
Uploads become safe assets
Decode and inspect real MIME; strip metadata; reject SVG/HTML; process video before playback; serve private derivatives.
Abuse friction only when needed
Rate limits and honeypots first. Show Turnstile only for elevated risk, not to every loving aunt.
Plain text, no tracking profile
Render contributor text as text. Log aggregate product events—not message contents—and never train on gifts.
Visible retention
Recommend 12 months after publication, show the deletion date, and give the host delete/export controls.
07 / FIRST BUILD
Prove the capability seam before video.
- 01Host + collection
Magic-link sign-in, one private collection, one random contributor URL.
- 02Text-only guest vertical slice
Create a message without an account and return a single-use raw edit token.
- 03Edit proof
Same browser can edit/delete; a fresh browser without the token is denied.
- 04Host moderation + publish
Hide/remove, close, then publish to an independent recipient token.
- 05Images and GIFs
Short-lived direct uploads, MIME decoding, derivatives, and one-attachment limit.
- 06Short video
Add managed transcoding only after authorization and moderation are solid.
08 / OPEN DECISIONS
Jam with me.
Click a stance to cycle it. Your calls stay in this browser and appear in the export panel.
01
Birthday-first brand, or neutral for every occasion?
Recommendation: warm all-occasion product with birthday as the clearest landing page.
02
One-time collection fee, subscription, or both?
Recommendation: one-time host purchase first; recurring plans only for teams later.
03
Approve every message, or show unless hidden?
Recommendation: show to host immediately; recipient never sees anything until publish.
04
May one browser leave multiple messages?
Recommendation: yes. Store one independent edit capability per message.
05
Default retention after publication?
Recommendation: 12 months, clearly displayed, with host-controlled early deletion.
06
Downloadable keepsake in MVP?
Recommendation: hosted page first. Design the data model so export can follow.
07
Video in first paid release?
Recommendation: yes commercially, but build it after the text/image capability seam.