Skip to content

Loops alternatives

12 tools that do a similar job, and what makes each one different.

What Loops is

Loops is email software aimed at SaaS teams, covering marketing, product and transactional email in one product rather than splitting them across separate tools. Emails are assembled from themes and reusable components so designs stay consistent across sends, and workflows are built from triggers, branching logic and audience filters. The free plan allows up to 1,000 subscribed contacts and 4,000 sends a month, includes unlimited team seats with no per-seat charge, and adds a Loops footer credit to every email. Paid plans put no cap on the total number of emails a team can send, and Loops charges no separate fee for those sends. Throughput differs too: free accounts are capped at 10 emails per second and paid teams at 1,000, and anything submitted above the per-second limit is queued rather than rejected. Transactional templates can be built in the visual editor or imported as MJML code, though the data variables passed into them accept only string or number values. A transactional email has to be published and its sending domain verified before the API will send it, which is the usual first thing to trip over when wiring up a new project. The API lives at app.loops.so/api and authenticates with a bearer token generated in dashboard settings. Standard endpoints allow 10 requests per second per team, while the content endpoints covering campaigns, components, email messages, themes, transactional emails, uploads and workflows are limited to 60 requests per 60 seconds per team. Requests over the limit return HTTP 429, with response headers reporting the limit and how much of it remains. Each value in a request body is capped at 500 characters including quotes. Loops publishes an OpenAPI specification in both YAML and JSON, official SDKs for Go, JavaScript, PHP, Ruby and Nuxt, and a CLI that installs by curl script or Homebrew tap and reads its API key from the LOOPS_API_KEY environment variable for use in CI. Setting up sending requires SPF, DKIM, MX and CNAME records supplied by Loops, and the recommendation is to send from a subdomain rather than the root domain. Free platform subdomains from Vercel, Netlify or Shopify cannot be used as a sending domain, which rules out the quickest route for a project still hosted on default infrastructure. Prebuilt integrations cover Stripe, Supabase, Clerk, Zapier, Make, Segment, Webflow, Bubble, PostHog, Auth0 and Framer. The Stripe integration accepts 21 event types spanning customers, subscriptions, invoices, checkout sessions, disputes and quotes, and ignores any event that arrives without an email address on it.

Transactional email designed for developers. Templates are React components, the API is small enough to learn in a sitting, and webhooks report delivery, opens and bounces. Deliverability tooling (domain authentication, dedicated IPs, suppression handling) is the part that actually determines whether the mail arrives, and it is taken seriously here.

Freemium

A newsletter platform built by people who grew one, with the growth side treated as a first-class feature rather than an add-on: referral programmes, recommendation networks, an ad marketplace and paid subscriptions. Deliverability and segmentation are solid. Most useful for a newsletter that is the business rather than a channel for one.

Freemium

Queue social posts once and let them publish on a schedule across the networks you use. Deliberately narrow (scheduling, a shared calendar, straightforward analytics and an engagement inbox), which is why small teams pick it over suites that do ten other things. The free plan covers one person managing a few accounts.

Freemium

Marketing, sales and support working from one contact record, which is the whole argument for it: no syncing between three systems that disagree. Email, landing pages, forms, pipelines, ticketing and reporting are included. The free CRM is real and widely used; costs climb steeply as contact counts and add-ons grow, and that is the thing to model before committing.

Freemium

Email campaigns and automations for lists that have outgrown a spreadsheet. Templates, segmentation, A/B testing and reporting are the core; landing pages and basic CRM sit around them. Long the default first choice for small businesses. Pricing scales with contacts including unsubscribed ones, which is the detail that surprises people at renewal.

Freemium

Free to use, where Loops is paid

Open source

A merchant of record for digital products, which means sales tax and VAT stop being your problem. They handle registration, collection and remittance globally. Checkout, subscriptions, licence keys and affiliate tooling are included. Fees are higher than a raw payment processor, and that difference buys you not running a tax compliance function.

Paid

Deploys a frontend by pushing to a branch, with a preview URL for every pull request, the workflow most React teams now expect by default. Built by the maintainers of Next.js, which it supports first and best. Edge functions, analytics and image optimisation are included. Costs are predictable until traffic is not, and bandwidth is the line to watch.

Freemium

A CRM that models your pipeline instead of making you adopt theirs. Objects, attributes and relationships are defined by you, and it builds from real data, email and calendar activity populate records rather than waiting for someone to log them. Aimed at startups and investment teams whose process does not fit a standard sales funnel.

Freemium

Managed vector search, so retrieval stops being an operational problem. You upsert embeddings with metadata and query by similarity with filters, and the indexing, sharding and scaling are handled. Serverless indexes bill on usage rather than provisioned pods. The decision is nearly always this against pgvector: a managed service that scales, or one less system to run.

Freemium

Runs open-source models behind an HTTP API so you never provision a GPU. Push a model with Cog and it becomes an endpoint; pull someone else's and it is one call. Billing is per second of compute, which suits bursty work and gets expensive under sustained load, at which point self-hosting is the comparison to make.

Paid

Workflows where every step can just be code. Connect a trigger, then write Node, Python, Go or Bash with managed authentication for the services you call, no credential handling of your own. Pre-built components cover the common cases. Suits developers who want the plumbing solved and the logic left alone.

Freemium