Curated

Curated is an editorial newsletter service for creators, publishers, and marketers who build issues around selected links and commentary. It brings collecting, publishing, sponsorships, paid subscriptions, and audience analytics together. Choose it for that focused workflow, but weigh its subscriber-based prices and message quota as your list grows.

Overview

Curated is built for newsletters that explain why a link matters, not just send a stream of email. Editors can collect material and add their own context before publishing; sponsorship handling and paid subscriptions extend that workflow into monetization. It is a more natural fit for editorial publications than for teams seeking a general-purpose email platform.

Key features

Collection and publishing

Links can be gathered with a bookmarklet, Chrome extension, or secret email address. Editors can add introductions, summaries, or personal insights, then send customizable newsletters. A web edition with searchable issue archives gives readers another way to find older material. Custom top-level domains and subdomains are supported, with HTTPS enabled after DNS setup.

Revenue and analytics

Curated handles sponsorship inquiries, bookings, and a scheduling calendar, which is useful for publications managing sponsor placements alongside their editorial schedule. Paid subscription newsletters are supported, and Curated says it takes 0% commission. Subscriber-level statistics cover audience growth and what is working, giving editors signals to guide future issues.

Integrations and limits

Zapier support includes four triggers and three actions. The public API uses token authentication at https://api.curated.co/api/v3. It can collect links, but not text items, and cannot publish issues, so API-led workflows still need another way to handle those parts of publishing.

The monthly message allowance is 31 times the plan's maximum subscriber count, and unused quota does not roll over. That ties sending capacity to list size and makes the no-carryover rule relevant for publishers with uneven schedules. Curated says it maintains reasonable, commercially acceptable security procedures but cannot guarantee absolute security. Its EU privacy page says servers are in the UK, with hourly backups retained for one week and daily backups for 30 days. Support is available through a support center and [email protected].

Pricing

Curated has a free plan and paid plans billed monthly according to subscriber count. Free covers 0–1,500 subscribers at no cost. That provides room to start without a subscription charge, but the subscriber ceiling means a growing publication must move to a paid tier.

• 1,501–2,500 subscribers: $39 a month.
• 2,501–5,000 subscribers: $69 a month.
• 5,001–10,000 subscribers: $129 a month.
• 10,001–15,000 subscribers: $189 a month.
• 15,001–25,000 subscribers: $299 a month.
• 25,001–50,000 subscribers: $399 a month.
• More than 50,000 subscribers: custom pricing; contact [email protected].

The stepped tiers make the monthly cost predictable within a subscriber band, but a larger audience brings a higher bill as well as a larger message allowance. A free trial is available. Check the quota against your sending pattern before committing, since unused messages do not carry over.

Platforms

Curated supports web, browser extension, and API access. That combination suits editors who collect links while browsing and publishers who need programmatic link intake; the API's inability to publish issues limits its usefulness as a complete publishing interface.

Who it's for

Curated is strongest for link-led editorial newsletters whose publishers want commentary, searchable archives, sponsorship administration, and paid subscriptions in the same service. It is less suitable when the core workflow depends on publishing text items or issues through the API, or when subscriber-based monthly charges and a non-carrying message quota do not suit the sending schedule.

Pros and cons

Pros

• Collection through a bookmarklet, extension, or email makes it practical to gather links from different workflows.
• Commentary, customizable newsletters, and searchable web archives serve publications built around curated material.
• Sponsorship scheduling, paid subscriptions with 0% commission, and subscriber-level analytics address several editorial business needs together.
• A free tier covers up to 1,500 subscribers, with monthly paid tiers as the audience grows.

Cons

• The API cannot collect text items or publish issues, leaving gaps for fully automated editorial pipelines.
• Monthly message quota is capped at 31 times the tier's maximum subscriber count, and unused messages expire rather than roll over.
• Monthly costs rise across subscriber bands, reaching custom pricing above 50,000 subscribers.

Alternatives

Newsletter Platforms is a useful starting point for comparing the category. Consider listmonk instead if free, open-source software and self-hosting matter more than Curated's integrated editorial workflow; listmonk requires a PostgreSQL database. Audienceful is another freemium email option, with a free tier for 1,000 contacts, one team collaborator, and one automated journey. Email Fast has a free plan with 2,500 emails per month and unlimited contacts and subscribers, which may suit readers prioritizing send volume over link curation.

LetterBucket offers a free plan for up to 1,000 subscribers and unlimited posts. phpList has a Forever Free plan with 300 messages and unlimited subscribers, a different trade-off for publishers whose list size matters more than monthly message volume. SendFox has a free plan for 1,000 contacts and 3,000 monthly sends. Stibee is a freemium alternative with Korean-won pricing. beehiiv has a free Launch plan for up to 2,500 subscribers, unlimited email sends, one team member, and three publications.

Verdict

Choose Curated if your publication depends on selecting links, adding editorial context, and managing newsletter revenue in one place. The integrated curation and sponsorship tools are its clearest reason to choose it. Look elsewhere if API-based issue publishing is essential or if subscriber-tier charges and a non-rolling message quota make your sending needs hard to manage.