Changelog
Everything we shipped, dated
Taken from the repository rather than from memory. Quiet months are shown as quiet months — a product that reports steady progress every single month is reporting something other than progress.
- Since April 2026
- 444 commits
- Updated as things ship
Release timeline
- Site & trust
The public site, and some honesty fixes
- Feature, tools and integration pages built — every link in the navbar now resolves.
- Free tools that genuinely run with no account: character counter, engagement rate calculator, image size cheatsheet and a timezone-aware posting planner.
- Integration pages that list what each network does NOT support as well as what it does.
- SEO foundation: canonical URLs, Open Graph images, robots.txt, a real sitemap and structured data across the site.
- Removed fabricated social proof from the landing page, and a '14-day Pro trial' that did not exist in any plan.
- Google Business review auto-replies are now metered against the owner's AI allowance and default to the free template mode rather than the paid AI one.
- Plans & billing
The money path, and the limits that go with it
- Creator plan built end to end — per-account slot pool, per-seat pricing and the Stripe path behind both.
- Connected accounts lock to paid slots on Creator, with changes taking effect at renewal rather than mid-cycle.
- Deep analytics gated to Pro and Agency; AI-only navigation hidden on plans without AI.
- Downgrades now take effect at period end, closing a leak where an account could burn a full month of AI after downgrading.
- Agency seat handling: teammate allowances, credit gifting and a seat prompt on downgrade.
- By a distance the busiest month of the project — most of the plan and billing surface dates from here.
- Publishing
Richer posts on X
- Image and video support added to X publishing.
- A quiet month otherwise — most of it went on the billing work that landed in August.
- Engagement
Auto-replies, the calendar and the first marketing pages
- The auto-replies engine: rules, generated reply variations and the unified inbox.
- Content calendar and the drafts kanban.
- First version of the blog and the marketing site.
- Foundations
Connections, and the shape of the product
- OAuth flows for X, LinkedIn, Snapchat and the rest of the initial platform set.
- Real-time connection state shared across the dashboard.
- Pinterest, WhatsApp and Reddit trialled and then removed from the supported set — their APIs did not support what we wanted to promise.
- First commit: 5 April 2026.
What is next
Named honestly, without dates we cannot keep.
TikTok and LinkedIn comment replies
Both networks are read-only in the inbox today. The reply plumbing exists for seven other networks, so this is adapter work rather than new architecture.
TikTok and LinkedIn post insights
Publishing works on both; post-level metrics are not pulled in yet. Ad performance on both is already reported.
A public API worth documenting
Key issuance and Bearer auth exist. The set of endpoints that accept a key is still small — see the API page for exactly where it stands.
Snapchat publishing
Blocked on Snapchat, not on us. They provide no organic content API to anyone. If that changes, the rest of the pipeline is already built.
No dates attached deliberately. A roadmap with dates on it is a promise, and we would rather ship the thing than manage the promise. Tell us which of these you need and it moves up.
Questions
- How often do you ship?
- Continuously, but not evenly. Some months are a single focused piece of work and some are most of the product — August 2026 carried more than the four months around it combined. The list above reflects that rather than smoothing it out.
- Where do these dates come from?
- The repository history. Each entry is the month the work actually landed, not the month it was planned or announced.
- Do you announce breaking changes?
- Anything that changes behaviour you rely on gets called out here and by email before it ships. Plan and billing changes take effect at your next renewal, never mid-cycle.
- Can I request a feature?
- Yes, and the contact form reaches a person rather than a queue. What gets built soonest is usually what several people have asked for independently.
Still stuck, or want a hand setting something up?