One calendar for thirteen social networks
Socialeasy is where your team plans the month, writes the posts, gets them approved, publishes them on time and proves what worked — without four browser tabs and a spreadsheet.
Free plan forever · 1 brand, 3 channels, 30 scheduled posts
13 networks, one calendar.
Single-origin Ethiopian is back on the bar tomorrow. Ten kilos, roasted Friday, gone by Sunday if last month is anything to go by.
- 13
- networks with native publishing
- 1
- composer for every variant
- 60s
- from brief to five scheduled posts
- 0
- spreadsheets required
Features
Everything between the idea and the monthly report
Six pieces of software most teams stitch together, built as one product so the calendar, the approvals and the numbers all talk to each other.
Drag a post to Thursday and every network moves with it
Month, week and list views for one brand at a time, colour-coded by campaign. Drag to reschedule, drop onto a queue slot to take the next best time, and see drafts, pending approvals and failures alongside what is already live.
- Drag-and-drop rescheduling that keeps status and channels intact
- Per-brand queue slots — drop a post in and it takes the next free time
- Campaign colours carry through to the calendar and the report
- Everything rendered in the brand’s own timezone, not yours
One idea in, a correct version for every network out
The composer knows each network’s character limit, media rules and quirks. Ask for variants and you get copy that fits X’s 280 characters, LinkedIn’s longer form and Instagram’s hashtag habits — in your brand voice, with your banned words respected.
- Per-network rewrites with live character and media validation
- Brand voice, audience and banned-word list applied every time
- Hashtag groups, alt text and first comments suggested inline
- Nothing publishes until you have read it
Ten kilos of single-origin Ethiopian. Roasted Friday. Bar opens 7am.
We roast on Friday so the bar pours on Saturday — here is why freshness beats volume for a 4-person roastery.
Friday roast, Saturday pour ☕ Ten kilos only. #specialtycoffee #singleorigin
Client sign-off that leaves a paper trail
Creators submit, reviewers decide. Approve, reject or request changes with a required note, and the decision is stored against the exact version it applied to. Internal comments stay internal; client review links stay read-only.
- Roles for owner, admin, manager, creator, reviewer, viewer and client
- Required note on “request changes” so nobody guesses
- Version history with one-click restore
- Client review links that need no seat and no login
Spring menu drops Monday. Three new drinks, one of which is decaf — yes, really.
Devon (client) — Can we say “oat by default”?
Priya (manager) — Approved — scheduling for Mon 08:15.
Cross-network numbers, then a PDF with your logo on it
Impressions, engagement, clicks and follower growth normalised across networks so a LinkedIn post and a Reel sit in the same table. Build a report once, brand it, and schedule it to land in the client’s inbox on the first of the month.
- Post-level and account-level metrics synced on a schedule
- Best-time recommendations derived from your own history
- White-label PDF reports — your logo, colours and footer
- Scheduled monthly sends, or a share link that never expires
Impressions
482K
+18%
Engagements
31.4K
+9%
Link clicks
6,208
+26%
Comments, DMs, mentions and reviews in one queue
Every conversation across every connected channel lands in the same list. Assign it, tag it, reply with a saved response or an AI draft, and mark it resolved — so “did anyone answer this?” stops being a question.
- One queue across all 13 networks, filtered by channel or kind
- Assignment, tags, sentiment and unread state
- Saved replies with shortcuts, plus AI drafts in brand voice
- Reply history stored next to the post that started it
@leilabrews
Do you ship to Ireland?
Tom Alvarez
Loved the oat flat white 👌
@coffee_nerd
What grinder is that?
5★ review
Best espresso on the street.
A start page that is actually measured
Build the page every profile points at — links, products, an embedded video, a newsletter signup — themed to the brand. Every click is counted, so the link in bio shows up in the same report as everything else.
- Blocks for links, headers, images, video, products and forms
- Per-brand theming with your own colours and fonts
- Click counts per block, rolled into brand analytics
- Published on your own slug, ready to paste into any profile
Northwind Coffee
Roastery + bar · Leeds
2,481 clicks this month
Twelve clients, twelve calendars, one login
Every client is a brand inside your workspace, with its own channels, voice, campaign colours, queue and timezone. Switch between them from the top bar; nothing leaks across.
Multi-brand workspaces
Unlimited brands on the Agency plan, each with its own channels, campaigns, queue slots and brand voice. Members can be scoped to only the brands they work on.
Client roles that fit
The client role sees only their brand: approvals, reports and the calendar. No billing, no other clients, no way to publish by accident.
White-label reports
Swap the Socialeasy mark for your own, set the accent colour and footer note, then schedule the PDF to send from your domain every month.
Per-brand timezones
A Sydney client and a Chicago client sit in the same workspace, and both calendars read in local time — including the 09:00 that is nine in the morning for them.
Comparison
How this differs from a scheduling-only tool
Plenty of tools post on a timer. The gap shows up once more than one person is involved, or once a client asks what any of it did.
| Capability | Socialeasy | Typical scheduling-only tool |
|---|---|---|
| Networks in one composerWrite once, adapt per network without leaving the editor. | 13 networks incl. Bluesky, Mastodon, Threads | The big four, usually |
| Per-platform variantsDifferent copy, media and first comment per channel. | Built in, AI-assisted, with live validation | Not offered |
| Approvals & client reviewReviewers, required notes, and a full decision trail. | Roles, review links without a seat, version history | Single approver, if any |
| Multi-brand workspacesKeep clients, voices and calendars separate. | Unlimited brands with per-brand scoping | One profile group per account |
| ReportingWhat you hand to a client at the end of the month. | Cross-network reports, white-label PDF, scheduled sends | CSV export |
| Unified inboxComments, DMs, mentions and reviews in one queue. | Assignment, saved replies, sentiment | Separate add-on |
| Link in bioThe landing page every profile points at. | Included, with click analytics | Not offered |
| AutomationQueue slots, best-time scheduling and recurrence. | Per-brand queues, best-time from your own history | Fixed time slots |
Capabilities are compared in general terms. Individual products vary — check the current feature list of anything you are evaluating.
Pricing
Four plans, no surprise line items
Every plan includes all 13 networks, the composer, the calendar and the link-in-bio page. What changes is how many brands, seats and AI credits you get.
Free
Get your calendar under control.
$0/month
- 1 brand, 3 channels
- 30 scheduled posts
- Calendar + queue
- 25 AI credits / month
- Link-in-bio page
Essentials
For creators who publish every day.
$12/month
- 2 brands, 10 channels
- Unlimited scheduling
- Full analytics + 12 months history
- 500 AI credits / month
- Unified inbox
Docs
Answers before you sign up
The short version of the documentation — connecting channels, how publishing actually runs, and what happens when a network says no.
Connecting channels
Most networks connect with OAuth in two clicks. Mastodon and Bluesky use an instance URL plus a token or app password, which we encrypt at rest. Instagram needs a Business or Creator account linked to a Facebook Page.
How publishing runs
Scheduled posts are picked up by a cron worker every minute, published per channel, and marked with the remote post ID and URL. Each channel succeeds or fails on its own, so one broken token does not take the rest down.
When something fails
The exact network error is stored against the channel, the post is marked failed, and the author is notified. Retry from the post list or the detail page — only the failed channels are attempted again.
FAQ