Send-time autopilot
Ferrywake learns when each subscriber usually opens email and delivers inside that hour, in their own time zone.
00:0008:0016:0024:00
Autopilot windowOpens by hour
Ship updates people read
Turn your changelog into a digest customers actually open.
Ferrywake collects what your team shipped, drafts a plain-language weekly digest, and sends it at the hour each subscriber reads.
- Send-time autopilotReady
- Audit log exportReady
- SSO domain captureAI draft
- Scheduler drift on daylight savingNeeds copy
Weekly digests for 1,900 product teams, including
- Driftpost
- Kelpworks
- Northquay
- moorline
- Tidevane
- Quillport
From merged to read in three moves.
Ferrywake plugs into the tools your team already ships from. You approve every sentence before anything sends.
feat(scheduler): per-subscriber send windowPR #1482, merged Tue by Ana PetrovAutopilotfeat(audit): export log as CSVPR #1477, merged Wed by Joel MarshAdminFW-218 SSO domain capture on sign-upTicket closed Wed by Priya RamanAuthfix(scheduler): tz drift on DST boundaryPR #1486, merged Thu by Ana PetrovAutopilotRelease note: EU region p95 improvementsDoc edited Thu by Noor HaddadInfra
5 items grouped into 4 features. Refactors and dependency bumps are filtered out.
feat(scheduler): per-subscriber send windowEach subscriber now gets the digest at the hour they usually read.
feat(audit): export log as CSVAdmins can export the full audit log as CSV in one click.
FW-218 SSO domain capture on sign-upTeammates who sign up with your company email join your workspace automatically.
Tone matched to Digests 38 to 42. Nothing sends until you approve it.
00:0008:0016:0024:00
07:40Helsinki, 212 readers
08:15Lisbon, 164 readers
09:05Toronto, 301 readers
Every reader gets Friday's digest inside their own best hour, local time.
Everything between merged and read.
Audience segments
Admins, end users and trials each get the cut of news that matters to them.
End users 820
Admins 212
Trials 188
EU accounts 431
Internal 64
Section analytics
See which kind of news gets read, so you know what to lead with next week.
Tone lock
Drafts match the voice of your last five digests, so nothing reads like a press release.
feat(audit): export log as CSV
Admins can export the full audit log as CSV in one click.
Matches Digests 38 to 42
Matches Digests 38 to 42
API and webhooks
Post entries from CI, mirror each digest to your docs site, or stream open events into your warehouse.
Find your API key in Settings# Add an entry from your deploy pipeline curl -X POST api.ferrywake.example/v1/entries \ -H "Authorization: Bearer $FERRYWAKE_KEY" \ -d title="Audit log export" \ -d section="new" \ -d source="PR #1477"
Customer story
Driftpost went from 19% to 44% digest opens in six weeks.
Their release crew of three used to spend Friday afternoons rewriting merge titles. Now they edit a few drafted sentences and let autopilot pick the hour.
- Digest open rate
- 44%
- Hours saved per release
- 3.5 h
- Sentences edited per week
- 4
Teams that stopped dreading release notes.
“Customers read the digest before they write to us. Our ‘is it live yet?’ tickets simply stopped piling up.”
52%fewer release-status tickets in one quarter
Mari HalonenHead of Support, Northquay
“Our open rate went from 19% to 44% in six weeks. The news was fine all along. The timing was wrong.”
Lena KovarHead of Product, Driftpost
“I paste the merge list on Friday, edit four sentences, and it's done. Release notes used to eat half my afternoon.”
Tomás OduyaFounder, Kelpworks
Questions teams ask before switching.
Can't find what you need? A person from our Helsinki or Toronto team replies within one working day.
From the tools you already ship with. Connect GitHub or GitLab for merged pull requests, your issue tracker for closed tickets, or post entries from CI through the API. Ferrywake only asks for read access to titles, labels and merge dates.
One credit drafts up to three customer-facing entries from your merged work, or rewrites a single entry. Plans include a monthly allowance, and credit packs top you up without changing plans. Pack credits never expire.
Yes. Every digest footer links to a preferences page where readers pick weekly, monthly, or major releases only. Autopilot still chooses the hour for whichever cadence they prefer.
Yes. Fleet workspaces can pin subscriber data to our EU (Frankfurt) or US (Virginia) region, and our standard DPA can be signed from the billing page. The DPA summary lists every sub-processor.
Digests stop at the end of your billing period and you keep read access to the archive for 90 days. You can export subscribers and past digests as CSV or HTML at any time, before or after cancelling.
Your next digest could send itself.
Start free with 10 AI credits. No card needed until your first send.
Prefer to look around first? Open the live demo
Pay for the digest, not the seats.
Every plan includes unlimited teammates. Change or cancel from the billing page whenever you like.
Skiff
For one product and a list under 1,000 readers.
$19/ month
Billed monthly, cancel anytime
- 1 digest stream
- Up to 1,000 subscribers
- 10 AI credits a month
- Fixed send time and public archive
- Open and click analytics
Fleet
For teams with several products or audiences.
$59/ month
Billed monthly, 14-day trial
- 5 digest streams
- Up to 15,000 subscribers
- 60 AI credits a month
- Send-time autopilot and segments
- Section analytics and tone lock
- SSO, audit log, EU or US data region
Credit pack
Top up drafting without changing your plan.
$12one time
40 AI credits that never expire
- Drafts up to 120 entries
- Works on Skiff and Fleet
- Shared across the workspace
- Used after your monthly credits
Compare plans
| Feature | Skiff | Fleet |
|---|---|---|
| Digest | ||
| Subscribers | 1,000 | 15,000 |
| Digest streams | 1 | 5 |
| AI credits each month | 10 | 60 |
| Public archive pages | ||
| Delivery | ||
| Fixed send time | ||
| Send-time autopilot | ||
| Audience segments | ||
| Security | ||
| Signed DPA | ||
| SSO and audit log export | ||
| EU or US data region | ||
Unlimited teammates
Invite every editor and approver you need. You pay for readers reached, never for seats.
How credits roll over
Monthly credits reset on your billing date. Pack credits never expire and are spent last.
Cancel from the billing page
No calls and no forms. You keep read access to your archive for 90 days.
Over 15,000 subscribers?
We'll set up custom volume, annual invoicing and a security review for your team.
Welcome back
Sign in to your Ferrywake workspace.
This is a clickable prototype. Sign-in is simulated, so any email with an 8-character password works.
or continue with email
By continuing you agree to the Terms and Privacy notice.
Back to ferrywake.example© 2026 Ferrywake Ltd.
“Autopilot sent our digest at 07:40 Helsinki time. Half our admins had read it before standup.”Mari Halonen, Head of Support at Northquay
How Driftpost's three-person release crew doubled digest opens.
Driftpost makes scheduling software for field-service teams. Their weekly product email had a 19% open rate and a Friday-afternoon writing habit nobody wanted to keep.
44%digest open rate, up from 19%
3.5 hsaved on every weekly release
4sentences edited per digest, on average
Release notes nobody read
Driftpost ships to production most days. Every Friday, Lena Kovar and two engineers turned forty merge titles into an email for 4,800 dispatchers and admins. It took most of the afternoon, went out at 16:00 Aarhus time, and landed after half their customers had gone home.
“We had good news every week,” Lena says. “It just arrived when nobody was looking.”
Letting the merge list write the first draft
Driftpost connected their GitHub organization and issue tracker in one sitting. Ferrywake now groups merged work by feature, filters out refactors and dependency bumps, and drafts a customer-facing sentence for each change in Driftpost's own tone.
The crew edits about four sentences a week. The rest go out as drafted.
“Friday release notes went from an afternoon of rewriting to one cup of coffee.”
Lena KovarHead of Product, DriftpostSending when each customer is listening
Dispatchers start early; office admins read after lunch. Send-time autopilot learned both patterns within three sends and now delivers every digest inside each reader's usual hour, in their own time zone.
Two segments get different lead stories from the same week of work, so dispatchers see routing changes first and admins see billing and permissions.
What changed for support
Tickets asking whether a fix had shipped fell sharply once customers saw the digest at the right moment. Support now links to the public archive page instead of writing one-off replies.
See your own changelog as a digest.
Ferrywake Weekly
What we shipped each week, written the way our customers read it. Yes, we send this with Ferrywake.
Security, privacy and terms
Plain-language summaries of how we protect your data and what we agree to. The signed documents govern.
Last updated 14 September 2026
Security
Ferrywake reads titles, labels and merge dates from the repositories and trackers you connect. We never request write access and never read source code.
Access and authentication
- OAuth scopes are read-only and can be revoked from your provider at any time.
- Fleet workspaces can require SSO through any SAML 2.0 identity provider.
- Every approval, send and settings change is written to an exportable audit log.
Infrastructure
- Data is encrypted in transit with TLS 1.2 or later and at rest with AES-256.
- Production access requires hardware keys and is reviewed every quarter.
Privacy
We store subscriber email addresses, names if you provide them, segment membership, and open and click events. We use this data only to deliver your digests and show you analytics.
- Open and click events are kept for 13 months, then aggregated.
- We do not sell data or use subscriber data to train models.
- Subscribers can unsubscribe or request deletion from any digest footer.
Terms
- Plans are billed monthly or yearly in advance; you can cancel at any time from the billing page.
- Monthly AI credits reset on your billing date. Credit packs are non-refundable and never expire.
- You own your content and your subscriber list. You are responsible for having consent to email your subscribers.
- After cancellation you keep read access to your archive for 90 days.
DPA and sub-processors
Our standard Data Processing Agreement includes the EU Standard Contractual Clauses and can be signed from the billing page. Fleet workspaces choose where subscriber data lives.
| Sub-processor role | Purpose | Location |
|---|---|---|
| Cloud infrastructure provider | Hosting and storage | EU (Frankfurt) or US (Virginia) |
| Transactional email provider | Digest delivery | EU or US, matching your region |
| Payment processor | Billing | EU and US |
| Error monitoring service | Application diagnostics | EU |
404
This page drifted out of the harbor.
The link may be old, or the page moved. Try the homepage or last week's digest.