All alternatives guides

Expensive at scale, data ownership concerns, block editor lock-in, AI features paywalled at higher tiers.

Task-based pricing punishes high-volume workflows, data leaves your infra, limited custom code, latency on premium features.

Free tier severely cut to 1 device and 50 notes, price increase, data ownership concerns, performance issues.

Pricing jumped significantly, limited free tier (2 GB), privacy concerns with cloud storage, expensive for teams.

Data privacy concerns, Google account dependency, 15 GB free limit, no end-to-end encryption by default.

Key features like reminders paywalled, no self-hosting, data not fully exportable, vendor lock-in.

Owned by Atlassian, free tier limited to 10 boards, power-ups paywalled, privacy concerns.

Expensive at team scale, free tier limited to 3 boards, data ownership, offline access limited.

Subscription-only (dropped one-time purchase), cloud-only vault, cost for families/teams, trust in closed-source.

Major security breaches (2022), free tier restricted to one device type, closed source, trust damaged.

Expensive ($30/mo), invite-only historically, no self-hosting, closed source, works only on top of Gmail/Outlook.

Per-seat pricing scales badly, message history caps on free tier, data sovereignty concerns, vendor lock-in.

Data privacy, cost at scale, model choice, offline capability, custom model fine-tuning.

GDPR/privacy concerns, GA4 UX complaints, cookie banner overhead, data ownership.

Expensive, per-envelope pricing adds up, vendor lock-in, overkill for basic signing needs.

Row limits, expensive scaling, data lock-in, no self-host option.

Very expensive at scale, MTU-based pricing, data warehouse coupling issues.

Per-seat pricing, no self-host, want data ownership, no free tier for teams >10.

The 3-seat minimum plus per-seat billing means small teams pay for capacity they do not use, and the features that justify the tool (automations, timeline views, dashboards) are metered or reserved for higher tiers. Automation and AI credit caps create surprise costs mid-month.

Per-seat cost applies to every collaborator including occasional participants, so the bill scales with headcount rather than usage. Reporting, portfolios, and workload views sit above the Starter tier, so the plan most teams buy is not the one that answers management's questions.

Content gets locked into Atlassian's storage format and macro ecosystem, so exports lose structure and migration is a project rather than a task. Search and page organization degrade badly at scale, and cost compounds because Confluence is rarely bought alone.

Pageview-based tiers mean a traffic spike bumps you up a bracket, and the cheapest tier caps you at one site with team features gated to Growth and Business. Note this is not a third-party swap: Plausible is open source (AGPL) and the self-hosted Community Edition is the same product you run on your own server for the cost of hosting, trading the subscription for maintaining it yourself.

Subscription is pageview-metered with no free tier, so low-traffic and hobby sites pay from day one, and costs step up sharply past 500k pageviews. Fathom's own tracker is closed source (only Fathom Lite, a discontinued predecessor, was open), so unlike Plausible there is no first-party self-host path and moving means switching to a third-party OSS tracker.

Issues is deliberately thin for planning work: no native sprints, estimates, or roadmap rollups, so teams outgrow it and end up paying per seat for a tracker they still supplement with something else. Your planning data is also locked to the same vendor as your code hosting.

Metered bandwidth and function overages turn a $20 bill into a surprise invoice under traffic spikes, the Hobby tier bars commercial use, and the platform is tightly coupled to Next.js deployment conventions.

The credit-based metering makes costs hard to forecast, build minutes and bandwidth overages add up on busy sites, and moving off means rebuilding the serverless function and edge glue you built against Netlify's APIs.

Business is over 2x Team per seat and the features that force the upgrade are governance basics like admin controls and SSO, so cost scales with headcount rather than usage, and there is still no self-host option for data residency.

Adobe acquisition concerns, expensive team plans, data lock-in.

Privacy concerns, meeting time limits on free tier, want self-host for compliance.

Billing is tied to contact count rather than sends, so a list that grows without sending more email still costs more every month. Contacts who unsubscribed can still count toward the tier, and audience/automation limits on cheaper plans push upgrades.

Designs are locked in a proprietary format with no meaningful export path for editable source files, so leaving means rebuilding assets. Premium stock elements are licensed only while you keep paying, which means past designs can become unusable if you downgrade.

Configuration complexity means workflows, permission schemes, and custom fields accumulate into something only an admin can change, which is its own form of lock-in. Performance degrades on large instances, and the seat count that drives the bill includes stakeholders who only read tickets.

Event-volume billing makes the bill unpredictable once you instrument more of the product, and the useful controls (SSO, project permissions, advanced exploration) sit behind quote-only Growth. All behavioural data lives on Amplitude's infra with no self-host option.

Event-volume pricing gets unpredictable as you instrument more, and hitting the free 1M event cap locks you out of your own reports until the month resets. Data lives entirely on Mixpanel's infra with no self-host path.

