Early access
Write the issue. A person approves. Then it goes out.
A newsletter app for small publishers: readers who confirmed by double opt-in, an editor with a test to your own address, an approval bound to the content and the audience, and sending that stops when complaints rise.
Early access, and plain about it: invite-only, payments in test mode, and sending to real inboxes is not switched on yet. The windows on this site show sample data.
Works with your own AIClaudeChatGPTGrok
Before anything else
What works today.
We would rather say it here than let you find out later.
- Pre-betaPublications, readers, issues and approval
Built and in the app now. Early access: people request access.
- Pre-betaSending runs in test mode
The sending pipeline, bounces, complaints and the automatic pause are built. No mail leaves the app until a mail provider is connected for production.
- Pre-betaYour own AI through the door
On every plan. It prepares work; it never approves or sends.
- Pre-betaBring your own AI
Your own AI does the preparing, on its own subscription.
What it does
Readers. Issues. A yes before every send.
Readers
Double opt-in, a consent log that only grows, and one-click unsubscribe.
ReadersWrite
An editor with templates, autosave, a preview and a test to your own address.
The editorApprove
A person approves the exact content for the exact audience.
ApprovalSend
Scheduled sends, delivery states, bounces and complaints handled.
Sending
Approval
Nothing goes out without a yes.
Every send waits for a person. The approval is tied to the content of the issue and to the audience it goes to, so a change after the yes needs a new yes. Your own AI can prepare an issue; it cannot approve it.
- Approval bound to content and audience
- A change means a new approval
- AI prepares, a person decides
Sending
Sending that stops itself.
Bounced and complained addresses are suppressed and never mailed again. When complaints pass 0.1 % of a send, the send pauses itself, and a kill switch stops everything at once. During early access this runs in test mode.
Questions
The first questions.
What is Geenius Newsletter?
A newsletter app for small publishers. Readers confirm by double opt-in, you write an issue and test it on yourself, a person approves it for its audience, and the send goes out at the time you pick.
Can I use it today?
In early access, yes: it is invite-only, and sending to real inboxes is not switched on yet, so sends run in test mode. Ask for a place.
Does it send real mail yet?
Not yet. The sending pipeline is built, but during early access sends run in test mode and no mail leaves the app. Real delivery comes when a mail provider is connected for production.
Why does every send need an approval?
So nothing goes out by mistake. The approval is tied to the content and the audience; change either and the send needs a new yes.
Does Newsletter write the issue for me?
Your own AI can. Bring your own AI: it can prepare drafts through the door on every plan, and a person approves every send.
How much does it cost?
Pro €19, Premium €39 and Max €79 per seat per month, with your own AI on every plan. Payments are in test mode during early access.
From the blog
Notes on mail people asked for.
Bringing your readers with you, with their consent
How importing an existing list into Geenius Newsletter works, what you state about consent, who is never imported, and how to take your list with you.
Why a person approves every send
Why every Geenius Newsletter send waits for a person, why the approval is tied to the content and the audience, and why your AI cannot give it.
Ask for a place.
Newsletter lets people in step by step. Ask for a place, or sign in.