Per-host pricing multiplies fast across environments, and each capability (APM, profiling, security, network) is a separate per-host charge on top of infrastructure. Custom metric and container allotments mean overage bills show up without a config change.

Session-based caps mean a traffic spike silently stops recording, and the three products (Observe, Ask, Engage) are priced separately so a full setup costs well over the headline number. Session recordings of real users sit on a third-party platform, which is a GDPR review every time.

Two separate per-person meters (builders and internal users) mean cost scales with everyone who merely opens an app, not just the people building. Workflow runs are metered on top, and your admin panels sit on a vendor platform with direct credentials into production databases.

Subscriber-tier pricing climbs steeply as the list grows even when send volume does not, and the audience, website, and monetization stack all live inside one hosted platform you cannot export wholesale.

Subscriber-count pricing compounds and just jumped 34% in one move, and the list plus automations sit on a platform whose export does not carry the sequences with it.

Cheap at the entry tier but the subscriber ladder gets expensive fast, and deliverability plus automation limits are set by the vendor rather than by you.

Seat pricing is only the floor: AI outcome charges and add-ons routinely multiply the real bill, and conversation history plus help centre content end up locked in a vendor whose pricing model has changed repeatedly.

Pricing is quote-only with annual contracts and steep minimums, and the Salesloft acquisition folded Drift into a larger revenue suite so standalone chat buyers now pay for a platform they may not need.

The gap between Starter and Professional is a 40x price jump, and the features most teams actually want (automation, reporting, custom workflows) sit above that line. Contact data and email history live in HubSpot's schema, which makes migrating out expensive once it is the system of record.

Per-seat pricing adds up fast for teams where scheduling is incidental to the job, and the free tier's single-event-type cap makes it unusable for anyone with more than one meeting format. Booking data and invitee details sit on Calendly's servers, which is a problem for regulated industries.

Response caps are the real pricing lever, so a single successful campaign can blow through the tier and force an upgrade mid-month. At $39/mo for the entry plan it is expensive relative to how often most teams actually collect forms, and survey responses containing PII sit with a third party.

$29 per user/month billed annually is a real jump from Free, and compute minutes, storage and AI credits are metered on top of the seat. Guest users are limited on Premium, so inviting stakeholders costs seats. GitLab is open-core: the self-managed Community Edition covers most of this for hosting cost, which is the usual escape route rather than a third-party tool.

The 10% cut is permanent and scales with your success, so a mature paid list pays far more than any flat-fee host, and the platform owns the discovery, network, and reader relationship.

The free tier's 5-minute recording limit and 25-video cap make it a trial rather than a usable plan, so most real usage lands on per-seat billing. Videos are hosted on Loom's infrastructure, so recordings containing customer data or internal systems leave your control, and cancelling risks orphaning links already embedded in docs and tickets.

Error-volume billing means a bad deploy or a noisy loop turns into a bill, and the separate meters for logs, replays and monitors make the real cost hard to predict. Sentry is open-core with a self-hosted distribution, so teams wanting data residency or a fixed server cost often move to running it themselves.

You are paying a hosting premium for software that is open source and self-hostable, and the member-count ladder plus staff-seat caps push you up tiers for reasons unrelated to actual traffic.

Per-channel pricing multiplies quickly once you run several brands or platforms, and your entire posting queue plus analytics history lives in a third-party account tied to fragile platform API access.

Starting at $99 per seat per month makes a small team cost more than most of their other tooling combined, and the pricing is now bundled with AI and listening modules many buyers never use.

Volume-tier pricing plus paid add-ons for dedicated IPs and validation adds up, and deliverability reputation is shared infrastructure you do not control.

Per-message costs are invisible until volume arrives and then dominate the bill, and carrier surcharges plus 10DLC registration make the effective rate hard to forecast.

Per-seat cost multiplies fast and the jump from Starter Suite to Pro Suite is 4x for features most teams hit within a year, plus API access and real customization sit behind Enterprise pricing.

Real costs compound because site plans, Workspace seats, and per-feature add-ons are billed separately, and the visual builder produces markup you cannot self-host or move off Webflow's hosting.

Credit-metered AI and per-editor seat charges push the real bill well past the headline price, and sites are locked to Framer hosting with no export path to your own infrastructure.

Usage-based billing across compute, storage, backup, and data transfer makes the monthly total hard to predict, and dedicated clusters jump to roughly $57/mo minimum the moment you need production isolation.

The gap between Essentials and Pro is severe — Pro carries a $200/month minimum — and Redis relicensed away from open source in 2024, which pushed many teams to look at forks or self-hosting.

Weak fit for the swaptosaas B2B thesis: Nitro is a per-user consumer cosmetic subscription (custom emoji, bigger uploads, HD streaming), not a business tool, so there is no seat-cost or data-sovereignty pain driving a self-hosting decision. Teams evaluating Discord for work are really comparing the platform, not Nitro.