Most “make money online” guides sell a dream. Site to Income gives you a system: 30 practical steps from choosing a niche to running a website with several income streams, with a checklist, template or worksheet at the end of every chapter.
What the ebook covers
Foundation (Steps 1-5): choosing your income model, picking and validating a niche, planning your monetization mix, business basics and budget.
Traffic (Steps 13-19): keyword research, content that ranks and gets cited in AI search, on-page SEO, responsible AI use, links, social channels and email.
Monetize (Steps 20-26): AdSense and display ads, affiliate marketing with proper disclosure, sponsorships, digital products, services, memberships, pricing and funnels.
Scale (Steps 27-30): measuring and optimizing, automation, taxes and compliance, and your 90-day action plan.
Who it is for
Beginners who want to start a website that earns, and bloggers whose site does not earn yet. It is written in plain English, with worked examples, step-by-step walkthroughs and an appendix of official resources.
What you get
Instant PDF download
30 chapters with checklists, templates and worksheets
Resource list with links to official documentation
It is a PDF you can download instantly after purchase and read on any phone, tablet or computer.
Do I need technical skills?
No. The guide is written for beginners in plain English, with step-by-step walkthroughs for setting up a WordPress site.
Which ways of earning from a website does it cover?
Display ads such as AdSense, affiliate marketing with proper disclosure, sponsorships, digital products, services and memberships.
Does it promise a specific income?
No. The ebook is for education only and guarantees no income. Results depend on your effort, niche and many other factors.
Earnings disclaimer: this ebook is for education only and does not promise or guarantee any income. Results depend on your effort, niche and many factors outside anyone’s control. It is not legal, tax or financial advice.
A roadmap is a strategic plan that defines a goal or desired outcome and includes the major steps or milestones needed to reach it. It also serves as a communication tool, a high-level document that helps articulate strategic thinking—the why—behind both the goal and the plan for getting there.
A business roadmap is a visual representation of your business strategy. It outlines the steps, goals, initiatives, and milestones needed to achieve your long-term plans. A business roadmap is also more tactical, focusing on how you will reach your objectives.
Eight Bukets – Challenge
Six – Create Value – Capture Value
I’m giving you the map, now you must walk the path
This article breaks down everything you need to know about uncut diamonds and how you can make a smart investment.
Filling in some gaps in your jewellery knowledge or trying to discover some untold secrets in the jewellery business? Uncut diamonds are not something that are often talked about. This article breaks down everything you need to know about uncut diamonds and how you can make a smart investment when picking out gorgeous stone jewellery.
Uncut Diamond Jewellery explained?
An uncut diamond, as suggested by the name, is a diamond in its most natural form. Prior to any shaping to enhance proportion, symmetry and polish involved in diamond cutting, an uncut diamond is a raw diamond that is completely virgin and free from human manipulation.
What is an uncut Diamond worth and why are Diamonds cut?
Apart from their quirky edge, there is not a whole lot of value in purchasing raw diamonds. Uncut diamonds are typically worth less than traditionally cut diamonds as their unpolished, rough edges hinder how well light is refracted. This reduces their sparkle and brilliance, thus reducing their market value.
What does a raw uncut Diamond look like?
An uncut diamond is often bumpy and dull with no real structure. An acquired taste, uncut diamond rings provide a uniqueness and level of beauty some like to hold with others even looking for a rough diamond ring to mark their love.
Diamond Cut Breakdown
To create beautiful diamonds that are worth thousands, diamond cutters have the difficult job of trying to create finished products which align in proportion, symmetry and polish. Make no mistake, while this is easy to decide in theory, cutting diamonds is a challenge where compromises often have to be made. Compromising factors such as diamond weight, to create the right proportions and symmetry, or proportions and symmetry to avoid cutting further diamond and reducing weight.
In a similar way to natural diamonds, poorly cut diamonds can also refract light badly, resulting in little to no sparkle and less spread for your carat weight. To identify how you can be savvy and well informed when choosing your own diamond jewellery, here is everything you need to know about cuts.
Developed in the 1940’s to 1950’s by the Gemological Institute of America (GIA), cut grades were developed to allow independent labs to identify a diamond’s clarity, colour and structure. A prime example of a predetermined cut grade is a brilliant cut diamond which will have 57 or 58 facets accurately cut and defined. While miniature, this provides a system to govern how well a diamond will sparkle.
While they offer a significant discount in price, poorly cut diamonds lack luster and you will be paying for a diamond without any sparkle. To ensure that you have an effective diamond that is worthwhile, we always suggest purchasing a diamond with an “excellent” to “good” cut. However, if you are still interested in purchasing a diamond of a lower cut, we suggest taking a look in person under various lighting conditions to avoid any disappointment.
Website, other related websites and blogs created as a scratch base pilot project for merging and evolving to something better and highly valuable.
Headcount planning and workforce analytics sit apart from both core HRIS (which stores employee records) and performance management (which tracks individual goals and reviews). This category answers a different question for finance and HR leaders: how many people, in which roles, at what cost, do we need next quarter and next year — and what’s actually happening across the workforce right now that should change that plan? This guide compares three platforms built for that job: Visier, a dedicated people-analytics and workforce-planning platform; ChartHop, an org-chart-centered people platform with a headcount planning module; and Workday Adaptive Planning (recently rebranded “Adaptive from Workday”), the planning product Workday sells alongside, but separately from, its core HCM suite.
At a Glance
Tool
Best For
Pricing Model
Starting Price
Key Strength
Visier
Large, complex organizations wanting deep workforce analytics plus planning, not planning alone
Quote-based
Not published
2,000+ prebuilt metrics and large benchmark datasets across 11 HR domains
ChartHop
Companies wanting headcount planning tied visually to a live, always-current org chart
Modular, quote-based
Not published
Headcount planning as one module on top of an org-design-first platform
Workday Adaptive Planning
Finance and HR teams wanting headcount planning driven directly through P&L financial models
Quote-based
Not published; free trial available
Driver-based planning that links headcount changes straight to financial outcomes
Short Verdict
None of these three publish pricing — this is a sales-quote category across the board, typically priced by employee count and module selection. Visier is the strongest choice when workforce analytics (understanding attrition, skills gaps, org structure today) matters as much as forward planning; it’s built analytics-first with planning as one module among several. ChartHop is the better fit when the org chart itself — who reports to whom, right now — is the thing the whole company looks at, with headcount planning as one of several add-on modules layered on top. Workday Adaptive Planning is the natural pick when finance, not HR, is driving the headcount conversation and wants staffing changes to flow directly into budget and P&L models, especially at organizations already in the Workday ecosystem.
Visier: Workforce Analytics First, Planning Built On Top
Visier — marketed as “Visier Workforce AI” — is structured around a few core capabilities: Workforce Insights, which unifies data across teams, systems, and time periods into a single current view of the workforce; Workforce Planning & Org Design, which lets HR and Finance model future headcount and org structure off that same underlying data rather than a separate spreadsheet; and Talent Agents (formerly Workforce Activation), which push recommended actions to managers directly in their workflow and track whether those actions actually changed outcomes. An AI agent called Vee surfaces insights proactively, and the platform supports both Visier-built and bring-your-own agents, the latter connecting through a “Visier MCP” integration layer. Visier backs this with scale claims of 2,000+ prebuilt metrics across 11 HR domains, more than 250 million HR benchmark data points, and over 2 billion compensation benchmark points, plus 20+ prebuilt connectors into existing HR systems and data warehouses.
Visier’s site gives no pricing information anywhere — the only actions available are “Book a Demo” and “Contact Sales.” The company cites more than 85,000 organizations as customers and markets toward data & AI teams, HR leaders, talent management, and workforce planners at organizations dealing with org redesign, skills gaps, attrition risk, and total workforce cost — language that points toward larger, more complex organizations rather than small businesses.
Pros: Deepest analytics layer of the three, with planning grounded in the same unified data rather than a separate import; large prebuilt metric and benchmark library reduces custom reporting work; agent/MCP architecture for connecting third-party AI tools to governed workforce data.
Cons: No pricing information published at all; positioning and feature depth suggest it’s overbuilt (and likely overpriced) for smaller companies that just need basic headcount planning; sits on top of existing HR systems rather than replacing them, so it’s an additional platform to integrate and pay for.
ChartHop: Headcount Planning as a Module on an Org-Chart Platform
ChartHop’s core identity is the live org chart — a continuously updated visualization of the company’s structure — and it sells headcount planning as one of several modules that attach to that core: others include AI Pro, Performance, Goals, Compensation Reviews, Engagement, and HRIS functionality, plus connections to more than 100 external systems. ChartHop explicitly markets its packaging as modular and “right-sized” rather than fixed tiers: prospective buyers answer a short questionnaire (including total headcount, “including contractors”) and receive a proposal built around which modules they actually need, with the company saying it responds to these requests within one business day.
ChartHop’s pricing page lists no dollar amounts, no named pricing tiers like “Starter” or “Enterprise,” and no minimum company size. Everything funnels into either a demo booking or the sizing questionnaire, consistent with a fully custom, quote-based sales process.
Pros: Headcount planning is visually and operationally tied to the actual org chart rather than a disconnected spreadsheet or model; modular packaging means (in theory) you pay only for the modules you select; broad integration footprint (100+ systems).
Cons: No public pricing at any level, not even a ballpark or entry tier; “modular, right-sized” pricing is harder to comparison-shop than a fixed tier structure, since the final package depends on a sales conversation rather than a published menu.
Workday Adaptive Planning: Headcount Through a Financial-Planning Lens
Workday Adaptive Planning (branded as “Adaptive from Workday” in product navigation) is filed under Workday’s Financial Planning & Analysis products, not its HCM suite, and that positioning shows in how it approaches headcount: workforce planning here is one of several planning disciplines (alongside financial and sales planning) and is built to be driver-based, meaning a change in headcount assumptions flows straight through to budget and P&L outcomes rather than living in an isolated HR plan. Its Workforce Planning capability covers staff and headcount modeling inclusive of salary, benefits, and tax costs; resource planning for skills-gap analysis and utilization by project, role, or region; labor management tracking productive versus idle hours; and what-if scenario modeling with predictive forecasting based on historical trends. An AI layer called Decision Intelligence adds a conversational assistant aimed at variance analysis. Workday markets this broadly across finance, HR, and operations teams, citing more than 7,000 customers across industries including financial services, healthcare, higher education, and government.
Workday does not publish pricing for Adaptive Planning; the only actions on its product pages are “Request a Demo” and a free-trial signup. We could not confirm from Workday’s own pages exactly how (or whether) Adaptive Planning natively integrates with Workday’s separate HCM product beyond general statements that it can connect to HR and payroll systems and pull in data automatically — organizations evaluating this for a Workday-HCM-plus-Adaptive-Planning setup specifically should confirm the integration depth directly with Workday rather than assume it’s seamless because both carry the Workday name.
Pros: Driver-based planning ties headcount decisions directly to financial outcomes, which is useful when finance leads the planning process; strong scenario/what-if modeling and predictive forecasting; free trial available, unusual in this category.
Cons: No published pricing; positioned and sold as an FP&A tool first, so HR-specific workforce features (skills intelligence, org design) are shallower than Visier’s or ChartHop’s; native integration depth with Workday’s own HCM product isn’t clearly documented on Workday’s public pages.
Bottom Line
All three vendors require a sales conversation for pricing, so the decision here comes down to which discipline should own the headcount plan. If HR and workforce analytics should drive it, with planning as an extension of understanding the current workforce, Visier’s depth of metrics and benchmarks makes it the strongest analytics-led option. If the org chart is the operational center of gravity for the company and headcount planning should be visually and structurally tied to it, ChartHop’s modular, org-chart-first approach fits better — and its questionnaire-based quoting process is at least faster to start than a cold demo request. If finance owns the plan and headcount needs to flow directly into budgets and P&L scenarios, Workday Adaptive Planning’s driver-based model is purpose-built for that, with the caveat that its connection to Workday’s own HCM data isn’t something we could verify as seamless from public documentation alone.
FAQ
Is Workday Adaptive Planning the same as Workday HCM? No. Adaptive Planning is a separate financial-planning product, filed under Workday’s FP&A line (now also referred to as “Adaptive from Workday”), with its own product login. Workday’s HCM and Workforce Management products are listed separately on Workday’s site, and we could not confirm the exact native integration depth between them from public pages.
Do any of these tools replace an HRIS? No. Visier and ChartHop both explicitly sit on top of existing HR systems (Visier cites 20+ connectors; ChartHop cites 100+ system connections) rather than replacing core employee-record systems. Workday Adaptive Planning connects to HR/payroll data sources as inputs to its financial models.
Which of these three has a free trial? Workday Adaptive Planning offers a free trial, per its own product page. Visier and ChartHop do not advertise self-serve free trials; both route to a demo request or sizing questionnaire.
Is pricing available anywhere for these products? Not publicly, for any of the three. All require a sales conversation, and pricing is reported elsewhere (third-party buyer guides, not these vendors’ own sites) to generally scale with employee headcount and module selection.
Two quick corrections before the comparison, both the result of checking primary sources rather than trusting old brand names. First, Clay.earth now redirects to me.sh — Clay rebranded to Mesh, confirmed by a Product Hunt post titled “Clay is now Mesh.” Second, Signal AI is not a people-briefing tool at all — it’s a media and risk-intelligence platform that monitors news coverage and reputational/regulatory risk for organizations, with no person-profiling or pre-meeting prep feature anywhere on its site. We’ve substituted Humantic AI, which is actually built for prepping on a specific person before a call. Here’s how Mesh, Dex, and Humantic AI compare for getting context on people before you talk to them.
At a Glance
Tool
What It Is
Best For
Starting Price
Mesh (formerly Clay)
AI-powered personal CRM / rolodex
Keeping ongoing context on your whole personal & professional network
Free (1,000 contacts); Pro $10/mo
Dex
Personal CRM with reminders & AI-assistant access
Relationship follow-up and light meeting context via notes/history
Premium $12/mo; Professional $20/mo
Humantic AI
Buyer/stakeholder personality & account intelligence for sales calls
Sales reps prepping for a call with a specific prospect or buying committee
Free report per lookup; paid plans not publicly listed
Short Verdict
These tools answer different versions of “who am I about to talk to.” Mesh and Dex are both personal CRMs — they store what you already know about someone (how you met, their job, their family, past conversations) and remind you of it before you reconnect, which is a form of meeting prep but built around your own notes rather than fresh research. Humantic AI does something closer to what “AI meeting briefing” usually implies in a sales context: it actively researches a person’s public footprint and personality signals, plus the target account, and hands you a profile you didn’t have to write yourself. If you need relationship memory, pick Mesh or Dex. If you need fresh intelligence on someone you’ve never met, Humantic AI is the better fit.
Mesh (Formerly Clay): A Rolodex That Builds Itself
Mesh — the product previously known as Clay, now living at me.sh — bills itself as a “beautiful rolodex and CRM” for iPhone, Mac, Windows, and web that assembles itself automatically from your emails, meetings, and connected accounts (LinkedIn, Facebook, Instagram, Notion, WhatsApp, and X among them). Instead of manually logging every contact, Mesh pulls in updates on job changes, birthdays, and news mentions, and surfaces a feed of relevant moments to reconnect on. An AI assistant called “Nexus” sits on top of your contact data to help you make use of it, and a Teams tier adds visibility into who-knows-whom across a company for warm-introduction hunting.
Pricing runs four tiers: Personal is free (a card is required) and covers up to 1,000 contacts with core search, groups, reminders, and life-update alerts. Pro is $10/month and adds unlimited contacts, CSV/spreadsheet import, and more frequent data refreshes, with a 14-day free trial. Team runs $40 per seat/month for up to four members, advanced enrichment, and admin controls. Enterprise is custom-quoted and adds SOC 2 Type II certification, SAML SSO, and a dedicated success manager.
Pros
Genuinely automatic contact-building from accounts you already use
Usable free tier up to 1,000 contacts, which covers most people’s real network
Team tier adds warm-introduction discovery, useful before a cold outreach or meeting
Cons
Recent rebrand from Clay to Mesh means older reviews/links may be stale or confusing
Built around people already in your network, not for researching a stranger before a first call
Annual pricing isn’t shown despite discount labels referencing it
Dex: Reminders and Notes, With AI Assistant Access
Dex is also a personal CRM, with a similar pitch to Mesh but a slightly different center of gravity: reminders and follow-up workflows. It syncs contacts from LinkedIn and other sources (auto-updating job titles), and lets you log how you met someone, their education and work history, important dates, family details, gift ideas, and event history. It nudges you to reach out when a connection changes jobs, and integrates with Gmail, Outlook, Google Calendar, LinkedIn, Facebook, Instagram, WhatsApp, and Zapier. Its most relevant feature for this comparison is MCP-based AI assistant access — you can connect Claude, ChatGPT, Gemini, or other MCP-compatible tools directly to your Dex data, letting an AI assistant read your notes and follow-ups on someone ahead of a conversation. Dex’s own marketing doesn’t explicitly promise an automated “pre-meeting brief,” but the underlying pieces (notes, calendar sync, AI access) support building one yourself.
Pricing is tiered at Premium ($12/month), Professional ($20/month), and Team ($40 per user/month), with discounts available for annual (40% off) and quarterly (20% off) billing.
Pros
MCP integration lets your own AI assistant (Claude, ChatGPT, etc.) draw directly on your relationship notes
Strong follow-up nudging tied to job-change detection
Privacy-forward positioning — subscription-funded, not ad-funded, with data export/delete options
Cons
No built-in, automatic “briefing” feature — you have to assemble context yourself or via a connected AI tool
Three paid tiers with no free plan mentioned on the pricing page
Like Mesh, it’s for people already in your orbit, not cold research on a stranger
Humantic AI: Actual Pre-Call Research on People You Don’t Know Yet
Humantic AI is the one tool in this comparison built specifically around researching someone you’re about to talk to for the first time, mainly in a B2B sales context. Its “Agent Pi” (People Intelligence) builds a profile of a stakeholder — DISC personality type, media appearances, hobbies, interests — and maps the full buying committee on complex deals. A companion “Agent Miia” (Account Intelligence) researches the target company itself: competitors, org chart, budget signals, tech stack, and buying intent. Used together, Miia explains why an account might be in-market, and Pi tells you how to approach the individual humans inside it. A third feature, HumanMail, uses the DISC profile to draft outreach emails matched to the recipient’s communication style.
You can generate a free report by pasting a LinkedIn URL, a work email, or naming two companies, and the tool is available as a web app plus Chrome, Edge, Firefox, and Outlook extensions. Pricing isn’t published for the core People/Account Intelligence product — Humantic AI’s site only lists a price for a separate add-on (Vidar, a visitor-identification tool, at $0.18 per identification); the main product requires a free trial or sales conversation to get plan pricing.
Pros
Actually built for the “I’ve never met this person, brief me before the call” use case
Combines individual personality insight with account-level business context in one workflow
Free single-report lookups let you test quality before committing to a plan
Cons
No published pricing for the core product — budgeting requires a sales conversation
Personality inference (DISC typing) from public data has inherent accuracy limits worth treating skeptically
Narrower focus than Mesh/Dex — it’s not a general relationship-management tool, just pre-call intelligence
Bottom Line
Match the tool to whether you already know the person. For your existing network — clients, old colleagues, investors, friends-of-friends — Mesh‘s free tier or Dex‘s reminder-driven workflow will do the job of surfacing what you already know before you reconnect; choose Mesh if you want more automatic data-pulling for free, Dex if you want deeper AI-assistant integration via MCP. For a prospect or stakeholder you’ve genuinely never spoken to, Humantic AI is the only one of the three built to generate a cold-start briefing from scratch. None of these should be confused with media-monitoring tools like Signal AI, which solve an entirely different problem — tracking what’s being said about your company, not prepping you for a conversation with a person.
FAQ
Is Clay (clay.earth) still a separate product from Mesh? No. Clay rebranded to Mesh; clay.earth now redirects to me.sh, and the companies describe it as the same product under a new name.
Why isn’t Signal AI on this list? Signal AI is a media and risk-intelligence platform for organizations — it monitors news coverage, reputation, and regulatory/geopolitical risk. It has no feature for researching or briefing on an individual person before a meeting, so it doesn’t fit this comparison.
Can Dex or Mesh research someone I’ve never met? Not really — both are built to organize and remind you about people already in your network (contacts, past meetings, connected accounts). For cold research on a stranger, a tool like Humantic AI is closer to what you need.
How accurate is DISC-style personality profiling from public data? Treat it as a directional signal, not a certainty. These profiles are inferred from public footprints (social posts, media mentions) rather than validated assessments, so they’re best used as a conversation-starting hint, not a definitive read on someone’s personality.
Compensation and benefits management software exists to answer a narrower, harder question than general HR software does: is this specific offer, raise, or equity grant fair, competitive, and inside budget — and can you defend that answer in an audit or a pay-equity review? This guide compares three tools built for that job: Pave, a real-time compensation benchmarking and planning platform; Carta Total Compensation, a benchmarking and equity-planning add-on from the cap-table company Carta; and PayScale (now marketed under the Payscale Intelligence Cloud), a longer-established compensation data and pay-decision platform.
A pattern worth flagging up front: none of these three vendors publish real prices for their paid tiers. Comp-management software is sold almost entirely through sales-led, quote-based contracts, typically priced by employee count and data coverage. Where that’s the case below, we say so plainly rather than guessing at numbers.
At a Glance
Tool
Best For
Pricing Model
Starting Price
Key Strength
Pave
Companies wanting real-time market data plus AI-driven comp analysis and workflow automation
Free entry tier + quote-based paid tiers
Free (Market Data Lite); paid tiers quote-only
Live benchmarking data from 9,000+ participating companies and agentic comp workflows
Carta Total Compensation
Startups and private companies, especially existing Carta cap-table customers, managing equity + salary together
Quote-based
Not published
Equity-specific benchmarking and over-allocation/dilution risk tools
PayScale (Payscale Intelligence Cloud)
Mid-size to large employers needing full pay-equity analysis, job architecture, and merit-cycle planning
Quote-based
Not published
Breadth across benchmarking, job architecture, pay equity, and merit planning
Short Verdict
Pave is the only one of the three you can start using today without a sales call, thanks to its free Market Data Lite tier — though anything beyond basic benchmarking (custom peer groups, global data, AI workflows) moves to a quote. Carta Total Compensation makes the most sense if equity compensation, not just cash, is central to your comp strategy and you’re already (or considering becoming) a Carta cap-table customer. PayScale is the deepest platform for compensation teams that also need job architecture and formal pay-equity analysis, not just market pricing — but like the other two, getting an actual number requires talking to sales.
Pave: Free Benchmarking, Paid Agentic Workflows
Pave’s pricing page is unusually structured in tiers of capability rather than company size. Market Data Lite is free and includes real-time salary and equity benchmarks sourced from over 9,000 participating companies, automated data collection, AI-assisted job matching across 290+ job families, and coverage of the U.S. plus one additional market of the buyer’s choice. Market Data Pro is quote-only and adds custom peer groups, global benchmarking and geo pay differentials across 60+ countries and 90+ metro areas, a “recent hire” filter, advanced equity data, and unlimited exports/custom reports. The top two tiers, Agentic Market Intelligence and Agentic Workflows, layer in an AI analyst for workforce metrics, job-architecture building, automated job pricing, MCP-based access to Pave data inside other AI tools, and — at the top tier — use of Pave as a comp data warehouse with a “Pave Agent” for complex workflows. Separately priced add-ons at the top tier include Compensation Planning, Team View, a Total Rewards portal for employees, and a Visual Offer Letter tool for candidates.
Pave does not publish dollar figures for Market Data Pro, Agentic Market Intelligence, Agentic Workflows, or any of the add-ons — all require “Request a Quote.” The company’s marketing cites more than 9,000 integrated client companies, including large, well-known names, but doesn’t state a minimum company size for any tier.
Pros: Genuinely free tier for basic salary/equity benchmarking, not just a trial; real-time data refresh rather than annual surveys; AI-driven job pricing and workforce-metrics analysis at higher tiers.
Cons: Everything past basic benchmarking — the features most comp teams actually need day to day, like compensation planning and total rewards statements — is quote-only; no published pricing for any paid tier.
Carta Total Compensation: Equity-First Benchmarking
Carta is best known for cap-table management, and Total Compensation is built to leverage that: it combines salary and equity benchmarking (Carta cites more than 40,000 unique data points, with roles updated quarterly) with tools for managing an equity pool, forecasting equity expense, and avoiding over-allocation. Companies that also run their cap table on Carta get additional real-time visibility into employee equity holdings and equity-planning recommendations tied directly to that data — a tighter loop between “what we’ve granted” and “what we should grant next” than a benchmarking-only tool can offer. Carta positions the product for private-market companies at any stage, with HRIS integrations for pulling in employee data, plus resources like a startup job-leveling guide and access to equity tax guidance.
Carta does not publish pricing for Total Compensation on its product page; it links to a separate “plans and pricing” destination and otherwise directs visitors to request a demo. Total Compensation is sold both to companies with no cap-table relationship with Carta and as an add-on for existing Carta cap-table customers, but no dollar figures are disclosed for either path.
Pros: Strongest equity-specific tooling of the three (pool management, dilution/over-allocation forecasting); natural fit and potential cost/data synergy for existing Carta cap-table customers; large benchmarking dataset.
Cons: No pricing published anywhere, including no free tier; less built out than PayScale on formal pay-equity analysis and job architecture; most useful advantages concentrate around equity, so cash-comp-only teams may get less differentiated value.
PayScale: Full Compensation Lifecycle, Still Quote-Based
PayScale’s current offering is marketed as the Payscale Intelligence Cloud, an umbrella for several named products: Ascent for pay decisions, JobNav for job architecture and job descriptions, JobNav Recruiter for compliant job postings, and Paycycle for merit-cycle and pay-raise planning. Feature-wise, this is the broadest of the three platforms: AI-guided salary benchmarking using industry- and geography-specific peer data, job architecture that feeds directly into benchmarking and planning, end-to-end merit-cycle and pay-raise management, offer modeling against live market data and budget guardrails, auto-generated pay-range language built to match local pay-transparency laws, formal pay-equity analysis with an auditable methodology and risk reporting, and manager-facing tools including pay snapshots, range-penetration views, and total-rewards statements. PayScale targets compensation and total-rewards teams, HR business partners, and talent acquisition, with particular emphasis on manufacturing, retail, hospitality, higher education, construction, and engineering/design industries.
Like Pave and Carta, PayScale does not publish prices. Its site directs visitors to a separate “Pricing & Plans” page and to “Get a Demo” or “Contact Sales,” which strongly implies quote-based pricing, though the page doesn’t state that policy explicitly.
Pros: Most complete feature set across benchmarking, job architecture, merit planning, and formal pay-equity analysis; built-in compliance support for jurisdiction-specific pay-range disclosure language; strong industry-specific targeting for non-tech sectors often underserved by newer comp tools.
Cons: No published pricing at all; multiple named sub-products (Ascent, JobNav, Paycycle) can make it unclear which modules a given quote actually includes without asking directly.
Bottom Line
Pricing transparency is the real dividing line in this category, and it only goes so far: Pave is the one platform you can start on for free today, but its free tier is benchmarking data only — the planning and workflow tools most comp teams eventually need are quote-gated, same as Carta and PayScale’s entire offerings. Choose Pave if equity-plus-cash benchmarking with modern AI workflows matters most and you want to start free; choose Carta Total Compensation if equity pool management and dilution forecasting are the priority, especially alongside an existing Carta cap table; choose PayScale if you need the fullest lifecycle coverage, including formal pay-equity analysis and job architecture, and don’t mind that every tier requires a sales conversation.
FAQ
Is any compensation management software here free? Pave’s Market Data Lite tier is free and provides real-time salary/equity benchmarking. Carta Total Compensation and PayScale have no published free tier.
Which tool is best for equity-heavy compensation (startups, pre-IPO)? Carta Total Compensation is the most equity-focused, with pool management and dilution/over-allocation forecasting, and extra value if you already use Carta’s cap-table product. Pave also publishes equity benchmarking data, including in its free tier.
Which tool handles formal pay-equity audits? PayScale is the most explicit about this, describing an “auditable methodology” and dedicated pay-equity risk reporting as part of its Intelligence Cloud.
Why don’t these vendors publish prices? Enterprise compensation software is typically priced by employee headcount, data-coverage scope (countries/metros), and which modules (planning, equity, pay-equity analysis) are included — variables significant enough that vendors in this category almost universally require a sales conversation rather than publishing a rate card.
Corporate learning and development software is a different market from the course-hosting platforms creators use to sell cohorts or masterclasses — enterprise LMS buyers care about compliance tracking, skills frameworks, HRIS integration, and reporting that satisfies an audit, not checkout pages and affiliate links. This guide compares three platforms built for internal employee training at scale: Cornerstone OnDemand (now sold as part of the Cornerstone Galaxy / Cornerstone Workforce AI platform), Docebo, and 360Learning.
At a Glance
Tool
Best For
Pricing Model
Starting Price
Key Strength
Cornerstone OnDemand
Large, complex enterprises wanting learning tied to talent management and succession
Quote-based
Not published
Breadth — learning, talent, performance, and workforce intelligence in one suite
Docebo
Mid-market to enterprise companies wanting a modern, AI-assisted LMS with modular add-ons
Quote-based, by active user model
Not published
Active-user pricing models and strong AI content/assistant features
360Learning
Organizations wanting fast rollout with collaborative, peer-authored content
Published entry tier + custom tiers
$8/user/month (Team plan, up to 100 users)
Only one of the three with a transparent starting price
Short Verdict
360Learning is the easiest to actually budget for — it’s the only one of the three with a published price, and its Team plan has no annual commitment. Docebo sits in the middle: no public price, but a clearly documented pricing model (active-user based, with modular add-ons) that makes a sales conversation more predictable. Cornerstone OnDemand is the deepest platform of the three, folding learning into a much larger talent-management and workforce-intelligence suite, but it’s also the most opaque on both pricing and even its own current product naming.
Cornerstone OnDemand: Learning Inside a Talent Platform
Cornerstone has rebranded parts of its suite under “Cornerstone Workforce AI” and “Cornerstone Galaxy,” and the LMS function now lives alongside Talent Development, Performance, Recruiting, Workforce Intelligence, and a set of AI “Readiness Agents” (Future of Work, Embark Navigator, Skills Architect). For corporate training specifically, the Learning Solutions line covers core learning delivery, a content/content-subscription marketplace, and Extended Enterprise training for partners and customers outside the organization, plus LMS products inherited through acquisition (Saba, SumTotal). Features emphasized on Cornerstone’s own marketing include learning tied directly to performance and succession planning, compliance management, frontline-worker training, AI-assisted content curation, and self-directed skills-based learning — one customer case study cited on Cornerstone’s site reports 76% of learning at that company now happens through self-directed paths rather than assigned courses.
Cornerstone does not publish pricing. Its site links to a “Packages and pricing” page but the only calls to action across its marketing pages are “Book a Demo” — there is no public price list, tier breakdown with dollar figures, or per-user rate disclosed anywhere we could verify. Buyers should expect a sales-led, likely per-employee-tier quote, consistent with other suite-level enterprise HR platforms.
Pros: Learning is tightly integrated with performance, succession, and workforce-intelligence modules rather than bolted on; strong compliance and frontline-training features; large ecosystem of integrations (AWS, Slack, LinkedIn, Salesforce, Microsoft).
Cons: Zero published pricing, including no entry-level figure; recent rebranding (Cornerstone Galaxy / Workforce AI) makes it harder to know exactly which product name a quote will reference; breadth of the suite can mean paying for talent-management modules you don’t need just to get the LMS.
Docebo: Active-User Pricing with Modular AI Add-Ons
Docebo’s pricing page doesn’t list dollar figures either, but it is unusually transparent about its pricing model: it charges by active learner usage rather than total licensed seats, and it lets customers choose between three user-counting approaches — Monthly Active User, Yearly Active User, or Registered Active User — depending on how predictable their training volume is. Docebo’s two named tiers are Elevate, the core LMS with personalization, white-labeling, compliance tracking, AI-powered content creation, multilingual training, and up to four included integrations; and Enterprise, which adds advanced analytics, up to six integrations, support for up to 10 extended-enterprise domains, two sandbox environments, a branded mobile app, a faster API rate limit (100 calls/minute), a dedicated database, and named account/success/solution engineering contacts.
Beyond the two core tiers, Docebo sells a long list of priced-separately add-ons: Advanced Analytics, Docebo Roleplay (priced by annual simulation volume), AI Credits for usage-based AI features (available as a shared pool or per-seat), Extended Enterprise, Branded Mobile App, a content marketplace, Communities, Gamified/Immersive Learning, E-Commerce, Headless Learning, Skills Intelligence (powered by 365Talents), Career Developer, and Talent Marketplace. All customers get 50GB of connected/indexed data included. None of these add-ons have published prices, and proof-of-concept trial availability depends on use case.
Pros: Active-user billing can be meaningfully cheaper than per-seat licensing for companies with large but intermittently-training workforces; clear tier structure (Elevate vs. Enterprise) even without prices; strong modern AI content and assistant features.
Cons: No published pricing at all, for either tier; heavy reliance on paid add-ons (analytics, roleplay, AI credits, extended enterprise) means the “real” cost of a full deployment is hard to estimate from the website alone.
360Learning: The Only Published Starting Price
360Learning differentiates itself with a collaborative-learning model — subject-matter experts across the company co-author and update course content rather than training relying solely on a central L&D team. It’s also the only platform in this comparison with a transparent, public starting price: the Team plan costs $8 per user per month for up to 100 users, billed monthly with no annual commitment required, aimed at small-to-mid-sized organizations. Above that, the Business plan and Enterprise plan move to custom pricing, generally under annual contracts, and layer in advanced integrations, premium onboarding, dedicated account management, priority SLAs, and strategic L&D guidance. Both Business and Enterprise support flexible user-counting that can combine registered and monthly-active-user models in a single contract.
360Learning’s FAQ states there’s no minimum user count or volume commitment on its paid plans, and no hidden setup fees, though professional services are priced separately and not published. A 30-day free trial is available. All plans include tailored implementation/launch support and access to 360Learning’s self-paced Academy resources. The feature checklist on the pricing page doesn’t clearly separate every capability by tier, so buyers evaluating SSO or specific integrations (some marked with an unexplained asterisk) should confirm tier inclusion directly with sales.
Pros: Only platform here with a real, public entry price; no annual lock-in on the Team plan; collaborative/peer-authored content model speeds up course creation for fast-moving teams; 30-day free trial.
Cons: Team plan caps out at 100 users, so most mid-market and enterprise buyers land in custom-quote territory anyway; feature-to-tier mapping on the pricing page is incomplete; less talent-management depth than Cornerstone.
Bottom Line
For a company under 100 employees that just wants a straightforward, budgetable LMS, 360Learning’s Team plan is the only option in this group you can price today without a sales call. Past that scale, all three vendors converge on quote-based, usage- or seat-tiered enterprise pricing — the real differentiator becomes platform shape rather than price: Cornerstone if you want learning bundled with full talent management and workforce intelligence, Docebo if you want a modern, AI-forward LMS with a clear (if undisclosed) active-user pricing logic and a menu of add-on modules, and 360Learning if collaborative content creation and faster rollout matter more than suite breadth.
FAQ
Does any of these three publish full pricing? No. Only 360Learning publishes a concrete starting price ($8/user/month, Team plan). Cornerstone and Docebo both require contacting sales for any dollar figure, at any tier.
What is “Cornerstone Galaxy”? It appears to be Cornerstone’s current branding for its broader AI-enabled talent platform (also referred to as “Cornerstone Workforce AI”), which houses the LMS alongside talent management, performance, recruiting, and workforce-intelligence products.
Which tool bills by active users rather than total seats? Docebo explicitly prices by active-user models (Monthly Active User, Yearly Active User, or Registered Active User). 360Learning’s Business and Enterprise tiers can also combine registered and monthly-active-user counting.
Is there a free trial for any of these? 360Learning offers a 30-day free trial. Docebo mentions proof-of-concept options depending on use case, not a blanket free trial. Cornerstone’s site does not mention a self-serve free trial.
Accounts payable teams drowning in PDF invoices, mismatched purchase orders, and three-way-match exceptions have a specific problem that generic document AI doesn’t fully solve: invoices arrive in hundreds of layouts, from hundreds of vendors, and still have to land in SAP, NetSuite, or Oracle with the right GL code and the right approver. This guide compares three of the most-cited platforms for AP-specific invoice automation in 2026: Rossum, a dedicated intelligent document processing platform built around accounts payable; UiPath Document Understanding, the document-AI layer inside UiPath’s broader RPA platform; and Automation Anywhere’s AP automation solution, which pairs OCR-based extraction with its Cloud RPA bots for end-to-end processing.
A note on naming: some vendor-comparison lists refer to a product called “Automation Anywhere AP Essentials.” We could not verify that this is an Automation Anywhere product — “AP Essentials” is actually sold by Tungsten Automation (formerly Kofax). This article instead covers Automation Anywhere’s actual accounts-payable automation offering, built on its Cloud RPA platform, which is the comparable product in this category.
At a Glance
Tool
Best For
Pricing Model
Starting Price
Key Strength
Rossum
Teams that want AP-dedicated IDP without building RPA workflows
Annual subscription, tiered
From $18,000/year (Starter)
Purpose-built AP data capture, matching, and fraud/duplicate checks
UiPath Document Understanding
Organizations already running UiPath RPA that want invoice data to feed existing automations
Usage-based (Platform Units per page), bundled in Automation Cloud licensing
Not publicly listed; quote-based
Deep integration with UiPath Studio, Taxonomy Manager, and robots
Automation Anywhere AP Automation
Enterprises wanting invoice capture plus full PO-matching and payment-cycle automation via bots
Contact sales
Not published
End-to-end AP workflow automation with anomaly/duplicate detection
Short Verdict
If your finance team wants a standalone system dedicated to invoice capture, coding, and matching — without first building out an RPA practice — Rossum is the most direct fit and the only one of the three with any published price. If you’re already a UiPath shop and want invoice extraction wired straight into existing bots and approval workflows, Document Understanding is the lower-friction add-on rather than a new platform. If you want a single vendor to own extraction and the downstream PO-matching, payment, and ERP-posting steps as bots, Automation Anywhere‘s AP automation solution is built for that, though you’ll need a sales conversation to get numbers either way.
Rossum: Purpose-Built AP Document AI
Rossum markets itself specifically around accounts payable rather than document processing in general. Its core engine, Rossum Aurora Document AI, extracts invoice data without requiring per-vendor templates — the company says it can learn a new layout from as few as 20 sample documents. Beyond extraction, Rossum handles the parts of the AP workflow that generic OCR tools leave to someone else: it infers GL and tax codes from document context and past decisions, runs configurable 2/3/4-way matching against POs and goods receipts, flags duplicate invoices and fraud indicators before they reach payment, and reads free-text payment terms to calculate early-payment discounts. It supports OCR and translation across 276 languages and has built-in support for e-invoicing mandates in Belgium, Poland, and France, alongside standard PDF processing. Prebuilt integrations cover SAP, Coupa, NetSuite, Workday, and Microsoft Dynamics.
On its pricing page, Rossum publishes a starting price for its Starter plan: $18,000 per year, billed annually, with unlimited seats, email/API/upload ingestion, the validation screen for handling exceptions, 12 months of document archive, and API access. The Business, Enterprise, and Ultimate tiers add custom business logic, SSO, sandboxes, document translation, multi-document transactions, and longer archive retention — but none of those have published prices; Rossum requires a quote. The minimum contract term is one year, and a 14-day free trial is available. Rossum reports customer results including an 87.5% reduction in invoice processing time at Veolia, 93% extraction accuracy across 100,000 annual invoices at Wolt, and a drop from 2 minutes to 35 seconds per invoice at Fugro across 300,000 invoices a year — all vendor-reported figures.
Pros: AP-specific out of the box (matching, GL coding, fraud checks); one published price point; fast learning curve for new invoice layouts; strong multilingual and e-invoicing coverage.
Cons: Only the entry tier has a public price; most AP-relevant add-ons (AP Apps, integrations, e-invoicing) are quote-only; $18,000/year entry point is a real commitment for very small AP teams.
UiPath Document Understanding: Invoice AI Inside a Broader RPA Platform
UiPath doesn’t sell a standalone “invoice tool” the way Rossum does — Document Understanding is a capability inside the UiPath platform, used alongside Studio, Taxonomy Manager, and Validation Station to build invoice-processing automations. The pitch is templateless extraction (handling varied layouts and noisy or skewed scans without manual template-building), models that are described as improving through use, and a human-in-the-loop validation step before data is handed to a robot that enters it into AP or expense systems. Because it sits inside the RPA platform, the practical advantage shows up when a company already has UiPath robots doing the downstream work — invoice data extraction becomes one more activity in an existing automation rather than a new system to integrate.
UiPath’s documented pricing model for Document Understanding is unusual: it’s metered in Platform Units (PUs) charged per page, not per document or per seat. Classification costs 0.04 PU per page; extraction costs 0.16 PU per page if the page was already classified, or 0.2 PU if not; a page that’s both classified and extracted is capped at 0.2 PU total regardless of how many models touch it. Generative Validation, where used, adds a further 0.2 PU. What UiPath doesn’t publish is what a Platform Unit actually costs in dollars — that depends on the customer’s Automation Cloud licensing tier and commitment, which requires talking to sales. In practice this makes UiPath’s AP cost structure the hardest of the three to estimate without a quote, even though the metering formula itself is transparent.
Pros: Transparent per-page metering formula; tight integration with UiPath Studio and existing robot workflows; strong fit if UiPath RPA is already deployed; handles messy/scanned invoices well.
Cons: No per-page dollar cost published, so true AP cost requires a sales conversation; not a dedicated AP product — matching, GL coding, and payment logic have to be built as separate automations rather than coming packaged; best value is tied to already owning UiPath licenses.
Automation Anywhere: AP Automation Through Cloud RPA
Automation Anywhere’s accounts-payable offering sits under its Finance & Accounting solutions and leans on its Cloud RPA platform plus AI-based OCR to cover the full invoice lifecycle: extracting invoice data, routing exceptions to AP staff for validation, matching invoices against purchase orders and goods receipts, generating POs automatically, posting updates into the ERP, and initiating payment. It layers in anomaly and duplicate detection with flags for investigation, real-time audit trails, and compliance support for multi-jurisdiction requirements including AML and KYC checks — features aimed more at enterprise shared-service centers than small AP teams. Automation Anywhere cites customer results such as 80% straight-through invoice processing with zero data-entry errors at Stant, a reported $3.3 million in savings and 1,500+ automated journal entries at Stanley Black & Decker, and a 100% faster processing cycle with 33% less manual labor at Juniper Networks — again, vendor-reported.
Pricing is not published anywhere on Automation Anywhere’s site for this solution; every page routes to “Request Demo.” A Cloud Community Edition exists for free, but it’s aimed at students and individual developers learning RPA, not production AP automation, so it isn’t a meaningful substitute for an enterprise deployment. As with most enterprise RPA buys, expect pricing tied to bot/document volume and negotiated per deal.
Pros: Covers the full AP cycle, not just extraction — PO matching, ERP posting, and payment initiation are part of the same platform; strong compliance and audit-trail features for regulated, multi-jurisdiction finance operations.
Cons: Zero published pricing, not even an entry tier; “AP Essentials” naming confusion in third-party listings means buyers should confirm exactly which Automation Anywhere product/SKU a quote covers; best suited to enterprises already comfortable with an RPA buying process.
Bottom Line
All three vendors gate most of their real pricing behind a sales call — that’s standard for enterprise AP software, and this comparison won’t pretend otherwise. Rossum is the one platform here with any public price ($18,000/year to start), and it’s the most AP-specific of the three out of the box, bundling matching, GL coding, and fraud checks rather than requiring you to assemble them. UiPath Document Understanding makes the most sense as an add-on to an existing UiPath RPA deployment, where its per-page Platform Unit metering is simply one more line item against a license you already have. Automation Anywhere’s AP automation is the most complete end-to-end option — extraction through payment — but also the most opaque on cost, and buyers should double-check product naming against what a rep quotes, since “AP Essentials” as a name belongs to a different vendor (Tungsten Automation/Kofax), not Automation Anywhere.
FAQ
Does Automation Anywhere sell a product called “AP Essentials”? Not that we could verify. “AP Essentials” is a product from Tungsten Automation (formerly Kofax). Automation Anywhere’s comparable offering is its AP automation solution built on Cloud RPA, covered above.
Is any of these three free to use? No. Rossum offers a 14-day free trial but no free tier. UiPath has a free Community Edition aimed at individual learning/development, not production AP workloads. Automation Anywhere does not publish a free production tier for its AP solution.
Which tool handles PO matching natively? Rossum and Automation Anywhere both build 2/3/4-way matching into their AP offerings. UiPath Document Understanding focuses on extraction and classification; matching logic is typically built as a separate automation using the extracted data.
Do I need existing RPA infrastructure to use any of these? No for Rossum, which is designed to run standalone. UiPath Document Understanding delivers the most value when paired with existing UiPath robots. Automation Anywhere’s AP solution is built on its own Cloud RPA platform, so it brings its own automation layer rather than requiring a separate one.
Hybrid teams have a specific, recurring problem: someone needs a desk, meeting room, or private office for a few hours or a day — not a year-long lease. LiquidSpace, Deskpass, and WeWork On Demand all solve that, but from different angles: two are marketplaces that pull in space from many operators, and one is a single brand’s own pay-as-you-go product. We confirmed WeWork On Demand is still a live, actively updated offering in 2026, not a discontinued program, which matters since flexible-workspace products have come and gone over the past few years.
At a Glance
Platform
Model
Coverage
Starting Price
LiquidSpace
Marketplace aggregating many independent & brand-name operators
10,500+ locations across 2,700+ cities
Free to browse/book individually; Enterprise is custom-quoted
Deskpass
Marketplace with pay-as-you-go passes plus a managed Teams product
Network of partner coworking locations (city-dependent)
Desks from $15/day; meeting rooms from $5/hour; private offices from $50/day
WeWork On Demand
Single-brand pay-as-you-go access to WeWork’s own locations
300+ WeWork locations across 70+ cities
Day pass from $29/day; meeting rooms from $39/hour; private offices from $60/day
Short Verdict
If you want the widest possible selection and don’t care which brand runs the space, LiquidSpace‘s marketplace scale (10,500+ locations) is hard to match, and it’s free to browse and book as an individual. If your team wants a managed program with budget controls and usage reporting across many cities, Deskpass Teams is purpose-built for that, though you’ll need to talk to sales for pricing. If you specifically want the WeWork brand experience — consistent design, amenities, and app — at a transparent published price, WeWork On Demand is the most predictable of the three, but only within WeWork’s own 300+ locations.
LiquidSpace: The Biggest Marketplace, Free for Individuals
LiquidSpace positions itself as a broad marketplace for flexible office space, claiming access to more than 10,500 locations across over 2,700 cities, spanning both brand-name operators and independent coworking spaces. That scale is its core advantage: if your hybrid team is scattered across many cities or travels frequently, LiquidSpace is more likely to have a nearby option than a single-brand network.
For individuals, the Individual plan is listed as completely free, with pay-as-you-go booking and a flexible cancellation policy — you only pay for the space itself when you book it. For companies, LiquidSpace’s Enterprise plan adds a “Workplace Manager” layer: dashboards, team-based booking permissions, centralized payments, and cost-center reporting, aimed at HR or workplace-ops teams managing flexible space spend across a distributed workforce. Enterprise pricing isn’t published and requires contacting LiquidSpace directly. The company also offers a standardized “DASH License” agreement used across many of its independent operator partners, which can simplify the legal side of booking space from smaller, less process-heavy operators.
Pros
Largest claimed inventory of the three — 10,500+ locations in 2,700+ cities
Free individual plan with no booking fees mentioned
Enterprise tier adds real workplace-management tooling (dashboards, cost centers) for distributed teams
Cons
No published Enterprise pricing — every company deal needs a sales conversation
Marketplace model means quality/consistency varies by which independent operator you book
The public site doesn’t detail a dedicated product for space-owner partners
Deskpass: Pay-As-You-Go Plus a Dedicated Teams Product
Deskpass splits cleanly into two tiers. Instant Workspace is the pay-as-you-go option: desks starting at $15/day (with day rates varying by partner location), meeting rooms starting at $5/hour, and private offices starting at $50/day, all with no membership and no long-term commitment — Deskpass’s own language is “No Hidden Fees. No Long-Term Commitment. No Memberships.” Deskpass Teams builds on that same network but adds the pieces a company actually needs to manage flexible space as a benefit: utilization-based pricing, an admin dashboard with budget controls, consolidated billing across everyone using it, and live reporting on usage.
Deskpass also folds in a community angle — members get access to local events and perks at partner businesses, which is a small but real differentiator if your hybrid team values more than just a desk. As with LiquidSpace’s Enterprise tier, Deskpass Teams pricing isn’t published; you need to book a demo or call their sales line to get a quote.
Pros
Published starting prices for individual desk/room/office bookings — not everything is a quote
Dedicated Teams product with budget controls and consolidated billing built specifically for managed company programs
No membership required to use pay-as-you-go access
Cons
Teams pricing is entirely quote-based despite clear Instant Workspace pricing
Day rates “vary by partner location,” so the $15/day floor won’t apply everywhere
Smaller publicly stated network than LiquidSpace’s marketplace scale
WeWork On Demand: One Brand, Transparent Published Pricing
WeWork On Demand is the pay-as-you-go arm of WeWork’s own network — not a multi-operator marketplace. You book a coworking day pass, a private office by the day, or a meeting room by the hour, directly through the WeWork app or Member web, and pay by card at confirmation. Access spans WeWork’s own 300+ locations across 70+ cities, with reservations running the full business day and keycard access activating 20 minutes before your booked start time. You’ll need a government-issued photo ID and must check in with on-site staff — a slightly more formal process than booking through a pure marketplace.
Pricing is published and specific: coworking day passes start at $29/day, meeting rooms start at $39/hour (charged per seat), and private offices start at $60/day. Locations are generally open weekdays 9 a.m. to 6 p.m. (excluding local holidays), bookings can be made up to 30 days in advance, and cancellations are fully refundable at least 24 hours before the start time. Note that On Demand is separate from WeWork All Access, which uses a credit-based membership model rather than straight pay-per-use.
Pros
Fully published, specific pricing for every booking type — no sales call needed
Consistent WeWork brand experience, amenities, and app across every location
Fully refundable cancellation up to 24 hours before start time
Cons
Limited to WeWork’s own 300+ locations — far smaller footprint than LiquidSpace’s marketplace
Highest published starting prices of the three for day passes and meeting rooms
Weekday 9–6 access windows and photo-ID check-in are more restrictive than some marketplace listings
Bottom Line
Choose based on how much you value selection versus consistency. LiquidSpace wins on sheer reach and costs nothing to browse or book individually, making it the default choice for hybrid teams spread across many cities. Deskpass is the strongest fit if you specifically want a managed company program with budget controls and reporting layered on top of pay-as-you-go access. WeWork On Demand is the right call when your team already trusts the WeWork brand and wants predictable, fully published pricing without comparing multiple independent operators.
FAQ
Is WeWork On Demand still available in 2026? Yes. WeWork’s own site shows On Demand as a live, currently priced product with 300+ locations across 70+ cities as of this writing — it has not been discontinued.
Do I need a membership to use any of these? No. LiquidSpace’s Individual plan, Deskpass’s Instant Workspace, and WeWork On Demand are all pay-as-you-go with no membership required. Deskpass Teams and LiquidSpace Enterprise are managed company programs, not consumer memberships.
Which platform has the widest city coverage? LiquidSpace, by a wide margin — its marketplace claims 2,700+ cities versus WeWork On Demand’s 70+ cities and Deskpass’s smaller, partner-dependent network.
Can a company manage spend across all its employees on these platforms? Yes, through LiquidSpace’s Enterprise/Workplace Manager tier or Deskpass Teams, both of which add admin dashboards, budget controls, and consolidated billing on top of the basic pay-as-you-go booking.
It’s easy to lump “secure file transfer” in with encrypted cloud storage, but they solve different problems. A cloud storage service like Tresorit’s main product, Dropbox, or Google Drive keeps files persistently synced and accessible over time. Tresorit Send, MASV, and SendSafely, by contrast, are built for the one-off job: getting a single large or sensitive file — a legal contract, a raw video master, a patient record — from one party to another, securely, without setting either side up with ongoing storage. This comparison sticks to that use case: occasional, large, or sensitive business file transfers, not day-to-day file syncing.
At a Glance
Feature
Tresorit Send
MASV
SendSafely
Starting price
Free
$0.25/GB pay-as-you-go (first 15GB/month free)
Free (Personal, 50MB/month)
Paid tier example
N/A (single free tool)
250GB/month: $58/month
Pro: $20/month (100GB/month, 10GB per file)
Business/team plan
Separate Tresorit business products
Enterprise Platform, custom pricing
Team: $120/month billed annually (5–25 users)
Max file size
5GB per upload, 100 files
No stated cap; built for petabyte-scale transfers
Up to 10GB per file (Pro)
Account required to send
No registration required
Yes, for most plans
Account for sender; recipients don’t need one
Encryption
End-to-end; Tresorit never holds the keys
TLS in transit; enterprise adds malware scanning
OpenPGP/AES end-to-end encryption
Link expiration
7 days or 10 downloads, whichever first
Configurable; files stored free 5 days, then billed
Configurable (paid plans)
Compliance certifications
Inherits Tresorit’s security model
SOC 2 Type II, ISO 27001:2022, HIPAA, TPN, GDPR
SOC 2 Type II, PCI DSS SAQ D-SP, HIPAA BAA (Business+)
Short Verdict
Tresorit Send is the simplest and cheapest option for an occasional, under-5GB, end-to-end encrypted transfer — no account, no cost, strong encryption by default. MASV is built for media and broadcast workflows moving very large files (think raw 4K footage, not PDFs) and bills by the gigabyte or by monthly allowance rather than by seat. SendSafely is the one built around compliance and audit trails — package-level tracking, HIPAA BAAs, and SIEM-ready logging — making it the pick for legal, healthcare, or financial teams that need to prove chain of custody, not just send a file.
Tresorit Send: Pricing and Limits
Tresorit Send is free with no registration required to send a file. Uploads are capped at 5GB total, across up to 100 files per upload. Files are encrypted end-to-end before they leave the sender’s device, and per Tresorit, the decryption key is stored in the link itself rather than on Tresorit’s servers — so Tresorit itself cannot open the file. Links expire automatically after 7 days or 10 downloads, whichever comes first, and senders can add an optional password and revoke the link early. There’s no paid tier for Send specifically — it’s a standalone free tool, separate from Tresorit’s subscription cloud-storage and business file-sharing products, which carry their own per-user pricing for persistent storage.
MASV: Pricing and Limits
MASV charges by data volume rather than by seat, which fits its target market of video and media teams moving very large files. The On-Demand plan is pay-as-you-go at $0.25/GB with the first 15GB each month free and no contract. The Subscription plan bills a flat monthly rate for an allowance: 250GB for $58/month, 500GB for $110/month, 1TB for $215/month, or 2TB for $410/month, each on a 12-month commitment with overages at a discounted rate. Pre-Buy Credits are a one-time purchase valid for 180 days — 5TB for $1,229, 10TB for $2,355, or 25TB for $5,632. Delivered files are stored free for 5 days, after which storage costs $0.07/GB per month. An Enterprise Platform tier adds centralized authentication, automated malware scanning, API-driven workflows, and unlimited portals/users, priced on request. MASV doesn’t publish a hard per-file size limit — its marketing is built around “petabyte-scale” transfers.
SendSafely: Pricing and Limits
SendSafely’s individual plans are: Personal (free, personal email addresses only, 50MB/month), Basic ($10/month, 250MB/month, adds expiration controls and an Outlook plug-in), and Pro ($20/month, 100GB/month with files up to 10GB each). For organizations, Team runs $120/month billed annually for 5–25 users with 10GB and 200 “packages” per month; Business is $232/month billed annually for 8–50 users with 30GB and 500 packages per month, adding white-label branding, API access, and a HIPAA BAA; Enterprise is custom-priced with 100GB and 1,000 packages per month plus SIEM-ready audit logging and multi-region storage. All plans use OpenPGP/AES end-to-end encryption, two-factor login, and download tracking. Team and above carry SOC 2 Type 2 and PCI DSS SAQ D-SP certifications; Business and Enterprise add HIPAA business associate agreements.
Encryption and Security Model
All three encrypt data, but the guarantees differ. Tresorit Send is explicitly zero-knowledge: the decryption key lives in the link, not on Tresorit’s servers, so Tresorit cannot access file contents even if compelled to. SendSafely layers OpenPGP/AES encryption with two-factor authentication and, on paid plans, download tracking and audit logs — its design center is proving who accessed what and when, which matters for regulated industries. MASV’s published security claims center on compliance certifications (SOC 2 Type II, ISO 27001:2022, HIPAA-compliant status, TPN verification for media workflows) and, on the Enterprise tier, automated malware scanning — it’s built to satisfy a studio’s or broadcaster’s security review rather than to advertise zero-knowledge encryption as its headline feature.
Pros and Cons
Tresorit Send
Pros: Free, no account needed, true end-to-end encryption, simple for a single quick transfer.
Cons: 5GB cap is small for media workflows; no audit trail, team management, or branding — it’s a single-purpose utility, not a platform.
MASV
Pros: Built for very large files with no practical size ceiling; flexible pay-per-GB, monthly, or pre-buy pricing; strong media-industry compliance (TPN).
Cons: Costs scale directly with volume, which adds up fast for large or frequent transfers; subscription tiers require a 12-month commitment.
SendSafely
Pros: Strong compliance posture (HIPAA BAA, PCI DSS, SOC 2) and audit logging aimed at regulated industries; free tier available for light personal use.
Cons: Volume limits (measured in MB, not GB) on the Personal and Basic tiers are restrictive; per-file size cap of 10GB even on Pro is lower than MASV’s effectively unlimited approach.
Bottom Line
Match the tool to the job, not the brand. For a quick, free, encrypted one-off send under 5GB, Tresorit Send needs no setup and no subscription. For large media files — raw footage, broadcast masters, multi-gigabyte datasets — MASV’s volume-based pricing and lack of a hard size ceiling fit the workload better than either competitor. For regulated businesses that need to prove who sent, received, and opened a file — with HIPAA, PCI DSS, or SOC 2 backing — SendSafely’s package-tracked, audit-logged model is the better fit, even though its free and entry tiers are the most limited of the three on raw volume.
FAQ
Is Tresorit Send the same product as Tresorit’s cloud storage?
No. Tresorit Send is a free, standalone tool for one-off encrypted transfers up to 5GB with no account required. Tresorit’s paid cloud storage and business file-sharing plans are separate products built for ongoing, persistent encrypted storage and collaboration.
Does MASV have a file size limit?
MASV doesn’t publish a hard per-file cap on its pricing page; it markets itself around support for very large, even petabyte-scale, media transfers, with cost scaling by gigabyte transferred or stored.
Which of these three has a free tier?
Tresorit Send is free for every transfer up to its 5GB limit. SendSafely’s Personal plan is also free but capped at 50MB per month. MASV’s On-Demand plan includes 15GB free per month, billing only beyond that.
Which is best for HIPAA-regulated file transfers?
Both MASV (HIPAA-compliant status) and SendSafely (HIPAA business associate agreements on Business and Enterprise plans) address healthcare compliance. SendSafely’s package-level audit logging is more explicitly built around proving compliant handling of individual files.
Every major parental control option takes a different approach to the same problem: how much visibility and control should a parent have over a child’s phone, tablet, or Chromebook? Qustodio, Bark, and Google Family Link sit at three different points on that spectrum — a paid cross-platform suite, an AI-driven monitoring service, and a free Google-ecosystem tool. This is a straightforward feature-and-pricing comparison of what each one actually does: screen time controls, content filtering, location tracking, and messaging oversight. It is not advice about any individual child’s situation — just the facts, so you can match the tool to your family’s devices and budget.
At a Glance
Feature
Qustodio
Bark (App)
Google Family Link
Starting price
$59.95/year (Basic)
$14/month or $99/year
Free
Top-tier price
$104.95/year (Complete)
Same plan, unlimited kids
Free
Devices covered
5 (Basic) / Unlimited (Complete)
Unlimited devices & kids
Unlimited (Android/ChromeOS only for the child’s device)
Google Family Link is the right call if your family lives inside Android and Chromebooks and you want screen time limits, app approval, and location tracking for $0. Qustodio is the best general-purpose paid option for mixed households (iPhone, Android, Windows, Mac, Kindle) that want one dashboard for everything, including call and text oversight. Bark leans hardest into content monitoring — its AI scans texts, social apps, email, and browsing for signs of trouble — making it the pick for parents more worried about what a teen is being exposed to than about blocking apps outright.
Qustodio: Pricing and Plans
Qustodio sells two consumer tiers. Basic runs $59.95/year and covers up to 5 devices; a “Care Plus” add-on (identity and wellbeing extras) costs an additional $12.99. Complete, Qustodio’s “best value” plan, is $104.95/year, covers unlimited family devices, and bundles Care Plus at no extra charge. Both tiers include the core feature set — screen time, content filtering, location tracking, and call/text monitoring — the difference is device count and the bundled extras. Qustodio offers a free trial of the premium features with no credit card required.
Bark: Pricing and Plans
The Bark App (the software-only product most comparable to Qustodio and Family Link) starts at $14/month or $99/year and covers unlimited devices and unlimited children on one family account. Monitoring texts, photos, and videos on iOS specifically requires either the optional Bark Sync add-on ($6/month or $49/year) or the Bark Desktop App. Bark also sells its own hardware — the Bark Phone ($360–$600 plus a $29+/month service plan) and Bark Watch ($288 plus $15/month) — for families that want a locked-down device rather than software layered onto an existing one, but those are a different product category from the app-based comparison here.
Google Family Link: Pricing and Plans
Family Link has no paid tier at all — every feature is free. The trade-off is platform reach: the parent app runs on Android 6.0+, iOS 16+, or a Chromebook, but the child’s supervised device must be running Android 6.0 or later, ChromeOS 71 or later, or be a compatible Fitbit. Google’s own support documentation is explicit that iPhones, iPads, and non-Chromebook computers “can’t be supervised with Family Link” — a hard limit that doesn’t apply to Qustodio or Bark, both of which support iOS as a supervised child device.
Screen Time and Scheduling
All three handle the basics — daily time limits, device locking, and bedtime windows — but with different granularity. Qustodio and Bark both let parents build custom schedules per day of the week and pause the internet entirely for homework or meals. Family Link sets a daily limit per Android device or Chromebook, supports bedtime/school-hours locking, and lets a parent grant bonus time remotely, but its scheduling is simpler and tied to Google’s own settings menus rather than a dedicated dashboard.
Content Filtering
Qustodio and Bark both filter and block at the website and app level across platforms, independent of which app store or browser a child uses. Family Link’s filtering is narrower by design: it restricts what can be downloaded or purchased from Google Play (by age rating) and applies Chrome’s SafeSearch and site-blocking, but it doesn’t offer the same cross-browser, cross-app blocking that Qustodio and Bark build as their core product.
Location Tracking
Location tracking is now a baseline feature in all three. Qustodio adds geofencing with arrival/departure alerts for saved places. Bark rolled out full location tracking to every Bark App subscriber. Family Link shows a child’s Android or Chromebook location on a map but doesn’t offer geofence-style place alerts in the same way the two paid tools do.
Messaging, Social Media, and Call Monitoring
This is where the free and paid tools diverge most. Family Link does not read or flag texts, calls, or social media content at all — it’s a device-management tool, not a monitoring tool. Qustodio tracks calls and texts and can alert on concerning messages or block specific contacts, though on iOS that requires pairing the child’s account with a Windows or Mac computer. Bark uses AI to scan texts, email, and 30+ apps (including social platforms) for signs of cyberbullying, self-harm language, or predatory contact, sending parents an alert rather than a full transcript — its most distinctive feature relative to the other two.
Pros and Cons
Qustodio
Pros: Broad cross-platform support including iOS and Kindle; one dashboard for screen time, filtering, location, and messaging; unlimited devices on the Complete plan.
Cons: Full call/text monitoring on iOS needs an extra Mac/PC pairing step; cheaper tier caps out at 5 devices.
Bark
Pros: Strongest AI-driven content monitoring across texts, email, and social apps; unlimited kids and devices on one plan; also offers locked-down hardware for families that want it.
Cons: iOS text/photo/video monitoring requires a paid add-on or a desktop app; monthly cost is higher than Qustodio’s Basic tier.
Google Family Link
Pros: Completely free; tightly integrated with Android, Chromebooks, and Google Play app approvals.
Cons: Can’t supervise an iPhone or iPad as the child’s device; no text, call, or social media monitoring; filtering limited mostly to the Google ecosystem.
Bottom Line
Pick based on your platforms and your priority, not on brand recognition. If your child’s phone is an iPhone and you want messaging oversight, Qustodio or Bark are the only two of these three that fit — Qustodio for the broader all-in-one dashboard, Bark for the deeper AI content analysis. If the whole family is Android/Chromebook and the budget is zero, Family Link covers screen time, app approval, and location without a subscription, just without the messaging and cross-platform filtering the paid tools add.
FAQ
Is Google Family Link really free?
Yes. There is no paid tier, subscription, or in-app purchase required to use Family Link’s core features.
Can Family Link supervise an iPhone?
The parent app runs on iOS, but the child’s own device can’t be supervised unless it’s Android, ChromeOS, or a compatible Fitbit. An iPhone or iPad can’t be the supervised device.
Does Bark read my child’s actual messages?
Bark’s AI scans content for risk signals (bullying, self-harm language, predatory contact, etc.) and sends parents an alert with relevant context rather than a continuous live feed of every message.
Which is cheapest for a large family?
Qustodio’s Complete plan ($104.95/year) and Bark’s App plan ($99/year) both cover unlimited devices and kids for a flat annual fee, which works out cheaper per child than paying per device on some competitors. Family Link remains free regardless of family size, within its Android/ChromeOS platform limits.
A quick note before the comparison: the well-known “Icebreaker” app for remote team connection rebranded to Gatheround back in 2021 — the Icebreaker name and domain no longer point to an active, separately branded product, so we’re reviewing it under its current identity. That’s a better match than reaching for an unrelated tool that happens to share a name. With that settled, here’s how Donut, Gatheround, and Gather actually differ for building remote team culture in 2026.
At a Glance
Tool
Core Format
Best For
Starting Price
Donut
Slack/Teams-native pairing & recognition bot
Teams that live in Slack and want lightweight, automated 1:1 intros and shoutouts
Free tier available; Standard from $74/mo
Gatheround (formerly Icebreaker)
Scheduled video meetings with structured activities
Onboarding sessions, all-hands icebreakers, and dedicated bonding events
$60/mo (Premium), up to 50 participants
Gather
Persistent 2D virtual office space
Fully remote teams wanting an always-on “office” for casual encounters, not just scheduled events
$12/user/mo (Essential); custom Enterprise
Short Verdict
These three solve overlapping but distinct problems. Donut is the lowest-friction option because it works inside Slack or Teams and runs itself — pairing people and surfacing shoutouts with no one needing to “go” anywhere. Gatheround is built for scheduled, structured bonding moments — onboarding cohorts, all-hands kickoffs, department socials — where someone deliberately plans an event with an agenda. Gather is the only one of the three built as a persistent space: a virtual office your team can drop into any time, which suits companies trying to recreate hallway run-ins rather than just scheduled events.
Donut: Automated Pairing and Recognition Inside Slack
Donut lives inside the tools your team already uses — primarily Slack, with Zoom, Microsoft Teams, and FigJam integrations — rather than asking anyone to open a new app. Its core mechanic is automated pairing: Donut’s “Intros” feature matches teammates for virtual or in-person meetups on a recurring schedule, which is specifically useful for distributed teams where people on different floors, offices, or time zones rarely cross paths organically. Beyond pairing, Donut runs “Watercooler” conversation prompts, “Celebrations” for milestones, and “Shoutouts,” a peer-recognition system with points and a redeemable rewards store. “Journeys” let you build automated message sequences for onboarding or training programs.
Pricing starts with a genuinely usable Free plan ($0/mo) covering one Slack channel each for Intros, Watercooler, and Celebrations, plus Google Calendar and Zoom integration. Standard starts at $74/month (billed annually) and adds multiple channels, gift-card rewards, and HRIS sync from 50+ platforms. Premium starts at $119/month (annual billing) and adds unlimited Shoutouts, unlimited Journeys, and prebuilt Journey templates. Both paid tiers scale further with headcount in Donut channels, and there’s a custom-quoted Enterprise tier aimed at companies over 500 employees. A 14-day free trial covers Standard and Premium.
Pros
Runs natively inside Slack/Teams — no new app for employees to learn
Genuinely useful free tier, not just a crippled trial
Automated, recurring pairing solves the “we never talk to people on other teams” problem without manual scheduling
Cons
No live, shared-space experience — everything happens asynchronously or in 1:1 pairings
Paid tier pricing scales with people/channels in ways that aren’t fully transparent without talking to sales
Less suited to big, single scheduled events than to ongoing background culture-building
Gatheround (Formerly Icebreaker): Structured Video Bonding Events
Gatheround is a scheduled-event platform: you pick a time, invite people, and run a video session built around pre-made agendas and interactive formats — Breakouts, Q&As, Polls, Quizzes, Flashcards, and a Photo Booth among them. It’s commonly used for new-hire onboarding cohorts, all-hands icebreakers, and recurring department socials where the point is a dedicated, facilitated block of time rather than an ambient connection. Hosts can record sessions, generate automatic event recaps, and export data afterward, which makes it easier to prove the program is actually running and to reuse what worked.
Pricing is published as a single Premium plan at $60/month, supporting up to 50 participants per event, unlimited meetings, access to hundreds of pre-built agendas, 10+ activity types, recording, recaps, and data export. There’s no separate free tier or lower-cost option listed, and no explicit enterprise tier breakdown on the public pricing page, so larger organizations should expect to confirm volume pricing directly with Gatheround.
Pros
Hundreds of ready-made agendas remove the planning burden from whoever’s running the event
Strong fit for onboarding cohorts and all-hands-style sessions, not just small-team socials
Recording and recaps make it easy to measure whether events are actually landing
Cons
Single published plan at $60/month with a 50-participant cap — no visible free tier
Event-based by design, so it won’t replace the kind of ambient, everyday interaction Gather or Donut provide
Rebrand from “Icebreaker” means older references to the product online may point to the wrong URL or name
Gather: A Persistent Virtual Office, Not Just an Event
Gather takes a different shape entirely: it’s a custom, always-available 2D virtual office your team can walk into and out of throughout the workday, rather than something you schedule for a one-hour event. People move an avatar around a shared map, and audio/video connects automatically based on proximity — the closest thing available to recreating hallway run-ins and desk-side chats for a fully distributed team. Beyond the ambient-presence angle, Gather includes unlimited audio/video calls, chat, meeting recording, AI-generated meeting notes and transcriptions, and calendar sync, positioning it as a daily-use tool rather than an occasional culture event.
Pricing is per-member rather than per-event: the Essential plan runs $12/month per member (with a 20% discount for annual billing) and includes every core feature. A Custom plan for larger teams adds custom onboarding, bigger/multiple office spaces, hybrid-work configurations, SSO, extended trials, and regional pricing — all behind a sales conversation. Every plan opens with a full-featured, no-credit-card 30-day free trial.
Pros
Only one of the three built for everyday, ambient presence rather than scheduled events
Per-member pricing is transparent and predictable at the Essential tier
Generous 30-day trial with full features and no credit card required
Cons
Requires actual adoption — a persistent virtual office only works if people choose to be “in” it during the day
Per-member monthly cost adds up for large teams compared to Donut’s flat/tiered pricing
Not built for structured, facilitated bonding activities the way Gatheround is
Bottom Line
Think about the shape of the interaction you’re trying to create, not just the budget. If you want background, automated connection with near-zero ongoing effort, start with Donut‘s free tier inside Slack. If you need a dedicated, facilitated session — onboarding a new cohort, running an all-hands icebreaker — Gatheround‘s event format and pre-built agendas do the planning for you. If your real goal is recreating the feel of a shared office for a fully remote team, Gather‘s persistent space is the only one of the three actually designed for that. Many teams end up running two of these together — Donut for ambient culture, plus either Gatheround for set-piece events or Gather for daily presence — rather than picking exactly one.
FAQ
What happened to the app called “Icebreaker”? The remote-team bonding platform formerly called Icebreaker (icebreaker.video) rebranded to Gatheround in 2021. It’s the same company and product line under a new name, which is why this article reviews it as Gatheround.
Can Donut and Gather be used together? Yes. They solve different problems — Donut automates pairing and recognition inside Slack, while Gather provides an always-on shared virtual space — and many distributed teams run both simultaneously.
Does Gatheround have a free plan? Its public pricing page lists a single paid Premium plan at $60/month with no separate free tier, unlike Donut and Gather, which both offer free or trial entry points.
Which tool is best for onboarding new remote hires specifically? Gatheround’s structured, pre-built agenda format is the most purpose-built for onboarding cohorts, though Donut’s “Journeys” automation can run alongside it for ongoing onboarding touchpoints.
This comparison is about a specific job: taking control of — or helping someone on — another computer, whether that’s an IT technician fixing an employee’s laptop, a help desk jumping into a customer’s machine, or an admin reaching an unattended server after hours. That’s a different category from meeting software like Zoom or screen-recording tools like Loom. TeamViewer, AnyDesk, and Splashtop are the three names that come up constantly for this job, and each has pulled its public pricing behind a sales conversation in different ways — which itself matters when you’re comparing them.
At a Glance
Tool
Best For
Published Pricing?
Standout Feature
TeamViewer
Enterprise IT support & operational technology (Tensor/ONE)
No — plan pricing requires a sales quote; add-ons scale by endpoints/users
Built-in AI assistant (“Tia”) and automated session summaries
AnyDesk
Teams needing many unattended/managed endpoints at predictable tiers
No — four named tiers (Solo/Standard/Advanced/Ultimate) with no listed prices
Tiered managed-device limits (100 to 2,000+ devices) with role-based address books
Splashtop
IT help desks and MSPs that want transparent, published per-tech pricing
Yes — exact monthly/annual prices published for every plan
Splashtop SOS: on-demand, code-based support for any device, from $22/month per technician
Short Verdict
If you want to know the price before you talk to anyone, Splashtop is the only one of the three that publishes exact numbers for both general remote access and dedicated IT/help-desk support (its SOS line). If you’re an enterprise IT department that wants AI-assisted troubleshooting and cross-platform device management at scale, TeamViewer‘s Tensor/ONE lineup is built for that — but expect a sales call. If your priority is unattended access to a large, predictable number of managed devices at tiered levels, AnyDesk‘s four-tier structure is the clearest way to reason about scale, even without posted prices.
TeamViewer: Enterprise-Grade Remote Support With AI Built In
TeamViewer’s product lineup splits into TeamViewer Remote (aimed at individuals and SMBs doing remote support and remote management), TeamViewer Tensor (the enterprise platform, also covering operational technology environments like factory floors), and TeamViewer ONE, which unifies both under one roof. For straightforward “help someone on another machine” work, Remote and Tensor are the relevant tiers.
Licensing is per-expert rather than per-device: the technician holds the license, not the machine being helped, which scales well for a help-desk team supporting many different end-user devices. TeamViewer layers in “licensed users” for multi-person teams and supports concurrent connections (multiple simultaneous sessions) and centrally managed devices for IT admins. Its newer differentiator is TeamViewer AI — “Tia,” a troubleshooting assistant, plus Session Insights, which automatically summarizes support cases, both aimed at cutting resolution time for high-volume help desks.
Pricing is entirely quote-based on TeamViewer’s own pricing page: subscriptions run annually, auto-renew unless canceled at least 28 days before term end, add-on costs scale with endpoints/users/storage with volume discounts, and there’s a standing 30% discount for non-profits and education. No specific dollar figures are published for the Remote or Tensor plans themselves.
Pros
Per-expert licensing scales cleanly for help-desk teams supporting many devices
AI troubleshooting assistant and automatic session summaries are genuinely aimed at support workflows
Tensor and ONE extend into enterprise device management and OT environments
Cons
No published prices anywhere on the official pricing page — everything is a quote
Add-on costs (endpoints, users, storage) make total cost hard to estimate up front
Annual auto-renewal with a strict 28-day cancellation window
AnyDesk: Tiered Plans for Scaling Unattended Access
AnyDesk organizes its paid plans into four named tiers — Solo, Standard, Advanced, and Ultimate — that scale primarily on two things: how many simultaneous connections you can run, and how many devices you can set up for unattended, managed access. Solo starts at one concurrent connection and 100 managed devices with a single 100-entry address book. Standard raises that to 500 managed devices across six address books (one personal, five shared). Advanced doubles concurrent connections to two and lifts managed devices to 1,000 across sixteen address books. Ultimate tops out at five simultaneous users, 2,000 managed devices, and unlimited address books with role-based access control for larger teams.
Managed Devices and Remote Restart are available as add-ons across all tiers, and a user can generally run sessions on up to three devices in parallel, though AnyDesk’s page doesn’t clearly map every feature (like session recording) to a specific tier — worth confirming directly with AnyDesk before buying if that’s a must-have.
Like TeamViewer, AnyDesk does not publish dollar prices on its pricing page. It does advertise a 20% discount on the first subscription year regardless of plan, and offers multi-year billing on request. Subscriptions auto-renew annually unless canceled.
Pros
Clear tier structure based on concurrent connections and managed-device counts
Scales up to 2,000 managed devices with role-based address books on Ultimate
20% first-year discount advertised on every plan
Cons
No listed prices — every plan requires contacting AnyDesk directly
Feature-to-tier mapping (e.g., session recording) isn’t fully clear from the public page
Solo and Standard tiers cap you at just one or two concurrent connections
Splashtop: Transparent Pricing, Dedicated IT Support Line
Splashtop is the outlier here in the best possible way: it publishes exact prices for both its general remote-access plans and a dedicated IT support product line. The general-access side runs Solo ($6/month or $72/year — unattended access, file transfer, remote print), Pro ($8.25/user/month or $99/user/year — adds multi-monitor support, role-based access, chat, and session recording), Performance ($13/user/month or $149/user/year — adds 4:4:4 color, 240fps, high-fidelity audio, and USB passthrough), and a custom-quote Enterprise tier with SSO, SIEM logging, and on-prem options.
The part that matters most for IT/help-desk use is Splashtop SOS, built specifically for on-demand support: a technician gives an end user a short session code, connects to essentially any computer or mobile device without pre-installing anything permanent, and can take control with or without the end user present. SOS starts at $22/month per concurrent technician license, or $259–$399/year per technician depending on how many managed computers are bundled in (options scale from 10 to 300 managed computers per license, stacking up to 1,200). An Enterprise Remote Support tier adds SSO, IP whitelisting, cloud session recording, and a service desk integration on top, for environments managing over 1,200 devices.
Pros
Every plan’s price is published — no sales call required to budget
SOS is purpose-built for one-off, code-based support sessions, not just unattended access
Clear upgrade path from individual access (Solo/Pro) to dedicated support tooling (SOS/Enterprise)
Cons
Per-technician licensing on SOS can get expensive fast for larger help-desk teams
Higher-end features (4:4:4 color, 240fps) target creative/technical use cases that most support techs won’t need
Add-ons like Autonomous Endpoint Management and antivirus are priced separately, adding complexity to total cost
Bottom Line
All three tools do the core job — reaching and controlling a remote machine — reliably. The real differences are in how they price and scale. Pick Splashtop if transparent, published pricing and a dedicated on-demand support product (SOS) matter more than brand recognition. Pick TeamViewer if you need enterprise-scale device management, OT support, and built-in AI troubleshooting, and you’re comfortable negotiating a quote. Pick AnyDesk if your main constraint is the sheer number of unattended, managed devices you need to support and you want a clean tier structure to reason about that scale, even without posted dollar amounts.
FAQ
Why don’t TeamViewer and AnyDesk publish prices anymore? Both companies now route most or all plan pricing through a quote request rather than listing it publicly, which this article reflects accurately rather than guessing at figures.
Which tool is best for a one-person IT consultant helping a handful of clients? Splashtop SOS is the easiest to budget for immediately since its per-technician pricing is published and starts relatively low at $22/month.
Are these tools the same as meeting or screen-recording software? No. These three are built for taking control of or accessing another device remotely (IT support, unattended servers), not for hosting video meetings or recording your own screen for later playback.
Do any of these offer a free tier? TeamViewer and AnyDesk both offer limited free versions for personal, non-commercial use (confirm current terms directly with each vendor); Splashtop’s plans listed here are paid, business-oriented tiers.
“AI accounting” means very different things depending on which vendor is saying it. Some products are built from the ground up as AI-first finance platforms. Others are AI features layered onto a card, spend, or bookkeeping product you already use. Vic.ai, Ramp, and QuickBooks’ Intuit Assist sit at three different points on that spectrum, and picking the wrong one for your situation means paying for capability you’ll never touch — or missing automation you actually needed.
Autonomous invoice processing with claimed 99% accuracy
Ramp
AI features bundled into a corporate card & spend-management platform
Companies that want AI-assisted coding and close baked into card/expense workflows
Free plan available; Plus from $15/user/mo plus a platform fee
Auto-coding of transactions and automated accrual/close workflows
QuickBooks (Intuit Assist)
AI feature bundled into QuickBooks Online — not a separate product
Small businesses already running QuickBooks Online
Included at no extra cost (for now) on QBO plans starting at $38/mo list
Turns forwarded emails/photos into draft invoices, bills, and estimates
Short Verdict
These three aren’t really competitors — they’re answers to different questions. If your question is “can AI run our entire AP department,” look at Vic.ai, a purpose-built, standalone automation platform for finance teams with real invoice volume. If your question is “can our card and spend platform also handle the coding and month-end grind,” Ramp bundles that in as part of its broader spend-management suite. If your question is “can QuickBooks save me time without buying anything else,” Intuit Assist is a free-for-now layer already sitting inside the software you probably use. None of them compete head-to-head on price because two of the three don’t have a standalone price at all — they’re features, not products.
Vic.ai: A Standalone AI-First AP Platform
Vic.ai is not a feature bolted onto another tool — it’s a dedicated accounts payable and finance automation platform built around AI from the start. Its core pitch is “autonomous invoice processing” that reads, codes, and routes invoices with minimal human touch, aimed at cutting both error rates and the time it takes to close the books each month.
The platform is organized into several modules: an AI-powered AP inbox for incoming invoices, a bill-pay and vendor-portal tool, a corporate card and non-payroll expense module, and an analytics layer that tracks invoice throughput and team productivity. It connects to major ERP systems including Sage Intacct, Oracle NetSuite, Workday, SAP S/4HANA, and Microsoft Dynamics, which signals where it’s aimed: mid-market and enterprise finance teams running real transaction volume, not a solo founder doing their own books.
Vic.ai markets itself heavily toward CFOs, controllers, and AP managers in freight and logistics, construction, manufacturing, and retail — industries with high invoice volume and complex vendor relationships. The company publicizes performance claims including 5x faster invoice processing, an 85% “no-touch” rate by month six of deployment, 99% invoice accuracy, and a roughly seven-month payback period. These are vendor-reported figures rather than independently audited benchmarks, so treat them as a starting point for your own evaluation rather than a guarantee.
Pricing is not published. Vic.ai sells through a demo-and-quote process, which is standard for enterprise AP software but means you can’t comparison-shop by price the way you can with Ramp or QuickBooks.
Pros
Built specifically for AP automation, not a side feature of a broader platform
Deep ERP integrations suited to mid-market/enterprise accounting stacks
Dedicated modules for invoice processing, bill pay, cards, and analytics
Cons
No public pricing — every deal requires a sales conversation
Overkill for small businesses with low invoice volume
Performance stats are vendor-reported, not third-party verified
Ramp’s AI Features: Automation Bundled Into a Spend Platform
Ramp is first and foremost a corporate card and business spend-management platform. Its AI accounting capabilities — marketed under the “Ramp Intelligence” and “Stack by Ramp” banners — are features layered on top of that platform, not a separate product you can buy on their own. That distinction matters: you’re adopting Ramp’s cards, bill pay, and expense tooling to get the AI, not subscribing to an AI accounting product in isolation.
The accounting-specific AI features center on four things. Auto-coding uses transaction details and your historical coding patterns to fill in GL accounts, classes, and other fields automatically, showing its confidence level and reasoning; Ramp states roughly nine in ten codings are correct on the first pass. Review flags transactions for approve/fix/investigate action. Auto-sync pushes transactions marked “ready” straight to your ERP once they meet policy and confidence thresholds. Close automation creates, posts, and reverses accruals and reconciles them against your ERP with links back to the source transaction — aimed squarely at shortening month-end close. Ramp has also rolled out AI agents for expense-approval workflows and spend analytics as part of ongoing 2025–2026 product releases.
Ramp’s pricing is tiered: a Free plan at $0/month/user, a Plus plan starting at $15/month per user plus a separate platform fee based on team size, and custom Enterprise pricing billed annually. Procurement and Accounts Receivable are separate add-ons, and 1099 filing runs $0.65 per IRS filing. The AI accounting features sit inside these existing card/spend tiers rather than carrying their own line-item price.
Pros
AI coding and close automation are included as part of an already-useful card/spend platform
Free tier exists, lowering the barrier to try the AI features
Broad ERP sync for auto-coded transactions
Cons
You can’t buy the AI accounting layer without adopting Ramp’s card/spend ecosystem
Bill pay and AI agent details are thin on Ramp’s own public pages
Platform fee on paid tiers isn’t disclosed up front — requires a sales conversation
QuickBooks’ Intuit Assist: AI Baked Into Software You Already Own
Intuit Assist is the clearest example of “feature, not product” on this list. It’s a generative-AI assistant built directly into QuickBooks Online (and QuickBooks Online’s mobile web experience) — there is no separate SKU, login, or subscription for it. If you’re already a QuickBooks Online customer, it shows up inside the product you’re using.
Its party trick is turning unstructured inputs into structured accounting records: forward an email, upload a photo of a handwritten note, or scan a document, and Intuit Assist drafts an estimate, invoice, or bill for you to review and send. It also scans for overdue invoices and drafts personalized reminder messages, extracts line-item detail from receipts and auto-fills the expense category/vendor/payment account, and matches QuickBooks Payments or Bill Pay transactions to the right bank line. All of this surfaces on a “Business Feed” homepage inside QuickBooks Online that collects drafted items for your review before anything is finalized.
Critically, Intuit says Intuit Assist is currently offered at no additional cost to eligible QuickBooks Online users in the United States — but it explicitly reserves the right to change pricing, terms, or availability, or discontinue the feature entirely. Some capabilities, like invoice reminders, aren’t available on every plan tier (QuickBooks Online Advanced is called out as an exception for at least one feature). As of the most recent QuickBooks Online pricing, the plans Intuit Assist rides on top of are Simple Start at a $38/month list price, Essentials at $85/month, Plus at $140/month, and Advanced at $340/month, with introductory discounts commonly available for new customers.
Pros
No separate purchase or setup — it’s already inside QuickBooks Online
Genuinely useful for turning messy inputs (photos, forwarded emails) into draft records
Currently free to use on top of your existing QuickBooks subscription
Cons
Not a standalone tool — you must already be paying for QuickBooks Online
“Free for now” language means Intuit could start charging or pull features later
Feature availability varies by plan tier and is US-only at launch
Built for small-business bookkeeping, not high-volume AP automation
Bottom Line
Match the tool to the shape of your problem, not the hype around “AI accounting.” Vic.ai is the only standalone product of the three and makes sense when invoice volume and AP complexity justify a dedicated platform and its custom-quote pricing. Ramp makes sense when you want AI-assisted coding and close automation as part of adopting a modern card and spend-management stack — you’re buying the platform, and the AI comes along for the ride. Intuit Assist makes sense for small businesses that just want QuickBooks to do more of the typing for them, at no extra cost, with no new vendor relationship to manage. For most small businesses already on QuickBooks, start with Intuit Assist since it costs nothing extra; graduate to Ramp if card spend and expense coding are the real pain point; reach for Vic.ai only once AP volume alone justifies a dedicated automation budget.
FAQ
Is Vic.ai an accounting software replacement? No. Vic.ai automates AP workflows (invoice capture, coding, approvals, payments) and integrates with your existing ERP or accounting system — it doesn’t replace your general ledger software.
Can I use Ramp’s AI accounting features without using Ramp cards? Ramp’s public pages don’t describe a way to buy the AI coding/close features as a standalone product separate from its card and spend platform. Expect to adopt Ramp’s broader ecosystem to get the AI layer.
Will Intuit Assist always be free? Intuit explicitly states pricing and availability may change and the feature could be discontinued, so “free” should be read as “free for now,” not a permanent commitment.
Which one is right for a very small business with simple books? Intuit Assist, since it’s already included if you use QuickBooks Online and requires no new tool or vendor relationship.
Short verdict: If you’re a single-marketplace Amazon seller spending under $10K/month on ads and want a clear flat rate, Teikametrics‘ Essentials plan is the easiest to budget for and comes with a free trial. If you’re scaling past $10K/month in ad spend and want deeper AI bid automation on Amazon specifically, Perpetua‘s Essentials or Growth tier is the strongest fit. If you’re an agency or large multi-retailer brand that needs Amazon, Walmart, Target, Instacart, and more under one roof, Pacvue is built for that scale — but, like ServiceTitan in field service software, it publishes no public pricing and requires a sales conversation.
This comparison is scoped specifically to Amazon (and, where relevant, Walmart) marketplace PPC and retail media optimization — bid automation, keyword harvesting, Amazon Marketing Cloud (AMC) reporting, and seller/vendor advertising workflows. It’s a different category from general Google Ads or Meta Ads management platforms already covered elsewhere on this site.
At a Glance
Tool
Starting Price
Ad Spend Threshold
Marketplaces
Best For
Perpetua
$695/mo (Essentials)
Up to $10K/mo included; Growth kicks in above that with a % of spend
Amazon-focused (AMC, Amazon Marketing Stream)
Amazon-only brands wanting deep AI bid automation
Pacvue
Custom quote only
Not published
100+ retailers across 30+ countries, incl. Amazon, Walmart, Target, Instacart
Agencies and large brands managing many retail media channels
Teikametrics
$149/mo annual ($179/mo monthly) (Essentials)
Up to $10K/mo included; Advanced/Enterprise add 3% of spend above $10K
Amazon and Walmart
Emerging sellers wanting an affordable, transparent entry plan
Prices above come directly from each vendor’s own pricing page as of November 2026 and are subject to change — confirm current rates before signing up.
Perpetua: Pricing and What You Get
Perpetua publishes three tiers, gated by monthly ad spend rather than user count:
Essentials ($695/mo, up to $10K/mo ad spend): AI-powered bid optimization, automated keyword harvesting, performance and profitability reporting, and data-driven recommendations. Support is via chat, a Slack community, and video tutorials through “Ad School.”
Growth ($695/mo plus a percentage of ad spend, for accounts over $10K/mo): adds hourly reporting and intraday optimization through Amazon Marketing Stream, hourly share-of-voice and organic rank insights, revenue opportunity analysis, competitor search term data, and a dedicated Client Success team.
Premium (custom pricing, for accounts over $500K/mo ad spend): adds competitor and market intelligence data, custom AMC reporting, custom data integrations, beta feature access, and a dedicated account team with white-glove onboarding.
Perpetua’s pricing page doesn’t mention a free trial — the only calls to action are “Get Started” and “Book a Demo.” Its feature set is built specifically around Amazon advertising (AMC, Amazon Marketing Stream, Amazon PPC), with no mention of Walmart or other retail media channels.
Pacvue: Why There’s No Published Price
Pacvue positions itself as an “AI-Powered Commerce Media OS” spanning retail media management, digital shelf optimization, revenue recovery, measurement, and AI agent tooling (Pacvue Agent and Pacvue Prism). Its public site lists no plans, tiers, or dollar figures anywhere — the only call to action across the marketing site is “Book a demo,” and there’s no separate pricing page to check. That makes Pacvue a quote-only product, similar to how ServiceTitan operates in field service software: you can’t self-serve a price, so budget comparisons against Perpetua and Teikametrics aren’t possible without contacting sales directly.
What is clear from the site is scope: Pacvue covers 100+ retailers and partners across 30+ countries, including Amazon, Walmart, Target, Instacart, Kroger, Chewy, eBay, Tesco, Carrefour, DoorDash, Sam’s Club, and Ace Hardware, plus programmatic and social channels like The Trade Desk, Yahoo DSP, Reddit, and Pinterest. It markets to both brands and agencies, and claims it’s used by “5 of 5” of the largest media agencies. That breadth — not price — is Pacvue’s main differentiator against the other two tools here, which focus primarily on Amazon (and, for Teikametrics, Walmart).
Teikametrics: Pricing and What You Get
Teikametrics publishes three tiers built around its “ARI” (Ads, Catalog, Inventory, Insights) strategic suite:
Essentials ($149/mo billed annually, $179/mo billed monthly, up to $10K/mo ad spend): the ARI suite plus Refunds Recovery. Marketed to “emerging marketplace sellers” on Amazon or Walmart. Offers a free trial.
Advanced (custom pricing, listed as +3% of ad spend above $10K/mo): adds Amazon DSP and Walmart Onsite Display management, integrated Amazon Marketing Cloud (AMC) reporting, dedicated onboarding, profitability dashboards, and an optional Managed Services add-on. Marketed to brands expanding across 2+ marketplaces. No free trial listed; the CTA is a “Free Opportunity Assessment.”
Enterprise (custom pricing, also listed as +3% of ad spend above $10K/mo — likely a copy error on Teikametrics’ page, since Enterprise is marketed for accounts over $100K/mo): adds customizable dashboards/reporting and full Teikametrics Managed Services. Marketed to “established retail leaders running multi-market operations.”
Teikametrics is the only one of the three with a genuinely self-serve, published entry price and a free trial, making it the most approachable option for a smaller or newer Amazon/Walmart seller who wants to try the software before committing.
Perpetua vs Teikametrics: The Two You Can Actually Price Out
Since Pacvue won’t quote a number without a sales call, the real head-to-head on price is Perpetua against Teikametrics:
Entry price: Teikametrics’ Essentials plan ($149–$179/mo) is dramatically cheaper than Perpetua’s Essentials plan ($695/mo) for sellers under the $10K/mo ad spend threshold — both tiers cover the same spend ceiling, but at very different price points.
Free trial: Teikametrics offers one; Perpetua doesn’t appear to, based on its pricing page’s calls to action.
Marketplace breadth: Teikametrics explicitly supports Walmart alongside Amazon (including Walmart Onsite Display on its Advanced tier); Perpetua’s public pricing page is Amazon-only.
Depth of AMC and intraday tooling: Perpetua leans harder into Amazon Marketing Stream and AMC-specific reporting even at its mid tier (Growth), whereas Teikametrics reserves AMC integration for its Advanced tier and up.
Scaling model: Both move to a percentage-of-spend model once you cross $10K/mo, but Teikametrics states its percentage explicitly (3% above $10K), while Perpetua’s Growth tier pricing beyond the flat $695/mo base isn’t spelled out in exact percentage terms on the page.
Pros and Cons
Perpetua
Pros: Deep, Amazon-specific AI bid automation; strong AMC and Amazon Marketing Stream integration even at the Growth tier; active community and training (Ad School). Cons: Highest entry price of the three for sub-$10K/mo sellers; no published free trial; Amazon-only on its public pricing page, with no Walmart support mentioned.
Pacvue
Pros: By far the broadest retailer and channel coverage (100+ retailers, 30+ countries); built for agencies managing many brands and many retailers at once; includes programmatic/social and AI agent tooling beyond pure Amazon PPC. Cons: Zero published pricing, so you can’t budget without booking a demo; the breadth that makes it powerful for agencies can be overkill for a single-marketplace Amazon seller.
Teikametrics
Pros: Lowest, clearest entry price of the three; genuine free trial; explicit Amazon + Walmart support even at lower tiers. Cons: AMC integration and DSP/Onsite Display management are reserved for the Advanced tier and up; the Enterprise tier’s pricing text on the vendor’s own page appears to duplicate Advanced’s terms rather than clearly stating its own.
Who Should Choose What
Choose Teikametrics if you’re an emerging Amazon or Walmart seller under $10K/mo in ad spend who wants the cheapest, most transparent entry point and a free trial before paying anything.
Choose Perpetua if you’re Amazon-focused specifically, already spending meaningfully on ads, and want the deepest AI-driven bid automation and AMC/Marketing Stream tooling, even if it costs more upfront.
Choose Pacvue if you’re an agency or a brand operating across many retailers beyond just Amazon — Walmart, Target, Instacart, and dozens more — and you need one platform to manage all of it, custom pricing and sales process included.
Bottom Line
Teikametrics and Perpetua are the two Amazon PPC tools you can actually compare dollar-for-dollar, since both publish real entry pricing — and for most single-marketplace Amazon sellers under $10K/mo in spend, Teikametrics’ lower price and free trial make it the easier first step. Perpetua earns its higher price with deeper, Amazon-specific automation and reporting once your spend justifies it. Pacvue is a different animal entirely: it’s the retail-media platform built for agencies and multi-retailer brands that need Amazon, Walmart, Target, and dozens of other channels under one roof, and like several enterprise software categories, it simply won’t tell you what that costs until you talk to sales.
FAQ
Which tool is cheapest for a small Amazon seller?
Teikametrics’ Essentials plan, at $149/mo billed annually (or $179/mo month-to-month) for up to $10K/mo in ad spend, is the cheapest published entry point of the three. Perpetua’s equivalent Essentials tier costs $695/mo for the same spend ceiling. Pacvue doesn’t publish pricing at all.
Do these tools support Walmart, not just Amazon?
Teikametrics explicitly supports Walmart alongside Amazon, including Walmart Onsite Display on its Advanced tier. Perpetua’s public pricing page focuses on Amazon only, with no mention of Walmart. Pacvue supports Walmart along with 100+ other retailers, per its site, though exact feature parity across retailers isn’t detailed publicly.
Why won’t Pacvue list its prices?
Pacvue’s marketing site has no dedicated pricing page and no plan tiers listed anywhere; its only call to action is to book a demo. This is common among enterprise retail-media and commerce platforms that serve agencies and large brands with highly variable scope — the number of retailers, markets, and ad formats you need changes the cost enough that vendors prefer to quote per deal rather than publish a flat rate.
What happens to pricing once I cross $10K/month in ad spend?
Both Perpetua and Teikametrics move away from a flat monthly fee once you exceed $10K/mo in ad spend. Teikametrics states this explicitly as an additional 3% of spend above that threshold on its Advanced and Enterprise tiers. Perpetua’s Growth tier keeps the $695/mo base but adds a percentage of spend without stating the exact rate on its public pricing page — ask their sales team for the specific figure that applies to your account.
Short verdict: If you run a solo operation or a small home-service crew and want transparent, self-serve pricing, start with Jobber. If you need heavier dispatch, route optimization, and multi-marketplace payment tools and don’t mind paying more per seat, Housecall Pro‘s Essentials or Max plan fits better. If you’re running a multi-crew HVAC, plumbing, or electrical operation with real back-office complexity, ServiceTitan is built for that scale — but you’ll need to request a quote, because it publishes no public pricing at all.
At a Glance
Tool
Starting Price
Pricing Model
Best For
Free Trial
Jobber
From $29/mo (Core, 1 user, billed annually)
Flat monthly fee by tier, scales with user count
Solo operators and small home-service teams
14 days, full Grow-plan access, no card required
Housecall Pro
From $59/mo (Basic, 1 user, billed annually)
Flat monthly fee by tier, scales with user count
Small-to-mid teams wanting heavier automation and dispatch
14 days, full Max-plan access, no card required
ServiceTitan
Custom quote only (per technician)
Quote-based; no published pricing
Larger multi-crew HVAC, plumbing, and electrical operations
No published free trial
Prices above are taken directly from each vendor’s own pricing page as of November 2026. Field service software pricing changes often, so confirm current rates before you commit.
Jobber: Pricing and What You Get
Jobber is built around four tiers — Core, Connect, Grow, and Plus — and each tier’s price climbs with the number of users you add. Billed annually, the published rates are:
Core (1 user): $29/mo — online booking and scheduling, quotes and invoices, online payments, a basic website, and reporting.
Grow (1–15 users): $149–$399/mo — adds two-way SMS, job costing, automatic time tracking, and custom workflow automations.
Plus (5–15 users): $399–$529/mo — adds unlimited photo/video storage, crew scheduling, profitability alerts, custom reports, and an AI receptionist.
Additional seats beyond a plan’s included count cost $29/mo each. Month-to-month billing without an annual or 1-year commitment costs noticeably more — Jobber advertises “save up to 25% with annual billing,” and the no-commitment Core price is $49/mo versus $29/mo billed annually. The free trial runs 14 days with full access to Grow-tier features and no credit card required.
Housecall Pro: Pricing and What You Get
Housecall Pro uses three tiers — Basic, Essentials, and Max — priced lower when billed annually:
Basic (1 user): $59/mo annually ($79/mo month-to-month) — online booking, scheduling and dispatch, estimates and invoicing, payments, price book, and review management.
Max (8 users): $299/mo annually ($329/mo month-to-month) — adds a sales proposal tool, recurring service plans, route optimization, open API access, and a dedicated onboarding specialist. Extra users cost $35/mo each.
Every Housecall Pro plan includes live phone and chat support, mobile apps, and built-in card processing. At the time of research, the site was also advertising 50% off the first three months — a promotional rate that may not be current when you check, so verify it directly on the pricing page. The 14-day free trial gives full access to Max-tier features with no credit card required.
ServiceTitan: Why There’s No Published Price
ServiceTitan doesn’t publish a single dollar figure anywhere on its pricing page. Instead, it lists three tiers — Starter, Essentials, and The Works — each gated behind a “Request Pricing” button, and the page states plainly that pricing is “per-technician” and tailored to your business. There’s no self-serve signup and no advertised free trial; you move forward with a sales conversation and a demo.
Starter: dispatching, scheduling, call booking, invoicing, and a pricebook.
Essentials: everything in Starter, plus mobile estimates and payroll management.
The Works: everything in Essentials, plus configurable payroll, and (per the page’s layout) advanced reporting, commission tracking, and customizable memberships.
Third-party review sites that track vendor cost data, such as Software Advice, list ServiceTitan’s starting price as “available upon request” with no free trial, and cite user reviews describing the software as high-cost relative to smaller field service tools, with one reviewer citing a roughly $22,000 contract exit cost — a single user’s claim, not a verified figure. We can’t responsibly state an actual monthly or per-technician price here because ServiceTitan has not published one; any number you see quoted elsewhere online is a third-party estimate, not an official rate.
Jobber vs Housecall Pro: Where They Actually Differ
Both target the same core market — plumbers, electricians, HVAC techs, cleaners, landscapers, and similar home-service pros — and both offer online booking, scheduling, invoicing, and payments at the entry tier. The practical differences show up as you scale:
Entry price: Jobber’s Core plan ($29/mo annually) undercuts Housecall Pro’s Basic plan ($59/mo annually) for a single user, making Jobber the cheaper starting point for true solo operators.
Dispatch depth: Housecall Pro’s Essentials and Max tiers lean harder into dispatch, route planning, and GPS tracking earlier in the lineup, which matters more once you’ve got several trucks in the field on the same day.
Marketing and AI tools: Jobber’s top Plus tier adds a built-in Marketing Suite and AI Receptionist that Housecall Pro doesn’t directly mirror at the same tier.
Extra-user cost: Jobber charges $29/mo per added seat; Housecall Pro charges $35/mo, a detail that adds up for teams in the 10–20 user range.
Pros and Cons
Jobber
Pros: Lowest published entry price; clear, self-serve pricing page; strong QuickBooks sync; Marketing Suite and AI Receptionist at the top tier. Cons: Per-user pricing climbs quickly past 10 seats; some automation and reporting features are locked to the Grow and Plus tiers.
Housecall Pro
Pros: Built-in route optimization and GPS tracking show up earlier in the plan ladder; open API access on Max; dedicated onboarding specialist included at the top tier. Cons: Higher entry price than Jobber for a single user; extra seats cost more per user than Jobber’s.
ServiceTitan
Pros: Purpose-built for larger, multi-crew residential and commercial trades operations; deep payroll, commission, and membership-management features at the top tier. Cons: No published pricing anywhere, so you can’t budget without a sales call; no advertised free trial; third-party reviews repeatedly flag cost as a pain point relative to SMB-focused tools.
Who Should Choose What
Choose Jobber if you’re a solo operator or a small team (1–10 people) who wants the lowest entry price and clear, published rates you can budget against today.
Choose Housecall Pro if you need stronger dispatch, route planning, and GPS tracking a tier or two earlier, and you’re comfortable paying somewhat more per seat for it.
Choose ServiceTitan if you’re running a larger trades business with multiple crews and real payroll/commission complexity, and you’re prepared to go through a sales process rather than self-serve signup.
Bottom Line
Jobber and Housecall Pro are the two field service platforms you can actually compare on price today, since both publish full rate cards. Jobber wins on entry-level affordability; Housecall Pro front-loads more dispatch and routing power. ServiceTitan plays a different game entirely — it’s an enterprise-grade platform for larger trades operations, and its refusal to publish any pricing means you should treat it as a “request a demo and negotiate” purchase, not a line item you can compare dollar-for-dollar against the other two.
FAQ
Which is cheapest for a one-person operation?
Jobber’s Core plan, at $29/mo billed annually for one user, is the cheapest published entry point of the three. Housecall Pro’s Basic plan starts at $59/mo annually for one user. ServiceTitan doesn’t publish a price, but its per-technician, enterprise-oriented model is generally not aimed at single-operator businesses.
Why doesn’t ServiceTitan list its prices?
ServiceTitan sells per-technician pricing tailored to each business’s size, trade mix, and feature needs, and every tier on its pricing page routes to a “Request Pricing” form rather than a dollar amount. This is common for software aimed at larger, more complex operations where implementation and configuration vary a lot business to business.
Do Jobber and Housecall Pro offer free trials?
Yes. Both offer a 14-day free trial with no credit card required, and both give full access to their top-tier features (Grow for Jobber, Max for Housecall Pro) during the trial period.
Can I switch between these tools later?
Most field service platforms, including all three here, support CSV or guided data migration for customers, jobs, and invoices, though the process and support level vary. If you’re on ServiceTitan, review your contract terms carefully — reported exit costs can be substantial for enterprise contracts.
EU regulators, works councils, and increasingly cautious public-sector buyers have spent the past few years pushing the big three US hyperscalers toward a specific promise: your data, and ideally your cloud operations, stay inside the EU/EEA, governed by EU law, run by EU-based staff. Each of AWS, Google Cloud, and Microsoft has answered differently, on a different timeline, and — as of 2026 — with meaningfully different degrees of “done.” This piece separates what’s actually live today from what’s still a roadmap item.
AT A GLANCE
Offering
Status as of 2026
Scope
Key detail
AWS European Sovereign Cloud
Generally available — launched January 15, 2026
New, physically/logically separate AWS partition; first Region in Brandenburg, Germany
Operated exclusively by EU residents, with independent EU governance entities; no critical dependency on non-EU AWS infrastructure; >90 services at launch; Local Zones planned for Belgium, Netherlands, Portugal
Google Cloud EU Data Boundary / sovereign controls
Partially live — rolled out incrementally via Assured Workloads since 2021, still expanding
Per-workload controls layered onto existing Google Cloud regions, not a separate partition
EU-only data residency (5+ EU regions), cryptographic Key Access Justifications, and EU-based support; relies partly on third-party sovereign partners (e.g. T-Systems, Thales) for full operational sovereignty
Microsoft EU Data Boundary for the Microsoft Cloud
Completed — final phase finished February 26, 2025
Existing Microsoft 365, Dynamics 365, Power Platform, and most Azure services, EU/EFTA-wide
Customer data, pseudonymized personal data, and technical-support data now stored/processed in EU/EFTA; limited exceptions remain for coordinated global security response
Short Verdict
These three offerings are not apples-to-apples. Microsoft’s EU Data Boundary is the most mature as a data residency commitment layered on its existing cloud — it’s been rolling out since 2023 and Microsoft says it completed the final phase in February 2025. AWS has gone furthest on operational sovereignty — a new, separate cloud partition with its own EU-resident leadership and governance structure, but it only reached general availability in January 2026 and currently has just one live region. Google Cloud’s approach is the most incremental and partner-dependent: real, usable controls (data residency, cryptographic access justifications, EU support) have existed in some form since 2021, but full “operational sovereignty” explicitly leans on third-party partners like T-Systems and Thales rather than being delivered end-to-end by Google alone.
What “Sovereign Cloud” Actually Means — Three Different Things
Vendors and analysts use “sovereignty” loosely, but it generally decomposes into three distinct guarantees, which matters because each vendor delivers a different mix:
Data residency: Data at rest (and ideally in processing) stays within a defined geographic/legal boundary.
Data sovereignty: Cryptographic and policy controls over who can access data and under what legal authority — e.g., blocking or requiring justification for provider-side access tied to non-EU legal requests.
Operational sovereignty: The infrastructure and the people running it — including during outages, legal disputes, or geopolitical disruption — are themselves EU-based and independent of the parent company’s non-EU operations.
AWS European Sovereign Cloud: A Separate, EU-Only Partition
AWS took the most structurally aggressive approach: rather than adding controls to existing regions, it stood up a new, physically and logically separate cloud partition, which reached general availability on January 15, 2026. Per AWS’s own announcement, the new partition has no critical dependencies on infrastructure outside the EU and is designed to keep operating even during a connectivity disruption with the rest of AWS’s global network. It is governed through a dedicated parent company and three German GmbH subsidiaries, led by EU citizens, with an advisory board made up of EU citizens/residents; day-to-day operations and all personnel with access to the infrastructure and customer data are EU residents. The first Region launched in Brandenburg, Germany, with more than 90 services available at launch, and AWS has committed to investing over €7.8 billion in Germany, supporting an estimated 2,800 full-time-equivalent jobs annually. Sovereign AWS Local Zones in Belgium, the Netherlands, and Portugal are planned to extend coverage, though AWS hasn’t published a firm timeline for those. This is the only one of the three offerings that is a genuinely distinct cloud, not an overlay of controls on an existing one.
Google Cloud: Per-Workload Controls, Built Incrementally
Google’s approach runs through Assured Workloads and its EU Data Boundary control package, applied per workload rather than as a separate region or partition. Its current official documentation describes an EU-only resource location constraint restricting workloads to EU regions (including europe-west1, europe-west3, europe-west4, and europe-north1), a minimum TLS version restriction, and a restricted service list so only vetted products/API endpoints are usable inside the boundary — with the most granular restrictions and exceptions documented for BigQuery. The underlying capabilities trace back to Google’s 2021 announcement of sovereign controls for EU customers: EU-only data residency across several regions, Key Access Justifications (cryptographic visibility into, and the ability to deny, each data-access request, tied to Cloud External Key Manager), and EU-based customer support. Google has been explicit that these controls do not by themselves deliver full independent operational sovereignty — for that, it points customers to partner-delivered sovereign offerings such as T-Systems (Germany) and Thales (France), which add independent oversight on top of Google’s technical controls. In other words, Google’s sovereignty story is real but composite: Google provides the technical primitives, and a local partner often provides the operational independence layer.
Microsoft: The Most Complete Data-Residency Rollout
Microsoft’s EU Data Boundary for the Microsoft Cloud is a phased commitment to keep customer data within the EU/EFTA for its core cloud services — Microsoft 365, Dynamics 365, Power Platform, and most Azure services — rather than a new separate cloud. Per Microsoft’s own announcement, the rollout happened in three phases: Phase 1 (January 2023) covered core-service customer data; Phase 2 (January 2024) added pseudonymized personal data; and Phase 3, which Microsoft says completed the boundary, finished in February 2025, adding professional-services/technical-support data (such as support logs and case notes) to the in-region requirement. Microsoft notes that for certain Azure services, customers may need to take additional configuration steps to get the full professional-services data-storage commitment, and that in limited security situations requiring a coordinated global response, some data may still be transferred outside the boundary, with encryption and strict access controls applied. Microsoft frames this alongside its separate Microsoft 365 Advanced Data Residency add-on and its broader Microsoft Cloud for Sovereignty program, which adds policy and operational controls on top of the data boundary for customers who need them.
Comparison: What’s Actually Guaranteed
Guarantee
AWS European Sovereign Cloud
Google Cloud (EU Data Boundary / Assured Workloads)
Microsoft EU Data Boundary
Data residency
Yes — new EU-only partition
Yes — per-workload EU region restriction
Yes — EU/EFTA, phased, now covering support data too
Not the primary mechanism; relies on EU Data Boundary + encryption/access controls
EU-resident operations staff
Yes, by design (new legal entities, EU citizens only)
Partial — relies on partners (T-Systems, Thales) for full independence
Not structurally separate; Microsoft’s global org still operates the service
Independent from parent company’s non-EU infra
Yes — explicitly no critical non-EU dependencies
No — same global Google Cloud infrastructure, EU-scoped
No — same global Microsoft Cloud infrastructure, EU-scoped
Pros and Cons
AWS European Sovereign Cloud
Pros: Strongest operational-independence story of the three; purpose-built legal/governance structure; large committed investment.
Cons: Brand new (GA only since January 2026) — single region, limited service catalog relative to AWS’s full global footprint, and planned Local Zones aren’t live yet.
Google Cloud EU Data Boundary / Sovereign Controls
Pros: Flexible, per-workload controls usable across existing EU regions today; strong cryptographic access-justification tooling; partner ecosystem for full sovereignty where needed.
Cons: Not a fully independent operational entity on its own — true operational sovereignty requires a third-party partner layer; service coverage inside the EU Data Boundary control package is uneven (some products/features explicitly unsupported).
Microsoft EU Data Boundary
Pros: Broadest, most mature phased rollout; covers Microsoft 365, Dynamics 365, Power Platform, and most Azure services; now includes support/technical data, not just customer data.
Cons: Not an operationally independent entity — same global Microsoft infrastructure and staff, just data-residency-scoped; limited exceptions remain for global security response; some Azure services need extra customer configuration for full coverage.
Who Each Is a Good Fit For
Organizations with the strictest regulatory or political requirements — public-sector bodies, defense-adjacent entities, or enterprises in heavily regulated sectors demanding provable EU-only operations — are the target for AWS’s new sovereign partition, accepting its current single-region limitation as a trade-off. Enterprises already standardized on Google Cloud that need EU data residency and strong cryptographic access controls, and are willing to pair Google’s technical controls with a sovereign partner (T-Systems, Thales) for full independence, fit Google’s model well. Organizations whose primary exposure is Microsoft 365/Dynamics/Azure workloads and whose main regulatory concern is “where is our data stored and processed” rather than “who operates the infrastructure” are well served by Microsoft’s now-completed EU Data Boundary.
Bottom Line
All three vendors can now credibly claim EU data residency. Only AWS currently offers a genuinely separate, independently operated EU cloud partition — and it’s brand new, with a single region and a growing-but-still-limited service catalog. Microsoft’s EU Data Boundary is the most completed data-residency commitment of the three, having finished its final rollout phase in February 2025, but it doesn’t change who operates the underlying global infrastructure. Google’s controls are flexible and technically strong but explicitly depend on third-party partners for full operational independence. “Which is more sovereign” depends entirely on which of the three guarantees — residency, cryptographic sovereignty, or operational independence — matters most for your specific regulatory requirement.
FAQ
Is the AWS European Sovereign Cloud available everywhere in the EU? No. As of its January 2026 general availability, it has one live Region, in Brandenburg, Germany, with more than 90 services. Sovereign Local Zones in Belgium, the Netherlands, and Portugal are planned but not yet confirmed as live.
Has Microsoft’s EU Data Boundary fully rolled out? Microsoft says its three-phase rollout completed in February 2025, covering customer data, pseudonymized personal data, and technical-support data for core services across the EU/EFTA, with narrow exceptions for coordinated global security incidents.
Does Google Cloud offer a fully independent sovereign cloud like AWS’s? Not entirely on its own. Google’s EU Data Boundary/Assured Workloads controls deliver strong data residency and cryptographic access controls, but Google has said that full operational sovereignty depends on partnering with local providers like T-Systems or Thales.
What’s the difference between data residency and operational sovereignty? Data residency means your data physically stays within a region. Operational sovereignty means the infrastructure, personnel, and governance running that cloud are themselves independent of the parent company’s non-EU operations — a much higher bar that only AWS’s new partition currently targets directly.
Which offering should an EU public-sector buyer evaluate first? It depends on the specific regulatory requirement, but if the requirement explicitly demands independent EU operation (not just EU data storage), AWS’s European Sovereign Cloud and Google’s partner-backed sovereign offerings (via T-Systems/Thales) are the closest match; if the requirement is primarily data-location-based and the workload is Microsoft 365/Azure-centric, Microsoft’s completed EU Data Boundary may already satisfy it.
Every major browser now claims to protect your privacy, but the actual architecture behind that claim varies enormously. Brave, Firefox, and the DuckDuckGo browser are three of the most-recommended privacy-first options, and all three are free. Because there’s no pricing to compare, this guide focuses on what actually matters for privacy: how each browser blocks trackers, what it does about fingerprinting, what the default search and data-handling setup looks like, and — specifically for DuckDuckGo — whether its desktop browser is still a real, maintained product in 2026, since its history on different platforms has shifted over time.
At a Glance
Browser
Platforms
Tracker/Ad Blocking
Fingerprinting Protection
Notable Extra
Brave
Windows, macOS, Linux, Android, iOS
Built-in Shields, blocks ads by default using EasyList/EasyPrivacy/uBlock Origin-derived lists
Included as part of Shields (per Brave’s own privacy features page)
Built-in Tor integration for private windows
Firefox
Windows, macOS, Linux, Android, iOS
Enhanced Tracking Protection, on by default
Built-in fingerprint blocking, per Firefox’s official features page
Total Cookie Protection isolates cookies per site
DuckDuckGo Browser
Windows, Mac, iOS, Android (desktop app officially limited to Windows and Mac)
Blocks third-party trackers from companies like Facebook and Google by default, per duckduckgo.com/app
Not explicitly detailed on the official app page
Built-in email tracker blocking and one-click “Fire Button” data clearing
Short Verdict
All three are legitimate privacy-first choices, and the differences are more about architecture and ecosystem than about one being “unsafe.” Brave leans hardest into blocking by default and adds Tor access for an extra layer of anonymity. Firefox is the most transparent about its tracking protection levels and has the longest track record as an independent, non-Chromium engine. DuckDuckGo Browser — confirmed still actively offered for Windows, Mac, iOS, and Android as of this writing — leans on simplicity: block trackers, block ads, and give you a one-tap way to erase everything.
Brave: Aggressive Default Blocking Plus Built-In Tor
Brave’s core privacy feature is Shields, which per Brave’s own privacy features page blocks trackers, cross-site cookie tracking, and browser fingerprinting by default — you can click the Shields icon in the address bar to see exactly what was blocked on any given page. Brave states its blocking draws on EasyList, EasyPrivacy, uBlock Origin’s lists, plus lists Brave itself maintains, and the company claims this blocks more unwanted tracker resources than other browsers (a claim made on Brave’s own site, not independently verified here).
Beyond Shields, Brave includes query-parameter filtering (stripping known tracking parameters out of URLs you click), bounce-tracking protections, and optional social media embed/login blocking you can configure at brave://settings/socialBlocking. Brave’s most distinctive feature is built-in Tor integration for private windows — you can open a private window that routes your traffic through Tor’s network to mask your IP address, directly from the browser, without installing a separate Tor Browser. Brave notes this can slow browsing speed, which is an expected trade-off of Tor routing.
Firefox: Cookie Isolation and Transparent Tracking Protection
Firefox’s flagship privacy feature is Total Cookie Protection, which, per Mozilla’s official features page, confines cookies to the site that set them so that “cookies can’t follow you across sites” — activity on one site stays on that site rather than being used to build a cross-site profile of you. Firefox also runs Enhanced Tracking Protection automatically, which Mozilla describes as blocking trackers “by default,” with the site citing an example of blocking over a thousand tracking attempts in a short browsing session.
Separately, Firefox includes built-in fingerprint blocking — Mozilla’s features page states Firefox “helps block browser fingerprinting with built-in protections,” aimed at preventing sites from identifying you via device/browser characteristics even when cookies are blocked. Firefox has long offered more granular control than most browsers (via its Standard/Strict/Custom tracking protection levels in settings), though the exact breakdown of what each level blocks is documented in Mozilla’s support pages rather than its marketing pages.
DuckDuckGo Browser: Still Alive and Actively Offered in 2026
DuckDuckGo’s desktop browser has had a winding path — it launched in open beta on Windows and Mac years ago after first building a mobile app and browser extension. As of this writing, DuckDuckGo’s own app page confirms the desktop browser is still being actively offered, with the site explicitly stating: “The DuckDuckGo desktop browser is only available on Windows and Mac operating systems.” Mobile apps are available for iOS and Android as well.
Per DuckDuckGo’s own app page, the browser blocks third-party trackers from companies like Facebook and Google by default, blocks most ads and cookie pop-ups, includes a built-in password manager, blocks hidden email trackers, and offers a one-click button that deletes all open tabs and browsing data at once (DuckDuckGo calls this the Fire Button in its broader documentation). The official page is lighter on technical detail about fingerprinting protection specifically than Brave’s or Firefox’s pages are — it doesn’t make an explicit fingerprinting-protection claim the way the other two do, so if fingerprint resistance is your top priority, that’s a gap worth noting rather than assuming is covered.
Privacy Architecture Comparison
Feature
Brave
Firefox
DuckDuckGo Browser
Default tracker blocking
Yes (Shields, on by default)
Yes (Enhanced Tracking Protection, on by default)
Yes (third-party trackers blocked by default)
Fingerprinting protection claimed
Yes, part of Shields
Yes, dedicated fingerprint blocking feature
Not explicitly detailed on the official app page
Cross-site cookie isolation
Via Shields’ cross-site tracking blocking
Yes — Total Cookie Protection
Blocks third-party trackers; not framed the same way
Anonymity network built in
Yes — Tor integration for private windows
No built-in Tor (separate Tor Browser exists from Mozilla-adjacent project)
No
One-click data wipe
Standard private window/clear browsing data
Standard clear browsing data controls
Yes — dedicated one-click Fire Button-style control
Pros and Cons
Brave
Pros: Aggressive default blocking; built-in Tor access for private windows without a separate app; available on every major desktop and mobile platform.
Cons: Built on Chromium, which means it inherits some of Google’s engine-level telemetry surface area even though Brave strips and blocks much of it; its own crypto/rewards features (not covered here) add complexity some privacy purists avoid.
Firefox
Pros: Independent, non-Chromium engine; clearly documented Total Cookie Protection and fingerprint blocking; long-standing reputation and active Mozilla backing.
Cons: No built-in anonymity network like Tor integration; some advanced protections require manually switching to “Strict” mode rather than being maximal by default.
DuckDuckGo Browser
Pros: Simple, opinionated privacy defaults; built-in email tracker blocking and quick data-clearing; same company behind the privacy-respecting DuckDuckGo search engine as the default.
Cons: Desktop app is limited to Windows and Mac only (no native Linux desktop browser); official marketing page doesn’t make the same explicit fingerprinting-protection claims Brave and Firefox do.
Who It’s a Good Fit For
Choose Brave if you want the most aggressive out-of-the-box blocking plus occasional built-in Tor access, and you’re fine with a Chromium-based browser.
Choose Firefox if you want an independent browser engine with clearly documented cookie isolation and fingerprint protection, and you value Mozilla’s non-profit-adjacent governance.
Choose DuckDuckGo Browser if you want the simplest possible “just block everything and give me an easy reset button” experience, especially if you’re already using DuckDuckGo search.
Who Should Look Elsewhere
Linux desktop users who specifically want DuckDuckGo’s browser will need to look elsewhere — its desktop app is limited to Windows and Mac. Anyone who wants Tor-level anonymity as a core requirement, not just an occasional private-window feature, is generally better served by the dedicated Tor Browser rather than any of these three. And if cross-device sync with a large ecosystem of extensions matters most, Firefox and Brave (both of which support browser extensions more broadly) will serve you better than DuckDuckGo’s more locked-down, simplicity-first browser.
Bottom Line
There’s no financial reason to pick one over another — all three are free — so the decision comes down to architecture and philosophy. Brave gives you the most built-in tooling (including Tor) layered on a familiar Chromium base. Firefox gives you an independent engine with transparent, well-documented protections. DuckDuckGo Browser gives you the simplest, most opinionated defaults, confirmed still actively maintained for Windows, Mac, iOS, and Android as of 2026, though it’s narrower in platform reach and extension support than the other two. Any of the three is a meaningful privacy upgrade over an unconfigured mainstream browser.
FAQ
Is DuckDuckGo’s desktop browser discontinued?
No. As of this writing, DuckDuckGo’s official app page lists the desktop browser as currently available for Windows and Mac, alongside mobile apps for iOS and Android. It is explicitly described as limited to those two desktop operating systems — there’s no native Linux desktop version.
Does Brave block fingerprinting as well as Firefox?
Both browsers advertise fingerprinting protection as part of their default privacy features — Brave bundles it into Shields, and Firefox offers a dedicated fingerprint-blocking feature. Neither company’s own marketing page gives a detailed technical breakdown sufficient to declare one definitively stronger than the other.
Which of these three has a built-in VPN or Tor access?
Brave is the only one of the three with built-in Tor integration for private browsing windows, per Brave’s own privacy features page. Firefox and DuckDuckGo Browser don’t include a built-in anonymity network of that kind.
Are any of these three based on Google Chrome’s code?
Brave is built on Chromium, the open-source project that also underlies Google Chrome, though Brave replaces Chrome’s default tracking and ad behavior with its own Shields system. Firefox uses Mozilla’s independent Gecko engine, not Chromium.
Every enterprise automation stack eventually hits the same wall: RPA bots and iPaaS connectors are great at moving data between two systems, but someone still needs to coordinate the multi-day, multi-system, multi-team process that ties those steps together — an order that has to wait on a payment, retry a failed shipment call, and escalate to a human if nothing happens for 48 hours. That coordination job belongs to a different category of tool: the workflow orchestration engine. This guide compares three of the most widely used options in 2026 — Camunda, Temporal, and AWS Step Functions — and explains how they differ from the RPA platforms and iPaaS tools already covered on this site.
A workflow orchestration engine’s job is to durably track the state of a long-running process — one that might take seconds or might take weeks — survive crashes and deploys without losing progress, retry failed steps automatically, and give developers or business analysts visibility into exactly where each instance of the process stands. That’s a materially different problem from RPA (automating clicks and keystrokes inside existing applications) or iPaaS (triggering an action in one SaaS app when something happens in another). Camunda, Temporal, and AWS Step Functions all solve the orchestration problem, but they start from very different design philosophies.
At a Glance
Tool
Core Model
Best For
Hosting
Pricing
Camunda
BPMN/DMN visual process models
Business-IT collaboration on regulated, auditable processes
SaaS or self-managed
Free local dev tier; SaaS trial; Enterprise is quote-based
Temporal
Code-first durable execution (workflows as code)
Engineering teams orchestrating distributed systems and microservices
Self-hosted (open source) or Temporal Cloud
Temporal Cloud: pay-as-you-go, $50 per million Actions plus storage; no minimum spend
AWS Step Functions
JSON-based state machines (Amazon States Language)
Teams already standardized on AWS who want a fully managed, serverless orchestrator
Fully managed AWS service
Usage-based: $0.025 per 1,000 state transitions (Standard); separate per-request/duration pricing for Express
Short Verdict
If your organization needs business analysts and compliance teams to read and approve the process definition itself, Camunda’s BPMN diagrams make that possible in a way code-first tools don’t. If your engineering team wants to write ordinary code — loops, conditionals, retries — and have the platform guarantee it survives crashes and deploys, Temporal is the more natural fit. If you’re already deep in AWS and want zero infrastructure to manage, with billing tied directly to usage, AWS Step Functions is the lowest-friction starting point, though it ties you to the AWS ecosystem and its state-transition pricing model.
Camunda: BPMN-Based Process Orchestration
Camunda’s defining feature is that processes are modeled as BPMN (Business Process Model and Notation) diagrams — a visual, standardized notation that both developers and non-technical stakeholders can read. Decision logic can be externalized into DMN decision tables. This matters most in regulated industries (insurance, banking, healthcare) where auditors or compliance officers need to review the actual process logic, not just trust that the code does what engineering says it does.
Camunda offers a free, local-only Self-Managed Development tier for building and testing on your own machine — Camunda’s documentation is explicit that this is for non-production use only. Production use requires either a Self-Managed Enterprise license (quote-based, deployed on your own infrastructure) or Camunda’s hosted SaaS, which includes a 30-day free trial with unbilled usage. Beyond the trial, SaaS pricing is also quote-based — Camunda does not publish per-seat or per-process dollar figures, so you’ll need to request a quote sized to your process volume and user count.
Temporal: Code-First Durable Execution
Temporal takes the opposite approach from Camunda: there’s no visual diagram. You write a “workflow” as ordinary code in Go, Java, TypeScript, Python, or .NET, and Temporal’s runtime guarantees that code’s execution state survives process crashes, deployments, and infrastructure failures — a property it calls “durable execution.” If a worker process dies mid-workflow, Temporal resumes it elsewhere from the last completed step rather than losing state or restarting from scratch. This model is popular with engineering teams orchestrating microservices, payment flows, or AI agent pipelines where the logic is genuinely code (branching, loops, external API calls) rather than a fixed business-approved diagram.
Temporal is open source and can be self-hosted at no software cost (you pay only for your own infrastructure). Temporal Cloud, the managed offering, moved to a pay-as-you-go model with no spend minimum: it meters “Actions” at $50 per million, plus Active Storage at $0.042 per GB-hour and Retained Storage at $0.00105 per GB-hour, according to Temporal’s own pricing page. Optional Developer Support is priced at 10% of usage. New Pay-as-you-go signups with Developer Support get $150 in trial credits valid for 90 days. Larger workloads can negotiate a committed-usage plan that discounts the per-Action rate.
Step Functions is AWS’s native orchestration service: you define a state machine in JSON (Amazon States Language) that coordinates calls to Lambda, ECS, DynamoDB, SQS, and virtually any other AWS service, plus many third-party APIs via built-in connectors. There’s no cluster to run or software to patch — it’s a fully managed, serverless service that scales automatically. The trade-off is that it’s AWS-specific: you’re buying into the AWS ecosystem rather than a portable, cloud-agnostic orchestrator.
AWS Step Functions offers two workflow types with different pricing models, per AWS’s official pricing page. Standard Workflows bill per state transition: $0.025 per 1,000 state transitions ($0.000025 each), with a perpetual free tier of 4,000 free state transitions per month that doesn’t expire after the standard 12-month AWS Free Tier window. Every retry of a failed step counts as an additional billable transition. Express Workflows, designed for high-volume, short-duration workloads, bill differently: $1.00 per million requests plus a tiered duration charge based on memory consumption, starting at $0.06 per GB-hour for the first 1,000 GB-hours and dropping at higher volumes. Charges for the downstream services a workflow invokes (Lambda, DynamoDB, data transfer, etc.) are billed separately at their normal rates.
Pricing & Model Comparison
Factor
Camunda
Temporal
AWS Step Functions
Definition style
BPMN/DMN visual diagrams
Code (Go, Java, TypeScript, Python, .NET)
JSON state machine (Amazon States Language)
Open source option
Zeebe engine is open source; SaaS/Enterprise license needed for production
Yes — fully open source, self-hostable
No — proprietary AWS service
Free tier
Local dev only (non-production)
Self-hosted is free; Cloud has no free tier beyond trial credits
4,000 free state transitions/month, ongoing
Published dollar pricing
No — quote-based for production use
Yes — per-Action and storage rates published
Yes — per-transition and per-request rates published
Cloud lock-in
Low — portable, multi-cloud
Low — portable, multi-cloud
High — AWS-native only
Pros and Cons
Camunda
Pros: Visual BPMN/DMN notation readable by non-engineers; strong fit for regulated, auditable processes; portable across clouds and on-prem
Cons: Production pricing is quote-based with no public figures; steeper learning curve for BPMN modeling conventions
Temporal
Pros: Write ordinary code instead of a DSL; strong durability guarantees; transparent, published Cloud pricing; free self-hosted option
Cons: No visual process diagram for non-technical stakeholders; requires engineering investment to adopt the SDK model correctly
AWS Step Functions
Pros: Zero infrastructure to manage; deep native integration with the AWS service catalog; transparent, published usage-based pricing; generous ongoing free tier
Cons: Locked to AWS; retries and nested states can inflate billable transitions; less suited to teams needing a cloud-agnostic or multi-cloud orchestrator
Who It’s a Good Fit For
Camunda — Enterprises in regulated industries where business stakeholders, auditors, or compliance teams need to read and sign off on the process definition itself.
Temporal — Engineering teams building distributed systems, payment pipelines, or AI agent workflows who want durable execution expressed in real code rather than a visual DSL.
AWS Step Functions — Teams already standardized on AWS who want a fully managed orchestrator with no cluster to operate and usage-based billing tied to AWS infrastructure spend.
Who Should Look Elsewhere
Teams that just need to automate UI interactions in legacy desktop apps should look at RPA platforms like UiPath or Automation Anywhere, not an orchestration engine.
Teams that only need to connect SaaS apps on simple trigger-action logic (e.g., “new Typeform response creates a Salesforce lead”) are better served by an iPaaS tool like Zapier, Make, or Workato.
Multi-cloud or on-prem shops that don’t want AWS lock-in should rule out Step Functions and compare Camunda and Temporal instead.
Bottom Line
Camunda, Temporal, and AWS Step Functions all solve the same underlying problem — keeping track of long-running, stateful processes reliably — but they target different teams. Camunda suits organizations where business and compliance stakeholders need to read the process itself. Temporal suits engineering teams who’d rather express orchestration logic as code with strong durability guarantees. AWS Step Functions suits AWS-native shops that want a fully managed, pay-as-you-go service with nothing to operate. None of the three has fully public, apples-to-apples enterprise pricing — Camunda is quote-based end to end, Temporal publishes Cloud usage rates but Enterprise commitments are negotiated, and Step Functions’ published rates still leave the downstream AWS service costs (Lambda, data transfer, etc.) as a variable you’ll need to model yourself.
FAQ
Is a workflow orchestration engine the same thing as RPA? No. RPA automates interactions with existing application UIs (clicking, typing, reading screens). Orchestration engines coordinate the state and sequencing of a broader process that may call RPA bots, APIs, and human tasks as individual steps.
Is a workflow orchestration engine the same thing as an iPaaS tool like Zapier or Workato? No. iPaaS tools excel at simple, mostly stateless trigger-action integrations between SaaS apps. Orchestration engines are built for long-running, stateful processes that may run for days or weeks, need durable retries, and require detailed visibility into where each instance currently stands.
Can Temporal or Camunda run outside the cloud they were built for? Yes — both are portable. Temporal is open source and self-hostable on any infrastructure, and Temporal Cloud itself runs on AWS and GCP. Camunda can be deployed self-managed on any infrastructure or consumed as SaaS. AWS Step Functions, by contrast, only runs on AWS.
Which option is cheapest for a small team just starting out? It depends on volume and whether you already run AWS infrastructure. Step Functions’ free tier (4,000 free state transitions/month) and pay-as-you-go pricing make it low-cost to start if you’re on AWS already. Temporal’s self-hosted open-source option has no software cost but requires you to run the server yourself; Temporal Cloud’s pay-as-you-go plan has no spend minimum. Camunda’s free tier is local development only — any production use requires a quote.
Tab hoarders have had no shortage of browsers and extensions promising to organize the chaos into tidy, project-based workspaces. We set out to compare three names that regularly come up in that conversation — Arc Browser, Microsoft Edge Workspaces, and Sidekick — and found that, as of November 2026, this category has shifted dramatically underneath two of the three. Here’s the accurate, current state of each, straight from vendor sources and recent reporting.
At a Glance
Tool
Current Status (Nov 2026)
Price
Best For
Arc Browser
Sunsetting — desktop app stops working December 22, 2026
Free (while it lasts)
Existing users who should start migrating to Dia now
Microsoft Edge Workspaces
Active, built into Edge
Free with Microsoft account sign-in
Windows/Mac users already on Edge who want simple project-based tab sets
Sidekick
Discontinued — acquired by Perplexity in 2025, team folded into Comet
N/A (no longer available as a standalone product)
No one; look at Comet or a Chrome extension instead
Short Verdict
This isn’t a clean three-way fight anymore. Arc Browser, once the most celebrated tab-and-workspace browser, is being shut down by its maker, The Browser Company, with the desktop app going dark on December 22, 2026. Sidekick, a dedicated workspace browser, was acquired by Perplexity and discontinued as a standalone product back in 2025. That leaves Microsoft Edge Workspaces as the only one of the three still actively developed and supported today — though it’s a simpler, more conservative feature than either Arc’s Spaces or Sidekick’s workspace system ever were.
Arc Browser: Sunsetting December 22, 2026
The Browser Company confirmed in late October 2026 that it is sunsetting Arc entirely, in three phases reported by TechCrunch and corroborated by multiple outlets. New Arc accounts can no longer be created as of the announcement. On November 23, 2026, the iOS and Android Arc Search apps lose their AI features (including “Browse for Me”) along with sign-in and tab sync, continuing to work only as basic local browsers. On December 22, 2026, Arc stops working entirely on Mac and Windows: accounts are deactivated and personal data is deleted within 30 days.
The Browser Company is directing users to Dia, its AI-first successor browser, and says bookmarks, extensions, passwords, history, Spaces, and tab groups can be migrated over. Dia is built on the same proprietary Arc Development Kit (ADK) that powered Arc, and carries over equivalents of Arc’s signature organizational features: “Profiles” (replacing Spaces), an optional vertical-tab sidebar, and “Pinned Tab Groups” (replacing Folders). The company’s stated reasoning is that keeping a browser secure now requires constant work that scales with AI-era threats, and it would rather concentrate that effort on one product.
If you’re currently using Arc: it still works today, but treat it as a dead end. Plan your migration to Dia (or another browser) well before December 22, 2026.
Microsoft Edge Workspaces
Microsoft Edge Workspaces is a built-in feature, not a separate app, that groups tabs and favorites by project so you can switch contexts and pick things back up later. Per Microsoft’s own documentation, it requires Edge version 144 or later on Windows 10, Windows 11, or macOS, and you must be signed in with a Microsoft (MSA) account or a Microsoft Entra ID / Azure AD account. Workspaces stay saved and up to date across sessions, and syncing can keep them current across your devices once you turn on “Workspaces and Tab Groups” syncing in Edge Settings.
You can create a workspace from your currently open tabs or start blank, move tabs between workspaces via right-click, and edit or delete workspaces from the workspaces menu. One notable limitation stated directly in Microsoft’s documentation: sharing, collaboration, and joining workspaces aren’t supported in the current Edge Workspaces experience, which puts it behind some earlier third-party tools that offered team-shared workspaces. Microsoft doesn’t list a separate price for this feature — it’s included with Edge at no extra cost beyond signing in with a Microsoft account.
Sidekick: Discontinued
Sidekick was a dedicated workspace-and-productivity browser built around named workspaces, app shortcuts, and session management. According to multiple independent sources — including Sidekick’s own company page, which now notes it was acquired by Perplexity — Perplexity acquired the Sidekick team in 2025, and the Sidekick team was folded into Perplexity’s Comet, an AI-assistant browser that is a different kind of product rather than a direct continuation of Sidekick’s tab-and-workspace workflow. As of our research in November 2026, there is no standalone Sidekick browser available, and the original meetsidekick.com domain now redirects to Perplexity’s Comet site. Treat Sidekick as fully discontinued.
If you were using Sidekick specifically for its workspace and vertical-tab workflow (rather than AI assistance), the closest options now are a Chromium-based browser’s native vertical tabs and tab groups, or a third-party Chrome extension built for named workspaces and tab-session management. Perplexity’s Comet is worth evaluating only if you want an AI-assistant browser, not a drop-in Sidekick replacement.
Status Comparison
Factor
Arc Browser
Edge Workspaces
Sidekick
Status
Sunsetting Dec 22, 2026
Active
Discontinued (2025)
Successor / replacement
Dia (same maker)
N/A — ongoing Edge feature
None direct; Comet is a different product
Sharing/collaboration
Was supported in Arc; check Dia’s current state
Not supported
N/A
Platform
Mac, Windows (until Dec 22, 2026); mobile losing features Nov 23, 2026
Windows 10/11, macOS (Edge 144+)
N/A
Pros and Cons
Arc Browser
Pros: Still functional today; data migration path to Dia is provided by the maker
Cons: Hard shutdown date of December 22, 2026; new accounts already blocked; not a viable long-term choice for anyone starting fresh
Microsoft Edge Workspaces
Pros: Free, built into a mainstream browser that isn’t going anywhere; syncs across devices with a Microsoft account
Cons: No sharing or collaboration support; requires sign-in with a Microsoft/Entra account; desktop-only (Windows/macOS)
Sidekick
Pros: None currently — the product is discontinued
Cons: Fully unavailable as a standalone browser; the Perplexity team’s focus moved to Comet, a different kind of AI-assistant product
Who It’s a Good Fit For
Current Arc users should start migrating to Dia or another browser now, well ahead of the December 22, 2026 shutdown.
Edge users on Windows or Mac who want simple, free, project-based tab organization without collaboration features are well served by Edge Workspaces today.
Former Sidekick users have no direct successor; consider a Chromium browser’s native tab groups plus a workspace-focused extension, or evaluate Comet if AI assistance (not workspace management specifically) is the priority.
Who Should Look Elsewhere
Anyone needing shared, collaborative workspaces (multiple people editing or viewing the same tab group) should look past Edge Workspaces, since Microsoft’s own documentation states sharing and collaboration aren’t supported in the current version. Anyone starting a new browser setup from scratch in late 2026 should not invest time building a workflow around Arc, given its confirmed shutdown date.
Bottom Line
The browser-workspace landscape looked very different a year or two ago than it does in November 2026. Of the three names in this comparison, only Microsoft Edge Workspaces is actively maintained and safe to build a workflow around today. Arc Browser is on a clear, published path to shutdown on December 22, 2026, with The Browser Company steering users toward its new browser, Dia. Sidekick is already gone, acquired by Perplexity and folded into the unrelated Comet product. If you need tab-and-workspace management right now, Edge Workspaces (if you’re on Windows or Mac) or Dia (if you want Arc’s organizational DNA carried forward) are the realistic choices.
FAQ
Is Arc Browser shutting down? Yes. The Browser Company confirmed in October 2026 that Arc’s desktop app for Mac and Windows stops working on December 22, 2026, with new account creation already disabled and mobile AI features ending November 23, 2026.
What happens to my Arc data? The Browser Company says bookmarks, extensions, passwords, history, Spaces, and tab groups can be migrated to Dia, its successor browser. Accounts are deactivated on the shutdown date and personal data is deleted within 30 days after.
Is Sidekick browser still available? No. Sidekick was acquired by Perplexity in 2025 and discontinued as a standalone product; its team moved to Perplexity’s Comet browser, and its original domain now redirects to Comet’s site.
Does Microsoft Edge Workspaces support team collaboration? No. Microsoft’s own documentation states that sharing, collaboration, and joining workspaces aren’t supported in the current Edge Workspaces experience — it’s built for individual project organization, not shared team tab sets.
Robotic process automation tools execute a process you’ve already defined. Process mining tools answer a different question first: what is your process actually doing, right now, according to the data your systems already generate? By reconstructing real event logs from ERPs, CRMs, and ticketing systems, process mining reveals the true workflow — with its bottlenecks, rework loops, and exceptions — rather than the idealized version in a flowchart. That discovery step is what makes RPA investments effective instead of automating the wrong thing faster. Celonis, UiPath Process Mining, and ABBYY Timeline are three of the leading platforms for this discovery work. Here’s how they compare in 2026.
What Process Mining Actually Does
Process mining tools ingest timestamped event logs — a purchase order created, approved, modified, shipped — and algorithmically reconstruct the actual sequence of steps a process followed, across every real variation, not just the documented one. That’s fundamentally different from RPA, which automates a known sequence of clicks and data entry once you’ve decided what that sequence should be. In practice, process mining and RPA are complementary: mining finds where a process breaks down or loops unnecessarily, and RPA (or broader automation tooling) then fixes it. All three vendors below increasingly position their tools this way — as the “find the problem” layer that feeds automation decisions, rather than automation itself.
At a Glance
Platform
Best For
Pricing
Standout Feature
Celonis
Large enterprises wanting process mining plus a broader execution management layer
Custom quote only
Context Model for real-time, system-agnostic process representation
UiPath Process Mining
Organizations already standardized on the UiPath automation platform
Consumption-based (Platform Units); rates not publicly listed
Tightly integrated with UiPath’s Maestro orchestration and RPA bots
ABBYY Timeline
Mid-size to enterprise teams wanting a dedicated, cloud-first mining tool
Custom quote; 30-day free trial offered
Combines process discovery with task mining and process simulation
Short Verdict
Celonis is the deepest and most strategically positioned option, especially if you want process mining to feed directly into an execution/orchestration layer rather than stand alone — but it’s also priced and sold as a major enterprise platform decision. UiPath Process Mining makes the most sense if you’re already running UiPath for RPA and want mining and execution on one consumption-based bill. ABBYY Timeline is the more approachable standalone option, with a public free trial and a clear, five-capability feature set, making it a reasonable starting point if you’re not yet locked into a broader automation platform.
Celonis: Process Intelligence as an Execution Platform
Celonis has evolved from a pure process-mining tool into what it calls a process intelligence and execution management platform, built around five components: a Data Core for extracting and querying data from any source, a Context Model that maintains a real-time, system-agnostic representation of the business for root-cause analysis and what-if scenarios, a three-stage Build Experience (Analyze, Design, Operate), an Integrated Marketplace of prebuilt partner solutions, and connectors to systems of record, data platforms, AI tools, and automation vendors. Process mining itself sits inside the “Analyze” stage, alongside process simulation and predictive capabilities. Celonis does not publish pricing anywhere on its site — every engagement goes through a sales conversation, consistent with its positioning as a strategic, enterprise-wide platform rather than a point tool.
UiPath Process Mining: Consumption-Based, Platform-Native
UiPath Process Mining is priced under UiPath’s Unified Pricing Plan using Platform Units (PUs) tied to data capacity — specifically, rows in the Event Log table, where 1 PU equals 625 rows. The first data load on a tenant costs 1,600 PUs, covering 1 million rows for 12 months (prorated if less than a year remains on your license); loading beyond your previous peak volume consumes additional PUs for the difference. Notably, Process Optimization apps built purely on Maestro-generated data (UiPath’s own orchestration data) aren’t charged at all, and apps mixing Maestro with external data get the first 10,000 rows free. UiPath doesn’t publish a dollar rate per Platform Unit — that requires talking to a UiPath account manager — and using Process Mining at all requires a Standard or Enterprise platform plan, with Enterprise additionally unlocking data extractors, process simulation, and multi-process apps. The clear advantage here is integration: if you’re already running UiPath RPA bots and Maestro orchestration, Process Mining plugs into the same licensing and data environment rather than requiring a separate platform.
ABBYY Timeline: Cloud-First and Still Actively Developed
Despite some market confusion about ABBYY’s product lineup in recent years, ABBYY Timeline is an actively maintained, cloud-based process intelligence platform — its own status page shows version releases as recent as early 2026. Its five core capabilities are process discovery (building a “digital twin” of a process from system event logs, plus optional desktop task mining), process analysis (25+ built-in analysis tools for bottlenecks and variations), process monitoring (near-real-time execution tracking with alerts via email, BPM, or RPA bots), process prediction (machine-learning forecasts of outcomes and flow deviations), and process simulation (testing proposed changes before implementation). ABBYY Timeline offers a public 30-day free trial, which is more accessible than either Celonis or UiPath’s sales-gated entry points, though full pricing still requires a quote via “Request a demo” or “Contact Sales.”
Pricing & Access Comparison
Celonis
UiPath Process Mining
ABBYY Timeline
Published dollar pricing
No
No (unit structure published, rate is not)
No
Free trial
Not published
Not applicable (requires existing platform plan)
Yes — 30 days
Pricing basis
Custom enterprise quote
Platform Units based on event-log row volume
Custom enterprise quote
Requires existing platform
No — standalone
Yes — UiPath Standard/Enterprise plan
No — standalone
Pros and Cons
Celonis
Pro: Goes beyond discovery into real-time context modeling and what-if simulation
Pro: Large partner marketplace of prebuilt, industry-specific solutions
Con: No published pricing or free trial; fully sales-gated
Con: Positioned as a strategic platform purchase, which can mean a longer buying cycle
UiPath Process Mining
Pro: Native integration with UiPath RPA bots and Maestro orchestration
Pro: Maestro-only data isn’t charged, which can lower costs for UiPath-centric workflows
Con: Requires an existing Standard or Enterprise UiPath platform plan — not usable standalone
Con: Pricing unit (Platform Units) is published, but the actual dollar rate is not
ABBYY Timeline
Pro: Public 30-day free trial — the most accessible entry point of the three
Pro: Clear, well-documented five-capability feature set including task mining and simulation
Con: Smaller partner/marketplace ecosystem than Celonis
Con: Full pricing still requires a sales conversation
Who It’s a Good Fit For
Choose Celonis if you want process mining as part of a broader, long-term execution management strategy and have the budget and timeline for an enterprise platform purchase. Choose UiPath Process Mining if you’re already standardized on UiPath for RPA and orchestration and want mining data flowing through the same licensing and environment. Choose ABBYY Timeline if you want to start evaluating process mining quickly, with a free trial, before committing to a larger platform decision.
Who Should Look Elsewhere
If what you actually need is to automate a process you’ve already fully mapped out — rather than discover how it’s really running — a dedicated RPA tool on its own may be all you need, without the added cost and complexity of a process mining layer. And if your organization has no centralized, timestamped event-log data (e.g., you’re running mostly manual, paper-based, or siloed spreadsheet workflows), process mining tools will have little to analyze until that data exists.
Bottom Line
All three platforms do genuine process discovery well, but they’re built for different buying situations. Celonis sells the broadest strategic platform at an entirely custom price. UiPath Process Mining is the right call only if you’re already inside the UiPath ecosystem, since it isn’t sold standalone. ABBYY Timeline is the easiest of the three to actually start trying today, thanks to its public free trial. None publish dollar pricing, so budget your evaluation timeline around a sales conversation regardless of which you pursue.
FAQ
Is process mining the same thing as RPA? No. Process mining discovers and analyzes how a process actually runs today using existing event-log data; RPA executes a defined sequence of steps. Mining typically informs where and how to apply RPA, rather than replacing it.
Can I use UiPath Process Mining without other UiPath products? No — it requires an existing UiPath Standard or Enterprise platform plan with available Platform Units, so it isn’t sold as a fully standalone product.
Is ABBYY Timeline still being actively developed? Yes. ABBYY’s own status page shows version updates and scheduled maintenance as recent as January 2026, indicating ongoing active development rather than a discontinued product.
Do any of these three publish a price list? No. Celonis, UiPath Process Mining, and ABBYY Timeline are all sold through custom, quote-based pricing — only UiPath publishes the unit structure (Platform Units) behind its pricing, without a dollar rate.
Cloud Access Security Broker (CASB) was once its own standalone product category. In 2026, it’s increasingly a feature embedded inside larger security platforms — and that shift matters a lot when you’re trying to work out what something actually costs and whether you can buy it on its own. Netskope, Microsoft Defender for Cloud Apps, and Cisco Umbrella represent three different takes on where CASB sits: a dedicated SSE vendor, a Microsoft 365-bundled security product, and a layer inside Cisco’s secure internet gateway. None of the three publish flat list prices for their CASB capability, so this comparison focuses on what’s verifiable — packaging, bundling, and how each is sold — rather than invented numbers.
At a Glance
Platform
Sold As
CASB Availability
Pricing
Best Fit
Netskope
Standalone CASB product or part of the Netskope One SSE/SASE platform
Standalone CASB, per Netskope’s own platform page
Not published; demo/contact-sales only
Organizations wanting a dedicated, vendor-neutral CASB/SSE platform
Microsoft Defender for Cloud Apps
Standalone license or bundled into Microsoft suites
Standalone license available; also included in EMS E5, Microsoft 365 E5/A5/G5, Microsoft Defender Suite, and Microsoft Purview Suite, per Microsoft’s own licensing documentation
Standalone list price not published on Microsoft’s public pricing pages; sold via Microsoft 365 licensing/CSP
Organizations already licensing Microsoft 365 E5 or EMS E5 who get MDCA bundled in
Cisco Umbrella
Feature within SIG (Secure Internet Gateway) package tiers
Included starting at SIG Essentials and above, per Cisco’s official package brochure — not in the DNS-only tiers
Not published; “Talk to an expert”
Organizations already using Cisco Umbrella/Secure Access for DNS and web security who want CASB as part of the same stack
Short Verdict
All three require a sales conversation before you’ll see a real price — this category simply isn’t sold off a public price list anywhere. What you can determine upfront is packaging: Netskope sells CASB as a distinct, standalone product (or as part of its broader SSE suite) from a dedicated SSE vendor. Microsoft Defender for Cloud Apps is most attractive if you’re already paying for Microsoft 365 E5 or EMS E5, since MDCA rides along with those suites rather than being a new line item. Cisco Umbrella only gets you CASB once you step up from its DNS-only tiers into SIG Essentials or above — so if you’re on a lower Umbrella tier today, CASB isn’t included and requires an upgrade.
Netskope: CASB as a Standalone Product or Part of SSE
Netskope positions Cloud Access Security Broker as one of its named, individual products, alongside a broader “Security Convergence (SSE)” suite under its Netskope One platform. Per Netskope’s own platform page, its suites “may be deployed either as a fully integrated platform or as standalone solutions” — meaning you are not necessarily forced to buy the entire SASE/SSE stack just to get CASB functionality.
Netskope’s site contains no published prices, tiers, or per-user rates for CASB or any other product. Every call to action is “Request a demo,” “Get Started,” or “Contact Us.” The company does offer a free trial of Netskope Private Access (its ZTNA product, not CASB) and complimentary ROI-consulting services, but neither substitutes for a real price quote. If you need a dedicated, vendor-neutral CASB without being locked into a single cloud provider’s ecosystem, Netskope is built for exactly that use case — you’ll just need to go through a sales cycle to find out what it costs for your organization’s size.
Microsoft Defender for Cloud Apps: Standalone License or Bundled Into E5
Microsoft Defender for Cloud Apps (MDCA) is Microsoft’s CASB, and per Microsoft’s own service description and licensing documentation on Microsoft Learn, it’s available two ways:
As a standalone license, purchased on its own.
Bundled into several existing Microsoft suites, including Enterprise Mobility + Security (EMS) E5, Microsoft 365 E5/A5/G5, the Microsoft Defender Suite, and the Microsoft Purview Suite. Microsoft’s official documentation states explicitly that it “doesn’t require Microsoft 365 productivity suite licenses,” meaning it can be layered onto a security-only license path too.
What we could not verify is a published per-user, per-month standalone list price on Microsoft’s public pricing pages — the general “Microsoft Security pricing” page doesn’t list MDCA by name with a figure, and pricing is instead delivered through Microsoft 365 licensing channels, partners, or the Cloud Solution Provider (CSP) program, where actual per-seat cost can vary by agreement. If your organization already licenses Microsoft 365 E5 or EMS E5, MDCA effectively comes “free” as part of that bundle rather than as a separate purchase decision — which is the most common way SMBs and enterprises alike end up with it.
Cisco Umbrella: CASB Lives in the SIG Tiers, Not the DNS Tiers
Cisco Umbrella is sold in package tiers, and per Cisco’s own package materials, CASB functionality is not part of the DNS-only tiers. The tier structure breaks down as:
DNS Security Essentials: DNS-layer blocking, off-network/mobile protection, shadow IT discovery by domain. No CASB.
DNS Security Advantage: Everything in Essentials plus proxying of risky domains and antivirus/AMP file inspection. No CASB.
SIG Essentials: Everything in DNS Security Advantage, plus a full secure web gateway proxy, cloud-delivered firewall, sandbox analysis — and CASB.
SIG Advantage: Everything in SIG Essentials, plus intrusion prevention (IPS), data loss prevention (DLP), and cloud malware detection.
In other words, CASB is a SIG-tier feature, not a DNS-tier feature. If your organization is currently on one of Umbrella’s DNS Security packages, you do not have CASB and would need to move up to SIG Essentials or SIG Advantage to get it. Cisco’s umbrella.cisco.com pricing/packages page does not publish dollar figures for any tier — it directs visitors to “Talk to an expert” and a separate package-comparison document for the feature-level detail.
Packaging & Pricing Model Comparison
Factor
Netskope
Microsoft Defender for Cloud Apps
Cisco Umbrella
Can CASB be bought alone?
Yes — sold as a standalone product per Netskope’s platform page
Yes — standalone license exists, per Microsoft documentation
No — only available from SIG Essentials tier and above
Common bundling path
Netskope One SSE/SASE suite
Microsoft 365 E5, EMS E5, Defender Suite, Purview Suite
Cisco Secure Access / SIG package tiers
Published pricing?
No — contact sales
No standalone figure on public pricing pages — sold via M365 licensing/CSP
No — contact sales
Pros and Cons
Netskope
Pros: Dedicated, vendor-neutral CASB; can be deployed standalone or as part of a broader SSE/SASE rollout.
Cons: No published pricing at all; requires a sales/demo process to get any cost estimate.
Microsoft Defender for Cloud Apps
Pros: Often “free” in practice if you already hold Microsoft 365 E5 or EMS E5; doesn’t require a Microsoft 365 productivity license to use.
Cons: No clear standalone list price published anywhere public; true cost depends on your existing Microsoft licensing agreement.
Cisco Umbrella
Pros: CASB sits alongside DLP, IPS, and secure web gateway in the same SIG package, consolidating multiple controls under one Cisco contract.
Cons: Not available at all on the lower-cost DNS-only tiers; no published pricing for any tier.
Who It’s a Good Fit For
Choose Netskope if you want a dedicated CASB/SSE vendor independent of your existing cloud or security stack.
Choose Microsoft Defender for Cloud Apps if you’re already licensing (or considering) Microsoft 365 E5 or EMS E5 — CASB essentially comes along for the ride.
Choose Cisco Umbrella if you’re already using or planning to use Cisco’s secure internet gateway and want CASB consolidated with DLP, IPS, and web filtering under SIG Advantage.
Who Should Look Elsewhere
If your organization is on Cisco Umbrella’s DNS-only tiers and assumed CASB was included, it isn’t — you’d need to budget for an upgrade to SIG Essentials or above. And if you need a hard, published price to put in a budget request before any sales conversation, none of these three vendors will give you that; all three CASB offerings here are ultimately quote-based, so plan your procurement timeline accordingly.
Bottom Line
CASB in 2026 is less a standalone purchase decision and more a question of “what’s already in my stack.” Netskope is the right call if CASB is a primary driver and you want a dedicated vendor. Microsoft Defender for Cloud Apps is the pragmatic choice if you’re already committed to Microsoft 365 E5 or EMS E5. Cisco Umbrella makes sense if you want CASB folded into the same contract as your DNS filtering, secure web gateway, and DLP — but only once you’re on SIG Essentials or higher. In every case, treat the “price” as a conversation to have with sales, not a number to look up.
FAQ
Is Microsoft Defender for Cloud Apps included in Microsoft 365 E5?
Yes. Per Microsoft’s own service description documentation, Microsoft Defender for Cloud Apps is included as part of Microsoft 365 E5/A5/G5, Enterprise Mobility + Security E5, the Microsoft Defender Suite, and the Microsoft Purview Suite, in addition to being available as a standalone license.
Does every Cisco Umbrella plan include CASB?
No. Per Cisco’s own package documentation, CASB is included starting at the SIG Essentials tier and above. The DNS Security Essentials and DNS Security Advantage tiers do not include CASB.
Can you buy Netskope’s CASB without the full SSE platform?
Yes. Netskope’s platform page states its products, including CASB, “may be deployed either as a fully integrated platform or as standalone solutions,” so CASB doesn’t require adopting the entire Netskope One suite.
Why can’t I find a price for any of these on the vendor’s website?
CASB and SSE/SASE platforms are almost universally sold through enterprise sales teams because pricing depends heavily on user count, data volume, existing licensing agreements, and which modules are bundled. None of the three vendors covered here publish flat list prices for CASB on their public sites.
Cloud bills don’t explain themselves, and three very different categories of tool have grown up to make them legible: cost-intelligence platforms that attribute spend to engineering units (CloudZero), Kubernetes-native cost allocation tools that most teams first meet as a free install (Kubecost), and workload/commitment optimization platforms that actually act on compute to cut the bill (Spot, now part of Flexera after its 2025 divestiture from NetApp). One important update for 2026: the tool widely known as “Spot by NetApp” changed owners last year, and the old branding is already out of date — more on that below.
AT A GLANCE
Tool
Category
Current owner
Pricing model
Free tier
CloudZero
Cost intelligence / unit economics
CloudZero, Inc. (independent)
Custom quote only — no published price list
No published free tier; demo-only sales motion
Kubecost
Kubernetes cost allocation & optimization
IBM (acquired Kubecost, Sept. 2024)
Free tier + paid “Enterprise” tiers (self-hosted or SaaS); third-party trackers cite pricing starting near $449/month for paid plans, not officially published by IBM
Yes — real free tier with limits (see below), plus the fully free, unlimited open-source OpenCost project it’s built on
Flexera (acquired NetApp’s Spot FinOps portfolio, announced Jan. 2025, completed by March 2025)
Custom quote only — no published price list
No published free tier; demo-only sales motion
Short Verdict
These three tools aren’t really substitutes for each other. CloudZero is for turning raw cloud bills into cost-per-customer, cost-per-feature, or cost-per-team numbers that engineering and finance can both act on. Kubecost (and its free open-source core, OpenCost) is the default way to see where money goes inside a Kubernetes cluster, and it’s the only one of the three with a genuinely free, usable tier. Spot’s products — now sold under Flexera’s FinOps portfolio rather than NetApp’s — are about automatically acting on compute (rightsizing, spot-instance orchestration, reserved-instance/savings-plan management) rather than just reporting on it. Most FinOps-mature organizations end up running a visibility tool alongside an optimization/automation tool, not choosing one over the other.
Important Update: “Spot by NetApp” Changed Owners
NetApp originally acquired Spot.io (the former Spotinst) in 2020 and later added CloudCheckr. In January 2025, Flexera announced it would acquire NetApp’s entire FinOps business — the Spot product line (Eco, Ocean, Elastigroup) plus CloudCheckr — and the deal closed by March 2025. As of 2026, spot.io redirects visitors directly to flexera.com, and the products are marketed as part of “Flexera One FinOps” (Cloud Cost Optimization, Rate Optimization, and Workload Optimization). If you’re evaluating this tool today, expect to deal with Flexera’s sales team and branding, not NetApp’s — any comparison that still lists it under NetApp is working from stale information.
CloudZero: Cost Intelligence and Unit Economics
CloudZero’s pitch is mapping cloud spend to business metrics — cost per customer, per feature, per team — rather than just per AWS service. Per its own pricing page, CloudZero does not publish a price list at all: it describes “a tiered pricing model that’s steady, predictable, and won’t vary month to month,” scaled to the size and complexity of your cloud environment, but the only calls to action are “Book a demo” and a product tour — you cannot self-serve a price quote or a trial sign-up from the page itself. What is published is the feature scope included in that single subscription: unlimited cost sources, users, dimensions, and dashboards; hourly cost granularity; anomaly detection; budgets and forecasts; multi-year data retention; and role-based access control. There is no free tier.
Kubecost: The Only One With a Real Free Tier
Kubecost is built on top of OpenCost, a CNCF-hosted open-source project (originally spun out of Kubecost itself) that provides the underlying real-time cost-allocation model for free, with no UI, SSO, or RBAC layered on. Kubecost itself — now “IBM Kubecost” following IBM’s September 2024 acquisition — wraps that core in a product with a genuine free tier plus paid plans:
Free tier: Per AWS’s own EKS documentation of Kubecost’s current (v3) packaging, the free tier supports an unlimited number of clusters but is gated once a cluster’s monitored spend exceeds $100,000 over a trailing 30-day window, and container request-sizing recommendations are limited to 250 cores. IBM’s own marketing states “all IBM Kubecost plans are free for 30 days” for the paid tiers, separate from this always-free tier.
Enterprise (self-hosted or SaaS): Removes the spend/core limits, adds unlimited metric retention, role-based access control, SSO integrations (Okta/Auth0/PingID/Keycloak), audits, and dedicated onboarding. IBM does not publish exact Enterprise pricing; third-party pricing trackers report figures starting around $449/month, but that number comes from resellers/trackers, not an official IBM price list, so treat it as indicative rather than authoritative.
Because OpenCost itself has no spend cap and is fully open-source, teams that just want Kubernetes cost allocation without any commercial relationship can run OpenCost alone and never hit a paywall — the limits described above apply specifically to the Kubecost product, not to OpenCost.
Spot (Flexera): Optimization, Not Just Visibility
Where CloudZero and Kubecost are primarily about seeing costs clearly, Spot’s product line is about automatically acting on infrastructure to reduce them: Eco manages reserved instances, savings plans, and committed-use discounts across AWS, Azure, and Google Cloud; Ocean handles Kubernetes infrastructure cost, performance, and availability (including spot-instance orchestration for stateless workloads); and Elastigroup automates scaling across spot instances and VMs. Under Flexera’s branding, these now sit inside “Flexera One FinOps,” alongside Flexera’s existing cloud license management tooling. As with CloudZero, pricing is quote-based — Flexera’s own site offers no published numbers, only “Book a demo” and “Chat with an expert,” with case-study ROI figures (not prices) as the only concrete numbers shown.
Pros and Cons
CloudZero
Pros: Strong unit-economics/cost-allocation story; unlimited dimensions and users in its single tier; good for engineering-finance alignment.
Cons: No published pricing or free trial; demo-gated sales process; not a workload-optimization tool — it reports, it doesn’t act.
Kubecost
Pros: Genuinely free tier (and a fully free open-source core, OpenCost); fast setup; Kubernetes-native; now backed by IBM’s resources.
Cons: Free tier is capped at $100K/30-day spend per cluster and 250 cores for sizing recommendations; official Enterprise pricing isn’t published; narrower scope (Kubernetes) than CloudZero or Spot’s multi-cloud reach.
Spot (Flexera)
Pros: Actually automates savings (commitment management, spot orchestration, rightsizing) rather than just reporting; multi-cloud; backed by Flexera’s established enterprise licensing relationships.
Cons: Recent ownership change (NetApp → Flexera) means outdated branding/comparisons are everywhere; no published pricing or free tier; evaluators need to confirm with Flexera sales which legacy Spot features remain unchanged post-acquisition.
Who Each Is a Good Fit For
CloudZero suits organizations that need to explain cloud spend to finance and product teams in business terms — SaaS companies tracking cost-per-customer, for example. Kubecost is the natural starting point for any team running meaningful Kubernetes workloads and wanting cost visibility without procurement friction — start with the free tier or OpenCost directly, and only talk to sales once you outgrow the spend/core limits. Spot (Flexera) fits organizations with large, elastic compute footprints (especially Kubernetes and autoscaling VM fleets) that want automated savings execution, not just a dashboard — but budget time to confirm current product names and support terms given the recent ownership transition.
Bottom Line
None of these three is a drop-in competitor to the other two — they occupy different layers of the FinOps stack. Kubecost is the only one you can actually try today without a sales call, thanks to its free tier and the fully open OpenCost core beneath it. CloudZero and Spot (now under Flexera, not NetApp) both require a conversation with sales to get a number, so budget time for that in your evaluation, and make sure whoever you’re evaluating is quoting current, Flexera-branded Spot terms rather than an outdated NetApp sheet.
FAQ
Is Spot.io still owned by NetApp? No. NetApp divested its entire Spot FinOps portfolio (Spot Eco, Ocean, Elastigroup, and CloudCheckr) to Flexera; the deal was announced in January 2025 and completed by March 2025. The spot.io domain now redirects to flexera.com.
Is Kubecost really free? Kubecost has a genuine free tier (unlimited clusters, gated at $100,000 of monitored spend per cluster over 30 days, with core-count limits on sizing recommendations), and its underlying engine, OpenCost, is fully open-source and free with no spend cap. Paid Enterprise tiers add unlimited retention, SSO, and audits.
Who owns Kubecost now? IBM acquired Kubecost in September 2024. It’s now marketed as “IBM Kubecost,” though the product and its open-source OpenCost foundation continue to operate largely as before.
Does CloudZero publish its prices anywhere? No. CloudZero’s own pricing page offers only a demo booking and product tour, with no published price list, tiers, or free trial as of this writing.
Can I use OpenCost without ever paying for Kubecost? Yes. OpenCost is a standalone CNCF project that provides core Kubernetes cost allocation for free; you only need a commercial Kubecost relationship if you want the full UI, SSO/RBAC, cloud billing integrations, or support beyond what OpenCost offers.
Salons, clinics, studios, and solo consultants need something different from a generic meeting scheduler: client-facing online booking with deposits, packages, intake forms, and staff calendars, not just a link for finding a free half hour. Acuity Scheduling, Square Appointments, and SimplyBook.me are three of the most established tools built specifically for that kind of service-business booking. Here’s how their official pricing and features stack up.
At a Glance
Software
Starting Price
Free Plan
Best For
Acuity Scheduling
$16/month (billed annually)
No – 7-day free trial
Solo providers and small teams wanting polished client-facing booking
Square Appointments
$0 for a single location; $29/location/month for Plus
Yes – single location, full core features
Businesses already using Square for payments/POS
SimplyBook.me
$0 (Free, 50 bookings/month); $11.90/month for Basic
Yes – 50 bookings/month, 1 provider
Budget-conscious businesses wanting lots of niche add-on features
Short Verdict
Square Appointments is the easiest free option if you’re a single-location business, especially one already processing payments through Square, since its Free plan has no time limit. SimplyBook.me has the lowest paid entry price and the deepest library of optional “custom features” (intake forms, memberships, classes, and more), which makes it attractive for niche service businesses. Acuity Scheduling skips a free plan entirely but offers the most polished, flexible client booking experience of the three, with real text reminders and packages available from its Standard tier.
Acuity Scheduling: Polished Booking, No Free Tier
Acuity’s three plans are billed per month, with lower rates on annual billing: Starter at $16/month (annual) or $20 (monthly) includes 1 calendar, online payments, email reminders, custom intake forms, and time zone conversion. Standard, at $27 (annual) or $34 (monthly), covers up to 6 calendars and adds text reminders, a waitlist, packages, memberships, and gift certificates. Premium, at $55 (annual) or $69 (monthly), covers up to 36 calendars and adds an AI booking assistant, a HIPAA Business Associate Agreement, removal of Acuity branding, support for multiple time zones, and custom API/CSS access. Every plan includes a 7-day free trial, but there’s no permanently free tier.
Square Appointments: Free for One Location, Built Around Payments
Square Appointments’ Free plan costs nothing for a single location and includes core scheduling, reminders, online booking, and invoicing, with unlimited calendars and no staff limit — though it lacks a waitlist, class booking, cancellation fees, and Google Calendar sync. Plus, at $29 per location per month, adds multi-location management, class booking, a waitlist, processing-time buffers, Google Calendar sync, cancellation fees, daily appointment limits, and reporting. Premium, at $69 per location per month, adds resource management (rooms, chairs, stations), advanced staff permissions, time tracking, service cost tracking, and custom contract fields. In-person card processing runs 2.6% + 15¢ on Free and 2.5% + 10¢ on Plus/Premium, with online processing at 2.9% + 30¢ across all plans. Custom pricing is available for businesses processing over $250,000 per year.
SimplyBook.me: Lowest Entry Price, Most A La Carte Features
SimplyBook.me’s Free plan supports 1 provider and up to 50 bookings per month with 1 custom feature. Paid tiers, shown at both annual and monthly rates, are Basic at $11.90/month (annual) or $13.90 (monthly) for 5 providers, 100 bookings, and 3 custom features; Standard at $24.90 or $29.90 for 15 providers, 500 bookings, and 8 custom features; and Premium at $49.90 or $59.90 for 30 providers, 2,000 bookings, and unlimited custom features. An Enterprise tier above Premium is fully custom-priced. “Custom features” is SimplyBook.me’s term for optional modules — things like memberships, classes, intake forms, and marketing tools — that you pick and choose per plan’s allowance. Extra bookings, SMS credits, and a custom domain with SSL are available as separate paid add-ons.
Pricing at a Glance
Plan
Acuity Scheduling
Square Appointments
SimplyBook.me
Free tier
None (7-day trial)
Yes – 1 location, unlimited staff/calendars
Yes – 1 provider, 50 bookings/mo
Entry paid tier
$16/mo (annual) – 1 calendar
$29/location/mo (Plus)
$11.90/mo (annual) – 5 providers, 100 bookings
Top published tier
$55/mo (annual) – up to 36 calendars, AI assistant
$69/location/mo (Premium)
$49.90/mo (annual) – 30 providers, 2,000 bookings
Pros
Acuity Scheduling: Clean, client-friendly booking pages; packages, memberships, and gift certificates built in from Standard up.
Square Appointments: Genuinely free for single-location businesses; tightly integrated with Square payments and POS.
SimplyBook.me: Cheapest paid entry point; widest range of optional add-on features for niche service businesses.
Cons
Acuity Scheduling: No free plan at all, and HIPAA support is locked behind the top Premium tier.
Square Appointments: Multi-location pricing is billed per location, which adds up fast for businesses with several sites.
SimplyBook.me: Many useful features are “custom feature” add-ons rather than included, and bookings/SMS beyond plan limits cost extra.
Who It’s a Good Fit For
Acuity Scheduling fits solo practitioners and small teams — coaches, therapists, consultants — who want a polished booking page and are willing to pay from day one. Square Appointments is the natural choice for single-location shops already using Square for payments, since the Free plan has no catch for one location. SimplyBook.me suits budget-conscious service businesses with niche needs (classes, memberships, intake forms) who want to pay only for the modules they use.
Who Should Look Elsewhere
Businesses wanting a permanently free plan should skip Acuity. Multi-location chains sensitive to per-location fees may find Square’s $29–$69 per location adds up versus a flat per-provider model. And teams that want every feature included by default, without an a la carte system, may find SimplyBook.me’s custom-feature structure more fiddly than they’d like.
Bottom Line
For a single-location service business already in the Square ecosystem, Square Appointments’ free plan is hard to beat. For the most polished, purpose-built client booking experience, Acuity Scheduling is worth paying for from the start. For the lowest-cost multi-provider setup with room to add niche features as you grow, SimplyBook.me offers the most flexibility per dollar.
FAQ
Is there a free version of Acuity Scheduling?
No. Acuity offers only a 7-day free trial; after that, plans start at $16/month billed annually ($20/month billed monthly).
Can I use Square Appointments without Square payments?
Square Appointments is built as part of the Square ecosystem, and its pricing page lists processing rates for card payments on every plan, so it’s designed around using Square’s own payment processing.
How many bookings does SimplyBook.me’s free plan allow?
The Free plan allows up to 50 bookings per month for a single provider, with 1 custom feature included.
Which tool is best for a multi-location business?
Square Appointments’ Plus and Premium tiers are explicitly built for multi-location management, though pricing is per location. Acuity’s higher tiers support more calendars under one account rather than separate locations.
This is specifically about autonomous AI customer support agents — software that resolves customer conversations end-to-end — not the live-chat helpdesk platforms underneath them. Intercom’s Fin, Ada, and Decagon all sell themselves as the AI agent layer sitting on top of (or alongside) support operations. Only one of the three publishes any pricing at all, and it uses an unusual model worth understanding before you sign.
AT A GLANCE
Tool
Pricing Model
Public Price
Best For
Intercom Fin
Per resolution (“per outcome”)
From $0.99 per Fin outcome, on top of or separate from seat pricing
Teams wanting a usage-priced AI agent that can bolt onto Intercom or an existing helpdesk
Ada
Custom quote
Not published — demo required
Enterprises wanting a dedicated AI-agent platform with its own tooling (Ada Computer, Playbooks)
Decagon
Custom quote
Not published — demo required
Large enterprises (airlines, telecoms, fintech) needing voice + chat + email in one AI layer
Short Verdict
Intercom Fin is the only one of these three with any public pricing, and it’s genuinely usage-based: Intercom’s own pricing page lists Fin starting at $0.99 per resolved outcome, billed on top of (or independent of) Intercom’s base seat plans. Ada and Decagon are both entirely demo-gated — neither publishes a single number, a per-resolution rate, or a seat price anywhere on their public sites, so this article cannot responsibly state what either costs. That gap alone is a meaningful buying signal: if transparent, predictable, usage-based pricing matters to you, Fin is verifiably the most transparent of the three; if you need an enterprise-scale voice/chat/email agent with deep customization, Ada and Decagon both pitch to that market but require a sales conversation to get a number.
Intercom Fin: Priced Per Resolution, Separate From Seats
Intercom’s core helpdesk plans are Essential ($19/seat/month for new customers, discounted from $29), Advanced ($85/seat/month), and Expert ($132/seat/month), per Intercom’s own pricing page. Fin, Intercom’s AI agent, is priced completely separately from those seats: it’s billed “from $0.99 per Fin outcome” — Intercom’s term for a resolved customer interaction — and that same starting rate is listed across every base plan. Importantly, Fin isn’t locked to Intercom’s helpdesk: the page explicitly offers Fin as a standalone product you can bolt onto an existing helpdesk with “no seats required,” at the same starting per-outcome rate. Additional named add-ons stack on top if needed — Intercom Pro (from $100/month), Copilot ($29/agent/month for human-agent assistance), and Proactive Support Plus ($99/month) — so a full deployment cost depends on which of these a team also adopts, not Fin’s per-outcome rate alone.
Ada: Enterprise Platform, Fully Demo-Gated
Ada’s pricing page is, in practice, a demo-booking page: it describes a 30-minute expert review, a custom demo built on the prospect’s own use cases, and an ROI business case — but no price, tier, or rate appears anywhere on it. Ada’s named platform components include “Ada Computer” (giving the AI agent tools to complete customer tasks, not just answer questions), “Playbooks” (automating complex standard operating procedures with agentic AI), and dedicated products for Voice, Messaging, and Email. Without public pricing, prospective buyers have no way to benchmark Ada’s cost against Fin’s transparent per-outcome rate without engaging sales directly.
Decagon: Enterprise-Only, No Pricing Published
Decagon’s homepage is similarly demo-only, with no pricing, tiers, or rates published anywhere. It positions itself squarely at large enterprises across financial services, travel and hospitality, healthcare, technology, retail, telecom, and insurance, citing customer logos including Deutsche Telekom, American Airlines, Notion, Duolingo, and Chime. Its platform is built around “Agent Operating Procedures” (plain-language workflow definitions), live A/B testing of agent behavior (“Experiments”), simulated testing/QA, and an always-on QA layer called “Watchtower.” Decagon’s own marketing cites vendor-reported results like a 70% voice/chat resolution rate for Chime and an 80% deflection rate for Duolingo — real figures, but self-reported by Decagon rather than independently audited, so treat them as directional rather than guaranteed outcomes for any new deployment.
Pricing & Feature Comparison
Dimension
Intercom Fin
Ada
Decagon
Published pricing
Yes — from $0.99/outcome
No
No
Requires base helpdesk seats
No — can run standalone on any helpdesk
Not stated publicly
Not stated publicly
Channels
Chat (plus Intercom’s phone/SMS/WhatsApp add-ons)
Voice, Messaging, Email
Voice, chat, email (unified)
Target customer size
SMB through enterprise (seat tiers span $19–$132/seat)
Enterprise
Large enterprise
Named workflow-builder feature
Fin (per-outcome agent) + Copilot for human agents
Playbooks, Ada Computer
Agent Operating Procedures, Missions
Pros and Cons
Intercom Fin
Pros: Only one of the three with transparent, public pricing; can run standalone without Intercom seats; usage-based model aligns cost to actual resolutions
Cons: “From $0.99” is a floor, not a guaranteed flat rate — actual per-outcome cost can be higher depending on complexity; add-ons (Copilot, Pro, Proactive Support Plus) add further cost
Ada
Pros: Dedicated agentic tooling (Ada Computer, Playbooks) built specifically for task completion, not just answering
Cons: Zero public pricing; full sales cycle required just to get a quote
Cons: Zero public pricing; headline resolution/deflection stats are vendor-reported, not independently verified
Who It’s a Good Fit For
Intercom Fin suits teams of any size that want a transparent, usage-based AI agent they can test and scale without a lengthy procurement process, especially if they’re already on or open to Intercom’s helpdesk. Ada suits enterprises wanting deep agentic task-completion tooling and are prepared for a custom sales process. Decagon suits very large enterprises, especially in regulated or high-volume consumer sectors (airlines, telecom, fintech), that need voice, chat, and email unified under one agent layer and have the scale to justify a bespoke enterprise contract.
Who Should Look Elsewhere
Smaller teams without enterprise procurement resources may struggle to even get a ballpark number from Ada or Decagon; Fin’s public per-outcome pricing makes it far easier to budget for without a sales call. Teams expecting a flat, predictable monthly AI-agent fee (rather than usage-based billing) should clarify Fin’s actual outcome volume and cost before committing, since “$0.99 per outcome” scales with support volume rather than staying fixed.
Bottom Line
Intercom Fin stands out in this category simply for publishing a real number — $0.99 per resolved outcome, available standalone or alongside Intercom’s seat-based plans. Ada and Decagon both pitch themselves at the enterprise end of the market and keep pricing entirely behind a demo request, so any cost comparison against Fin has to wait until you’ve actually talked to their sales teams. If budget transparency matters as much as capability, that asymmetry should weigh into the decision.
FAQ
Is Intercom Fin priced per seat or per resolution? Per resolution. Intercom’s own pricing page lists Fin “from $0.99 per Fin outcome,” separate from its $19–$132/seat/month helpdesk plans, and Fin can also be bought standalone with no seats required.
Can I get a price for Ada or Decagon without a sales call? No. Neither company publishes pricing, tiers, or rates on its public website; both require booking a demo to get a quote.
Does Intercom Fin require using Intercom’s base helpdesk plan? No. Per Intercom’s pricing page, Fin can be deployed standalone on top of an existing helpdesk, with no Intercom seats required, at the same starting per-outcome rate.
Are Decagon’s resolution-rate statistics independently verified? No. Figures like the 70% resolution rate cited for Chime and 80% deflection rate cited for Duolingo are reported by Decagon on its own marketing pages, not from an independent audit.
Spreadsheet budgeting only gets you so far once you’ve got multiple accounts, shared expenses, and investments to track. YNAB, Monarch Money, and Copilot Money are three of the most talked-about personal finance apps right now, each with a different philosophy on how budgeting should work. We pulled pricing and platform details straight from each company’s own site to see how they actually compare.
At a Glance
App
Price
Free Trial
Platforms
Best For
YNAB
$14.99/mo or $109/yr (~$9.08/mo)
34 days, no card required
iOS, Android, Web
Hands-on zero-based budgeters
Monarch Money
$14.99/mo or $99.99/yr
First week free (per site); 30% off annual Core with promo code
iOS, Android, Web
Couples and households wanting shared net-worth tracking
Copilot Money
$9/mo or $109/yr (regular $119/yr)
1 month free
iPhone, iPad, Mac, Web (no Android)
Apple users who want AI-assisted categorization with a polished native app
Short Verdict
YNAB remains the gold standard for zero-based, envelope-style budgeting and gives subscribers the longest free trial (34 days) plus free sharing with up to five other people. Monarch Money is built more around household-wide net worth and investment tracking than strict envelope budgeting, with a lower annual price than YNAB. Copilot Money is the cheapest on paper and leans on AI for auto-categorization and a slick native design, but it’s locked to Apple’s ecosystem — there’s no Android app, only iPhone, iPad, Mac, and a web companion.
YNAB (You Need A Budget)
YNAB charges $14.99/month or $109/year, which works out to about $9.08/month when billed annually — a $70 savings versus paying monthly, according to YNAB’s own pricing page. Signing up directly through YNAB gets you a 34-day free trial with no credit card required (third-party app stores may ask for card details). YNAB’s subscription covers real-time syncing across devices, savings and spending goal tracking, debt-management tools including an integrated loan calculator, and bank import for select US, Canadian, UK, and EU institutions, with file-based import available elsewhere. One subscription can be shared with up to five additional people at no extra cost. College students can get a full 365-day free trial with proof of enrollment, and anyone upgrading from the old YNAB 4 desktop app gets a 10% lifetime discount on the annual plan.
Monarch Money
Monarch Money (whose pricing page now lives at monarch.com) lists two tiers: a base Core plan and a Plus plan, priced at $14.99/month or $99.99/year. The site offers 30% off the annual Core plan for new users with a promo code, and headlines a “your first week is on us” offer, though the exact trial terms aren’t spelled out in detail on the page itself. Plus is pitched at people managing more than day-to-day budgeting — it adds forecasting tools, tracking of multiple income sources, and deeper investment-tracking features. Both tiers include cancel-anytime terms and a money-back guarantee. Monarch is built to be used by couples or households jointly, with shared visibility into accounts and goals.
Copilot Money
Copilot Money’s own pricing page lists $9/month, or $109 billed yearly as a limited-time offer (the standard annual price is $119). It offers a 1-month free trial. There’s a single plan — no tiers, no add-ons, no separate AI credits, according to Copilot’s own site. The subscription includes connections to more than 16,000 banks, an AI-driven “money assistant” for categorization and insights, and support from real people rather than just a chatbot.
Platform note: Copilot Money is built for Apple’s ecosystem. Per Copilot’s own FAQ page, the officially supported platforms are the iPhone, iPad, and Mac apps, plus a web app — there is no Android app. If you’re not on Apple hardware (or need a native Android experience), Copilot simply isn’t an option; YNAB and Monarch both run natively on Android as well as iOS.
Pricing & Platform Comparison
Factor
YNAB
Monarch Money
Copilot Money
Monthly price
$14.99
$14.99
$9
Annual price
$109 (~$9.08/mo)
$99.99
$109 (limited-time; $119 regular)
Free trial
34 days
First week free (per site)
1 month
Android support
Yes
Yes
No
Shared access
Up to 5 extra people, included
Built for joint/household use
Partner invite listed as coming later in the year
Pros and Cons
YNAB
Pros: Longest free trial at 34 days, no card required; free sharing with up to 5 people; strong debt and goal tracking; cross-platform including Android
Cons: Highest effective monthly cost if you pay month-to-month rather than annually; the zero-based method has a learning curve
Monarch Money
Pros: Lowest published annual price of the three; strong household/investment-focused features on the Plus tier; promo discount available
Cons: Pricing page doesn’t clearly spell out full trial terms; Core plan’s exact feature list isn’t detailed on the pricing page itself
Copilot Money
Pros: Cheapest monthly price; single straightforward plan with no add-ons or tiers; AI-assisted categorization; connects to 16,000+ banks
Cons: No Android app — iPhone, iPad, Mac, and web only; partner/shared access isn’t available yet (listed as coming later in the year)
Who It’s a Good Fit For
Choose YNAB if you want a disciplined, envelope-style budgeting method and plan to split the cost with family members.
Choose Monarch Money if you and a partner want shared visibility into net worth, investments, and multiple income streams.
Choose Copilot Money if you’re fully on Apple hardware and want a clean, AI-assisted app without juggling tiers or add-ons.
Who Should Look Elsewhere
Android users should skip Copilot Money entirely, since it has no Android app. Anyone wanting strict envelope/zero-based budgeting discipline may find Monarch’s and Copilot’s more net-worth-centric approaches less structured than YNAB’s method.
Bottom Line
These three apps solve overlapping but distinct problems. YNAB is the most structured budgeting method with the best trial terms. Monarch Money is the better fit for households tracking net worth and investments together at a lower annual price. Copilot Money is the cheapest and most AI-forward, but only if every budget-holder in your household is on an Apple device. Platform compatibility, more than price, is likely to be the deciding factor for most readers.
FAQ
Is Copilot Money available on Android? No. Per Copilot’s own FAQ, supported platforms are iPhone, iPad, Mac, and a web app — there is no Android app.
Which app is cheapest? Copilot Money has the lowest monthly list price at $9/month. On an annual basis, Monarch Money’s $99.99/year is the lowest published annual price among the three.
Can I share an account with my partner? YNAB includes sharing with up to five additional people at no extra cost. Monarch Money is designed around joint household use. Copilot Money lists partner-invite functionality as coming later this year, so it isn’t available yet per the company’s own site.
Do any of these require a credit card to start a free trial? Signing up for YNAB directly through its own site requires no credit card for the 34-day trial (third-party app stores may differ). Monarch’s and Copilot’s trial sign-up requirements for cards aren’t detailed in the pages we reviewed, so check at checkout.
Social listening and brand monitoring platforms track what’s being said about a brand, product, or topic across social networks, news, forums, and review sites — at a scale no human team could read manually. Brandwatch, Sprinklr, and Meltwater are three of the largest names in this category, each aimed primarily at enterprise marketing, communications, and research teams. One thing all three have in common: none of them publish dollar pricing. Here’s an honest look at what each platform offers and why you’ll need to talk to sales no matter which you choose.
At a Glance
Platform
Best For
Pricing
Standout Feature
Brandwatch
Market research and consumer insights teams
Custom quote; “standard to enterprise” plans per solution
Iris AI assistant over ~1.7 trillion historical conversations
Sprinklr
Large enterprises wanting listening unified with CX/social management
Custom quote only; no published tiers
Insights suite spans listening, surveys, LLM Insights, and video intelligence
Meltwater
Comms and PR teams needing media + social monitoring together
Custom quote across four named tiers
Full Reddit firehose access plus traditional media monitoring
Short Verdict
Brandwatch is the strongest pick if your priority is deep historical data and AI-assisted consumer research. Sprinklr makes the most sense if social listening needs to plug directly into a broader customer experience and social management operation rather than stand alone. Meltwater is the natural fit for communications and PR teams who want media monitoring and social listening in a single contract rather than two separate tools. None publish pricing, so budget conversations start with a sales call regardless of which you pick.
A Note on Pricing Transparency
We checked each vendor’s official pricing pages directly for this comparison. Brandwatch’s pricing page describes “custom plans across three solutions” and “standard to enterprise plans,” with every option leading to a demo request — no dollar figures appear anywhere. Meltwater states outright that it “uses tailored pricing rather than a one-size-fits-all list,” though it does name four plan tiers (Starter, Pro, Enterprise, and Agency) that all include Media Intelligence and Social Listening. Sprinklr’s site likewise shows no pricing — only “Demo,” “Contact us,” and “Talk to an expert” calls to action. If a comparison article elsewhere claims to show you exact Brandwatch, Sprinklr, or Meltwater prices, treat that figure as a third-party estimate, not an official rate.
Brandwatch: Deep History, AI-Assisted Research
Brandwatch’s Consumer Intelligence product is built around a four-step workflow — search, segment, analyze, and act — and leans heavily on scale: the company cites roughly 1.7 trillion historical conversations dating back to 2010, with about 501 million new conversations added daily, including official firehose access to X (formerly Twitter) and Tumblr alongside coverage of Facebook, Instagram, LinkedIn, Threads, Bluesky, broadcast, reviews, and news. Its generative AI assistant, Iris, is designed to turn raw conversation data into readable insights, and the platform includes AI-powered image analysis (identifying objects, scenes, logos) and machine-learning-based auto-segmentation. Brandwatch targets market researchers, social and PR teams, and agencies across industries like retail, CPG, financial services, and pharma.
Sprinklr: Listening as Part of a Unified CXM Platform
Sprinklr Insights is one of four suites on Sprinklr’s broader Unified-CXM platform, and Social Listening is just one module within it — alongside Competitive Insights and Benchmarking, Product Insights, Location Insights, Visual Insights, Surveys, and newer additions like LLM Insights and Video Intelligence. Platform-wide, Sprinklr cites coverage of 23 social channels and 11 messaging channels plus chat, SMS, and email, with its Social suite separately citing 30+ digital and social channels. The company describes “over a decade of AI innovation,” with specialized, generative, and agentic AI features, and recent 2026 product updates (its Spring ’26 release) added further AI copilots and LLM-based insight generation. Sprinklr is positioned for large enterprises — the site says it’s used by “thousands of the world’s largest enterprises” — spanning industries like CPG, financial services, retail, and travel.
Meltwater: Media Monitoring and Social Listening Together
Meltwater packages Media Intelligence and Social Listening into every one of its four named plans — Starter (small comms/marketing teams and startups), Pro (regional, multi-channel marketing orgs), Enterprise (global brands across multiple markets), and Agency (agencies managing multiple clients). Its social listening coverage spans 20+ networks including X, Meta (public data), YouTube, TikTok, LinkedIn, Reddit (full firehose access), Threads, Bluesky, Pinterest, Snapchat, Discord, and Twitch, plus regional platforms like WeChat, Weibo, and Naver — with claimed coverage across 200+ countries and 240+ languages. Features include real-time alerting on sentiment shifts and spikes, competitor share-of-voice tracking, automated dashboards, and an AI assistant (referenced on the site as “Mira”) for sentiment analysis and automated executive summaries.
Pricing & Access Comparison
Brandwatch
Sprinklr
Meltwater
Published dollar pricing
No
No
No
Named plan tiers
Not publicly named (solution-based packaging)
Not publicly named
Starter / Pro / Enterprise / Agency
Free trial / demo
Free demo only
Demo / “talk to an expert” only
Demo via “Contact Sales” on every plan
Reddit firehose access
Not specifically stated
Not specifically stated
Yes, full firehose
Pros and Cons
Brandwatch
Pro: Enormous historical data archive, useful for longitudinal research
Pro: Iris AI assistant and image recognition add real analytical depth
Con: No pricing published anywhere; packaging is “solution-based” and opaque
Con: Best suited to research-heavy use cases, less so pure real-time social care
Sprinklr
Pro: Listening sits alongside social management, CX, and surveys in one platform
Pro: Frequent AI feature releases (LLM Insights, Video Intelligence)
Con: Zero pricing transparency, not even named tiers
Con: Breadth of modules can mean paying for capabilities you don’t need
Meltwater
Pro: Combines traditional media monitoring with social listening in one contract
Pro: Clear tier names (Starter/Pro/Enterprise/Agency) make it easier to ask the right questions in a sales call
Con: Still fully quote-based — tier names don’t come with prices
Con: Agency tier aside, less tailored to pure market-research use cases than Brandwatch
Who It’s a Good Fit For
Choose Brandwatch if your priority is deep historical and consumer-insight research rather than day-to-day social media management. Choose Sprinklr if you want listening embedded in a single platform alongside social publishing, customer care, and CX workflows. Choose Meltwater if your team handles both PR/media monitoring and social listening and wants one vendor and one contract for both.
Who Should Look Elsewhere
All three of these platforms are built for enterprise budgets and enterprise procurement processes. If you’re a small business or solo marketer who just wants to track brand mentions and sentiment without a multi-week sales cycle, a lighter-weight, self-serve social listening tool will almost certainly serve you better and faster than any of these three.
Bottom Line
Brandwatch, Sprinklr, and Meltwater are all capable, enterprise-grade platforms, but comparing them on price isn’t possible from public information — all three require a sales conversation before you’ll see a number. The honest way to choose is by use case: Brandwatch for research depth, Sprinklr for CX/platform breadth, and Meltwater for combined media-and-social monitoring. Get quotes from at least two before signing, since none of them anchor pricing publicly and negotiated rates can vary significantly by deal size.
FAQ
Do any of these three publish pricing? No. As of this writing, Brandwatch, Sprinklr, and Meltwater all require a sales conversation or demo request to get a quote — none list dollar amounts on their official pricing pages.
Which tool offers the most social network coverage? Meltwater publishes the most specific coverage claims (20+ networks, 200+ countries, 240+ languages) including full Reddit firehose access. Brandwatch and Sprinklr also cover major networks broadly but publish fewer specific numbers.
Is any of these three suitable for a small business? Not really — all three are built and sold for enterprise or large mid-market budgets and typically involve a sales cycle rather than self-serve signup.
Can I get a free trial of any of them? Public pricing pages for all three point to demos rather than self-serve free trials, so a trial (if offered at all) would need to be arranged directly with sales.
Most of the coverage of Nvidia’s data center push focuses on the GPU — Blackwell’s transistor count, its tensor core throughput, its NVLink fabric. But sitting next to that GPU in Nvidia’s highest-end systems is a CPU most of the conversation skips past: Grace, Nvidia’s own Arm-based processor. Grace isn’t a side project — it’s the piece that lets Nvidia build “superchips” where a CPU and one or more GPUs share a single coherent memory space at bandwidths ordinary PCIe-connected x86 servers can’t match. This piece focuses specifically on Grace and the Arm-based CPU+GPU architecture it enables, distinct from Blackwell’s own GPU architecture, which Nvidia documents separately.
At a Glance
Product
Composition
CPU Cores
CPU Memory
CPU-GPU Interconnect
Grace CPU Superchip
2x Grace CPU chips (CPU-only)
144 Arm Neoverse V2 cores total (72 per chip)
Up to 960GB LPDDR5X
900 GB/s NVLink-C2C (chip-to-chip)
Grace Hopper Superchip
1x Grace CPU + 1x Hopper GPU
72 Arm Neoverse V2 cores
Up to 480GB LPDDR5X
900 GB/s NVLink-C2C, coherent CPU-GPU memory
GB200 Grace Blackwell Superchip
1x Grace CPU + 2x Blackwell GPUs
72 Arm Neoverse V2 cores
Up to 480GB LPDDR5X at up to 512 GB/s
NVLink-C2C per GPU; 3.6 TB/s total NVLink bandwidth
Short Verdict
Grace matters because of what it enables rather than because of raw CPU benchmarks: a CPU-GPU link fast enough and coherent enough that the GPU can treat CPU memory almost like an extension of its own, instead of waiting on comparatively slow PCIe transfers. For workloads that move enormous amounts of data between CPU and GPU — large language model training and inference chief among them — that coherent link is often a bigger practical win than any single spec. For general-purpose, GPU-free workloads, the standalone Grace CPU Superchip is Nvidia’s bet that Arm-based energy efficiency can compete with established x86 server CPUs on performance-per-watt, which is Nvidia’s own claim and worth validating against independent benchmarks for any specific workload before committing.
What a “Superchip” Actually Is
Nvidia’s “superchip” naming refers to multiple dies — two CPUs, or a CPU and GPUs — packaged and connected via Nvidia’s NVLink Chip-to-Chip (NVLink-C2C) interconnect, rather than communicating over a standard motherboard bus like PCIe. The Grace CPU Superchip connects two Grace CPU dies over NVLink-C2C at 900 GB/s, for a combined 144 Arm Neoverse V2 cores and up to 960GB of LPDDR5X memory — a CPU-only product aimed at traditional server workloads that still benefit from Arm’s power efficiency, with no GPU involved. The Grace Hopper Superchip instead pairs one Grace CPU with one Hopper GPU, and the GB200 Grace Blackwell Superchip pairs one Grace CPU with two Blackwell GPUs — in both cases using the same NVLink-C2C link, but now joining a CPU to GPUs rather than CPU to CPU.
Why Arm Instead of x86
Grace is built on Arm’s Neoverse V2 core design rather than x86, the architecture nearly all traditional data center CPUs (Intel Xeon, AMD EPYC) use. Nvidia’s rationale, laid out in its own architecture documentation, centers on power efficiency and memory design choices that are easier to make from a clean-sheet Arm design: Grace uses server-class LPDDR5X memory with ECC — which Nvidia describes as the first use of this memory class in a data center server CPU — instead of the DDR5 or HBM found in most server CPUs. Nvidia states LPDDR5X delivers up to 500 GB/s of bandwidth at around 16W, roughly one-fifth the power of comparable DDR5 memory, and claims the Grace CPU Superchip offers roughly 2x the performance-per-watt of traditional x86 server CPUs using DDR5, plus up to 3x better energy efficiency on graph analytics workloads versus leading x86 systems in Nvidia’s own benchmark configurations. Grace is far from the only Arm server chip in this market — AWS’s Graviton and Google’s Axion take a similar power-efficiency bet on Arm — but Grace is distinguished by being built specifically to pair with Nvidia’s own GPUs via NVLink-C2C, which neither Graviton nor Axion is designed to do.
The Real Differentiator: Coherent CPU-GPU Memory
In a conventional x86 AI server, the CPU and GPU are separate chips connected over PCIe, with each maintaining its own distinct memory pool; moving data between them means explicit transfers across a comparatively narrow, higher-latency link, and the CPU and GPU do not share a unified view of memory. Grace-based superchips change that by connecting CPU and GPU dies with NVLink-C2C at 900 GB/s — roughly 7x the bandwidth of PCIe Gen5 x16 — and, in the Grace Hopper and Grace Blackwell designs, maintaining memory coherency between the CPU’s LPDDR5X and the GPU’s HBM. In practice, this means the GPU can address CPU-attached memory (and vice versa) without the application explicitly managing separate memory pools and copies, which matters most for workloads with large memory footprints that exceed what fits in GPU HBM alone, such as large-scale LLM training and serving. The GB200 superchip, for instance, pairs 480GB of Grace’s LPDDR5X with 372GB of Blackwell HBM3E running at 16 TB/s, giving a combined system memory pool the GPU can draw on far beyond its own onboard HBM.
From Superchip to Rack: GB200 NVL72
Nvidia scales the Grace Blackwell architecture up from an individual superchip to a full rack in its GB200 NVL72 system, which combines 36 Grace CPUs and 72 Blackwell GPUs (18 GB200 superchips) in a single liquid-cooled rack. Nvidia’s NVLink Switch System connects all 72 GPUs into one NVLink domain that Nvidia describes as functioning like a “single massive GPU,” with 130 TB/s of aggregate NVLink bandwidth. At the rack level, the combined Grace CPU memory reaches 17 TB of LPDDR5X alongside 13.4 TB of HBM3E GPU memory. This is the Grace architecture’s clearest demonstration: Nvidia isn’t just building a fast chip, it’s building an entire rack-scale system where CPU, GPU, memory, and interconnect are co-designed, something that’s much harder to replicate by bolting Nvidia GPUs onto a generic x86 server platform.
Trade-offs
Pros: NVLink-C2C’s 900 GB/s CPU-GPU link and coherent memory substantially reduce data-movement bottlenecks for memory-intensive AI workloads; LPDDR5X’s power efficiency reduces overall system power draw; Arm Neoverse V2 cores bring strong performance-per-watt for general compute running alongside GPU work.
Trade-offs: Arm-based Grace requires software compiled or recompiled for Arm (aarch64), which can complicate migration for organizations with deep x86-specific toolchains, legacy binaries, or Arm-incompatible dependencies; Grace-based systems are tightly coupled to Nvidia’s own GPU and interconnect roadmap, which is a form of platform lock-in distinct from a generic x86 server that can pair with GPUs from multiple vendors.
Who This Matters For
Infrastructure teams designing or procuring large-scale AI training and inference clusters are the primary audience, especially where model or dataset sizes push against the memory limits of GPU HBM alone. It also matters to organizations evaluating Arm as a general-purpose server CPU architecture for efficiency reasons, independent of any GPU attachment, via the standalone Grace CPU Superchip. It’s less relevant to teams running smaller, GPU-memory-bound workloads that don’t benefit meaningfully from CPU-GPU memory coherence.
Bottom Line
Grace is Nvidia’s answer to a specific bottleneck: moving enormous volumes of data between CPU and GPU fast enough, and coherently enough, that it stops being the limiting factor in large AI workloads. The Arm-based Neoverse V2 design gives Nvidia the power-efficiency and clean-sheet flexibility to build NVLink-C2C directly into the chip, something retrofitting onto an existing x86 design would be far harder to do. Whether evaluating a standalone Grace CPU Superchip for general compute or a GB200/GB300 Grace Blackwell system for AI training and inference, the architectural story is the same: CPU and GPU designed together as one coherent memory system, not bolted together after the fact.
FAQ
Is Grace a GPU or a CPU? Grace is a CPU — specifically an Arm-based processor built on Arm Neoverse V2 cores. It’s a separate product from Nvidia’s GPUs (Hopper, Blackwell), though it’s frequently paired with them in “superchip” designs.
What’s the difference between the Grace CPU Superchip and Grace Hopper/Grace Blackwell? The Grace CPU Superchip connects two Grace CPU dies together with no GPU involved, aimed at general-purpose server workloads. Grace Hopper and Grace Blackwell instead connect one Grace CPU to one or more GPUs (Hopper or Blackwell, respectively) over the same NVLink-C2C interconnect, aimed at AI training and inference.
Why does CPU-GPU memory coherence matter? It lets a GPU effectively draw on CPU-attached memory without explicit, slower data copies across a narrower bus, which matters most for workloads — like large language models — whose memory footprint exceeds what fits in the GPU’s own onboard HBM memory.
How is Grace different from AWS Graviton or Google Axion? All three are Arm-based server CPUs built for power efficiency, but Graviton and Axion are general-purpose cloud CPUs not designed around a coherent GPU interconnect. Grace is built specifically to pair with Nvidia’s own GPUs via NVLink-C2C, which is its core differentiator.
Do I need to recompile software to run on Grace? Generally yes. Because Grace uses the Arm (aarch64) instruction set rather than x86, software needs to be compiled for Arm, or already have Arm-compatible builds available, to run natively.
E-commerce sellers outgrow spreadsheets fast, and the gap between “we track stock in a sheet” and “we need real inventory and order management” usually opens right when order volume starts to matter. Zoho Inventory, Cin7 Core, and Katana MRP all promise to close that gap, but they’re built for different sellers: one is an affordable all-rounder, one is a multi-channel and manufacturing powerhouse, and one is a production-floor-first tool that recently rebuilt its pricing around a free tier plus custom contracts. Here’s how their official pricing and features actually compare.
At a Glance
Software
Starting Price
Free Plan
Best For
Zoho Inventory
$29/org/month (annual), $0 free tier
Yes – up to 50 orders/month, 1 user, 1 location
Small to mid-size e-commerce sellers on a budget
Cin7 Core
$349/month
No
Multi-channel brands that also need light manufacturing/MRP
Katana MRP
$0 (Free, up to 30 SKUs); Advantage tier is custom-quoted
Yes – limited to 30 SKUs
Manufacturers needing production planning tightly linked to inventory
Short Verdict
Zoho Inventory is the clear pick for sellers who want solid multichannel inventory and order management without a big monthly bill — its $29/month Standard plan undercuts the other two by hundreds of dollars. Cin7 Core costs ten times as much to start ($349/month) but earns it with unlimited locations, deeper manufacturing (MRP) tools, and higher order ceilings built for brands already doing real volume. Katana MRP sits in between in a different way: its new Free plan (30 SKUs) is genuinely usable for a very small manufacturer, but anything beyond that requires a custom “Advantage” contract with no published price, so budgeting for growth means a sales call, not a pricing page.
Zoho Inventory: Affordable and Full-Featured for Small Teams
Zoho Inventory’s free plan covers 1 user, 1 warehouse location, and up to 50 orders per month — enough to test the platform but not to run a real store on. The paid tiers, billed per organization per month (annual billing), are Standard at $29 (500 orders/month, 3 users, 2 locations), Premium at $79 (3,000 orders/month, 5 users, 4 locations, 500 bins per location), Plus at $129 (7,500 orders/month, 10 users, 6 locations), and Enterprise at $249 (15,000 orders/month, 10 users, 10 locations, 5,000 bins per location). As part of the broader Zoho ecosystem, it integrates cleanly with Zoho Books, Zoho CRM, and major marketplaces like Amazon, eBay, Etsy, and Shopify.
Cin7 Core: Built for Multi-Channel Scale and Manufacturing
Cin7 Core (formerly DEAR Systems) starts at $349/month for the Standard plan: 5 users, 2 e-commerce/app integrations, and 6,000 sales orders per year, with unlimited inventory locations included at every tier. Pro, the most popular tier at $599/month, raises that to 10 users, 4 integrations, 24,000 orders/year, and adds material requirements planning (MRP) for light manufacturing. Advanced, at $1,199/month, goes to 15 users, 6 integrations, 120,000 orders/year, and adds advanced warehouse management. Additional users, integrations, and order volume can be purchased beyond those caps, and add-ons like ForesightAI demand forecasting, a B2B portal, POS, and advanced automations cost extra on top of the base subscription.
Katana MRP: Manufacturing-First, Now Freemium Plus Custom Contracts
Katana has moved away from its old tiered-pricing structure to a two-plan model: Free, which costs $0 and includes unlimited users, integrations, and inventory locations but caps you at 30 SKUs (with only Shopify as an available e-commerce integration), and Advantage, a custom-priced annual contract that unlocks unlimited SKUs plus a dedicated implementation manager, 24/7 live support, custom integrations and dashboards, and an SLA. Katana doesn’t publish an Advantage price anywhere on its site, so anyone past the 30-SKU Free tier needs to request a quote to know what they’ll actually pay — a real limitation if you’re trying to compare costs without talking to sales first.
Zoho Inventory: Lowest cost of the three with a genuinely usable free tier; tight integration with Zoho Books/CRM and major marketplaces.
Cin7 Core: Unlimited locations on every plan; built-in MRP from the Pro tier up, good for brands blending retail, wholesale, and light manufacturing.
Katana MRP: Free plan has no time limit and includes unlimited users/locations; strong production-floor and shop-floor features once on Advantage.
Cons
Zoho Inventory: Order and location caps climb quickly on paid tiers, which can push high-volume sellers to the top of the range fast.
Cin7 Core: Starting price is steep for small sellers, and extra users/integrations/orders cost more on top of the base plan.
Katana MRP: Free tier’s 30-SKU cap is restrictive for most real catalogs, and Advantage pricing is entirely hidden behind a sales call.
Who It’s a Good Fit For
Zoho Inventory suits small to mid-size online sellers who want multichannel order and stock tracking without a big line-item in the budget, especially if they’re already using other Zoho apps. Cin7 Core fits growing multi-channel brands — wholesale plus D2C plus marketplaces — that need unlimited warehouses and light manufacturing without a dedicated MRP system. Katana MRP is the right call for small manufacturers or makers who need production scheduling tied directly to inventory, as long as they’re comfortable with an undisclosed price once they outgrow 30 SKUs.
Who Should Look Elsewhere
High-volume sellers who need enterprise-grade warehouse management at a predictable monthly price may find Cin7 Core’s add-on costs stack up quickly. Budget-conscious manufacturers who need more than 30 SKUs but want transparent pricing upfront should treat Katana’s Advantage tier as an unknown until they get a quote. And anyone who needs heavier manufacturing/BOM functionality than Zoho Inventory’s Professional-tier add-ons provide will likely outgrow it.
Bottom Line
If budget is the deciding factor, Zoho Inventory wins outright at $29/month for a real paid tier. If you need unlimited warehouses and manufacturing at genuine scale and can absorb a four-figure monthly cost, Cin7 Core is built for that. If you’re a small manufacturer who can live within 30 SKUs or is willing to negotiate a custom contract, Katana MRP’s shop-floor-first design is worth the trade-off of hidden pricing above the free tier.
FAQ
Does Zoho Inventory have a free plan?
Yes. Zoho Inventory’s free plan includes 1 user, 1 location, and up to 50 orders per month, with no cost.
Does Cin7 Core offer a free trial?
Cin7 Core’s pricing page doesn’t list a free plan; pricing starts at $349/month for the Standard tier. Check Cin7’s site directly for any current trial offers, as these can change.
How much does Katana MRP cost above the free plan?
Katana doesn’t publish a price for its Advantage tier, which is required once you exceed 30 SKUs. It’s sold as a custom annual contract, so you’ll need to contact Katana directly for a quote.
Which of these three is best for a small manufacturer?
Katana MRP is purpose-built for manufacturing and production scheduling tied to inventory, making it the strongest fit if your business makes products rather than just reselling them — as long as your SKU count and budget work with its pricing structure.
SIEM (Security Information and Event Management) has a reputation as an enterprise-only category — expensive licenses, dedicated SOC analysts, and six-figure deployments. That reputation is only half-true in 2026. A small or mid-size business doesn’t need the same SIEM a Fortune 500 security operations center runs, but it does increasingly need some way to centralize logs, detect anomalies, and prove compliance. Wazuh, Microsoft Sentinel, and Splunk sit at three very different points on that spectrum: free and self-hosted, cloud-native and consumption-priced, and enterprise-grade with pricing available only on request.
This comparison focuses specifically on SMB feasibility — what it actually takes to stand up and run each one with a small IT or security team, not just feature checklists built for a 24/7 SOC.
At a Glance
Tool
Deployment
Licensing Cost
Pricing Model
SMB Feasibility
Wazuh
Self-hosted (or Wazuh Cloud) open source
$0 for the platform itself
Free and open source; paid Wazuh Cloud and professional support available but not published publicly
High if you have in-house Linux/infra skills; low if you need a vendor to run it for you
Microsoft Sentinel
Cloud-native (Azure)
Pay-as-you-go by data ingested, or reserved “commitment tier” capacity
Usage-based; no flat license fee, but costs scale with log volume
High for organizations already on Microsoft 365/Azure; ingestion costs need active management
Splunk
Cloud or on-prem (Splunk Enterprise Security)
Not published — “Get a quote”
Quote-based: activity-based, workload, or ingest pricing per Splunk’s own pricing page
Low-to-medium; built and priced for larger security teams, though smaller deployments are possible
Short Verdict
If your business has someone comfortable managing Linux servers and wants to avoid license fees entirely, Wazuh is the most budget-friendly real SIEM available — the platform itself costs nothing. If you’re already deep in Microsoft 365 or Azure and want a SIEM that scales with you without per-seat licensing, Microsoft Sentinel‘s consumption-based model fits well, as long as you actively manage data ingestion volume. Splunk remains the most capable and most “enterprise” of the three, but its pricing is entirely quote-based, which makes it harder to budget for as an SMB without first talking to sales.
Wazuh: Free and Open Source, But You Run It
Wazuh describes itself on its own site as “a free and open source security platform,” available at no cost, that combines SIEM and XDR-style capabilities: log analysis, file integrity monitoring, vulnerability detection, and intrusion detection in one open-source stack. There is no license fee for the core software — you can download, deploy, and run it yourself indefinitely at zero licensing cost.
The catch for SMBs is operational, not financial. Self-hosting Wazuh means you’re responsible for the underlying infrastructure (servers, storage, scaling the indexer as log volume grows), patching, and tuning detection rules yourself. Wazuh the company also offers Wazuh Cloud (a managed, ready-to-use hosted version) plus professional support, consulting, and training — but none of these have published prices on wazuh.com; they require contacting the company directly. If your team already runs Linux infrastructure comfortably, the zero-dollar licensing cost can make Wazuh the cheapest real SIEM option by a wide margin. If you don’t have that skill set in-house, the “free” software can still mean real costs in staff time or a managed-service contract.
Microsoft Sentinel: Cloud-Native, Pay for What You Ingest
Microsoft Sentinel is a cloud-native SIEM built on Azure, and its pricing is entirely consumption-based rather than a flat per-seat license. Per Microsoft’s own pricing page, there are two main ways to pay:
Pay-as-you-go: billed on the volume of data ingested and analyzed, with no upfront commitment.
Commitment tiers: you reserve a fixed amount of daily ingestion capacity, from 100 GB/day up to 50,000 GB/day (a 50 GB/day tier is in public preview), in exchange for savings Microsoft advertises as “up to 52% over Pay-As-You-Go rates.” Usage beyond your committed tier is billed at that same discounted rate, and you can upgrade anytime but can only downgrade after 31 days.
There’s also a modest free allowance — Microsoft states you get “up to 5 MB of free Microsoft Sentinel data ingestion daily per user for key security logs” — plus a newer Sentinel data lake option where some ingested logs can be stored at no additional cost, with a 30-day free period during its preview for storage and processing. Microsoft’s pricing page explicitly notes that displayed figures are estimates and that actual per-GB rates vary by region and are shown in an interactive calculator rather than a flat published table.
For a small business, the appeal is clear: no SIEM license to buy, and if your log volume is modest, your bill scales down with it. The risk is the opposite of a flat fee — a noisy environment or misconfigured data connector can quietly inflate ingestion volume and your monthly bill. SMBs adopting Sentinel should budget time for tuning which data sources actually get ingested, not just for the tool itself.
Splunk: Capable, But Pricing Is a Black Box Until You Call Sales
Splunk’s Enterprise Security product is widely regarded as one of the most powerful SIEM platforms available, with deep correlation, search, and investigation tooling. But Splunk’s own pricing page for Enterprise Security publishes no dollar figures at all. It states that pricing can follow “activity-based, workload, or ingest pricing” models, compares its Essentials and Premier editions by feature (Premier adds SOAR, UEBA, and Automated Threat Analysis, for example), and directs every buyer to “Contact a Splunk pricing expert” or “Get a quote.” The FAQ mentions volume discounts exist, again without numbers.
We are not going to guess at what Splunk costs — it isn’t published, full stop. That opacity is itself a material consideration for SMBs: you cannot self-serve a budget estimate the way you can with Sentinel’s calculator or Wazuh’s “it’s free” baseline. If your business is considering Splunk, plan on a sales conversation and a proof-of-concept scoping exercise before you’ll have a real number, and expect that number to reflect Splunk’s enterprise-oriented positioning.
Pricing & Deployment Model Comparison
Factor
Wazuh
Microsoft Sentinel
Splunk
Core software cost
$0 (open source)
No license fee; usage-based billing
Not published
Managed/cloud option
Wazuh Cloud (price on request)
Native Azure service
Splunk Cloud Platform (price on request)
Support
Community forums free; paid professional support available
Microsoft/Azure support plans
Vendor support included in quoted contract
Best existing-stack fit
Linux-centric, vendor-neutral environments
Microsoft 365 / Azure-centric environments
Large, heterogeneous environments with dedicated SOC staff
Pros and Cons
Wazuh
Pros: No licensing cost for the platform; open source and vendor-neutral; combines SIEM, file integrity monitoring, and vulnerability detection.
Cons: You own the infrastructure and tuning burden unless you pay for Wazuh Cloud or support, and those prices aren’t public.
Microsoft Sentinel
Pros: No flat license fee; scales naturally with Microsoft 365/Azure environments; commitment tiers can cut costs substantially at predictable volumes.
Cons: Costs are directly tied to data ingestion volume, which requires active monitoring to avoid surprise bills; exact per-GB rates aren’t published as flat numbers and vary by region.
Splunk
Pros: Deep search, correlation, and investigation capability; flexible pricing models (activity, workload, or ingest) can be negotiated to fit use case.
Cons: Zero published pricing anywhere on Splunk’s own site; typically positioned and priced for larger security operations, making budget planning hard upfront for a small business.
Who It’s a Good Fit For
Choose Wazuh if you have (or can hire) Linux/infrastructure skills in-house and want to eliminate SIEM licensing costs entirely.
Choose Microsoft Sentinel if you’re already a Microsoft 365/Azure shop and want a cloud-native SIEM billed on usage rather than seats.
Choose Splunk if you need best-in-class search/correlation and have the budget (and patience) for a quote-based enterprise sales process.
Who Should Look Elsewhere
A very small business with no dedicated IT/security staff may struggle to get value out of any of these three without either hiring staff or paying for a managed service layer (Wazuh Cloud, a Sentinel-managed MSSP, or Splunk Cloud) — a basic endpoint protection or DNS filtering tool alone may be a better starting point before investing in a full SIEM. Organizations wanting a fixed, published monthly price with no usage surprises should lean toward Wazuh self-hosted (where the cost is infrastructure, not software) over Sentinel’s consumption billing.
Bottom Line
There isn’t a single “best SIEM for SMBs” — there’s a best fit depending on what resource you have more of: engineering time, Azure budget, or a willingness to negotiate an enterprise contract. Wazuh removes the licensing cost but shifts the burden to your own infrastructure team. Microsoft Sentinel removes the up-front commitment but requires watching your ingestion volume like a utility bill. Splunk offers the deepest capability but requires a sales conversation before you’ll know what it costs. Whichever you pick, scope a pilot with your real log volume before committing — that’s the only way to get a true cost picture for any of the three.
FAQ
Is Wazuh really completely free?
The core Wazuh platform is free and open source, per Wazuh’s own site. Paid options — Wazuh Cloud (managed hosting), professional support, consulting, and training — exist but don’t have published prices; you’d need to contact Wazuh directly for a quote.
How is Microsoft Sentinel priced if there’s no flat fee?
Sentinel bills based on the volume of data you ingest and analyze, either pay-as-you-go or through reserved “commitment tiers” (100 GB/day up to 50,000 GB/day) that offer a discount versus pay-as-you-go rates. There’s also a small free daily allowance per user for certain security logs.
Why doesn’t Splunk publish its SIEM pricing?
Splunk’s own pricing page for Enterprise Security gives no dollar figures and directs every visitor to request a quote, citing multiple possible pricing models (activity-based, workload, or ingest). This is common for enterprise security platforms where deployment size varies enormously between customers.
Can a small business realistically self-host Wazuh?
Yes, but it requires someone comfortable managing Linux servers, storage, and ongoing maintenance. Businesses without that skill set in-house often look at Wazuh Cloud or a managed service provider instead, which reintroduces a cost even though the underlying software license is free.
Sources
Wazuh.com — official site, open-source positioning and services
A cluster of a few thousand nodes needs to know, within a few seconds, which of its peers are alive and which have failed — without a central registry that would itself become a bottleneck and a single point of failure. The standard solution is a gossip protocol (also called epidemic broadcast): nodes periodically exchange small amounts of state with a few random peers, the same way a rumor spreads through a crowd, until everyone converges on the same picture. Cassandra, Consul, and Serf all use gossip for membership and failure detection, and the technique traces back to a specific, well-studied algorithm: SWIM.
AT A GLANCE
Aspect
Detail
What it solves
Decentralized membership tracking and failure detection without a central coordinator
Core mechanism
Each node periodically exchanges state with a small number of random/selected peers; information spreads epidemically
Convergence time
Roughly logarithmic in cluster size (Cassandra’s own docs estimate ~10 seconds to propagate across 1,000 nodes)
Foundational algorithm
SWIM (Scalable Weakly-consistent Infection-style process group Membership), 2002
Real-world users
Apache Cassandra (built-in gossip), HashiCorp Consul and Nomad (via Serf/memberlist library), Serf itself, Akka Cluster
Trade-off
Weak/eventual consistency of membership view in exchange for scalability and no single point of failure
Short Verdict
Gossip protocols solve a genuinely hard problem — keeping every node’s view of cluster membership roughly accurate — without the scalability ceiling of a heartbeat-to-everyone approach or the single point of failure of a central registry. The cost is that membership is only ever “eventually” consistent: at any instant, different nodes may disagree slightly about who’s up or down, and that’s an accepted trade-off rather than a bug. Systems that need to scale to hundreds or thousands of nodes with cheap, constant-size-per-node overhead (Cassandra, Consul, Serf) have standardized on gossip for exactly this reason.
Why Not Just Use Heartbeats?
The naive way to detect failures is for every node to send a heartbeat to every other node (or to a central monitor) on a fixed interval. That works for small clusters, but the message volume grows quadratically with every node you add, and a central monitor becomes both a bottleneck and a single point of failure. Gossip protocols avoid both problems: each node sends a small, fixed number of messages per round regardless of cluster size, and no node holds a privileged, authoritative view. Updates piggyback on messages nodes are already exchanging, and the membership picture converges across the whole cluster through repeated peer-to-peer contact rather than any one node “announcing” the truth.
The SWIM Protocol: The Common Ancestor
SWIM (Scalable Weakly-consistent Infection-style process group Membership), introduced by Das, Gupta, and Motivala in 2002, separates gossip into two concerns that many production systems still mirror today:
Failure detection: Each node periodically picks a random peer and sends it a direct probe. If there’s no response, the node asks several other peers to probe the suspect indirectly — a path through a different route in the network. Only when all of those indirect probes also fail does the node get marked as suspected, which avoids false positives caused by one flaky link rather than an actually-dead process.
Suspicion before death: A node isn’t declared dead the instant it misses a probe. It’s marked “suspected” first and still counts as a member; if it responds before a timeout, the suspicion is refuted. Only an unanswered suspicion for the full timeout results in the node being declared dead and removed from the membership list.
Dissemination via piggybacking: Rather than broadcasting membership changes to everyone, SWIM attaches updates to the probe/ack messages nodes are already sending as part of failure detection. This keeps per-node bandwidth constant as the cluster grows, while the information still reaches everyone within a bounded, logarithmic number of rounds.
HashiCorp later published the “Lifeguard” refinements to SWIM, addressing a specific real-world failure mode: a node that’s simply overloaded (high CPU, network congestion) can look “dead” to its peers even though it’s actually alive, producing false-positive failure reports. Lifeguard adds local health awareness so a struggling node can adjust its own timing, cutting down on these false alarms.
How Cassandra’s Gossip Works
Cassandra implements its own gossip protocol natively (it predates and is independent of SWIM/Serf). Each node runs a gossip round roughly once per second: it contacts one live peer chosen at random, and may also probabilistically contact a currently-unreachable node or a configured seed node, to help heal partitioned views of the cluster. The exchange uses a three-way handshake built around digests — compact summaries of what each node knows — so that only the actually-missing state gets transferred, keeping steady-state bandwidth low.
Each node tracks an EndpointState for every peer it knows about, made of a HeartBeatState (a generation number set when a node starts, plus a version incremented every round — a higher generation always wins, discarding stale pre-restart data) and ApplicationState (versioned key-value pairs like STATUS, TOKENS, SCHEMA, DC, RACK). Failure detection uses the Phi Accrual algorithm, which outputs a continuous suspicion level rather than a binary alive/dead flag; a node is marked DOWN once that level (phi) crosses a configurable threshold (phi_convict_threshold, default 8). UP/DOWN decisions are made locally by each node based on direct communication and are not themselves gossiped — only the underlying state is. Cassandra’s own documentation estimates that information propagates to the whole cluster in roughly O(log N) rounds — about 10 seconds for a 1,000-node cluster.
How Consul and Serf Use Gossip
HashiCorp’s Consul uses Serf, its standalone gossip library (built on SWIM, with the Lifeguard refinements), to run two separate gossip pools, per Consul’s own architecture documentation: a LAN gossip pool, enabled by default, that connects every node within a single datacenter — used for automatic server discovery, distributing failure detection work across the cluster, and fast event broadcasts (default UDP/TCP port 8301) — and a WAN gossip pool that extends gossip between a primary datacenter and secondary datacenters in a multi-region (WAN-federated) deployment, so servers can route cross-datacenter requests (default port 8302). All gossip traffic is encrypted with a dedicated, rotatable gossip key. Serf itself is also used directly by other tools (including HashiCorp Nomad) wherever lightweight membership and event broadcast is needed without pulling in all of Consul.
Pros
No single point of failure — any node can detect and propagate failures.
Constant per-node bandwidth regardless of cluster size, unlike all-to-all heartbeating.
Self-healing: a temporarily partitioned node’s state reconciles automatically once connectivity returns.
Battle-tested at scale across years of production use in Cassandra, Consul, and Serf deployments.
Cons / Trade-offs
Membership views are only eventually consistent — different nodes can briefly disagree about who’s up during propagation.
Convergence time grows (logarithmically) with cluster size, so very large or very high-churn clusters need careful tuning of gossip intervals and fanout.
Overloaded-but-alive nodes can be falsely suspected unless the implementation accounts for it (the problem Lifeguard specifically targets).
Not a substitute for strongly consistent coordination (leader election, distributed locks) — gossip tells you who’s probably alive, not who’s authoritative.
Who It’s a Good Fit For
Gossip is the right tool when you need cluster-wide membership and failure detection that scales horizontally without a central bottleneck — the exact problem faced by wide, peer-to-peer data stores (Cassandra, ScyllaDB) and service-mesh/service-discovery tooling (Consul, Serf, Nomad). It’s a poor fit when you need strongly consistent, immediately authoritative state — that’s what consensus protocols like Raft and Paxos are for, and many systems (including Consul itself, for its own Raft-backed KV store) layer gossip for membership underneath a separate consensus layer for data consistency.
Bottom Line
Gossip protocols trade a small amount of consistency delay for enormous gains in scalability and resilience, by letting nodes spread state the way an epidemic spreads through a population — a handful of random contacts per round, repeated continuously, until everyone converges. SWIM formalized the technique with indirect probing and suspicion-before-death; Cassandra’s native gossip and HashiCorp’s Serf (used by Consul and Nomad) are the two most widely deployed real-world implementations, and understanding how they detect and propagate failures explains a lot about how these systems behave under partial network failure.
FAQ
Is gossip the same as a consensus protocol like Raft? No. Gossip spreads membership/state information probabilistically and eventually; consensus protocols like Raft or Paxos guarantee a strongly consistent, agreed-upon value across a quorum. Many systems use both — gossip for membership, consensus for critical shared data.
How fast does information spread via gossip? Typically in a number of rounds that grows logarithmically with cluster size. Cassandra’s own documentation estimates roughly 10 seconds to propagate across a 1,000-node cluster.
What’s the difference between Cassandra’s gossip and Consul’s gossip? Cassandra implements its own native gossip protocol with Phi Accrual failure detection. Consul uses Serf, a separate library built on the SWIM protocol with HashiCorp’s Lifeguard refinements, run as two pools (LAN and WAN).
Why does SWIM use indirect probing instead of just retrying? A direct probe can fail because of a single bad network path rather than an actually-dead node. Asking other peers to probe the same target through different network paths distinguishes a real failure from a localized connectivity issue, reducing false positives.
Can gossip protocols scale to tens of thousands of nodes? Yes, that’s their main design goal — per-node cost stays roughly constant as the cluster grows, unlike all-to-all heartbeating. Very large deployments still need tuning (probe intervals, fanout, suspicion timeouts) to keep convergence time acceptable.
This is a comparison of AI video dubbing — taking footage or audio you already have and translating it into other languages with AI-generated voice and (in some cases) lip-sync — not AI video generation from a text prompt. HeyGen, ElevenLabs, and Synthesia all sell this as a feature, but they price it differently, cap minutes differently, and support different numbers of languages. Here’s what each one’s own pricing page actually says.
Basic: free, 10 min/mo allowance; Starter from $9 first month, then $19/mo (or $14/mo annual)
Not specified by count on pricing page; dubbing included at all paid tiers
Short Verdict
ElevenLabs is the most dedicated dubbing tool of the three — it’s a named, standalone product (Automatic Dubbing v2) rather than a feature bundled into a bigger avatar-video suite, and it supports 90+ languages with sync-aware translation timing. HeyGen offers the broadest language count once you’re past the free tier (175+ languages and dialects from Creator up) and specifically advertises “lip-sync translation” in its FAQ, though full lip-sync access appears limited on the free tier. Synthesia bundles dubbing into its existing Studio video-creation credits rather than selling it as an independent product, which makes it convenient if you’re already using Synthesia for avatar videos but harder to evaluate purely as a dubbing tool on price alone.
HeyGen: Widest Language Coverage, Tiered by Video Length
Per HeyGen’s own pricing page, the Free plan allows 3 watermarked videos per month, up to 1 minute each, with translation into 30+ languages and limited trial access to “lip-sync translation” per the FAQ. The paid tiers unlock a much larger language list — 175+ languages and dialects — starting at Creator ($29/month, or $24/month billed annually) for videos up to 30 minutes, rising to Pro ($49/month) which adds the ability to edit and proofread translation scripts, and Business ($149/month plus $20/seat/month) for videos up to 60 minutes. Enterprise removes the video-length cap entirely but is custom-quoted. HeyGen’s credit system also scales independently of these plan names — the FAQ cites a range from 1,000 credits at $49/month up to 100,000 credits at $4,300/month for heavier usage, so high-volume dubbing work should be budgeted on credits consumed, not just the named tier.
ElevenLabs: Dubbing-First, Priced in Credits
ElevenLabs treats dubbing as a first-class, named product (Automatic Dubbing v2) available on every self-serve plan, including Free. Per its own dubbing page, the tiers are Free (10,000 credits/month), Starter ($6/month, with a discounted $1 first month, 30,000 credits/month), Creator ($22/month, discounted to $11 the first month, 121,000 credits/month), and Pro ($99/month, 600,000 credits/month). Each tier includes a certain number of dubbed minutes before an extra per-minute rate kicks in — the page’s own figures show the per-extra-minute cost dropping as you move up tiers (roughly $4.91/minute on Free down toward $2.23/minute on Pro), though exact minute allotments per tier weren’t fully legible on the page and should be confirmed with ElevenLabs directly before committing to volume. The feature supports 90+ languages and ElevenLabs describes dubs as “sync-aware,” aligning speech start/stop to the original rather than confirming true lip-sync — a meaningful distinction from HeyGen’s lip-sync claim.
Synthesia: Dubbing as Part of the Broader Studio Credit Pool
Synthesia doesn’t sell dubbing as a separate product; it’s one use of the same monthly credit allowance used for its avatar-video Studio tool. Per its pricing page: Basic is free, with a shared 10-minute allowance for Studio video creation or dubbing; Starter costs $9 for the first month, then $19/month billed monthly (or $14/month billed annually), and includes up to 16 minutes of dubbing per month on the monthly plan (197 minutes/year on annual billing); Pro (labeled “creator” in the site’s URLs) costs $49 for the first month, then $89/month billed monthly (or $59/month billed annually), with up to 78 minutes of dubbing per month on monthly billing (947 minutes/year annually). A separate “1-Click Translation” feature is listed for Business/Enterprise tiers, where the page notes translations consume credits and lip-sync specifically doubles the credit cost when enabled. Business and Enterprise pricing is not published and requires a demo.
Pricing & Feature Comparison
Dimension
HeyGen
ElevenLabs
Synthesia
Dubbing sold as
Feature within avatar-video plans
Standalone named product
Feature sharing Studio’s credit pool
Free tier dubbing
1-min videos, 30+ languages
10,000 credits/mo
10 min/mo shared allowance
Cheapest paid tier
Creator $29/mo ($24 annual)
Starter $6/mo ($1 first month)
Starter $19/mo ($14 annual)
Lip-sync
Advertised (“lip-sync translation”), limited on free tier
Not confirmed; describes timing-aware sync only
Available; doubles credit cost when enabled
Language count
175+ (paid tiers)
90+
Not stated by count
Enterprise
Custom-quoted, no length cap
Not applicable (credit scales up)
Custom-quoted
Pros and Cons
HeyGen
Pros: Largest language count (175+) once past free tier; script editing/proofreading at Pro
Cons: Dubbing is bundled with broader avatar-video pricing, making pure dubbing cost harder to isolate; Business tier adds a per-seat fee on top of the base price
ElevenLabs
Pros: Cheapest paid entry point ($6/mo, $1 first month); dubbing is the actual product, not a side feature; 90+ languages
Cons: No confirmed true lip-sync; exact minutes-per-tier breakdown is not clearly presented on the pricing page
Synthesia
Pros: Lip-sync available and clearly priced (2x credits); convenient if already using Synthesia for avatar videos
Cons: Dubbing minutes are modest on lower tiers (16 min/mo on Starter); shares a credit pool with other video creation, so heavy dubbing use eats into avatar-video capacity
Who It’s a Good Fit For
ElevenLabs suits teams whose primary need is dubbing existing content into many languages at the lowest entry cost, especially podcasts, YouTube content, or e-learning. HeyGen suits teams that want the widest language reach and are comfortable with avatar-video-style pricing. Synthesia suits teams already invested in its Studio avatar-video workflow who want dubbing as a bonus capability rather than a dedicated line item.
Who Should Look Elsewhere
If true lip-sync is a hard requirement, Synthesia’s explicit lip-sync toggle (at double credit cost) is the most clearly documented option — ElevenLabs doesn’t confirm lip-sync, only timing-aware sync. If you need large volumes of dubbed minutes on a predictable low budget, confirm ElevenLabs’ and Synthesia’s exact per-tier minute allotments directly with sales, since both pages leave some of that math less than fully clear.
Bottom Line
For dedicated, lowest-cost dubbing, ElevenLabs is the clearest fit as a standalone, named product starting at $6/month. For the widest language coverage once you’re on a paid plan, HeyGen’s 175+ languages leads the pack. For teams that want dubbing as an extension of an existing avatar-video workflow with explicit lip-sync support, Synthesia is the most integrated option — just expect its dubbing minutes to compete with your other video credits.
FAQ
Is this the same as Midjourney/Runway-style AI video generation? No. This article covers dubbing and translating video/audio you already have into other languages using AI voice and sync — a different category from text-to-video generation tools.
Does ElevenLabs’ dubbing include lip-sync? ElevenLabs’ own dubbing page does not explicitly confirm lip-sync; it describes dubs as “Perfectly Synced” with sync-aware translation timing, which is not the same claim as visual lip-sync.
How many languages does HeyGen’s Video Translate support? 30+ on the Free tier (1-minute videos only), expanding to 175+ languages and dialects from the Creator tier ($29/month) up, per HeyGen’s pricing page.
Does Synthesia charge extra for lip-sync dubbing? Yes. Per Synthesia’s pricing page, enabling lip-sync uses 2x the normal credit cost for that dub.
Unlike most software in this category, ad mediation platforms aren’t sold on a subscription or per-seat basis — they’re free tools that compete for a cut of the ad revenue that flows through your app. For mobile developers monetizing with ads, the mediation layer you pick determines which networks compete for your inventory, how much control you get over the auction, and ultimately how much revenue lands in your account. We looked at the three biggest names — Google AdMob, AppLovin MAX, and Unity LevelPlay — straight from their own documentation.
At a Glance
Platform
Cost to Publishers
Model
Best For
Google AdMob
Free (AdMob API itself is free to use)
Waterfall + bidding mediation groups, with AdMob network as default fallback fill
Developers already in the Google/Ad Manager ecosystem
AppLovin MAX
Free for publishers (“Max mediation is free for publishers”)
Unified real-time auction; bidding networks pay AppLovin a fee on revenue they generate
Teams that want one real-time auction across all demand sources
Unity LevelPlay
Free to integrate (standard mediation revenue-share model)
SDK + platform for mediating multiple ad networks, rebranded from ironSource
Unity game developers already in Unity’s ecosystem
Short Verdict
None of these three platforms charges a subscription fee — the “cost” is embedded in how ad networks pay to participate in each auction, not in a bill to you. AdMob is the easiest default for Android/iOS developers who are already in Google’s ad ecosystem. AppLovin MAX stands out for running every bid, from every network including AppLovin’s own demand, through one unified real-time auction rather than a legacy waterfall. Unity LevelPlay is the natural choice if you’re building in Unity and want mediation tightly integrated with your engine and UA tools, though be aware the underlying ironSource Ads network and exchange are being wound down separately in 2026 (more below).
Google AdMob Mediation
AdMob Mediation lets you manage multiple ad sources for your app from a single dashboard. According to Google’s own support documentation, when an ad unit requests an ad, AdMob compares the request against your mediation groups’ targeting settings (location, platform, format). If one group matches, it fills the request from one of its configured ad sources; if several groups match, the group with the highest priority (lowest priority number) wins. If nothing matches, the default AdMob network group fills the request. Ad sources inside a group can be arranged in a traditional waterfall, or a group can mix real-time bidding sources with waterfall sources — in that hybrid setup, the bidding auction’s winning eCPM is slotted into the waterfall and compared against the other sources’ eCPMs.
Google’s developer pricing page confirms the AdMob API itself is free to use. AdMob doesn’t charge a mediation fee on top; its business model, like the other two platforms here, runs through its own ad network competing for fill alongside third parties.
AppLovin MAX
AppLovin states directly on its MAX product page that “Max mediation is free for publishers.” Instead of charging publishers, AppLovin charges bidding networks a fee on the ad revenue those networks generate through the platform. Every impression runs through a single real-time auction where the highest bid wins, and AppLovin says its own demand competes on equal terms with every other network in that auction, with all bidders receiving the same auction signals — a structural difference from a traditional tiered waterfall.
MAX’s feature set includes user- and impression-level reporting (via dashboard or API), built-in integrations with major MMPs (AppsFlyer, Adjust, Singular, Kochava, Tenjin, Branch), A/B testing of networks and price points, automated ad-quality review, and support for the standard ad formats: rewarded video, app open, interstitial, MREC, banner, and native. A lightweight SDK supports the major platforms and engines, with one-click Unity integration, and AppLovin says most publishers integrate in under a day. A Mediation Debugger tool lets you test ads from every network before launch.
Unity LevelPlay
Unity LevelPlay is Unity’s current mediation product, consisting of a LevelPlay SDK (available for Unity, Android, iOS, Adobe AIR, Flutter, and React Native) and a LevelPlay Platform for configuring mediation settings. LevelPlay traces back to ironSource’s mediation technology; Unity acquired ironSource in 2022 and has continued developing the mediation product under the LevelPlay name, with features like Editor-integrated setup, multiple ad unit support with placement-level waterfall customization, and a unified growth dashboard that combines UA and revenue data.
Important 2026 context: Unity is separately sunsetting “ironSource Ads” — the direct-demand ad network and the ironSource Exchange (iSX) that used to sit alongside LevelPlay. Per Unity’s own sunset page, the ironSource Ads direct-demand business wound down by April 30, 2026, and the ironSource Exchange and the iAds SDK will stop delivering ads entirely on December 31, 2026. Unity says this lets it focus on Unity Vector and a single, unified Unity Ads SDK. This sunset affects the ironSource Ads network and exchange specifically, not the LevelPlay mediation product itself, but developers who relied on ironSource as one of their mediated demand sources should confirm its status directly with Unity before year-end, since Unity’s own FAQ on the sunset page notes the question of LevelPlay’s impact without giving a clear public answer in the material we reviewed.
Model Comparison
Factor
Google AdMob
AppLovin MAX
Unity LevelPlay
Publisher cost
Free (API free to use)
Free (“free for publishers”)
Free to integrate
Auction type
Mediation groups: waterfall, bidding, or hybrid
Unified real-time auction across all demand
SDK/platform mediation with configurable waterfalls
Native ecosystem tie-in
Google Ads / Ad Manager
AppLovin’s own ad network and Ad ROAS tools
Unity engine and UA tools
2026 status note
Stable, actively maintained
Actively maintained, core AppLovin product
Active, but underlying ironSource Ads network/exchange sunsetting in 2026
Pros and Cons
Google AdMob
Pros: Free API; deep integration with Google Ads and Ad Manager; flexible mediation group logic with waterfall/bidding hybrids
Cons: Google doesn’t publicly post a specific revenue-share percentage for mediation on the pages we reviewed, so exact take-rate math requires checking your own account dashboard
AppLovin MAX
Pros: Free for publishers; unified real-time auction instead of a legacy waterfall; strong MMP integrations and ad-quality tooling; fast SDK integration
Cons: AppLovin’s own demand competes in the same auction it operates, so some publishers prefer a visibly independent mediator
Unity LevelPlay
Pros: Tight Unity engine integration; multi-platform SDK; unified growth dashboard combining UA and revenue
Cons: The ironSource Ads network and exchange are being sunset in 2026, adding uncertainty for anyone relying on ironSource as a specific demand source inside LevelPlay
Who It’s a Good Fit For
Choose Google AdMob if your app is already running Google Ads campaigns or using Google Ad Manager and you want mediation that plugs straight into that stack.
Choose AppLovin MAX if you want every demand source, including AppLovin’s own, to compete in one real-time auction rather than a tiered waterfall.
Choose Unity LevelPlay if you’re building in Unity and want mediation setup inside the Editor, but confirm directly with Unity which specific demand sources remain active given the ironSource Ads wind-down.
Who Should Look Elsewhere
Developers who need guaranteed, auditable revenue-share figures in writing before committing should request those numbers directly from each platform’s account team rather than relying on public documentation, since none of the three publishes a flat percentage on the pages we reviewed. Studios not using Unity’s engine get little added benefit from LevelPlay’s Editor-integrated workflow.
Bottom Line
All three platforms are free to integrate, and each earns money by taking a cut of the ad auction rather than charging a subscription. The real decision comes down to ecosystem fit and auction architecture: AdMob for Google-centric stacks, AppLovin MAX for a unified real-time auction with strong tooling, and Unity LevelPlay for Unity-native workflows — with the caveat that Unity is actively retiring the ironSource Ads network and exchange through the end of 2026, so confirm current demand-source availability before building a long-term mediation strategy around it.
FAQ
Do I have to pay to use any of these mediation platforms? No. All three are free to integrate for publishers. They make money by taking a share of the ad revenue generated through their auctions, not by charging you a subscription.
Is ironSource shutting down? The ironSource Ads direct-demand network wound down by April 30, 2026, and the ironSource Exchange (iSX) and iAds SDK stop delivering ads on December 31, 2026, per Unity’s own announcement. Unity LevelPlay, the mediation SDK/platform that succeeded ironSource’s mediation product, is a separate, currently active offering, though developers should verify directly with Unity which demand sources remain live inside LevelPlay after this wind-down.
Can I use more than one mediation platform in the same app? It’s technically possible but adds engineering overhead and complicates reporting, since each platform wants to be the single layer coordinating all your demand sources. Most developers pick one.
What’s the difference between a waterfall and real-time bidding? A waterfall calls ad sources in a fixed priority order, while real-time bidding runs a live auction where sources bid simultaneously for the impression. AdMob supports both, often in hybrid mediation groups, while AppLovin MAX runs all sources through one unified real-time auction by design.
Ask “which of these ten thousand points are within 500 meters of me” and a database with no spatial structure has only one option: check every single point. That’s a linear scan, and it falls apart fast as data grows. Spatial indexing exists to avoid that — and the two structures that dominate real-world systems, from PostGIS to game engines to mapping platforms, are the quadtree and the R-tree. They solve the same underlying problem — fast 2D range and nearest-neighbor queries — with different tree shapes and different trade-offs. This is not about pathfinding or shortest-path graph traversal (covered elsewhere); it’s about finding which objects exist in a region of space quickly.
Irregularly shaped/sized geometries, clustered real-world data
PostGIS spatial queries, GIS platforms, mapping systems
Short Verdict
Both structures beat a linear scan by orders of magnitude for range and nearest-neighbor queries, but they’re tuned for different data. A quadtree is simpler to implement and works well when data is reasonably uniform in density, which is why it shows up constantly in game physics engines for broad-phase collision detection. An R-tree handles real-world geometries — polygons, lines, clustered points of wildly different sizes — more gracefully, which is why it’s the structure PostGIS and most production GIS systems actually use under the hood.
Why Linear Scans Fail at Scale
A naive “find all points in this box” query without an index has to examine every row and test whether it falls inside the box — O(n) work per query, where n is the total number of objects. The PostGIS project’s own introductory workshop materials describe this concretely: in a join between two 10,000-record tables, an unindexed query can require up to 100 million comparisons, versus as few as 20,000 with a spatial index — a difference of roughly four orders of magnitude. A real-world census-block lookup in the same material dropped from around 300ms unindexed to around 50ms indexed, and that gap widens as the table grows. Spatial indexes solve this by pre-organizing objects so a query only has to inspect a small, relevant subset of the tree.
Quadtrees: Recursive Quadrant Splitting
A quadtree recursively divides 2D space into four equal quadrants. Each node represents a rectangular region; when a node holds more objects than some threshold, it splits into four child quadrants (northwest, northeast, southwest, southeast), and objects are reassigned to whichever child region they fall into. A range query walks the tree starting from the root, descending only into quadrants whose bounding region actually intersects the query area, and skipping entire subtrees that don’t.
This is exactly the pattern used for broad-phase collision detection in 2D game engines: rather than testing every pair of game objects for collision (an O(n²) problem), the engine inserts objects into a quadtree each frame and only tests pairs of objects that land in the same or neighboring quadrant. The structure’s weakness is uneven density — if most objects cluster in one quadrant, that branch keeps splitting deeply while the rest of the tree stays shallow, producing an unbalanced tree that no longer gives even performance across the space.
R-Trees: Grouping by Bounding Rectangle
The R-tree was introduced by Antonin Guttman in the paper “R-Trees: A Dynamic Index Structure for Spatial Searching,” published as a UC Berkeley technical report and at ACM SIGMOD 1984. Rather than subdividing fixed regions of space, an R-tree groups nearby objects together and wraps each group in a minimum bounding rectangle (MBR) — the smallest rectangle that fully contains everything in that group. Those rectangles are themselves grouped into larger bounding rectangles at the next level up, forming a balanced tree where every leaf holds actual data and every internal node holds the MBR of its children.
A range query descends the tree checking only which child MBRs overlap the query region, pruning branches whose bounding rectangle doesn’t intersect it at all. Because grouping is based on actual object proximity rather than a fixed grid, R-trees adapt naturally to irregular, clustered, or variably sized geometries — which is exactly the kind of data real maps and GIS datasets contain: a country border, a road network, and a point-of-interest dataset all have wildly different shapes and densities. This is why PostGIS implements its spatial indexes on top of PostgreSQL’s GiST (Generalized Search Tree) index type using an R-tree structure, and why most commercial GIS platforms (including Oracle Spatial, per PostGIS’s own documentation) use the same underlying approach.
How PostGIS Actually Uses This
PostGIS doesn’t index full geometries directly — it indexes each feature’s bounding box, then runs queries in two passes. The index pass quickly finds candidates whose bounding boxes intersect the query box (an approximate, fast filter); a second, exact pass then runs the real geometric test — such as ST_Intersects or ST_DWithin — only on that smaller candidate set. A minimal example of creating that index:
CREATE INDEX idx_places_geom
ON places
USING GIST (geom);
-- Uses the index automatically via the bounding-box filter,
-- then applies the exact distance test:
SELECT name FROM places
WHERE ST_DWithin(geom, ST_MakePoint(-122.42, 37.77)::geography, 500);
Functions like ST_Intersects, ST_Contains, and ST_DWithin use the index automatically. For operations the planner can’t optimize this way, PostGIS documentation recommends adding an explicit bounding-box filter (the && operator) alongside the exact test. It’s also worth noting the planner will skip the index entirely when a query is expected to return most of the table — at that point, a sequential scan is genuinely faster than tree traversal.
Quadtree vs R-Tree: Direct Comparison
Dimension
Quadtree
R-Tree
Partitioning logic
Fixed recursive quadrant splits
Bounding rectangles grouped by proximity
Balance guarantee
Not guaranteed — depends on data distribution
Height-balanced by construction/split algorithm
Handles irregular/variable-size geometries
Poorly — assumes point-like, evenly distributed data
Well — designed explicitly for rectangles of varying size
Implementation complexity
Low
Higher (node-splitting heuristics on insert)
Typical home
Game engines, in-memory spatial structures
Database engines (PostGIS/GiST), GIS platforms
Pros and Cons
Quadtree pros: simple to implement and reason about; cheap to build and rebuild each frame, which suits real-time games.
Quadtree cons: degrades with clustered/uneven data; not the structure most production databases use for persistent spatial indexes.
R-tree pros: handles real-world irregular geometry well; the structure actual spatial databases (PostGIS/GiST) are built on.
R-tree cons: more complex insert/split logic; rebalancing on insert/delete is costlier than a quadtree’s simpler splits.
Who/What Each Structure Fits Best
Quadtrees fit real-time, in-memory use cases where data is rebuilt frequently and rough uniformity can be assumed — game collision broad-phase, terrain/image tiling, and similar simulation workloads. R-trees fit persistent, disk-backed spatial databases handling real-world geographic data with irregular shapes — which is exactly why PostGIS, most commercial GIS software, and mapping platforms build their spatial indexes around R-tree-style structures rather than quadtrees.
Bottom Line
Both quadtrees and R-trees exist to answer the same question — “what’s near this point or inside this region” — far faster than checking every record. The right choice comes down to your data’s shape: evenly distributed, simulation-style data favors a quadtree’s simplicity; irregular, real-world geographic data favors an R-tree’s adaptive bounding-rectangle grouping, which is why it underpins production spatial databases like PostGIS.
FAQ
Is a quadtree the same as an octree? No — a quadtree subdivides 2D space into four regions per split; an octree is its 3D analog, subdividing space into eight regions, commonly used in 3D graphics and voxel engines.
Does PostGIS use quadtrees? No — per PostGIS’s own indexing documentation, its spatial indexes run on PostgreSQL’s GiST index type implementing an R-tree-style structure, not a quadtree.
Are these the same as pathfinding structures like A*? No. Quadtrees and R-trees answer “what objects exist in this region” (spatial range/nearest-neighbor queries); pathfinding algorithms like Dijkstra and A* answer “what’s the shortest route through a graph” — a different problem entirely, even though both are common in games and mapping software.
Who invented the R-tree? Antonin Guttman, in a paper published as a UC Berkeley technical report and presented at ACM SIGMOD in 1984.
All-in-one SEO suites like Ahrefs or Semrush are built for keyword research, backlinks, and rank tracking. They’re not built to crawl a 500,000-page site and tell you exactly which templates are generating duplicate titles, broken canonical tags, or orphaned pages. That’s a different job — technical SEO auditing — and three tools dominate it: Screaming Frog SEO Spider, Sitebulb, and Lumar (formerly DeepCrawl). Here’s how their pricing and crawl capabilities actually compare in 2026.
At a Glance
Tool
Best For
Starting Price
Deployment
Screaming Frog SEO Spider
Freelancers, consultants, and in-house SEOs wanting a desktop crawler
Free (500 URLs) or £199/year per licence
Desktop app (Windows, macOS, Ubuntu)
Sitebulb
Agencies wanting visual, actionable audit reports
Desktop Lite/Pro (price not published) or Cloud from £95/month
Screaming Frog remains the best value for individual SEOs and small agencies — a one-time-feeling annual licence at a published, low price, with virtually every technical SEO check you’d need. Sitebulb is the better choice if your team (or your clients) need the crawl data translated into prioritized, plain-English recommendations rather than raw tables. Lumar is built for enterprises running continuous, scheduled crawls across many large domains and teams, but it comes at enterprise, quote-only pricing with no self-serve tier.
Screaming Frog: The Desktop Standard
Screaming Frog SEO Spider is free to download and use, with the free version capped at crawling 500 URLs — still enough for small sites or quick spot-checks. The paid licence costs £199 per year per user, with volume discounts kicking in at 5+ licences (£189/year each), 10+ (£179/year each), and 20+ (£169/year each). The paid licence removes the URL cap entirely — the practical ceiling depends on your machine’s memory and storage rather than any artificial limit — and unlocks the same full feature set available in the free version otherwise, including crawling, custom extraction, JavaScript rendering, and integrations with Google Analytics and Search Console.
The tradeoff is presentation: Screaming Frog is extremely powerful but shows you raw tables and exportable data rather than prioritized recommendations, so interpreting results takes real technical SEO knowledge.
Sitebulb: Guided Audits With Prioritized Fixes
Sitebulb splits into desktop and cloud products. Desktop Lite covers a single user and audits up to 10,000 URLs, with over 100 “Hints” (its term for flagged issues), JavaScript crawling, and integrations with Google Analytics, Search Console, and Sheets. Desktop Pro covers 1 to 50 users (sold in tiers) and raises the default audit limit to 500,000 URLs (expandable up to 2 million), adding 300+ Hints, advanced configuration, audit comparisons over time, scheduled audits, and customized PDF reporting — with extra users priced from £7/month each. Neither Lite nor Pro publishes a flat headline price on the pricing page. Sitebulb Cloud, aimed at teams needing hosted, collaborative audits with recurring crawls, starts at £95/month per the site’s FAQ, with large-team plans reportedly running above £20,000/year. All desktop plans include a 14-day free trial equivalent to Pro, with no credit card required, and annual billing saves 15% versus monthly.
Sitebulb’s main selling point is interpretation: its “Hints” system doesn’t just surface an issue, it explains why it matters and how to fix it — useful for agencies presenting findings to clients who aren’t SEO specialists themselves.
Lumar: Enterprise-Scale, Modular Crawling
Lumar (the rebranded DeepCrawl) takes a fully modular, quote-only approach with no published pricing anywhere on its site — every plan starts with a sales form. Its platform is built around four core apps: Analyze (crawling and technical analysis), Monitor (tracking changes and trends across many domains over time), Protect (automated website QA testing, e.g. pre-deployment checks), and Impact (measuring the business results of optimization work). On top of that, Lumar sells add-on metrics modules for GEO/AI search visibility, technical SEO, site speed, and web accessibility, plus a free AI-visibility scan called Lumar GEO Studio and bespoke SEO professional services. This a-la-carte structure means a buyer only pays for the modules they need, but it also means there’s no way to get a price estimate without going through sales.
Lumar is the right scale for organizations managing dozens of large domains that need continuous monitoring and cross-team collaboration, not a one-off desktop crawl.
Pricing Comparison
Screaming Frog
Sitebulb
Lumar
Free tier
Yes — up to 500 URLs
14-day free trial (Pro-equivalent), no card required
Free GEO/AI-visibility scan only; no free crawl tier
Published entry price
£199/year (single licence)
Cloud from £95/month; Desktop price not shown
None — quote only
Crawl limit (entry paid tier)
Unlimited (memory-bound)
Lite: 10,000 URLs; Pro: 500,000 (up to 2M)
Not published; scales to enterprise volumes
Deployment
Local desktop app
Desktop app or cloud
Cloud SaaS
Pros and Cons
Screaming Frog
Pro: Clear, published, low annual price with volume discounts
Pro: Extremely deep and flexible crawling/extraction features
Con: Raw data output requires real SEO expertise to interpret
Con: Desktop-only; no built-in hosted scheduling or collaboration
Sitebulb
Pro: “Hints” explain issues and fixes, not just raw data
Pro: Cloud option adds scheduling and hosted collaboration
Con: Desktop plan prices aren’t published, only feature tiers
Con: Cloud pricing can scale into five figures per year for larger teams
Pro: Adds specialized modules (GEO/AI visibility, accessibility, site speed)
Con: Absolutely no published pricing — can’t even estimate cost without a sales call
Con: Overkill and likely overpriced for a single-site audit
Who It’s a Good Fit For
Choose Screaming Frog if you’re an individual consultant or small agency that wants maximum crawling power at the lowest, clearest price. Choose Sitebulb if you need to turn crawl data into client-ready, prioritized recommendations without writing the analysis yourself. Choose Lumar if you’re running technical SEO across many large enterprise domains and need continuous monitoring, QA automation, and cross-team workflows — and have budget to match.
Who Should Look Elsewhere
If what you actually need is keyword research, backlink analysis, or rank tracking rather than crawl-level technical diagnostics, none of these three tools are the right starting point — look at an all-in-one SEO suite instead. And if your site is under a few hundred pages, Screaming Frog’s free tier alone may cover everything you need.
Bottom Line
These three tools solve the same core problem — crawling a site and surfacing technical issues — at three very different scales and price points. Screaming Frog is the affordable, powerful default. Sitebulb trades some of that rawness for guided, presentable analysis. Lumar trades a published price entirely for enterprise-grade modularity and scale. Match the tool to your site size and team, not just the feature list.
FAQ
Is Screaming Frog’s free version actually usable? Yes, for smaller sites. The free version includes the full feature set, just capped at crawling 500 URLs per crawl.
Does Sitebulb publish desktop pricing? Not on its public pricing page — Lite and Pro show feature and user-count tiers, and an extra-user rate for Pro (from £7/month), but no flat headline price. Only Cloud has a stated starting price (£95/month).
Why doesn’t Lumar publish any pricing? Lumar sells a modular platform (separate apps and metrics add-ons) aimed at enterprise customers with varying needs, so it prices each deal individually rather than offering a fixed rate card.
Can I run any of these on a schedule automatically? Screaming Frog’s desktop app supports scheduling locally. Sitebulb’s Pro and Cloud tiers support scheduled audits, with Cloud adding hosted recurring crawls. Lumar’s Monitor app is built specifically for ongoing, scheduled tracking across domains.
AWS has published Trainium and Inferentia chip roadmaps for years, but Project Rainier is a different kind of announcement: a specific, named compute cluster, built for a specific customer, now confirmed operational. According to AWS’s own account, Project Rainier is an AI training supercluster built on AWS’s second-generation Trainium chips, developed in partnership with Anthropic to train and run future versions of its Claude models. It’s one of the clearest public windows into what a hyperscaler’s AI infrastructure actually looks like at the scale frontier labs now require.
At a Glance
Attribute
Detail (per AWS’s public statements)
What it is
An EC2 UltraCluster of Trainium2 UltraServers — an AI training supercompute cluster
Chip generation
AWS Trainium2, AWS’s custom-designed AI training/inference chip
Scale
Nearly half a million Trainium2 chips; AWS says this Trainium2 buildout is 70% larger than any prior AI computing platform in AWS’s history
Server architecture
UltraServers combine four Trainium2 servers of 16 chips each (64 chips per UltraServer); tens of thousands of UltraServers form the UltraCluster
Networking
NeuronLink for high-bandwidth connections within an UltraServer; Elastic Fabric Adapter (EFA) connecting UltraServers within and across data centers
Partner
Built with and for Anthropic, to train and deploy future Claude models
Status
Operational, confirmed by AWS less than a year after the project was announced
Short Verdict
Project Rainier is AWS’s clearest public demonstration that Trainium has moved from “an alternative to Nvidia GPUs worth considering” to “the infrastructure backbone of one of the world’s leading AI labs’ training strategy.” AWS states the cluster gives Anthropic more than five times the compute power used to train its previous models, and that Anthropic expects to run on more than a million Trainium2 chips across training and inference by the end of the year. Those are AWS’s own disclosed figures; AWS has not published exact power, cooling, or FLOPS specifications for the cluster as a whole, so claims beyond what AWS has stated should be treated as unconfirmed.
What Project Rainier Actually Is
Project Rainier is AWS’s name for a large-scale AI training compute cluster built around Trainium2, architected as what AWS calls an EC2 UltraCluster of Trainium2 UltraServers. The naming reflects two layers of aggregation: individual Trainium2 chips are grouped into servers, servers are grouped into UltraServers for tighter interconnect, and UltraServers are in turn networked together into the UltraCluster that spans multiple U.S. data centers. AWS has described the cluster as now operational, reaching that milestone less than a year after the project was first announced — a notably fast timeline for infrastructure at this scale. AWS named the project after Mount Rainier, the 14,410-foot stratovolcano visible from Seattle, continuing AWS’s pattern of naming major infrastructure projects after landmarks.
The Hardware: Trainium2 and UltraServers
Trainium2 is AWS’s second-generation custom silicon purpose-built for training large AI models, developed through AWS’s Annapurna Labs silicon team as part of the same custom-chip strategy that produced Graviton (general-purpose Arm CPUs) and Inferentia (inference-optimized chips). According to AWS, each UltraServer in Project Rainier combines four Trainium2 servers, with 16 chips per server, for 64 chips per UltraServer. Tens of thousands of these UltraServers are then networked together to form the full UltraCluster. Within an UltraServer, AWS’s NeuronLink interconnect provides the high-bandwidth, low-latency connections chips need to function as a coordinated unit for distributed training. Across UltraServers — both within a single data center and between the multiple data centers that make up the cluster — AWS uses its Elastic Fabric Adapter (EFA) networking technology, the same high-performance networking layer AWS uses elsewhere in its HPC and machine learning infrastructure, to keep the whole cluster synchronized during large distributed training runs.
The Anthropic Partnership
AWS has stated that Project Rainier was built with Anthropic and that Anthropic is using it to train and deploy its Claude models. AWS has publicly said the cluster provides Anthropic with more than five times the compute power the company used to train its previous generation of models, and that Anthropic’s use of Trainium2 is expected to scale to more than one million chips — across both training and inference — by the end of the year. AWS has not, in the material reviewed for this piece, published exact figures for the cluster’s total power draw, number of individual data center sites, or aggregate FLOPS, so those specific figures should be treated as not publicly disclosed rather than assumed. One concrete site AWS has named is a set of data centers in St. Joseph County, Indiana, which AWS notes require no cooling water from October through March — a detail about that specific location’s cooling design, not necessarily representative of every site in the broader cluster.
Why a Hyperscaler Builds Its Own Chips for This
Trainium exists because AWS, like Google (TPUs) and Microsoft (Maia), has concluded that relying entirely on third-party GPUs for AI infrastructure at this scale carries both cost and supply risk. Designing its own training silicon lets AWS optimize the chip, the server, the interconnect, and the data center power and cooling design as one integrated system rather than working around a GPU vendor’s reference architecture. Project Rainier is the proof point for that strategy: it shows AWS and a major AI lab committing production-scale frontier model training to custom silicon rather than exclusively to merchant GPUs, at a scale large enough that AWS itself describes it as the largest Trainium buildout in the company’s history.
Trade-offs
Pros: Purpose-built silicon and interconnect (NeuronLink, EFA) tuned specifically for large-scale distributed training; reduces AWS’s and Anthropic’s dependence on third-party GPU supply; AWS controls the full stack from chip to data center design.
Trade-offs: Trainium’s software ecosystem (via the AWS Neuron SDK) is less universally adopted than Nvidia’s CUDA stack, meaning workloads need to be specifically optimized for Trainium rather than running unmodified from a CUDA-first codebase; AWS has not disclosed the cluster’s total power/cooling footprint or cost, limiting independent comparison against GPU-based clusters of similar scale.
Who This Matters For
This matters most to infrastructure and AI strategy teams tracking where frontier-scale model training capacity is actually being built, and to anyone evaluating AWS Trainium as a training platform for their own large models. It’s also a relevant data point for understanding Anthropic’s compute strategy specifically, since Project Rainier is described by AWS as central to how Anthropic trains and serves Claude going forward.
Bottom Line
Project Rainier is AWS’s largest disclosed Trainium deployment to date — a multi-data-center UltraCluster built on Trainium2 chips, developed with Anthropic to train and run Claude models, and now confirmed operational. The publicly confirmed facts are the chip generation, the roughly 500,000-chip scale, the UltraServer/UltraCluster architecture, the NeuronLink/EFA networking approach, and AWS’s “more than 5x compute” claim relative to Anthropic’s prior training runs. Total power, full data center count, and aggregate FLOPS have not been published by AWS, and should not be assumed or estimated beyond what AWS has stated.
FAQ
What chip does Project Rainier use? AWS Trainium2, AWS’s second-generation custom AI training chip.
How many chips are in the cluster? AWS has stated the cluster involves nearly half a million Trainium2 chips, calling it 70% larger than any other AI computing platform in AWS’s history. AWS has also said Anthropic’s use of Trainium2 overall (training plus inference) is expected to exceed one million chips by the end of the year.
Who is Project Rainier for? AWS states it was built with and for Anthropic, to train and deploy future versions of its Claude AI models.
Is Project Rainier one data center or several? Several. AWS describes the UltraCluster as spread across multiple data centers in the United States, with one named example being data center facilities in St. Joseph County, Indiana. AWS has not published the total number of sites involved.
Is Project Rainier bigger than AWS’s other AI infrastructure? Yes, per AWS’s own statement: the company describes this Trainium2 buildout as 70% larger than any other AI computing platform previously built in AWS’s history.
Habit trackers are one of the few app categories where the “best” choice depends entirely on what motivates you. Some people need a strict streak counter that makes missing a day feel like a loss. Others need a game layered on top of their to-do list to make the whole thing fun. And some just want a clean, no-frills log of what they did and didn’t do. Streaks, Habitica, and Way of Life represent three very different answers to that problem, and all three have been around long enough to have genuinely mature, stable apps rather than trend-chasing new entrants.
This comparison looks at what each app actually charges, how it’s built, and who it suits — based on each developer’s own App Store listing and official site, not on marketing copy alone.
At a Glance
App
Platforms
Pricing Model
Core Style
Best For
Streaks
iOS, iPadOS, macOS, Apple Watch
$5.99 one-time purchase, no IAP
Minimalist streak counter (up to 24 tasks)
Apple users who want a simple, no-subscription tracker
Habitica
iOS, Android, web (habitica.com)
Free core app; optional auto-renewing subscriptions from $4.99/mo and one-time Gem purchases from $0.99
Gamified RPG-style habit and task tracker
People who respond to game mechanics, rewards, and accountability parties
Way of Life
iOS, Android
Free with unlimited habits capped; Premium in-app purchase unlocks unlimited habits (tiers at $4.99 / $14.99 / $29.99)
Simple yes/no/skip daily chain log with charts
Users who want a lightweight visual log without gamification
Short Verdict
If you want the simplest possible experience and never want to see a subscription prompt, Streaks is the easiest recommendation — pay once, own it, done. If you’re motivated by game mechanics, social accountability, and don’t mind a steeper learning curve, Habitica gives you the most depth for free, with optional paid perks. If you just want a clean visual chain of habits without any RPG layer and you’re on Android as well as iOS, Way of Life is the straightforward middle ground, though its paid tiers are a little opaque on the App Store listing.
Streaks: The One-Time-Purchase Minimalist
Streaks is built entirely around a simple premise: pick up to 24 tasks, do them, and don’t break the chain. There’s no social layer, no points economy, and critically, no subscription. According to its official App Store listing, Streaks is a $5.99 one-time purchase with no in-app purchases listed at all — you pay once and the app is fully unlocked.
It’s deeply integrated with Apple’s ecosystem: it pulls data from the Health app automatically for things like steps or workouts, syncs via iCloud, and has a dedicated Apple Watch app. That tight integration is also its biggest limitation — Streaks is iOS/iPadOS/macOS only, so it’s not an option if you’re on Android or want to log habits from a browser.
Habitica: Turning Your Life Into an RPG
Habitica treats your habits, dailies, and to-dos as quests in a role-playing game. Complete tasks and you level up a customizable avatar, earn gold, and hatch pets; miss your dailies and your avatar’s health takes damage. It supports “Party” groups and guilds, so friends or coworkers can hold each other accountable and take on boss battles together.
Habitica has long been associated with a donation-supported, free-to-use model, and its App Store listing confirms the core app “can be fully enjoyed for free.” That said, Habitica now also sells formal auto-renewing subscriptions directly through the app, rather than relying purely on donations:
1 month: $4.99
3 months: $14.99
6 months: $29.99
12 months: $47.99 (listed as a 20% discount versus monthly)
There are also one-time Gem purchases (a premium in-game currency) ranging from $0.99 for 4 Gems up to $19.99 for 84 Gems, used for cosmetic items, pets, and other extras. None of this is required to use the habit- and task-tracking functionality itself — subscriptions mainly add cosmetic rewards and a monthly item bundle.
Way of Life: A Simple Visual Chain
Way of Life strips out the gamification entirely. Each day you mark a habit as a yes, no, or skip, and the app builds a color-coded chain and charts showing your consistency over time. It’s built for people who want something closer to a quantified log than a game.
The app is free to download, with its App Store listing showing it as “Free · In-App Purchases.” The paid tier is called Premium, and per the listing it “simply unlocks unlimited habits” — the free version caps how many habits you can track at once. The App Store lists Premium at three price points ($4.99, $14.99, and $29.99), but the listing itself doesn’t clearly state which price maps to which billing period (e.g., monthly vs. yearly vs. lifetime), so check the in-app purchase screen before buying if the exact term matters to you. Notably, the developer has moved some previously paid features to free for everyone over time — all themes and backup/restore are now included at no cost, per the app’s own version history.
Pricing & Platform Comparison
App
Free Tier
Paid Tier
Android?
Web App?
Streaks
None (paid upfront)
$5.99 once, full app unlocked
No
No
Habitica
Full habit/task/RPG functionality
$4.99–$47.99 subscriptions and $0.99–$19.99 Gem packs, mostly cosmetic
Pros: One-time $5.99 purchase with no subscription or ads; deep Health app and Apple Watch integration; very fast, minimal UI.
Cons: Apple-only; capped at 24 tracked tasks; no social or accountability features.
Habitica
Pros: Fully usable for free; strong social/accountability tools (parties, guilds, challenges); available on iOS, Android, and the web.
Cons: RPG framing and UI can feel cluttered for people who just want a plain tracker; subscription and Gem purchases add complexity to the pricing.
Way of Life
Pros: Clean, chain-based visual log; available on both iOS and Android; many features (themes, backup) have been made free over time.
Cons: Free tier limits the number of habits; the App Store listing doesn’t clearly explain which Premium price corresponds to which billing term.
Who It’s a Good Fit For
Choose Streaks if you’re fully in the Apple ecosystem and want a simple, private, subscription-free tracker tied to Health and Apple Watch data.
Choose Habitica if you want gamified motivation, group accountability, or you track both habits and to-dos together and like the idea of leveling up a character.
Choose Way of Life if you want something in between — visual, simple, cross-platform (iOS and Android) — without RPG mechanics.
Who Should Look Elsewhere
If you need team or workplace habit tracking with reporting for a manager or coach, none of these three are built for that — they’re personal-use apps. And if you specifically want a free tracker with zero in-app purchases of any kind, Habitica and Way of Life both have paid upsells (even if optional), while Streaks requires its $5.99 payment upfront with nothing further to buy.
Bottom Line
There’s no universal winner here because these apps are built on different psychological approaches to habit-forming. Streaks is the pick for simplicity and a one-time cost. Habitica is the pick for anyone who wants gamification and community pressure to stick with their goals, at no required cost. Way of Life sits in between as a straightforward, cross-platform daily log. Try the free tiers of Habitica and Way of Life before paying for anything, and only buy Streaks if you’re committed to the Apple ecosystem long-term.
FAQ
Is Habitica really free?
Yes. Habitica’s own App Store listing states the app “can be fully enjoyed for free.” Optional subscriptions ($4.99–$47.99) and Gem purchases ($0.99–$19.99) add cosmetic items and monthly bonuses but aren’t required for core habit and task tracking.
Does Streaks have a subscription?
No. Streaks’ App Store listing shows a single $5.99 one-time purchase with no in-app purchases offered.
Is Way of Life available on Android?
Yes, per the developer’s own site, Way of Life is listed for both iOS (Apple App Store) and Android (Google Play).
Which app works without an internet connection?
Streaks and Way of Life are primarily local, on-device apps with optional cloud sync/backup, so they’re usable offline. Habitica is more cloud-dependent since it syncs your character, party, and quest data to its servers.
Can I track habits with friends or a group?
Habitica is the strongest option here, with built-in Parties, Guilds, and Challenges for group accountability. Streaks and Way of Life are single-user apps without built-in social features.
Ask an analytics database “how many users are in the US, on the free plan, who logged in this week” and it needs to intersect three (or thirty) large sets of row IDs fast. A naive approach — scanning every row and checking each predicate — doesn’t scale. The classic fix is a bitmap index: one bit per row per value, so filtering becomes a bitwise AND. The modern twist is Roaring Bitmaps, a compressed bitmap format that keeps the speed of a plain bitmap while using a fraction of the memory, and which now sits inside most of the analytics engines you’ve heard of — ClickHouse, Apache Druid, Lucene/Elasticsearch, Apache Spark, Pinot, and more.
AT A GLANCE
Aspect
Detail
What it is
Compressed bitset data structure for representing sets of integers (e.g. row/document IDs)
License / project
Apache License 2.0, open-source, reference implementations in Java, C/C++, Go, Rust, Python, JS, C#, and more — roaringbitmap.org
Core idea
Splits 32-bit integers into 65,536-value chunks; each chunk auto-picks the smallest of three container types (array, bitmap, or run)
Why it matters
Enables fast AND/OR/XOR/ANDNOT set operations directly on compressed data — no need to decompress first
Who uses it
Apache Lucene, Elasticsearch/OpenSearch, Apache Druid, ClickHouse, Apache Spark, Apache Pinot, Hive, Trino, Flink, Iceberg, Delta Lake, Redis, and products from Google, Netflix, Datadog
A bitmap index is a simple, powerful idea — one bit per row, per distinct value — that makes filtering and counting over large columns extremely cheap, as long as the uncompressed bitmaps don’t blow up your memory footprint on sparse or high-cardinality data. Roaring Bitmaps solve exactly that problem: by adapting storage per 65,536-value chunk instead of using one encoding for an entire column, Roaring keeps the random-access speed of an uncompressed bitmap while shrinking storage the way older run-length formats (WAH, EWAH, Concise) did — without their decompression overhead. That combination is why it’s become the de facto standard bitmap format across modern analytics and search engines.
What a Bitmap Index Actually Is
A bitmap index maps each distinct value in a column to a bitmap (a bit vector) the length of the table: bit i is 1 if row i has that value, 0 otherwise. Filtering on “country = US” becomes “look up the bitmap for US.” Combining predicates — “country = US AND plan = free” — becomes a bitwise AND of two bitmaps, which CPUs do extremely fast, word at a time. Counting matching rows is a population count (popcount) over the result. This is why bitmap indexes have traditionally been favored for low-to-medium cardinality columns (status flags, categories, countries, boolean tags) in data warehouses and OLAP systems, where B-tree indexes don’t help much and the set-intersection pattern dominates the query workload.
The catch is storage. A raw (uncompressed) bitmap for a billion-row table costs 125MB per distinct value, even if that value only matches a handful of rows. Classic compression schemes like WAH (Word-Aligned Hybrid), EWAH, and Concise solve the size problem using run-length encoding, but they typically have to be decompressed, at least partially, before you can perform bitwise operations or random access — which costs CPU time that eats into the speed advantage bitmaps are supposed to provide.
How Roaring Bitmaps Work
Roaring Bitmaps, introduced by Chambi, Lemire, Kaser, and Godin, take a different approach: instead of one compression strategy applied uniformly, a Roaring bitmap splits the 32-bit integer space into chunks of 65,536 consecutive values, and each chunk independently picks whichever of three container types is smallest:
Array container — used when a chunk is sparse (few set bits); stores the actual set values as a sorted array of 16-bit integers.
Bitmap container — used when a chunk is dense; stores a plain 8KB bitmap, giving O(1) access.
Run container — used when a chunk has long runs of consecutive set bits; stores (start, length) run pairs, similar in spirit to run-length encoding.
Because each container picks the most efficient representation for its own local data distribution, Roaring adapts automatically to sparse, dense, and clustered data within the same bitmap — no manual tuning required. Critically, AND, OR, XOR, and ANDNOT operations are implemented to work directly on whichever container types are involved, without first expanding everything into plain bitmaps. According to the project’s own benchmarks, this makes Roaring “often hundreds of times faster” than older formats like WAH, EWAH, and Concise, while also giving constant-time random access to individual bits — something compressed run-length formats generally can’t offer. A published serialization format also means a Roaring bitmap written by one language’s implementation (say, Java) can be read directly by another (say, Go or C), which matters when a search engine and an analytics pipeline need to interoperate.
Where It Shows Up in Real Databases
Apache Lucene (and therefore Elasticsearch/OpenSearch) uses Roaring-style bitsets for its doc ID sets and cached filters — small sets use a sparse array representation, larger/denser sets switch to a bitmap, mirroring Roaring’s core idea. Elastic has also documented using Roaring for its own filter caching and aggregations. Apache Druid, a column-oriented analytics database built for sub-second OLAP queries, uses compressed bitmap indexes — Roaring or a Druid-specific “Concise” format — as the default inverted index for its string-encoded dictionary columns; Druid’s own segment design docs describe choosing a bitmap index implementation per column to balance compression against AND/OR performance across segments. ClickHouse ships a dedicated family of bitmap functions (bitmapBuild, bitmapAnd, bitmapOr, bitmapXor, groupBitmap, and more) backed by the Roaring format, letting you build and intersect bitmaps directly in SQL for use cases like retention analysis and audience segmentation. The same format backs set operations inside Apache Spark, Apache Pinot, and several data-lake table formats (Iceberg, Delta Lake).
Comparison: Bitmap Index Approaches
Format
Compression strategy
Random access
Operate without decompressing?
Plain/uncompressed bitmap
None
O(1), fastest
Yes, but memory-expensive on sparse data
WAH / EWAH / Concise
Run-length encoding of words
Slow (sequential scan)
Partial — often needs decoding runs first
Roaring Bitmaps
Per-chunk adaptive (array/bitmap/run container)
O(1) within containers
Yes — native operations per container type
Pros
Combines the compactness of compressed formats with near-uncompressed-bitmap speed.
Adapts automatically to sparse, dense, and clustered data without manual index tuning.
Cross-language, standardized serialization — portable between systems and libraries.
Battle-tested: embedded in Lucene, Druid, ClickHouse, Spark, Pinot, and others for years.
Cons / Trade-offs
Bitmap indexes in general still work best on low-to-medium cardinality columns; very high-cardinality columns (e.g. unique IDs) gain little and can even bloat storage.
Roaring’s container-switching logic adds implementation complexity compared with a plain bitmap — not something you’d hand-roll for a one-off script.
Write-heavy, highly randomized updates to individual bits can still be costlier than in a plain uncompressed bitmap, depending on container churn.
It’s a building block, not a query planner — the database still has to decide when a bitmap index is the right strategy versus a B-tree or a full scan.
Who It’s a Good Fit For
Engineers building or tuning OLAP/analytics systems, search indexes, or any workload dominated by set intersections/unions over large ID spaces — audience segmentation, retention cohorts, log/event filtering, faceted search — benefit most. If you’re evaluating or operating ClickHouse, Druid, Elasticsearch, or similar systems, understanding that a Roaring-backed bitmap index sits underneath your filter and aggregation queries helps explain why certain predicates (low-cardinality equality filters) are fast and others (range scans on high-cardinality numeric columns) are not.
Bottom Line
Bitmap indexes turn filtering into bitwise arithmetic, and Roaring Bitmaps make that arithmetic cheap at scale by compressing adaptively instead of uniformly. You rarely interact with Roaring directly unless you’re using ClickHouse’s bitmap functions or writing a custom data structure, but it’s quietly doing the heavy lifting behind fast filters and aggregations in most of the serious analytics and search engines in production today.
FAQ
Is a Roaring Bitmap the same thing as a bitmap index? No. A bitmap index is the database concept (one bit per row per value). Roaring is a compressed data structure commonly used to store and operate on those bitmaps efficiently.
Why not just use an uncompressed bitmap? Uncompressed bitmaps are fast but can waste enormous amounts of memory for sparse or high-cardinality columns — a billion-row table needs 125MB per distinct value stored as a plain bitmap, regardless of how few rows actually match.
Which databases use Roaring Bitmaps today? Documented users include Apache Lucene (and Elasticsearch/OpenSearch), Apache Druid, ClickHouse, Apache Spark, Apache Pinot, Hive, Trino, Flink, and several data lake table formats like Iceberg and Delta Lake, per the RoaringBitmap project’s own list.
Do I need to implement Roaring myself to benefit from it? No. If you use ClickHouse’s bitmap functions, or rely on Druid’s or Elasticsearch’s default indexing, you’re already using Roaring (or a closely related format) under the hood.
Does Roaring help with high-cardinality columns too? Less so. Its advantage is adapting per-chunk between sparse and dense regions; a column where nearly every value is unique doesn’t compress well with any bitmap approach, and a different index structure (hash or B-tree) is usually a better fit.
Legal AI has moved well past “summarize this PDF.” Harvey, Spellbook, and LinkSquares each sell AI systems that draft, review, redline, and research legal documents — but all three have made a deliberate choice to keep pricing off their public websites entirely. That’s worth saying plainly up front, because it shapes how you should shop: none of these can be compared on a price-per-seat basis without first booking a call. Here’s what we could verify about what each product actually does, and what we could not verify about what it costs.
AT A GLANCE
Tool
Core Focus
Public Pricing?
Best For
Harvey AI
AI research, drafting, and agentic workflows for law firms and legal departments
No — demo/contact sales only
Large law firms and enterprise legal departments (3,500+ organizations, 80+ AmLaw 100 firms per Harvey)
Spellbook
Contract review, drafting, and Q&A inside Microsoft Word
No — custom quote based on team size, after a demo; 7-day free trial
In-house teams and law firms doing high-volume contract drafting/review in Word
LinkSquares
End-to-end contract lifecycle management with embedded AI (LinkAI)
No — custom quote based on contract volume, users, and modules
Mid-size to enterprise legal/ops teams managing a full contract repository
Short Verdict
All three vendors are enterprise/custom-quote only — there is no self-serve monthly price published for any of them, and this article will not invent one. What differs is scope and workflow. Harvey is the broadest, positioning itself as an agentic AI platform for research, drafting, and multi-step legal tasks across both law firms and in-house teams. Spellbook is the most narrowly focused of the three: it lives inside Microsoft Word as an add-in for reviewing, drafting, and asking questions about contracts, plus a multi-document agent called Associate. LinkSquares is closer to a full contract lifecycle management (CLM) platform, with AI (LinkAI) embedded across repository search, risk-flagging, drafting, and redlining rather than being the whole product.
Harvey AI: Enterprise-Only, No Self-Serve Tier
Harvey’s own homepage does not list any pricing, plans, or costs anywhere — the only calls to action are “Request a Demo” and region-specific login links. Per the site, Harvey serves over 3,500 legal organizations, including more than 80 AmLaw 100 firms, across both law firms and corporate legal departments. Its named products include Contract Intelligence (AI contract review and negotiation), Knowledge (legal, regulatory, and tax research), Agents (multi-step task coordination), Vault (document storage and analysis), and Horizon Scanning (regulatory tracking). Given the complete absence of public pricing and the explicit enterprise/AmLaw positioning, prospective buyers should assume Harvey is priced for large legal departments and firms rather than solo practitioners or small firms, and budget for a sales cycle rather than a credit-card signup.
Spellbook: A Word Add-In With a 7-Day Trial, No Listed Price
Spellbook (correctly at spellbook.com) also keeps pricing off its site, but it’s more transparent about the shape of its offer. Per its own pricing page, Spellbook sells two audience-based packages — one for Law Firms, one for In-House Teams — both built around the same core “Spellbook Suite” (a Word add-in plus a multi-document AI agent called Associate) with AI features named Review, Draft, Ask, Benchmarks, and Playbooks. Pricing depends on team size and requires booking a demo; the page explicitly states there’s no fixed per-seat number published. It does offer a 7-day free trial for lawyers and legal teams (with extended trials possible for larger organizations) and free access for academic institutions through partnerships — concrete, verifiable details that Harvey’s page doesn’t offer at all.
LinkSquares: CLM Platform With AI Baked In, Priced by Volume
LinkSquares’ pricing page is explicit that there is no published price list: cost depends on contract volume, number of users, which modules you select, and the level of implementation/onboarding support needed. The page does commit to “no hidden fees,” stating implementation and onboarding costs are disclosed upfront as part of the quote. Its AI, branded LinkAI, is described as built into the core of the platform rather than a bolt-on, powering Contract Intelligence (surfacing key terms, obligations, and risk) and an “AI Legal Assistant” for drafting, redlining, and research. Unlike Harvey and Spellbook, LinkSquares is positioned less as a point-solution AI tool and more as a full contract repository and workflow platform where AI is one layer among several (it also sells separate Automation & Workflows and Playbooks & Libraries modules).
Feature Comparison
Dimension
Harvey AI
Spellbook
LinkSquares
Delivery format
Standalone platform/agents
Microsoft Word add-in + agent (Associate)
Full CLM platform with embedded AI (LinkAI)
Contract review/redlining
Yes (Contract Intelligence)
Yes (Review, Draft)
Yes (Contract Intelligence, AI Legal Assistant)
Legal research
Yes (Knowledge)
Yes (Ask, Benchmarks)
Yes (AI Legal Assistant — research)
Free trial
Not offered publicly
7 days (extended trials possible)
Not offered publicly
Pricing published online
No
No
No
Primary buyer
Law firms + enterprise legal depts
Law firms + in-house legal teams
Mid-size to enterprise legal/ops teams
Pros and Cons
Harvey AI
Pros: Broadest product suite (research, drafting, agents, regulatory tracking); large verified enterprise/AmLaw customer base
Cons: Zero public pricing information of any kind; no self-serve trial mentioned on its site
Spellbook
Pros: Lives inside the Word workflow lawyers already use; offers an actual free trial and academic access
Cons: Still fully custom-quoted; narrower scope than LinkSquares if you need full contract lifecycle/repository management
LinkSquares
Pros: Full CLM platform, not just a review tool; explicit no-hidden-fees commitment in its FAQ
Cons: No trial mentioned; pricing scales with contract volume, which is hard to estimate without engaging sales
Who It’s a Good Fit For
Harvey suits large firms and enterprise legal departments that need a broad, agentic platform and have the budget and procurement process for an enterprise AI deployment. Spellbook suits individual lawyers and small-to-mid legal teams who want AI contract help without leaving Word and want to try before committing. LinkSquares suits organizations that need a full contract repository and lifecycle workflow, with AI as part of a bigger operational platform rather than the whole point.
Who Should Look Elsewhere
Solo practitioners or very small firms wanting a transparent, low monthly price should be cautious with all three — none publish self-serve pricing, and all three appear built primarily for firms and legal departments with dedicated procurement budgets. If your workflow doesn’t already center on Microsoft Word, Spellbook’s add-in-first model may feel limiting compared to Harvey’s or LinkSquares’ standalone platforms.
Bottom Line
This is a category where “contact sales” is the pricing model, not an exception to it. Harvey is the broadest and most enterprise-skewed; Spellbook is the most accessible with a real free trial, built around Word; LinkSquares is the most operationally complete if you need full contract lifecycle management with AI built in. Budget time for a sales conversation and a demo with all three before you can get a real number — and ask each vendor directly how they price per-seat versus per-document-volume, since none of that is public.
FAQ
Is Harvey AI’s pricing public anywhere? No. Harvey’s website offers no pricing, plans, or cost information — only a demo request and region-specific login links.
Is Spellbook’s correct domain spellbook.legal or spellbook.com? Spellbook.com. Its pricing page confirms the company name and product as “Spellbook” with pricing pages hosted at spellbook.com/pricing and spellbook.com/learn.
Does Spellbook offer a free trial? Yes — Spellbook’s pricing page states a 7-day free trial for lawyers and legal teams, with extended trials possible for larger organizations.
How is LinkSquares priced? LinkSquares does not publish fixed pricing. Per its own pricing page, cost depends on contract volume, number of users, selected modules, and implementation/onboarding support, determined through a custom quote.
If you sell on Google Shopping, you already know the headache: your product data lives in one format in your store, but Google wants it in another, with its own quirks, required attributes, and constant feed errors. Product feed management tools exist to bridge that gap, cleaning, mapping, and optimizing your catalog before it ever reaches Google (and often Meta, Amazon, and dozens of other channels too). We compared three of the most established players — DataFeedWatch, Feedonomics, and GoDataFeed — on pricing, features, and who each one actually fits.
At a Glance
Tool
Starting Price
Free Trial
Best For
DataFeedWatch
$64/mo (Shop plan, 1,000 SKUs, 3 feeds)
15 days
Growing merchants who want hands-on, self-serve control
Feedonomics
Custom quote (no published tiers)
Free feed audit
Large catalogs that want a managed, full-service feed team
GoDataFeed
$99/mo (Plus plan, 1,000 SKUs)
14 days
Mid-size sellers who want a feed builder plus PPC/marketplace add-ons
Short Verdict
DataFeedWatch is the most transparent and flexible option for merchants who want to see exact pricing and tinker with their own feed rules. Feedonomics leans fully managed — strong if you’d rather hand the whole feed operation to a team of specialists and don’t mind skipping a public price list. GoDataFeed sits in between: a self-serve feed builder with clear per-channel add-on costs, best for sellers who want to add marketplaces (Amazon, Walmart) alongside Google Shopping without jumping to an agency-tier plan.
DataFeedWatch: Transparent Tiers, Self-Serve Control
DataFeedWatch publishes its pricing outright, which is rare in this category. The Shop plan runs $64/month for 1,000 SKUs, 3 feeds, and 1 connected shop, with one sync per day and a single onboarding session. Merchant steps up to $84/month for 5,000 SKUs, 10 feeds, and 2 shops with two daily syncs and chat support added. Agency, marked as the most popular tier, is $239/month for 30,000 SKUs, 150 feeds, and unlimited shops, and it adds a dedicated success agent, master rules across feeds, an MCC account, and 24/7 monitoring. Enterprise is a custom quote built around catalogs of 100,000+ SKUs and unlimited feeds.
Annual billing saves 17% across all tiers. Beyond the included limits, DataFeedWatch charges per-1,000-SKU overage fees that shrink as you move up tiers ($5 on Shop down to $2 on Enterprise), plus optional add-ons for extra shops, extra feeds, a $450/month coaching package, and a fully managed service starting at $750/month. Every plan includes a 15-day free trial with full feature access.
Feedonomics: Fully Managed, Quote-Based
Feedonomics takes the opposite approach to pricing: there’s no published plan or price on its site. Cost depends on SKU count, how many channels you need, and the level of service you want, and you get a quote only after talking to its team. Feedonomics is explicit that it does not take a percentage of your ad or sales revenue, which separates its model from some agency arrangements. In exchange for the opacity, Feedonomics is built around a managed-service model — its team handles feed setup, troubleshooting, and channel-specific optimization rather than leaving you to build rules yourself. It also offers a free feed audit as a low-commitment way to see what a paid engagement would catch.
This makes Feedonomics harder to compare dollar-for-dollar against DataFeedWatch or GoDataFeed, but it’s the natural fit if your catalog is large and complex enough that you’d rather pay for expertise than configure syncs and attribute mappings yourself.
GoDataFeed: Builder Plus Per-Channel Add-Ons
GoDataFeed uses a plan-builder on its pricing page that recommends a tier based on your SKU count and which PPC or marketplace channels you select — marketplace channels (like Amazon or Walmart) require at least the Pro plan. The only tier priced outright on the page is Plus, shown by default at $99/month for a 1,000-SKU base allotment. Beyond that base, extra SKUs cost $5 per 1,000 up to 50,000 (with lower tiered rates above that), additional PPC channels are $29/month each beyond your plan’s allotment, and additional marketplace channels run $99/month each beyond allotment.
Every GoDataFeed plan includes unlimited optimization rules, AI-generated titles and descriptions, error monitoring, and free expert onboarding. Done-for-you services — PPC feed setup, marketplace feed setup, and full-service management — are available but not priced publicly. GoDataFeed offers a 14-day free trial and lets you cancel anytime.
Pricing & Model Comparison
Factor
DataFeedWatch
Feedonomics
GoDataFeed
Entry price
$64/mo (1,000 SKUs)
Custom quote
$99/mo (1,000 SKUs)
Pricing transparency
Fully published
Not published
Builder shows add-on costs; base tier pricing partly disclosed
Service model
Self-serve with optional coaching/managed add-ons
Fully managed by default
Self-serve builder with optional done-for-you add-ons
Cons: Overage fees on SKUs, feeds, and shops can add up fast on the entry tier; coaching and managed service cost extra
Feedonomics
Pros: No revenue percentage taken; fully managed feed operations; free feed audit to test the waters
Cons: No public pricing, so budgeting requires a sales call; less hands-on control for teams that want to self-serve
GoDataFeed
Pros: Unlimited optimization rules and AI-assisted listings on every plan; clear per-channel add-on pricing; free expert onboarding and 14-day trial
Cons: Marketplace channels gated behind Pro plan or higher; full plan comparison isn’t laid out as plainly as DataFeedWatch’s
Who It’s a Good Fit For
Choose DataFeedWatch if you want full visibility into costs and are comfortable building your own feed rules and syncs.
Choose Feedonomics if your catalog is large, your team is stretched thin, and you’d rather pay for a managed service than configure feeds yourselves.
Choose GoDataFeed if you’re expanding from Google Shopping into marketplaces like Amazon or Walmart and want predictable per-channel add-on pricing.
Who Should Look Elsewhere
Very small catalogs (a few dozen SKUs on one channel) may find any of these three more tool than they need — a native Google Merchant Center feed or a simpler plugin might suffice until you scale. Budget-conscious sellers who want to see an exact number before committing should be cautious with Feedonomics until they’ve gone through the quote process.
Bottom Line
All three tools solve the same core problem — getting clean, channel-ready product data in front of shoppers — but they differ sharply in how much control versus convenience they hand you. DataFeedWatch wins on pricing transparency, Feedonomics wins on hands-off managed service, and GoDataFeed splits the difference with a self-serve builder that scales cleanly into marketplaces. Match the choice to how much feed work your team actually wants to do in-house.
FAQ
Do these tools replace Google Merchant Center? No. They sit upstream of Merchant Center, transforming and optimizing your product data before it’s submitted, and they typically push the finished feed into Merchant Center and other channels automatically.
Can I use more than one of these tools at once? Technically yes, but it’s rarely worth it — each tool is designed to be your single source of feed truth for a given channel set, and running two in parallel risks conflicting data pushes.
Which tool is cheapest for a small catalog under 1,000 SKUs? DataFeedWatch’s Shop plan at $64/month is the lowest published entry price among the three for a catalog at or under 1,000 SKUs.
Does Feedonomics ever publish pricing? Not as of this review — pricing is quote-based and depends on SKU count, channel count, and service level, determined after a conversation with its sales team.
Heatmaps and session recordings tell you where visitors hesitate. A/B testing platforms let you actually change the page and measure whether a variant converts better — with the statistical rigor to know if that difference is real. Optimizely, VWO, and AB Tasty are three of the most established names in experimentation infrastructure, and 2026 brought a twist: VWO’s parent company Wingify and AB Tasty have merged into a single ~$100M-revenue group under Everstone Capital, announced in January 2026. Here’s what that means if you’re comparing these three platforms today.
At a Glance
Platform
Best For
Pricing Model
Standout Feature
Optimizely
Large enterprises with complex, multi-product experimentation needs
Fully custom, quote-based (“every plan individually packaged”)
Agentic Experimentation with a proprietary stats engine and feature management
VWO (Wingify)
Mid-market to enterprise teams wanting visual + code-based testing
Growth / Pro / Enterprise tiers, quote-based
Multi-armed bandit campaigns and built-in QA assistant
AB Tasty
Teams wanting testing plus personalization in one suite (now under the same parent as VWO)
Quote-based; no published self-serve pricing
Combined experimentation and personalization workflows
Short Verdict
Optimizely remains the choice for large enterprises that need an experimentation platform wired into a broader content and commerce stack, but it’s also the most expensive and least transparent on price. VWO offers the clearest tiered feature breakdown of the three and a genuinely capable free trial path. AB Tasty is best understood today not as a fully independent competitor but as a sibling product to VWO under the same parent company (Wingify/Everstone) following their January 2026 merger — worth noting if you’re choosing between the two, since consolidation is underway.
The VWO–AB Tasty Merger: What Changed in 2026
In January 2026, Everstone Capital (which had acquired Wingify, the parent of VWO, in 2025) combined Wingify with French experimentation vendor AB Tasty, reportedly forming a group with over $100 million in combined revenue. As of this writing, both brands’ public pricing and plans pages route through Wingify’s own pricing page, and AB Tasty’s “Plans” page redirects there as well — a strong signal the two product lines are being consolidated commercially, even if (per available public information) the extent of product-level integration and the long-term fate of each brand hadn’t been fully detailed yet. If you’re evaluating AB Tasty specifically, it’s worth confirming directly with sales whether you’d be buying AB Tasty’s product, VWO’s, or a converged offering, since this is still unfolding.
Optimizely doesn’t publish any pricing tiers or dollar figures. Its pricing page states plainly that “every Optimizely plan is individually packaged” — you describe your needs and a plan is built around them. Its experimentation lineup now centers on what it calls Agentic Experimentation: A/B, multi-page, feature, and server-side testing, a proprietary statistics engine, real-time personalization and audience targeting, and warehouse-native analytics, alongside a separate Feature Management product for flagging and rollouts. Optimizely also sells this alongside a much broader suite — a CMS, content marketing platform, commerce, and data platform — so it tends to suit organizations already considering (or already using) Optimizely for content and commerce, not just standalone testing.
VWO: Clear Tiering, Strong Mid-Market Fit
VWO (branded on its pricing page as Wingify) structures its Web Experimentation & Rollout product into three named tiers — Growth, Pro, and Enterprise — each clearly differentiated by feature, even though no dollar prices are published; every tier routes to “Schedule a Demo.” Growth includes a visual and code editor, unlimited experiments, variations and metrics, basic targeting, multi-armed bandit and rollout campaigns, and a QA assistant. Pro adds advanced targeting, guardrail metrics, sample-ratio-mismatch detection, multivariate and cross-domain testing, and pull-based integrations. Enterprise adds self-hosting, approval workflows, mutually exclusive experiment groups, SSO, API access, and 24×7 support. VWO also sells separate Growth/Pro/Enterprise-tiered products for Feature Experimentation, Personalization, Behavior Analytics, Journey Analytics, and User Feedback — so the platform can expand well beyond core A/B testing if needed.
AB Tasty: Testing and Personalization, Now Under the Same Roof as VWO
AB Tasty has historically positioned itself around combining A/B testing with on-site personalization in a single workflow, aimed at marketing and product teams rather than pure engineering-led experimentation teams. As of 2026, its public pricing page redirects to Wingify’s, and no independent AB Tasty price list is currently published separately. Prospective buyers should treat AB Tasty’s roadmap and support structure as being in transition following the merger, and should ask directly whether new contracts are being sold under the AB Tasty brand, the VWO brand, or a combined offering.
Pricing Comparison
Optimizely
VWO
AB Tasty
Published dollar pricing
No
No
No
Named tiers
Not publicly named for experimentation
Growth / Pro / Enterprise
Not currently published independently
Free trial
Not stated on pricing page
“Start Trial” option present; terms not stated
Historically offered; current terms unconfirmed post-merger
Corporate structure (2026)
Independent (owned by Insight Partners)
Merged with AB Tasty under Everstone Capital, Jan 2026
Merged with VWO/Wingify under Everstone Capital, Jan 2026
Pros and Cons
Optimizely
Pro: Enterprise-grade stats engine and feature management, well-suited to complex orgs
Pro: Integrates with a wider CMS/commerce/content suite if you need it
Con: Zero published pricing — every deal starts from scratch
Con: Can be overkill (and costly) for teams that only need standalone A/B testing
VWO
Pro: Clear, well-documented feature tiers even without public prices
Pro: Broad product family (analytics, personalization, feedback) under one tiering structure
Con: No dollar figures published anywhere; every plan needs a demo call
Con: Mid-merger with AB Tasty, so roadmap/support continuity is worth confirming
AB Tasty
Pro: Historically strong at combining testing with on-page personalization
Con: No independently published pricing page as of 2026 (redirects to Wingify)
Con: Buyers can’t yet be fully certain what they’re purchasing — AB Tasty’s product, VWO’s, or a merged one
Who It’s a Good Fit For
Choose Optimizely if you’re a large enterprise that wants experimentation tied into a broader content/commerce platform and has budget for a fully custom deal. Choose VWO if you want the clearest feature-tier breakdown of the three and value having analytics, personalization, and feedback tools in the same family. Approach AB Tasty with the merger in mind — it may still be the right fit for personalization-heavy use cases, but confirm current contract terms directly given the 2026 consolidation with VWO.
Who Should Look Elsewhere
If you just need to see where users hesitate or rage-click rather than run statistically rigorous experiments, a heatmap/session-recording tool is the simpler, cheaper starting point before any of these experimentation platforms. And if your team wants self-serve pricing with a credit card and no sales call, none of these three vendors currently offer that for their core testing products.
Bottom Line
None of these three platforms publish prices, so the real differentiator in 2026 is scope and corporate stability. Optimizely sells the deepest enterprise stack at the highest likely cost. VWO offers the most legible tier structure. AB Tasty is currently the most uncertain of the three, not because of product quality but because of its just-completed merger with VWO’s parent — get clarity on contract terms before signing.
FAQ
Are VWO and AB Tasty now the same product? Not exactly — they’re now sibling products under the same parent group (Wingify, under Everstone Capital) following a January 2026 merger, but as of this writing both brands still exist and the extent of product convergence hadn’t been fully detailed publicly.
Does Optimizely publish any pricing at all? No. Its pricing page states every plan is individually packaged based on a needs conversation, with no tiers or figures listed.
Can I try any of these before buying? VWO’s pricing page includes a “Start Trial” button, though it doesn’t state trial length or terms. Optimizely and AB Tasty’s current public pages point to demos rather than self-serve trials.
Which is best for a small team on a tight budget? None of the three publish self-serve, budget-friendly pricing — all require a sales conversation, so smaller teams may want to get quotes from all three (and consider lighter-weight alternatives) before assuming any one is affordable.
The terminal emulator market has quietly gotten interesting again. For years the choice was simple — iTerm2 on a Mac, something from the Linux distro on Linux, and whatever shipped with Windows on Windows. AI-assisted, block-based terminals changed that calculus, and the incumbents responded. Warp built an AI-native terminal from scratch and expanded beyond its original macOS-only launch to Linux and now Windows. iTerm2 stayed exactly what it has always been: a free, open-source, deeply customizable macOS terminal with no AI ambitions. And Microsoft’s Windows Terminal picked up a GitHub Copilot-powered chat feature while remaining free and open source under the MIT license. Here’s how they actually differ.
At a Glance
Terminal
Platforms
License/Cost
AI Features
Maintainer
Warp
macOS, Linux, Windows
Free tier available; Build from $20/mo, Max from $200/mo
Warp is the right pick if you want an AI agent genuinely built into your terminal workflow — not bolted on — and you’re comfortable paying for heavier agent usage once the free allotment runs out. iTerm2 remains the best free, no-strings macOS terminal for anyone who wants deep customization (profiles, hotkey windows, tmux integration) without any AI layer at all. Windows Terminal is the only reasonable default on Windows — it’s free, actively maintained by Microsoft, and now has an optional Copilot-powered chat feature if you want it.
Warp: AI-Native, Now Cross-Platform
Warp’s core pitch is an AI agent that lives inside the terminal rather than a separate chat window. Per Warp’s pricing page, the terminal itself has a genuinely free tier — core terminal features cost nothing — but AI usage is metered: the Free plan gives pay-as-you-go agent usage at API rates, while Build ($20/month, or $18/month billed annually) includes $20 of agent usage per month, and Max ($200/month) includes $200 of agent usage, roughly ten times Build’s allotment. Business runs $50 per user/month (up to 25 seats) with SAML SSO and admin data controls, and Enterprise offers custom pricing with self-hosted cloud agents. Warp Agent supports both frontier and open-source models with per-prompt model selection or automatic routing, and integrates with Slack, Linear, and GitHub so you can mention @Warp to investigate a bug or open a pull request directly. Warp launched on macOS first, later added Linux, and has since shipped a Windows version — it’s now the only one of these three terminals available on all three major desktop platforms.
iTerm2: The Free macOS Standard
iTerm2 has no pricing tiers because it doesn’t have a business model — it’s free software, GPL v2-licensed, with its source on GitHub, built specifically as a modern replacement for Apple’s bundled Terminal app on macOS 10.14 and later. There’s no AI assistant, no cloud account, and no subscription of any kind. Its value proposition instead is deep, long-accumulated customization: split panes, hotkey-triggered quake-style windows, extensive profile management, native tmux integration, and shell integration features that predate most of the “modern terminal” wave by years. It is strictly macOS-only, which rules it out for any team that needs a cross-platform standard.
Windows Terminal: Free, Open Source, Now With Copilot
Windows Terminal is Microsoft’s own modern terminal application, open source under the MIT license with its code public in the microsoft/terminal GitHub repository, and distributed through the Microsoft Store, GitHub Releases, and package managers like winget and Chocolatey. It requires Windows 10 build 19041 or later. Its core feature set covers tabs, panes, rich text rendering, globalization, and theming/configurability. In 2025, Microsoft added Terminal Chat — an AI assistant panel first shipped in the Canary preview channel and later made broadly available through GitHub Copilot integration, including for users on the free tier of GitHub Copilot. Terminal Chat lets you ask questions about commands or errors without leaving the terminal, but — unlike Warp’s agent — it is explicitly an add-on integration with GitHub Copilot rather than a first-party AI system built from the ground up.
iTerm2 cons: macOS only; no AI features of any kind; development pace is slower than the venture-backed alternatives.
Windows Terminal pros: free and open source with Microsoft’s backing; Terminal Chat is included free via GitHub Copilot Free, not gated behind a terminal-specific subscription.
Windows Terminal cons: Windows only; AI features depend on a separate GitHub Copilot account/entitlement rather than being native to the terminal itself.
Who Each Terminal Fits Best
Warp fits developers and teams who want an AI agent woven into their day-to-day terminal work and are willing to pay for it once free usage runs out. iTerm2 fits Mac users who want a powerful, free, no-subscription terminal and don’t need or want AI features. Windows Terminal fits any Windows developer by default — it’s free, actively developed by Microsoft, and its optional Copilot chat costs nothing extra if you already have GitHub Copilot Free.
Bottom Line
None of these three terminals is strictly “better” — they serve different platforms and different philosophies about AI. Warp is the AI-first choice and the only one of the three that now runs on all three major desktop operating systems. iTerm2 is the mature, free, AI-free choice for Mac loyalists. Windows Terminal is simply the correct default on Windows, with Copilot-powered chat as an optional, low-friction add-on rather than a core differentiator.
FAQ
Is Warp available on Windows now? Yes — Warp launched on macOS first, added Linux support, and has since shipped a Windows version, making it cross-platform across all three major desktop OSes.
Is iTerm2 ever coming to Windows or Linux? There’s no indication of this on iTerm2’s own site; it remains explicitly macOS-only (10.14 and later) with no cross-platform roadmap stated.
Do I need a paid GitHub Copilot plan to use Terminal Chat? No — Microsoft’s own announcement states Terminal Chat became available to users on GitHub Copilot Free, not only paid Copilot tiers.
Is Warp open source? No — unlike iTerm2 and Windows Terminal, Warp’s pricing and product pages don’t present it as an open-source project.
Oracle has two very different cloud ERP products, and the AI push happening inside each of them is easy to conflate. Oracle Fusion Cloud Applications — the suite covering Fusion ERP, HCM, and SCM — targets large enterprises and has its own AI Agent Studio for building custom agents on top of that suite. NetSuite is a separate product: a unified cloud ERP, built originally as an independent company and acquired by Oracle in 2016 for $9.3 billion, aimed primarily at small and mid-market businesses that want financials, inventory, CRM, and e-commerce in one system rather than stitched-together point solutions. NetSuite has its own, separately branded set of AI features rolling out through its periodic releases (most recently 2026.1 and 2026.2), and that’s the focus here — not Fusion Applications or AI Agent Studio.
At a Glance
Area
Feature
What It Does
Financial Close
Intelligent Close Manager
AI-driven status view of close progress; flags trends, errors, and projected activities
Fraud/Risk
Exception Management payment risk detection
Flags changes to critical vendor fields occurring near payment events
Cash Management
Generative AI bank transaction matching
Extracts structured data from bank statements to improve auto-matching rates
EPM: Reconciliation
Account Reconciliation AI assistant
Auto-detects new accounts and sets up reconciliation assignments and risk attributes
EPM: Matching
AI transaction matching assistant
ML-based matching with confidence scores, improving as users approve suggestions
EPM: Variance Analysis
GenAI flux analysis
Detects balance fluctuations against thresholds and drafts plain-language explanations
Planning
Multivariate AI forecasting
Surfaces the drivers behind each forecast for finance teams to validate
Procurement
Spend Classification model
Predictive model assigning procurement transactions to UNSPSC spend categories
Integration
Agentic AI (Integration Platform)
Agents with tools, memory, and RAG, connectable to a preferred LLM
Short Verdict
NetSuite’s 2026 AI releases focus heavily on the financial back office — close, reconciliation, cash, and forecasting — rather than broad generative chat features bolted onto the UI. The pattern across nearly every feature is the same: use AI to do the pattern-matching and first-draft work (matching transactions, drafting variance explanations, flagging anomalies), while keeping a human reviewer in the loop to approve or override. For mid-market finance and operations teams already running NetSuite, these additions compound incrementally release over release rather than representing one single “AI product” to evaluate — the value comes from adopting several of them together inside the existing ERP workflow.
NetSuite vs. Oracle Fusion Applications: Not the Same Product
This distinction matters because Oracle runs two parallel enterprise application businesses. Oracle Fusion Cloud Applications is the ERP/HCM/SCM suite built for large enterprises, with its own AI Agent Studio for building and deploying custom AI agents across that suite. NetSuite, by contrast, is the cloud ERP platform Oracle acquired as an independent company in 2016 in a deal valued at $9.3 billion. NetSuite retains its own product identity, release cadence, and AI roadmap, aimed at growing and mid-sized businesses that need one system covering financials, inventory, order management, and CRM rather than a large-enterprise application stack. Oracle does not merge NetSuite’s feature set or AI tooling into Fusion Applications, or vice versa — they are sold, licensed, and developed as separate product lines under the same parent company.
AI in the Financial Close
NetSuite’s Intelligent Close Manager, introduced in recent releases, gives finance teams a status view of close progress with hyperlinked tasks they can act on without switching screens. Its AI layer surfaces insights covering trends, errors, projected activities, and areas that need attention — aiming to shorten the manual effort of chasing down what’s blocking a close. A related capability, exception management for payment risk, flags changes to critical vendor data fields (like bank account details) that occur close to a scheduled payment — a pattern commonly associated with vendor-impersonation fraud — so finance teams can investigate before funds move rather than after.
AI in Cash Management and Reconciliation
On the cash side, NetSuite added generative AI to bank transaction matching: rather than relying on rigid rule-based parsing of bank statement data, the generative AI layer extracts richer, more structured information from statements so the underlying auto-match engine can successfully match a larger share of transactions automatically, reducing manual reconciliation work. In Enterprise Performance Management, the Account Reconciliation AI assistant detects when new general ledger accounts are created and automatically sets up their reconciliation assignments, preparers, formats, and risk attributes, learning from how prior reconciliation cycles were configured. A companion AI transaction matching assistant layers machine learning on top of traditional rule-based matching to surface less obvious relationships between transactions, presenting suggested matches with confidence scores that improve as accountants approve or reject them over time.
Variance Analysis, Forecasting, and Procurement
NetSuite’s GenAI flux analysis watches account balances for fluctuations against configurable thresholds and drafts plain-language explanations of what likely drove a variance, based on available financial and operational context — explanations a controller then reviews rather than accepts blindly. In planning and budgeting, multivariate AI forecasting doesn’t just produce a number; it exposes the drivers behind each forecast so finance teams can interpret and sanity-check the model’s output instead of treating it as a black box. On the procurement side, a Spend Classification predictive model automatically assigns incoming procurement transactions to standard UNSPSC spend categories, and a separate Product Recommendation model predicts which products a given customer is likely to purchase next — both narrower, task-specific machine learning models rather than general-purpose generative AI.
Agentic AI in the Integration Layer
NetSuite’s Integration Platform Enterprise tier includes agentic AI capabilities — agents built with tools, memory, and retrieval-augmented generation (RAG), with the ability to connect to a preferred large language model rather than being locked to one vendor’s model. Practically, this extends into workflow automation: integration workflows can pause mid-process for a human approval or additional input and resume automatically once that response arrives, rather than failing or requiring a manual restart.
Trade-offs
Pros: AI features are embedded directly into existing financial workflows (close, reconciliation, forecasting) rather than requiring a separate tool; most features keep a human-in-the-loop review step rather than fully autonomous action; task-specific predictive models (spend classification, product recommendation) tend to be more reliable than general-purpose generative AI for narrow, repeatable classification tasks.
Trade-offs: Many of the more advanced EPM and planning AI features are tied to specific modules (Account Reconciliation, Planning and Budgeting, Profitability and Cost Management) that may require separate licensing beyond base NetSuite; as with any AI feature trained on historical data, output quality depends on the cleanliness and consistency of a company’s existing NetSuite data.
Who This Matters For
This is most relevant to finance, accounting, and operations leaders at small and mid-market businesses already running or evaluating NetSuite as their core ERP — not to large enterprises evaluating Oracle Fusion Applications, which has a separate AI roadmap built around AI Agent Studio. Controllers and accounting teams doing manual reconciliation and close work are the most direct beneficiaries, since that’s where the bulk of 2026’s AI feature releases have concentrated.
Bottom Line
NetSuite’s AI strategy in 2026 isn’t one flagship feature — it’s a steady accumulation of narrow, workflow-embedded AI assistants across the financial close, cash management, reconciliation, forecasting, and procurement modules, each designed to reduce manual pattern-matching work while keeping a human reviewer in the loop. It’s a distinctly separate product and roadmap from Oracle’s Fusion Applications/AI Agent Studio line, aimed at a different customer segment. Mid-market finance teams evaluating NetSuite should look at which specific modules (EPM, Planning and Budgeting, Integration Platform Enterprise) carry the AI features that matter to them, since several require add-on licensing beyond the base platform.
FAQ
Is NetSuite the same product as Oracle Fusion ERP? No. NetSuite is a separate cloud ERP product that Oracle acquired as an independent company in 2016. Oracle Fusion Cloud Applications (including Fusion ERP) is a different, separately developed suite aimed at larger enterprises.
Does NetSuite have anything equivalent to Oracle’s AI Agent Studio? NetSuite offers its own agentic AI capabilities through its Integration Platform Enterprise tier, including agents with tools, memory, and RAG. This is a NetSuite-specific capability, distinct from Fusion Applications’ AI Agent Studio.
Who is NetSuite designed for? NetSuite is primarily aimed at small and mid-sized, growing businesses that want financials, inventory, order management, and CRM unified in one cloud system, rather than the largest enterprises Oracle’s Fusion suite typically targets.
Are NetSuite’s AI features fully autonomous? Generally no. Most of the AI capabilities described in NetSuite’s recent releases — reconciliation assistants, flux analysis, transaction matching — are designed to draft suggestions, flag anomalies, or surface patterns for a human reviewer to confirm, rather than acting without oversight.
How much did Oracle pay to acquire NetSuite? Oracle’s acquisition of NetSuite, announced and closed in 2016, was valued at approximately $9.3 billion.
Inbox overload is a different problem from “I was in a meeting and need notes” — it’s “I have 400 unread emails and need to know which three actually matter.” A new generation of AI email tools targets exactly that: triage, summarization, and drafting inside the inbox itself. This roundup covers three distinct approaches — a dedicated AI-first client (Shortwave), a premium speed-focused client with AI add-ons (Superhuman), and Google’s own Gemini features rolling directly into Gmail — and what each actually costs once you look past the marketing page.
AT A GLANCE
Tool
Core AI Triage Feature
Entry Price
Best For
Shortwave
AI filters (auto-label/organize), summaries, attachment analysis
Business: $30/seat/mo
Teams wanting a full AI-native email client with custom automation rules
Superhuman
Ask AI, Auto Drafts (plus “most AI features” at entry tier)
Starter: $30/mo; Business: $40/mo for Ask AI/Auto Drafts
Individual power users who want speed plus AI drafting
Gmail (Gemini)
Conversation summaries, Help Me Write, Suggested Replies; AI Inbox (triage) in limited testing
Free for summaries/drafting; “Ask your inbox” needs Google AI Pro/Ultra
Anyone already using Gmail who wants baseline AI for free
Short Verdict
Shortwave is the most purpose-built for triage: its “AI filters” let you write a plain-language rule (“archive anything from a newsletter that isn’t from my saved contacts”) and have it run automatically, with the number of filters scaling by tier (3 on Business, 10 on Premier, 50 on Max). Superhuman leans more on speed and a traditional inbox workflow, adding AI drafting (Auto Drafts) and an “Ask AI” feature at its $40/month Business tier, though it does not advertise an automated triage/filtering feature by that name. Gmail’s Gemini features are the free option with real substance — conversation summaries and smart draft replies are now rolling out to everyone at no cost — but the more advanced “ask your inbox” conversational search requires a paid Google AI Pro or Ultra subscription, and a genuine AI-driven inbox triage feature is still limited to trusted testers.
Shortwave: AI Filters as the Triage Engine
Shortwave prices itself at three tiers, per its own pricing page: Business at $30/seat/month, Premier at $45/seat/month, and Max at $120/seat/month. All three include “AI autocomplete, summaries & attachment analysis,” and the key triage differentiator is the number of custom “AI filters” you can run — natural-language rules that act on incoming mail — capped at 3 on Business, 10 on Premier, and 50 on Max. The underlying model also scales by tier, moving from a “standard intelligence” model on Business up through “expert intelligence” on Max, which Shortwave states is powered by progressively higher-tier Claude models. Features like “AI inbox organization,” “instant AI summaries,” and “personalized AI writing” are listed on the page but not clearly mapped to a specific tier, so smaller teams should confirm exactly which bundle includes what they need before buying.
Superhuman: Drafting and Q&A, Not Automated Triage
According to Superhuman’s own help center pricing article, the current plans are Starter at $30/month ($300/year) and Business at $40/month ($396/year), with Enterprise custom-quoted via direct contact. Starter includes “most Superhuman AI features” without naming them individually; Business adds two named features on top: Ask AI (conversational Q&A over your inbox) and Auto Drafts (AI-generated reply drafts). Notably, Superhuman’s own documentation does not name a dedicated automated “AI triage” or rule-based filtering feature the way Shortwave does — its AI investment is concentrated on speed, search, and drafting rather than autonomous inbox sorting.
Gmail: Free AI for Most, Paywalled AI for Power Features
Google has been rolling Gemini-branded features directly into Gmail rather than treating it as a separate product. Per Google’s own blog, conversation summaries (AI Overviews that synthesize long threads), Help Me Write (drafting/polishing), and Suggested Replies (an upgrade to the old Smart Reply) are rolling out to everyone at no additional cost. Two more advanced capabilities are gated behind a paid Google AI Pro or Ultra subscription: asking natural-language questions directly against your inbox contents, and an AI-powered Proofread tool. A genuine triage feature — AI Inbox, which filters clutter, flags to-dos, and identifies VIPs — exists but per Google’s announcement is limited to trusted testers only, with wider availability promised “in the coming months,” not yet generally available. Separately, Google’s Workspace Updates blog confirms these Gemini features are also expanding to Google Workspace business/enterprise customers 18 and older, with admins able to toggle them off, though Google’s posts don’t spell out a separate per-seat add-on price for Workspace tiers beyond the existing Workspace subscription.
Pricing & Feature Comparison
Dimension
Shortwave
Superhuman
Gmail (Gemini)
Entry price
$30/seat/mo (Business)
$30/mo (Starter)
Free (summaries, drafting); Google AI Pro/Ultra for advanced search
Automated rule-based triage
Yes — AI filters (3/10/50 by tier)
Not named as a distinct feature
AI Inbox — trusted testers only, not GA
Thread summarization
Included from Business
Included, tier unclear
Free for everyone
AI drafting
Included (autocomplete)
Auto Drafts — Business tier ($40/mo)
Help Me Write — free
Natural-language Q&A over inbox
Not specifically named
Ask AI — Business tier ($40/mo)
“Ask your inbox” — requires paid Google AI subscription
Pros and Cons
Shortwave
Pros: Real automated triage via custom AI filters; summaries and attachment analysis included from the entry tier
Cons: Per-seat pricing is higher than Superhuman’s entry tier; filter count caps could limit power users on lower plans
Superhuman
Pros: Fast, keyboard-driven UX; Ask AI and Auto Drafts are genuinely useful for high email volume
Cons: No clearly documented automated triage/filtering feature; top AI features locked to the $40/mo Business tier
Gmail (Gemini)
Pros: Core summarization and drafting features are free for everyone; zero migration needed if you already use Gmail
Cons: The actual triage feature (AI Inbox) isn’t generally available yet; deeper AI search needs a paid Google AI subscription
Who It’s a Good Fit For
Shortwave suits teams that want to codify triage logic as explicit, editable rules. Superhuman suits individuals who prioritize raw speed and are willing to pay for AI drafting as a bonus rather than the main event. Gmail’s Gemini rollout suits anyone who wants free, no-setup AI summarization today and is willing to wait for AI Inbox triage to reach general availability — or pay for Google AI Pro/Ultra if they want inbox Q&A now.
Who Should Look Elsewhere
If automated rule-based triage is the single must-have feature, Superhuman’s public documentation doesn’t clearly support that use case today — Shortwave is the better documented fit. If budget is the constraint, Gmail’s free tier covers summarization and drafting without a subscription, making both paid tools hard to justify unless you specifically need custom filters or a faster UI.
Bottom Line
There’s no single “best” AI inbox tool — it depends on whether you want rule-based automation (Shortwave), a fast client with AI bolted on (Superhuman), or free baseline AI inside the inbox you already use (Gmail). The one feature genuinely missing from the market right now is a widely available, no-waitlist, fully automated AI triage system: Gmail’s version is still testing, and Superhuman doesn’t document one at all. Shortwave is currently the clearest documented option if automated triage rules are the priority.
FAQ
Is Gmail’s AI Inbox feature available to everyone? No. Per Google’s own announcement, AI Inbox (the clutter-filtering, to-do-flagging triage feature) is limited to trusted testers, with broader rollout promised “in the coming months” as of the announcement.
Does Superhuman have an automated email-sorting AI feature? Superhuman’s official pricing documentation names Ask AI and Auto Drafts as its Business-tier AI features; it does not name a distinct automated triage/filtering feature the way Shortwave does.
How many AI filters does Shortwave give you on its cheapest plan? Three, on the $30/seat/month Business tier, scaling to 10 on Premier ($45/seat/month) and 50 on Max ($120/seat/month), per Shortwave’s pricing page.
Do I need to pay for Gmail’s AI features? Conversation summaries, Help Me Write, and Suggested Replies are free. Asking natural-language questions against your inbox and the Proofread tool require a Google AI Pro or Ultra subscription.
Once an application splits into multiple services, each with its own database, a single business operation can no longer rely on one ACID transaction to keep everything consistent. An order might need to debit a wallet service, reserve stock in an inventory service, and schedule a shipment in a logistics service — three separate databases, no shared transaction log. Distributed systems engineers have two long-standing answers to this problem: the Two-Phase Commit (2PC) protocol, which tries to make a distributed transaction behave like a local one, and the Saga pattern, which gives up strict atomicity in exchange for availability and loose coupling. This article explains how each works, where each breaks down, and when to reach for one over the other.
AT A GLANCE
Dimension
Two-Phase Commit (2PC)
Saga Pattern
Consistency model
Strong / atomic (all-or-nothing)
Eventual consistency via compensation
Coordinator
Single transaction coordinator, synchronous
Orchestrator (optional) or choreography via events
Failure handling
Blocking — participants wait, holding locks, if coordinator fails after prepare
Two-Phase Commit gives you a real atomic transaction across multiple resources, but it does so by blocking and holding locks until every participant agrees — a design that doesn’t survive the availability and decoupling goals of modern microservices. The Saga pattern accepts eventual consistency and pushes the complexity of “what if a step fails” onto explicit compensating transactions, but it keeps services independently deployable and available. For most microservice architectures built since the mid-2010s, Sagas have won; 2PC survives mainly inside single-vendor database clusters and legacy enterprise middleware.
How Two-Phase Commit Works
2PC coordinates a transaction across multiple participants (resource managers) through a dedicated transaction coordinator, in two rounds:
Phase 1 — Prepare/Vote: The coordinator asks every participant to prepare the transaction. Each participant does whatever work is needed to guarantee it can commit — writing to its own log, acquiring locks — then replies “yes” (ready) or “no” (abort).
Phase 2 — Commit/Abort: If every participant voted yes, the coordinator logs the decision and tells everyone to commit. If any participant voted no, or timed out, the coordinator tells everyone to abort.
Once a participant votes “ready” in phase 1, it has given up the right to unilaterally abort — it must wait for the coordinator’s final word. That’s precisely what makes 2PC powerful (every participant ends up in the same state) and precisely what makes it fragile: if the coordinator crashes after collecting votes but before broadcasting the decision, every participant that voted “ready” is stuck holding its locks, unable to safely commit or abort on its own, until the coordinator recovers. This is the classic blocking problem of 2PC, and it’s the reason participants keep other transactions waiting on the same rows for however long the coordinator is down. Three-Phase Commit (3PC) adds a timeout-driven pre-commit phase to reduce blocking, but it can’t fully eliminate inconsistency risk during network partitions, which is why most distributed databases now favor leader-election via Paxos or Raft for coordinator availability instead.
How the Saga Pattern Works
A Saga, as defined by Chris Richardson’s microservices.io pattern catalog, implements a business transaction that spans several services as “a reliably coordinated sequence of local transactions.” Each service commits its own local transaction and publishes an outcome; there is no cross-service lock and no global coordinator holding resources hostage. If a step fails partway through, the saga doesn’t roll back in the database sense — it runs compensating transactions that semantically undo the completed steps (for example, refunding a payment or releasing reserved inventory), which developers must design explicitly because sagas get none of the automatic rollback an ACID transaction provides.
There are two coordination styles:
Choreography: No central coordinator. Each service’s local transaction publishes an event; other services subscribe and react, triggering their own local transactions. This keeps services decoupled but makes the overall flow harder to trace as the number of steps grows.
Orchestration: A saga orchestrator explicitly tells each participant which local transaction to run, and decides whether to continue or trigger compensations based on the replies. AWS’s own prescriptive guidance recommends orchestration (for example, with AWS Step Functions) for sagas with more than a handful of steps, because it’s easier to visualize, test, and monitor than a web of choreographed events.
Because the saga’s steps complete asynchronously, the overall business transaction is only eventually consistent — a client typically learns the final outcome through a callback, a status endpoint it polls, or a notification, not an immediate response. Sagas also provide no isolation: another process can read intermediate, partially-applied state while the saga is still running, so designers need explicit countermeasures (e.g., semantic locks, commutative updates, or “pessimistic view” patterns) to avoid anomalies.
Pros and Cons
Two-Phase Commit — Pros
True atomicity: every participant ends up in the same committed or aborted state.
No application-level compensation logic to design or test.
Well-supported by XA-compliant databases and transaction managers (JTA/JTS).
Two-Phase Commit — Cons
Blocking: a crashed coordinator can leave participants holding locks indefinitely.
Poor fit across service/network/trust boundaries — assumes all participants are reachable and well-behaved.
Reduces availability and throughput under contention since locks are held across the whole round trip.
Rarely supported across heterogeneous message brokers and modern cloud-native databases.
Saga Pattern — Pros
No distributed locks; services stay available and independently deployable.
Scales naturally with asynchronous, event-driven architectures.
Failure handling (compensation) is explicit and testable business logic rather than infrastructure magic.
Saga Pattern — Cons
Only eventual consistency — clients can’t assume the operation is “done” immediately.
No built-in isolation; concurrent sagas can expose dirty reads unless you add countermeasures.
Compensating transactions must be idempotent and may not perfectly reverse side effects (e.g., an email already sent can’t be unsent).
Requires reliable messaging patterns (Transactional Outbox, event sourcing) so a service’s DB write and event publish don’t drift out of sync.
Who Each Is a Good Fit For
Two-Phase Commit still makes sense inside a single trust domain with low-latency, highly reliable links — for example, coordinating writes across shards of the same distributed database product, or XA transactions spanning an application server and a database in a traditional monolith. The Saga pattern is the default choice for microservice architectures where services own separate databases, deploy independently, and must stay available even when one downstream dependency is degraded — order processing, booking and travel reservations, and payment workflows are the textbook examples cited by both Chris Richardson and AWS’s own architecture guidance.
Bottom Line
2PC trades availability for atomicity; Sagas trade atomicity (and isolation) for availability and loose coupling. Neither is “wrong” — they solve different problems. If you’re building microservices with independently owned data stores, start by assuming you’ll need a Saga and design your compensations up front; reach for 2PC only when every participant lives in the same tightly controlled, low-latency domain and you genuinely need all-or-nothing semantics.
FAQ
Is the Saga pattern a replacement for ACID transactions? No. It’s a workaround for situations where a single ACID transaction across services isn’t possible. It provides eventual consistency and requires explicit compensation logic, not the atomicity guarantees of ACID.
Why don’t modern cloud databases use 2PC more widely? Because its blocking behavior is incompatible with high availability goals — a coordinator failure can stall transactions and hold locks until recovery. Distributed databases generally prefer consensus protocols (Raft/Paxos) for coordinator failover, or avoid cross-shard transactions altogether.
What’s the difference between saga orchestration and choreography? Orchestration uses a central coordinator that explicitly directs each step and compensation; choreography has services react to each other’s events with no central controller. Orchestration is easier to monitor and debug; choreography is more decoupled but harder to trace as complexity grows.
Can you combine 2PC and Sagas in the same system? Yes. It’s common to use 2PC/local ACID transactions within a single service’s own database, and Sagas to coordinate across services. The two aren’t mutually exclusive — they operate at different scopes.
What is a “compensating transaction”? A business-level operation that semantically undoes the effect of a previously committed local transaction — for example, issuing a refund instead of reversing a payment at the database level. It must be designed to be idempotent since messages can be redelivered.
A backend-as-a-service (BaaS) platform is more than a hosted database — it’s the whole package: authentication, serverless functions, file storage, and realtime sync, wired together so a small team can ship an app without standing up its own infrastructure. That’s a different question than “which hosted database should I use,” which is why this comparison deliberately sets aside Supabase (already covered on this site as a database-as-a-service option alongside PlanetScale and Neon) and instead looks at three platforms built around the full backend: Google’s Firebase, the open-source Appwrite, and the Hasura-powered Nhost.
At a Glance
Platform
Database Model
Free Tier
Entry Paid Plan
Self-Hostable?
Firebase
Firestore (NoSQL) + Realtime Database
Spark: 50K MAU auth, 1GB Firestore storage, no credit card required
Blaze: pay-as-you-go, Spark limits included free
No — Google Cloud only
Appwrite
Document/NoSQL (with Postgres option)
Free org plan, resources freeze (not deleted) at limits
Pro (usage-based, extra charges past limits)
Yes — open source, self-hostable
Nhost
Dedicated PostgreSQL instance
Starter: free, 1GB DB, 1GB storage, 1 active project
Pro: from $25/month + $15 compute credit
Partially — open components, managed platform is primary
Short Verdict
Firebase is still the most mature and battle-tested option, with the deepest mobile SDKs and the largest free-tier ceiling for auth (50,000 monthly active users). Appwrite is the best fit if you want an open-source, self-hostable backend you can run on your own infrastructure without changing your application code. Nhost is the strongest choice if your app’s data model is fundamentally relational and you want a real dedicated Postgres instance plus Hasura’s instant GraphQL layer, rather than a NoSQL document store.
Firebase: The Mature Default
Firebase runs on two plans: Spark, a genuinely free tier with no payment method required, and Blaze, pay-as-you-go pricing that keeps Spark’s free quotas and bills only for usage above them (plus up to $300 in free credit for eligible accounts). The free quotas are generous for early-stage apps: authentication is free up to 50,000 monthly active users via Identity Platform, Firestore gives 1 GiB storage with 20,000 writes and 50,000 reads per day, and Hosting includes 10GB storage with 360MB/day transfer. Cloud Functions, notably, requires the Blaze plan — it isn’t available on Spark at all. Firebase’s core services are Authentication, Firestore, Realtime Database, Cloud Functions, Cloud Storage, and Hosting, all tied into the Google Cloud ecosystem (and billed at Google Cloud rates once you exceed free quotas).
Appwrite: Open Source, Self-Hostable
Appwrite’s core differentiator is that it’s fully open source, with its source code on GitHub, and designed to be self-hosted on your own servers in addition to the managed Appwrite Cloud. Its free organization plan is “100% free” with no time limit, though hitting a resource limit freezes the project (making the console read-only) rather than deleting data, until you upgrade or the billing cycle resets. The Pro plan removes that freeze and adds overage billing with 75%/100% usage alerts and an optional budget cap. Every plan includes the “full Appwrite platform toolkit” — Auth, Databases, Storage, Functions, and Realtime are bundled rather than priced as separate add-ons, alongside additional products like Messaging and Sites. Appwrite also offers dedicated database compute tiers for teams that need guaranteed resources.
Nhost: Postgres-First, Hasura-Powered
Nhost’s defining choice is using a real, dedicated PostgreSQL instance per project rather than a shared NoSQL document store, paired with the Hasura GraphQL Engine for instant realtime GraphQL subscriptions and event triggers, role-based authorization, and auto-generated APIs. Plans run Starter (free forever, 1 GB database, 1 GB storage, 5 GB egress, one active project that pauses after a week of inactivity), Pro (from $25/month, includes $15 in compute credit, 10 GB database and 50 GB storage included, automated backups and point-in-time recovery starting at $100), Team (from $599/month), and custom Enterprise. Authentication supports unlimited users on every plan, including social OAuth, email/password, magic links, and 2FA, with advanced security features reserved for Enterprise. Functions execution is billed per GB-hour past the included allotment.
Feature Comparison
Capability
Firebase
Appwrite
Nhost
Auth free tier
50K MAU
Unlimited on Free (subject to other project limits)
Unlimited users on all plans
Database type
NoSQL document (Firestore) + Realtime DB
Document/NoSQL, with a managed Postgres option
Dedicated PostgreSQL
GraphQL support
No native GraphQL layer
No native GraphQL layer
Yes — Hasura GraphQL Engine built in
Serverless functions
Cloud Functions (Blaze plan only)
Included on all plans
Included, billed per GB-hour past quota
Self-hosting
Not possible
Fully supported, open source
Core components open, managed platform is primary path
Pros and Cons
Firebase pros: mature SDKs for every mobile/web platform, huge community, generous auth free tier.
Firebase cons: Cloud Functions requires the paid Blaze plan; NoSQL data modeling can be awkward for relational data; vendor lock-in to Google Cloud.
Appwrite pros: genuinely self-hostable with no feature gating between cloud and self-hosted; generous free org plan with no hard deletion on limits.
Appwrite cons: smaller mobile SDK maturity than Firebase; dedicated database compute tiers get expensive fast ($999–$4,099/month).
Nhost pros: real relational database with proper SQL, built-in GraphQL via Hasura, unlimited auth users even on the free tier.
Nhost cons: free project pauses after a week of inactivity; Team plan jumps steeply from Pro ($25 to $599/month).
Who Each Platform Fits Best
Firebase fits mobile-first teams that want the most mature, widely documented backend with minimal setup. Appwrite fits teams with data-residency or compliance requirements who need to self-host, or anyone who wants to avoid cloud vendor lock-in entirely. Nhost fits teams whose data is naturally relational and who want GraphQL out of the box without hand-building a Hasura deployment themselves.
Bottom Line
The real decision here isn’t “which BaaS is best” in the abstract — it’s whether your data is relational, whether you need to self-host, and how much you value Firebase’s maturity against newer, more open alternatives. Firebase remains the safest default for mobile apps with NoSQL-friendly data. Appwrite is the right call when self-hosting or open-source licensing is a requirement, not a preference. Nhost is the right call when you want Postgres and GraphQL without assembling the stack yourself.
FAQ
Can I use Firebase Cloud Functions on the free Spark plan? No — according to Firebase’s own pricing page, Cloud Functions requires the pay-as-you-go Blaze plan, though Blaze still includes a free monthly quota (2 million invocations) before charges apply.
Is Appwrite’s free plan time-limited? No, Appwrite describes free organizations as “100% free” indefinitely; hitting a resource limit freezes the project rather than deleting it or cutting off the trial.
Does Nhost’s free tier expire? The project itself doesn’t expire, but it pauses after one week without activity and needs to be manually resumed.
Which of these includes built-in GraphQL? Only Nhost, via the bundled Hasura GraphQL Engine with realtime subscriptions and event triggers; Firebase and Appwrite don’t ship a native GraphQL layer.
Web analytics tools tell you how many people visited a page. Product analytics tools tell you what they actually did once they got there — which features they clicked, where they dropped off in an onboarding flow, and whether a new release moved retention at all. For product and growth teams building software, that event-level, user-centric view is the whole point. Amplitude, Mixpanel, and PostHog are the three platforms product teams compare most often in 2026, and each takes a noticeably different approach to pricing and scope. Here’s how they stack up.
At a Glance
Platform
Best For
Free Tier
Entry Paid Pricing
Standout Feature
Amplitude
Mid-market and enterprise product teams
2M events/month, forever
Plus: usage-based, starts at $0 and scales with MTUs/events
Behavioral cohorts and built-in experimentation
Mixpanel
Startups through growth-stage teams
Up to 1M events/month
Growth: from $0, e.g. ~$438/mo (annual) at 5M events
Fast self-serve funnel and retention analysis
PostHog
Engineering-led teams wanting an all-in-one toolkit
1M events/month, plus free allowances on other products
Pay-as-you-go beyond free tier; per-event billing, no seat fees
Analytics, session replay, flags, and surveys in one suite
Short Verdict
Amplitude is the strongest pick for product teams at mid-market or enterprise scale who need robust cohorting, governance, and cross-functional reporting alongside analytics. Mixpanel remains the fastest way for a lean team to get from “we added an event” to a usable funnel or retention chart, and its free tier is genuinely useful. PostHog is the one to choose if you want analytics bundled with session replay, feature flags, A/B testing, and surveys under a single, usage-based bill rather than buying several separate tools.
Amplitude: Built for Scale and Governance
Amplitude’s free plan now includes 2 million events per month with no time limit, plus 10,000 session replays and 5,000 AI agent sessions monthly — a meaningfully larger free tier than it has historically offered. Its Plus plan starts at $0 and scales with usage up to roughly 700,000 monthly tracked users (MTUs) or 70 million events, adding more behavioral cohorts, longer data retention, and additional workspace “spaces.” Growth and Enterprise plans move to custom, event-based pricing with higher session-replay and AI-agent-session allowances, faster support SLAs, and (at Enterprise) a dedicated account manager. Amplitude doesn’t publish flat dollar figures for Growth or Enterprise — both require talking to sales, and several add-ons (like the Activation add-on with the Behavioral Cohorts API) are priced as a percentage of the base plan.
Where Amplitude earns its reputation is in analysis depth: cohort-building, journey/pathfinder analysis, and governance features (data taxonomy management, role-based access) that larger orgs with multiple product teams tend to need. The tradeoff is a steeper learning curve and a pricing model that gets opaque fast once you’re past the free tier.
Mixpanel: Fast Setup, Transparent Self-Serve Pricing
Mixpanel’s free plan covers up to 1 million events per month with unlimited users, 10,000 session replays, 1,000 monthly experiment users, and up to 10 active feature flags — enough for most early-stage products to get real signal before paying anything. The Growth plan is the clearest-priced option of the three platforms here: Mixpanel publishes a live calculator showing, for example, roughly $100/month (annual billing) at 1.5M events, climbing to around $438/month at 5M events and about $840/month at 10M events, with volume discounts built in. Anything above 20M events/month moves to custom Enterprise pricing, which adds unlimited alerts, anomaly detection, root-cause analysis, and a dedicated success team.
Mixpanel’s strength is speed to insight — its funnel, retention, and flow reports are built for a PM or marketer to self-serve without writing SQL. It also runs a Startup Program offering a full year free (including 1 billion events) for companies founded within the last five years that meet funding eligibility rules.
PostHog: Analytics Plus the Rest of the Product Toolkit
PostHog’s pitch is different: instead of just product analytics, it bundles analytics, session replay, feature flags, error tracking, surveys, and experimentation into one platform with one bill. Every product gets its own monthly free allowance — 1 million analytics events, 5,000 session replays, 1 million feature flag requests, 100,000 tracked exceptions, 1,500 survey responses, and 10GB of ingested logs. Beyond those limits, billing is pay-as-you-go and per-event, with no published flat per-event rate on the pricing page (it links to a separate usage breakdown) but no seat-based fees either. There are no minimum commitments or required annual contracts, though volume and startup/non-profit discounts are available.
The tradeoff is that PostHog’s analytics UI, while capable, is less polished for non-technical self-serve than Mixpanel’s, and it’s best suited to teams comfortable with a more engineering-centric, self-hosted-friendly tool.
Pricing Snapshot
Amplitude
Mixpanel
PostHog
Free tier
2M events/month, forever
1M events/month
1M events/month (plus other free product allowances)
Entry paid tier
Plus — usage-based from $0
Growth — e.g. ~$438/mo at 5M events (annual)
Pay-as-you-go, per-event beyond free tier
Enterprise
Custom quote
Custom quote (up to 1T events/month)
Custom annual/volume agreements available
Published rate card?
Partial (Free/Plus limits only)
Yes, for Growth tier
Free-tier limits published; per-event rate not listed on main page
Pros and Cons
Amplitude
Pro: Deep cohorting, pathfinder analysis, and governance tools suited to larger product orgs
Pro: Generous 2M-event free tier with no expiry
Con: Growth and Enterprise pricing is entirely quote-based, making budgeting harder
Con: Steeper learning curve than Mixpanel for first-time users
Mixpanel
Pro: Clearest, most transparent self-serve pricing of the three
Pro: Fast, intuitive funnel and retention reporting
Con: Feature-flag and experimentation limits are tight on lower tiers
Con: Enterprise-grade governance features require custom pricing
PostHog
Pro: One platform covers analytics, replay, flags, surveys, and experiments
Pro: No seat fees; generous combined free allowances across products
Con: Per-event overage pricing isn’t published on the main pricing page
Con: Analytics UI is less guided than Mixpanel’s for non-technical users
Who It’s a Good Fit For
Choose Amplitude if you’re a mid-market or enterprise product org that needs governed, cross-team analytics and is willing to negotiate custom pricing. Choose Mixpanel if you want the most predictable self-serve pricing and the fastest path from event tracking to a usable dashboard. Choose PostHog if you’d rather consolidate analytics, session replay, flags, and experimentation into one usage-based bill, especially if your team is engineering-heavy.
Who Should Look Elsewhere
If you only need pageview and traffic-source reporting for a marketing site rather than in-product event tracking, a web analytics tool like GA4 or Plausible is a better (and cheaper) fit than any of these three. And if budget certainty matters more than analytical depth, both Amplitude’s and PostHog’s upper tiers can surprise you — get a usage estimate before committing.
Bottom Line
All three tools can answer “what are users actually doing in our product,” but they get there differently. Mixpanel optimizes for fast, transparent self-serve. Amplitude optimizes for depth and governance at scale, with pricing to match. PostHog optimizes for consolidation — fewer vendors, one usage-based bill. The right choice depends less on raw analytics quality, which is strong across all three, and more on how your team wants to pay and how much surrounding tooling (replay, flags, experiments) you want bundled in.
FAQ
Is Amplitude or Mixpanel better for startups? Mixpanel’s pricing is more transparent at low-to-mid volumes, and its free tier (1M events) plus self-serve Growth calculator make budgeting easier for an early-stage team. Amplitude’s free tier is larger (2M events) but Growth/Enterprise pricing requires a sales conversation.
Does PostHog require self-hosting? No — PostHog offers a managed cloud product with the same pay-as-you-go pricing; self-hosting is an option, not a requirement.
Can these tools replace a web analytics platform like GA4? Not really. They’re built for in-product, event-level user behavior analysis rather than marketing-site traffic and acquisition reporting, so most teams run them alongside a web analytics tool rather than instead of one.
Which platform has the most generous free tier? By raw event volume, Amplitude’s 2M events/month (with no expiry) is the largest single number, but PostHog’s free tier spans more products (analytics, replay, flags, surveys, error tracking) at smaller individual allowances.
Service meshes like Istio, Linkerd, and Cilium get a lot of attention for how they move and secure traffic between services. But traffic encryption and L7 policy don’t catch a process inside a container spawning a reverse shell, writing to a file it has no business touching, or escalating privileges once an attacker is already on the box. That’s a different problem — runtime security — and the tool of choice for solving it at scale is eBPF: a Linux kernel technology that lets lightweight, sandboxed programs run inside the kernel itself to observe or intervene in what’s actually happening on a host. Three open-source projects have become the standard names in eBPF-based runtime security: Falco, Tetragon, and Aqua Tracee. They overlap in purpose but differ in architecture and depth of enforcement.
Detection and alerting (response via Falcosidekick to 50+ destinations)
CNCF graduated project (2024)
Tetragon
Isovalent (part of Cisco)
eBPF kernel observability tied to the Cilium project’s tooling
Can both observe and actively block/kill actions in-kernel in real time
Open source, developed within the Cilium ecosystem
Aqua Tracee
Aqua Security (Team Nautilus)
eBPF syscall + Linux Security Module (LSM) hook events, rule engine in Go/Rego
Detection/forensics by default; enforcement available via Aqua’s commercial platform
Open source (aquasecurity/tracee on GitHub)
Short Verdict
Falco is the most broadly adopted and vendor-neutral choice, with the largest rule ecosystem and the deepest CNCF governance, making it a safe default for teams that mainly need detection and alerting across containers, hosts, and cloud events. Tetragon stands out when real-time, in-kernel enforcement matters — stopping a malicious process before it finishes executing, not just alerting after the fact — and it’s the natural choice for teams already running Cilium for networking. Aqua Tracee is the best fit for teams wanting a lightweight, portable, open-source forensics tool with LSM-hook-based detection that’s harder to evade than plain syscall tracing, especially if they’re already evaluating or using Aqua’s commercial platform.
What eBPF Is, and Why Runtime Security Tools Use It
eBPF (extended Berkeley Packet Filter) is a Linux kernel technology that allows small, verified programs to run safely inside the kernel without modifying kernel source code or loading traditional kernel modules. Before eBPF, observing low-level activity — every system call a process makes, every file it opens, every network connection it initiates — typically meant either slow, invasive instrumentation or a custom kernel module carrying real stability and security risk. eBPF programs are checked by an in-kernel verifier before they’re allowed to run, can be attached to specific kernel events (a system call, a network packet, a security hook), and execute with minimal overhead because the filtering and aggregation happen in the kernel instead of shuttling every raw event up to userspace first. That combination — safety, low overhead, and deep visibility — is exactly what runtime security needs: the ability to watch everything a workload does at the kernel level, in real time, without the workload itself being modified or aware it’s being observed. This is fundamentally different from a service mesh sidecar, which operates at the network layer between services; eBPF-based tools operate underneath the application entirely, at the level of the operating system itself.
Falco: The CNCF-Graduated Standard
Falco was created by Sysdig and donated to the Cloud Native Computing Foundation in 2018, reaching incubating status in 2020 and graduating — the CNCF’s highest maturity tier — in 2024. Falco describes itself as working like “a network of security cameras” for infrastructure: it collects events from the Linux kernel (via a modern eBPF probe, its preferred collection method, or an older kernel-module option), from Kubernetes audit logs, and from cloud event sources like AWS CloudTrail, then checks all of it against a large library of rules. Built-in and custom rules can flag behavior such as cryptomining processes, unexpected file exfiltration, privilege escalation attempts, and rootkit installation. Falco itself focuses on detection and alerting; its companion project Falcosidekick forwards matched events to more than 50 downstream destinations — Slack, email, message queues, serverless functions — so a response action can be triggered externally. Falco’s biggest advantages are its maturity, its large community-maintained rule set, and its CNCF governance, which makes it a low-risk default pick for most organizations.
Tetragon: Real-Time Enforcement From the Cilium Ecosystem
Tetragon comes out of Isovalent, the company behind the Cilium networking and security project; Isovalent was acquired by Cisco (announced in December 2023), and Isovalent’s own materials now identify the team as “Isovalent at Cisco,” operating as part of Cisco’s security portfolio. Isovalent describes Tetragon as providing “eBPF-based transparent security observability combined with real-time runtime enforcement.” The key architectural difference from Falco is that Tetragon’s policies run entirely in the kernel and can actively intervene — not just alert — stopping a dangerous system call or action as it happens rather than only logging it afterward. Because the filtering and policy logic execute in-kernel, overhead stays low even with fine-grained enforcement rules in place. Tetragon is open source and doesn’t require Cilium to run, but it shares engineering and community ties with the broader Cilium project, making it a natural complement for teams that have already adopted Cilium for Kubernetes networking and want the same eBPF foundation extended into runtime security enforcement.
Aqua Tracee: Forensics-Focused and LSM-Aware
Aqua Tracee, released by Aqua Security’s Team Nautilus in 2019, was originally built around eBPF syscall tracing but evolved specifically because syscall tracing alone is vulnerable to time-of-check-to-time-of-use (TOCTOU) evasion techniques, where an attacker changes what a syscall actually does between the moment it’s checked and the moment it executes. To close that gap, Tracee added collection of Linux Security Module (LSM) hook events, which Aqua describes as giving more comprehensive and reliable detection than syscall tracing by itself. Tracee’s architecture splits into an eBPF-based tracing component that collects events and a rule engine (supporting both Go and Rego/OPA policies) that evaluates them against built-in behavioral signatures — covering things like anti-debugging techniques, possible code injection, fileless execution, unauthorized kernel module loading, and LD_PRELOAD abuse. A 2021 update (version 0.6.0) added CO-RE (Compile Once – Run Everywhere) portability, letting Tracee run on BTF-enabled kernels without needing to compile the eBPF probe separately for each kernel version — a meaningful operational improvement for anyone running mixed kernel versions across a fleet. Tracee is fully open source on GitHub; Aqua’s commercial platform builds on the same eBPF foundation to add runtime enforcement and broader workload protection.
Trade-offs
Falco — Pros: largest community and rule library, CNCF-graduated governance, broad event-source support beyond just the kernel. Trade-offs: primarily detection/alerting rather than in-kernel blocking; response actions depend on integrating Falcosidekick with an external system.
Tetragon — Pros: genuine real-time in-kernel enforcement, not just alerting; low overhead by design. Trade-offs: smaller standalone community than Falco; closest value realized alongside the broader Cilium/Isovalent ecosystem, now under Cisco.
Aqua Tracee — Pros: LSM-hook detection resists simple syscall-level evasion; CO-RE portability simplifies multi-kernel deployments. Trade-offs: full enforcement capability sits behind Aqua’s commercial platform rather than the open-source core; smaller community footprint than Falco’s.
Who This Matters For
Security and platform teams running containerized workloads in production — particularly on Kubernetes, where a single compromised container can be a foothold into much more — are the core audience. These tools matter most for organizations that need to detect or stop in-host threats (privilege escalation, container breakout attempts, cryptomining, data exfiltration) that happen below the network layer a service mesh or firewall can see. They’re complementary to, not a replacement for, network-layer security tools like Cilium’s own network policies or Istio’s mutual TLS.
Bottom Line
All three tools rest on the same core technology — eBPF’s ability to observe kernel-level activity cheaply and safely — but they diverge on what happens next. Falco is the mature, CNCF-governed detection standard with the broadest adoption. Tetragon pushes further into real-time in-kernel enforcement and is backed by the team behind Cilium, now inside Cisco. Aqua Tracee carves out a niche with LSM-hook detection that’s more resistant to evasion than syscall tracing alone, with commercial enforcement available through Aqua’s broader platform. Many organizations end up running Falco or Tetragon as their primary detection layer and evaluating Tracee for specific forensics or evasion-resistance needs, rather than treating the three as mutually exclusive.
FAQ
What’s the difference between eBPF-based runtime security and a service mesh like Cilium or Istio? A service mesh secures and observes traffic moving between services at the network layer. eBPF-based runtime security tools operate at the operating-system level, watching what processes inside containers actually do — system calls, file access, privilege changes — regardless of network activity.
Does using Cilium for networking require also using Tetragon for security? No. Tetragon is a separate, independent project that doesn’t require Cilium to run, though it shares the same eBPF foundation and engineering lineage, and many teams adopt both together.
Is Isovalent still an independent company? No. Cisco announced its acquisition of Isovalent in December 2023, and Isovalent’s own current materials identify the team as operating as part of Cisco.
Can these tools block an attack, or do they only alert? It depends on the tool. Falco is primarily a detection and alerting system, relying on external integrations for response. Tetragon can enforce policy and block actions directly in the kernel in real time. Aqua Tracee’s open-source core is detection-focused, with active enforcement available through Aqua’s commercial product.
Do these tools require special kernel versions? eBPF capabilities depend on the Linux kernel version and configuration (such as BTF support for CO-RE portability). Falco can also fall back to a kernel-module collection method on systems where its modern eBPF probe isn’t the best fit. Always check each project’s current documentation for supported kernel versions.
Every major BI vendor now ships a natural-language AI layer on top of its dashboards, but none of them give it away for free. Tableau, Microsoft Power BI, and ThoughtSpot have each built a conversational assistant that lets business users ask questions in plain English instead of building pivot tables — the catch is that in all three cases, the AI layer is gated behind a specific license tier, a separate compute add-on, or a “contact sales” bundle. This guide breaks down exactly what you get, and what it actually costs, before you commit budget to one of these platforms.
AT A GLANCE
Tool
AI Feature
Entry Price (with AI)
Best For
Tableau
Tableau Pulse + Tableau Agent
Cloud Standard from $15/user/mo (Pulse); Agent requires Server/Cloud+ or Tableau Next
Teams already inside the Salesforce/Tableau ecosystem
Microsoft Power BI
Copilot in Power BI / Fabric
Requires Fabric F2+ capacity or Premium Per User ($24/user/mo); Pro alone ($14/user/mo) does not include it
Microsoft 365 and Fabric shops
ThoughtSpot
Spotter AI Agent
Pro tier from $50/user/mo (25 Spotter queries/user/mo) or usage-based from $0.10/credit
Search-driven, self-serve analytics for business users
Short Verdict
If you only need AI-generated plain-language summaries of existing dashboards, Tableau Pulse is included starting at the $15/user/month Cloud Standard tier, making it the cheapest entry point to “AI-assisted BI.” If your organization already pays for Microsoft 365 and a Fabric capacity (even a small F2 SKU, since Microsoft removed the old F64 requirement), Power BI Copilot is effectively bundled in rather than a new line item. If your priority is letting non-technical staff type questions and get instant visual answers rather than browse pre-built dashboards, ThoughtSpot’s Spotter is the most purpose-built option, but it’s also the one most likely to need a paid, per-user AI allotment or usage-based credits once you go past the free query cap.
Tableau: Pulse and Agent, Split Across Products
Tableau’s AI story is split into two separate features that are not available in the same way everywhere. Tableau Pulse — natural-language, AI-generated metric summaries delivered proactively (think “your revenue is down 4% this week because of X”) — is listed on Tableau’s own pricing page as part of Tableau Cloud, starting at the Standard tier ($15/user/month, billed annually). Tableau Agent, a generative AI assistant for building and editing content conversationally, appears instead on the Tableau Server tiers (Authoring and Prep) and on the higher Cloud+ and Tableau Next tiers. Cloud+, Server+, and the full “Tableau+” bundle (which adds Tableau Next, Tableau’s semantic/agentic layer at $40/user/month standalone) are all quoted as “Contact Sales” rather than published self-serve prices. In practice, that means a team on plain Tableau Cloud Standard gets Pulse but not Agent, and getting the full generative AI experience means moving to a higher, custom-quoted tier.
Microsoft Power BI: Copilot Now Opens Up at F2, But Pro Alone Isn’t Enough
Power BI’s core subscription tiers are Pro ($14/user/month) and Premium Per User ($24/user/month), the latter adding “Advanced AI” capabilities per Microsoft’s own pricing comparison. Copilot in Power BI — which drafts report summaries, generates DAX, and answers questions about a dataset in natural language — has historically required Fabric capacity at the F64 SKU or above, which was an expensive jump for smaller teams. Microsoft’s Fabric team announced it is removing the F64 requirement, extending Copilot and other Fabric AI capabilities to all paid Fabric SKUs starting at F2, rolled out beginning April 30 (per the official Fabric Updates Blog). That’s a meaningful change: a smaller, cheaper Fabric capacity reservation can now unlock Copilot rather than forcing a jump to the top tier. Note that a shared “Fabric Copilot Capacity” feature still requires F64. Either way, a Power BI Pro license by itself, with no Fabric capacity and no Premium Per User, does not include Copilot — budget for the capacity or the per-user upgrade separately.
ThoughtSpot: Spotter Is the Product, Not an Add-On — But It’s Metered
ThoughtSpot built its platform around search-driven analytics, and Spotter (its AI agent for natural-language Q&A over data) is the most deeply integrated of the three rather than a bolt-on. Per ThoughtSpot’s own pricing page, the entry-level Essentials tier (from $25/user/month) does not list Spotter. Spotter becomes available at the Pro tier, which comes in two pricing structures: a usage-based model starting at $0.10/credit with unlimited LLM tokens for Spotter, or a user-based model from $50/user/month that caps Spotter usage at 25 queries per user per month. Heavier usage requires either the usage-based credits or an add-on ThoughtSpot calls “Unlimited Spotter” (no public price listed — contact sales). Enterprise, as usual, is fully custom-quoted.
Pricing & Feature Comparison
Dimension
Tableau
Power BI
ThoughtSpot
Base license (no AI)
Cloud Standard $15/user/mo
Pro $14/user/mo
Essentials from $25/user/mo
AI-inclusive tier
Cloud Standard (Pulse) / Cloud+ or Server+ (Agent) — Cloud+ is custom-quoted
Premium Per User $24/user/mo, or any paid Fabric capacity from F2
Pro, from $50/user/mo (25 queries/mo) or $0.10/credit usage-based
Natural-language Q&A
Tableau Agent (Server/Cloud+/Next)
Copilot in Power BI
Spotter
Unlimited AI usage path
Custom quote
Scales with Fabric capacity size
Usage-based credits or “Unlimited Spotter” add-on, custom quote
Top tier
Tableau+ Bundle (custom)
Fabric Capacity Reservation (custom)
Enterprise (custom)
Pros and Cons
Tableau
Pros: Pulse’s AI summaries are included at a relatively low entry price; strong visualization depth; mature ecosystem
Cons: Full conversational Agent experience is split across multiple tiers and the top bundle is custom-priced only
Power BI
Pros: Copilot is now reachable at a much lower Fabric capacity tier (F2) than before; tight Microsoft 365/Excel integration
Cons: Pro license alone doesn’t include Copilot; you must separately budget for Fabric capacity or Premium Per User
ThoughtSpot
Pros: Search/AI-first UX built from the ground up, not retrofitted; usage-based pricing can suit variable workloads
Cons: Entry tier excludes Spotter entirely; per-user query caps on the user-based Pro plan can be restrictive for heavy analysts
Who It’s a Good Fit For
Tableau suits organizations already in the Salesforce ecosystem that want AI summaries without re-platforming. Power BI is the natural choice for Microsoft-centric enterprises that already run Fabric or are willing to adopt a small Fabric capacity. ThoughtSpot fits teams whose primary ask is “let business users ask data questions in natural language” as the core workflow, not an add-on to existing dashboards.
Who Should Look Elsewhere
Budget-constrained teams unwilling to pay for Fabric capacity should think twice about Power BI’s AI story, since Pro alone won’t unlock Copilot. Teams needing guaranteed, uncapped AI query volume at a fixed low price may find ThoughtSpot’s metering frustrating. Any team wanting one single transparent per-user AI price across the whole platform will be disappointed by all three vendors, since each pushes real volume use toward custom enterprise quotes.
Bottom Line
None of these three vendors sell “AI-powered BI” as a single clean price — each gates the generative layer behind a specific tier, capacity SKU, or usage meter. Tableau Pulse is the cheapest way to get AI summaries into users’ hands; Power BI Copilot is now more accessible than it used to be but still requires a Fabric capacity purchase; ThoughtSpot Spotter is the most AI-native but meters usage tightly below Enterprise. Match the AI feature you actually need to the specific tier that includes it before signing — don’t assume the advertised “base” price includes the AI your team is excited about.
FAQ
Does Power BI Pro include Copilot? No. Per Microsoft’s own comparison table, Copilot in Power BI requires either a paid Fabric capacity (now available from the F2 SKU up, not just F64+) or a Premium Per User license at $24/user/month.
Is Tableau Pulse the same as Tableau Agent? No. Pulse is proactive, AI-generated metric summaries, included starting at Tableau Cloud Standard ($15/user/month). Tableau Agent is a conversational assistant for building/editing content, listed on Server tiers and the higher Cloud+/Tableau Next tiers, several of which are custom-quoted.
How many Spotter queries do I get on ThoughtSpot’s cheapest AI-enabled plan? On the user-based Pro plan (from $50/user/month), ThoughtSpot caps Spotter at 25 queries per user per month. The usage-based Pro plan ($0.10/credit) instead includes unlimited LLM tokens for Spotter, metered by credit consumption.
Can I get exact enterprise pricing for any of these online? No. Tableau+ Bundle, Tableau Cloud+/Server+, Power BI Fabric capacity reservations, and ThoughtSpot Enterprise are all quoted only after contacting sales.
Cross-platform mobile development has three serious contenders left standing in 2026, and each one now has a fundamentally different answer to the same question: how do you share code across iOS and Android without sacrificing native feel? React Native rebuilt its internals around a new architecture to close the performance gap. Flutter replaced its rendering engine outright. And Kotlin Multiplatform took the opposite approach entirely — share logic, not UI, unless you specifically opt into Compose Multiplatform. None of these are marketing taglines; they’re documented architectural facts worth understanding before you commit a team to one.
At a Glance
Framework
Language
UI Approach
Rendering
Maintained By
React Native
JavaScript/TypeScript
Shared UI via native components
Fabric (native-backed shadow tree)
Meta + open-source community (MIT license)
Flutter
Dart
Shared UI, fully custom-drawn
Impeller (mandatory on iOS, default elsewhere)
Google (BSD-3 license)
Kotlin Multiplatform
Kotlin
Shared logic; UI optional via Compose Multiplatform
Native UI by default, Compose when opted in
JetBrains + Kotlin Foundation (Apache 2.0)
Short Verdict
React Native is the pragmatic default for teams with existing JavaScript/web expertise and a need for a huge plugin ecosystem. Flutter is the strongest choice when pixel-perfect, consistent UI across every platform (including desktop and embedded) matters more than using native widgets. Kotlin Multiplatform is the best fit for teams — especially ones with existing native Android/iOS codebases — who want to share business logic and networking code while keeping fully native UI, with the option to share UI later via Compose Multiplatform.
React Native’s New Architecture
React Native’s biggest change in recent years is the move away from the original asynchronous JSON “bridge” between JavaScript and native code. The replacement, generally called the New Architecture, rests on three pieces: JSI (JavaScript Interface), a C++ layer that lets JavaScript hold direct references to native objects instead of serializing messages across a bridge; Fabric, the new rendering system that builds a shared C++ shadow tree and supports React 18+ concurrent features; and TurboModules, which replaces the old native module system with lazily loaded, JSI-backed modules generated from typed specs. Together these enable “Bridgeless mode,” where the legacy bridge is removed entirely. React Native is MIT-licensed and primarily driven by Meta’s React Native team, with substantial community and partner contributions (including Microsoft’s React Native Windows/macOS and Expo).
Flutter’s Impeller Rendering Engine
Flutter’s defining architectural trait has always been that it doesn’t use native UI widgets at all — it draws every pixel itself via its own rendering engine, which is how it guarantees visual consistency across platforms. That engine used to be Skia; it is now Impeller, which precompiles shaders and builds pipeline state objects ahead of time instead of compiling shaders at runtime, specifically to eliminate the jank caused by first-run shader compilation. Per Flutter’s own documentation, Impeller is the only supported rendering engine on iOS (no Skia fallback exists there), is the default on Android API 29+ with Vulkan (falling back to OpenGL on older devices), and became the default — with an opt-out still available — on macOS, Linux, and Windows as of Flutter 3.47. Flutter’s web target still uses Skia. Flutter and Dart are developed by Google under a BSD-3-Clause license.
Kotlin Multiplatform (KMP) takes a structurally different stance: it’s built to let you share business logic, data models, and networking code across Android, iOS, desktop, web, and server targets — while leaving the UI layer native and separate by default. That’s a deliberate contrast with React Native and Flutter, both of which share UI code as their core premise. If you do want to share UI, Compose Multiplatform — JetBrains’ declarative UI framework modeled on Jetpack Compose — sits on top of KMP and is documented as stable on Android, iOS, and desktop, with web support still in Beta. KMP itself is described by JetBrains as production-ready across its supported platforms. Kotlin is developed by JetBrains and governed by the Kotlin Foundation under an Apache 2.0 license, with Google promoting KMP heavily for Android-first teams extending to iOS.
Architecture and Performance Trade-offs
Factor
React Native
Flutter
Kotlin Multiplatform
Native look-and-feel
High — uses real native components
Lower — custom-drawn widgets mimic native style
Highest — UI is fully native unless using Compose Multiplatform
Startup/JS overhead
JS engine startup cost, reduced by Bridgeless mode
No JS engine; Dart compiles to native/AOT code
No bridge or JS engine; compiles to native binaries/bytecode
Ecosystem size
Very large (npm, long history)
Large, growing fast
Smaller but growing, strong in Android-first shops
Desktop/web targets
Possible via community packages
First-class (Windows, macOS, Linux, web)
Supported via Compose Multiplatform/Kotlin-Wasm
Pros and Cons
React Native pros: enormous ecosystem, large hiring pool, New Architecture closed much of the performance gap.
React Native cons: migrating older apps to the New Architecture can be nontrivial; still an abstraction layer over native UI.
Flutter cons: custom-drawn widgets can feel slightly “off” from true native controls; Dart has a smaller talent pool than JS or Kotlin.
Kotlin Multiplatform pros: true native UI by default; incremental adoption inside existing native codebases; backed by JetBrains and the Android team.
Kotlin Multiplatform cons: sharing UI via Compose Multiplatform is newer and less battle-tested on web; smaller third-party library ecosystem than JS.
Who Each Framework Fits Best
React Native suits product teams with web/JS skills who want fast iteration and the largest available library ecosystem. Flutter suits teams that need visual consistency across mobile, desktop, and web from one codebase and are comfortable with Dart. Kotlin Multiplatform suits teams — particularly those with an established native Android app — who want to incrementally share logic with iOS without rewriting their UI layer, and who value staying close to each platform’s native APIs.
Bottom Line
The three frameworks have genuinely diverged in philosophy rather than converging on one “right” answer. React Native bets on bridging to native UI efficiently; Flutter bets on owning the entire rendering pipeline; Kotlin Multiplatform bets on sharing logic while leaving UI native. The right choice in 2026 depends less on raw performance — all three are fast enough for the overwhelming majority of apps — and more on your team’s existing language skills and how much UI consistency you actually need across platforms.
FAQ
Is React Native’s New Architecture mandatory now? It became the default starting with React Native 0.76; existing apps on the old bridge architecture should plan a migration, but the exact cutover timeline depends on the version you’re running.
Can Flutter still use Skia instead of Impeller? Only on Android (via a manifest flag) and desktop platforms where an opt-out is still available for now; iOS has no Skia fallback, and Flutter’s documentation says the opt-out elsewhere is planned to be removed in a future release.
Does Kotlin Multiplatform require Compose Multiplatform? No. KMP lets you share non-UI code while keeping fully native UI (SwiftUI/UIKit on iOS, Jetpack Compose or Views on Android); Compose Multiplatform is an optional, separate layer for teams that also want to share UI.
Which has the largest third-party package ecosystem? React Native, by a wide margin, due to its age and overlap with the broader npm/JavaScript ecosystem.
Most organizations running Kubernetes at scale don’t run one cluster — they run dozens, spread across regions, clouds, and sometimes on-premises data centers. Managing that sprawl by logging into each cluster separately doesn’t scale past a handful of environments. A category of “fleet management” or multi-cluster platforms has grown up to solve this: a single control plane for applying policy, rolling out upgrades, and monitoring health across every cluster an organization runs, regardless of where it lives. The three most common names in this space are SUSE’s Rancher, Google’s GKE Enterprise (formerly branded Anthos), and Microsoft’s Azure Arc-enabled Kubernetes paired with Azure Kubernetes Fleet Manager. Each takes a different approach to the same underlying problem.
At a Glance
Tool
Vendor
Best For
Cluster Scope
Licensing Model
Rancher (Rancher Prime)
SUSE
Any CNCF-conformant cluster, any cloud or on-prem, vendor-neutral fleets
EKS, AKS, GKE, RKE2, K3s, and other CNCF-certified distributions
Free open-source core; paid Prime tier adds 24/7 enterprise support
GKE Enterprise (formerly Anthos)
Google Cloud
Teams standardizing on GKE who also need to attach external or on-prem clusters
GKE natively; attached clusters for EKS, AKS, on-prem, and edge
Paid edition of GKE; priced per vCPU/hour on top of underlying infrastructure
Azure Arc-enabled Kubernetes + Fleet Manager
Microsoft
Azure-centric organizations managing hybrid and multicloud AKS/attached clusters
AKS natively via Fleet Manager; Arc attaches clusters running anywhere
Arc control-plane features largely free; billed for underlying compute and select add-ons
Short Verdict
If your clusters span multiple clouds, multiple vendors, and on-prem hardware, and you don’t want to be locked into one hyperscaler’s control plane, Rancher is the most neutral option — it’s built specifically to manage any CNCF-conformant cluster the same way. If you’ve already standardized on GKE as your primary platform and occasionally need to attach an EKS, AKS, or on-prem cluster into the same fleet, GKE Enterprise extends that investment without forcing a new tool. If your organization is Azure-first, Azure Arc plus Kubernetes Fleet Manager gives you native integration with Azure Policy, Azure Monitor, and Entra ID for governing clusters wherever they run, with Fleet Manager specifically optimized for managing many AKS clusters as one logical unit.
What “Multi-Cluster Management” Actually Solves
A single Kubernetes cluster already has its own API server, RBAC, and networking. The problem emerges once an organization has ten, fifty, or hundreds of clusters — one per team, per region, per compliance boundary, or per customer. Without a unifying layer, platform teams end up scripting the same upgrade, the same network policy, and the same security scan separately against every cluster, and drift between clusters becomes almost guaranteed. Multi-cluster management tools address three recurring needs: centralized visibility (one dashboard showing the health and inventory of every cluster), centralized policy (applying RBAC, network, and admission-control rules consistently), and centralized lifecycle operations (provisioning new clusters and rolling out version upgrades in a controlled, staged way).
Rancher: The Vendor-Neutral Layer
Rancher, now sold commercially as Rancher Prime after SUSE’s acquisition of the project, is built around the idea that it shouldn’t matter where a cluster runs. It supports provisioning and managing clusters on EKS, AKS, GKE, and on-prem distributions like RKE2 and K3s, and more broadly “any CNCF-certified Kubernetes distribution.” SUSE’s own product pages describe Rancher’s role as covering cluster provisioning, version management, monitoring, and centralized audit logging, while enforcing consistent security policy across every attached cluster using Kubewarden-based policy rules. Rancher’s free community edition is fully open source; Rancher Prime adds 24/7 enterprise support and additional supply-chain features such as signed, hardened application images through SUSE’s Application Collection. Because Rancher doesn’t require any single cloud as its home base, it’s the natural fit for organizations deliberately avoiding lock-in to one hyperscaler’s control plane.
GKE Enterprise: Anthos Folded Into GKE
Anthos, Google’s original multi-cluster and hybrid-cloud platform, has been consolidated into GKE Enterprise, the premium edition of Google Kubernetes Engine. Google Cloud describes GKE Enterprise as bringing “the best of GKE and Anthos into an integrated and intuitive container platform, with a unified console experience.” In practice, this means fleet-based management is now a built-in capability of GKE itself rather than a bolt-on product: clusters are grouped into fleets, policy and configuration can be applied consistently across a fleet, and teams can be scoped to see only the clusters and namespaces relevant to them. GKE Enterprise natively manages GKE clusters and can attach externally running clusters — including EKS, AKS, and on-premises clusters — into the same fleet for unified policy and monitoring, though the depth of control available to an attached non-GKE cluster is generally less than for a native GKE cluster. As of September 2025, Google consolidated GKE into a single paid offering, with some advanced capabilities now available as standalone add-ons rather than requiring the full legacy Anthos license.
Azure Arc and Kubernetes Fleet Manager
Microsoft splits this problem into two related products. Azure Arc-enabled Kubernetes lets any CNCF-conformant cluster — running in another cloud, on-premises, or at the edge — be “attached” to Azure so it shows up in the Azure portal and can receive Azure Policy, Azure Monitor, GitOps configuration, and Microsoft Defender security coverage, without migrating the cluster itself. Azure Kubernetes Fleet Manager is built specifically for managing many AKS clusters as a single logical fleet: it supports staged, approval-gated update runs across clusters and regions, namespace-scoped resource placement based on labels and capacity, DNS-based traffic distribution across member clusters via Azure Traffic Manager, and GitOps-based automated deployments from a Git repository. Microsoft’s own Fleet Manager documentation has at times been inconsistent about whether Arc-attached (non-AKS) clusters can fully participate as Fleet Manager members, so organizations planning to mix AKS and non-Azure clusters in one fleet should verify current support against Microsoft’s latest documentation before committing to that architecture.
Trade-offs
Rancher — Pros: cloud-agnostic, fully open-source core, broad distribution support. Trade-offs: enterprise support and advanced supply-chain features require a paid Prime subscription; you own more of the operational burden of running the Rancher management cluster itself.
GKE Enterprise — Pros: deepest integration if GKE is your primary platform, unified console, built-in service mesh and policy tooling. Trade-offs: non-GKE attached clusters get shallower management than native GKE clusters; licensing has shifted over time, so cost planning requires checking current GKE edition pricing.
Azure Arc + Fleet Manager — Pros: tight Azure AD/Entra ID, Policy, and Monitor integration; Fleet Manager’s update orchestration is genuinely useful for large AKS estates. Trade-offs: Arc’s value is strongest for organizations already inside the Azure ecosystem; cross-cloud fleet support has had rough edges in documentation and preview features.
Who This Matters For
Platform engineering teams responsible for more than a handful of clusters are the core audience. A startup running a single cluster doesn’t need any of these tools yet. But once an organization has separate clusters per environment (dev/staging/prod), per region for latency or data-residency reasons, or per business unit, the cost of managing each one by hand — repeating the same RBAC changes, network policies, and upgrade windows manually — starts to outweigh the cost of adopting a fleet management layer. The choice between the three generally comes down to which cloud (if any) already anchors the organization’s infrastructure, rather than a strict feature-for-feature comparison.
Bottom Line
There’s no universally “best” multi-cluster tool — the right pick depends on how anchored an organization already is to a particular cloud. Rancher wins on neutrality and openness, GKE Enterprise wins for GKE-first shops that want Anthos’s old capabilities without a separate product, and Azure Arc plus Fleet Manager wins for Azure-first organizations that want hybrid visibility without leaving the Microsoft ecosystem. All three continue to evolve quickly, so teams evaluating them should check each vendor’s current documentation for the latest feature scope before standardizing.
FAQ
Is Anthos still a separate product from GKE Enterprise? No. Google has consolidated Anthos’s capabilities into GKE Enterprise, the premium edition of GKE, rather than selling it as a standalone product with its old branding.
Is Rancher free to use? Rancher’s core platform is open source and free. SUSE sells Rancher Prime, which adds enterprise-grade support and additional hardened-image and supply-chain features on top of the free core.
Can Azure Arc manage clusters that aren’t running on Azure at all? Yes — that’s its core purpose. Arc-enabled Kubernetes can attach clusters running in other clouds, on-premises data centers, or at the edge, so they appear in and can be governed from the Azure portal.
Do these tools replace a service mesh like Istio or Cilium? No. Multi-cluster management tools handle fleet-level provisioning, policy, and lifecycle operations; a service mesh handles traffic routing, mutual TLS, and observability between services. Several of these platforms (such as GKE Enterprise) bundle a managed service mesh as an additional component, but the two solve different layers of the problem.
Can I mix tools — for example, use Rancher to manage an AKS cluster? Generally yes, since Rancher is designed to manage any CNCF-conformant cluster including AKS, EKS, and GKE. The reverse is more limited: cloud-native fleet tools like Fleet Manager are optimized for their own cloud’s clusters first.
GraphQL has settled into a predictable shape by 2026: most teams aren’t writing a resolver layer from scratch, they’re buying or self-hosting a platform that handles federation, schema governance, and gateway routing for them. Three names keep coming up in that conversation, and they’re no longer directly interchangeable the way they once looked. Apollo GraphQL has consolidated around GraphOS, a managed control plane paired with its open-source Router. Hasura has moved its flagship product to Hasura DDN, a metadata-driven “data delivery network” that generates APIs over existing sources. And WunderGraph — once a broader backend-as-a-service style API gateway — has narrowed its focus entirely to Cosmo, an Apache 2.0-licensed, eBay-backed open-source GraphQL federation platform. This piece compares what each one actually is today, not what it was marketed as two years ago.
At a Glance
Platform
Core Model
Free Tier
Entry Paid Tier
Open Source?
Apollo GraphOS
Managed schema registry + self-hosted Router
Up to 3 devs, 1-day data retention, Router capped at 60 req/min
Developer: from $5 per million ops/month
Router is source-available; GraphOS platform is closed
Hasura DDN
Metadata-driven instant GraphQL/REST over data sources
DDN Free (fallback after trial)
DDN Base (30-day free trial, then usage-based)
Core engine has open-source roots; DDN billing is proprietary
If your organization already runs Apollo Server/Client and needs an enterprise-grade managed control plane with deep tooling (contracts, schema proposals, operation-level observability), Apollo GraphOS is the safest default — at a price. If you want to expose GraphQL (and REST/JSON:API) over existing Postgres, MySQL, or other data sources without hand-writing resolvers, Hasura DDN remains the fastest path from database to API. If you want a fully open-source federation gateway you can self-host indefinitely with no vendor lock-in, and you’re comfortable running your own schema registry, WunderGraph Cosmo is the strongest free option of the three.
Apollo GraphOS: The Incumbent’s Control Plane
Apollo’s business today is GraphOS — a cloud platform that pairs a schema registry, usage reporting, and change-check tooling with the self-hosted GraphOS Router, a Rust-based gateway that executes federated queries across subgraphs. The Router supports federated subscriptions, the @defer directive, automatic persisted queries, JWT-based authorization, and distributed query-plan caching.
Pricing is tiered by developer seat count and data retention rather than purely by request volume: the Free plan supports up to 3 developers with just 1 day of operation history and a Router capped at 60 requests per minute, which is really a sandbox limit, not a production one. The Developer plan starts at $5 per million operations billed monthly, supports up to 10 developers, and includes a $50 signup credit. Standard and Enterprise move to custom, sales-negotiated pricing with longer data retention (90 days and 18 months respectively) and formal SLAs.
Hasura DDN: Instant APIs Over Your Data
Hasura’s pitch has always been different from Apollo’s: instead of federating hand-written GraphQL services, it generates a GraphQL (and JSON:API) layer directly from your connected data sources, with role-based authorization baked in. The current product line is Hasura DDN (“Data Delivery Network”), which replaces the older Hasura v2 engine with a metadata-first model built around “Model” and “Command” objects.
DDN ships three plans — Free, Base, and Advanced — with Base and Advanced each offering a 30-day free trial that does not auto-convert to paid. Billing is unusual among the three platforms here: it’s based on the number of models and “active models” (those queried more than 1,000 times a month), the number of availability zones you run in, and data transfer, rather than a flat per-request rate. Hasura’s own pricing page is explicit that costs don’t scale directly with traffic, which is a meaningfully different cost model than Apollo’s per-operation billing.
WunderGraph Cosmo: The Open-Source Federation Bet
This is where the “verify current product status” caveat matters most. WunderGraph originally marketed itself as a broader API/BaaS-style gateway product. That positioning has effectively been replaced: WunderGraph’s site today centers on Cosmo, described as “full lifecycle API management for (federated) GraphQL” — a schema registry, composition checker, analytics/tracing layer, and a Go-based router, all released under the Apache 2.0 license on GitHub. According to TechCrunch’s March 2025 reporting, eBay backed WunderGraph specifically to build Cosmo as an open-source federation gateway, reflecting eBay’s own internal use of federated GraphQL at scale.
Cosmo’s pricing runs Developer (free, self-hosted router, 1 federated graph, up to 10M requests/month, Discord support), Launch ($499/month, 2 graphs, 250M requests/month, email support), Scale (custom, 5 graphs, up to 1B requests/month, SSO/RBAC), and Enterprise (custom, dedicated solutions architect, up to 99.99% uptime SLA). Every tier, including Enterprise, lists a self-hosted router option — the managed/cloud control plane is what you’re really paying for as you move up tiers.
Feature Comparison
Capability
Apollo GraphOS
Hasura DDN
WunderGraph Cosmo
Federation support
Yes (Apollo Federation spec)
Limited — primarily single-engine over connected sources
Yes (Federation v1 and v2)
Auto-generated API from DB
No — you write subgraphs
Yes, this is the core value proposition
No — connects existing GraphQL services
Self-hosted router license
Elastic License (source-available)
Varies by component
Apache 2.0 (fully open source)
Event/streaming integration
Via subscriptions
Event triggers
Streams (Kafka, NATS, Redis)
Billing basis
Per-operation + seats
Models + AZs + data transfer
Graphs + requests/month
Pros and Cons
Apollo GraphOS pros: mature tooling, the de facto federation standard, strong enterprise support tier.
Apollo GraphOS cons: free tier’s 60 req/min Router cap is production-unfriendly; per-seat pricing penalizes larger teams.
Hasura DDN pros: fastest time-to-API over existing databases; traffic-independent pricing can be cheaper at high volume.
Hasura DDN cons: billing model (models/AZs) is harder to forecast than flat request pricing; less suited to hand-rolled federation across many bespoke services.
WunderGraph Cosmo pros: genuinely open source end to end; generous free tier (10M requests/month); no lock-in.
WunderGraph Cosmo cons: smaller ecosystem and community than Apollo; you manage more infrastructure yourself even on paid tiers.
Who Each Platform Fits Best
Apollo GraphOS fits teams already invested in the Apollo ecosystem (Apollo Client, Apollo Server) that need enterprise governance features like schema proposals and contracts. Hasura DDN fits teams that want to expose a GraphQL API over Postgres or other databases quickly, without maintaining resolver code. WunderGraph Cosmo fits platform engineering teams building a federated graph from many existing services who want full control and no recurring vendor fee for the core router.
Bottom Line
These three products solve related but distinct problems. Apollo sells governance and federation tooling around a router you still have to design subgraphs for. Hasura sells speed — turning a database into a GraphQL API with minimal code. WunderGraph’s Cosmo sells openness — a federation gateway you can run entirely on your own terms, backed now by real production use at eBay scale. Picking between them should start with which problem you actually have, not which name is most familiar.
FAQ
Is WunderGraph still a separate BaaS product? No. WunderGraph’s current public-facing product is Cosmo, an open-source GraphQL federation platform; the company’s site no longer centers on a general-purpose BaaS gateway offering.
Can I self-host Apollo’s router for free in production? The Router binary itself is source-available and free to run, but GraphOS’s Free plan throttles the managed control plane to 60 requests per minute, so production use typically requires at least the Developer tier.
Does Hasura DDN replace Hasura v2? DDN is Hasura’s current flagship product line with a different metadata model (Models/Commands) and a different, traffic-independent billing approach than the older v2 engine.
Is Cosmo compatible with Apollo Federation? Yes — Cosmo states support for both Federation v1 and v2, so existing Apollo-style subgraphs can generally be composed through Cosmo’s router.
A dedicated business number is one of the first things a solopreneur or a newly distributed team needs, and it’s rarely worth tying to a personal cell plan. Google Voice, OpenPhone, and Grasshopper are three of the most commonly recommended options — but one of them has quietly changed its name. We verified current pricing directly from each vendor’s own site as of November 2026, and we’re flagging that rebrand clearly below rather than letting readers stumble into a confusing mismatch between what they searched for and what they find when they click through.
At a Glance
Tool
Starting Price
Free Plan
Best For
Google Voice
Free for personal use; business (Workspace) from $10/user/month
Yes — personal use is free with one US number
Solopreneurs already on Google Workspace who want the cheapest possible business number
OpenPhone (now Quo)
From $19/user/month monthly, $15/user/month annual
No free plan; 7-day free trial
Small teams wanting a modern, AI-assisted shared business line with CRM integrations
Grasshopper
From $18/month monthly, $14/month annual (True Solo)
No free plan; 7-day free trial
Solo entrepreneurs who want a virtual phone system layered on top of an existing personal or mobile number
Short Verdict
If budget is the only concern and you’re comfortable inside the Google ecosystem, personal Google Voice is free and covers a huge share of solopreneur needs (one number, free US calls and texts); step up to the paid Google Voice for Business tier only once you need multiple users or admin controls. OpenPhone rebranded to Quo during 2025 — the product, team, and underlying technology are the same company, just under a new name and with new AI features (an assistant called Sona) bolted on — and it remains the strongest pick for small teams that want shared numbers, CRM integrations, and call analytics. Grasshopper is the most “old school” virtual phone system of the three, built around forwarding calls to a number you already carry rather than a fully native app experience, which makes it a solid fit for true solopreneurs who don’t want to switch phones at all.
What These Tools Actually Do
All three give you a phone number that’s separate from your personal cell number, routable to one or more devices, with business features like voicemail transcription, call recording, auto-attendants, and (for the paid tools) team features like shared lines and call routing. Google Voice has two very different faces: a genuinely free personal product (one number, calls/texts to the US and Canada largely free) and a separate, paid Google Workspace add-on aimed at businesses that need multiple users and admin control. Quo (the rebranded OpenPhone) and Grasshopper are both purpose-built small-business phone systems from the ground up, with no free personal tier — you’re always on a trial or a paid plan.
A sourcing note on the Grasshopper numbers: Grasshopper’s own live pricing page renders its plan cards through a script that didn’t return tier-by-tier detail to our fetch tool, so we cross-verified the figures above against a secondary industry source and against Grasshopper’s own page metadata, which independently states a starting price of “$14/month, billed annually” with “savings over 20%” versus monthly billing — both of which match the True Solo figures exactly. We’re treating these as reliable but recommend a final check at grasshopper.com/pricing before you buy, since add-on costs (extra numbers run $9/month each; extra extensions on Solo Plus run $3–$5/month) sit on a separate part of the page we couldn’t independently confirm beyond that secondary source.
Pros and Cons
Google Voice
Pros: Genuinely free for personal/solo use with no catch for US-based calling and texting; business tier starts at the lowest per-user price of the three; tight integration with Gmail, Calendar, and the rest of Google Workspace.
Cons: The free personal tier isn’t designed for team/shared-line use; business tier requires a Google Workspace subscription underneath it, adding cost most comparisons leave out; fewer small-business-specific features (like dedicated CRM integrations) than Quo.
Quo (formerly OpenPhone)
Pros: Strong AI features (call summaries, transcripts, the Sona agent) baked into every tier; native HubSpot/Salesforce integrations starting at Business; shared numbers with unlimited paid users on Business and up.
Cons: Most expensive starting price of the three by a wide margin; automatic call recording isn’t available until the Business tier; AI “Sona” automation runs on a separate credit system that can add real cost beyond the base per-user price.
Grasshopper
Pros: Cheapest starting price of the dedicated business-phone tools; built to layer on top of an existing personal number, so there’s no need to switch devices or carriers; AI voicemail sentiment included even at the entry tier.
Cons: Entry-level True Solo plan excludes auto-attendant, call recording, and simultaneous call handling — all common small-business needs; limited to 1 user until Solo Plus; extra phone numbers and extensions each carry separate add-on fees.
Who It’s a Good Fit For
Google Voice — true solopreneurs who just need one separate US number for free, or Google Workspace shops that want the cheapest possible paid tier for a small team.
Quo — small teams that want shared lines, CRM integrations, and AI-assisted call handling, and are willing to pay a premium for it.
Grasshopper — solo founders and small service businesses that want a professional-sounding virtual phone system without giving up their existing personal number or device.
Who Should Look Elsewhere
International-first businesses should scrutinize Google Voice’s international calling rates and Quo/Grasshopper’s US/Canada-centric calling before assuming either covers global calling needs out of the box.
Teams needing call recording or an auto-attendant from day one should skip Grasshopper’s entry-level True Solo plan and budget for Solo Plus instead.
Cost-sensitive small teams unwilling to pay $19+/user/month should compare Quo against Google Voice for Business’s $10–$20/user range before assuming AI features are worth the premium.
Bottom Line
For a true solo operator on a tight budget, free personal Google Voice is hard to beat, with Grasshopper as the natural paid upgrade once you need auto-attendants or multiple extensions without switching numbers. For small teams that want shared lines, built-in AI call handling, and CRM integrations, Quo (the company formerly known as OpenPhone) is the more capable — and more expensive — option. Google Voice for Business sits in between on price but requires an existing Workspace subscription to access, which is easy to overlook when comparing headline per-user prices.
FAQ
Is OpenPhone still a separate product from Quo?
No. OpenPhone rebranded to Quo; the company is the same (its site footer still reads “OpenPhone Technologies, Inc.”), and pricing, sign-up, and support all now run through quo.com rather than openphone.com.
Is personal Google Voice really free, or is there a hidden catch?
Google’s own support documentation states that almost all Google Voice calls to the US and Canada from within the US are free. International calls are billed at Google’s published international rates, and the free personal product is distinct from the paid Google Voice for Business (Workspace) tier.
Which of these three offers a free trial?
Both Quo and Grasshopper offer 7-day free trials with no credit card required. Google Voice doesn’t need a trial in the traditional sense for personal use since that tier is free; the business tier runs through standard Google Workspace trial terms.
Does Grasshopper require switching to a new phone or carrier?
No — Grasshopper is designed to forward calls from a dedicated business number to whatever phone or phones you already use, which is part of why it’s popular with solopreneurs who don’t want to carry a second device.
Which option is cheapest for a 3-person team?
Based on published pricing, Google Voice for Business Starter ($10/user/month annual, where available) is the cheapest per-user rate of the three for a small team, followed by Grasshopper’s Solo Plus (flat $25/month annual for unlimited users on one number), with Quo’s Starter ($15/user/month annual) the most expensive per-seat option.
Employee monitoring software sits at the uncomfortable intersection of productivity measurement and workplace trust. For remote and hybrid teams, three names come up constantly: Hubstaff, Time Doctor, and ActivTrak. All three track activity and produce reports, but they differ sharply in philosophy, pricing structure, and how much of the “surveillance” versus “insights” dial they lean on. We pulled current pricing directly from each vendor’s own site (and, for Hubstaff, its own published review page where the live pricing widget didn’t render in our fetch) as of November 2026.
At a Glance
Tool
Starting Price
Free Plan
Best For
Hubstaff
From $4.99/seat/month (annual), 2-seat minimum on most tiers
Yes — limited to 1 user
Time tracking with optional activity levels and payroll, for agencies and project-based teams
Time Doctor
From $6.67/user/month (annual)
No free plan; 14-day free trial of Premium features
Granular attendance, payroll, and productivity rating tools for larger distributed teams
ActivTrak
From $7/worker/month (annual, requires 3-year term)
Yes — limited to 3 workers
Workforce analytics and productivity benchmarking rather than raw time-clock tracking
Short Verdict
Hubstaff is the most affordable entry point and the most familiar “time tracker with screenshots” format, scaling cleanly from freelancer teams up through Enterprise-grade SSO and compliance. Time Doctor leans harder into attendance, payroll integration, and granular productivity ratings, with the most detailed à la carte add-on menu of the three — useful if you want to pay only for what you use, tedious if you want one simple number. ActivTrak is the odd one out: it’s priced and positioned around workforce analytics and benchmarking rather than a literal time clock, and its cheapest tier requires a 3-year commitment to hit the advertised $7/worker/month rate.
What These Tools Actually Do
All three products track how remote or hybrid employees spend their working hours — through a desktop/mobile app (Hubstaff, Time Doctor) or a lighter background agent (ActivTrak) — and turn that activity into dashboards for managers. Common features across the category include time tracking, app and website usage logs, idle-time detection, and screenshots or activity scores. Where they diverge is emphasis: Hubstaff and Time Doctor both still frame themselves primarily as time-tracking-plus-payroll tools that happen to include monitoring features, while ActivTrak explicitly markets itself around “workforce analytics,” productivity benchmarking, and (on its priciest tier) AI-driven workflow insights rather than attendance and payroll.
One honest caveat about this research: Hubstaff’s live pricing page renders its plan cards through a JavaScript widget that didn’t return plan-by-plan detail to our fetch tool. We cross-checked the numbers below against Hubstaff’s own published review article on its own domain, where the same figures appear in a static table, and they match the example used in Hubstaff’s pricing FAQ ($10/seat/month for the “Team” plan, annual). We’re comfortable calling these figures verified from a primary source, but if you’re pricing out a large deployment, double-check hubstaff.com/pricing directly since seat minimums and promotional pricing can shift.
Pricing Breakdown
Plan
Annual price
Monthly price
Key inclusions
Hubstaff Starter
$4.99/seat/mo
$7/seat/mo
Basic time tracking, timesheets, activity levels (2-seat minimum)
ActivTrak bills annually only — the company states plainly that it currently offers no monthly billing option. It also layers on add-ons: an AI Insights module costs an extra $4/worker/month on the Workforce Management or Productivity Optimization tiers, and extending activity-data history beyond the included window costs $1/worker/month. Time Doctor’s add-on menu is even longer, with items like Benchmarks AI, Video Screen Recording, and Meeting Insights each priced separately at $2–$3/user/month, plus flat per-account charges of $200/month for things like SSO or native payroll integrations.
Pros and Cons
Hubstaff
Pros: Cheapest entry point of the three; clean four-tier structure that’s easy to reason about; 14-day free trial with no credit card; free single-user plan exists for very small shops.
Cons: 2-seat minimum on Starter through Team means solo users pay for a seat they may not use; unlimited screenshots only arrive at the Team tier; Enterprise jumps sharply to $25/seat and is annual-only.
Time Doctor
Pros: Very detailed feature breakdown by tier, so you can see exactly what you’re paying for; generous 14-day trial that defaults to full Premium features; strong attendance/payroll tooling on Standard and up.
Cons: No free-forever plan; the long list of $2–$3/user add-ons and $200/month flat fees (SSO, provisioning, HRIS/payroll integrations) can make the “real” price meaningfully higher than the headline Premium rate.
ActivTrak
Pros: Genuine free plan (3 workers) with no time limit mentioned other than an inactivity rule; strongest workforce-analytics and benchmarking depth of the three; bundling Workforce Management + Productivity Optimization gets a 30% discount.
Cons: The advertised $7/worker/month entry price requires a 3-year commitment — shorter terms will cost more, though ActivTrak doesn’t publish the exact 1- or 2-year rate; annual billing only, no monthly option at all; accounts over 50 seats require paid “Premier” or “Signature” support at an unlisted price.
Who It’s a Good Fit For
Hubstaff — agencies, freelance teams, and project-based businesses that want simple time tracking plus payroll without a lot of extra complexity.
Time Doctor — mid-size distributed teams that want granular attendance, leave, and payroll features and don’t mind assembling a custom add-on stack.
ActivTrak — operations and transformation teams that care more about productivity trends, benchmarking, and workflow insight than about a literal punch clock.
Who Should Look Elsewhere
Teams with privacy concerns about screenshots and keystroke-level monitoring should review each vendor’s data-retention and consent features carefully before rolling out any of these tools company-wide.
Very small teams (1–2 people) may find Hubstaff’s 2-seat minimum or ActivTrak’s inactivity-deletion policy on its free plan impractical.
Budget-conscious teams unwilling to commit to a 3-year contract should expect to pay more than ActivTrak’s headline $7/worker/month rate.
Bottom Line
There’s no single “best” here — the three tools are aimed at subtly different jobs. If you want straightforward time tracking with payroll bolted on, Hubstaff’s pricing is the simplest to plan around. If you need deep attendance and leave management and don’t mind assembling add-ons, Time Doctor’s Standard or Premium tiers deliver the most granular controls. If your real goal is understanding productivity trends and capacity planning rather than clocking hours, ActivTrak’s analytics-first approach — and its generous free 3-seat plan for testing it out — is worth evaluating first.
FAQ
Which of these three has a genuinely free plan?
Hubstaff and ActivTrak both publish free tiers (1 user and 3 workers respectively). Time Doctor does not offer a free-forever plan, only a 14-day free trial of its Premium tier.
Do any of these charge per active user, or always per total seat?
All three are billed per seat/worker/user rather than by usage. Unlike some async-standup tools that bill only active participants, Hubstaff, Time Doctor, and ActivTrak all charge for every licensed member added to the account.
Why does ActivTrak’s cheapest plan say “starting as low as $7”?
ActivTrak’s own pricing page marks that $7/worker/month figure with an asterisk tied to a 3-year subscription term. Shorter commitments will cost more, though the exact 1- or 2-year price isn’t published — you’d need to contact ActivTrak sales for that quote.
Is Time Doctor’s free trial limited in features?
No — Time Doctor’s 14-day trial gives full access to Premium-tier features with no credit card required. After the trial, you choose to subscribe to Premium or downgrade to a lower tier.
Can I get volume discounts on any of these?
ActivTrak explicitly offers multi-year contracts and volume discounts along with custom Enterprise pricing. Time Doctor and Hubstaff both route custom/volume pricing conversations through their respective Enterprise tiers.
Interview scheduling sounds like a small problem until a talent acquisition team is coordinating five-person panel interviews across three time zones, dozens of roles, and an ATS that doesn’t talk to anyone’s calendar automatically. GoodTime, Calendly, and Paradox all get pulled into this conversation, but they’re not really three versions of the same tool — they occupy three different points on the spectrum from general-purpose scheduling to full conversational-AI recruiting. We checked each vendor’s current site directly before writing this, since Paradox in particular has repositioned its product more than once.
At a Glance
Tool
What It Actually Is (2026)
Scheduling Scope
Entry Pricing
GoodTime
Enterprise AI recruiting/coordination platform built around an AI agent (“Cori”)
Single-day, multi-day, and panel interview scheduling, plus screening, messaging, and interview analytics
Not published — quoted by annual candidate volume
Calendly
General-purpose scheduling platform with a “Recruiting” team solution, not an HR-specific product
1:1 and round-robin team scheduling; no dedicated panel-interview or ATS-native workflow
Free tier available; Standard $10/seat/mo, Teams $16/seat/mo
Paradox
Conversational hiring platform built around an AI assistant (“Olivia”); now also sells its own “Conversational ATS”
Chat/text-based scheduling where candidates pick slots, as one feature within a broader conversational recruiting suite
Not published — demo/contact sales only
Short Verdict
These three aren’t direct substitutes. Calendly is the lightweight, transparently-priced generalist — fine for recruiting teams with simple scheduling needs, but it isn’t built as recruiting software. GoodTime is the purpose-built enterprise coordination layer for high-volume, complex interview logistics (panels, multi-day loops, interviewer load-balancing) that plugs into an existing ATS. Paradox has moved furthest from “just a scheduling tool”: it’s now a full conversational hiring platform, including its own ATS, with interview scheduling as just one of several automated candidate-facing workflows. If you genuinely just need scheduling, don’t assume you need all three categories.
What Each Tool Actually Is
GoodTime markets itself as AI recruiting software for enterprise talent teams, centered on interview scheduling and hiring coordination rather than full applicant tracking. Its current site describes an AI agent, Cori, that handles coordination tasks — scheduling, conflict resolution, interviewer follow-up — with limited prompting from a recruiter. Beyond scheduling (single-day, multi-day, and panel interviews), GoodTime’s own product page lists AI applicant screening, SMS/WhatsApp candidate messaging, a branded self-scheduling portal, an interviewer portal with AI-assisted scorecards, an AI notetaker that transcribes and summarizes interviews, and hiring analytics with bottleneck detection. It syncs two-way with major ATS platforms (Workday, SAP SuccessFactors, iCIMS, Greenhouse, SmartRecruiters, Lever, Jobvite, Ashby). GoodTime’s pricing page states pricing is based on annual candidate volume rather than seat count, with all integrations included — but gives no actual numbers; you have to request a quote.
Calendly is not recruiting software — it’s a general scheduling platform that lists “Recruiting” as one of several team use cases, alongside sales and customer success. Calendly’s own pricing page is fully public: a permanently free tier (one event type, one calendar, 1:1 scheduling only), a Standard tier at $10/seat/month, a Teams tier at $16/seat/month (round-robin and team scheduling, lead routing, centrally managed event types, Salesforce meeting sync), and an Enterprise tier starting at $15,000/year for a minimum of 50 seats (SAML SSO, audit logs, a data-deletion API, dedicated account support). Calendly’s pricing page does not describe recruiting-specific workflows like panel coordination or ATS-native sync in any detail — it’s a flexible scheduling layer that recruiting teams can bolt onto their process, not a purpose-built recruiting coordination tool.
Paradox has repositioned significantly since its earlier “recruiting chatbot” branding. Its current site still centers on Olivia, its conversational AI assistant, but Paradox now sells a full suite: a “Conversational ATS” (marketed as “the ATS that automates, not frustrates”), a standalone “Candidate Experience Agent” that layers onto a company’s existing ATS rather than replacing it, Career Site Studio, and separate conversational modules for Apply, Scheduling, Events, CRM, Onboarding, and Surveys. Within that suite, interview scheduling is presented as one capability — candidates pick an open slot through chat or text — rather than the product’s primary identity. Paradox’s site cites vendor-reported outcomes for named customers (for example, a claimed 54% drop in cost-per-hire for Neighborly and a claimed 58% reduction in time-to-apply for Tractor Supply), which, like the RPA ROI claims discussed elsewhere on this site, are the company’s own case-study figures rather than independently audited results. Paradox publishes no pricing; the only calls to action on its site are “Request demo” and “Log in.”
Pricing Breakdown
Vendor
Pricing Model
What’s Public
GoodTime
Quoted by annual candidate volume
Nothing numeric — “Request GoodTime pricing” is the only path
Calendly
Per-seat tiers, billed monthly or annually
Free / $10 (Standard) / $16 (Teams) per seat/month; Enterprise from $15,000/year, 50-seat minimum
Paradox
Custom quote
Nothing — demo and sales contact only
Calendly is the only one of the three with a transparent, self-serve rate card. GoodTime and Paradox are both enterprise-sales-motion products where price depends on scale (candidate volume for GoodTime; likely employee/hire volume and module mix for Paradox), so budgeting for either requires a sales conversation before you can model total cost.
Pros and Cons
GoodTime
Pros: Purpose-built for complex, high-volume interview logistics; AI agent (Cori) specifically targets the coordination grunt work recruiters hate; strong ATS integration list; security certifications (SOC 2 Type II, ISO 42001) relevant to enterprise procurement.
Cons: No public pricing at all; candidate-volume-based pricing can be hard to predict for teams with seasonal hiring spikes; overkill for small teams with simple scheduling needs.
Calendly
Pros: Transparent, low-cost, self-serve pricing with a genuine free tier; fast to set up; familiar to most candidates and interviewers already.
Cons: Not built for recruiting specifically — no native panel-interview workflow, no ATS-native candidate pipeline, and no recruiting-specific analytics; “Recruiting” is just one listed use case among many, not a dedicated product.
Paradox
Pros: Broadest end-to-end conversational candidate experience (apply, screen, schedule, onboard) in one suite; multilingual support (100+ languages per its site); now offers a full ATS option for teams that want to consolidate rather than bolt on.
Cons: No public pricing; its scope has grown well beyond “scheduling,” so teams that only want a scheduling tool may be buying (and paying for) far more platform than they need; vendor-cited outcome numbers (cost-per-hire reduction, time-to-apply reduction) are unaudited marketing claims, not independently verified results.
Who It’s a Good Fit For
GoodTime: Enterprise talent acquisition teams running high-volume panel/multi-day interview loops who need deep two-way ATS sync and want AI handling scheduling logistics specifically.
Calendly: Smaller teams or recruiters who need simple, cheap, reliable scheduling and don’t need deep ATS-native workflows or candidate messaging automation.
Paradox: Organizations (especially high-volume, high-turnover hiring like retail, hospitality, or healthcare) that want an end-to-end conversational candidate experience, potentially replacing their ATS rather than just adding scheduling.
Who Should Look Elsewhere
Teams wanting a hard, comparable price upfront should lean toward Calendly; GoodTime and Paradox both require a sales conversation before you’ll see a number.
If all you need is “let a candidate pick a time,” Paradox’s full conversational suite and GoodTime’s enterprise coordination platform are both likely more tool (and cost) than the problem requires.
If you need recruiting-specific analytics, ATS-native candidate workflows, or panel-interview coordination, Calendly alone won’t cover it — budget for GoodTime, Paradox, or a dedicated module in your existing ATS instead.
Bottom Line
GoodTime, Calendly, and Paradox are frequently compared but aren’t really competing for the same budget line. Calendly is a transparent, affordable generalist that happens to work fine for simple recruiting scheduling. GoodTime is the specialist for enterprise interview-coordination complexity. Paradox has evolved into the broadest player of the three — now a full conversational hiring platform with its own ATS option — so evaluating it purely as a “scheduling tool” undersells (and potentially overpays for) what it’s actually selling. Match the tool to how complex your interview logistics really are, not to which name shows up most often in a vendor comparison list.
FAQ
Is Paradox still just a recruiting chatbot? No. Paradox’s current site centers on its Olivia AI assistant but has expanded into a broader “Conversational ATS” plus separate modules for apply, scheduling, events, CRM, onboarding, and surveys — a materially broader platform than the “chatbot” branding it’s sometimes still associated with.
Can Calendly replace a dedicated interview-scheduling tool like GoodTime? For simple 1:1 or round-robin scheduling, yes. For complex multi-day panel interviews with deep two-way ATS sync, interviewer load-balancing, and recruiting-specific analytics, Calendly’s own site doesn’t describe those capabilities — that’s the gap GoodTime is built to fill.
Does GoodTime replace an ATS? No. GoodTime positions itself as syncing with an existing ATS (Workday, Greenhouse, Lever, and others) rather than replacing it — it’s a coordination and scheduling layer, not a system of record for candidates.
Are Paradox’s cited results (like cost-per-hire reductions) independently verified? No. The figures on Paradox’s site are the company’s own case-study claims about named customers, with no independent audit disclosed — the same caveat that applies to most vendor-published ROI and outcome statistics in this software category.
Which of the three has transparent pricing? Only Calendly. GoodTime and Paradox both require a sales conversation, with GoodTime stating it prices by annual candidate volume and Paradox publishing no pricing model at all.
TensorFlow, PyTorch, and JAX all do the same basic job — building and training differentiable numerical computations on GPUs and TPUs — but they got there through very different design decisions, and those decisions still show up in how each framework feels to use. There’s no pricing to compare here; the real differences are governance, programming model, hardware support, and ecosystem maturity. Everything below is drawn from each project’s own documentation or GitHub repository.
At a Glance
Framework
Primary steward
Programming model
Hardware support
Typical use case
Learning curve
TensorFlow
Google
Eager execution by default; tf.function traces an optimized graph for performance/export
CPU, GPU, TPU
Production deployment, mobile/server serving via SavedModel
Moderate — two mental models (eager vs. traced graphs) to learn
PyTorch
PyTorch Foundation (Linux Foundation); originated at Meta
Eager, define-by-run execution
CPU, NVIDIA GPU (CUDA), AMD GPU (ROCm)
Research, rapid prototyping, now also widely used in production
Gentle — code runs the way it reads, line by line
JAX
Open-source project under the jax-ml organization, originated at Google
Functional, NumPy-like API with composable transforms (grad, jit, vmap) compiled via XLA
CPU, NVIDIA GPU, Google TPU; experimental AMD/Apple/Intel GPU support
Research requiring custom autodiff, large-scale training, scientific computing
Steeper — functional style and tracing rules take adjustment
Bottom Line (Short Version)
PyTorch is the easiest to pick up and remains the default choice for most new research and a large share of production work. TensorFlow’s traced-graph model via tf.function still has real advantages for deployment and export when you need a model to run outside Python. JAX asks for more functional-programming discipline up front but rewards you with precise control over compilation and differentiation, which is why it’s become a favorite for large-scale and research-heavy training runs, including much of the work inside Google DeepMind.
How Each Framework’s Programming Model Works
TensorFlow runs eagerly by default — operations execute immediately and return concrete values, so `x + x` behaves like ordinary Python. For performance-critical code, you wrap a function in @tf.function; the first call traces a complete, optimized computation graph, which is reused on later calls unless the input shapes or dtypes change (a new dtype or shape triggers a fresh trace). That traced graph can also be exported via tf.saved_model so a trained model can run on a server or mobile device without a Python runtime at all — a genuine advantage for production deployment.
PyTorch uses a define-by-run (eager) model with no separate tracing step required for basic use: you write ordinary Python, and operations on tensors execute immediately, which is a large part of why it reads so naturally and debugs so easily with standard Python tools.
JAX takes a functional approach: you write plain NumPy-style functions, and JAX’s composable transformations do the heavy lifting. jax.grad differentiates a function automatically, jax.jit compiles it via XLA for speed, and jax.vmap vectorizes it across a batch dimension — and, notably, these transforms compose with each other, so you can JIT-compile a vmapped gradient in one line.
Minimal Code Comparison
A simple example — creating a small tensor/array — shows the flavor of each API, taken directly from each project’s own documentation.
TensorFlow supports GPU acceleration out of the box (checked via tf.config.list_physical_devices('GPU')) and has long-standing first-party TPU support, reflecting Google’s own infrastructure.
PyTorch‘s official install matrix offers CPU-only builds plus CUDA builds (for NVIDIA GPUs, with multiple CUDA versions supported) and ROCm builds (for AMD GPUs) — the ROCm build exposes the same torch.cuda API surface, so code written against CUDA largely works unchanged on AMD hardware.
JAX‘s README lists the widest accelerator matrix of the three: CPU (Linux x86_64/aarch64, Mac aarch64, Windows x86_64, WSL2), NVIDIA GPU (Linux, experimental on WSL2), Google TPU (Linux x86_64), AMD GPU (Linux x86_64, experimental on WSL2), and experimental support for Apple GPU and Intel GPU.
Ecosystem & Governance
TensorFlow is a Google project, documented and distributed through tensorflow.org, with a mature ecosystem around production serving (TF Serving), mobile (TF Lite), and the Keras high-level API. PyTorch originated inside Meta’s AI research division but was transferred to the independent PyTorch Foundation, hosted by the Linux Foundation, with its own governing board and technical advisory council — a deliberate move toward vendor-neutral governance rather than single-company control. JAX is developed in the open under the jax-ml GitHub organization; its own README describes it as a research-oriented project rather than an official product, with closely associated libraries like Flax (neural network layers) and Optax (optimizers) filling in the higher-level tooling that JAX itself deliberately leaves out.
Who Should Pick Which
Pick TensorFlow if your priority is exporting a trained model to run outside Python — on a server, in the browser, or on mobile — and you want first-party TPU support without extra configuration.
Pick PyTorch if you want the gentlest learning curve, the largest base of research code and tutorials to learn from, and you’re training mainly on NVIDIA or AMD GPUs rather than TPUs.
Pick JAX if you need precise, composable control over automatic differentiation and compilation — common in novel research architectures, large-scale distributed training, and scientific computing — and you’re comfortable with a more functional coding style.
Comparison Table
Dimension
TensorFlow
PyTorch
JAX
Execution style
Eager by default; traced graphs via tf.function
Eager / define-by-run
Functional, traced and JIT-compiled via XLA
Autodiff
Built in (tf.GradientTape)
Built in (autograd/torch.autograd)
Built in (jax.grad), composable with jit/vmap
Model export for non-Python serving
Yes — tf.saved_model
Via TorchScript/ExportedProgram tooling
Less standardized; typically exported through XLA/StableHLO tooling
TPU support
First-party, mature
Supported but less central to the ecosystem
First-party, mature (originated at Google)
Governance
Google-led
PyTorch Foundation / Linux Foundation
Open-source, jax-ml organization
Bottom Line
None of these three is simply “better” — they encode different bets about how code should relate to the hardware running it. TensorFlow bets on a traceable, exportable graph for production; PyTorch bets on code that reads and runs like ordinary Python; JAX bets on functional purity and composable transformations for maximum control. Most teams will be well served by starting with PyTorch for research and prototyping, and reaching for TensorFlow or JAX specifically when their deployment or scale requirements call for it.
FAQ
Is TensorFlow still actively developed in 2026? Yes, TensorFlow remains an actively maintained Google project with current documentation on tensorflow.org covering eager execution, tf.function graph tracing, and GPU/TPU acceleration.
Who governs PyTorch now that it’s not purely a Meta project? PyTorch is stewarded by the independent PyTorch Foundation, hosted under the Linux Foundation, with its own governing board and technical advisory council — a deliberate shift toward multi-company, vendor-neutral governance.
Does JAX support AMD or Apple GPUs? Only experimentally — JAX’s official README lists AMD GPU support on Linux x86_64 (and experimentally on WSL2) and Apple GPU support as experimental on Mac aarch64, alongside mature CPU, NVIDIA GPU, and Google TPU support.
Can I run PyTorch code on AMD GPUs the same way I run it on NVIDIA GPUs? Largely yes — PyTorch’s ROCm (AMD) build exposes the same torch.cuda API surface at the Python level, so most CUDA-targeted code runs with little or no change.
What’s the practical difference between jax.jit and TensorFlow’s tf.function? Both trace a function into an optimized, reusable compiled form on first call, but JAX’s tracing is built around functional transformations that compose (you can nest jit, grad, and vmap), while TensorFlow’s tf.function is primarily aimed at turning eager Python/TensorFlow code into an exportable graph.
Scheduling across time zones usually breaks down in one of two ways: either nobody can agree on a meeting time, or everyone’s calendar turns into back-to-back chaos because no one is protecting focus time. Three tools have long been recommended for fixing this — Reclaim.ai, Clockwise, and World Time Buddy — but one critical fact changes this comparison entirely, and we want to say it clearly up front rather than bury it: Clockwise shut down on March 27, 2026. If you’re reading this after that date, Clockwise is no longer an option to sign up for or renew. We’re keeping it in this comparison because so many teams are actively migrating off it right now, and because understanding what it offered (and where to go instead) is exactly what you need if you’re one of them.
At a Glance
Tool
Status / Starting Price
Free Plan
Best For
Reclaim.ai
Active. Free “Lite” plan; paid from $10/seat/month (annual)
Yes — 1 user, limited AI agents and integrations
AI-driven calendar defense (focus time, habits, buffer) plus team scheduling
Clockwise
Discontinued — shut down March 27, 2026. No longer accepting new signups.
N/A — product unavailable
Historical reference only; Reclaim is the vendor-recommended migration path
World Time Buddy
Active. Free, ad-supported; no paid tier found
Yes — fully usable without an account
Quick visual time-zone overlap checks and simple meeting-time planning
Short Verdict
With Clockwise off the table, this is really a two-horse comparison now. Reclaim.ai is the closest thing to a direct successor — it offers AI-driven focus-time protection, habit scheduling, and team meeting coordination, and Reclaim itself has publicly offered a price-match guarantee for teams migrating off Clockwise. World Time Buddy is a completely different kind of tool: a free, no-login-required visual time-zone converter and meeting planner, not a calendar-defense AI. Most distributed teams will want Reclaim for the deeper scheduling automation and World Time Buddy as a free companion for quick “what time is that for them” lookups — the two aren’t really competing for the same job.
What These Tools Actually Do
Reclaim.ai and Clockwise both belonged to a category sometimes called “AI calendar assistants”: they sync with Google or Outlook calendars and automatically carve out focus time, move flexible meetings around fixed ones, add buffer time between back-to-back calls, and help teams find meeting slots that work across time zones without endless “does 3pm work for you?” threads. World Time Buddy is a simpler, older tool: a browser-based world clock and overlapping-hours visualizer that lets you drag a time slider and instantly see what that time looks like in every other city or time zone you’ve added — no calendar sync, no AI, no account required.
Clockwise’s own site confirms the shutdown directly: it tells existing customers that prepaid subscriptions extending past March 27, 2026 will be refunded on a prorated basis, and that the company is trying to avoid any further charges before the shutdown date. The same page points departing customers to Reclaim and references a “100% price match guarantee for migrating team,” though it does not list Reclaim’s actual prices — those come from Reclaim’s own pricing page, covered below.
Pricing Breakdown
Plan
Price
Notes
Reclaim.ai Lite
Free
1-user team; 5 AI agents (Focus Time, Habits, Buffer Time, Smart Meetings, Meeting Quality); 1-week scheduling range; 1 calendar sync; 1 scheduling link; limited integrations (Google Tasks, Slack, Zoom, Google Meet)
Reclaim.ai Starter
$10/seat/month annual, $12/seat/month monthly
Up to 10 seats; 10 AI agents per seat; 8-week scheduling range; 3 calendar syncs; unlimited integrations (Todoist, Asana, ClickUp, Jira, Linear, and more)
Reclaim.ai Business
$15/seat/month annual, $18/seat/month monthly
Up to 100 seats; 100 AI agents per seat; 12-week scheduling range; unlimited calendar syncs; Team OOO calendar; delegated access for assistants/admins
Reclaim.ai Enterprise
$22/seat/month annual; not available monthly
100+ seats; unlimited AI agents; SSO/SCIM; org-chart-aware scheduling intelligence; custom quote available
Clockwise
N/A — discontinued
No new signups; existing prepaid balances past March 27, 2026 refunded prorated
World Time Buddy
Free
No pricing page, premium tier, or paid plan found as of November 2026; appears to be ad-supported
A transparency note on Reclaim.ai’s add-on pricing: the site also lists optional “Attendee User” add-ons for non-seat meeting participants, priced per bundle (for example, 3 attendee users on the Starter plan run $8/month annual or $10/month billed monthly). At the time of our research, Reclaim’s page listed these add-ons as free through July 31 as a launch promotion — confirm current status before budgeting, since promotional pricing like this is exactly the kind of detail that changes without much notice.
Pros and Cons
Reclaim.ai
Pros: Genuinely useful free tier for solo users; scales from 1 to 100+ seats with clear per-tier limits; now the default migration target for displaced Clockwise customers, with a price-match offer; broad task-tool integrations on paid tiers.
Cons: Free plan’s 1-week scheduling range and single calendar sync are quite limited; Enterprise tier has no monthly billing option; as a newly-expanded migration target, expect some growing pains as it absorbs a wave of Clockwise refugees.
Clockwise (historical)
Pros: None currently — the product is discontinued and not accepting new users.
Cons: Shut down entirely as of March 27, 2026; any pricing or feature information from before that date is no longer actionable; existing customers must migrate.
World Time Buddy
Pros: Completely free with no account required; fast, visual way to compare overlapping working hours across multiple cities; works well as a simple meeting-planner widget alongside whatever calendar tool you already use.
Cons: No calendar sync, AI scheduling, or automated meeting booking — it’s a lookup tool, not a scheduling assistant; monetization model and long-term support are less clear than a funded SaaS product with a published pricing page.
Who It’s a Good Fit For
Reclaim.ai — remote teams of any size that want automated focus-time protection and AI-assisted meeting scheduling, and especially former Clockwise customers who need a direct replacement.
World Time Buddy — anyone who just needs a fast, free visual reference for “what time is it for them” across a handful of time zones, with no calendar integration required.
Who Should Look Elsewhere
Anyone still trying to sign up for or renew Clockwise — it’s no longer available, full stop.
Teams wanting calendar-sync automation shouldn’t expect World Time Buddy to provide it; it’s a converter, not an assistant.
Solo users who need more than a 1-week scheduling horizon should budget for Reclaim’s Starter tier rather than relying on the free Lite plan.
Bottom Line
This comparison looks different in November 2026 than it would have a year ago: Clockwise is gone, and Reclaim.ai has effectively absorbed its use case, backed by a price-match offer for migrating teams. If you’re choosing fresh, Reclaim is the clear pick for AI-assisted calendar defense and cross-time-zone meeting scheduling, with a usable free tier for individuals. World Time Buddy remains worth bookmarking as a free, zero-setup companion for quick time-zone math, but it’s solving a narrower problem and isn’t a substitute for Reclaim’s automation.
FAQ
Is Clockwise really shut down, or just being phased out gradually?
Clockwise’s own website states the product became unavailable starting March 27, 2026, with prepaid subscription balances past that date refunded on a prorated basis. It is not a gradual wind-down — new signups are not being accepted.
What should former Clockwise users switch to?
Clockwise’s shutdown page points customers toward Reclaim.ai and references a price-match guarantee for migrating teams. Reclaim’s own pricing — from a free Lite plan up to $22/seat/month for Enterprise (annual) — is the most directly comparable alternative we found.
Does World Time Buddy have a paid or premium version?
We could not find any published pricing page, premium tier, or subscription option on World Time Buddy as of November 2026. It appears to operate as a free, ad-supported tool.
Can I still use Reclaim.ai for free?
Yes. Reclaim’s “Lite” plan is free for a single user and includes five AI scheduling agents, though with a shorter one-week scheduling range and only one calendar sync compared to paid tiers.
Is Reclaim.ai’s Enterprise plan available month-to-month?
No — according to Reclaim’s pricing page, the Enterprise tier ($22/seat/month) is billed annually only; monthly billing is listed as unavailable for that tier.
Annual performance reviews are mostly dead in name only — most mid-size and large employers have shifted to continuous feedback, OKRs, 360 reviews, and manager-effectiveness coaching, usually layered on top of engagement surveys. Lattice, 15Five, and Culture Amp are the three names that come up most often when HR and People teams build a shortlist for this category in 2026. We compared their current pricing, packaging, and feature sets directly from each vendor’s own pricing page.
At a Glance
Tool
Performance Entry Price
Packaging Model
Standout Feature
Public Pricing?
Lattice
$10/seat/mo (Performance) or $13/seat/mo (Foundations bundle)
À la carte products (Performance, Goals & OKRs, Engagement) plus paid add-ons
Talent Reviews, Calibration, and Succession Planning built into the base Performance product
Yes — base tiers and add-ons listed; Enterprise is custom
15Five
$11/seat/mo (Perform)
Three bundles (Engage, Perform, Total Platform) plus separate manager-coaching add-ons
AI-driven Manager Effectiveness Index and AI-assisted reviews (AMAYA)
Yes — all core tiers and add-ons listed, updated Feb. 2026
Culture Amp
Not published
Modular products (Engage, Perform) plus People Science Consulting, priced by headcount and service tier
Built-in “People Science” consulting and I/O-psychology backed survey design
No — priced by employee count/tier, quote-based
Short Verdict
Lattice and 15Five both publish real per-seat pricing, which makes early budgeting much easier — Lattice is more modular (buy just Goals & OKRs, or just Engagement, if that’s all you need), while 15Five bundles its products into three tiers and leans harder into AI-assisted manager coaching. Culture Amp is the odd one out: no public pricing of any kind, with cost driven by employee count, product mix, and service tier — a sign that it’s positioned, and typically priced, toward larger or more complex deployments, often alongside a dedicated People Scientist.
What Each Tool Is
Lattice sells performance management, goal-tracking, and engagement as three separate base products that can be bought individually or combined. Per Lattice’s own pricing page, Performance runs $10 per seat/month and covers performance reviews, succession planning, promotions, performance improvement plans (PIPs), talent reviews, and calibration. Goals & OKRs is $8/seat/month, and Engagement (pulse surveys, onboarding/exit surveys, eNPS) is $4/seat/month. All three include meetings, weekly updates, feedback, Q&A boards, analytics, an AI agent, and integrations. Lattice also sells a “Foundations” bundle at $13/seat/month, described on its own pricing page as the most popular package, and two paid add-ons: Compensation (+$6/seat/month) and Grow, a career-development module (+$4/seat/month). Lattice’s page states there’s a $4,000 minimum annual contract value and no separate implementation fee.
15Five packages its platform into three named tiers rather than à la carte products. Engage ($4/seat/month) is the engagement-survey layer; Perform ($11/seat/month, flagged as 15Five’s most popular tier) is the performance-management core, including 360° reviews, lifecycle reviews, calibrations, weighted OKRs, career paths, a 9-Box Talent Matrix, and a suite of AI tools 15Five brands as AMAYA, plus an “Insights Dashboard” and “Manager Effectiveness Index.” Total Platform ($16/seat/month) combines Engage and Perform and adds an HR dashboard and manager-training microlearning. 15Five also sells manager-focused add-ons separately: a $49/manager/month on-demand learning library, 1:1 executive coaching at $399 per credit, an AI notetaker (Kona Notetaker) at $2/employee/month, and an AI coach (Kona Coach) at $19/manager/month, plus compensation modules at $9–$11/user/month. 15Five’s page notes this pricing was last updated February 2026 and is subject to change.
Culture Amp is built around two core products — Engage (employee surveys) and Perform (performance management, coaching, development) — both of which now include an “AI Coach” feature, plus an optional “People Science Consulting” add-on for organizations that want direct access to Culture Amp’s in-house I/O psychologists. Rather than publishing per-seat prices, Culture Amp’s pricing page states cost depends on employee count, which products you choose, and a service tier based on company size: a lighter-touch tier for companies under 200 employees, a tier with a dedicated Customer Success partner for 200–999 employees, and a full Enterprise tier (1,000+ employees) that adds manager/executive training and People Scientist-led results calls. Every plan, per the page, includes 1-on-1 meeting templates, SSO, HRIS integrations, Slack/Teams integrations, and SOC 2/GDPR compliance.
Pricing Breakdown
Vendor
Tier
Price (per seat/month, annual billing)
Notes
Lattice
Engagement
$4
Can be bought standalone
Lattice
Goals & OKRs
$8
Can be bought standalone
Lattice
Performance
$10
Can be bought standalone
Lattice
Foundations (bundle)
$13
Most popular package per Lattice
Lattice
Enterprise
Custom quote
Based on seats, complexity, scale
15Five
Engage
$4
Engagement surveys
15Five
Perform
$11
Most popular tier per 15Five
15Five
Total Platform
$16
Engage + Perform + HR dashboard
Culture Amp
All tiers
Not published
Quote-based on headcount, products, service tier
Pros and Cons
Lattice
Pros: Transparent, modular, published pricing; can buy only the piece you need (e.g., just Goals & OKRs); strong native succession-planning and calibration tools in the base Performance product.
Cons: Add-ons (Compensation, Grow) stack up quickly on top of base pricing; the $4,000 annual minimum may be a consideration for very small teams; the page’s layout makes the Foundations bundle’s full inclusions less clear at a glance.
15Five
Pros: Heavy investment in AI-assisted manager tools (AMAYA, Manager Effectiveness Index, Kona Coach); clear three-tier structure that’s easy to compare; frequent, dated pricing updates suggest active maintenance of the pricing page.
Cons: Manager coaching and notetaking are separately priced add-ons, not included even in Total Platform; per-credit coaching pricing ($399) can get expensive for organizations that want coaching widely available rather than occasional.
Culture Amp
Pros: People Science Consulting gives direct access to I/O psychologists for survey design and action planning — a differentiator Lattice and 15Five don’t market in the same way; service tiers scale support level with company size.
Cons: Zero public pricing, even an indicative range, makes early-stage budgeting harder; smaller teams may find the People Science positioning (and likely price point) oriented more toward larger organizations.
Who It’s a Good Fit For
Lattice: Teams that want to buy only specific modules (e.g., OKRs now, performance reviews later) and want pricing they can model without a sales call.
15Five: Organizations prioritizing manager effectiveness and willing to pay for AI-driven coaching and notetaking as discrete add-ons.
Culture Amp: Larger organizations (roughly 200+ employees, based on its own service tiers) that want survey design and people-analytics expertise bundled in, not just software.
Who Should Look Elsewhere
Very small teams on a tight, fixed budget may find Lattice’s $4,000 annual minimum or 15Five’s add-on-heavy model adds up faster than expected relative to a lighter standalone tool.
Organizations that need a hard price before they can get budget sign-off should treat Culture Amp’s quote-only model as a planning constraint, not just a formality.
Teams that only need lightweight pulse surveys, with no performance-review or OKR component, may be better served by a narrower engagement-only tool than any of these three full platforms.
Bottom Line
Lattice and 15Five both make their pricing public and modular enough to model a realistic budget before talking to sales — Lattice by selling individual products, 15Five by bundling into three clear tiers with optional AI-coaching add-ons. Culture Amp keeps pricing entirely behind a quote, which tracks with its positioning as a more consultative, People Science-backed platform aimed at organizations that want expert support alongside the software itself. For most mid-market buyers, start with Lattice or 15Five’s published pricing to build an initial business case, and bring Culture Amp into the conversation specifically if survey design expertise and people-analytics consulting are a priority, not just the performance-management workflow.
FAQ
Can I buy Lattice’s Goals & OKRs without buying Performance? Yes — Lattice’s pricing page lists Performance, Goals & OKRs, and Engagement as separate base products that can be purchased independently or combined.
Does 15Five’s Total Platform include manager coaching? No. Per 15Five’s pricing page, 1:1 executive coaching, the Manager Products learning library, Kona Notetaker, and Kona Coach are all priced as separate add-ons on top of any of the three core tiers, including Total Platform.
Why doesn’t Culture Amp publish prices? Culture Amp’s own pricing page states cost depends on employee count, which products (Engage, Perform, People Science Consulting) are selected, and a service tier tied to company size — variables the company appears to prefer quoting individually rather than standardizing into a public rate card.
Is there a free tier for any of these three? No. None of the three vendors’ pricing pages list a free tier; all require a paid subscription, and Lattice additionally specifies a $4,000 minimum annual contract.
Content moderation APIs usually get compared as if they’ll all still be around next year. One of the three tools in this comparison won’t be — and that single fact should shape the decision more than any feature checklist. Here’s what OpenAI’s Moderation API, Google’s Perspective API, and Microsoft’s Azure AI Content Safety actually offer and cost, straight from each vendor’s own documentation, including the retirement notice that changes the calculus for anyone currently relying on Perspective.
At a Glance
API
Cost
Modalities
Status
Best for
OpenAI Moderation API
Free
Text and images
Active
Filtering OpenAI-adjacent text/image content for policy violations
Google Perspective API
Free
Text (toxicity-style scoring)
Shutting down — no service after Dec 31, 2026
Legacy comment-toxicity scoring only; not for new projects
Azure AI Content Safety
Free tier (F0) + paid Standard tier
Text and images, plus prompt/groundedness checks
Active
Enterprise content safety needing text + image + generative-AI-specific protections
Short Verdict
The single most important fact in this comparison: Google has announced it is sunsetting Perspective API, with the service going offline after December 31, 2026, and new or increased-quota API access requests accepted only through February 2026. Anyone building new moderation infrastructure in late 2026 should not plan around Perspective at all. That leaves a real two-way decision between OpenAI’s free, text-and-image Moderation API (ideal if you’re already using OpenAI models) and Microsoft’s Azure AI Content Safety, which is the only one of the three built with explicit generative-AI-era features like prompt injection shielding and groundedness detection, sold through a metered paid tier above a modest free allowance.
What Each One Is
OpenAI’s Moderation API is a free classification endpoint, currently built on the omni-moderation-latest model, that scores text and images against 13 categories including harassment, hate, self-harm, sexual content, and violence (several sub-categories are text-only; image inputs are scored only against the categories that support images). A separate, access-controlled CSAM Image Classifier handles child-sexual-abuse-material detection outside the standard moderation flow.
Google’s Perspective API, built by Google’s Jigsaw team, scores text for attributes associated with toxicity and is widely used by publishers and comment-section moderation tools. It has been free throughout its life — and Google’s own retirement notice confirms it will stay free until it’s switched off entirely at the end of 2026.
Azure AI Content Safety is Microsoft’s content-moderation service inside Azure AI, covering text and image moderation plus features aimed specifically at generative AI risks: Prompt Shields (detecting prompt-injection attempts), Protected Material Detection, and Groundedness Detection (checking whether a model’s output is actually supported by its source material).
Pricing Breakdown
OpenAI Moderation API
Perspective API
Azure AI Content Safety
Base cost
Free — “the moderation endpoint is free to use,” per OpenAI’s own docs
Free — described as “a free developer tool” on its own site
Free tier (F0): 5,000 text records/month and 5,000 images/month, then usage stops at the limit
Paid tier
Not applicable — no paid tier exists
Not applicable
Standard tier: priced per 1,000 text records and per 1,000 images (exact published rate not reproduced here — confirm current figures on Azure’s pricing calculator, as Microsoft’s page did not render dollar amounts in our fetch)
Rate limits
Not published on the main moderation guide; check OpenAI’s general rate-limits documentation
Governed by a quota system; new or increased quota requests accepted only through February 2026
Governed by the Standard tier’s commitment options, up to 720M text records/year and 180M images/year on disconnected-container commitment tiers
Availability after 2026
Ongoing, no end date announced
Fully shuts down December 31, 2026
Ongoing, no end date announced
Each text record in Azure’s pricing model covers up to 1,000 Unicode characters, so a 7,500-character input is billed as 8 records. Prompt Shields and Groundedness Detection appear to bill at the same per-1,000-text-record Standard rate rather than as separate line items, based on how Microsoft’s pricing page groups them.
Pros
OpenAI Moderation API: Completely free with no usage tier to manage; covers both text and images in one call; actively maintained alongside OpenAI’s other models.
Perspective API: Free and simple, if you can tolerate building on a service with a published shutdown date.
Azure AI Content Safety: Purpose-built generative-AI protections (prompt injection, groundedness) that neither competitor offers; usable free tier for low-volume testing; scales to very high enterprise volumes with commitment pricing.
Cons
OpenAI Moderation API: No support for audio moderation; being free and unpaid also means no SLA to point to if you need contractual guarantees.
Perspective API: Being retired entirely — not a viable choice for any new project, and existing integrations need a migration plan before December 31, 2026.
Azure AI Content Safety: Free tier is modest (5,000 records/images per month) before paid billing kicks in; requires an Azure account and subscription setup, adding more operational overhead than the two free competitors.
Who It’s a Good Fit For
Choose OpenAI’s Moderation API if you’re already building on OpenAI’s models and want a free, zero-setup safety net for text and image content. Choose Azure AI Content Safety if you need enterprise-grade volume, an SLA-backed paid tier, or specifically need prompt-injection and groundedness protections for a generative AI product. Do not choose Perspective API for anything new — if you’re already using it, start migrating now.
Who Should Look Elsewhere
Anyone needing audio moderation should look beyond all three — none of them moderates audio directly in the APIs covered here. Teams wanting a single free tier with no cloud account setup at all should lean toward OpenAI over Azure, since Azure requires a full Azure subscription even for free-tier use.
Bottom Line
This comparison effectively collapses to two live options once Perspective API’s confirmed shutdown is factored in. OpenAI’s Moderation API wins on simplicity and cost (free, no tier management); Azure AI Content Safety wins on depth, generative-AI-specific protections, and enterprise scalability, at the cost of needing an Azure subscription and a paid tier past a small free allowance.
FAQ
Is Google really shutting down Perspective API? Yes — Google’s own Perspective API site states it is sunsetting the service, that it will no longer be in service after 2026, that the service stays active through December 31, 2026, and that new or increased quota requests are accepted only through February 2026.
What should I migrate to if I currently use Perspective API? Google’s own notice doesn’t name a direct successor — it only says tools “inspired by Perspective’s capabilities” exist elsewhere — so evaluate OpenAI’s Moderation API or Azure AI Content Safety based on whether you need image moderation and generative-AI-specific protections.
Does OpenAI’s Moderation API cost anything? No — OpenAI’s own documentation states the moderation endpoint is free to use, with no paid tier.
What is Azure’s free tier limit for Content Safety? The F0 free tier covers 5,000 text records and 5,000 images per month; usage stops once that limit is reached rather than rolling into overage billing.
Can any of these three moderate audio content? Not directly through the APIs covered in this article — OpenAI’s moderation model explicitly does not classify audio, and audio isn’t a listed modality for Perspective or the Azure Content Safety features referenced here.
Daily standups are easy in an office and painful across five time zones. That’s the gap async standup and status-update tools are built to close: a short daily or weekly check-in that team members answer on their own schedule, with the results rolled up automatically for everyone else to read. We looked closely at three of the longest-running names in the category — Geekbot, Range, and Status Hero — and verified current pricing and features directly on each vendor’s own site as of November 2026. One important update up front: Status Hero rebranded to Steady in early 2024 and now runs on a usage-credit pricing model rather than a per-seat one, which changes the comparison math more than most “versus” posts let on.
At a Glance
Tool
Starting Price
Free Plan
Best For
Geekbot
Free up to 10 users; paid from $2.50/participant/month (standups, annual billing)
Yes — up to 10 users, unlimited standups/polls
Slack- or Teams-native async standups with minimal setup
Range
Free up to 12 users; Pro from $8/user/month
Yes — up to 12 users, 2 teams
Check-ins combined with goals, meeting agendas, and team culture prompts
Status Hero (now Steady)
From $25/month for 500 usage credits — not priced per seat
No published free tier; trial signup only, terms not listed
Teams that want unlimited users and are comfortable with usage-based billing
Short Verdict
For most small-to-midsize remote teams, Geekbot is still the easiest default: it’s free for up to 10 people, lives inside Slack or Microsoft Teams, and its paid tier bills only active participants rather than every seat in your workspace. Range is the better pick if you want check-ins bundled with lightweight goal-tracking and meeting agendas rather than a pure standup bot, and its free plan is slightly more generous at 12 users. Steady (formerly Status Hero) is the one to evaluate carefully: it has moved away from per-user pricing entirely, charging instead for usage credits that cover check-ins, digests, and integrations, which can be cheaper for large teams with light usage or more expensive for teams that check in constantly — you’ll need to model your own usage against its credit tiers rather than assume a flat per-head cost.
What These Tools Actually Do
Async standup tools send a recurring set of questions (what did you do yesterday, what are you doing today, any blockers) to each team member at a set time, collect the answers, and post a readable summary to a channel or dashboard. The pitch is simple: distributed teams spread across time zones can’t all show up to a 9am stand-up, so the stand-up comes to them instead, on their own clock. All three tools in this comparison also push into adjacent territory — polls, mood tracking, 1:1 agendas, and goal check-ins — but their core product is still the daily or weekly async report.
The rebrand worth flagging: Status Hero relaunched as Steady (runsteady.com) in January 2024 as “Status Hero 2.0,” adding a combined cross-team Daily Digest and Action Items view. The underlying statushero.com login and API have continued to work, so if your team has used Status Hero in the past, you’re likely already on Steady without having noticed a hard cutover.
Pricing Breakdown
Plan
Price
Notes
Geekbot Starter
Free, up to 10 users
Unlimited standups, polls, surveys; full customization; analytics dashboard
Geekbot Basic
$2.50/participant/month (standups) + $0.75/respondent (polls), billed annually. Monthly billing is $3/participant and $1/respondent.
Only active participants are billed, not every workspace member; 30-day free trial
Check-ins, up to 12 meeting agendas, Slack/Teams integration, 30-day check-in history
Range Pro
$8/team member/month
Unlimited teams, history, goals, and meetings; billing is described as month-to-month, with no published annual discount
Range Enterprise
Custom (100+ users recommended)
SSO (Okta/OneLogin), dedicated account manager, custom data export
Steady (Status Hero)
From $25/month for 500 credits, scaling to $1,750/month for 35,000 credits; custom above that
Users are free to add — you pay for usage (check-ins, digests, integrations), not seats; all plans include Slack/Teams integration and SOC 2 Type 2 security
One caveat worth stating plainly: Steady’s pricing page does not list a specific free-trial length or credit allowance for new signups, only a generic “free trial” link. If a published trial allowance matters to your evaluation, confirm it directly with Steady’s sales team before committing.
Pros and Cons
Geekbot
Pros: Generous free tier (10 users); billed by active participant rather than total seats; deep Slack/Teams native integration; AI-assisted report summarization; CSV export and API access on paid plans.
Cons: Polls and standups are billed separately, which can get confusing to forecast; free tier caps out quickly for growing teams; deeper enterprise integrations (Jira, Asana) require the custom-priced Enterprise tier.
Range
Pros: Free plan supports slightly more users (12) than Geekbot’s; combines standups with goal-tracking, meeting agendas, and team-culture prompts (mood sharing, icebreaker questions) in one tool; straightforward flat per-user pricing on Pro.
Cons: No published annual-billing discount on Pro, unusual for the category; private check-ins and unlimited history are locked behind the paid tier; smaller third-party integration ecosystem than Geekbot.
Steady (formerly Status Hero)
Pros: No per-seat charge, so adding team members is free; usage-based model can be cost-effective for large teams with infrequent check-ins; includes AI “agent teammates,” goal tracking, and SOC 2 Type 2 compliance on all plans.
Cons: No clearly published free tier; credit-based pricing is harder to forecast than flat per-seat pricing, especially for teams checking in multiple times a day; the rebrand means some older “Status Hero” reviews and pricing pages found online are now out of date.
Who It’s a Good Fit For
Geekbot — small-to-midsize remote or hybrid teams already living in Slack or Microsoft Teams who want standups and polls without adopting a new standalone app.
Range — teams that want one tool for standups, 1:1 agendas, and lightweight OKR-style goal check-ins, and that can live with per-seat pricing once they outgrow the free 12-user cap.
Steady — larger or fast-growing teams that want to add unlimited users without a per-seat bill increasing every time someone joins, and that are willing to monitor credit usage instead.
Who Should Look Elsewhere
Teams under 10–12 people with simple needs may not need any paid plan at all — both Geekbot’s and Range’s free tiers likely cover you.
Teams that want predictable, flat monthly costs may find Steady’s credit model harder to budget than Geekbot’s or Range’s per-seat pricing.
Teams needing heavy enterprise integrations (Jira, deep SSO, custom security review) out of the box, rather than on a custom-quoted tier, should budget for Enterprise pricing on any of the three.
Bottom Line
All three tools solve the same basic problem well, so the decision mostly comes down to billing model and which adjacent features you want bundled in. Geekbot remains the lowest-friction, lowest-cost starting point for most distributed teams. Range is worth a look if you want check-ins and goals in one product. Steady is the most interesting option for teams that have outgrown per-seat pricing and want to decouple cost from headcount — just model your actual check-in volume against its credit tiers before you commit, since the usage-based structure means your real-world cost won’t be obvious from the pricing page alone.
FAQ
Is Status Hero still a separate product from Steady?
No. Status Hero relaunched as Steady in January 2024. Existing statushero.com logins and API endpoints continue to work, but all new signups, pricing, and feature development happen under the Steady/runsteady.com brand.
Does Geekbot charge for every Slack or Teams member, or only people who answer standups?
Geekbot’s own pricing page states it only charges for active participants in standups (and separately, unique respondents to polls/surveys) — not every member of your workspace.
Can I use any of these tools entirely free?
Geekbot is free for up to 10 users with unlimited standups and polls. Range is free for up to 12 users across 2 teams. Steady does not publish a permanent free tier on its pricing page as of this writing — only a trial signup with unspecified terms.
Which tool is best for a team that’s purely distributed across many time zones?
All three are built for this use case, since async check-ins are the whole point. Geekbot’s and Range’s per-seat pricing is easier to forecast for a known headcount; Steady’s usage-based pricing may suit a very large, time-zone-spread team if their check-in frequency per person is relatively low.
Do any of these replace a project management tool?
No — all three are status-reporting and check-in layers, not task or project trackers. They’re typically used alongside tools like Jira, Asana, or Linear rather than instead of them, and Geekbot and Steady both offer integrations with those platforms.
Every conversation about Nvidia’s dominance in AI eventually lands on the same word: moat. Most of the time, that moat gets described in hardware terms — Blackwell GPUs, NVLink interconnects, Spectrum-X networking. But the deeper, harder-to-cross part of the moat isn’t silicon at all. It’s software: two decades of CUDA libraries, compiler tooling, and framework integrations that make Nvidia GPUs the default target for anything written in PyTorch, TensorFlow, or JAX. AMD’s answer is ROCm, an open-source GPU compute stack that has spent years trying to make AMD hardware a drop-in alternative for the same workloads. This piece is about that software layer specifically — not GPU specs — and every claim below is checked against Nvidia’s and AMD’s own developer documentation rather than secondary commentary.
At a Glance
Nvidia CUDA
AMD ROCm
Maturity
Launched 2006; current CUDA Toolkit at major version 13.x
Launched 2016; current stable release in the ROCm 7.2.x line
License model
Proprietary, Nvidia-controlled
Open-source core stack
Primary hardware target
All CUDA-capable Nvidia GPUs (consumer and data center)
Primarily AMD Instinct data-center GPUs; “select” Radeon consumer cards per AMD’s own wording
PyTorch support
Native, default backend; most code “just works”
Native ROCm backend exists; AMD ships official quarterly Docker images, but with documented operator-level gaps
Porting CUDA code
N/A (native)
HIPIFY tool auto-translates most CUDA source to HIP/ROCm
Supercomputer deployments
Widely used across HPC, incl. Nvidia-based systems
Powers El Capitan, Frontier, and LUMI, per AMD
What CUDA Actually Is
Per Nvidia’s own CUDA Zone developer page, CUDA is described as “the foundation for GPU computing” — a platform that lets developers write accelerated code in C++, Python, or Fortran, or simply use GPU-accelerated libraries and frameworks (PyTorch being the named example) without writing low-level GPU code at all. The CUDA Toolkit bundles the compiler, libraries, and developer tools; on top of that sits “CUDA-X,” Nvidia’s umbrella term for the layer of pre-built, GPU-accelerated libraries spanning AI and HPC domains — things like cuDNN for deep learning primitives and cuDF, which Nvidia says offers drop-in GPU acceleration for pandas, Polars, and Apache Spark with no code changes required. As of late 2026, Nvidia’s CUDA Toolkit download page lists version 13.x as current (Nvidia’s own page shows slightly inconsistent version labeling between 13.3 and 13.5 across metadata, a reminder to always check the download page directly rather than trust a cached number). The practical reality for a developer is that virtually every major AI framework ships CUDA support first, tests against it most thoroughly, and treats it as the reference implementation.
What ROCm Actually Is
AMD describes ROCm, on its own product page, as “open software stack that includes programming models, tools, [and] compilers” for AI and HPC development on AMD GPUs — an open platform for deploying and scaling workloads across GPUs and nodes. AMD names Instinct GPUs as the primary data-center target, while stating plainly that “certain ROCm features support select AMD Radeon graphics cards” — language that itself signals Radeon (consumer-card) support is partial and model-dependent, not universal, in contrast to CUDA’s much broader consumer-GPU reach. On the framework side, AMD lists training and development support for PyTorch, TensorFlow, and JAX, serving/optimization support via vLLM, SGLang, AMD Quark, and AITER, and ecosystem integrations with ONNX, DeepSpeed, Triton, and OpenXLA. AMD also points to real HPC credibility: ROCm is the compute stack behind the El Capitan, Frontier, and LUMI supercomputers. As of late 2026, AMD’s current generally available release line is ROCm 7.2.x (with newer 7.1x and a next-generation “ROCm 10” branded “ROCm.AI” line visible in preview documentation), published on rocm.docs.amd.com.
Where the Real Gap Still Is in 2026
AMD’s own ROCm documentation is unusually candid about the remaining gaps, which is exactly why it’s the right primary source to use here rather than a marketing page. AMD’s ROCm-PyTorch compatibility notes state directly that “ROCm and CUDA are separate platforms, and their tools and APIs are not directly interchangeable” — code depending on CUDA-specific APIs or libraries may need changes. AMD’s HIPIFY tool automates much of that translation for CUDA source code, and PyTorch’s own ROCm backend uses the same tooling so that, in principle, existing PyTorch code runs without manual rewrites. But the documented caveats are specific and real: unsigned integer types beyond uint8 (uint16, uint32, uint64) have limited support in eager mode on ROCm; the reduced-precision FP16/BF16 reduction options available in CUDA’s PyTorch backend aren’t supported on ROCm; torchaudio GPU acceleration requires manually moving tensors to the GPU rather than happening automatically; torchrec has no ROCm-specific kernels; and torchserve is no longer actively maintained on either platform, with its last official release tied to PyTorch 2.4. None of these are fatal, but they are the kind of small, accumulating friction that shows up only once a team tries to run a real production pipeline on ROCm rather than a benchmark script.
Hardware breadth compounds the software gap. CUDA runs on essentially any CUDA-capable Nvidia GPU released in the last decade-plus, consumer cards included, which is a large part of why CUDA became the default teaching and prototyping platform at universities and in open-source projects. ROCm’s own compatibility matrix is narrower and release-specific: AMD’s PyTorch compatibility notes call out architecture-level support differences — for example, hipBLASLt being enabled by default on gfx908 starting with ROCm 6.3, and AOTriton 0.10b offering official support on gfx950 and gfx1201 but only experimental support on several other Radeon architectures (gfx1101, gfx1151, gfx1150, gfx1200). In practice, that means a ROCm deployment’s actual capability depends heavily on which specific GPU and which specific ROCm version you pair it with — a level of version-sensitivity CUDA developers mostly stopped worrying about years ago.
Who Should Care About This Comparison
Platform and MLOps teams choosing infrastructure need to know that “PyTorch supports ROCm” is true but incomplete — it’s true for mainstream training and inference workloads on recent Instinct hardware, and increasingly true for serving via vLLM/SGLang, but teams relying on less-common ops, mixed-precision reduction tricks, or older tooling (torchserve, torchrec) should test thoroughly before committing. Researchers and students porting existing CUDA-based code should budget real time for HIPIFY-assisted translation and validation, not assume a one-command conversion. Procurement and finance teams evaluating AMD Instinct hardware purely on price-per-FLOP need to separately evaluate the software migration cost, which is real but shrinking every ROCm release as AMD closes specific gaps. Hyperscalers and large AI labs are the group with the most leverage to absorb ROCm’s remaining friction in exchange for supply diversification and negotiating power against Nvidia — which is precisely why AMD’s HPC wins (El Capitan, Frontier, LUMI) matter disproportionately as proof points, even though they don’t map directly onto commercial AI training workloads.
Comparison: CUDA vs ROCm by Layer
Layer
CUDA (Nvidia)
ROCm (AMD)
Compiler/toolkit
CUDA Toolkit, proprietary, deeply mature
Open-source compiler and runtime stack
Deep learning libraries
cuDNN, TensorRT, CUDA-X suite
MIOpen and ROCm math libraries, narrower library catalog
Framework integration
Default/reference backend for PyTorch, TensorFlow, JAX
Official but secondary backend; quarterly official Docker images
Data science acceleration
cuDF: drop-in acceleration for pandas/Polars/Spark, per Nvidia
No directly equivalent claim found on AMD’s own pages
Code portability from the other platform
N/A
HIPIFY auto-translates most CUDA source to HIP
Consumer-hardware reach
Broad — most Nvidia GPUs since the mid-2000s
Narrow and version-specific — “select” Radeon cards, per AMD’s own wording
Bottom Line
Nvidia’s software moat in 2026 isn’t about raw GPU performance — it’s about two decades of library depth, framework-default status, and near-universal hardware support that AMD is still closing release by release rather than all at once. ROCm is a genuinely open, genuinely improving stack with real production proof points (PyTorch’s native backend, AMD’s own supercomputer wins, quarterly official container releases), and AMD’s documentation is honest about exactly where the remaining rough edges are — which is itself a sign of a maturing platform rather than a marketing exercise. But “can open GPU software close the gap” has a specific, unglamorous answer right now: not uniformly, not yet, and the gap is measured less in headline benchmark numbers than in the accumulation of small operator-level and hardware-version-specific caveats that AMD’s own docs list openly. Teams evaluating a move should test their actual workload against the current ROCm release rather than relying on either company’s framing.
FAQ
Can I run PyTorch on an AMD GPU without rewriting my code? In most mainstream cases, yes — PyTorch has a native ROCm backend, and AMD’s HIPIFY tooling handles most CUDA-to-HIP translation automatically. But AMD’s own compatibility documentation lists specific operator-level gaps (certain unsigned integer types, reduced-precision reduction modes, some torchaudio and torchrec behavior) that can require code changes depending on what your pipeline actually uses.
Does ROCm work on consumer Radeon GPUs or only data-center Instinct cards? AMD’s own ROCm product page states that “certain ROCm features support select AMD Radeon graphics cards,” which means consumer-card support exists but is partial and architecture-specific — check AMD’s compatibility matrix for your exact GPU and ROCm version before assuming full feature support.
Is ROCm actually open-source? Yes, ROCm’s core stack is open-source, in contrast to CUDA, which remains proprietary and Nvidia-controlled. That openness is central to AMD’s pitch, though it doesn’t by itself guarantee feature parity with CUDA.
What’s the single biggest reason CUDA still dominates? Breadth of library depth (CUDA-X, cuDNN, TensorRT, cuDF) combined with near-universal Nvidia GPU support built up over roughly two decades — every major framework treats CUDA as the reference implementation first, which means it gets the newest features and the most thorough testing before any other backend.
Is this comparison about hardware performance? No — this piece is specifically about the software and developer-ecosystem layer (library support, framework compatibility, driver/documentation maturity, and portability), not GPU silicon specs, which is a separate comparison covered elsewhere.
Walk into any RPA vendor’s resources page and you’ll find a wall of eye-popping numbers: hundreds of percent ROI, millions of dollars saved, payback periods measured in months. Those numbers show up again in sales decks, analyst webinars, and — if we’re honest — in plenty of blog posts that repeat them as settled fact. We pulled the actual case studies behind three of the most commonly cited figures from UiPath, Automation Anywhere, and Microsoft Power Automate, and looked at what’s really being claimed, who calculated it, and how it was verified (or wasn’t).
The short version: every number below is a vendor-sourced or vendor-commissioned claim, not an independently audited result. That doesn’t make them worthless — self-reported customer outcomes are still a useful signal — but they should be read as marketing evidence, not proof of what your organization will achieve.
At a Glance: Vendor ROI Claims vs. Independent Verification
Vendor
Named Case Study
Claimed ROI/Result
Independently Verified?
UiPath
Royal Mail Group (UK postal/logistics)
£55M in value delivered to date; “over 300% above expectations” vs. an original £13.7M target; 662,000 employee hours returned
No. Published by UiPath on uipath.com as a case study; quotes come from Royal Mail staff, but no external auditor or methodology is cited.
Automation Anywhere
Cerner (healthcare IT)
628% ROI; 6-month payback; $130,007 average annual benefit; ~60% developer productivity gain
Partially. Figures originate from a Nucleus Research “ROI Case Study” one-pager (an analyst firm, not Automation Anywhere itself) — but the page discloses no calculation methodology, and the underlying study appears to date back roughly a decade, recycled in current marketing.
Microsoft Power Automate
Composite organization built from interviews at 6 companies (incl. Evri, CoreLogic Asia Pacific, Brisa)
248% ROI, $39.85M NPV, under 6-month payback (3-year, risk-adjusted)
Partially. Conducted by Forrester Consulting, a third party — but the study was commissioned and reviewed by Microsoft, models a hypothetical “composite” company rather than reporting any single real customer’s P&L, and assumes Power Apps is deployed alongside Power Automate.
Short Verdict
None of the three big RPA ROI claims in heaviest circulation — UiPath’s Royal Mail numbers, Automation Anywhere’s Cerner case study, or Microsoft’s Forrester-commissioned Power Automate study — have been independently audited in the way a financial statement is audited. The Forrester study is the most methodologically transparent of the three because Forrester publishes its assumptions and composite-company model, and because Forrester states outright that it “maintains editorial control” even though Microsoft paid for and reviewed the study. The UiPath and Automation Anywhere figures are closer to traditional customer-reference marketing: real customer names, real quotes, but no visible methodology and no third party checking the math.
What’s Actually Being Claimed, Case by Case
UiPath + Royal Mail Group
UiPath’s own case study page on uipath.com, published under UiPath’s byline, credits Royal Mail Group with £55 million in value “delivered with RPA to date,” against an original internal target of £13.7 million — described as “over 300% above expectations.” The £55 million figure is a blend of four very different categories: £4.8 million in employee time saved, £22.4 million in “additional revenue,” £17.5 million in cost reduction/avoidance, and £10.3 million in “capacity creation.” Mixing time savings, cost avoidance, and new revenue into one headline number is a common pattern in RPA marketing, and it’s worth unpacking before treating “£55 million saved” as a literal cash figure — much of it is estimated value, not verified savings on a balance sheet. The quotes in the piece come from named Royal Mail staff (a program lead, a business analyst, and others), which lends it more credibility than an anonymized case study, but there’s no mention of an external audit of the numbers.
Automation Anywhere + Cerner
The “628% ROI” figure attached to Cerner (the healthcare IT company, now part of Oracle Health) traces back to a Nucleus Research ROI Case Study, a short one-page report style Nucleus has produced for many enterprise software vendors over the years, marked in this instance as a past “ROI Award Winner.” It states a 6-month payback, a 1:11.1 cost-benefit ratio, and an average annual benefit of $130,007, attributed to Ben Mitchell, a systems engineer at Cerner Ambulatory. Nucleus Research is an independent analyst firm rather than Automation Anywhere itself, which is a meaningful step up from a vendor writing about its own customer — but the publicly visible excerpt discloses no calculation methodology, and these vendor-commissioned ROI one-pagers are typically paid for by the software company being evaluated. The dated, awards-badge styling of the page also suggests this is an older study still being recirculated in current sales and marketing material rather than a fresh 2026 result.
Microsoft Power Automate (Forrester Total Economic Impact Study)
Microsoft’s most-cited Power Automate ROI figure — 248% ROI with $39.85 million in net present value over three years — comes from a Forrester Consulting “Total Economic Impact” (TEI) study commissioned by Microsoft in 2024. Forrester interviewed representatives at six organizations (Microsoft supplied the customer names and introductions, but Forrester conducted the interviews itself) and built a hypothetical “composite organization” — modeled at 30,000 employees and $10 billion in revenue — to represent the blended financial impact. Forrester is explicit that it “maintains editorial control” of TEI studies even when a vendor pays for them, and the published report states plainly that the benefits assume customers are also running Power Apps alongside Power Automate, and that Forrester “advises readers to use their own estimates within the framework provided” rather than take the composite numbers as a guarantee. That’s a materially more transparent disclosure than either the Royal Mail or Cerner case studies offer — but it’s still a commissioned study, not an independent audit, and the 248% figure describes a modeled composite, not any single real company’s actual results.
Why These Numbers Deserve Skepticism — Without Being Dismissed
Self-selection bias. Vendors choose which customers to feature. A case study is, almost by definition, a success story a company agreed to let the vendor publish — failed or disappointing deployments rarely become case studies.
Blended metrics. “Value delivered” often mixes hard cost savings with soft estimates of “capacity created” or “additional revenue,” which inflates headline totals in ways that are easy to miss on a skim.
Undisclosed methodology. None of the three studies above publish the underlying calculation in enough detail for an outsider to reproduce the number.
Age and reuse. ROI figures — especially from analyst-firm one-pagers like the Nucleus Research reports — can circulate in current sales material for a decade or more after the original study was conducted.
They’re still useful as a prior. A case study that names a real company and a named employee is harder to fully fabricate than an anonymous number, and it does tell you the deployment happened and that the customer was willing to publicly associate their name with a positive outcome.
How to Build Your Own ROI Case Instead of Borrowing a Vendor’s
Run a time-boxed pilot on your own processes and measure before/after cycle time, error rate, and FTE hours directly — don’t extrapolate from someone else’s numbers.
Separate hard savings (headcount, overtime, error-correction cost) from soft/estimated value (capacity “created,” revenue “enabled”) in your own business case, and present them separately to stakeholders.
Ask the vendor directly for the methodology behind any case study or analyst report they cite, including whether the study was vendor-commissioned.
Treat any vendor-supplied ROI calculator (several of which the three vendors above offer on their own sites) as a sales tool, not a financial forecast.
Bottom Line
UiPath’s Royal Mail numbers, Automation Anywhere’s Cerner figures, and Microsoft’s Forrester-commissioned Power Automate study are all real, named, traceable claims — not fabrications — but all three are vendor-sourced or vendor-commissioned, none has been independently audited, and at least one (Cerner/Nucleus) appears to be a much older study still being used in current marketing. Use them as a sanity check that RPA can produce real value in the right circumstances, not as a substitute for measuring your own pilot.
FAQ
Are vendor RPA ROI case studies fake? No — the case studies we reviewed name real customers and real employees. But “real” doesn’t mean “independently verified.” They’re vendor-published or vendor-commissioned marketing content, selected because the outcome was favorable.
What’s the difference between a vendor case study and a Forrester TEI study? A vendor case study is written and published entirely by the software company about its own customer. A Forrester TEI study is commissioned and paid for by the vendor, but conducted and written by Forrester, which states it retains editorial control and discloses its modeling assumptions — a meaningfully more transparent (though still not independent) process.
Why do RPA ROI percentages look so much higher than typical software ROI? RPA case studies often count the fully-loaded cost of human labor hours displaced against a relatively small software and implementation cost, which can produce triple-digit ROI percentages even when the absolute dollar savings are modest for a large enterprise.
Can I ask a vendor for the raw methodology behind a cited ROI number? Yes, and you should. If a vendor or its account team can’t explain how a headline ROI figure was calculated, treat the number as directional marketing rather than something to build a budget justification on.
Document-heavy processes — invoices, claims forms, contracts, ID documents, purchase orders — are one of the biggest remaining drags on automation programs. A plain RPA bot can click buttons and move files, but it can’t reliably read a scanned invoice with a handwritten signature or a contract clause buried on page 14. That’s the job of intelligent document processing (IDP): software that uses OCR, machine learning and (increasingly) generative AI to turn unstructured paper and PDFs into structured data an automation, ERP or case-management system can act on.
Three names dominate enterprise shortlists in 2026: UiPath Document Understanding, ABBYY Vantage, and Automation Anywhere’s document-processing product — still widely searched under its old name, IQ Bot, though Automation Anywhere now markets it as “Document Automation.” We compared what each one actually is, how it’s sold, and who it fits, based on each vendor’s current official product and pricing pages.
All three vendors have converged on the same pitch — OCR plus machine learning plus generative AI, feeding straight into an automation or agent layer — and all three hide their prices behind a sales call. If you’re already committed to one RPA platform, its native IDP product (UiPath Document Understanding or Automation Anywhere’s Document Automation) is the path of least integration friction. If you run a multi-vendor automation estate, or want document processing decoupled from a single RPA vendor’s roadmap, ABBYY Vantage’s platform-agnostic design and large pre-built skill library are worth a serious look.
What Each Tool Actually Is
UiPath Document Understanding lives inside UiPath Automation Cloud rather than as a separate SKU. According to UiPath’s own pricing page, the capability to “classify and extract enterprise data from documents and communications at scale” and combine IDP with automation sits in the Standard and Enterprise Automation Cloud tiers — both of which are quote-based, reachable only through “Contact Sales.” UiPath’s cheaper Basic tier ($25/month, per UiPath’s pricing page) explicitly does not include the document-processing capabilities, and the free Community tier is aimed at individual developers, not production IDP workloads.
ABBYY Vantage is ABBYY’s dedicated intelligent document processing platform, which the company’s own site calls “the industry’s first low-code/no-code platform” for IDP. It’s built to run independently of any one RPA vendor: ABBYY’s product page lists direct connections to Microsoft Power Automate, Blue Prism, UiPath, and Automation Anywhere, plus a REST API for anything else. Vantage ships with pre-trained “skills” for more than 150 document types, a low-code Skill Designer for building custom ones, and a human-in-the-loop review step for low-confidence extractions. It can be deployed as a SOC2-certified cloud service (hosted in Europe, the US, or Australia), on-premises, or as a private cloud instance on Microsoft Azure using Docker/Kubernetes.
Automation Anywhere’s Document Automation is the current name for the product most of the market still calls IQ Bot. Automation Anywhere’s own product page doesn’t mention the old name at all — it’s now positioned as part of the company’s “Agentic Process Automation System.” It extracts data from emails, contracts, invoices, tax forms and other documents (including handwriting, barcodes, QR codes and tables) using a combination of NLP, computer vision, generative AI and what Automation Anywhere calls its “Process Reasoning Engine.” Extracted, validated data is then handed to AI Agents or routed into existing applications via Automation Co-Pilot. The page also claims its Cloud Extraction Service is “up to 5x faster” for large-scale extraction, though it gives no independent benchmark for that figure.
Pricing: None of These Vendors Publish List Prices for IDP
This is worth stating plainly rather than guessing at numbers: UiPath, ABBYY, and Automation Anywhere all keep IDP pricing behind a sales conversation. None of the three official product or pricing pages we reviewed lists a per-document, per-seat, or per-page rate for their document-processing product.
Vendor
Pricing Model (as published)
What’s Public
UiPath
Bundled into Automation Cloud Standard/Enterprise
Only that Basic ($25/mo) excludes document processing; Standard/Enterprise are “Contact Sales”
ABBYY Vantage
Custom quote, likely tied to document/page volume and skills used
Nothing — demo/contact-sales only
Automation Anywhere Document Automation
Custom quote
Nothing — a savings calculator is offered, but no rate card
In practice, IDP deals in this tier are typically priced on a mix of document/page volume, the number of “skills” or document types in production, and whether you’re buying it bundled with a broader automation platform license. Budget for a proof-of-concept or paid pilot before any multi-year commitment, since real-world extraction accuracy on your specific document types — not the vendor’s demo documents — is what determines whether the deal pencils out.
Pros and Cons
UiPath Document Understanding
Pros: Native fit with UiPath’s RPA, orchestration, and (newer) agentic tooling; one vendor relationship and one platform to administer; large existing UiPath partner/integrator ecosystem.
Cons: Locks document processing to the UiPath platform; no standalone pricing or SKU — you’re buying into Automation Cloud’s Standard/Enterprise tier structure; not a fit if your automation estate is multi-vendor.
ABBYY Vantage
Pros: Platform-agnostic by design, with out-of-the-box connectors to the major RPA vendors; large pre-trained skill library (150+ use cases) shortens initial setup; flexible deployment (cloud, on-prem, Azure private cloud).
Cons: No published pricing at all, even a starting range; adds a second vendor relationship on top of whatever RPA or BPM tool you already run; low-code Skill Designer still requires real document-ops expertise to tune for messy real-world documents.
Automation Anywhere Document Automation
Pros: Tight integration with Automation Anywhere’s broader Agentic Process Automation System; generative-AI extraction layered on top of classic computer vision/NLP; strong audit-trail and compliance framing for regulated industries.
Cons: Branding confusion — most buyer research still references “IQ Bot,” which the current site doesn’t even acknowledge; like the other two, pricing is entirely quote-based; the “5x faster” extraction claim is vendor-stated with no cited benchmark.
Who It’s a Good Fit For
Organizations already running UiPath or Automation Anywhere at scale, where native IDP avoids a second integration project.
Finance, insurance, healthcare and logistics teams drowning in semi-structured documents (invoices, claims, bills of lading) that need both OCR accuracy and workflow routing.
Enterprises that can commit to a paid pilot/PoC to validate extraction accuracy on their own documents before signing a multi-year contract.
Who Should Look Elsewhere
Small teams with low document volumes, where a lighter-weight, self-serve OCR/extraction API (rather than an enterprise IDP platform) will be far cheaper.
Buyers who need a hard price before they can get budget approval — none of these three vendors will give you one without a sales call.
Teams expecting near-zero setup effort; all three still require tuning extraction models or skills against real document samples.
Bottom Line
There’s no clear “winner” among UiPath Document Understanding, ABBYY Vantage, and Automation Anywhere’s Document Automation (IQ Bot) in 2026 — the honest answer is that the right choice is mostly determined by what RPA platform, if any, you’ve already committed to. UiPath and Automation Anywhere both want IDP to be a reason to deepen your investment in their broader platform; ABBYY is betting that buyers increasingly want document intelligence decoupled from any single automation vendor. All three will ask you to get on a call before they’ll tell you what it costs, so plan your evaluation timeline — and your PoC budget — accordingly.
FAQ
Is IQ Bot still a product name? Not officially. Automation Anywhere’s current site markets the capability as “Document Automation” within its Agentic Process Automation System, though “IQ Bot” remains the term most commonly used in the market and in older documentation.
Can I use ABBYY Vantage with UiPath or Automation Anywhere instead of their native IDP tools? Yes. ABBYY’s product page lists direct connectors to UiPath, Automation Anywhere, Blue Prism, and Microsoft Power Automate, plus a REST API, specifically so Vantage can serve as a document-processing layer independent of which RPA tool executes the downstream workflow.
Why won’t any of these vendors publish prices? Enterprise IDP pricing typically depends on document volume, the number of distinct document types (“skills”) in production, accuracy/SLA requirements, and bundling with a broader automation license — variables none of the three vendors appear willing to standardize into a public rate card.
Do these tools use generative AI now, or just traditional OCR/ML? All three now blend traditional OCR/computer-vision extraction with generative AI. UiPath and Automation Anywhere both explicitly cite generative AI in their current product descriptions; ABBYY’s Vantage platform uses a mix of pre-trained models, low-code custom skills, and human-in-the-loop review rather than leading with generative AI messaging.
Should I run a proof-of-concept before buying? Yes. Because pricing and accuracy both depend heavily on your specific document types, a paid pilot against real (not demo) documents is the only reliable way to validate the business case before a multi-year commitment.
A customer data platform (CDP) collects behavioral and transactional data from every app, website, and system your customer touches, stitches it into one profile per person, and makes that profile usable by your marketing, analytics, and product tools. Segment, mParticle, and Tealium were the three names that effectively defined this category — but one of them has changed ownership since the last time most comparison articles were written, and all three gate their real pricing behind usage or a sales call. We went to each vendor’s own site to confirm exactly what is and isn’t public before writing a single number below.
At a Glance
Platform
Ownership
Pricing transparency
Entry point
Pricing basis
Segment (Twilio)
Twilio
Partially public — self-serve tiers listed
Free plan, $0/mo
Monthly Tracked Users (MTUs)
mParticle
Rokt (acquired January 2025, ~$300M)
Not public — contact sales
No self-serve tier found
Not disclosed
Tealium
Independent (Tealium, Inc.)
Not public — “Get a Pricing Quote”
No self-serve tier found
Inbound events (usage-based)
Short Verdict
Segment is the only one of the three where you can actually see starting prices without booking a call, which makes it the natural starting point for a smaller marketing team or a startup validating a CDP use case before committing budget. mParticle has effectively become a different product since Rokt’s 2025 acquisition — its own pricing page now redirects into Rokt’s e-commerce-transaction-focused platform, and the company is clearly leaning into monetization and audience activation around checkout moments rather than being a neutral, general-purpose CDP. Tealium remains the enterprise-leaning, usage-priced option, with the broadest published destination-count claim (1,300+) but zero public numbers to back a budget estimate.
What Each Platform Actually Is
Segment, owned by Twilio, sells two product tiers per its own pricing documentation: a “Customer Data Pipeline” product (data collection and routing to 700+ destinations, no identity resolution) and a full “Customer Data Platform” product that adds Unify (identity resolution) and Engage (AI-powered audiences and journey orchestration). Both are priced on Monthly Tracked Users. Segment publishes genuine self-serve numbers for the Pipeline product: a Free plan ($0/month, up to 1,000 MTUs, 2 sources, 1 warehouse destination), a Team plan (starting at $120/month, including 10,000 MTUs, with a 14-day free trial), and a custom-quoted Business plan for larger volumes and features like HIPAA eligibility and regional data residency. Team-tier overage for additional MTUs is listed at roughly $10–$12 per extra 1,000 MTUs depending on which part of Twilio’s own pricing page you read — the figures aren’t fully consistent between the comparison table and the FAQ on the same page, so treat that specific overage rate as directional rather than exact.
mParticle is no longer an independently positioned CDP in the way it was a few years ago. Rokt, an e-commerce transaction-moment advertising company, acquired mParticle in January 2025 in a deal reported at roughly $300 million. mParticle’s own pricing URL now redirects to a Rokt platform page branded “Rokt mParticle,” which leads with features like “Match Boost,” “Audience Expansion,” “Household Reach,” and an “mParticle Agent” conversational assistant for building audiences and running predictions — all framed around Rokt’s transaction-moment advertising business rather than a standalone, vendor-neutral CDP pitch. The page lists no pricing, no plan tiers, and no free trial; every call to action leads to “Talk to an expert” or “Contact us.”
Tealium remains an independent company and still frames itself as a CDP built around real-time and warehouse-native identity resolution. Its own CDP overview page describes identity resolution across devices and sessions, real-time and scheduled activation, warehouse-native activation on Snowflake, Databricks, BigQuery, and Redshift, 1,300+ pre-built destination connectors, and consent/governance enforcement carried through to activation. Pricing is explicitly usage-based — priced on inbound events, with no per-seat or per-integration fees, according to Tealium — but no rate card exists publicly; the page’s “Get a Pricing Quote” link leads to a demo-request form rather than a price.
Pricing Breakdown
Platform
Plan
Published rate
What it includes
Segment
Free
$0/month
Up to 1,000 MTUs, 2 sources, 1 warehouse destination, 500,000 Reverse ETL records/mo, 10 seats
Segment
Team
Starting at $120/month
10,000 MTUs included, unlimited sources, 1,000,000 Reverse ETL records/mo, public API access, 14-day free trial
Contact sales; no self-serve tier or trial found on the current page
Tealium
N/A
Not published
Usage-based on inbound events; quote required via demo request
Pros and Cons
Segment
Pros: Real, visible self-serve pricing with a usable free tier; backed by Twilio’s broader communications/data infrastructure; 700+ pre-built destinations; clear path from free to paid.
Cons: Full identity-resolution and audience-orchestration features (Unify/Engage) sit in a separately priced, custom-quoted product, not the self-serve plans; MTU overage pricing is confusingly presented on Twilio’s own site.
mParticle (Rokt mParticle)
Pros: Deep identity resolution and predictive audience tooling; now backed by Rokt’s e-commerce transaction-moment reach and investment; 350+ listed integrations.
Cons: No public pricing or trial of any kind; post-acquisition positioning is now tilted toward Rokt’s advertising/monetization use cases, which may not fit teams wanting a neutral, standalone CDP; buyers should factor in the ownership change when evaluating long-term product direction.
Tealium
Pros: Independent ownership; genuinely usage-based pricing model (no seat or integration fees, per Tealium); largest published destination-connector count (1,300+); strong warehouse-native activation story.
Cons: Zero public numbers anywhere — not even a starting “from $X” figure — so you cannot budget without a sales call; no self-serve or trial path visible on the public site.
Who It’s a Good Fit For
Choose Segment if you want to start small, see real pricing, and grow from a free or $120/month plan into a custom enterprise deal only once you’ve proven the use case. Choose mParticle (Rokt mParticle) if your core goal is leveraging first-party data for monetization and advertising at the transaction moment — particularly in retail, travel, or media — and you’re comfortable buying into Rokt’s broader platform direction. Choose Tealium if you need strong warehouse-native activation across Snowflake/Databricks/BigQuery/Redshift and want an independent vendor not tied to a specific cloud or ad-tech parent company, and your organization is large enough to justify an enterprise sales process.
Who Should Look Elsewhere
If you need firm, comparable pricing across vendors before you can even get budget approval to start evaluating, none of the three will fully satisfy that on their own — you’ll need actual quotes from mParticle and Tealium, and a usage estimate against Segment’s published MTU-based rates, before any apples-to-apples comparison is possible.
Bottom Line
The CDP market in 2026 looks different from a few years ago mainly because of what happened to mParticle: Rokt’s acquisition has visibly reshaped its public-facing positioning away from a neutral CDP pitch and toward transaction-moment monetization, and its pricing is now completely opaque. Segment remains the most transparent and most self-serve-friendly of the three, even though its deepest identity-resolution features require a custom quote. Tealium is the steady, independent, usage-priced enterprise option — but like mParticle, you will not get a number without picking up the phone.
FAQ
Is mParticle still a separate product from Rokt? Rokt completed its acquisition of mParticle in January 2025 (reported at roughly $300 million), and mParticle’s own pricing URL now redirects to a Rokt-branded platform page, so its public identity has merged into Rokt’s.
Does Segment’s free plan include identity resolution? No. Segment’s published Free and Team plans cover the Customer Data Pipeline product (collection and routing only); identity resolution and audience orchestration (Unify/Engage) are part of the separately, custom-priced Customer Data Platform product.
Why can’t I find a starting price for Tealium? Tealium prices on inbound event volume rather than a flat plan, and its own pricing page sends every pricing inquiry to a demo-request form rather than publishing a rate card — this is standard for enterprise-tier CDPs but means no public “starting at” figure exists.
What’s a Monthly Tracked User (MTU)? It’s Segment’s billing unit — broadly, a unique user your Segment workspace tracks events for in a given month — and it’s the basis for both the Free plan’s 1,000-MTU cap and the Team plan’s 10,000-MTU included allowance.
Can a small business realistically afford any of these? Segment’s Free and $120/month Team plans are realistic for a small business handling collection and routing only. mParticle and Tealium are both positioned and priced for mid-market-to-enterprise deployments, and neither publishes a small-business-friendly entry tier.
A web application firewall sits in front of your app or API and filters out malicious HTTP traffic — SQL injection attempts, cross-site scripting, credential-stuffing bots, and the long tail of OWASP Top 10 attacks — before it reaches your servers. It’s infrastructure-layer security, which is why the three tools worth comparing here come from very different corners of the industry: Cloudflare is a CDN/edge network that bundles WAF into its plans, AWS WAF is a pay-as-you-go primitive built for anyone already running on AWS, and Imperva is a dedicated application-security vendor selling WAF as its core product. We pulled every number below directly from cloudflare.com and aws.amazon.com/waf/pricing, and confirmed Imperva’s pricing is not publicly listed.
At a Glance
Platform
Pricing model
Entry price
WAF on entry tier?
Best known for
Cloudflare WAF
Flat-rate plan tiers
$0/mo (Free plan)
Yes — included even on Free
Simplicity, bundled CDN + WAF + DDoS
AWS WAF
Pure pay-as-you-go (per web ACL, rule, and request)
No subscription — usage-based, from ~$5/mo for one web ACL
Yes, but priced à la carte
Deep AWS-native integration (CloudFront, ALB, API Gateway)
Imperva Cloud WAF
Not public — quote-based
Contact sales
Yes, on all plans (scope depends on quote)
Low false-positive managed rules, dedicated threat research team
Short Verdict
Cloudflare is the fastest path to “some WAF protection” for almost nothing — it’s literally on the free plan — and scales cleanly into paid tiers as you need compliance features and SLAs. AWS WAF is the right call if your app already lives behind CloudFront, an Application Load Balancer, or API Gateway, because it’s billed by the component (web ACL, rule, request) rather than by plan, which can be cheaper or pricier depending on traffic shape. Imperva is the choice for security teams who want a vendor-managed rule set tuned by a dedicated research team and are willing to go through a sales process to get a number — it’s priced like an enterprise security product because, unlike the other two, that’s Imperva’s whole business.
What Each Platform Actually Is
Cloudflare WAF ships as a feature bundled into Cloudflare’s CDN plans rather than sold separately. Per cloudflare.com/plans, the Free plan ($0/month) already includes the WAF, a free managed ruleset, unmetered DDoS protection, and a universal SSL certificate. Pro ($20/month billed annually, or $25 billed monthly) and Business ($200/month annually, or $250 monthly) add more managed rules and features; Business is the first tier with PCI DSS 4.0 compliance and an uptime SLA. The top tier — which Cloudflare’s own pricing page now labels “Contract” rather than “Enterprise” — is custom-priced and adds things like network prioritization and higher-multiplier uptime service credits.
AWS WAF has no plan tiers at all in the traditional sense — it’s billed per component. Per aws.amazon.com/waf/pricing: $5.00 per web ACL per month, $1.00 per rule (or per managed rule group) per web ACL per month, and $0.60 per million web requests at the default inspection level, with small surcharges if you raise the Web ACL Capacity Unit (WCU) limit or inspect larger request bodies. Allow, Block, and Count actions carry no extra charge. Add-on modules are priced separately: Bot Control costs $10/month per web ACL plus $1 per million requests (first 10 million monthly requests free), and the Fraud Control modules (Account Takeover Prevention, Account Creation Fraud Prevention) are $10/month per web ACL each plus tiered per-request fees. New AWS customers get a limited allocation under the AWS Free Tier for the first 12 months.
Imperva Cloud WAF is a SaaS WAF managed through the Imperva Management Console, positioned around “near-zero false positives” because its managed rules are written and tested by Imperva’s own Threat Research team before release, rather than relying purely on automated rule generation. Imperva’s product page lists integrated bot protection and API security, machine-learning “Attack Analytics” that correlates alerts into incident narratives, automated SSL certificate management, file-upload scanning, a Terraform provider, and an AI Assistant for natural-language investigation. Imperva also sells on-premises (WAF Gateway) and Kubernetes-native (Elastic WAF) deployment options alongside the cloud product. None of this comes with a published price — every path on the page leads to “Schedule demo,” “Contact Us,” or a free trial sign-up.
Pricing Breakdown
Platform
Published rate
Notes
Cloudflare Free
$0/mo
WAF, managed ruleset, unmetered DDoS, SSL, SSO, RBAC all included
Cloudflare Pro
$20/mo (annual) or $25/mo (monthly)
Adds performance features (image optimization, AMP)
Billed hourly-prorated; scales with number of ACLs and rules
AWS WAF Bot Control
$10/mo + $1/million requests (10M free)
Separate add-on per web ACL
AWS WAF Fraud Control
$10/mo per module + tiered per-request fees
Account Takeover Prevention and Account Creation Fraud Prevention are priced separately
Imperva Cloud WAF
Not published
Quote-based; free trial available at imperva.com/free-trial
Pros and Cons
Cloudflare WAF
Pros: Genuinely free tier with real WAF protection; predictable flat pricing; bundled with CDN, DDoS protection, and SSL; easiest onboarding of the three.
Cons: Advanced compliance and SLA features gated behind Business and Contract tiers; custom rule depth is lighter than a dedicated application-security vendor.
AWS WAF
Pros: True pay-as-you-go with no plan lock-in; tight integration with CloudFront, ALB, API Gateway, and AppSync; granular control over rules and WCU budget.
Cons: Costs stack up fast once you add Bot Control and Fraud Control modules; pricing structure (WCUs, body-inspection tiers, CAPTCHA fees) takes real effort to model correctly; no bundled CDN or DDoS product unless you’re also paying for CloudFront/Shield.
Imperva Cloud WAF
Pros: Managed rules vetted by a dedicated threat research team; strong analytics and incident correlation; flexible deployment (cloud, on-prem, Kubernetes) under one vendor.
Cons: No public pricing anywhere — every evaluation starts with a sales call; likely overkill (and over-budget) for a small team that just needs baseline protection.
Who It’s a Good Fit For
Choose Cloudflare if you want WAF protection today with zero procurement process, or you’re already using Cloudflare for DNS/CDN and want it bundled in. Choose AWS WAF if your application is already running on AWS infrastructure and you want security billed the same granular way as the rest of your stack — and you’re comfortable modeling costs component by component. Choose Imperva if you’re a mid-size-to-enterprise security team that wants a vendor-managed, actively curated rule set and dedicated support, and your budget process can absorb a quote-based enterprise security purchase.
Who Should Look Elsewhere
If you need multi-cloud WAF coverage (not just AWS) with a single pane of glass, neither Cloudflare’s app-specific rules nor AWS WAF’s AWS-only scope will fully satisfy you without extra tooling — that’s a case where Imperva’s cloud-agnostic positioning, or a dedicated multi-cloud security platform, is worth the sales conversation.
Bottom Line
These three aren’t interchangeable line items — Cloudflare sells WAF as part of a broader edge-network subscription, AWS sells it as a metered infrastructure primitive, and Imperva sells it as a dedicated, support-heavy security product. For most small-to-mid-size teams, Cloudflare’s free-to-$200/month ladder is the easiest decision to justify. Teams already deep in AWS should model AWS WAF’s per-component costs against their real traffic before assuming it’s cheaper. And any team that needs white-glove rule tuning and incident analytics should expect to get Imperva on the phone rather than finding a number online.
FAQ
Is the WAF on Cloudflare’s Free plan actually usable, or just a teaser? Per Cloudflare’s own plan comparison, the Free plan includes the WAF along with a free managed ruleset, so it’s a real (if more basic) deployment, not a disabled demo.
How much does AWS WAF cost for a typical small site? At minimum, one web ACL with a few rules runs roughly $5–$10/month in base fees, plus $0.60 per million requests — the real cost driver is add-ons like Bot Control ($10/month + per-request fees) if you need them.
Why doesn’t Imperva publish any pricing? Imperva sells WAF as an enterprise security product with variable scope (traffic volume, number of sites, deployment model), which it — like most enterprise security vendors — prices through a sales conversation rather than a public rate card.
Can I use AWS WAF if my app isn’t hosted on AWS? AWS WAF is designed to attach to AWS resources (CloudFront, Application Load Balancer, API Gateway, AppSync, Amplify, Cognito, Verified Access), so it’s not a general-purpose option for non-AWS-hosted applications — Cloudflare or Imperva fit that case better.
Does any of these offer a free trial? Cloudflare’s Free plan is a permanent free tier, not a trial. AWS WAF has no trial as such — you simply pay for usage, with a limited free allocation under the AWS Free Tier for new accounts. Imperva offers a dedicated free trial sign-up at imperva.com/free-trial.
Every supervised model still needs labeled data, and the market for getting that labeling done has split into two camps: platforms you operate yourself with transparent self-serve pricing, and managed services where the price is a conversation. Labelbox, Scale AI, and Amazon SageMaker Ground Truth sit at different points on that spectrum. Here’s what each actually publishes about cost and capability, and where the gaps in public pricing are real rather than just marketing fog.
At a Glance
Tool
Deployment
Published pricing
Labeling labor
Best for
Labelbox
Hosted SaaS platform
Yes — self-serve rates published
Self-serve ($8–10/hr) or managed (Enterprise)
Teams that want a labeling tool plus optional managed workforce
Scale AI
Managed service + platform
No — contact sales only
Scale-managed workforce
Large-scale, high-stakes datasets (autonomous vehicles, LLM training data)
SageMaker Ground Truth
AWS-native service
Partial — billed per reviewed object, no flat published rate
Amazon Mechanical Turk, vendor workforce, or your own team
Teams already building on AWS who want labeling in the same billing pipeline
Short Verdict
Labelbox is the only one of the three that tells you a number before you talk to a salesperson — its Free and Starter tiers publish an actual hourly labeling rate. Scale AI publishes no pricing at all on its own site; every path on scale.com leads to “book a 1:1 intro call,” which is consistent with its history of serving large enterprise and government contracts rather than self-serve teams. SageMaker Ground Truth sits in between: AWS documents the billing unit (per reviewed dataset object) and the workforce options, but the actual per-object rate depends on your chosen workforce and task type, so there’s no single number to quote either.
What Each One Is
Labelbox is a labeling and data-curation platform you log into directly. It supports image, video, text, and document annotation, model-assisted labeling (pre-labeling with your own model to speed up human review), and workflow tools for QA. You can either have your own team label inside Labelbox or use Labelbox’s own labeling workforce for an hourly rate.
Scale AI began as a human-in-the-loop data labeling company for autonomous vehicle perception and has expanded into a broader “Scale Data Engine” plus a GenAI data portfolio (RLHF data, evaluation data, red-teaming) and its Donovan product for government/defense use cases. It positions itself as a managed service: you describe the dataset and task, Scale runs the labeling operation.
Amazon SageMaker Ground Truth is AWS’s built-in data labeling feature inside SageMaker. You create a labeling job, pick a workforce (your own private team, Amazon Mechanical Turk’s public workforce, or a third-party vendor workforce from AWS Marketplace), and pay based on the number of dataset objects reviewed. Ground Truth Plus is a separate, fully managed variant where AWS’s own team and tooling handle the labeling instead of you managing a workforce yourself.
Pricing & Cost Structure
Plan/Tier
Labelbox
Scale AI
SageMaker Ground Truth
Entry tier
Free: self-serve labeling at $8/hour, up to 30 users, 50 projects, 25 ontologies, 1 workspace
Not published
No flat tier; you pay per dataset object reviewed, plus underlying AWS compute/storage
Mid tier
Starter: labeling from $10/hour, unlimited users/projects/ontologies, custom workflows, model-assisted labeling
Not published
Mechanical Turk workforce: priced per object per review instance (no fixed public rate; varies by task/modality)
Top tier
Enterprise: custom, quote-based, volume discounts, fully managed labeling with an SLA, up to 3 workspaces
Enterprise-only; “book a 1:1 intro call” is the only published path to pricing
Vendor workforce (AWS Marketplace): each vendor sets its own per-label price; Ground Truth Plus is a fully managed option with no published rate
Education
Free for qualifying educators/students, non-commercial research only
Not applicable
Not applicable
The honest summary: Labelbox is the most price-transparent of the three for anyone doing their own labeling or hiring Labelbox’s workforce by the hour. Scale AI’s site discloses no pricing whatsoever — every pricing claim you’ll see about Scale on third-party comparison sites is an estimate, not a published figure. AWS documents how Ground Truth bills (per reviewed object) but not a universal rate, because that rate depends on which workforce you choose and what kind of data you’re labeling (images, video frames, text, audio, or 3D point clouds).
Pros
Labelbox: Transparent self-serve pricing; flexible between DIY labeling and managed workforce; model-assisted labeling to cut manual effort.
Scale AI: Deep experience with very large, high-stakes datasets; broad portfolio covering traditional labeling and newer GenAI data needs (RLHF, evals, red-teaming).
SageMaker Ground Truth: Billing lives inside your existing AWS account; choice of workforce (your own team, Mechanical Turk, or vendors) gives cost/quality flexibility; integrates directly with the rest of the SageMaker ML pipeline.
Cons
Labelbox: Enterprise tier (managed labeling with SLA) is quote-only, same as the competitors, once you need that level of service.
Scale AI: Zero public pricing of any kind, which makes it hard to budget or comparison-shop without a sales conversation.
SageMaker Ground Truth: No fixed public per-object rate; final cost depends heavily on workforce choice and task complexity, so estimating total spend takes real test-job data, not a pricing page.
Who It’s a Good Fit For
Choose Labelbox if you want to start labeling today with a credit card and scale into managed services later without switching tools. Choose Scale AI if you’re running a large enterprise or frontier-model training program where a dedicated account team and custom workforce design matter more than self-serve pricing. Choose SageMaker Ground Truth if your ML pipeline already lives in AWS and you want labeling billed through the same account, with the option to use Mechanical Turk’s public workforce for lower-stakes tasks.
Who Should Look Elsewhere
If you need a guaranteed, fixed per-label cost before you start a project, none of the three fully delivers that at scale — Labelbox’s hourly self-serve rate is the closest thing to a transparent number, but Enterprise-tier managed labeling on all three ultimately requires a quote. Teams with no AWS footprint may find Ground Truth’s setup (IAM roles, workforce configuration, S3 buckets) adds overhead a dedicated labeling SaaS wouldn’t.
Bottom Line
There is no universal “price per label” you can quote across these three tools, and that’s a genuine finding, not a gap in this research — Scale AI discloses nothing publicly, and AWS discloses the billing model but not a rate. Labelbox is the one vendor here that puts an actual number on its pricing page, which makes it the easiest to budget for at small-to-mid scale.
FAQ
Does Labelbox have a free plan? Yes — Labelbox’s Free tier supports up to 30 users, 50 projects, and 25 ontologies, with self-serve labeling priced at $8/hour if you use Labelbox’s own labeling workforce.
Why doesn’t Scale AI publish pricing? Scale.com’s own pricing page has no plans or rates; it routes every visitor to “book a 1:1 intro call,” consistent with its focus on large, custom enterprise and government engagements rather than self-serve signup.
What’s the difference between SageMaker Ground Truth and Ground Truth Plus? Ground Truth is a self-managed labeling job where you configure and oversee the workforce (your own team, Mechanical Turk, or a vendor); Ground Truth Plus is a fully managed service where AWS’s team runs the labeling operation for you.
Can I use Amazon Mechanical Turk workers through Ground Truth? Yes, Mechanical Turk’s public workforce is one of the three workforce options in Ground Truth, alongside a private workforce (your own team) and third-party vendor workforces listed on AWS Marketplace.
Is there an education discount for any of these? Labelbox offers a free tier for qualifying educators and students, limited to non-commercial research use; Scale AI and SageMaker Ground Truth don’t publish an education-specific tier.
Generative image and video tools have split into three very different businesses. Midjourney stays a closed, subscription-only image generator accessed through Discord or a web app. Stability AI gives away open-weight Stable Diffusion models under a revenue-based license while also selling a hosted creative platform. Runway has moved furthest into video, selling credit-based plans built around its Gen-series video models. The marketing copy on all three sites is confident; the fine print on pricing, ownership and commercial rights is where the real differences show up. This guide sticks to what each company states on its own pricing and terms pages as of November 2026.
At a Glance
Tool
Entry price
Core medium
Who owns the output
Best for
Midjourney
$10/mo (Basic), $8/mo billed yearly
Still images
You, if under $1M annual revenue or on Pro/Mega
Stylized, art-directed still images
Stable Diffusion (Stability AI)
Free to self-host under $1M revenue; hosted Trial free, Creator $19/mo
Images, audio, 3D; open weights
You own outputs, subject to license tier
Teams that want to self-host or fine-tune models
Runway ML
Free (125 one-time credits); Standard $15/mo ($12/mo yearly)
Video generation and editing
Not stated on pricing page; check Terms of Use
AI video generation and editing workflows
Short Verdict
Midjourney still produces the most consistently polished still images for a flat, predictable subscription, but its commercial-use terms tighten sharply once a company crosses $1 million in annual revenue. Stable Diffusion remains the only one of the three that can be run on your own hardware, which matters if you need to fine-tune a model or avoid per-generation fees entirely — but the free “Community” license only applies below the same $1 million revenue line. Runway is the strongest of the three for video specifically, with the most transparent credit math, though its own pricing page is silent on commercial ownership of outputs, so enterprise users should read Runway’s separate Terms of Use before shipping client work.
What Each One Actually Is
Midjourney is a hosted, closed-source image generator. There is no self-hosting option and no public API in the traditional sense; access is through Discord or Midjourney’s own web interface, and every image you generate is public by default unless you’re on a plan with Stealth Mode. It focuses almost entirely on stills — there is no first-party video generation feature comparable to Runway’s.
Stable Diffusion is not really one product — it’s a family of open-weight models (SDXL, Stable Diffusion 3.5, Stable Audio, Stable Fast 3D, and others) released by Stability AI under its own model license. You can download the weights and run them locally or on your own cloud infrastructure, use third-party hosts, or pay Stability AI directly through its hosted Creator/Core/Enterprise plans for an all-in-one platform with curated model routing and support.
Runway ML is a hosted video and image generation and editing platform built around its own Gen-series models (plus some third-party models). It’s the only one of the three with a genuinely mature text-to-video and video-editing toolset, including tools for motion brush, inpainting, and lip-sync, sold through a monthly credit allowance rather than a flat generation count.
Pricing & Licensing Breakdown
Plan tier
Midjourney
Stable Diffusion (Stability AI)
Runway ML
Free
Not offered
Community License: free to self-host for researchers, developers, small businesses and creators under $1M/yr revenue
$0/mo — 125 one-time credits, 5GB storage, a selection of models
Entry paid
Basic: $10/mo, or $8/mo billed yearly
Hosted Creator plan: $19/mo for end-to-end generation/editing
Standard: $15/mo, or $12/mo billed yearly — 625 credits/mo, 20GB storage, no watermark
Max: $95/mo, or $76/mo billed yearly — 9,500 credits/mo, 500GB, one month of credit rollover
Enterprise
Not published; Pro/Mega required for commercial ownership above $1M revenue
Enterprise License: custom pricing, required once annual revenue exceeds $1M, adds support and optional fine-tuning/consulting
Custom pricing via “Contact sales”
Ownership, in the vendors’ own words: Midjourney’s Terms of Service state that “You own all Assets You create with the Services to the fullest extent possible under applicable law,” but add that companies — and employees of companies — with more than $1,000,000 USD in annual revenue must be on a Pro or Mega plan to retain that ownership. Midjourney content is also public and remixable by default; Stealth Mode (private generations) is included on Pro and Mega.
Stability AI’s license page states plainly that “you own outputs generated from the Core Models or Derivative Works,” and that self-hosting its Core Models is free unless you use them commercially and your organization’s annual revenue exceeds $1 million, at which point an Enterprise License is required.
Runway’s public pricing page does not include a statement on commercial use rights or output ownership for any plan — that language lives in Runway’s separate Terms of Use rather than the pricing page, so we’re flagging it rather than guessing: enterprise buyers should confirm current commercial terms directly with Runway before relying on this article for a legal answer.
Pros
Midjourney: Consistently strong aesthetic output with minimal prompt engineering; simple flat-rate pricing; fast generation.
Stable Diffusion: Only option here you can self-host and fine-tune; no per-image API fees if you run it yourself; multiple modalities (image, audio, 3D).
Runway ML: Most capable first-party video generation and editing suite; transparent credit-per-plan math; free tier has no time limit.
Cons
Midjourney: No self-hosting or fine-tuning; commercial ownership gets legally complicated above $1M revenue; images are public by default.
Stable Diffusion: Self-hosting requires your own GPU infrastructure and ML ops know-how; Enterprise License pricing is not published, so budgeting requires a sales call.
Runway ML: Monthly credits don’t roll over on most tiers; commercial/ownership terms aren’t spelled out on the pricing page itself; Enterprise pricing is quote-only.
Who It’s a Good Fit For
Pick Midjourney if you mainly need high-quality still images for marketing, concept art, or social content and don’t need to touch model weights. Pick Stable Diffusion if you need to run models on your own infrastructure, fine-tune on proprietary data, or want zero per-image API costs at small scale. Pick Runway if video generation and editing — not stills — is the actual job.
Who Should Look Elsewhere
Companies already over the $1M annual revenue mark need to budget for Midjourney’s Pro/Mega tier or Stability’s Enterprise License before they can safely rely on either for client-facing commercial work. Teams with no ML infrastructure or MLOps staff should treat Stable Diffusion’s self-hosting path as a real engineering project, not a quick swap-in for a hosted tool.
Bottom Line
These three tools aren’t really substitutes for each other — Midjourney and Stable Diffusion overlap on stills, Runway owns video — so the real decision is less “which is best” and more “which medium and deployment model do you need.” Whichever you choose, read the revenue-based licensing clauses before scaling a commercial product on top of free or entry-tier access.
FAQ
Can I use Midjourney images commercially on the $10 Basic plan? Yes, as long as your company and you as an individual earn under $1,000,000 USD in annual revenue; above that, Midjourney’s terms require a Pro or Mega subscription to retain ownership of the assets.
Is Stable Diffusion really free? The models are free to download and self-host under Stability AI’s Community License if your organization’s annual revenue is under $1 million; above that threshold, an Enterprise License (custom pricing) is required for commercial use.
Does Runway say who owns the videos I generate? Not on its public pricing page. That information sits in Runway’s separate Terms of Use, so enterprise users should confirm current language there rather than assume.
Do unused Runway credits roll over? On Standard and Pro, no — unused monthly credits are forfeited at renewal. The Max plan is the exception, allowing up to one month of unused credits to roll over.
Can I fine-tune Midjourney or Runway’s models the way I can with Stable Diffusion? No — Midjourney and Runway are closed-weight hosted services with no public model download, so fine-tuning in the traditional sense isn’t available; Stable Diffusion’s open weights are the only one of the three built for that.
Finding out which of your servers, laptops, and web apps have exploitable holes — before an attacker does — is the job of a vulnerability scanner. Turning that list of holes into closed tickets is the job of patch and remediation management. For a small business with a lean IT team, the gap between those two jobs is where most breaches actually happen: the vulnerability was known, a scan even flagged it, and it just never got patched. Tenable Nessus, Qualys VMDR, and Rapid7 InsightVM are three of the most widely deployed tools that try to close that gap, but they are not three versions of the same product. Nessus is, at its core, a scanner. Qualys VMDR and Rapid7 InsightVM are full detection-and-response platforms built around a scanner. That distinction matters more than any feature checkbox, so we verified it directly against each vendor’s own product and pricing pages rather than relying on secondary “comparison” sites.
Yes, length not stated; Expert free for 7 days for existing Pro users
Qualys VMDR
Qualys
Full vulnerability management, detection & response platform
Not public — segmented by business size, contact sales
Yes — 30 days
Rapid7 InsightVM
Rapid7
Vulnerability management platform, now sold as part of Exposure Command
Not public — asset-based, contact account team
Offered, duration not stated
Short Verdict
If you need a straightforward, affordably-priced scanner you can point at your network, servers, and a handful of web apps and get a clear, prioritized list of what to fix, Nessus is the easiest tool for a small IT team to own and its price is actually public. If you want one platform that discovers assets, scans them, scores risk, and can push remediation or open tickets automatically, Qualys VMDR and Rapid7 InsightVM are the stronger (and pricier, quote-only) choices — and between the two, the decision usually comes down to which ecosystem you already live in (ServiceNow/Jira integration depth, cloud-native asset discovery, or existing Rapid7 InsightIDR/SIEM investment) rather than a hard feature gap.
What Each Tool Actually Is
Tenable Nessus is a single-purpose vulnerability scanner that ships as Nessus Professional and Nessus Expert. Per Tenable’s own product page, both editions cover unlimited IT vulnerability assessments, CVSS v4/EPSS/VPR-based vulnerability scoring, configuration and compliance audits, more than 450 pre-built templates, CIS benchmark auditing, and web application scanning covering five fully qualified domain names (FQDNs) by default, with more available as an add-on. Nessus also integrates with Terrascan to scan infrastructure-as-code before it is deployed, and both editions list coverage of more than 336,000 CVEs. Nessus does not include its own ticketing, remediation orchestration, or asset-risk dashboard across an organization — it is designed to be the scan engine, and enterprises often pair it with Tenable’s larger platforms (Tenable.io, Tenable One) for that layer.
Qualys VMDR (Vulnerability Management, Detection and Response) is a cloud platform that bundles asset discovery, scanning, risk scoring, and automated remediation into one subscription. Qualys’s own product page describes asset discovery across on-premises, cloud, and internet-facing environments; a “TruRisk” scoring model pulling from more than 25 real-time threat-intelligence sources; prioritization mapped to MITRE ATT&CK and exploited-in-the-wild status; and automated remediation that can deploy patches and mitigations directly or open tickets in ServiceNow or Jira. It includes unlimited virtual scanners, cloud agents, passive sensors, and container sensors, plus PCI ASV assessments and CIS benchmark checks.
Rapid7 InsightVM is now sold as part of Rapid7’s broader “Exposure Command” family rather than as a pure standalone SKU — Rapid7’s own product page names two packages, Exposure Command Essentials (InsightVM plus attack surface management) and Exposure Command Ultimate (which adds cloud and application security on top). Rapid7 describes coverage as “flexible, based on the asset types you use” and directs pricing questions to your account team rather than listing rates publicly.
Same core engine as Pro, marketed for “the modern attack surface”; 7-day free upgrade trial for Pro users
Qualys VMDR
Not published — “Speak to an Expert” / segment-specific subscription pages (Small Business, Mid-Sized, Enterprise, Public Sector)
Full VMDR platform; 30-day free trial confirmed on qualys.com
Rapid7 InsightVM
Not published — contact your Rapid7 account team
Sold under Exposure Command Essentials or Ultimate packages
Nessus is the only one of the three with a list price you can see without talking to a salesperson, and that alone makes it attractive to a very small business or a solo IT admin doing initial budgeting. Qualys and Rapid7 both gate pricing behind a quote, which almost always means the number scales with asset count and will be negotiable — budget for a call, not a checkout page, if you’re evaluating either.
Pros and Cons
Tenable Nessus
Pros: Transparent list pricing, low learning curve, very broad CVE coverage, strong compliance/CIS auditing templates, portable (runs on platforms as small as a Raspberry Pi).
Cons: No built-in remediation workflow, ticketing, or multi-team dashboard; scales awkwardly past a handful of scanners; web app scanning capped at 5 FQDNs by default.
Qualys VMDR
Pros: One platform for discovery, scanning, risk scoring, and remediation; unlimited scanners/agents; strong compliance tooling (PCI ASV, CIS); ITSM integrations built in.
Cons: No public pricing, so budgeting requires a sales conversation; feature depth can be more than a very small business needs.
Rapid7 InsightVM
Pros: Flexible asset-based coverage; now bundled with broader exposure management (attack surface, cloud, app security) if you need it; strong track record in mid-market and MSP deployments.
Cons: No public pricing or trial length stated; the product is increasingly sold as part of a bundle, which can push a small business toward paying for scope it doesn’t need yet.
Who It’s a Good Fit For
Choose Nessus if you’re a small business or MSP that mainly needs a reliable scanner with clear, upfront pricing and you’re comfortable handling remediation yourself (via your existing RMM, patch tool, or manual process). Choose Qualys VMDR if you want one subscription that both finds and helps fix issues, and you’re willing to get on a call to find out what that costs at your asset count. Choose Rapid7 InsightVM if you anticipate growing into broader exposure management (cloud posture, external attack surface) and want a platform that can expand with you, or if your team already uses other Rapid7 Insight products.
Who Should Look Elsewhere
If you have zero in-house security staff and no time to triage scan output, any of these three will produce more findings than you can act on without a managed service wrapped around them — in that case, a managed vulnerability management service from an MSSP may serve you better than buying a tool directly.
Bottom Line
Nessus, Qualys VMDR, and Rapid7 InsightVM aren’t really three competitors fighting for the same budget line — Nessus competes on being the affordable, transparent scanner, while Qualys and Rapid7 compete against each other as full remediation platforms priced by quote. A small business on a tight budget that just needs visibility should start with Nessus; one that wants scanning and remediation handled in a single subscription should get quotes from both Qualys and Rapid7 and compare them against actual asset counts, since list prices for either aren’t published anywhere.
FAQ
Is Nessus the same thing as Tenable.io or Tenable One? No. Nessus is Tenable’s standalone scanner product. Tenable.io and Tenable One are separate, larger platforms built on top of the same scanning engine, aimed at organizations that need multi-team dashboards and broader exposure management.
Does any of these three actually install patches automatically? Qualys VMDR’s own page describes “automated remediation” that can deploy patches or mitigations directly, or create ITSM tickets. Nessus and the core InsightVM product are oriented toward detection and prioritization, with remediation typically handled through your existing patch tooling or ticketing system.
Why don’t Qualys and Rapid7 publish prices? Both price based on asset count and deployment scope, which varies too much between customers for a simple price list — this is standard for enterprise security platforms, and both vendors confirm pricing requires a sales conversation.
Can a very small business realistically use Nessus alone? Yes — for a business with a handful of servers and a small web presence, Nessus Professional’s unlimited scanning and compliance templates can cover the detection side, as long as someone owns turning findings into fixed tickets.
Is there a free option for any of these? None has a permanent free tier for business use. All three offer free trials: Nessus’s trial length isn’t stated on its page, Qualys VMDR explicitly offers 30 days, and Rapid7 offers a trial without a stated length.
Passkeys have moved from an early-adopter curiosity to something most people have already used without necessarily noticing — that Face ID or fingerprint prompt that replaced a password field on Amazon or GitHub. The FIDO Alliance’s Passkey Index 2026 reports that 36% of successful sign-ins now use a passkey, up from 26% in 2025, and that passkey sign-ins succeed 93% of the time compared with 78% for traditional multi-factor authentication (MFA) — and are roughly three times faster, saving an average of about 27 seconds per sign-in. But passkeys are not a universal password replacement yet. Here’s where they genuinely work in 2026, and where passwords (or at least traditional MFA) still have the edge.
At a Glance
Dimension
Passkeys
Passwords (+ traditional MFA)
Sign-in success rate
93% (FIDO Alliance, 2026)
78% for traditional MFA (FIDO Alliance, 2026)
Phishing resistance
High — credentials are bound to the origin domain and can’t be typed into a fake site
Low to moderate — passwords and OTP codes can be phished or relayed
Cross-device use
Works via platform sync (same ecosystem) or Bluetooth+QR for cross-device, per Google/Microsoft/Apple documentation
Works anywhere you can type
Recovery if all devices are lost
Possible via platform-specific escrow (e.g., Apple iCloud Keychain), but recovery steps vary by provider
Password reset flows are more universally understood
Universal site support
No — many sites, most banks, and most government/healthcare portals don’t support them yet
Yes — effectively universal fallback
Where Passkeys Actually Work
The technical standard behind passkeys — FIDO2/WebAuthn — is mature and well-documented by the major platform vendors. According to Microsoft’s own Entra identity documentation, passkeys come in two flavors: device-bound passkeys that never leave the physical device (Windows Hello, FIDO2 hardware keys like YubiKey) and synced passkeys that are encrypted and copied across every device linked to the same cloud account (Apple iCloud Keychain, Google Password Manager, or a synced password manager like 1Password or Bitwarden). Microsoft’s documentation lists minimum supported platforms as Windows 10 version 1903+, macOS 13 (Ventura)+, iOS 16+, and Android 9+, across Edge, Chrome, Firefox, and Safari.
In practice, passkey support is strongest among large technology, e-commerce, and financial-technology platforms that moved early: Apple ID (since 2022), Google Accounts and GitHub (since 2023), Microsoft personal accounts, Amazon, eBay, and PayPal (since 2023), according to tracking by independent passkey-adoption sites, which we’re citing as informal trackers rather than vendor-official sources. Google’s own support documentation confirms passkeys work for signing in to a Google Account and for “some third-party apps or services,” while Apple’s support documentation confirms passkey sync through iCloud Keychain, described as “end-to-end encrypted with strong cryptographic keys not known to Apple.”
Cross-device sign-in — using a passkey stored on your phone to log into a website open on your laptop — is also genuinely functional today, but it isn’t invisible. Both Google’s and Microsoft’s documentation describe this flow the same way: the two devices need Bluetooth and an internet connection, and the laptop displays a QR code the phone scans to complete a secure handshake. It works, but it is a deliberate extra step compared with just typing a saved password.
Where Passwords (or Traditional MFA) Still Win
Site coverage is still partial. The same independent tracking cited above lists several widely used services as not yet supporting passkeys as of early 2026, including Netflix (described as offering passwordless sign-in only via emailed link, not a FIDO2 passkey) and Spotify, plus “most traditional banks,” “most government services,” and “most healthcare portals.” Until a specific site or app explicitly documents passkey support, a password (ideally stored in a password manager, with MFA layered on top) remains the only option.
Moving a passkey between ecosystems is still clunky. A passkey synced into Apple’s iCloud Keychain isn’t automatically available inside Google Password Manager or a different password manager — you generally have to re-register a new passkey with the site rather than “export” the old one. The FIDO Alliance itself acknowledged this gap: in October 2024 it published new Credential Exchange Protocol (CXP) specifications specifically intended to let users securely move passkeys between providers, which indicates that broad, provider-agnostic portability was not yet solved as of that announcement. As of this writing, adoption of that exchange standard across every major platform is still in progress, so “I switched phones/ecosystems and lost easy access to my passkeys” remains a real support headache for some users.
All-device loss recovery varies by vendor and isn’t always simple. Apple’s own support documentation describes a specific, multi-step recovery process if someone loses every device holding their synced passkeys: it requires the iCloud account password, an SMS code sent to a registered phone number, the device passcode, and allows only a limited number of attempts (Apple’s page specifies a 10-attempt limit) before the escrowed credential is destroyed and the user has to contact Apple Support. That’s a real recovery path, but it’s more involved — and more dependent on having kept recovery details current — than simply remembering a master password.
Some organizational accounts restrict passkeys to a secondary role. Google’s own documentation notes that some Google Workspace accounts don’t allow passkey-only sign-in; in those configurations, a passkey can serve only as a second factor or recovery method rather than a full password replacement. Enterprise identity admins (on Microsoft Entra, for example) also control whether passkeys can be required at all — Microsoft’s Entra External ID documentation notes that passkeys currently can’t be enforced as a sole method through Conditional Access authentication-strength policies in that product.
Bottom Line
Passkeys are no longer experimental: FIDO Alliance’s own 2026 data shows they’re faster and more reliable at the point of sign-in than traditional MFA, and the major platforms (Apple, Google, Microsoft) have genuinely solid, documented support for creating, syncing, and using them. What hasn’t caught up yet is universal site coverage, frictionless portability between ecosystems, and dead-simple account recovery if every device is lost at once. For 2026, the realistic approach is a hybrid one: use passkeys everywhere a site offers them, and keep a password manager (with MFA) as the fallback for the sites that don’t.
FAQ
Are passkeys actually more secure than passwords? Yes, structurally — a passkey is a public/private key pair bound to the specific website’s domain, so it can’t be typed into a phishing site the way a password can. FIDO Alliance’s 2026 data also shows a higher real-world sign-in success rate (93%) than traditional MFA (78%).
What happens if I lose my phone? If your passkeys are “synced” (iCloud Keychain, Google Password Manager, or a synced password manager), they’re also present on your other linked devices, per Microsoft’s and Apple’s documentation. If you lose every device at once, recovery is possible but provider-specific and more involved than a password reset — Apple’s process, for example, requires your iCloud password, an SMS code, your device passcode, and allows a limited number of attempts.
Can I use a passkey stored on my phone to log into a site on a different computer? Yes, via a cross-device flow that uses Bluetooth and a QR code, as documented by both Google and Microsoft. It requires both devices to have Bluetooth and an internet connection on.
Do all websites support passkeys now? No. Independent tracking sites that monitor passkey rollout list major platforms like Apple, Google, Microsoft, Amazon, GitHub, and PayPal as supporting them, while noting that most traditional banks, many government and healthcare portals, and some major consumer platforms like Netflix and Spotify did not support FIDO2 passkeys as of early 2026.
Can I move my passkeys from one password manager or ecosystem to another? Not seamlessly in all cases yet. The FIDO Alliance published Credential Exchange Protocol specifications in October 2024 aimed at solving this, but universal support across every platform and password manager is still rolling out.
Password managers built for consumers and families solve a different problem than the ones businesses actually have. A company doesn’t just need encrypted vaults — it needs centralized admin controls, single sign-on (SSO) integration, automated user provisioning and deprovisioning, and audit logs that satisfy an IT or compliance team. 1Password Business, Bitwarden Teams/Enterprise, and Keeper Business/Enterprise are three of the most commonly deployed options for teams, and each takes a noticeably different approach to pricing and admin tooling. Here’s how they actually compare for a business buyer, not a household.
At a Glance
Tool
Entry Business Tier
Published Starting Price
SSO
Automated Provisioning
1Password Business
Business
$8.99/user/month (billed annually)
Yes (Okta, Entra ID, OneLogin, Duo)
Yes (Azure AD, Google Workspace, Okta, OneLogin, Rippling, JumpCloud)
SAML 2.0/OIDC (passwordless SSO on Enterprise only)
SCIM on both tiers; Directory Connector sync on both tiers
Keeper
Business / Enterprise
Reported from ~$2.00/user/month billed annually (see pricing note below); Enterprise is quote-only
SAML 2.0 SSO (named as an Enterprise-tier addition)
SCIM API; AD/LDAP sync (Enterprise)
Short Verdict
1Password Business is the most complete out-of-the-box package for a mid-size team that wants strong SSO/provisioning integrations and a mature admin console without self-hosting. Bitwarden is the best value for IT teams that are comfortable configuring their own SSO/SCIM setup and want the option to self-host or move up to Enterprise-only features like custom roles and account recovery. Keeper leans on a tiered add-on model — its core Business plan is the cheapest entry point of the three, but the features most relevant to IT administration (SCIM provisioning, AD/LDAP sync, RBAC) are reserved for the Enterprise tier, which is quote-only.
What Each Tool Actually Is
1Password Business is 1Password’s team-oriented tier, sitting above the personal and Teams Starter Pack plans. It’s built around shared vaults with role-based permissions, Watchtower security alerts that flag weak or breached credentials, and an admin console with custom policies and custom groups. For identity management, it integrates with Okta, Microsoft Entra ID, OneLogin, and Duo for SSO, and separately supports user and group provisioning through Azure AD, Google Workspace, Okta, OneLogin, Rippling, or JumpCloud — so new hires and leavers can be added or removed from vault access automatically rather than through manual admin work.
Bitwarden is the open-source-rooted password manager that built its business case on transparency and self-hosting flexibility. Both its Teams and Enterprise tiers include SCIM provisioning and a Directory Connector for syncing users from an existing directory, plus user groups and event/audit logs — meaning the provisioning basics aren’t locked behind the top tier the way they are with some competitors. What Enterprise adds on top is passwordless/SSO login with device trust, organization-wide policies, custom roles for granular admin permissions, an account recovery workflow, self-hosting, and Access Intelligence reporting.
Keeper positions its Business tier as “company-wide security, visibility and administration,” with shared team folders, delegated administration, and — notably — a free Keeper Family Plan bundled in for every licensed user, which the other two vendors don’t offer. Keeper’s Admin Console centralizes user, team, and device management across every tier. But the identity-management features a larger IT team will actually want — direct SCIM API provisioning, AD/LDAP sync, SAML SSO, and role-based access control — are described on Keeper’s own pricing page as part of the Enterprise tier, which is sold by quote rather than listed price.
Pricing Breakdown
Plan
Price
Billing
Notes
1Password Teams Starter Pack
$24.95/month flat
Monthly or $299.40/year
Covers up to 10 members; additional seats up to 20 total at $4.99/seat/month
1Password Business
$8.99/user/month
Billed annually
1-user minimum; full admin console, SSO, provisioning integrations
A pricing transparency note on Keeper: Keeper’s own public pricing page (keepersecurity.com/pricing) shows plan tiers and feature lists but does not display a specific per-user dollar figure for its Business plan when checked directly — pricing appears to be gated by region or account context. A third-party SaaS pricing-change tracker recorded Keeper’s Business Starter plan at $2.00 per user per month, billed annually, as of a March 2026 page capture. We’re including that figure for context, but a prospective buyer should confirm the exact current rate directly with Keeper sales before budgeting against it.
Pros
1Password Business: Broadest out-of-the-box SSO and provisioning integration list (Okta, Entra ID, OneLogin, Duo, Azure AD, Google Workspace, Rippling, JumpCloud) without needing the top-tier plan.
Bitwarden: SCIM provisioning and directory sync are included starting at the lower-priced Teams tier, not reserved for Enterprise, and open-source transparency plus self-hosting (Enterprise) appeal to security-conscious IT teams.
Keeper: Lowest reported entry price of the three, plus a free Family Plan bundled in per seat — a useful recruiting/retention perk most competitors don’t include.
Cons
1Password Business: At $8.99/user/month billed annually, it’s the most expensive of the three at the entry business tier.
Bitwarden: The features most useful to a growing company — custom roles, organization-wide policies, account recovery, passwordless SSO — are Enterprise-only, pushing the real “business-ready” price to $6.00/user/month.
Keeper: SCIM, AD/LDAP sync, SSO, and RBAC — the core IT-administration features — sit behind the quote-only Enterprise tier, and the Business tier’s own published pricing isn’t transparently listed.
Who It’s a Good Fit For
1Password Business suits a company that wants its password manager to plug directly into an existing Okta or Entra ID identity stack on day one, with minimal manual configuration, and that’s willing to pay a premium for that convenience. Bitwarden Teams suits a smaller, technically capable team that wants SCIM provisioning without paying for a top-tier plan, with the option to move up to Enterprise later if custom roles or self-hosting become necessary. Keeper suits a budget-conscious small business that primarily needs shared vaults and a free family-plan perk, provided it doesn’t yet need SSO or SCIM — or a larger company willing to go through a sales quote to get Keeper’s full Enterprise provisioning stack.
Who Should Look Elsewhere
A company that needs SSO and automated provisioning on day one but has a tight budget may find Bitwarden Enterprise ($6.00/user/month) a better fit than 1Password Business ($8.99/user/month). A business that wants fully transparent, published per-seat pricing with no “request a quote” step for any administration feature should be cautious with Keeper, since its most relevant business features currently sit behind a custom-quote tier.
Bottom Line
All three vendors can secure a business’s credentials; the real differentiator is how much of the IT-administration stack (SSO, provisioning, RBAC) is included at the entry business price versus locked behind a higher tier or a sales call. Bitwarden currently offers the most IT functionality per dollar at its Teams tier, 1Password offers the broadest ready-made integrations for a premium, and Keeper offers the lowest advertised entry cost but asks admin-focused buyers to go through Enterprise sales to get there.
FAQ
Do these business plans include a personal or family vault for employees? Keeper’s Business plan bundles a free Keeper Family Plan per user, according to its own pricing page. 1Password and Bitwarden separate personal and business vaults by plan rather than bundling a family plan automatically.
Which of these three supports SCIM provisioning at the lowest price? Based on each vendor’s published plan pages, Bitwarden includes SCIM provisioning starting at its Teams tier ($4.00/user/month). 1Password includes directory-based provisioning at its Business tier ($8.99/user/month). Keeper names SCIM provisioning as part of its Enterprise tier, which is quote-only.
Can any of these be self-hosted? Bitwarden Enterprise supports self-hosting. 1Password Business and Keeper Business/Enterprise are cloud-hosted SaaS offerings as described on their pricing pages.
Is there a minimum number of seats? 1Password Business lists a 1-user minimum on its pricing page. Bitwarden and Keeper’s business tiers don’t publish a stated minimum seat count on the pages reviewed here, though very small teams may be better served by starter-pack style plans.
Should I trust third-party pricing trackers over a vendor’s own page? No — always confirm current pricing directly with the vendor before budgeting. We flagged Keeper’s figure above specifically because its own pricing page didn’t display a dollar amount for us directly, while a third-party pricing-change tracker did.
Passkeys are now the default sign-in method pushed by most major apps, and that’s changed what people actually need from a password manager on their phone. Bitwarden, Apple Passwords, and Google Password Manager are the three most common options for everyday mobile users, but they differ sharply in cross-platform reach and how passkeys behave on iOS versus Android. This comparison focuses specifically on the mobile app experience and passkey support, based on each vendor’s own documentation.
At a Glance
Tool
Cost
Cross-platform mobile
Passkey support
Bitwarden
Free (Premium $19.80/year)
Dedicated apps on iOS and Android
Full passkey creation, storage, and biometric unlock on both platforms
Apple Passwords
Free with any Apple ID
iOS/iPadOS/macOS native; Windows via iCloud + Chrome/Edge
Full support on Apple devices; not natively usable as an Android passkey provider
Google Password Manager
Free with any Google Account
Native on Android; works on iOS 17+ through the Chrome app
Default Android passkey provider; iOS requires setting Chrome as the autofill provider
Short Verdict
If your household or team mixes iPhones and Android phones, Bitwarden is the only one of the three built as a genuinely cross-platform app from the start, and its free plan already includes passkey management. Apple Passwords is the most frictionless choice if everyone is on Apple hardware. Google Password Manager is the natural default for Android users, and it can now reach iOS through Chrome, though that setup takes an extra step most people never find on their own.
What Each Tool Actually Is
Bitwarden is a dedicated, open-source password manager with standalone mobile apps for iOS and Android, a browser extension, and desktop clients. Every account, including the free tier, includes passkey management and unlocking with biometrics, according to Bitwarden’s own pricing page. Its Premium tier adds an integrated authenticator, encrypted file attachments, emergency access, and security health reports for $1.65/month billed annually ($19.80/year); the Families plan covers up to six people for $3.99/month ($47.88/year) with 5 GB of shared storage.
Apple Passwords is Apple’s standalone password and passkey app, introduced with iOS 18, iPadOS 18, and macOS Sequoia (also available on visionOS 2). It syncs through iCloud Keychain, generates and autofills passwords, flags weak or reused ones, and lets you create a Shared Group to pass credentials and passkeys to family or trusted contacts. On Windows, there’s no Passwords app itself — instead, iCloud for Windows exposes the same passwords and passkeys inside Chrome or Edge. Apple’s own documentation does not describe an Android path for the app.
Google Password Manager is built into Android and Chrome rather than sold as a separate branded app. On Android, it’s enabled by default as the system passkey provider, and Android’s Credential Manager saves new passkeys there automatically unless the user picks a different provider (Android 14+ allows switching). On iOS and iPadOS, passkey support runs through the Chrome app: Chrome on iOS 16+ can use passkeys at all, and on iOS/iPadOS 17+ a user can go into system settings and set Chrome as the autofill provider so new passkeys land in Google Password Manager instead of Apple’s Keychain.
Up to 6 premium accounts, unlimited sharing, 5 GB personal + 5 GB family storage
Apple Passwords
$0
Included with any Apple ID; no separate paid tier
Google Password Manager
$0
Included with any Google Account; no separate paid tier
Pros
Bitwarden: True cross-platform parity — the same features are available whether you’re on iOS, Android, or desktop.
Apple Passwords: Deep OS-level integration means autofill and passkey creation feel instant and require no extra setup on Apple hardware.
Google Password Manager: Already the default on every Android phone, so there’s nothing to install for most Android users.
Cons
Bitwarden: Requires installing and actively choosing a third-party app rather than using what’s already on the phone.
Apple Passwords: Apple’s own documentation does not describe a native Android companion, which limits it for mixed-device households.
Google Password Manager: Reaching it on iOS requires manually setting Chrome as the autofill provider in Settings, a step most iPhone users never take.
Who It’s a Good Fit For
Anyone in a mixed-device household or a team where some people carry iPhones and others carry Android phones is best served by Bitwarden, since it’s the only one of the three with first-class, identical apps on both platforms, and its free tier already covers passkeys. Households fully inside Apple’s ecosystem will have the smoothest experience with Apple Passwords, since it needs no setup beyond having an Apple ID. Android-first users who occasionally touch an iPhone can get by with Google Password Manager, especially once Chrome is set as the iOS autofill provider.
Who Should Look Elsewhere
People who want zero setup and are fully committed to one ecosystem may not need Bitwarden’s extra app at all. iPhone-only users with no Android devices in the picture gain little from Google Password Manager’s iOS workaround. And anyone who wants built-in extras like an authenticator app, encrypted attachments, or emergency access will find both Apple Passwords and Google Password Manager more limited than Bitwarden Premium.
Bottom Line
For single-platform households, the built-in option — Apple Passwords on iOS, Google Password Manager on Android — is free, already installed, and good enough for most people. The moment a household or team spans both iOS and Android, Bitwarden is the more dependable choice, since it treats both platforms as equally first-class rather than one being the “native” experience and the other a workaround.
FAQ
Can I use Apple Passwords on an Android phone? Apple’s own support documentation covers iOS, iPadOS, macOS, visionOS, and iCloud for Windows (via Chrome/Edge), but does not describe an Android app or integration.
Does Google Password Manager work on an iPhone? Yes, through the Chrome app. On iOS/iPadOS 17 and later you can set Chrome as your autofill provider in system settings so new passkeys save to Google Password Manager instead of Apple’s Keychain.
Is Bitwarden’s free plan enough for passkeys? Yes. Per Bitwarden’s pricing page, passkey management and unlocking with biometrics are included on every account tier, including the free plan.
Which option is best for a family with mixed phones? Bitwarden’s Families plan (up to 6 accounts for $3.99/month) is built for exactly this case, since it works identically on iOS and Android rather than favoring one platform.
Do any of these charge for passkey support specifically? No. Passkey storage and use is a free, core feature across Bitwarden’s free tier, Apple Passwords, and Google Password Manager.
Every RPA vendor splits its robots into two categories: attended bots that work alongside a human, and unattended bots that run entirely on their own. The distinction isn’t just technical — it drives licensing cost, infrastructure needs, and which processes you can realistically automate first. This explainer breaks down what each type actually does, what vendors charge for them according to their own pricing pages, and how to decide which one a given process needs.
At a Glance
Attended Bots
Unattended Bots
Trigger
Started by a human, on demand
Runs on a schedule, event, or queue, with no human present
Typical licensing unit
Per user
Per bot / per robot
Example price (2026)
Microsoft Power Automate Premium: $15/user/month
Microsoft Power Automate Process: $150/bot/month; Hosted Process: $215/bot/month
Infrastructure
Runs on the employee’s own workstation
Needs a dedicated machine or virtual machine per concurrent run
Best for
Variable, judgment-heavy tasks a person still triggers or reviews
High-volume, fully-defined, rule-based processes that run the same way every time
What an Attended Bot Actually Does
An attended bot sits on a specific employee’s desktop and waits to be invoked, usually with a button click, a keyboard shortcut, or a trigger inside an application the person is already using. It then automates a defined sub-task, such as pulling data into a form, reformatting a document, or cross-referencing a record across systems, while the employee stays in the loop to handle exceptions or make a final judgment call. Because it only runs when a human starts it, an attended bot needs no dedicated server or virtual machine; it consumes the same workstation the employee is already using. Microsoft licenses this model directly: its Premium plan, at $15 per user per month (billed annually), bundles cloud flows with attended desktop flows under a single per-user price, according to Microsoft’s own Power Automate pricing page.
What an Unattended Bot Actually Does
An unattended bot runs on its own machine (physical or virtual) and executes without a person present to start it or watch it work. It’s typically triggered by a schedule, a queue item, or an event from another system, and it runs the same logic every time with no variation unless the underlying data changes in a way the bot wasn’t built to handle. Because it has to occupy a machine for the duration of its run, unattended automation is priced per bot rather than per user: Microsoft’s Process plan costs $150 per bot per month, and its Hosted Process plan, which adds a Microsoft-managed virtual machine so you don’t have to provision your own, costs $215 per bot per month, again per Microsoft’s own pricing page. A single bot can only run one unattended flow at a time, so running five processes concurrently around the clock means licensing five bots, not one.
How UiPath and Automation Anywhere Price the Same Split
UiPath doesn’t break attended and unattended pricing into separate line items the way Microsoft does. Its published Basic plan, starting at $25/month, bundles two robots with a small number of user seats (up to 5 Basic, 5 Plus, and 1 Pro user), without the pricing page specifying how many of those robots are attended versus unattended. Anything beyond Basic — the Standard and Enterprise tiers, which is where most production unattended automation actually runs — requires a custom quote from UiPath sales, so there’s no public per-robot rate to cite for serious unattended deployments.
Automation Anywhere is even less transparent: its own site publishes no pricing at all beyond a capped, free Community Edition, and the only way to get a quote for either attended or unattended bot licenses is to talk to sales. Third-party pricing research has surfaced old reference points — a 2020 press release describing a $750/month Cloud Starter Pack that included one unattended “Bot Runner” and one attended-capable “Bot Creator,” with additional unattended runners at $500/month and attended runners at $125/month — but those figures are more than five years old and Automation Anywhere’s current site gives no way to confirm whether they still apply. We’re flagging that explicitly rather than presenting dated numbers as current pricing.
The Real Trade-off: Cost vs Control
Attended automation is cheaper per seat and faster to deploy because it doesn’t need its own infrastructure, but it only saves time during the minutes an employee actively uses it, and it can’t run overnight or scale to volumes a person physically can’t trigger. Unattended automation removes the human bottleneck entirely and can run 24/7, but each concurrent process needs its own licensed bot and, in Microsoft’s case, potentially its own hosted virtual machine, so costs scale directly with how many processes you want running at once rather than with how many employees you have.
In practice, most organizations don’t choose one model exclusively. A common pattern is to start with attended bots on a handful of well-understood, high-friction tasks to prove value quickly and cheaply, then migrate the most stable, highest-volume of those processes to unattended bots once the logic is reliable enough to run without a human watching it.
When You Need Attended Automation
Attended bots fit processes where a person still needs to exercise judgment, handle exceptions, or satisfy a compliance requirement that a human sign off on the action. Customer service agents pulling customer data into multiple systems during a live call, underwriters assembling a loan file before making a decision, or finance staff reconciling an invoice flagged as unusual are all good candidates: the bot removes the repetitive data-handling, but the human stays accountable for the outcome.
When You Need Unattended Automation
Unattended bots fit processes that are fully rule-based, high-volume, and don’t require human judgment once the rules are defined: nightly batch reconciliation, invoice processing against a fixed set of validation rules, data migration between systems, or report generation that runs on a fixed schedule. If the process runs the same way every single time regardless of who’s watching, it’s a strong candidate to move off a person’s desktop and onto a dedicated unattended bot.
Bottom Line
Attended and unattended bots aren’t a better-or-worse choice; they’re priced and deployed differently because they solve different problems. Budget for attended automation per employee who’ll use it, and budget for unattended automation per process you want running independently, not per person — and when comparing vendors, check whether a platform publishes a real per-bot or per-user rate (as Microsoft does) or requires a sales call to find out (as UiPath’s higher tiers and Automation Anywhere do).
FAQ
Can one bot license cover both attended and unattended work? Not typically. Microsoft licenses them as separate plans (Premium for attended, Process/Hosted Process for unattended); check each vendor’s own pricing page, since bundling varies.
Do unattended bots need their own computer? Yes. An unattended bot needs a machine (yours or a vendor-hosted VM) dedicated to it for the duration of each run; one bot license generally covers one concurrent run.
Is attended automation always cheaper? Per seat, usually yes — Microsoft’s attended plan is $15/user/month versus $150+/bot/month for unattended — but attended automation only saves time while an employee is actively using it, so the comparison depends on volume, not just sticker price.
Which type should a new RPA program start with? Many organizations start with attended automation on a small number of high-friction tasks to prove value before investing in the infrastructure unattended bots require, though this varies by process maturity and in-house technical capacity.
Why don’t UiPath and Automation Anywhere publish per-bot prices like Microsoft? Both companies publish only entry-level or free-tier pricing; their Standard, Enterprise, and comparable paid tiers (where most unattended production work runs) require a custom quote, according to their own pricing and sales pages.
Picking a monorepo build tool is really two decisions at once: which task-running and caching engine fits your codebase, and whether you want a vendor-backed product with a hosted CI layer or a fully open, self-hosted system with no company behind it at all. Nx and Turborepo both come from venture-backed companies (Nx from Nrwl, Turborepo from Vercel) and increasingly compete on cloud-hosted CI acceleration. Bazel, Google’s original large-scale build system, sits apart as a free, open-source project with no paid tier whatsoever. Here’s how the three actually differ in 2026.
At a Glance
Tool
Best For
License
Hosted CI/Caching Pricing
Language Scope
Nx
TypeScript/polyglot monorepos wanting an integrated CI product
MIT (core)
Free Hobby tier; CI plans from $99/mo (beta pricing)
Large, polyglot, or multi-repo codebases needing reproducible builds at scale
Apache-2.0
No paid tier — fully open source and self-hosted
Java, C++, Go, Android, iOS, and more via rules
Short Verdict
Turborepo is the simplest on-ramp for a JavaScript/TypeScript monorepo: its remote cache is free on every Vercel plan, subject to fair-use limits, and setup is minimal. Nx goes further, adding an “affected” task graph, a plugin ecosystem, and an increasingly aggressive hosted CI product with its own usage-based pricing, still in beta as of this writing. Bazel is the odd one out — there’s no company selling you a hosted tier at all, which is exactly why large, polyglot organizations (Google’s own codebase among them) still reach for it despite its steeper learning curve.
What Each Tool Actually Is
Nx, maintained by Nrwl, is an MIT-licensed monorepo tool built in Rust for performance and extensible through TypeScript plugins, per its own GitHub repository. It caches task outputs, runs only the projects “affected” by a given change, and bundles an integrated CI product (Nx Cloud) that can distribute and self-heal pipeline runs. Nx Cloud’s pricing is unusual in that its CI Plan is explicitly marked “beta” with “$0 base fee during beta” even though the page separately states it “starts at $99/month” — worth confirming directly before budgeting against either figure.
Turborepo is an MIT-licensed build system for JavaScript and TypeScript codebases, written in Rust and now owned by Vercel. Its core feature is content-aware caching of previously run tasks (builds, tests, lints) so unchanged work is replayed instantly rather than re-executed, and that cache can be shared across a whole team and CI via Vercel’s Remote Cache. Vercel’s own pricing docs state plainly that “Vercel Remote Cache is free for all plans,” including Hobby, Pro, and Enterprise, subject to fair-use upload and request limits rather than a subscription fee.
Bazel is Google’s open-source build system, licensed under Apache-2.0 and maintained by the bazelbuild organization and community rather than sold as a product. Its own site frames the pitch as “Fast, Correct — Choose two,” emphasizing incremental builds that rebuild only what changed, using local and distributed caching, dependency analysis, and parallel execution, with multi-language support (Java, C++, Go, Android, iOS, and more) extended through a rules ecosystem. There is no hosted Bazel product from Google itself baked into the core tool — remote caching and remote execution exist as protocols that various third-party and self-hosted services implement.
Pricing Breakdown
Plan
Nx
Turborepo (Vercel)
Bazel
Free tier
Hobby: $0 — 50K monthly credits, up to 5 active contributors, External CI
Nx’s CI Plan (the product that actually runs your pipelines on Nx’s infrastructure, as opposed to just caching) is priced separately and is still in beta: it lists a “$0 base fee during beta” alongside a conflicting “starts at $99/month” statement, plus per-worker-minute compute rates (roughly $0.002–$0.016 depending on worker size) and per-task charges for things like cache restores and dynamic task packing. Turborepo’s story is simpler because Remote Caching itself carries no price tag on any Vercel plan — cached artifacts just expire automatically after 7 days, and the limits that exist are fair-use throughput caps, not billing tiers. Bazel has no pricing conversation to have at all; any cost comes from the compute you run it on or from third-party remote-execution services, not from Bazel itself.
Pros
Nx: A genuinely free Hobby tier plus a rich plugin ecosystem that extends well beyond JavaScript, with “affected” project detection built in from day one.
Turborepo: Minimal setup and a remote cache that’s free on every plan tier, which removes pricing friction entirely for teams already on Vercel.
Bazel: No vendor lock-in, no billing relationship of any kind, and proven correctness and scale across some of the largest codebases in the industry.
Cons
Nx: The CI Plan’s beta pricing page contains a direct contradiction between “$0 base fee during beta” and “starts at $99/month,” which makes it hard to predict real costs once the beta ends.
Turborepo: It’s JavaScript/TypeScript-focused, so polyglot codebases mixing in Go, Python, or Java services don’t get the same first-class task graph that Nx or Bazel offer.
Bazel: The steepest learning curve of the three by a wide margin — BUILD files, a custom query language, and a different mental model from typical package-manager-driven tooling.
Who It’s a Good Fit For
Turborepo fits JavaScript/TypeScript-only monorepos, especially teams already deploying on Vercel who want remote caching with essentially no configuration or billing overhead. Nx fits teams that want more built-in structure — generators, a plugin ecosystem, and dependency-graph visualization — and that are willing to evaluate its CI product on its own terms given the beta pricing caveats. Bazel fits large, multi-language organizations (often with build graphs spanning many repos or teams) that need guaranteed build reproducibility and are willing to invest in the tooling and ramp-up time it requires.
Who Should Look Elsewhere
Small, single-language JavaScript projects rarely need Bazel’s complexity and will be better served by Turborepo or Nx. Teams that want zero billing ambiguity should treat Nx’s CI Plan pricing cautiously until the beta language is resolved, or stick to its free Hobby tier and plain Nx Cloud caching. And teams not using Vercel for deployment at all may not get as much out of Turborepo’s Remote Cache integration as they would from Nx’s or Bazel’s more platform-agnostic caching options.
Bottom Line
For most JavaScript/TypeScript teams, Turborepo’s free remote caching is the lowest-friction starting point. Nx is worth it once you want more structure, cross-project dependency graphs, and are comfortable evaluating a CI product that’s still finding its final pricing. Bazel remains the right call when correctness and scale across multiple languages matter more than developer convenience — and it’s the only one of the three with literally no price tag to ever worry about.
FAQ
Is Turborepo tied exclusively to Vercel hosting? No — Turborepo itself is an open-source, MIT-licensed CLI that works with any hosting provider; Vercel’s free Remote Cache is an optional add-on, and Turborepo also supports a self-hosted or third-party remote cache via its Remote Cache SDK.
Does Bazel have any official paid support option from Google? Bazel’s own site and GitHub repository describe it only as an open-source project maintained by the bazelbuild organization and community, with no official Google-sold support tier mentioned.
What does Nx’s “affected” feature actually do? It analyzes your dependency graph to figure out which projects were actually touched by a given code change, so CI only builds and tests what could have broken, rather than the entire monorepo.
Can I use Nx and Turborepo’s caching ideas with Bazel? Bazel has its own long-standing local and remote caching and remote execution protocols that predate both Nx and Turborepo, so there’s no need to bolt either on — they solve the same caching problem differently.
Which tool has the lowest learning curve for a small team? Turborepo is generally the fastest to adopt for a JS/TS monorepo given its minimal configuration; Nx requires learning its plugin and generator conventions, and Bazel has by far the steepest ramp-up of the three.
Google has been designing its own AI accelerators since 2015, longer than any other hyperscaler, and by 2026 that program has produced two generations enterprises are actively deploying: Trillium (TPU v6e), generally available since late 2024, and Ironwood (internally TPU7x), Google’s seventh-generation chip announced in April 2025 and explicitly built for inference rather than training. The two chips mark a real architectural leap in a short span — roughly 2.5x the raw compute and up to 6x the memory capacity, per Google’s own published specifications. Here’s what actually changed under the hood, straight from Google Cloud’s own documentation.
At a Glance: Official Per-Chip Specifications
Spec (per chip)
TPU v5p
Trillium (TPU v6e)
Ironwood (TPU7x)
Peak compute (BF16)
459 TFLOPs
918 TFLOPs
2,307 TFLOPs
Peak compute (FP8)
459 TFLOPs
918 TOPs (Int8)
4,614 TFLOPs
HBM capacity
95 GiB
32 GiB (31.25 GiB usable)
192 GiB
HBM bandwidth
2,765 GBps
1,638 GBps
7,380 GBps
ICI bandwidth
1,200 GBps
800 GBps
1,200 GBps
Max chips per pod
8,960
256
9,216
Figures sourced directly from Google Cloud’s own TPU documentation. Note that Trillium’s per-chip HBM capacity (32 GiB) is lower than the older v5p’s (95 GiB) — Trillium was optimized differently, trading some per-chip memory for higher compute density and a design meant to pack more chips efficiently per pod, while Ironwood restores and substantially exceeds v5p-class memory capacity.
Trillium (TPU v6e): The Workhorse Generation
Per Google’s own documentation, Trillium delivers 918 TFLOPs of peak bf16 compute and 1,836 TOPs at Int8 per chip, backed by 32 GB of HBM (31.25 GiB usable after system and runtime reservations) at 1,638 GBps of bandwidth. Chips connect over a 2D-torus Inter-Chip Interconnect (ICI) fabric rated at 800 GBps bidirectional per chip across four ICI ports. A full Trillium Pod tops out at 256 chips (arranged 16×16, with 8 chips per host), delivering a pod-level 234.9 PFLOPs of bf16 compute, 102.4 TB/s of all-reduce bandwidth, and 3.2 TB/s of bisection bandwidth. Slice configurations range from a single chip up to the full 256-chip pod, with an 8-chip single-VM slice specifically optimized for inference workloads. Google’s documentation describes v6e as sharing design similarities with the earlier v5e generation, scaled up substantially in compute and networking.
Ironwood (TPU7x): Built for the “Age of Inference”
Ironwood, which Google’s own blog post calls “the first Google TPU for the age of inference,” pushes every major spec further. Per chip, it delivers 2,307 TFLOPs of bf16 compute and 4,614 TFLOPs at FP8 — roughly 2.5x Trillium’s bf16 throughput. Memory jumps to 192 GiB of HBM (6x Trillium’s capacity) at 7,380 GBps of bandwidth (about 4.5x Trillium’s), and ICI bandwidth rises to 1,200 GBps bidirectional across six links, 1.5x Trillium’s figure and matching the older v5p generation. A full Ironwood pod scales to 9,216 chips, organized as 144 cubes of 4x4x4, which Google rates at 42.5 exaflops of pod-level peak compute — a figure Google says is more than 24 times the roughly 1.7 exaflops-per-pod rating of El Capitan, which it describes as the world’s largest supercomputer. Google also claims a 2x improvement in performance-per-watt over Trillium, and says Ironwood is nearly 30x more power-efficient than Google’s original 2018 Cloud TPU, attributing part of that gain to liquid cooling that it says sustains up to twice the performance of standard air cooling under heavy load.
The “inference” framing is deliberate and specific: Google’s blog describes a shift from AI that responds to queries toward AI that proactively retrieves information and generates insights and multi-step reasoning on its own — the kind of workload Google calls “thinking models,” including large mixture-of-experts systems. Ironwood’s enhanced SparseCore, a dedicated unit for handling large embeddings efficiently, is aimed specifically at these larger, sparser model architectures, as well as at ranking and recommendation workloads in finance and science. Google states Ironwood chips can be combined via its Pathways software into pools of hundreds of thousands of chips working together, though the company’s blog post stops short of giving a maximum chip count for that combined configuration beyond the 9,216-chip single pod figure.
How the Two Generations Fit Together
Google doesn’t frame Ironwood as a strict replacement for Trillium; the two generations are positioned for different jobs. Trillium remains a capable, widely deployed general-purpose TPU generation with a smaller per-chip memory footprint tuned for cost-efficient scale-out. Ironwood is explicitly inference-first, with the memory capacity and bandwidth that large, parameter-heavy production models need to serve efficiently at scale, while also being capable of training. Both are available through Google Cloud as part of what Google calls its AI Hypercomputer architecture, which bundles the TPUs with Google’s specific networking, storage, and software stack rather than selling the chips as a standalone product the way a CPU or GPU vendor typically would.
Notably, Google’s own public materials for both chips avoid naming GPU competitors or giving direct GPU comparisons; the company’s competitive claims are made relative to its own earlier TPU generations and, for Ironwood, against the El Capitan supercomputer. That’s worth flagging for readers trying to benchmark TPUs directly against Nvidia or AWS silicon: Google has not published a like-for-like comparison, so any such comparison circulating elsewhere is a third-party estimate, not a Google-sourced figure.
Bottom Line
The jump from Trillium to Ironwood is one of the larger generational leaps in Google’s TPU history by its own published numbers — roughly 2.5x the compute, 6x the memory capacity, and a dedicated design orientation toward serving today’s largest reasoning and mixture-of-experts models efficiently rather than purely training smaller ones faster. For teams already on Google Cloud, the practical choice between the two generations should hinge on whether the workload is inference-heavy and memory-hungry (favoring Ironwood) or a more standard training/serving mix where Trillium’s wider availability and lower per-chip memory footprint remain a reasonable fit. For anyone evaluating TPUs against GPU or other custom-silicon alternatives, the key caveat is that Google has not published a direct, apples-to-apples comparison against any competing chip — all of the figures above are Google’s own, measured against its own prior generations.
FAQ
Is Ironwood the same as “TPU v7”? Google’s own technical documentation refers to it as TPU7x, while its marketing materials call it Ironwood and describe it as the seventh generation of Cloud TPU; both names refer to the same chip.
Why does Trillium have less HBM per chip than the older v5p? Per Google’s own published specs, Trillium (32 GiB) has less per-chip HBM than v5p (95 GiB); Google’s documentation frames v6e as sharing design lineage with the smaller v5e generation rather than v5p, reflecting a different scale-out design trade-off rather than a straightforward upgrade on every single spec.
How big is a full Ironwood pod? Up to 9,216 chips, arranged as 144 cubes of 4x4x4, rated by Google at 42.5 exaflops of peak pod-level compute.
Does Google compare Ironwood directly to Nvidia GPUs? No. Google’s official announcement and documentation compare Ironwood only to its own prior TPU generations and, for scale, to the El Capitan supercomputer — it does not publish a direct GPU comparison.
Can Trillium and Ironwood chips be combined into larger clusters? Google states that Pathways, its distributed-training software, can combine hundreds of thousands of Ironwood chips; the single-pod maximums (256 chips for Trillium, 9,216 for Ironwood) describe the largest tightly interconnected unit within one pod, not an absolute ceiling on total deployable chips.
Hiring across borders without opening a local legal entity usually means choosing an Employer of Record (EOR) or global payroll platform, and Deel, Remote.com, and Oyster are three of the most visible names doing it in 2026. Unlike most enterprise HR software, all three publish real prices for at least some of their plans — which makes a direct, sourced comparison possible. Here’s what each one actually charges and includes, pulled from their own pricing pages.
At a Glance
Tool
Best For
EOR Starting Price
Standout Feature
Deel
Companies that want hiring, contractor payments, and EOR in one platform with a hiring/sourcing layer
$599 per EOR employee/month
An integrated “Find talent” hiring layer ($14/worker/month) alongside EOR and contractor tools
Remote.com
Teams prioritizing indemnity protection and in-house local expertise
€553 per employee/month (annual contract)
Separately priced Global Payroll plan (€17/employee/month) for companies with their own entities
Oyster
Teams that want straightforward, all-in EOR pricing without a separate payroll SKU
$699 per employee/month
Misclassification risk protection (“Oyster Shell”) up to $500,000 bundled with contractor management
Short Verdict
Remote.com is the standout if you already have local entities in some countries and just need global payroll layered on top — its dedicated Global Payroll plan at €17 per employee per month is far cheaper than paying full EOR rates everywhere. Deel is the strongest all-in-one choice if you also want sourcing and candidate screening bundled with employment, not just payment and compliance. Oyster is the simplest to budget for if you want one EOR price with contractor protection built in and don’t need a separate low-cost payroll-only tier.
What Each Platform Actually Is
Deel organizes its pricing around three hiring motions rather than a single EOR product. Per Deel’s pricing page, “Find talent” ($14 per worker/month) covers job posting, AI screening, offer generation, and interview scheduling. “Hire contractors” runs $49 per contractor/month, or $325 per contractor of record/month if Deel takes on classification liability. “Hire employees” — the EOR tier — runs $599 per employee/month, covering full legal employment in 130+ countries, managed payroll and tax filings, global and U.S. benefits, and on-demand HR, legal, and tax expertise; a separate U.S. PEO option runs $125 per employee/month. Deel does not publish a standalone global payroll price, saying only that EOR fees cover payroll processing and tax filings.
Remote.com is the only one of the three to clearly separate EOR from global payroll as two distinctly priced products. Per Remote’s pricing page (shown in euros), EOR starts at €553 per employee/month on an annual contract and includes hiring in 90+ countries without a local entity, a dedicated onboarding specialist, local payroll, compliance safeguards, and localized benefits. Global Payroll, for companies that already have their own legal entities, is priced separately at €17 per employee/month and covers local gross-to-net calculation, tax filing and remittance, and time-off/timesheet/expense syncing. Remote also lists Contractor Management (€27/contractor/month), Contractor Management Plus (€91/contractor/month, with indemnity protection), Contractor of Record (€299/contractor/month), and U.S. PEO (€91/employee/month) — all with the core platform included at no separate base fee.
Oyster keeps its pricing structure the simplest of the three. Per Oyster’s pricing page, EOR runs $699 per employee/month (with annual discounts available) and covers compliant employment in 120+ countries, multi-country payroll in 120+ currencies, automated expense and time-off handling, and onboarding/offboarding specialists. Global Contractors runs $29 per contractor/month (free for the first 30 days), including instant contracts in 180+ countries, in-app identity verification, and a built-in misclassification analyzer. Oyster has no standalone global payroll plan — multi-country payroll is simply bundled into the EOR price. It also sells People Partner Services at $300/hour for project-based HR advisory, and an add-on called Oyster Shell that extends misclassification risk protection up to $500,000 in aggregate for Global Contractors customers.
Pricing Breakdown
Product
Deel
Remote.com
Oyster
Employer of Record (EOR)
$599/employee/mo
€553/employee/mo (annual)
$699/employee/mo
Global Payroll (own entity)
Not separately priced
€17/employee/mo
Not offered as standalone; bundled into EOR
Contractor management
$49/contractor/mo
€27–€91/contractor/mo
$29/contractor/mo
Contractor of Record
$325/contractor/mo
€299/contractor/mo
Not offered as a named tier
US PEO
$125/employee/mo
€91/employee/mo
Not offered
Pros
Deel: Hiring and candidate sourcing are built into the same platform as employment and payments, so you’re not stitching together an ATS separately.
Remote.com: A genuinely separate, much cheaper Global Payroll tier (€17/employee/month) exists for companies that already have their own foreign entities and don’t need full EOR.
Oyster: One clear EOR price covers multi-country payroll with no extra payroll SKU to figure out.
Cons
Deel: No published global payroll price for companies with their own entities — only full EOR pricing is clear.
Remote.com: Its EOR rate (€553/month on an annual contract) is priced in euros on the page reviewed here, which adds a currency-conversion step for U.S.-based budgeting.
Oyster: Has the highest listed EOR per-employee rate of the three ($699/month) and no separate, cheaper payroll-only option for companies with existing entities.
Who It’s a Good Fit For
Deel fits companies building out international teams from scratch who want sourcing, contracting, and employment in one system rather than connecting a separate ATS. Remote.com fits companies that already operate legal entities in some countries and want to add EOR only where they lack one, while using its cheaper Global Payroll tier everywhere they already have a presence. Oyster fits teams that want one predictable EOR line item and value its bundled misclassification protection on the contractor side.
Who Should Look Elsewhere
Companies that already have local entities everywhere they hire have little reason to pay full EOR rates with any of the three — Remote.com’s dedicated Global Payroll plan is the clearest fit for that situation, and the others don’t offer an equivalent standalone tier. Very small teams hiring only one or two contractors abroad may find EOR-oriented platforms like these more infrastructure than they need, compared with a simple contractor-payment tool.
Bottom Line
On listed price alone, Remote.com’s EOR (€553/month) undercuts Deel ($599/month) and Oyster ($699/month), and its separate, far cheaper Global Payroll tier is a real differentiator for companies with existing entities. Deel’s advantage is breadth — sourcing, contracting, and employment in one system — while Oyster’s is simplicity and bundled contractor risk protection. None of these prices include potential setup costs, benefits add-ons, or country-specific surcharges, so get a country-by-country quote before committing.
FAQ
Which platform is cheapest for full EOR employment? Based on each vendor’s own published rate, Remote.com’s €553/employee/month (on an annual contract) is lower than Deel’s $599/employee/month and Oyster’s $699/employee/month, though currency differences mean the real comparison depends on your local exchange rate.
Do any of these offer global payroll without full EOR? Yes — Remote.com is the only one of the three with a clearly separate, standalone Global Payroll plan (€17/employee/month) for companies that already have their own legal entity in a given country. Oyster bundles payroll into its EOR price with no standalone option; Deel does not publish a standalone global payroll rate.
What does “Contractor of Record” mean, and which platforms offer it? It means the platform itself holds the contract and pays the contractor directly, taking on misclassification liability. Both Deel ($325/contractor/month) and Remote.com (€299/contractor/month) offer this as a named tier; Oyster’s pricing page reviewed here does not list an equivalent standalone tier.
Does Deel include recruiting tools? Yes. Deel’s “Find talent” tier, priced at $14 per worker/month, includes job posting, AI screening, offer generation, and interview scheduling — a hiring layer that Remote.com and Oyster do not list as part of their core pricing.
Are there extra fees beyond the listed per-employee price? Possibly. Oyster’s page notes a refundable deposit for EOR team members and a currency-conversion fee if you pay in a currency different from the contract currency. Remote.com’s and Deel’s pages reviewed here did not provide complete answers on setup or deposit fees, so confirm directly with each vendor before signing.
Small teams outgrow shared spreadsheets and Slack threads fast, and the three tools most of them evaluate next are Asana, ClickUp, and Monday.com. All three handle tasks, timelines, and basic reporting, but they price and package things differently enough that the “right” choice really depends on team size and how much structure you want out of the box. Here’s what each one actually costs and includes, based on their own 2026 pricing pages.
Asana’s Starter plan is the most straightforward pick for a small team that wants clean task management without a steep learning curve. ClickUp packs in the most features per dollar on its Core plan, but that configurability means more setup time. Monday.com sits in between on price but requires a minimum of 3 paid seats on every paid tier, which can push the real monthly cost higher than the advertised per-seat rate for very small teams.
What Each Tool Actually Is
Asana is a task and project management tool built around lists, boards, timelines, and goals, with a strong focus on readability — it’s often chosen by teams that found other tools too cluttered. Its free Personal plan caps out at 2 users, and paid plans add Gantt-style timelines, reporting dashboards, unlimited automations, and forms, plus a modest allowance of built-in AI requests per user.
ClickUp markets itself as an all-in-one workspace: tasks, docs, chat, whiteboards, and goals inside one app with a large number of configurable views. Its free plan has no hard user cap but limits storage and some features; the entry paid plan was recently renamed from “Unlimited” to “Core” on ClickUp’s own pricing page, and sits below a “Business” tier and a high-end “Max” tier aimed at AI-heavy workflows.
Monday.com is a visual work management platform built around color-coded boards and columns, with a large library of templates for marketing, CRM, HR, and dev-adjacent workflows. Its free plan is capped at 2 seats, and every paid plan (Basic, Standard, Pro) requires a minimum of 3 seats, so a 2-person team moving to a paid plan effectively pays for a third seat it may not use.
Pricing Breakdown
Plan
Price (annual billing, per user/month)
Notes
Asana Personal
Free
Capped at 2 users
Asana Starter
$10.99 ($13.49 billed monthly)
No seat cap; timelines, dashboards, forms
Asana Advanced
$24.99 ($30.49 billed monthly)
Adds portfolios, goals, resource management
ClickUp Free Forever
$0
No stated user cap; feature/storage limits apply
ClickUp Core
$9 (promotional; list price $12)
Monthly-billed price not published on ClickUp’s current pricing page
ClickUp Business
$17 (promotional; list price $25)
Adds advanced automation and reporting
Monday.com Free
$0
Up to 2 seats
Monday.com Basic
$9/seat
Minimum 3 seats
Monday.com Standard
$12/seat
Minimum 3 seats; adds timeline/Gantt and automations
Monday.com Pro
$19/seat
Minimum 3 seats; adds time tracking and formula columns
Note: ClickUp’s pricing page shows a “Monthly / Yearly” toggle but the monthly-billed per-user rates for Core and Business weren’t shown in the fetched page content, so only the annual-billed figures above are confirmed directly from ClickUp.com. Monday.com’s FAQ states paid plans “start from 3 users,” so very small teams should budget for 3 seats minimum even if only 2 people will use the account.
Pros
Asana: Clean, uncluttered interface that’s quick for new hires to pick up with minimal training.
ClickUp: One subscription covers tasks, docs, and chat, which can reduce the number of separate tools a small team pays for.
Monday.com: Large template library makes it fast to stand up a working board for a new process without building from scratch.
Cons
Asana: Free plan is limited to just 2 users, so most small teams will need a paid plan almost immediately.
ClickUp: The sheer number of views, fields, and settings can be overwhelming to configure well for a brand-new team.
Monday.com: Every paid plan requires a minimum of 3 seats, which inflates the effective cost for 2-person teams.
Who It’s a Good Fit For
Small teams that want task management to just work, without a lot of setup, tend to do well with Asana’s Starter plan. Teams that want to consolidate several tools — task tracking, docs, and simple chat — into one subscription are the best fit for ClickUp, especially once they’re willing to invest some time in setup. Teams with at least 3 people who want a highly visual, color-coded way to track work across departments (marketing, sales, ops) tend to prefer Monday.com’s board-based approach.
Who Should Look Elsewhere
Teams of exactly 2 people on a tight budget may find Monday.com’s 3-seat minimum an unnecessary cost and should look at Asana’s or ClickUp’s free tiers instead. Teams that want a tool to work well immediately with minimal configuration may find ClickUp’s depth of options more friction than benefit. And teams that need heavy native CRM or sales pipeline features will outgrow all three and should look at a dedicated CRM instead.
Bottom Line
For most small teams, Asana offers the easiest on-ramp and ClickUp offers the most value once you’re willing to configure it. Monday.com is a strong visual option for teams of 3 or more, but its seat minimum makes it a poor fit for very small teams. None of the three is categorically “best” — the deciding factor is usually how much structure your team wants out of the box versus how much it wants to build itself.
FAQ
Can a 2-person team use any of these for free? Yes. Asana’s Personal plan and Monday.com’s Free plan both cap at 2 users, and ClickUp’s Free Forever plan has no stated user cap, though all three free tiers come with feature and storage limits.
Does ClickUp’s “Unlimited” plan still exist? As of ClickUp’s current pricing page, the entry paid tier is named “Core,” priced at a promotional $9/user/month (list price $12) billed annually; some older third-party guides still refer to it by its former name, “Unlimited.”
Why does Monday.com require 3 seats minimum? Per Monday.com’s own pricing FAQ, paid plans “start from 3 users,” regardless of how many people will actually use the account.
Which tool has the best built-in automation on its cheapest paid plan? Asana’s Starter plan includes unlimited automations; Monday.com’s automation features scale up starting at the Standard tier; ClickUp’s automation depth increases from Core to Business.
Do any of these charge extra for AI features? Asana includes a limited number of AI requests per user on paid plans and sells additional AI credits separately; ClickUp sells its Brain AI assistant as an add-on priced separately from the base per-user fee.
Oracle entered the hyperscale AI infrastructure race later than AWS, Azure, and Google Cloud, and its strategy for closing that gap has been consistent: lean hard into bare-metal GPU access, undercut the competition on price, and build networking and data-center campuses sized for the largest AI training runs anyone is attempting. By late 2025, that strategy had a name — OCI Zettascale10 — and a scale that Oracle says reaches hundreds of thousands of GPUs across gigawatt-class data-center campuses. Here’s what’s verifiable about how OCI’s GPU infrastructure is actually built, and how its public positioning against AWS and Azure holds up.
At a Glance
Dimension
OCI detail
Max GPUs per Supercluster
Up to 131,072 (B200/GB200); 65,536 (H200); 16,384 (H100); 16,384 (AMD MI300X)
Zettascale10 target scale
Up to 800,000 Nvidia GPUs across multiple gigawatt-scale campuses
Zettascale10 peak performance
Up to 16 zettaFLOPS (Oracle says 10x its first Zettascale cluster, baseline not restated)
Cluster networking
RDMA, up to 3,200 Gb/sec bandwidth, microsecond-level latency (bare metal)
GPU access model
Bare metal (no hypervisor overhead) for NVIDIA and AMD instances — a claimed OCI differentiator
Example on-demand price
AMD MI300X at $6/GPU-hour, same price in every region, no long-term commitment required
Flagship deployment
Stargate campus, Abilene, Texas, built with OpenAI
Zettascale10 availability
Orders open now; general availability targeted for H2 2026
The Core Bet: Bare Metal Access as a Differentiator
OCI’s own GPU and AI infrastructure page frames its core differentiator plainly: Oracle says it is the only major cloud provider offering bare-metal instances with both Nvidia and AMD GPUs, free of the virtualization overhead that comes with running on a hypervisor. That matters for CUDA-heavy training workloads where every bit of memory bandwidth and interconnect latency affects wall-clock training time, and it’s also the mechanism behind Oracle’s price claims — Oracle’s own page states that other cloud providers’ comparable GPU instances can run up to 220% more expensive, based on on-demand pricing it dated to June 2024. That comparison is now well over a year old by late 2026 and both AWS and Azure have since adjusted GPU pricing and instance options, so treat the specific “220%” figure as dated context rather than a current, up-to-the-minute comparison.
Oracle’s GPU lineup spans current and prior Nvidia generations — Blackwell, H200, H100, L40S, A100, and A10 — plus GB200 Grace Blackwell Superchips used in its largest superclusters, and AMD’s Instinct MI300X (192 GB of memory per GPU) with MI355X also listed as becoming available. On the scale side, Oracle’s published Supercluster maximums are tiered by GPU generation: up to 131,072 GPUs for B200/GB200 configurations, 65,536 for H200, and 16,384 each for H100 and AMD MI300X, all connected over RDMA networking rated at up to 3,200 Gb/sec with microsecond-level latency on bare-metal instances.
Zettascale10: Scaling Past 100,000 GPUs
Oracle’s October 2025 announcement of OCI Zettascale10 pushed the strategy further: a cluster architecture connecting “hundreds of thousands” of Nvidia GPUs across multiple data centers, with initial deployments targeting up to 800,000 GPUs and up to 16 zettaFLOPS of peak performance — a figure Oracle described as 10 times the output of its first Zettascale cluster from September 2024, though the release didn’t restate that earlier cluster’s absolute numbers for a direct comparison. The networking layer behind this is Oracle’s own Acceleron RoCE (RoCEv2) architecture, which uses switching built into GPU network interface cards to route traffic across multiple isolated network planes — so a failure in one plane doesn’t take down the cluster — combined with a flatter two-tier network design (down from three tiers) intended to make GPU-to-GPU latency more uniform across a large cluster, and Linear Pluggable and Linear Receiver Optics to cut power and cooling costs at 400G/800G networking speeds.
Physically, Oracle is building these clusters inside gigawatt-scale data-center campuses, with multiple campuses sited within a two-kilometer radius of each other to keep latency low across what is effectively one giant logical cluster. The flagship example is the Stargate campus in Abilene, Texas, built jointly with OpenAI; OpenAI’s own VP of Infrastructure, Peter Hoeschele, is quoted in Oracle’s release saying the custom RoCE design “maximizes fabric-wide performance at gigawatt scale.” Oracle is taking orders for Zettascale10 capacity now, with general availability targeted for the second half of 2026.
How This Actually Stacks Up Against AWS and Azure
It’s worth being direct about a gap in Oracle’s own materials: Oracle’s Zettascale10 press release does not mention AWS or Azure by name at all — the competitive comparison exists mainly on OCI’s separate GPU product page, in the form of the pricing claims above, not in Oracle’s biggest infrastructure announcements. Oracle’s actual competitive argument, pieced together from its own public materials, rests on three legs: lower claimed GPU-instance pricing (OCI’s own page cites MI300X at a flat $6/GPU-hour with no regional variation or commitment requirement), bare-metal access that avoids virtualization overhead AWS and Azure’s standard GPU instances typically carry, and raw scale-out ambition through Zettascale10’s multi-campus design. What Oracle’s materials don’t provide is an apples-to-apples benchmark against a specific AWS or Azure supercluster offering, so the “better than AWS and Azure” framing should be read as Oracle’s own pricing and architecture claims rather than an independently verified head-to-head result.
Bottom Line
Oracle’s GPU strategy is coherent and aggressive: bare-metal access, a specific and public pricing undercut argument, custom RoCE networking engineered for massive, failure-tolerant GPU fabrics, and gigawatt-scale campuses built in partnership with anchor customers like OpenAI. Whether that adds up to a genuine lead over AWS or Azure for a given AI workload depends heavily on specifics — region, GPU generation, commitment terms — that Oracle’s own public materials don’t fully spell out in a current, side-by-side comparison. For organizations evaluating OCI specifically for large-scale GPU training, the Zettascale10 roadmap and bare-metal architecture are real and substantive; the specific cost-savings percentages Oracle advertises are worth re-verifying against current, same-day pricing from all three providers rather than taking at face value.
FAQ
What is OCI Zettascale10? It’s Oracle’s next-generation AI supercluster architecture, announced in October 2025, designed to connect hundreds of thousands of Nvidia GPUs — up to 800,000 in initial deployments — across multiple gigawatt-scale data-center campuses, reaching up to 16 zettaFLOPS of peak performance per Oracle’s own figures.
What does “bare metal” GPU access actually mean, and why does Oracle emphasize it? It means the GPU instance runs without a virtualization/hypervisor layer in between, which Oracle argues removes performance overhead; Oracle positions this as a key differentiator versus AWS and Azure, whose standard GPU offerings more commonly run virtualized.
Is Oracle’s GPU pricing actually cheaper than AWS and Azure? Oracle’s own page claims competitors can be up to 220% more expensive, but that figure is based on pricing data dated to June 2024, so it should be re-verified against current pricing rather than treated as an up-to-date comparison.
When will Zettascale10 be generally available? Oracle is taking orders now (as of its October 2025 announcement), with general availability targeted for the second half of 2026.
Does OCI only support Nvidia GPUs? No. OCI also offers AMD Instinct MI300X (and lists MI355X as becoming available) alongside its Nvidia lineup, which spans Blackwell, H200, H100, L40S, A100, and A10.
WebAssembly (Wasm) was originally pitched as a faster way to run compiled code inside the browser alongside JavaScript. That’s still true, but it’s no longer the interesting part. The official WebAssembly specification was deliberately written to support “non-web embeddings” from the start, and a companion standard — the WebAssembly System Interface (WASI) — has spent the last several years building out exactly what Wasm needs to run well outside a browser tab: on servers, at the network edge, and inside plugin systems for products that have nothing to do with the web.
At a Glance
Use Case
What Wasm Provides
Real Example
Server-side functions
A sandboxed, near-native-speed runtime for untrusted or multi-tenant code
Shopify Functions (checkout customization, compiled from Rust or other languages)
Edge computing
Fast-starting, per-request isolated execution close to users
Fastly Compute (custom code compiled to Wasm, run with per-request isolation)
Plugin systems
A safe way to run third-party extensions without native code access
Extism, an open-source, cross-language Wasm plugin framework
Portable system interfaces
WASI: a standard, capability-based API for files, sockets, and clocks across hosts
WASI 0.2/0.3 (Preview 2/3) and the Component Model
What WebAssembly Actually Is
Per the official specification at webassembly.org, “WebAssembly (abbreviated Wasm) is a binary instruction format for a stack-based virtual machine,” designed as a portable compilation target for languages like C, C++, and Rust. The spec names four core design goals: it should be efficient and fast, aiming for near-native execution speed; safe, running inside a sandboxed, memory-safe environment; open and debuggable, with a human-readable text format alongside the binary one; and portable, versionless, and backward-compatible across hosts. Critically, the spec states plainly that Wasm “supports deployment on the web… as well as non-web embeddings,” and that “WebAssembly also supports non-web embeddings” through a separate specification track.
WASI: The Standard That Makes “Beyond the Browser” Possible
A browser already gives Wasm code access to the DOM and Web APIs. Outside a browser, Wasm needs a different, standard way to talk to files, sockets, clocks, and other system resources — that’s what the WebAssembly System Interface (WASI) specifies. WASI is developed as a standards-track effort by the WASI Subgroup inside the W3C WebAssembly Community Group, and it has shipped three milestone releases so far, nicknamed Preview 1, 2, and 3 (WASI 0.1, 0.2, and 0.3). WASI 0.3 is the newest, adding native async support built around stream<T> and future<T> types. WASI works alongside the Component Model, a related specification for building interoperable, composable Wasm applications, and both are explicitly designed for a wide set of non-browser workloads: “web apps, plugins, serverless functions, database UDFs, embedded controllers, and sidecar networking filters,” per WASI’s own site. The security model is capability-based: a WASI module starts with zero ambient authority and can only touch what its host explicitly grants it — a meaningfully different default than a typical OS process.
Real Production Use Case: Server-Side Plugin Execution (Shopify Functions)
Shopify Functions is one of the clearest production examples of Wasm running business logic on a server rather than in a browser. Merchants (or third-party app developers) write custom logic — generating discount types, defining delivery options, or validating carts — compile it to Wasm, and Shopify runs it inside checkout. Shopify’s own developer documentation states that functions can be written in “any language that can compile to WebAssembly,” though “Shopify strongly recommends Rust as the most performant language choice.” Because the code runs inside a tightly bounded sandbox, Shopify can enforce hard resource limits directly on the compiled binary: up to 11 million Wasm instructions per execution for carts with up to 200 line items (scaling for larger carts), a 256 KiB compiled binary size cap, 10 MiB of linear memory, and 128 kB of input data. That’s the sandboxing and portability promise of Wasm doing real work: Shopify can run merchant-submitted code inside its own checkout flow without giving that code arbitrary access to the host system.
Real Production Use Case: Edge Computing (Fastly Compute)
Fastly Compute lets developers compile custom code to WebAssembly and run it across Fastly’s edge network, with each incoming request getting its own isolated Wasm instance. According to Fastly’s own product documentation, the platform is built around “per-request isolation and lightweight sandboxing,” and Fastly specifically credits its work with the Bytecode Alliance — the same open-source organization that stewards WASI and the Component Model — for expanding language support over time. The appeal at the edge is straightforward: Wasm modules are small and fast to instantiate compared to spinning up a full container or VM per request, which matters when a request might be served from any one of dozens of globally distributed points of presence.
Real Production Use Case: Plugin Systems
Before Wasm, letting end users or third parties extend a product with “plugins” usually meant either a restrictive scripting language or accepting the security risk of native code. Wasm’s sandboxing model is well suited to this problem, which is the whole premise behind Extism, an open-source project that describes itself as “the cross-language framework for building with WebAssembly” and “the open source, universal plug-in system.” Extism ships host SDKs for more than a dozen languages — including Rust, Go, Python, Java, Node, and .NET — so a plugin author can write in one language and a host application written in a completely different language can load and run that plugin safely, with the Wasm sandbox enforcing the boundary.
A Minimal WASI Example
To illustrate what a non-browser Wasm module looks like in practice, here’s a minimal Rust function compiled against the wasm32-wasip1 target. It takes no network or filesystem access by default — under WASI’s capability-based model, a host must explicitly grant any such access:
// src/main.rs
// Build with: rustup target add wasm32-wasip1
// cargo build --release --target wasm32-wasip1
// Run with: wasmtime target/wasm32-wasip1/release/greet.wasm -- "Ada"
use std::env;
fn main() {
let args: Vec<String> = env::args().collect();
let name = args.get(1).map(|s| s.as_str()).unwrap_or("World");
// WASI grants no filesystem or network access unless the host
// explicitly configures it — this module only touches stdout.
println!("Hello, {}! This ran as a sandboxed Wasm module.", name);
}
Compiled this way, the resulting .wasm file can run unmodified on any WASI-compliant host — a CLI runtime like Wasmtime, an edge platform, or a plugin host like Extism — without recompiling for a specific operating system, which is the portability guarantee the specification is built around.
Trade-Offs to Know Before Betting on Wasm Outside the Browser
None of this makes Wasm a universal replacement for containers or native code. WASI itself is still mid-rollout — 0.3 only recently added native async support, and tooling maturity varies a lot by language and target. Resource limits like Shopify’s instruction-count cap exist precisely because Wasm sandboxes, while safe, still need an explicit ceiling to stop runaway execution. And server-side Wasm’s ecosystem of libraries and system bindings is still thinner than what’s available to a normal server process in Node, Python, or Go — code that depends heavily on OS-specific APIs or mature native libraries may not have a clean WASI equivalent yet.
Bottom Line
WebAssembly’s browser roots get most of the attention, but its design goals — sandboxed safety, near-native speed, and strict portability — turn out to matter just as much, if not more, outside the browser. WASI gives Wasm a standard way to talk to the operating system; real products like Shopify Functions and Fastly Compute are already running untrusted or third-party logic on servers and at the edge because of it; and frameworks like Extism are turning that same sandboxing model into a general-purpose plugin architecture. It’s not a drop-in replacement for containers yet, but it’s no longer a browser-only technology either.
FAQ
Is WebAssembly only for languages like C, C++, and Rust? No — the spec defines Wasm as a general compilation target, and tooling now exists for many languages, though support quality and the size of the compiled output still vary a lot by language and toolchain.
What’s the difference between WASI and the Component Model? WASI defines the system-facing APIs (files, sockets, clocks, and so on); the Component Model is a separate specification for building interoperable, composable Wasm applications, and WASI can be implemented by either plain Wasm modules or Component Model components.
Does Wasm outside the browser have access to the filesystem or network by default? No. WASI uses a capability-based security model: a module starts with no ambient authority and can only access what the host explicitly grants.
Why would an edge platform like Fastly use Wasm instead of containers? Fastly’s own documentation points to per-request isolation and lightweight sandboxing as the draw; Wasm modules are generally smaller and faster to instantiate than spinning up a full container per request.
Is WASI finished, or still changing? Still changing. As of this writing, WASI has shipped three milestone releases (0.1 through 0.3), with 0.3 adding native async support — it remains an active, standards-track effort inside the W3C WebAssembly Community Group.
Onboarding is easy to underrate until it’s broken: a new hire’s first two weeks shape whether they feel set up to succeed or already regretting the move. Workday, BambooHR, and Rippling all sell onboarding, but as very different kinds of product — a dedicated enterprise module, a feature folded into a broader HRIS, and a fast, app-provisioning-driven workflow. This comparison looks specifically at each platform’s onboarding capability, not its general HR feature set, which is where this guide differs from a broader HRIS comparison.
At a Glance
Tool
Best For
Onboarding Pricing
Standout Onboarding Feature
Workday Onboarding
Large enterprises already on Workday HCM
Not published; part of a Workday HCM contract
Preboarding tied to live learning, recruiting, and HCM data in one system
BambooHR Onboarding
Small and mid-size businesses wanting onboarding bundled with their HRIS
Included in Core, Pro, and Elite plans (from $10–$10.25/employee/month)
Self-paced new hire packets that pre-fill from ATS candidate data
Rippling Onboarding
Companies that want new hires working in their actual tools within minutes
Not separately published; bundled into Rippling’s modular per-employee pricing
Automatic app provisioning (e.g., Slack) and sub-two-minute setup claims
Short Verdict
BambooHR offers the most complete, document-and-checklist-driven onboarding experience for a small or mid-size business, with templates, e-signature, and automatic syncing into the employee record. Rippling’s onboarding is narrower but faster where it matters most day-to-day: getting a new hire’s accounts and apps working almost immediately. Workday Onboarding is the deepest option on paper — tying preboarding to live learning and recruiting data — but it is realistically only available to organizations already committed to the full Workday HCM suite.
What Each Onboarding Module Actually Is
Workday Onboarding, per Workday’s own product page, starts with preboarding once an offer is accepted, sharing key content before day one. It centralizes onboarding tasks alongside learning and recruiting data in one self-service hub, so new hires aren’t bouncing between systems. The page highlights “Day One readiness” through role-specific content, onboarding insights for measuring and optimizing the process over time, and AI-powered progress tracking that generates recommendations for each new hire. It also links into Workday Journeys for ongoing, concierge-style support through later events like promotions or role changes. No pricing is published; access requires a Workday HCM contract and a sales conversation.
BambooHR Onboarding is bundled into every pricing tier rather than sold separately. Per BambooHR’s onboarding page, the module lets new hires start before their first day through pre-onboarding packets and self-paced onboarding, and supports electronic signatures for tax forms, direct deposit, and similar paperwork. Candidate data from BambooHR’s own ATS pre-fills the “Add Employee” form, so HR doesn’t re-enter information already collected during hiring. Customizable checklists assign and automate tasks across teams, a visual progress dashboard tracks packet completion, and pre-built templates can be tailored by role and work mode. A “Get to Know You” welcome email is built in to help new hires connect with teammates before day one, and all onboarding data syncs automatically into the permanent employee record.
Rippling Onboarding is the most narrowly scoped of the three but focuses heavily on operational speed. Per Rippling’s onboarding page, the platform automates document collection and eSignature requests, and claims employees and contractors can be onboarded “in 90 seconds.” Its most distinctive feature is one-click app access and automatic provisioning — the page specifically cites instantly adding new hires to Slack and giving one-click access to tools like Zoom or Teams. The page frames this under “Delight your employees with a seamless experience” but gives limited detail on document templates, checklists, or progress tracking compared to BambooHR’s page.
Pricing Breakdown
Tool
Is Onboarding a Separate Line Item?
Starting Cost Context
Workday Onboarding
No — included within a Workday HCM enterprise contract
Not published; enterprise quote only
BambooHR Onboarding
No — included in every BambooHR plan
From $10–$10.25/employee/month (Core plan), or a flat $250/month for companies with 25 or fewer employees
Rippling Onboarding
No standalone price shown; bundled into Rippling’s modular pricing
Rippling’s overall plans start “from $8 per employee per month” plus a monthly base fee
None of the three vendors sell onboarding as an independently priced add-on with its own published rate — it’s either folded into an HRIS tier (BambooHR), bundled into modular per-employee pricing (Rippling), or part of a broader enterprise HCM contract (Workday). Budgeting for “onboarding software” alone, separate from the rest of the HR platform, isn’t realistic with any of these three.
Pros
Workday Onboarding: Preboarding content and tasks draw on live recruiting, learning, and HCM data already in the system, rather than a separate onboarding database.
BambooHR Onboarding: New hire packets pre-fill directly from ATS candidate data, cutting duplicate data entry between hiring and onboarding.
Rippling Onboarding: Automatic app provisioning means a new hire can be working in Slack and other tools almost immediately, not after a separate IT ticket.
Cons
Workday Onboarding: Not available as a standalone purchase — it only makes sense within a full Workday HCM deployment, and no pricing is published anywhere.
BambooHR Onboarding: It’s a feature within the HRIS rather than a specialized onboarding product, so highly complex, multi-department onboarding workflows may outgrow its checklist model.
Rippling Onboarding: Its own page gives far less detail on document templates, role-based personalization, and progress tracking than BambooHR’s does.
Who It’s a Good Fit For
BambooHR fits small and mid-size companies that want onboarding tightly connected to hiring data and a clean paper trail of signed documents and completed tasks. Rippling fits companies where IT provisioning speed is the biggest pain point — teams hiring remote or distributed employees who need working accounts on day one, not day three. Workday Onboarding fits large enterprises that are already running Workday HCM and want onboarding data to live alongside learning, recruiting, and workforce data without a separate system.
Who Should Look Elsewhere
Companies not already using Workday HCM have little reason to evaluate Workday Onboarding on its own, since it isn’t sold or supported as an independent product. Teams that need deep, document-heavy onboarding workflows (multi-stage compliance sign-offs, highly customized role-based journeys) may find Rippling’s page under-detailed compared with BambooHR for that specific use case. Businesses that don’t need app provisioning automation at all may find Rippling’s broader modular platform more than they need just for onboarding.
Bottom Line
If onboarding documentation and new hire experience is the priority, BambooHR’s bundled onboarding module is the most fully described of the three. If getting new hires productive in company tools within minutes is the priority, Rippling’s app-provisioning approach is the differentiator. Workday Onboarding is compelling primarily as part of a complete Workday HCM rollout, not as a reason to adopt Workday on its own.
FAQ
Can I buy any of these onboarding modules on their own? No. BambooHR’s onboarding is bundled into its Core, Pro, and Elite HRIS plans; Rippling’s is bundled into its modular per-employee pricing; Workday’s requires a broader HCM contract. None are sold as a standalone, separately priced onboarding product.
Which tool onboards new hires fastest? Rippling’s own page is the only one of the three to make a specific speed claim, stating employees and contractors can be onboarded “in 90 seconds,” largely through automatic app provisioning.
Does BambooHR’s onboarding connect to its own hiring tool? Yes. BambooHR’s onboarding page states that candidate data from its ATS pre-fills the “Add Employee” form, avoiding duplicate data entry between hiring and onboarding.
Does Workday Onboarding include AI features? Workday’s own product page describes “AI-powered insights” that show onboarding plan progress and generate recommendations for each new hire, though it gives limited detail on how those recommendations are generated.
Is onboarding included in Gusto, too? This comparison focuses on Workday, BambooHR, and Rippling specifically; Gusto’s onboarding capabilities were not reviewed as part of this article and should be checked separately on Gusto’s own site if relevant to your decision.
IBM’s Power processor line has always sold itself on a different pitch than x86 commodity servers: fewer, more reliable systems for the workloads a business genuinely cannot afford to lose — core banking, ERP, retail transaction processing. Power11, announced in July 2025 and now the generation enterprises are actively evaluating and deploying through 2026, pushes that pitch further by wrapping in built-in quantum-safe cryptography, automated ransomware detection, and on-chip AI inferencing. This explainer breaks down what actually changed in Power11 versus Power10, based on IBM’s own announcements, and separates vendor performance claims from independently confirmed specifications.
At a Glance
Attribute
Power11 detail
Announced / GA
July 8, 2025 / July 25, 2025 (most systems); PowerVS cloud July 15, 2025
Process node
Refined 7nm (Samsung), not a new 5nm node
Cores per chip
16 per die; up to 15 active for workloads, 1 automatic hot-spare core
Top clock speed
Up to 4.4 GHz (Power E1180); up to 4.15 GHz (Power S1122)
Memory
High-speed DDR5; some systems also support DDR4 at reduced bandwidth
Uptime claim
99.9999% availability (single Power E1180, IBM-measured, unplanned downtime)
AI acceleration
On-chip inferencing; first Power server to support the IBM Spyre Accelerator (Q4 2025)
Security
Built-in NIST-approved quantum-safe cryptography; Power Cyber Vault ransomware alerting in under 1 minute
The Chip: Incremental Silicon, Not a New Node
Power11 is not a ground-up redesign. Per IBM’s own briefings, it stays on a refined 7-nanometer Samsung process rather than jumping to 5nm, and keeps the same 16-core-per-die layout as Power10. What’s new is how IBM uses that 16th core: up to 15 cores are available for AIX, IBM i, or Linux workloads, and the 16th is a spare that automatically activates if an active core fails, with no manual intervention or downtime, according to IBM. Clock speeds move up modestly — the two-socket Power S1122 reaches up to 4.15 GHz versus a flat 4 GHz on the Power10-based S1022, and the high-end Power E1180 reaches 4.4 GHz versus 4.15 GHz on the E1080. IBM also credits 2.5D integrated stacked-capacitor packaging and other thermal engineering for the efficiency gains, and adds a new Energy Efficient Mode that trades 5–10% of core performance for up to 28% lower energy use, a figure IBM states relative to its own Maximum Performance Mode.
IBM’s headline performance claims — up to 45% more capacity than Power10 in entry and midrange models, up to 55% more core performance than Power9, and roughly 2x the performance per watt of “comparable” x86 servers — are IBM’s own vendor-reported figures, measured against specific IBM and HPE server configurations rather than an independent third-party benchmark suite. They’re directionally useful for understanding IBM’s positioning, but procurement teams evaluating a specific workload should ask IBM for configuration-matched benchmark data rather than taking the headline percentages at face value.
Reliability and Security: The Real Differentiator
Where Power11 most clearly tries to separate itself from x86 alternatives is uptime and security guarantees. IBM states Power11 delivers 99.9999% availability, based on unplanned downtime measured on a single Power E1180 system, and claims zero planned downtime for maintenance — though IBM’s own footnotes note that some maintenance activity may still require Live Partition Mobility to move workloads between systems, so “zero planned downtime” describes the workload’s experience, not the complete absence of any maintenance operation.
On security, Power11 ships with built-in, NIST-approved quantum-safe cryptography, which IBM positions as protection against “harvest-now, decrypt-later” attacks where encrypted data is stolen today to be decrypted once quantum computers mature, as well as against firmware-integrity attacks. The IBM Power Cyber Vault feature guarantees a ransomware alert within one minute of detected anomalous activity; it’s worth noting precisely what that guarantee covers, per IBM’s own terms — the guarantee is for the alert itself, with remediation limited to drive replacement up to the covered product’s cost and subject to IBM’s stated terms, not a broader breach-recovery guarantee. Other security features include immutable snapshots, autonomous patching and workload migration that can occur without IT intervention, and integration with IBM Concert, which uses generative AI to help identify risks and automate security patching.
AI: On-Chip Inferencing and the Spyre Accelerator
Power11 supports on-chip inferencing, letting enterprises run AI models directly against data that lives on-premises or in a hybrid-cloud Power environment rather than moving it elsewhere first. IBM states Power11 is the first Power server generation to support the IBM Spyre Accelerator, a dedicated AI system-on-a-chip that IBM also designed to be compatible with its IBM z17 mainframe and LinuxONE 5 platforms, with availability targeted for Q4 2025. Power11 also supports IBM’s watsonx AI platform and Red Hat OpenShift AI for running and managing models. It’s worth being precise about what “AI chip” means here: Power11’s own silicon provides on-chip inferencing acceleration, while the heavier AI acceleration workload is intended to run through the separate Spyre accelerator attached to the system — the two are complementary, not identical.
The Server Lineup
Power S1122 / L1122: Two-socket systems; the “L” variant is lower-cost and Linux-only.
Power S1124 / L1124: Larger scale-out systems in the same family.
Power E1150: Midrange enterprise system.
Power E1180: High-end flagship, the system IBM’s uptime and top clock-speed figures are measured on.
Power S1112: Entry-level, half-width, single-socket system; reported to be planned for 2026 as the successor to the Power10-based S1012.
IBM did not disclose pricing at launch, and Power11 is explicitly not IBM’s mainframe line — it’s a separate product family from IBM Z, despite sharing some underlying design philosophy and, via Spyre, some AI accelerator compatibility.
Bottom Line
Power11 is best understood as a disciplined, reliability-and-security-focused refresh rather than a dramatic architectural leap: the same 16-core, 7nm-class silicon as Power10, with meaningful but incremental clock-speed gains, wrapped in genuinely new quantum-safe cryptography, faster ransomware detection, and a path to dedicated AI acceleration via Spyre. For enterprises already standardized on Power for mission-critical workloads, it’s a straightforward, lower-risk upgrade. For organizations evaluating Power against x86 or cloud-native alternatives for new workloads, the decision will hinge less on raw clock speed than on how much IBM’s uptime, security, and AI-readiness claims are worth relative to the total cost of the platform — a number IBM has not published and that varies by configuration.
FAQ
Is Power11 built on a new manufacturing process? No. It uses a refined 7nm Samsung process, the same node family as Power10, rather than moving to 5nm.
How many cores does a Power11 chip actually have? 16 cores per die, but IBM reserves one as an automatic hot spare; up to 15 are available to run workloads, and IBM has stated there is no way for customers to manually activate all 16.
Is Power11 the same as IBM’s mainframe (Z) line? No. Power and IBM Z are separate processor families with different target workloads; Power11 is IBM’s Unix/Linux/IBM i enterprise server line, not a mainframe.
What is the IBM Spyre Accelerator and does Power11 include it? Spyre is a separate AI accelerator chip, targeted for availability around Q4 2025, that Power11 is the first Power generation to support; it is an add-on accelerator rather than part of the base Power11 chip itself.
Has IBM published Power11 pricing? Not at launch. IBM confirmed general availability dates for most systems (July 25, 2025) and PowerVS cloud (July 15, 2025) without publishing list pricing in its initial announcements.
Database schema management tools tend to get picked once and then forgotten about for years, which makes it easy to miss how differently the three major players now price and position themselves. Flyway and Liquibase both started as free, SQL-script-based migration runners and have since built paid “Enterprise” or “Secure” layers around governance and support. Atlas took a newer approach, generating migrations from a declarative schema definition and publishing transparent, calculator-style pricing instead of quote-only tiers. Here’s how they actually compare in 2026.
At a Glance
Tool
Migration Style
Starting Price
Public Pricing?
Maintainer
Flyway
Versioned, hand-written SQL scripts
Free (Community); Enterprise by quote
No (paid tier)
Redgate
Liquibase
Changelogs (SQL, XML, YAML, or JSON)
Free (Community); Secure plans by quote
No (paid tier)
Liquibase (formerly Datical)
Atlas
Declarative schema with auto-generated migration plans
Free (Starter); Pro from $9/developer/mo
Yes
Ariga
Short Verdict
Flyway and Liquibase are both mature, widely adopted tools with genuinely free, usable community editions — the difference shows up once you need governance, drift detection, or vendor support, where both go to “request a quote” with no public number. Atlas stands out for actually publishing its Pro and add-on pricing, and for its declarative, diff-based approach to generating migrations rather than requiring you to hand-write every change script.
What Each Tool Actually Is
Flyway, maintained by Redgate, is a version-based migration tool: you write numbered SQL migration scripts and Flyway tracks which ones have run against a given database, applying new ones in order. The free Community edition targets individual developers and simple setups; the Enterprise edition adds Redgate’s comparison-engine-generated migrations, undo/rollback scripts, object-level and static-data versioning, policy-as-code enforcement, drift detection, and audit history, with a 28-day free trial available before you talk to sales.
Liquibase uses “changelogs” that can be written in SQL, XML, YAML, or JSON, and it supports a broader set of database platforms than most competitors out of the box. The free Community edition is self-managed — you handle drivers, extensions, and security patching yourself — while the paid “Secure” plans (Starter, Team, Business, Enterprise) add Liquibase-managed drivers, Change Automation, Change Governance, Change Intelligence features, enterprise support, and (at the top tiers) formal RBAC with 24/7 SLA support. Every Secure plan requires a Professional Services package and is sold by quote.
Atlas, from Ariga, takes a declarative approach: you describe the schema you want in HCL, SQL, or an ORM integration, and Atlas computes and generates the migration plan needed to get there, rather than you writing each incremental script by hand. The free Starter tier covers ORM integration, migration planning/execution, and IDE support with limited inspection and database coverage. The paid Pro tier adds automated CI/CD, “Database Security as Code,” migration linting, CVE scanning, schema governance policies, and drift monitoring, with published per-seat and per-project pricing.
Pricing Breakdown
Plan
Flyway
Liquibase
Atlas
Free tier
Community: $0 — core migration engine, individual/education use
Community: $0 — self-managed changelogs and drivers, core CLI
Pro: from $9/developer/mo + usage-based CI/CD and database add-ons; capped at 50 seats
Top tier
Enterprise: quote only — governance, drift detection, secret-manager integration, change history for audits
Enterprise: quote only — 4 database types, 2,000 targets, RBAC, 24/7 premium support
Enterprise: custom, starting at 20 databases — SSO, custom SLA, air-gapped deployment, no seat cap
Atlas also sells two add-ons with their own published rates: Pipelines (CI/CD automation) starts free on its own Starter tier, then $59/month per project with 2 target databases included and $39/month per additional target; Schema Monitoring runs $39/month per monitored database. Flyway and Liquibase, by contrast, give no public figures for their paid tiers at all — both direct every quote request through a sales conversation, so any number you see quoted elsewhere online should be treated as unverified unless it’s quoted directly from Redgate or Liquibase.
Pros
Flyway: Simple, well-understood versioned-script model that’s been battle-tested across huge numbers of production codebases for over a decade.
Liquibase: Supports the widest range of database platforms and changelog formats, which helps in polyglot environments running several database engines at once.
Atlas: Declarative schema plus auto-generated migrations removes a whole category of hand-written-script mistakes, and pricing is actually published so you can budget before talking to anyone.
Cons
Flyway: No published pricing for Enterprise, and the free Community edition is explicitly scoped to individuals and education rather than team use.
Liquibase: The Secure tiers require a mandatory Professional Services package on top of whatever the subscription costs, and no plan — not even Starter — lists a price publicly.
Atlas: Pro’s Registry is capped at 500 root schema objects, and the per-seat-plus-usage model (developers, CI/CD projects, database targets) means the final bill takes some assembly to estimate accurately.
Who It’s a Good Fit For
Flyway suits teams that already have a mature SQL-script-writing discipline and just want a reliable runner, especially inside the Redgate/SQL Server ecosystem. Liquibase suits organizations running multiple database engines who want one changelog format (or several) to standardize migrations across all of them, and who are comfortable negotiating enterprise pricing. Atlas suits teams that want schema-as-code with automatic diffing, transparent self-serve pricing, and CI/CD-native drift detection without a sales call to get started.
Who Should Look Elsewhere
Teams that want to compare exact enterprise pricing across vendors before engaging sales will be frustrated by both Flyway and Liquibase, since neither publishes a number for their advanced tiers. Teams wanting a purely declarative, ORM-first workflow may find Flyway and Liquibase’s script/changelog-first model more manual than they’d like. And teams with very simple, single-database setups and no CI/CD automation needs may not need Atlas’s Pro-tier features at all.
Bottom Line
Flyway and Liquibase remain safe, proven defaults for script-based migrations, particularly in larger or more heterogeneous database environments, but expect a sales conversation the moment you need anything beyond the free community tier. Atlas is the more modern, declarative alternative, and it’s the only one of the three where you can actually see Pro and add-on pricing before signing up.
FAQ
Are Flyway and Liquibase both open source? Their Community editions are free to use, though “free” here refers to Redgate’s and Liquibase’s own Community/free tiers rather than a single unified open-source license across every feature — check each project’s licensing terms for your specific use case.
Why doesn’t Atlas’s declarative approach need hand-written migration scripts? Atlas computes the difference between your current database schema and the schema you’ve declared, then generates the SQL needed to reconcile them, rather than requiring you to write each incremental change yourself.
Is there any way to get real pricing numbers for Liquibase Secure or Flyway Enterprise without contacting sales? Not from the vendors’ own pricing pages as of this writing — both list every paid tier as “Get a Quote” or “Contact sales,” with no self-serve checkout.
Can these tools be used together? They solve the same problem in different ways, so most teams pick one as their primary migration tool rather than combining them, though it’s technically possible to use Atlas’s planning on top of a database also managed by Flyway or Liquibase scripts if migrated carefully.
Does Atlas support ORMs like Prisma or Rails? Yes — ORM integration is listed as a feature on Atlas’s free Starter tier, not gated behind Pro.
Every team that shares files across more than one laptop eventually runs into the same question: which cloud storage service actually fits how we work? Google Drive, Dropbox, and Microsoft OneDrive (sold as part of Microsoft 365) are the three services most small and mid-sized teams land on, and each takes a different approach to storage, pricing, and collaboration. This comparison looks at what each one actually costs per user, how much storage you get, and which type of team fits best with each, based on the vendors’ own 2026 pricing pages.
At a Glance
Service
Entry plan (per user/month)
Storage on entry plan
Best known for
Google Drive (Google Workspace)
Business Starter, $7 (promotional $4.90 through Feb 2027)
30 GB pooled per user
Real-time co-editing in Docs/Sheets/Slides
Dropbox Business
Standard, $15
3 TB shared across the team
Sync reliability and file-level link sharing
OneDrive (Microsoft 365 Business)
Business Basic, $7
1 TB per user
Deep integration with Word, Excel, and Teams
Short Verdict
If your team already lives in Google Docs and Sheets, Google Drive’s Business Standard plan ($14/user/month for 2 TB pooled storage) is the easiest fit. If you need the most generous per-user storage at the lowest entry price, Microsoft 365 Business Basic gives every user a full 1 TB for $7/month. Dropbox costs more per seat but remains the choice for teams that care most about sync speed and granular file-sharing controls rather than built-in office apps.
What Each Tool Actually Is
Google Drive is the file storage and sync layer inside Google Workspace. It’s sold as part of a bundle that also includes Gmail, Docs, Sheets, Slides, and Meet, so you’re really buying a productivity suite with storage attached, not a standalone drive. Storage is pooled across the whole organization rather than allocated strictly per user, which helps teams with uneven storage needs.
Dropbox Business is a dedicated file sync and sharing service, built from the ground up around keeping files identical across every synced device. It doesn’t bundle office apps the way Google and Microsoft do; instead it focuses on sync performance, file recovery, link-level permissions, and integrations with tools like Slack and Zoom. Dropbox’s Standard plan starts at 3 TB for the whole team and can be used by a single person or a larger group.
OneDrive is Microsoft’s cloud storage layer, included with every Microsoft 365 Business subscription and tightly wired into Word, Excel, PowerPoint, and Teams. Files saved to OneDrive or SharePoint can be co-edited live inside the desktop or web apps, and the storage allowance is a flat 1 TB per user on every Business tier, from Basic up through Premium.
Pricing Breakdown
Plan
Price per user/month
Storage
Google Workspace Business Starter
$7 (intro $4.90 through Feb 9, 2027)
30 GB pooled
Google Workspace Business Standard
$14 (intro $9.80)
2 TB pooled
Google Workspace Business Plus
$22 (intro $11.00)
5 TB pooled
Dropbox Standard
$15 (1+ users)
Starts at 3 TB for the team
Dropbox Advanced
$24 (3+ users)
Starts at 15 TB for the team
Microsoft 365 Business Basic
$7
1 TB per user
Microsoft 365 Business Standard (with Copilot)
$23.50
1 TB per user
Note: Dropbox’s pricing page lists per-user monthly rates but does not clearly separate a discounted annual rate from the monthly rate for its team plans, so treat the $15/$24 figures as the published per-user prices rather than a confirmed annual-vs-monthly split. Microsoft’s Business Standard tier now bundles Copilot AI by default; a no-Copilot, no-Teams version is also sold at a lower price if your team doesn’t need those features.
Pros
Google Drive: Native real-time collaboration in Docs, Sheets, and Slides with no file locking or merge conflicts.
Dropbox: Sync is widely regarded as fast and reliable even with very large files and folders.
OneDrive: Every user gets a full 1 TB even on the cheapest Business plan, with deep Office and Teams integration.
Cons
Google Drive: The entry Business Starter plan’s 30 GB pooled storage is thin for teams that handle large media files.
Dropbox: No bundled word processor or spreadsheet app, so teams typically still need a separate office suite.
OneDrive: Real-time co-editing works best inside Microsoft’s own apps; the experience is less smooth with non-Microsoft file types.
Who It’s a Good Fit For
Teams already standardized on Gmail and Google Docs will get the most value from Google Drive, since storage, email, and document collaboration are already unified under one login. Teams that exchange large design files, videos, or client deliverables with outside partners often prefer Dropbox for its sharing controls and sync consistency. Teams built around Word, Excel, and Outlook — especially ones that already pay for Microsoft 365 for email — get the best per-dollar storage from OneDrive, since even the cheapest Business tier includes 1 TB per person.
Who Should Look Elsewhere
Teams on a tight budget who need generous storage with minimal per-user overhead may find Google’s 30 GB Starter tier too small and should budget for Business Standard instead. Organizations that don’t need a full office suite and only want straightforward file sync may find Dropbox’s $15–$24/user pricing hard to justify next to OneDrive’s 1 TB-for-$7 offer. And teams with no Microsoft dependency at all may not need to add a Microsoft 365 subscription just for storage.
Bottom Line
There’s no universal winner here — the right choice depends on which productivity suite your team is already committed to. Google Drive suits Google-first teams, OneDrive suits Microsoft-first teams and offers the most storage per dollar on its entry tier, and Dropbox suits teams that want a dedicated, suite-agnostic sync tool and are willing to pay a premium for it.
FAQ
Is Google Drive storage shared across my whole team? Yes. On Google Workspace Business plans, storage is pooled across the organization rather than locked to individual users, so heavy and light users can balance out.
Does Dropbox include an office suite like Google or Microsoft? No. Dropbox focuses on file sync and sharing; teams typically pair it with a separate word processor and spreadsheet tool.
Do all Microsoft 365 Business plans include 1 TB of OneDrive storage? Yes, per Microsoft’s own plan comparison, Business Basic, Standard, and Premium all include 1 TB of OneDrive storage per user.
Can I mix and match — use Dropbox for files but Google Docs for documents? Yes, many teams do exactly this, syncing Google Docs files into a Dropbox folder, though it adds a layer of complexity versus using one integrated suite.
Which is cheapest for a 10-person team? On entry-level plans, Microsoft 365 Business Basic ($7/user, 1 TB each) and Google Workspace Business Starter ($7/user, 30 GB pooled) are priced the same, but Microsoft gives far more storage per dollar at that tier.
AI resume screening has moved from a novelty to infrastructure: tools from HireVue, Eightfold, LinkedIn, and Workday now sit between millions of job applications and the recruiters who used to read them by hand. The vendors describe these systems as faster and fairer than human screening. Regulators, courts, and researchers have spent the past several years testing that claim, and the legal landscape itself has shifted significantly — in ways that matter to anyone deploying or being screened by these tools in 2026. Here is what the tools actually do, what their makers claim, and where the documented risk sits today.
At a Glance
Tool
What It Claims to Do
Primary Mechanism
HireVue
Screens candidates early in hiring using job-specific predictive models
One machine-learning model per job type, trained to identify who is likely to succeed compared to current employees in that role
Eightfold
Scans an entire talent network in seconds and ranks candidates by fit
Deep learning matched against stated role requirements, including “skill learnability”
LinkedIn Hiring Assistant
Evaluates every applicant for a role and surfaces top candidates to recruiters
AI agent connected to a company’s ATS via Recruiter System Connect; also generates applicant targeting criteria and follow-up messages
Workday AI screening
Helps recruiters process large applicant volumes faster
Machine-learning recommendations inside recruiting analytics; is the subject of an active federal discrimination lawsuit over how its screening functions operate
How These Tools Actually Work
Despite different marketing language, most AI screening tools do one of two things: rank candidates against a job description, or predict which candidates most resemble people already succeeding in the role. HireVue’s own description of its process, published on its blog, says each of its assessments is a separate machine-learning model built for a specific job type, with the single task of identifying which candidates in a pool are most likely to succeed compared with current job holders — the output is handed to a human recruiter as decision support, not a final decision. Eightfold describes a similar logic on its own site: deep-learning models scan a company’s entire talent network “within seconds” and rank candidates by how closely their profile matches a role’s stated requirements, including a factor it calls “skill learnability” — a candidate’s estimated potential to learn a new skill. LinkedIn’s Hiring Assistant, per LinkedIn’s own 2026 product update pages, connects to a company’s applicant tracking system and evaluates every applicant for a given role, while separately generating AI-written candidate-targeting criteria and follow-up messages for recruiters. Workday’s own recruiting product page describes its AI capability narrowly, as “machine learning recommendations” inside analytics dashboards, rather than as a dedicated resume-screening engine — though, as covered below, how its screening functions actually operate is now the subject of active litigation.
What the Vendors Claim
Every vendor examined here claims some version of “faster and less biased than a human.” Eightfold’s own candidate-screening page describes its ranking as “fast, unbiased, and intuitive.” HireVue goes further, describing an internal testing loop it says it runs for every model: auditing training data for bias, testing predictions for adverse impact, removing factors shown to produce biased results, and retraining until the disparity is addressed — the company gives the example of disabling a speech-speed feature after testing showed it scored men higher than women. Workday, in materials cited in ongoing litigation, has said its technology assesses only job qualifications and that it tests its products for bias through an internal Responsible AI program. These are vendor self-reports rather than independent, published audits, and none of the three companies’ own pages reviewed for this article cite third-party verification of their bias-testing results.
The Documented Legal and Bias Risks
The clearest primary-source rule in this space is New York City’s Local Law 144. Per the New York City Department of Consumer and Worker Protection’s own page, employers and employment agencies may not use an “automated employment decision tool” unless it has been subject to an independent bias audit within the past year, and a summary of that audit must be made publicly available; the city’s Department of Consumer and Worker Protection began enforcing the law on July 5, 2023.
Federal guidance has moved in the opposite direction. The EEOC’s technical assistance documents on assessing adverse impact from AI and algorithmic hiring tools were removed from eeoc.gov in January 2025 and, as of a March 2026 review by the National Law Review, had not been restored or replaced — only a broken-link shell page on AI and the ADA remained. That doesn’t change the underlying law: Title VII and the federal Uniform Guidelines on Employee Selection Procedures still apply, and the EEOC’s current Strategic Enforcement Plan still lists AI-related discrimination as a priority, but the explanatory guidance employers used to assess their own tools is currently unavailable. Into that gap, at least four states have moved with their own rules: California’s automated-decision-system regulations under its Fair Employment and Housing Act took effect October 1, 2025; Illinois’s HB 3773 takes effect January 1, 2026, with a private right of action; Texas’s TRAIGA takes effect the same day but requires proof of discriminatory intent rather than disparate impact alone; and Colorado’s AI Act (SB 24-205), covering high-risk employment decisions, is set to take effect June 30, 2026.
The most closely watched court case is Mobley v. Workday. According to a June 2026 ruling reported by HCAMag, a federal judge in San Francisco allowed the proposed class action to proceed, rejecting Workday’s motion to dismiss most claims. The plaintiff, who is Black, over 40, and has a disability, alleges he was rejected from more than 100 jobs at companies using Workday’s screening software, often within minutes of applying, and that the software flagged applicants using proxy indicators for disability such as gaps in employment history. The court held that Workday can be treated as an “employer” under federal anti-discrimination law because it performs screening functions that client companies would otherwise handle themselves — a significant finding for any vendor selling AI screening as a service, not just Workday. Workday disputes the allegations and points to its internal bias-testing program; the case remains an unresolved proposed class action, not a final verdict, and court filings cited in that reporting reference roughly 1.1 billion job applications processed through the challenged tools over the relevant period.
What to Do About It
With federal guidance in flux and state rules arriving on different timelines, the practical burden has shifted toward independent verification rather than vendor assurance. Open-source and commercial bias-auditing frameworks exist specifically for this gap: IBM’s AI Fairness 360 (now maintained by the Linux Foundation) is an open-source toolkit with more than 70 fairness metrics and ten bias-mitigation algorithms for testing machine-learning models before and after deployment. Commercial platforms such as Fiddler and Credo AI offer similar model-monitoring and AI-governance capabilities aimed at enterprise compliance teams, though this article has not independently verified their specific feature claims against primary sources the way it did for AI Fairness 360, so treat vendor-specific capability claims from either company with the same caution applied to the hiring-tool vendors above. The throughline for any employer using these tools in 2026: a vendor’s internal bias-testing claim is not the same as an independent audit, and in New York City, only an independent audit satisfies the law.
Bottom Line
AI resume and candidate screening tools genuinely do speed up high-volume hiring, and every major vendor now markets some form of internal bias testing. But the regulatory floor supporting those claims is uneven and moving: NYC’s Local Law 144 is real, specific, and enforced; federal EEOC guidance that once helped employers interpret their Title VII obligations has been pulled with no replacement; and a live federal lawsuit is testing, in real time, whether a vendor’s screening software can itself be held liable for discrimination. Anyone deploying or relying on these tools should treat 2026 as a year of active legal uncertainty, not settled practice.
FAQ
Is AI resume screening illegal? No, it is not illegal outright, but its use is increasingly regulated. New York City requires an independent bias audit before using an “automated employment decision tool,” and several states now impose their own disclosure or disparate-impact rules.
Did the EEOC say AI hiring tools cause discrimination? Its prior technical assistance documents addressed how to assess adverse impact from such tools, but those pages were removed from eeoc.gov in January 2025 and have not been replaced as of a March 2026 legal review. The underlying Title VII law and Uniform Guidelines on Employee Selection Procedures remain in force regardless.
What is Mobley v. Workday? It’s a proposed federal class action alleging Workday’s AI screening software disadvantaged applicants based on race, age, and disability. A judge allowed most claims to proceed in a June 2026 ruling, but the case has not been decided on the merits and Workday denies wrongdoing.
Can a bias-auditing tool guarantee a hiring AI is fair? No single tool guarantees fairness. Frameworks like IBM’s open-source AI Fairness 360 provide metrics and mitigation algorithms to test models, but they measure specific statistical definitions of fairness and require ongoing use — they are a mitigation step, not a one-time certification.
Do all states now require bias audits for hiring AI? No. As of this writing, only New York City has an enforced independent-audit requirement. California, Illinois, Texas, and Colorado have each passed their own, differently structured AI employment laws, with effective dates ranging from October 2025 through June 2026, but none mirror NYC’s audit mandate exactly.
AWS has spent close to a decade building its own AI silicon, and by late 2025 that bet reached a new generation: Trainium3, paired with Trainium3 UltraServers that AWS says scale to hundreds of thousands of chips. The pitch is not that Trainium beats Nvidia’s GPUs on raw throughput — AWS doesn’t make that claim on its own product pages — but that it beats them on cost per token, delivered as part of a vertically integrated stack AWS fully controls, from the Graviton host CPUs and Nitro hypervisor to the Elastic Fabric Adapter (EFA) networking and the Neuron software stack. Here’s what’s verifiably true about Trainium3’s architecture, how it stacks up against Nvidia’s current flagship data center GPU platform, and where the comparison gets murkier.
At a Glance
Spec (per chip/GPU)
AWS Trainium3
Nvidia Blackwell (GB200 NVL72, per GPU)
Peak compute
~2.52 PFLOPS MXFP8 (derived from UltraServer total)
AWS Neuron SDK; claims unmodified PyTorch, vLLM, HuggingFace, Ray support
CUDA, cuDNN, Transformer Engine, Magnum IO
Note: AWS publishes Trainium3 figures per chip and per 144-chip UltraServer directly. Nvidia publishes GB200 NVL72 figures at the rack level (72 GPUs); the per-GPU numbers above are derived by dividing rack totals and should be read as approximate, not as Nvidia’s own stated per-chip spec.
What Trainium3 Actually Is
According to AWS’s own Trainium product page, Trainium3 is built around eight large NeuronCores per chip, each combining Tensor, Vector, Scalar, and GPSIMD engines that run concurrently. AWS claims up to 2x MXFP8 compute throughput over Trainium2, plus hardware-level support for Mixture-of-Experts (MoE) routing — relevant given how many frontier models now use MoE architectures. Each chip carries 144 GB of HBM3e at 4.9 TB/s of bandwidth, which AWS describes as 1.7x the bandwidth of Trainium2, and supports hardware-accelerated W4A8 quantization that AWS says doubles effective weight-loading speed. A two-level on-chip SRAM hierarchy sits between the HBM and the compute engines to reduce memory-access latency.
Chips are grouped into Trainium3 UltraServers of up to 144 chips, which AWS rates at 362 PFLOPS of MXFP8 compute, 20.7 TB of pooled HBM3e, and 706 TB/s of aggregate memory bandwidth. Inside the UltraServer, a NeuronSwitch all-to-all fabric doubles interchip bandwidth versus Trainium2 UltraServers, with redundant NeuronLink lanes for chip-level fault tolerance. For scaling beyond a single UltraServer, EFA networking provides up to 28.8 Tbps of aggregate scale-out bandwidth, and AWS’s “UltraClusters 3.0” architecture is designed to connect hundreds of thousands of chips.
What Nvidia’s Blackwell Platform Brings to the Comparison
Nvidia’s GB200 NVL72 — 72 Blackwell GPUs and 36 Grace CPUs in a single rack — is the current reference point for large-scale GPU training, per Nvidia’s own product page. Nvidia publishes the rack as a single 72-GPU NVLink domain: 13.4 TB of pooled HBM3e, 576 TB/s of aggregate memory bandwidth, and a 130 TB/s NVLink domain, with fifth-generation NVLink providing 1.8 TB/s of GPU-to-GPU bandwidth. Nvidia’s own materials claim roughly 4x faster LLM training than the prior H100 generation on a 1.8-trillion-parameter MoE benchmark — a figure the company’s own footnote flags as “projected and subject to change” — plus up to 30x faster real-time trillion-parameter LLM inference and roughly 25x better energy efficiency versus H100 air-cooled infrastructure. Nvidia’s pitch is the inverse of AWS’s: a single, enormous, CUDA-programmable compute domain built for both bleeding-edge training performance and the broadest possible software compatibility.
The Trade-Offs: Cost, Risk, and Ecosystem
AWS’s central argument for Trainium is economics, not peak performance. Amazon has publicly claimed customers see roughly 50% lower training and inference costs compared with “GPU alternatives” — a framing that does not name Nvidia specifically and is based on AWS’s own customer case studies (cited examples include Karakuri, Metagenomi, NetoAI, Ricoh, and Splash Music), not an independently verified benchmark. Anthropic is the most prominent named customer running production workloads on Trainium, and Amazon Bedrock itself serves production traffic from Trainium3 infrastructure.
The catch is ecosystem maturity. Moving a training or inference workload to Trainium means going through AWS’s Neuron SDK, and performance-critical code sometimes needs to be rewritten or re-tuned for it, whereas CUDA remains the default, far more battle-tested target for nearly every published model architecture, research paper, and open-source framework. That’s a real switching cost that AWS’s own page addresses indirectly by emphasizing “unmodified” support for PyTorch, vLLM, HuggingFace, and Ray — a claim about framework-level compatibility, not a guarantee of matching CUDA-level performance out of the box. For teams doing novel model R&D where every detail of kernel behavior matters, that relative novelty is a real risk; for teams running well-understood training or inference workloads at large, predictable scale, it’s a more acceptable trade for lower cost.
It’s also worth noting AWS and Nvidia aren’t purely adversarial here. AWS has signaled that its next generation, Trainium4 (expected late 2026 or early 2027), will add support for Nvidia’s NVLink Fusion interconnect alongside the UALink open standard, which would let AWS build heterogeneous clusters mixing its own silicon with Nvidia GPU resources rather than treating the two as strictly separate options. AWS is also reported to remain one of Nvidia’s largest cloud customers, buying GPU capacity even as it scales up its own chips.
Bottom Line
Trainium3 is a credible, rapidly maturing alternative to GPUs for specific, well-understood training and inference workloads at AWS scale, built on genuinely competitive memory bandwidth and a purpose-built MoE-aware architecture — but it competes primarily on cost and vertical integration, not on raw per-chip compute, where Nvidia’s Blackwell platform still appears to hold a lead based on each company’s own published figures. The practical decision for most teams isn’t “Trainium or Nvidia” in the abstract; it’s whether a given workload’s tolerance for Neuron SDK porting work is outweighed by the cost savings AWS advertises, and that calculus will differ sharply between a stable production inference pipeline and a team pushing the frontier of new model architectures.
FAQ
Is Trainium3 faster than Nvidia’s Blackwell GPUs? Based on each company’s own published figures, Blackwell’s GB200 NVL72 appears to have higher peak per-GPU compute and memory bandwidth than Trainium3. AWS does not claim to beat Nvidia on raw throughput; its public claims focus on cost per token instead.
What is a Trainium3 UltraServer? It’s AWS’s term for a tightly interconnected cluster of up to 144 Trainium3 chips, sharing 20.7 TB of pooled HBM3e memory and connected by a NeuronSwitch fabric, rated by AWS at 362 PFLOPS of MXFP8 compute.
Do I need to rewrite my code to use Trainium? AWS states that PyTorch, vLLM, HuggingFace, and Ray run on Trainium “without modification” at the framework level, but workloads optimized specifically for CUDA kernels may still need re-tuning through the Neuron SDK to get comparable performance.
Which major AI companies use Trainium in production? Anthropic is the most prominent named customer running production workloads on Trainium, per AWS and third-party reporting; Amazon Bedrock also runs production inference traffic on Trainium3.
Will AWS keep buying Nvidia GPUs even as it builds Trainium? All available reporting suggests yes — AWS continues to offer Nvidia GPU instances alongside Trainium, and Trainium4 is expected to add support for Nvidia’s NVLink Fusion interconnect, pointing toward coexistence rather than full replacement.
Enterprises shopping for robotic process automation (RPA) in 2026 keep landing on the same three names: UiPath, Automation Anywhere, and Microsoft Power Automate. All three now bolt generative AI onto classic rule-based bots, but they differ sharply in how they’re priced, how they’re deployed, and who they’re actually built for. This comparison pulls directly from each vendor’s own pricing and product pages to show what you’d actually pay and get, rather than repeating marketing claims.
At a Glance
Platform
Best For
Starting Price
Free Option
UiPath
Enterprises wanting one platform for automation, testing, and process mining
Basic plan from $25/month (2 robots)
Community Edition, free forever for small teams
Automation Anywhere
Cloud-native automation with generative AI document processing
Not published; quote-based for all paid tiers
Community Edition, free for qualifying small businesses
Microsoft Power Automate
Organizations already standardized on Microsoft 365 and the Power Platform
Premium at $15/user/month (attended); Process at $150/bot/month (unattended)
30-day free trial
Short Verdict
If your organization already runs on Microsoft 365 and Dataverse, Power Automate is the path of least resistance and the only one of the three with published per-user and per-bot list prices. UiPath has the most complete automation suite (process mining, testing, and orchestration under one roof) and the only transparent small-team entry price among the dedicated RPA vendors, but its Standard and Enterprise tiers — where most real deployments land — are quote-only. Automation Anywhere leans hardest into generative AI for document work, but publishes no pricing at all beyond its capped free Community Edition, which makes it the hardest of the three to budget for without talking to sales.
What Each Tool Actually Is
UiPath is built around Automation Cloud, a platform spanning Studio (bot design), Orchestrator (deployment and scheduling), attended and unattended robots, Process Mining, and Test Suite. Its pricing page lists a Basic tier starting at $25/month with two robots and a small mix of user seats, a Standard tier with a 60-day free trial and no published robot or user cap, and an Enterprise tier, both of which require contacting sales for a quote. A free Community edition exists for individuals and small teams, though the page notes the Basic plan’s exact offering is “evolving.”
Automation Anywhere runs on its Automation 360 cloud platform and markets itself heavily around Prompt-to-Automate (natural-language bot creation) and generative AI document extraction. Its free Community Edition is available to organizations with fewer than 250 machines, fewer than 250 users, and under $5 million in annual revenue, capped at five machines and 100 pages per month of document automation for small businesses. Beyond that, the company’s own site has no public pricing page; the only path forward is “Talk to Sales.” Independent pricing research (such as an August 2026 analysis from eesel.ai) found a handful of scattered reference points — a 2020 press release citing a $750/month Cloud Starter Pack, and a $126,000-per-year AWS Marketplace listing described as “for reference only” — but no current, authoritative public rate card.
Microsoft Power Automate is part of the Power Platform and separates attended work from unattended work in its pricing structure rather than bundling them. The Premium plan, at $15 per user per month (paid yearly), covers cloud flows and attended desktop (RPA) flows, plus a small allotment of process and task mining. Unattended automation is licensed per bot: the Process plan is $150 per bot per month and the Hosted Process plan, which adds a Microsoft-hosted virtual machine so you don’t need your own, is $215 per bot per month. A dedicated Process Mining add-on costs $5,000 per tenant per month and is only available on top of Premium.
Pricing Breakdown
Plan
Price
What It Covers
UiPath Community
Free
Individuals and small teams; no stated robot cap on the pricing page
UiPath Basic
From $25/month
2 robots; up to 5 Basic, 5 Plus, and 1 Pro user
UiPath Standard / Enterprise
Custom quote
No published robot or user limit; Standard includes a 60-day trial
Automation Anywhere Community Edition
Free
Orgs under 250 machines/users and $5M revenue; capped at 5 machines, 100 pages/month document automation
Automation Anywhere paid tiers
Custom quote only
No published rate card; AI usage billed separately at roughly 1,000 credits per $1
Unattended desktop flows, one bot = one concurrent run
Power Automate Hosted Process
$215/bot/month (annual)
Unattended flows plus a Microsoft-hosted VM
Power Automate Process Mining add-on
$5,000/tenant/month
100GB data storage; add-on to Premium only
Pros
UiPath: The broadest single platform, combining bot development, orchestration, testing, and process mining, with the only published small-team starting price among the three RPA-first vendors.
Automation Anywhere: Strong generative AI document extraction and natural-language bot creation available even in the free Community Edition.
Microsoft Power Automate: Transparent, published per-user and per-bot list prices, plus native fit with Microsoft 365, Teams, and Dataverse that other platforms can’t replicate as tightly.
Cons
UiPath: The Standard and Enterprise tiers most mid-size and large deployments actually need are quote-only, so real-world cost isn’t visible upfront.
Automation Anywhere: No public pricing anywhere beyond the capped free tier; reviewers commonly flag pricing complexity, especially for smaller teams.
Microsoft Power Automate: Costs climb quickly once you license unattended bots, hosted VMs, premium connectors, and Dataverse capacity separately, and dedicated process mining alone runs $5,000/tenant/month.
Who It’s a Good Fit For
UiPath suits organizations that want one vendor covering bot development through testing and process discovery, and that are prepared to negotiate once they outgrow Basic. Automation Anywhere fits teams prioritizing generative AI-driven document processing who are comfortable entering a sales conversation without a reference price in hand. Power Automate is the clear fit for organizations already paying for Microsoft 365, Dataverse, or Azure, where per-user attended licensing and per-bot unattended licensing can be layered onto an existing Microsoft agreement.
Who Should Look Elsewhere
Teams that need a firm number before they can even start a budgeting conversation will struggle with Automation Anywhere’s total absence of public pricing, and to a lesser extent with UiPath once they move past Basic. Organizations without any Microsoft Power Platform footprint may find Power Automate’s per-bot unattended pricing adds up faster than expected once hosted VMs and Dataverse storage enter the equation. Smaller teams whose automation needs are closer to app-to-app workflow glue than full-scale enterprise RPA may be better served by an iPaaS tool instead — see our comparison of Zapier, Make, and Workato.
Bottom Line
None of these three platforms is “cheap,” and two of the three (Automation Anywhere entirely, UiPath above Basic) require a sales conversation before you’ll see a real number. Power Automate is the only one with a full, published rate card across attended, unattended, and process-mining use cases, which makes it the easiest to model in a spreadsheet before you ever talk to a salesperson — provided your organization is already in the Microsoft ecosystem.
FAQ
Which of the three has the cheapest published starting price? UiPath’s Basic plan at $25/month is the only published small-team price among the dedicated RPA vendors; Power Automate’s Premium plan at $15/user/month is cheaper per seat but only covers attended automation, with unattended bots priced separately at $150+/bot/month.
Does Automation Anywhere publish any pricing at all? Only for its free Community Edition, which is capped at organizations under 250 machines/users and $5 million in revenue. Every paid tier requires contacting sales.
Can I trial any of these before buying? Yes. UiPath offers a free Community Edition and a 60-day trial on its Standard plan, Automation Anywhere offers a capped free Community Edition, and Microsoft offers a 30-day free trial of Power Automate.
Do I need Microsoft 365 to use Power Automate? Power Automate Premium is licensed per user independently of a Microsoft 365 subscription, but it integrates most deeply with organizations already using Microsoft 365, Dataverse, and Teams.
What’s the real difference between attended and unattended pricing? Attended bots work alongside a human and are typically licensed per user (as with Power Automate Premium or UiPath user seats); unattended bots run independently and are typically licensed per bot or per robot. See our dedicated explainer on attended vs. unattended RPA costs for a full breakdown.
Feature flagging has grown from “a way to hide unfinished code” into a full experimentation and release-management category, and the vendor landscape shifted again recently: Split Software, once a standalone leader, was acquired by Harness and rebranded as Harness Feature Management & Experimentation (FME). That consolidation, alongside LaunchDarkly’s move to usage-based pricing and Statsig’s analytics-plus-flags bundle, makes this a good moment to compare where each platform actually stands.
At a Glance
Platform
Best For
Starting Price
Pricing Model
Public Self-Serve Pricing?
LaunchDarkly
Teams wanting flags, experiments, and app/LLM observability in one product
Teams that want flags and product analytics/experimentation bundled
Free (Developer tier); Pro $150/mo
Event volume-based
Yes
Short Verdict
LaunchDarkly offers the most generous named free tier and the clearest self-serve usage pricing of the three, now expanded well beyond flags into agent/LLM observability. Split no longer operates as an independent, self-serve product — as Harness FME, it’s sold as one module inside Harness’s broader DevOps platform, with pricing only available by contacting sales. Statsig is the one to consider if you want feature flags and product analytics (events, session replay, experimentation) from a single vendor at a flat monthly starting price.
What Each Platform Actually Is
LaunchDarkly is a feature management platform built around flags, targeting rules, A/B testing, and multi-armed bandit experiments, and it has pushed further into AI-era tooling with agent configuration, LLM observability (with LLM-as-judge evaluation), session replay, and error/trace monitoring built into the same product. Pricing is unusual in that seats are unlimited and free; you pay for usage instead, measured across service connections, client-side MAU, AI runs, session replays, errors, and trace/log volume.
Split was a standalone feature-flagging and experimentation platform until Harness acquired it in 2024; the product is now called Harness Feature Management & Experimentation (FME) and is sold as one of several modules inside the Harness DevOps suite (alongside CI, CD, Infrastructure as Code, and others). Its official documentation confirms the rebrand directly. There is no public self-serve price list for FME — both the “Essentials” and “Enterprise” Harness bundles route to “Contact Sales,” and FME itself isn’t included in the lower-cost Essentials package at all.
Statsig combines feature flags, A/B testing and experimentation, product/web analytics, and session replay in one platform, aimed at teams that want flag rollouts and the analytics to evaluate them without separate billing relationships. Its free Developer tier is usage-capped by monthly events rather than seats, and the paid Pro tier scales with additional event volume.
Pricing Breakdown
Plan
LaunchDarkly
Split / Harness FME
Statsig
Free tier
Developer: $0 — unlimited flags, 1K client-side MAU, 5 service connections, 5K AI runs, unlimited A/B tests; 1 project, 3 environments only
The gap in the middle column is a material finding of this research, not an oversight: Harness’s public pricing page lists no prices for any module, including FME, and its own documentation and comparison pages from third parties consistently describe FME as quote-only. Teams evaluating Split/FME today should expect a sales conversation rather than a self-serve checkout.
Pros
LaunchDarkly: Unlimited free seats plus a genuinely usable free usage tier, with transparent published rates for every metric once you exceed it.
Split / Harness FME: Strong fit if you’re already standardizing on Harness for CI/CD, since flags, pipelines, and infrastructure-as-code live under one contract and admin console.
Statsig: One bill covers flags, experimentation, and the analytics needed to judge them, instead of paying a flagging vendor and an analytics vendor separately.
Cons
LaunchDarkly: The free Developer tier is capped at a single project and three environments, and lacks SSO, approval workflows, or audit logging — all common requirements once more than one team touches flags.
Split / Harness FME: No published self-serve pricing at all, and it isn’t included in Harness’s lower-cost “DevOps Essentials” bundle, so even small teams must go through a sales cycle to get a number.
Statsig: The Pro tier caps you at one project per subscription, and heavy event volume can push costs up quickly at $0.05 per 1,000 events beyond the included 5 million.
Who It’s a Good Fit For
LaunchDarkly fits teams of almost any size that want to start free and scale into usage-based billing with full transparency, especially ones also experimenting with AI agents and wanting observability for them in the same tool. Split/Harness FME fits organizations already committed to Harness’s DevOps platform who are comfortable negotiating an enterprise contract. Statsig fits product and growth teams who want flags and the analytics to measure their impact without juggling two vendor relationships.
Who Should Look Elsewhere
Teams that need enterprise controls like SSO on a tight budget may find LaunchDarkly’s jump from the free tier to Enterprise pricing jarring. Teams that want to compare self-serve pricing between vendors before talking to anyone will find Split/Harness FME frustrating, since there’s simply no public number to compare. And organizations that specifically don’t want their analytics and feature-flag data living in the same platform may prefer to keep those functions separated rather than adopting Statsig’s bundled approach.
Bottom Line
LaunchDarkly and Statsig both compete openly on published, usage-based pricing, which makes them easy to evaluate side-by-side. Split’s absorption into Harness FME has effectively removed it from that kind of self-serve comparison — it’s now a sales-led enterprise module, which may still be the right choice for Harness customers but changes the buying process entirely.
FAQ
Is Split still a separate product from Harness? No. Harness’s own developer documentation states that Harness acquired Split in June 2024 and the product is now called Harness Feature Management & Experimentation (FME).
Does LaunchDarkly charge per seat? No — all three LaunchDarkly plans include unlimited seats at no per-seat fee; billing is based on usage metrics like client-side MAU and service connections instead.
What counts as an “event” on Statsig’s free tier? Statsig’s Developer plan includes 2 million events per month alongside unlimited flag and config checks; the event count specifically covers analytics/logging events rather than flag evaluations.
Can I get a trial of Harness FME without a sales call? Based on Harness’s public pricing page, no — every paid tier, including the module containing FME, routes to “Contact Sales,” with no listed self-serve trial.
Which platform is easiest to start with as a solo developer or small team? LaunchDarkly’s and Statsig’s free tiers are both usable without a credit card and don’t require a sales conversation, making either a lower-friction starting point than Split/Harness FME.
Enterprises rolling out AI models in 2026 face a harder compliance landscape than they did even two years ago: the EU AI Act’s risk-management obligations are in force, US state-level algorithmic accountability laws are multiplying, and procurement teams increasingly ask vendors to show their bias-testing paper trail before signing a contract. Three names come up constantly in that conversation: IBM’s open-source AI Fairness 360 (AIF360) toolkit, Fiddler AI’s monitoring and governance platform, and Credo AI’s enterprise governance suite. They are not, however, interchangeable. One is a free Python library for measuring and mitigating statistical bias; the other two have evolved into broader AI governance and observability platforms where fairness is one feature among many, not the headline. This comparison looks at what each tool actually does today, based on their own current product pages, not on their 2018–2021 reputations.
At a Glance
Tool
Category
License/Pricing
Core Focus Today
Best For
IBM AI Fairness 360
Open-source library
Free (Apache-2.0 style open source)
Bias metrics + 9 mitigation algorithms for datasets/models
Data scientists running hands-on fairness tests in Python
Fiddler AI
Commercial platform
Free tier; Developer at $0.002/trace; custom Enterprise
Agentic AI observability, evals, guardrails, governance
Teams monitoring production LLM/agent behavior at scale
Credo AI
Commercial platform
Enterprise, custom quote only
AI registry, risk intelligence, and policy/compliance mapping
Large regulated enterprises needing audit-ready governance
Short Verdict
If what you need is a hands-on, no-cost way to run specific statistical fairness metrics and mitigation algorithms against a dataset or model, AIF360 is still the most direct tool for that narrow job, though it has not had a new release since version 0.6.1 in April 2024, which is worth factoring into any long-term dependency decision. If what you actually need is continuous oversight of a live AI system — agents, LLM apps, or classic ML models — in a regulated environment, Fiddler and Credo AI are the more realistic candidates, but neither markets itself primarily as a “bias auditing” tool anymore. Fiddler’s current pages center on agent observability, evaluation, and guardrails; Credo AI’s center on AI registries, risk intelligence, and policy automation. Fairness testing, where it exists in either platform, now sits inside a larger governance workflow rather than being the product itself.
What Each Tool Actually Is
IBM AI Fairness 360 is an open-source Python toolkit that IBM Research first released in September 2018. Per IBM’s own description, it is “a comprehensive open-source toolkit of metrics to check for unwanted bias in datasets and machine learning models,” paired with nine bias-mitigation algorithms drawn from the academic fairness literature, including optimized pre-processing, disparate-impact removal, reject-option classification, prejudice-remover regularization, and adversarial debiasing. It’s built to feel familiar to anyone who has used scikit-learn, with a similar fit/predict interface, and ships with tutorials on credit scoring, medical-expenditure prediction, and face-image classification by gender. It is a library you integrate into your own ML pipeline, not a hosted platform.
Fiddler AI has repositioned itself as what its site calls “the System of Trust for the Agentic Lifecycle.” Its current Control Plane product spans Agentic AI (continuous evaluations, agentic observability/tracing, and guardrail-based policy enforcement, powered by Fiddler’s own “Centor Models” for fast, low-cost in-environment evaluation), Predictive AI (ML observability), and a Governance layer for risk and compliance. Fairness-specific tooling — a “Bias Detector” methodology — appears in Fiddler’s own archive dated to 2021; the company’s 2026 release notes (Control Plane for Coding Agents in June, Dynamic Model Escalation in October, Agent Registry in November) are focused on agent evaluation and inventory rather than fairness metrics specifically. Fiddler’s site also currently carries a banner stating that CrowdStrike is acquiring the company to add agent observability to its security platform; no deal terms or closing date are disclosed on that page.
Credo AI sells an enterprise AI governance platform built around three pieces: an AI Registry that catalogs models, agents, vendors, and “shadow AI” with risk classification; Risk Intelligence, which does continuous risk assessment and connects to observability tools for drift detection; and a Policy Engine that turns written policy into enforceable rules, ships pre-built packs mapped to frameworks like the EU AI Act, NIST AI RMF, and ISO 42001, and produces audit-ready evidence trails. An AI assistant called GAIA handles governance intake. Credo AI’s own homepage does not mention fairness or bias metrics directly; its stated risk focus is on operational and agentic risks such as scope drift and tool misuse, so prospective buyers specifically after bias-metric tooling should confirm that capability directly with Credo AI rather than assume it from public marketing.
Pricing and Availability
IBM AI Fairness 360: Free and open source, distributed via PyPI and GitHub under the Trusted-AI organization. No paid tier exists because it is a library, not a hosted service.
Fiddler AI: A Free plan covers real-time guardrails. A Developer plan is usage-based at $0.002 per evaluated trace and includes observability, custom evaluators, and SSO. Enterprise plans are custom-quoted and add advanced guardrails, flexible deployment, and dedicated support. Fiddler notes that each evaluated trace can also trigger an external LLM API call billed separately by that provider.
Credo AI: No public pricing. The company offers demos and sales calls only; its customer base skews toward large enterprises in financial services, insurance, healthcare, and federal government.
Pros and Cons
IBM AI Fairness 360
Pros: Free; transparent, peer-reviewed algorithms; scikit-learn-like API lowers the learning curve; good for one-off audits or academic-grade rigor.
Cons: No managed hosting, dashboards, or continuous monitoring; release cadence has slowed (latest PyPI release, 0.6.1, dates to April 2024); still tagged “Alpha” on PyPI; requires in-house ML engineering to operate.
Fiddler AI
Pros: Real production monitoring and tracing for agentic and predictive AI; transparent usage-based entry pricing; in-environment evaluation models avoid some external API costs; active 2026 product cadence.
Cons: Fairness/bias auditing is no longer a headline capability on current product pages; pending CrowdStrike acquisition introduces roadmap and ownership uncertainty; enterprise pricing is opaque.
Credo AI
Pros: Strong fit for multi-framework compliance (EU AI Act, NIST AI RMF, ISO 42001); AI/agent/vendor registry gives a single inventory for audit purposes; large reference customers (Mastercard, Databricks, Northrop, Booz Allen cited on its site).
Cons: No published pricing; no explicit fairness-metrics capability stated on its own marketing pages; best suited to organizations that already have governance processes to formalize, not teams starting from zero on bias testing specifically.
Who It’s a Good Fit For
AIF360 suits ML engineers and researchers who need to run specific, well-documented fairness metrics (disparate impact, equal opportunity difference, and similar) against a model or dataset and who are comfortable building their own reporting layer around it. Fiddler fits engineering and platform teams running LLM agents or predictive models in production who need real-time evaluation, tracing, and guardrails, and who are willing to treat fairness as one slice of a broader observability practice. Credo AI fits compliance, risk, and legal teams at large, regulated enterprises that need a cross-functional system of record for every AI system in use, mapped to specific regulatory frameworks, more than they need a technical bias-testing engine.
Who Should Look Elsewhere
Teams wanting a fully managed, dashboard-driven fairness-monitoring product with active current development around bias metrics specifically may find none of these three a perfect match as of late 2026: AIF360 has no managed layer, and both commercial platforms have broadened well beyond fairness into general agent/model governance. Smaller teams without dedicated ML engineering staff may also find Credo AI’s enterprise sales motion and lack of public pricing a mismatch versus simpler point solutions.
Bottom Line
The “bias-auditing tools” category has quietly merged into the broader AI governance and observability market. AIF360 remains the clearest free option for direct, metric-level fairness testing, but buyers should weigh its slowing release cadence. Fiddler and Credo AI are stronger choices for organizations that need ongoing oversight of production AI systems and defensible compliance documentation, but prospective buyers specifically chasing bias-metric functionality should ask both vendors directly what, concretely, their platforms measure and report today, rather than relying on either company’s historical reputation in the fairness space.
FAQ
Is IBM AI Fairness 360 still maintained in 2026? Its GitHub repository and PyPI package exist and remain installable, but the most recent published release, version 0.6.1, dates to April 2024, with no newer release found as of this writing. Treat it as stable but slow-moving rather than actively evolving.
Does Fiddler AI still offer dedicated bias-detection features? Fiddler’s current public product pages emphasize agentic AI evaluation, observability, and guardrails rather than a standalone bias-detection feature; its fairness-specific “Bias Detector” material on its own site is dated to 2021. Confirm current fairness capabilities directly with Fiddler before purchasing for that specific use case.
Is the Fiddler/CrowdStrike acquisition finalized? As of this writing, Fiddler’s own website displays a banner announcing the acquisition but does not state deal terms or a closing date, so treat it as pending rather than closed.
Does Credo AI provide specific fairness metrics like AIF360 does? Credo AI’s public marketing centers on AI registries, risk intelligence, and policy/compliance mapping; it does not publicly detail specific statistical fairness metrics on its homepage, so this should be confirmed directly with the vendor for any procurement decision.
Can these tools be used together? Yes — a common real-world pattern is running AIF360 or similar metric libraries during model development, then using a platform like Fiddler or Credo AI for ongoing production monitoring and compliance documentation after deployment.
Small businesses shopping for an HRIS in 2026 are usually choosing between three very different pricing philosophies, not just three feature lists. BambooHR sells named, stacked tiers. Rippling sells modular, à la carte products billed per employee. Gusto sells tightly scoped plans built around payroll first and HR second. All three publish at least some real numbers, which makes this comparison unusually verifiable — here’s what each one actually charges and includes, straight from their own pricing pages.
At a Glance
Tool
Best For
Starting Price
Standout Feature
BambooHR
Small businesses that want a dedicated, full-featured HRIS
$10–$10.25 per employee/month (Core); flat $250/month for 25 or fewer employees
Three clear tiers with compliance training and HR benchmarks built in
Rippling
Businesses that want to mix and match HR, IT, and finance tools
From $8 per employee/month plus a monthly base fee
Modular pricing across HRIS, IT, and payroll in one admin console
Gusto
Very small teams that want payroll and HR basics in one simple plan
$49/month base + $6 per person/month (Simple plan)
Transparent, flat per-plan pricing with no custom quote required
Short Verdict
Gusto is the easiest entry point for a very small, payroll-first business that wants predictable, published pricing with no sales call. BambooHR is the strongest pick once a company needs a genuine HRIS — performance reviews, compliance tracking, and HR analytics — and is willing to pay accordingly as it moves up tiers. Rippling fits fast-growing small businesses that expect to need IT and finance tools (device management, expense cards, global payroll) alongside HR, since its modular pricing lets you add those without switching systems later.
What Each Tool Actually Is
BambooHR is a standalone HRIS sold in three named tiers. Per BambooHR’s pricing page, Core covers employee records, reporting, hiring and onboarding, time-off and benefits tracking, wellbeing tools, HR benchmarks, one compliance course, on-demand pay, and an AI assistant for HR data questions. Pro adds performance management with 360° reviews and 1:1s, an employee community, recognition and rewards, 15 compliance courses, and a policy-aware AI assistant. Elite adds compensation management with Mercer salary benchmarking, custom dashboards, 300+ compliance courses, and premium support. The page states per-employee rates of $10 (Core), $17 (Pro), and $25 (Elite) per month in one spot, but its own FAQ lists $10.25 and $17.50 for Core and Pro respectively — a discrepancy worth confirming directly with BambooHR before budgeting. Small companies of 25 employees or fewer instead pay flat monthly rates of $250 (Core), $425 (Pro), or $650 (Elite), and BambooHR offers a 15% bundle discount when Payroll and Benefits Administration are added, plus an extra 15% for registered nonprofits.
Rippling does not sell named plans at all. According to Rippling’s pricing page, it prices modularly: “Rippling plans start at $8 per employee per month” plus a separate monthly base fee, with the final cost depending entirely on which modules you select. Its HR product line includes HRIS, HR Services, Recruiting, Headcount Planning, Performance, Surveys, Learning Management, Benefits Administration, PEO, Time & Attendance, Scheduling, and Chat — each priced and quoted individually. Payroll, Global Payroll, Employer of Record, and Contractor of Record are sold the same way, as separate modules with custom quotes rather than published per-module rates.
Gusto is the most transparently priced of the three. Gusto’s pricing page lists Simple at $49/month base plus $6 per person/month, covering unlimited payroll runs, tax filings and payments, and basic PTO and holiday pay. Plus is $80/month base plus $12 per person/month, adding time tracking and scheduling, unlimited next-day pay, multi-state payroll, and contractor invoice management. Premium is $180/month base plus $22 per person/month, adding premium account support, HR guidance tools, compliance support, unlimited same-day and instant pay, project-based costing, and 25 included invoice payments per month.
Pricing Breakdown
Plan
Base Price
Per-Person Price
Notes
BambooHR Core
$250/mo flat for ≤25 employees
$10–$10.25/mo
Pricing page and FAQ list slightly different per-employee rates
BambooHR Pro
$425/mo flat for ≤25 employees
$17–$17.50/mo
Adds performance management and more compliance courses
BambooHR Elite
$650/mo flat for ≤25 employees
$25/mo
Adds compensation management and advanced analytics
Rippling
Custom monthly base fee
From $8/mo
Final price depends on which modules you select; no published tiers
Gusto Simple
$49/mo
$6/mo
Payroll and basic PTO only
Gusto Plus
$80/mo
$12/mo
Adds time tracking, multi-state payroll
Gusto Premium
$180/mo
$22/mo
Adds HR guidance and compliance support
Pros
BambooHR: Clear, named tiers make it easy to know exactly what you’re paying for as you scale up features.
Rippling: Modular pricing means you only pay for HR, IT, or finance modules you actually need, and can add more later without migrating.
Gusto: Every price is published on the website with no sales call required to find a starting number.
Cons
BambooHR: Its own pricing page and FAQ disagree on Core and Pro per-employee rates, so you should confirm current pricing directly with sales.
Rippling: No published per-module rates beyond the $8 starting figure, so the real monthly cost only appears after a custom quote.
Gusto: Deeper HR functionality (performance management, compensation benchmarking) isn’t part of its scope the way it is for BambooHR or Rippling.
Who It’s a Good Fit For
Gusto fits a small team — often under 25 people — that mainly needs reliable payroll with light HR support layered on top, and wants to see real pricing before talking to anyone. BambooHR fits a growing small business that has outgrown spreadsheet HR and wants dedicated tools for performance, compliance, and reporting, with a clear upgrade path as headcount grows. Rippling fits a small business that is scaling quickly and expects to need IT provisioning or multi-country payroll soon, since adding those modules later doesn’t require switching platforms.
Who Should Look Elsewhere
Businesses that want one simple, fixed monthly bill with no module-by-module decisions may find Rippling’s à la carte pricing more complex than they want to manage. Teams that need deep performance management or compensation benchmarking from day one will find Gusto’s scope too limited. Companies that are extremely price-sensitive on a per-employee basis should get a live Rippling quote before assuming its $8 starting figure reflects their real, fully loaded cost.
Bottom Line
For most small businesses just getting their first real HRIS, Gusto’s published, flat-rate plans remove the most friction. Once performance management, compliance training, and compensation data become priorities, BambooHR’s tiered structure is the more natural next step. Rippling is worth serious evaluation if you expect HR needs to expand into IT or multi-country payroll — just get a detailed module-by-module quote rather than budgeting off the $8 headline figure.
FAQ
Why do BambooHR’s pricing page and FAQ show different numbers? BambooHR’s own site lists $10 and $17 per employee/month for Core and Pro in one place and $10.25 and $17.50 in its FAQ. The source doesn’t explain the gap, so confirm the current rate with BambooHR directly.
Does Rippling have a published price list? No. Rippling confirms only a starting per-employee rate of $8 plus an unspecified monthly base fee; actual pricing depends on which modules you select and requires a custom quote.
Which plan is cheapest for a 10-person company? Based on published rates, Gusto Simple ($49 + $6/person, or $109/month for 10 employees) is the lowest verifiable starting cost of the three, though BambooHR’s flat $250/month Core rate for companies of 25 or fewer could be cheaper or more expensive depending on your exact headcount and desired features.
Does Gusto offer a nonprofit or bundle discount like BambooHR? Gusto’s pricing page, as reviewed here, does not mention nonprofit or bundling discounts; BambooHR explicitly offers a 15% bundle discount for Payroll plus Benefits Administration and an additional 15% for registered nonprofits.
Can I add global payroll to any of these three? Rippling explicitly lists Global Payroll and Employer of Record as add-on modules. BambooHR’s pricing page does not mention global payroll. Gusto is U.S.-focused and its pricing page does not list international payroll.
API testing tools have quietly become one of the most contested corners of the developer tools market. Pricing changes at the category leader, a corporate acquisition reshaping a competitor, and a wave of lightweight, Git-native alternatives have all hit within the same year. If you’re choosing (or re-choosing) an API client in 2026, the decision now hinges as much on licensing and pricing philosophy as on feature checklists. This comparison looks at three of the most-discussed options: Postman, the long-time incumbent; Insomnia, Kong’s open-core client; and Bruno, the offline-first, Git-friendly newcomer.
At a Glance
Tool
Best For
Starting Price
Collection Storage
Offline Use
Postman
Teams needing full API lifecycle tooling, mocks, and monitoring
Free; Solo $9/mo, Team $19/user/mo (annual)
Cloud workspaces
Limited without login
Insomnia
Teams wanting Git-based sync with a generous free tier
Free (Essentials); Pro $12/user/mo
Cloud or Git sync
Yes, via local vault
Bruno
Developers who want a fully offline, file-based, Git-native client
Free (MIT-licensed core); Pro $6/user/mo
Local filesystem (.bru files)
Yes, by design
Short Verdict
Postman remains the deepest platform if your team needs mock servers, monitoring, and governance in one place, but its per-seat pricing adds up quickly and the product has grown heavier over the years. Insomnia sits in the middle: a genuinely useful free tier, Git sync, and a cleaner UI than Postman, now backed by Kong’s enterprise sales machine. Bruno is the one to pick if you’re tired of cloud accounts altogether — it stores requests as plain-text files you commit alongside your code, with no sync requirement at all.
What Each Tool Actually Is
Postman is a full API platform rather than just a request client: it bundles an API client, mock servers, automated collection runners, performance testing, API specs, and (more recently) AI-assisted request generation into one product, all built around cloud-hosted workspaces. It’s the tool most developers learned API testing on, and its collection format has become a de facto standard that other tools import.
Insomnia, owned by Kong since 2019, is a desktop API client that supports REST, GraphQL, gRPC, and WebSocket testing, with Git-based or cloud sync for sharing collections across a team. Kong positions it as an entry point into its broader API gateway and governance ecosystem, which shows up in Enterprise-tier features like SSO and SOC2-aligned controls.
Bruno is an open-source (MIT-licensed), offline-only API client that stores each request as a plain-text file (its own “Bru” markup format) directly on disk inside your project folder. There’s no mandatory cloud account: collections are versioned with Git like any other source file. The paid tiers add deeper Git provider integration, team administration, and support rather than gating the core request/response workflow.
Pricing Breakdown
Plan
Postman
Insomnia
Bruno
Free tier
$0 — 100 AI credits/mo, core API client, mock servers, collection runner
$0 (Essentials) — Git Sync for up to 3 users, unlimited projects, 1,000 mock requests/mo
A few billing details worth flagging: Postman’s paid tiers are quoted as annual rates, with a savings of up to 25% versus monthly billing, and the Enterprise tier pools AI credits across seats. Insomnia’s Pro and Enterprise figures come from its public pricing page, though the page doesn’t clarify whether the $12/user figure is monthly or annual billing, so budget-conscious teams should confirm at checkout. Bruno’s paid tiers all list annual billing; its Enterprise plan is also available via quote for organizations needing invoicing or custom terms.
Pros
Postman: The most complete feature set in one product — API client, mocking, monitoring, and documentation generation without stitching together separate tools.
Insomnia: A free tier that already includes Git Sync and unlimited collection runs, plus a noticeably lighter interface than Postman’s.
Bruno: Requests live as readable text files in your own repo, so there’s nothing to export, no vendor lock-in, and code review works on API tests the same way it works on code.
Cons
Postman: Per-seat Team pricing at $19/user/month (annual) gets expensive fast for larger teams, and the free tier’s AI credit limits are easy to exhaust.
Insomnia: Jumping to Enterprise for SSO or SCIM is a steep leap at $45/user/month, with no clearly priced mid-tier option for that specific need.
Bruno: The open-source edition caps you at 2 workspaces and 5 OpenAPI syncs a month, and because it’s offline-only by design, there’s no built-in cloud sync if your team specifically wants that convenience.
Who It’s a Good Fit For
Postman suits organizations that want one vendor covering the whole API lifecycle — design, mocking, testing, monitoring, and internal documentation — and that have budget for per-seat licensing. Insomnia fits teams already inside Kong’s ecosystem (or considering an API gateway) who want a capable free client with a clear upgrade path to governance features. Bruno is the natural choice for engineering teams that already treat everything as code: if your workflow is “clone the repo, open the editor, run the tests,” Bruno’s filesystem-based collections slot in without friction.
Who Should Look Elsewhere
If you need a lightweight tool and have no interest in mock servers, API monitoring, or governance dashboards, Postman’s breadth may just feel like overhead. If your team has strict no-cloud-storage requirements for request data, Insomnia’s free and Pro tiers still lean on cloud or Git sync conveniences that some security teams will want to scrutinize closely. And if you specifically need polished, built-in collaboration features like shared cloud workspaces with fine-grained roles out of the box, Bruno’s open-source core won’t give you that without moving to a paid tier.
Bottom Line
There isn’t a single “best” API client anymore — there’s a best fit for how your team already works. Postman still wins on raw feature depth, Insomnia offers the best balance of a usable free tier and a path to enterprise controls, and Bruno is the cleanest answer for teams that want API testing to behave like any other version-controlled artifact in the codebase.
FAQ
Is Bruno really free for commercial use? Yes — Bruno’s core client is MIT-licensed and free for individuals and teams. The Open Source plan limits you to 2 workspaces and 5 OpenAPI syncs per month; paid plans remove those caps and add admin/support features.
Can I import my existing Postman collections into Insomnia or Bruno? Both Insomnia and Bruno support importing Postman collection exports, which is one of the most common reasons teams evaluate a switch.
Does Postman’s free tier still work for solo developers? Yes, but it’s now scoped around AI credits (100/month) alongside the core client, mock servers, and collection runner — fine for light use, but power users testing extensively with AI features will likely need Solo or Team.
Which tool is best for CI/CD pipelines? All three ship a CLI or CI-friendly runner (Postman’s Newman, Insomnia’s inso CLI, and Bruno’s own CLI with official Docker images), so this comes down to which collection format your team already maintains.
Do any of these require a cloud account to use at all? Bruno does not — it works fully offline with local files. Postman and Insomnia both expect an account for their full feature set, though Insomnia’s Git Sync option limits how much request data touches their cloud.
Choosing an applicant tracking system is one of the few software decisions that touches almost every department: recruiters live in it daily, hiring managers are judged by how fast it moves candidates through a pipeline, and finance watches the invoice. Greenhouse, Lever, and Workday Recruiting are three of the most common names that come up in 2026 shortlists, but they are built for different hiring philosophies and, in two of the three cases, neither vendor publishes a public price list. This guide compares what each platform actually does, what’s verifiable about cost, and who each one genuinely fits.
At a Glance
Tool
Best For
Pricing Model
Standout Feature
Greenhouse
Structured, scalable hiring at mid-size to large companies
Custom quote, three tiers (Core, Plus, Pro)
Structured interview kits and scorecards built into the core workflow
Lever
Teams that want ATS + CRM sourcing in one system
Custom quote, single core platform plus paid add-ons
Built-in CRM for proactive sourcing and talent pipelines
Workday Recruiting
Large enterprises already running Workday HCM
Enterprise quote, bundled with Workday HCM licensing
Native integration with Workday’s workforce planning and compensation data
Short Verdict
Greenhouse is the strongest pick for companies that want a dedicated, structured ATS without being locked into a broader HR suite. Lever suits teams whose biggest bottleneck is sourcing rather than process rigor, since its CRM is native rather than bolted on. Workday Recruiting rarely makes sense as a standalone choice — it earns its place almost exclusively inside organizations that already run Workday HCM and want recruiting data to live next to compensation, workforce planning, and onboarding in one system.
What Each Tool Actually Is
Greenhouse is a dedicated applicant tracking and hiring platform organized around three tiers that each build on the last. According to Greenhouse’s own pricing page, the Core plan includes sourcing and CRM tools, structured interview kits and scorecards, an AI notetaker, scheduling, reporting, and single sign-on. Plus adds AI-powered report filters, a business intelligence connector, sourcing automation, and texting. Pro adds unlimited CRM events, enterprise-level data configuration and security, audit logs, and a developer sandbox. Greenhouse does not publish prices for any tier; the page directs every plan to a “Get a demo” conversation instead.
Lever positions itself as an “AI-powered hiring platform” built around a single core offering that combines ATS and CRM functionality in one interface, rather than Greenhouse’s layered tiers. Per Lever’s pricing page, that core platform includes reporting and analytics, AI screening, unlimited AI interview transcripts and summaries, and AI fraud-prevention signals, plus key integrations. Lever sells Candidate Insights, AI Screening by VONQ, and Onboarding as separate paid add-ons, each requiring its own quote. Like Greenhouse, no list prices are published; the site states pricing scales with team size and hiring needs.
Workday Recruiting is a module inside the broader Workday Human Capital Management suite rather than a freestanding ATS. Workday’s own product page emphasizes that it works “with the rest of Workday,” spanning workforce planning through onboarding. Features described on that page include a centralized Recruiting Hub, candidate review from any device, one-click internal promotions with linked requisitions, offers built from live compensation data, shared interview feedback with calendar sync, a referral leaderboard, and high-volume hiring tools like bulk dispositions and evergreen requisitions. Its only AI mention on that page is “machine learning recommendations” inside its analytics dashboards — it does not advertise AI resume screening the way Lever or Greenhouse’s Real Talent features do. No pricing is listed anywhere on the page; enterprise buyers go through “Contact Sales.”
Pricing Breakdown
Tool
Published Starting Price
How Pricing Works
Greenhouse
Not published
Three named tiers (Core, Plus, Pro); every plan requires a custom quote based on company size and hiring volume
Lever
Not published
One core platform priced on a quote basis; Candidate Insights, AI Screening by VONQ, and Onboarding are separately quoted add-ons
Workday Recruiting
Not published
Sold as part of a Workday HCM enterprise contract; no self-serve or published tiering
None of the three vendors publish list prices, which is typical for ATS platforms sold to mid-market and enterprise buyers. Any specific dollar figure you see quoted on third-party comparison sites is an estimate, not an official rate, so budget for a sales conversation and a request for references from companies of similar size before signing.
Pros
Greenhouse: Structured interview kits and scorecards are built into the core workflow from day one, which helps reduce ad hoc, inconsistent interviewing.
Lever: CRM and ATS live in the same system, so sourcing and pipeline management don’t require a second tool.
Workday Recruiting: Recruiting data, compensation, and workforce planning sit in one data model, so offers can be built directly from live comp data without exporting anything.
Cons
Greenhouse: Advanced features like unlimited CRM events and audit logs are reserved for the top Pro tier, which pushes larger teams toward the most expensive plan.
Lever: Onboarding and AI screening are not included in the core platform — both are paid add-ons quoted separately.
Workday Recruiting: It is not sold as a standalone ATS in practice; adopting it generally means buying into the wider Workday HCM ecosystem.
Who It’s a Good Fit For
Greenhouse fits companies that want to formalize interviewing and scale hiring consistently, especially those growing past the point where a spreadsheet or a lightweight tool can keep up. Lever fits recruiting teams whose real constraint is top-of-funnel sourcing — agencies, high-growth startups, and in-house teams that proactively build talent pools rather than only reacting to inbound applications. Workday Recruiting fits large enterprises that have already standardized on Workday HCM and want recruiting to be one more module in that single system of record, not a separate point solution.
Who Should Look Elsewhere
Small businesses and lean teams without dedicated recruiting headcount will likely find all three platforms more process than they need, and should consider lighter-weight or free-tier ATS tools instead. Companies that are not already Workday customers have little reason to adopt Workday Recruiting on its own, since its biggest advantages come from integration with modules most non-Workday shops don’t have.
Bottom Line
There isn’t a single “best” ATS among these three — the right choice depends on whether your bottleneck is process structure (Greenhouse), sourcing volume (Lever), or enterprise-wide data unification (Workday Recruiting). Because none of the three publish prices, treat any number you see elsewhere as a rough estimate and get a live quote based on your actual headcount and hiring volume before comparing total cost.
FAQ
Does any of these three publish public pricing? No. Greenhouse, Lever, and Workday Recruiting all require a custom quote, confirmed directly on each vendor’s own pricing or product page as of this writing.
Can I buy Workday Recruiting without the rest of Workday HCM? Workday’s own materials present Recruiting as integrated with the rest of the HCM suite, spanning workforce planning through onboarding, so it is sold and used primarily as part of a broader Workday deployment rather than as an isolated module.
Does Lever include onboarding? No. Lever sells Onboarding as a separate paid add-on alongside Candidate Insights and AI Screening by VONQ, each quoted independently of the core platform.
Which tool has the most built-in AI screening features? Based on each vendor’s own pages, Lever’s core platform explicitly lists AI screening and AI fraud-prevention signals; Greenhouse’s AI features (AI Notetaker, AI-powered report filters) are more oriented toward productivity than candidate scoring; Workday Recruiting’s only stated AI capability is machine-learning recommendations inside its analytics dashboards.
Is Greenhouse or Lever better for a startup? It depends on the constraint: Greenhouse’s structured kits suit a startup trying to professionalize its interview process, while Lever’s native CRM suits one focused on building and nurturing a sourcing pipeline before roles even open.
Yes, if the heuristic is admissible (and consistent, for efficient graph search)
Yes
Same worst-case bound as Dijkstra; typically far fewer node expansions in practice
One-to-one pathfinding with a known goal: game AI, robotics, puzzle solving
Contraction Hierarchies / Multi-Level Dijkstra (used by OSRM)
Yes
No runtime heuristic — relies on heavy offline preprocessing of the graph instead
Near-instant query time after preprocessing; preprocessing itself is expensive
Continent-scale GPS and road-network routing
How Dijkstra’s Algorithm Works
Dijkstra’s algorithm finds the shortest path from a single source node to every other reachable node in a weighted graph with non-negative edge weights. It works greedily: maintain a running “tentative distance” for every node (infinity for all but the source, which starts at zero), and repeatedly pick the unvisited node with the smallest tentative distance, mark it visited, and “relax” its outgoing edges — that is, check whether reaching a neighbor through this node would beat the neighbor’s current best-known distance, and update it if so. Because non-negative weights mean distances can only grow as you add edges, once a node is marked visited its tentative distance is guaranteed final; the algorithm never needs to revisit it. A priority queue (min-heap) is what makes “pick the smallest tentative distance” efficient instead of a linear scan every step.
Time and Space Complexity
With a binary heap as the priority queue, Dijkstra’s algorithm runs in O((V+E) log V) time, where V is the number of vertices and E the number of edges — each vertex is extracted from the heap once (O(log V) each) and each edge can trigger one heap update (also O(log V) each). With a Fibonacci heap, the bound improves to O(E + V log V), a classical result from Fredman and Tarjan (1984); the Fibonacci heap’s amortized O(1) “decrease-key” operation removes the log factor from the edge-relaxation term, leaving the log factor only on the V heap-extraction operations. In practice, binary heaps are far more common in production code because of their simplicity and good cache behavior, even though Fibonacci heaps are asymptotically better for sparse graphs with many more edges than vertices. Space complexity for both is O(V + E), dominated by storing the graph and the distance/visited tracking structures.
A Minimal Dijkstra Implementation in Python
import heapq
def dijkstra(graph, source):
"""Return shortest distances from source to every reachable node.
graph: dict mapping node -> list of (neighbor, non_negative_weight) tuples
"""
distances = {source: 0}
visited = set()
heap = [(0, source)]
while heap:
current_dist, node = heapq.heappop(heap)
if node in visited:
continue
visited.add(node)
for neighbor, weight in graph.get(node, []):
if weight < 0:
raise ValueError("Dijkstra requires non-negative edge weights")
candidate = current_dist + weight
if candidate < distances.get(neighbor, float("inf")):
distances[neighbor] = candidate
heapq.heappush(heap, (candidate, neighbor))
return distances
if __name__ == "__main__":
graph = {
"A": [("B", 4), ("C", 1)],
"B": [("D", 1)],
"C": [("B", 2), ("D", 5)],
"D": [],
}
print(dijkstra(graph, "A"))
# {'A': 0, 'C': 1, 'B': 3, 'D': 4}
How A* Improves on Dijkstra
A* is Dijkstra’s algorithm with one addition: instead of ranking nodes purely by the known cost-so-far g(n), it ranks them by f(n) = g(n) + h(n), where h(n) is a heuristic estimate of the remaining cost from node n to the goal. This lets A* bias its search toward the goal instead of expanding outward uniformly in every direction, which is why A* so often explores dramatically fewer nodes than plain Dijkstra when a good heuristic is available and a specific target is known in advance.
Two formal properties of the heuristic determine what A* can guarantee. A heuristic is admissible if it never overestimates the true remaining cost to the goal — it’s an optimistic lower bound, and h(goal) = 0. An admissible heuristic guarantees A* returns an optimal (shortest) path. A heuristic is consistent (also called monotone) if, for every edge (x, y), h(x) ≤ cost(x, y) + h(y) — a form of the triangle inequality. Consistency is the stronger property: it guarantees that once A* finalizes a node’s cost, that cost is optimal and the node never needs to be re-expanded, which is what lets an efficient graph-search implementation safely use a closed list. On classic grid maps, common admissible-and-consistent heuristics are Euclidean distance (any movement allowed) or Manhattan distance (four-directional grid movement only).
On complexity: A*’s worst case is the same O((V+E) log V) bound as Dijkstra with a binary heap, since A* is essentially Dijkstra running on a reweighted version of the graph. The informal “O(b^d)” intuition sometimes cited for A* — where b is the branching factor and d is the depth of the shallowest solution — is a rough mental model for tree search, not a precise bound for graph search; the real-world payoff of A* comes from expanding far fewer nodes in practice with a good heuristic, not from a better worst-case guarantee.
Dijkstra vs A*
Dijkstra
A*
Search pattern
Expands outward from the source roughly uniformly in all directions
Biases expansion toward the goal using the heuristic
Needs a specific goal upfront?
No — naturally solves one-to-all
Yes — the heuristic requires knowing the target
Heuristic required
No
Yes (admissible for correctness; consistent for efficient re-expansion-free search)
Worst-case time complexity (binary heap)
O((V+E) log V)
Same worst-case bound; typically far fewer nodes expanded in practice
Real-World Applications
A* is a staple of game AI pathfinding: NPC movement, unit pathing in strategy games, and navmesh-based navigation in 3D games commonly run A* (or a variant) over a grid or navigation mesh, where Euclidean or Manhattan distance to the target makes a cheap, admissible heuristic.
GPS and road-network routing is a more nuanced story, and it’s worth correcting a common assumption here: not every major routing engine actually runs A* under the hood. OSRM (the Open Source Routing Machine), one of the most widely used open-source routing engines, explicitly does not use A* as its core algorithm. According to OSRM’s own GitHub README, it offers two pre-processing pipelines instead: Contraction Hierarchies (CH) and Multi-Level Dijkstra (MLD), with the project stating “we recommend using MLD by default except for special use cases such as very large distance matrices,” where CH is favored instead. Both techniques work by heavily preprocessing the road graph offline — adding “shortcut” edges that skip over long chains of low-importance roads — so that at query time, a much smaller search (still fundamentally a form of Dijkstra, run over the pre-contracted graph) can return a shortest path in milliseconds across a continent-scale map. Plain Dijkstra or A* run directly on a raw, unprocessed road graph simply can’t hit that latency at that scale; the heavy lifting happens ahead of time, not per query.
Trade-offs
Use plain Dijkstra when you genuinely need distances to every node from a single source (one-to-all), or when no good heuristic is available. Use A* when you have a single, known target and a cheap, reliable heuristic — it will typically explore a small fraction of the nodes Dijkstra would, with no loss of optimality given an admissible heuristic. Use precomputed hierarchical methods like Contraction Hierarchies or Multi-Level Dijkstra when the graph is large and mostly static (a road network that changes rarely) and you need repeated queries answered in milliseconds — the upfront preprocessing cost pays for itself across the huge number of queries a mapping service handles.
Bottom Line
Dijkstra and A* solve the same core problem — shortest paths in a weighted graph — but A* is only strictly better when you have a known destination and a good, admissible heuristic; otherwise it degenerates to Dijkstra anyway (a heuristic that’s always zero makes A* identical to Dijkstra). For massive, mostly-static graphs like road networks, production routing engines increasingly skip both in their pure form and lean on precomputed speed-up techniques such as Contraction Hierarchies and Multi-Level Dijkstra, as OSRM’s own documentation confirms.
FAQ
Does A* always outperform Dijkstra? Only when a good admissible heuristic exists and you’re searching for a single specific target. For one-to-all shortest paths, or when no reasonable heuristic is available, Dijkstra is the appropriate tool — and with a zero heuristic, A* simply becomes Dijkstra.
What happens if an A* heuristic isn’t admissible? A* can return a suboptimal (not-shortest) path, because an overestimating heuristic can cause the algorithm to prune a node that actually lies on the true shortest path.
Do real GPS navigation apps use A*? Not necessarily. OSRM, a major open-source routing engine, uses Contraction Hierarchies and Multi-Level Dijkstra instead of A*, precomputing shortcuts over the road graph so queries resolve in milliseconds. Other routing engines may use different techniques; A* is not a universal standard for production-scale road routing.
Can Dijkstra’s algorithm handle negative edge weights? No. Dijkstra assumes non-negative weights because its correctness proof relies on distances only increasing as paths get longer. Graphs with negative edge weights need a different algorithm, such as Bellman-Ford.
No fixed numeric ceiling published; Kafka’s own docs emphasize that performance “stays roughly constant” as retained data grows
RabbitMQ
Traditional AMQP message broker (exchanges, bindings, queues)
FIFO within a single queue
~80,000 msgs/sec on a replicated, fsync’d quorum queue; ~100,000 msgs/sec on a classic queue; multiple millions/sec via streams (all per RabbitMQ’s own published figures)
Amazon SQS
Fully managed cloud queue service (Standard or FIFO)
Standard: best-effort only. FIFO: strict order per message group
FIFO: 300 TPS/action unbatched, 3,000 msgs/sec batched; up to 70,000 TPS/action (region-dependent) with High Throughput Mode
How Kafka Works: A Distributed Commit Log
Kafka’s own documentation describes events as being “organized and durably stored in topics,” which are multi-producer and multi-subscriber. Unlike a traditional queue, a message isn’t deleted once it’s read — Kafka retains events for as long as a configured retention period dictates, and performance stays roughly constant regardless of how much data has accumulated, since reads and writes are essentially sequential disk operations against an append-only log.
Each topic is split into partitions, which spread the topic across multiple brokers so clients can read and write in parallel. This is where Kafka’s ordering guarantee lives: events with the same key are routed to the same partition, and Kafka guarantees a consumer reading a given topic-partition receives events “in exactly the same order as they were written.” Crucially, that guarantee is per-partition, not per-topic — if you need strict ordering across an entire topic, you need exactly one partition, which caps your write parallelism. Brokers form the storage layer of a cluster, and topic-partitions are typically replicated (a replication factor of 3 is common in production), so that if one broker fails, another takes over without losing acknowledged data.
How RabbitMQ Works: Exchanges, Bindings, and Queues
RabbitMQ implements the AMQP messaging model (0-9-1 historically, with the RabbitMQ team now recommending AMQP 1.0 for new applications). Publishers don’t send messages directly to a queue — they send to an exchange, which routes the message according to its type and its bindings. RabbitMQ’s documentation defines four exchange types: direct (exact routing-key match), fanout (ignores the routing key, copies to every bound queue), topic (pattern-matches the routing key, for selective pub/sub), and headers (routes on header values rather than the routing key). Every queue is also automatically bound to a nameless default direct exchange using its own name as the routing key.
Queues themselves are strictly FIFO: ordered collections where messages are enqueued at the tail and dequeued from the head. RabbitMQ’s current documentation is explicit about a key architectural limit: “a single queue replica (whether leader or follower) is limited to a single CPU core on its hot code path,” which is why RabbitMQ recommends using multiple queues rather than one giant queue when you need to scale throughput — a single queue is called out as generally an anti-pattern at scale. For workloads that need to push past normal queue throughput, RabbitMQ offers streams: append-only, replicated logs with offsets and replay, conceptually closer to Kafka partitions than to a classic AMQP queue. Modern RabbitMQ also offers quorum queues (Raft-replicated, fsync’d per message before confirming) as the default durable queue type, trading some throughput for stronger delivery guarantees than classic queues.
How Amazon SQS Works: Fully Managed, Two Queue Types
SQS removes broker management entirely — AWS runs the service, and you interact with it only through the SendMessage, ReceiveMessage, and DeleteMessage API actions. Standard queues favor throughput over strict ordering: the AWS documentation says they support “a very high, nearly unlimited number of API calls per second, per action,” but ordering is best-effort and duplicate delivery is possible (at-least-once delivery).
FIFO queues trade some of that throughput for strict ordering within a message group and exactly-once processing. Per the AWS SQS Developer Guide, a standard (non-high-throughput) FIFO queue supports 300 transactions per second per API action without batching, or up to 3,000 messages per second per API action when batching up to 10 messages into a single call. For higher scale, AWS offers High Throughput Mode for FIFO queues, which raises per-API-action limits well beyond that — but the ceiling is region-dependent. In US East (N. Virginia), US West (Oregon), and Europe (Ireland), the documented limit is 70,000 TPS per action unbatched (700,000 messages/second batched); other regions step down from there, with a default of 2,400 TPS unbatched (24,000 batched) in regions not otherwise listed. These limits apply per API action and can be increased further via a Service Quotas request.
Throughput and Ordering Guarantees Compared
System
Ordering Scope
Officially Published Throughput Figures
Apache Kafka
Within a single topic-partition only
No numeric throughput ceiling is published in Kafka’s own docs; capacity scales with partition count and broker hardware
RabbitMQ (quorum queue)
FIFO within the queue
~80,000 messages/sec while replicating and fsyncing each message (RabbitMQ’s own comparison page)
RabbitMQ (classic queue)
FIFO within the queue
~100,000 messages/sec
RabbitMQ (streams)
Offset-ordered within a stream
Several million messages/sec on a single well-batched stream; over 17 million messages/sec combined across five streams in RabbitMQ’s own benchmark
Up to 70,000 TPS/action unbatched / 700,000 msgs/sec/action batched in top-tier regions; as low as 2,400 TPS/action (24,000 batched) by default elsewhere
Trade-offs: Choosing the Right Tool
These three systems solve different problems well enough that “which is fastest” is often the wrong question. Kafka’s log-based model is built for durable, replayable event streams that multiple independent consumers read at their own pace — event sourcing, change-data-capture pipelines, and analytics ingestion are natural fits, and its own comparison documentation (published by RabbitMQ, which has every incentive to be fair here since it’s comparing itself) singles out tiered storage and log compaction as Kafka-only strengths. RabbitMQ’s exchange-and-binding model shines for task queues, RPC-style workloads, and routing logic that changes at runtime — its per-message features (TTL, 32 priority levels, delayed retry, dead-letter routing) suit workloads where individual messages matter, not just aggregate throughput. SQS trades flexibility for zero operational burden: there’s no cluster to patch, scale, or fail over, which is why it’s the default choice for decoupling services inside AWS, as long as your throughput needs fit inside its documented FIFO quotas (or you’re willing to shard across many message groups and queues to work around them).
Worth noting: RabbitMQ’s own documentation is candid that benchmark comparisons between Kafka and RabbitMQ streams land “in the same ballpark” for raw throughput and latency, and that one-sided tuning easily distorts any benchmark. Treat all vendor-published throughput numbers, including the ones in this article, as upper bounds achieved under specific, favorable configurations rather than guaranteed real-world results.
Bottom Line
Choose Kafka when you need a durable, replayable event log that many independent consumers read at different speeds. Choose RabbitMQ when you need flexible routing, per-message delivery guarantees, and priority/retry semantics for task-queue-style workloads, and you’re prepared to operate a broker (or use a managed one). Choose Amazon SQS when you’re already on AWS and want a queue with effectively no operational overhead, understanding that FIFO ordering comes with specific, documented throughput quotas you need to design around.
FAQ
Does Kafka guarantee global ordering across an entire topic? No. Kafka only guarantees order within a single partition. A topic with multiple partitions has no guaranteed cross-partition order; if you need strict topic-wide ordering, use a single partition.
What’s the real throughput ceiling for RabbitMQ? There’s no single number — it depends on queue type. RabbitMQ’s own documentation cites roughly 80,000 messages/second for a replicated, fsync’d quorum queue, about 100,000/second for a classic queue, and several million per second using streams, with the caveat that these figures depend heavily on configuration and batching.
Can an SQS FIFO queue scale past 300 TPS? Yes, two ways: batch up to 10 messages per API call (up to 3,000 msgs/sec/action), or enable High Throughput Mode, which raises the per-action ceiling as high as 70,000 TPS unbatched in supported regions.
Which of the three requires the least operational overhead? Amazon SQS, since AWS fully manages it end to end. Kafka and RabbitMQ both require you to operate a cluster yourself unless you use a managed offering (e.g. Confluent Cloud, Amazon MSK, or a managed RabbitMQ service).
Google Vertex AI AutoML (now under the Gemini Enterprise Agent Platform)
Usage-based, no flat platform fee — you pay separately for training hours, deployed endpoint-hours, and predictions (e.g. AutoML Vision training lists at $3.465/hour)
No AutoML-specific free tier; only Google Cloud’s general trial credit
Teams already on Google Cloud that want no-code tabular or image models without managing infrastructure
DataRobot
Not publicly listed — custom quote required
Free trial via sign-up (credit-based)
Enterprises wanting a governance-heavy, fully managed AutoML/MLOps platform and willing to negotiate a contract
Azure Machine Learning (AutoML)
No platform fee — you pay only for the underlying compute, billed by the second
No AutoML-specific free tier; general Azure trial ($200 credit / 30 days)
Teams in the Microsoft/Azure ecosystem wanting code-optional AutoML across tabular, vision, and NLP tasks
Short Verdict
None of these three platforms charges a traditional “per-seat” software license for AutoML. Instead they split into two very different pricing philosophies: Google and Microsoft both meter the underlying compute you consume, while DataRobot keeps its pricing off the public web entirely and negotiates per account. If transparent, pay-as-you-go pricing matters most, Azure Machine Learning and Vertex AI AutoML are easier to budget for than DataRobot. If you need a single vendor to manage governance, monitoring, and explainability for you at enterprise scale, DataRobot’s opacity on pricing is the trade-off for that white-glove positioning.
What It Is: Google Vertex AI AutoML
Vertex AI is Google Cloud’s unified machine learning platform, and AutoML is its no-code/low-code layer for training tabular, image, and forecasting models without writing model architecture code. There’s an important naming wrinkle worth flagging for 2026 buyers: Google’s own Vertex AI documentation now states that the Vertex AI docs are “no longer updated” and that its services are “now part of” the Gemini Enterprise Agent Platform. The current pricing page for this stack doesn’t use the term “Vertex AI” at all — it’s framed entirely around “Gemini platform” consumption and “Gemini Enterprise Flexible Savings Plan” discount tiers, while noting that costs “remain the same as they are for the legacy AI Platform and AutoML products that Gemini platform supersedes.” In practice, the underlying AutoML training and serving mechanics haven’t changed — the branding and documentation home have.
On capability: AutoML for tabular data (classification, regression, forecasting) and AutoML Vision (image classification, object detection) remain available today. AutoML Text and AutoML Video, however, are confirmed deprecated — AutoML Text was deprecated on September 15, 2024 and shut down on June 15, 2025; AutoML Video was deprecated on July 31, 2024 and shut down on July 31, 2025. Google’s guidance is to replace both with Gemini prompting and tuning workflows (for example, fine-tuning Gemini on labeled text or video for classification, entity extraction, or sentiment tasks) rather than a dedicated AutoML text/video trainer. Several even older “Legacy AutoML” products (Legacy AutoML Natural Language, Video Intelligence, Vision, and Tables) were also retired between 2023 and mid-2024, superseded first by Vertex AI and now folded into the Gemini Enterprise Agent Platform.
What It Is: DataRobot
DataRobot is an enterprise automated machine learning and MLOps platform built around a model “leaderboard” — it trains and ranks many candidate models automatically, then adds governance, monitoring, and explainability tooling on top for production deployment. It’s positioned less as a developer tool and more as an enterprise platform purchase, which shows up clearly in its pricing: DataRobot’s own pricing page lists no dollar figures or tiers at all, only calls to action to “Request a Demo” or start a trial. Third-party enterprise software review site TrustRadius corroborates this, stating plainly that DataRobot “offers customized solutions to their customers, so to obtain an estimate or demo, contact DataRobot’s team.” A free trial using usage credits is available, but production pricing is quote-only and reportedly varies by consumption model (hosted cloud vs. credit-based) and by deployment scale.
What It Is: Azure Machine Learning (AutoML)
Here’s a naming correction worth making explicit, since it trips up a lot of comparisons: “Azure Machine Learning Studio” and “Azure Machine Learning studio” are not quite the same thing anymore. The original drag-and-drop “Machine Learning Studio (classic)” was a separate, older product that Microsoft stopped allowing new resources on starting December 2021 and fully retired on August 31, 2024, directing customers to migrate to Azure Machine Learning. Today, “Azure Machine Learning studio” refers to the web UI of the modern Azure Machine Learning service — and that’s where its current no-code AutoML experience lives. Within that current service, Automated ML supports classification, regression, and time-series forecasting through the no-code studio UI, plus computer vision (multi-class/multi-label image classification, object detection, instance segmentation) and NLP (text classification, named entity recognition) through the CLI/SDK.
On pricing, Microsoft’s official pricing page is unambiguous: “there is no additional charge to use Azure Machine Learning.” You pay only for the compute you provision — billed per second with no long-term commitment — plus any other Azure services you choose to layer on, such as Blob Storage, Key Vault, Container Registry, or Application Insights, which are billed separately from Azure Machine Learning itself.
Pricing Breakdown
Platform
Training
Deployment / Hosting
Prediction
Vertex AI AutoML Vision
List price $3.465/hour (classification or object detection); $18.00/hour for edge/on-device training
$1.375/hour (classification) to $2.002/hour (object detection) while a model is deployed to an endpoint — billed even if idle
Batch prediction listed at $2.222/hour; 1-year and 3-year Flexible Savings Plan discounts reduce these rates (e.g. classification training drops to $3.1185/hr at 1 year, $2.772/hr at 3 years)
Vertex AI AutoML Tabular
$21.252 per node-hour (list)
Charged at standard custom-model inference rates (e.g. an n1-highmem-8 instance lists around $0.544/hour, plus any accelerator fees)
Same as deployment compute rate; Explainable AI is also charged at the inference rate
Vertex AI AutoML Forecasting
$21.252/hour (list)
N/A (prediction only)
Tiered per 1,000 forecasted data points, per month: $0.20 (first 1M), $0.10 (1M–50M), $0.02 (above 50M)
DataRobot
Not disclosed publicly
Not disclosed publicly
Not disclosed publicly — contact sales for a quote
Azure Machine Learning AutoML
No AutoML-specific fee — billed as standard compute by the second
No AutoML-specific fee — billed as standard compute
No AutoML-specific fee — billed as standard compute
Pros
Vertex AI AutoML
Transparent, published per-hour pricing for every stage (training, deployment, prediction)
Deep integration with the rest of Google Cloud’s data and AI tooling
Multi-year Flexible Savings Plan discounts for predictable workloads
DataRobot
Strong model governance, monitoring, and explainability tooling aimed at regulated enterprises
Automated model comparison (“leaderboard”) across many algorithm types in one run
Free trial available before committing to a quote
Azure Machine Learning
No platform fee at all — the simplest pricing model of the three
No-code AutoML UI for tabular tasks plus SDK-based AutoML for vision and NLP
Per-second compute billing with no long-term commitment required
Cons
Vertex AI AutoML
Documentation and branding are mid-transition to the Gemini Enterprise Agent Platform, which can confuse teams searching for “Vertex AI” guidance
AutoML Text and AutoML Video are gone — teams must re-architect around Gemini tuning instead
A deployed endpoint bills continuously until explicitly undeployed, even with zero traffic
DataRobot
No public pricing anywhere — budgeting requires a sales conversation before you know your cost
Harder for small teams or individual developers to evaluate cost-effectiveness quickly
Azure Machine Learning
No AutoML-specific free tier beyond the generic Azure trial credit
No-code AutoML UI is strongest for tabular data; vision and NLP AutoML require the SDK/CLI, reducing the “no-code” claim for those task types
Legacy naming overlap with the retired “Machine Learning Studio (classic)” still causes confusion in search results and older tutorials
Who It’s a Good Fit For / Who Should Look Elsewhere
Vertex AI AutoML fits teams already standardized on Google Cloud who want predictable, published unit pricing for tabular or vision models. Teams that relied on AutoML Text or AutoML Video should look elsewhere, or plan a migration to Gemini-based tuning instead.
DataRobot fits large, regulated enterprises that need governance and explainability baked in and have the procurement process to negotiate a custom contract. Smaller teams, startups, or anyone wanting to see a price before talking to a salesperson should look elsewhere.
Azure Machine Learning fits Microsoft-ecosystem teams that want the lowest-friction pricing model and are comfortable mixing a no-code UI (for tabular AutoML) with some SDK work (for vision/NLP AutoML). Teams wanting a single no-code UI that covers every data type equally well may find this split frustrating.
Bottom Line
There’s no single “cheapest” answer here because the pricing models aren’t comparable on the same axis: Vertex AI AutoML and Azure Machine Learning both meter compute transparently (Azure adds zero platform markup; Google publishes per-hour rates with volume discounts), while DataRobot simply doesn’t publish pricing and expects a sales conversation. For most teams building straightforward tabular or vision models inside an existing cloud, Vertex AI AutoML or Azure Machine Learning AutoML will be easier to budget for than DataRobot. DataRobot remains the right call primarily when governance and explainability tooling, not raw AutoML cost, are the deciding factor.
FAQ
Is “Vertex AI” still the correct name for Google’s AutoML platform? Functionally, yes — the underlying training and serving APIs are the same — but Google’s current documentation says the Vertex AI docs are no longer updated and that these services are now part of the Gemini Enterprise Agent Platform. Expect more rebranding in docs and pricing pages going forward.
Can I still train a new AutoML Text or AutoML Video model on Google Cloud? No. AutoML Text training ended with its June 15, 2025 shutdown, and AutoML Video training ended with its July 31, 2025 shutdown. Google directs new projects to Gemini prompting/tuning instead.
Does DataRobot publish any pricing at all? No. Its official pricing page contains no dollar figures or tiers — only demo and trial sign-up links. A free trial is available, but production pricing requires contacting sales.
Is today’s “Azure Machine Learning studio” the same product as a few years ago? Not quite. The old drag-and-drop “Machine Learning Studio (classic)” stopped accepting new resources in December 2021 and fully retired on August 31, 2024. “Azure Machine Learning studio” today is the web interface of the current Azure Machine Learning service, which includes the present-day AutoML feature.
Every major video-calling platform now has some kind of built-in transcript, but dedicated AI meeting notetakers go further: searchable transcripts, auto-generated summaries and action items, CRM syncing, and increasingly, “ask your meetings a question” chat interfaces. Otter.ai, Fireflies.ai, and Fathom are three of the most widely used standalone options. Here’s how their pricing, integrations, and — importantly — their data-handling policies compare, straight from each vendor’s own pages.
At a Glance
Tool
Starting Price
Free Plan
Best For
Otter.ai
$16.99/user/month billed monthly, or $8.33/user/month billed annually (Pro plan)
Individuals and small teams wanting a straightforward transcription-and-notes tool with light CRM/Zapier integration on Pro
Fireflies.ai
$10/seat/month billed annually (Pro plan)
Yes — Free plan, unlimited transcription with 400 minutes of team storage
Teams wanting unlimited transcription at a low per-seat cost plus a vendor commitment not to train AI models on meeting content
Fathom
$20/user/month billed monthly, or $16/user/month billed annually (Premium plan)
Yes — Free plan, unlimited recordings and transcription for individuals
Sales and customer-facing teams wanting CRM field sync, deal tracking, and AI coaching scorecards on top of notetaking
Short Verdict
All three will competently record, transcribe, and summarize Zoom, Google Meet, and Microsoft Teams calls (per each vendor’s own site) — the real differentiators are pricing shape, feature depth per tier, and especially how each company says it handles your meeting data. Fireflies is the most explicit about not training AI models on customer meeting content and offers the lowest headline seat price. Fathom leans hardest into sales-team features (CRM sync, deal views, coaching scorecards) and lets users opt out of AI-training use of their data in account settings. Otter is the most mature and widely integrated option but is the only one of the three whose privacy policy explicitly describes training its AI on de-identified user recordings and transcripts without describing an opt-out.
What It Is
Otter.ai is one of the longest-running AI meeting transcription tools, built around live transcription, searchable notes, and automated summaries, with integrations for Zoom, Microsoft Teams, Google Meet, Salesforce, HubSpot, and Zapier at various tiers, per its own pricing page.
Fireflies.ai centers on an AI assistant it calls “Fred” that records, transcribes, and summarizes meetings, with an AI chat layer (AskFred) for querying meeting history, plus a task manager and, on higher tiers, “Voice Agents” and conversation-intelligence analytics for sales teams.
Fathom (now operating its pricing and marketing at fathom.ai, with fathom.video redirecting there) focuses on instant AI call summaries and action items, with a notable “bot-free” capture option on some plans, plus — starting at the Business tier — CRM field sync, a Deal View, and AI coaching scorecards aimed squarely at sales teams.
Pricing Breakdown
Tool
Plan
Price
Key Limits / Inclusions
Otter.ai
Basic
Free forever
300 minutes/month, 30-min max per conversation, 1 concurrent meeting, 5 workspace members
Otter.ai
Pro
$16.99/user/month billed monthly, or $8.33/user/month billed annually
1,200 minutes/month, 90-min max per conversation, Salesforce/HubSpot/Zapier integrations
Otter.ai
Business
$30/user/month billed monthly (“Best Value”), or $19.99/user/month billed annually
Unlimited meeting minutes, 4-hour max per conversation, live notes/captioning for Zoom, 25 workspace members
Otter.ai
Enterprise
Custom — contact sales
Custom CRM/dialer integrations, Otter API and webhooks, AI Chat with Gmail/Drive/Notion/Jira
Fireflies.ai
Free
$0
Unlimited transcription, 400 minutes of team storage, limited AI summaries, AskFred assistant, API access
Fireflies.ai
Pro
$10/seat/month billed annually
Unlimited transcription, 8,000 minutes storage/seat, unlimited AI summaries, video recording, unlimited integrations
Fireflies.ai
Business
$19/seat/month billed annually
Unlimited transcription and storage, Multi-language Mode, conversation intelligence, team analytics
Fireflies.ai
Enterprise
$39/seat/month billed annually only
SSO/SCIM, audit logs, HIPAA-ready with BAA, private storage, custom data retention
Fathom
Free
$0 “free forever”
Unlimited recordings/transcription, bot-free (beta) or bot capture, instant AI summaries, clips and playlists
Fathom
Premium
$20/user/month billed monthly, or $16/user/month billed annually
$19/user/month billed monthly, or $15/user/month billed annually (2-user minimum)
Shared workspace, trackers, “Ask Fathom” across team calls, HIPAA compliance with standard BAA
Fathom
Business
$34/user/month billed monthly, or $25/user/month billed annually (2-user minimum)
CRM field sync, Deal View, AI coaching scorecards, custom org-wide summaries
Fathom
Enterprise
Billed annually only; the exact per-user figure was ambiguous on Fathom’s own pricing page — confirm with sales
“Launch Assist” implementation, SSO/SCIM, custom data retention, dedicated Success Manager
Pros
Otter.ai: The most mature integration set of the three at the Pro/Business tiers, including Salesforce, HubSpot, Zapier, and at Enterprise, a public API and webhooks.
Otter.ai: Transcription is supported in six languages (English, Spanish, French, German, Japanese, Chinese) per its pricing page.
Fireflies.ai: States explicitly that it does not use meeting content to train AI models, and that its AI vendors are contractually barred from doing so — a stronger, more specific commitment than the other two make.
Fireflies.ai: Lowest entry-level paid seat price of the three ($10/seat/month annually) with unlimited transcription even on its free plan.
Fathom: A genuinely free plan with unlimited recordings and transcription for individuals, plus a bot-free (beta) capture option.
Fathom: Deepest sales-workflow features of the three — CRM field sync, Deal View, and AI coaching scorecards — starting at its Business tier.
Cons
Otter.ai: Its own privacy policy states it trains its proprietary AI on de-identified audio recordings and transcriptions, relying on consent or “legitimate interests” as the legal basis, and the policy doesn’t describe a specific opt-out mechanism for this training use.
Otter.ai: Some of the lowest-advertised pricing (the $8.49/$4.17 “promo” rates) is explicitly restricted to India-issued credit cards per the page’s own footnote, so most buyers will pay the higher listed rate.
Fireflies.ai: Per-meeting recording length is capped even on paid plans (2 hours on Free/Pro, 3 hours on Business, 4 hours on Enterprise) — a hard ceiling for very long sessions.
Fireflies.ai: Enterprise is billed annually only, with no monthly-billing option disclosed.
Fathom: Team and Business plans both carry a 2-user minimum, so a true single-user paid upgrade only exists via the solo Premium plan.
Fathom: Its own pricing page presented Enterprise pricing ambiguously (two similar but unlabeled dollar figures), making it harder to confirm the exact rate without contacting sales.
Who It’s a Good Fit For
Teams already using Salesforce, HubSpot, or Zapier heavily, and who want those integrations available without jumping straight to an Enterprise plan, are well served by Otter’s Pro/Business tiers. Teams and privacy-conscious buyers who want the clearest vendor statement against using meeting content for AI training, at a low per-seat price, should look closely at Fireflies. Sales organizations that want notetaking paired with CRM sync, deal tracking, and rep coaching should look at Fathom’s Business tier.
Who Should Look Elsewhere
Organizations with strict internal policies against any AI training on recorded conversations should read Otter’s privacy policy carefully before adopting it, since it is the most explicit of the three about training on user data without describing an opt-out. Teams needing routine meetings well over 2-4 hours should check Fireflies’ and Otter’s per-conversation caps before relying on either for very long sessions. And solo users or very small teams who don’t need CRM/deal-tracking features will find Fathom’s Team/Business 2-seat minimums an unnecessary cost floor compared to its own solo Premium plan or Fireflies’ lower-cost Pro seat.
Bottom Line
Functionally, Otter, Fireflies, and Fathom all record, transcribe, and summarize the same core set of meeting platforms. The decision increasingly comes down to two things vendor marketing doesn’t always lead with: integration depth for your existing CRM/stack, and exactly what each company says, in its own privacy policy, about using your meetings to train AI. On that second point, Fireflies’ and Fathom’s current policies are more specific and more opt-out-friendly than Otter’s, which is worth weighing alongside price and features.
FAQ
How accurate is each tool’s transcription? None of the three vendors publish a specific accuracy percentage or word-error-rate figure on their own pricing or marketing pages at the time of writing. Otter markets itself with the tagline “the world’s smartest AI Notetaker,” and Fireflies and Fathom describe their output as “AI generated” summaries and transcripts — these are vendor marketing claims, not independently verified benchmarks, and should be treated as such.
Which of these three trains AI models on my meeting data? Per each company’s own privacy policy: Otter.ai states it trains its proprietary AI on de-identified audio recordings and transcriptions. Fireflies.ai states it does not use meetings, transcripts, or conversations to train AI models, and operates a “Zero Data Retention” policy for meeting content with its AI vendors. Fathom says it may use de-identified meeting data to train its own in-house models, depending on account settings, but states users can opt out, and that it does not authorize third parties (it names OpenAI, Anthropic, and Google) to train on that data.
Do all three support Zoom, Google Meet, and Microsoft Teams? Yes — each vendor’s own site confirms support for all three platforms, though the specific features available per platform (for example, live captioning vs. post-meeting transcription) vary by plan.
Is there a genuinely free plan among the three? Yes, all three offer a free tier: Otter’s Basic plan (300 minutes/month), Fireflies’ Free plan (unlimited transcription, 400 minutes of team storage), and Fathom’s Free plan (unlimited recordings and transcription for individuals).
Which is cheapest for a small team that just needs basic transcription? On list price, Fireflies’ Pro plan at $10/seat/month (billed annually) undercuts both Otter’s Pro ($8.33-$16.99/user/month depending on billing and promo eligibility) and Fathom’s Team plan ($15-$19/user/month, 2-user minimum) — though Otter’s annual rate can come close if you qualify for its listed pricing.
Secrets management used to be a niche DevOps concern. In 2026 it is a baseline requirement: every API key, database password, and cloud credential that touches your infrastructure needs a home that is more secure than a `.env` file in a repo. HashiCorp Vault, AWS Secrets Manager, and Doppler approach that problem from three different directions — self-hosted (or hybrid-managed) platform, AWS-native managed service, and developer-first SaaS. Here is how they actually compare on deployment model, pricing, and core capability, based on each vendor’s own documentation.
At a Glance
Tool
Starting Price
Free Plan
Best For
HashiCorp Vault
Free to self-host (BSL-licensed Community edition); HCP Vault Dedicated and Vault Enterprise are usage-based or custom-quoted
Yes — self-managed Vault is free to run under HashiCorp’s Business Source License
Teams that need dynamic, short-lived credentials across many backends and are willing to run or pay HashiCorp/IBM to run the infrastructure
AWS Secrets Manager
$0.40 per secret/month + $0.05 per 10,000 API calls
No dedicated free tier for the service itself, though new AWS accounts can apply up to $200 in general AWS Free Tier credit to it for 6 months
Teams already standardized on AWS who want a zero-infrastructure, pay-as-you-go secrets store wired into IAM
Doppler
Free for up to 3 users, then $8/user/month on the Developer plan
Yes — Developer plan is free for up to 3 users
Small-to-mid dev teams who want a fast SaaS secrets/config manager without standing up any infrastructure
Short Verdict
If you need Vault’s dynamic-secrets engine and can absorb either the operational overhead of self-hosting or the cost of HashiCorp’s managed HCP Vault Dedicated, it remains the most capable option on paper. If your workloads already live in AWS and you just need a durable, audited place to store and rotate credentials, Secrets Manager’s flat per-secret pricing is the path of least resistance. If you want something a small team can set up in an afternoon with no servers to run, Doppler’s free-to-start, per-seat SaaS model is the easiest on-ramp — though its most Vault-like features, like dynamic secrets, are reserved for its Enterprise tier.
What It Is
HashiCorp Vault is a secrets-management platform originally built by HashiCorp, which IBM completed its acquisition of on February 27, 2025, according to IBM’s own newsroom announcement. IBM has kept Vault and Terraform available under the “HashiCorp, an IBM company” banner, with no rename announced as of this writing. Vault itself has shipped under the Business Source License (BSL v1.1) since August 2023 rather than a fully open-source license — HashiCorp’s own licensing FAQ says internal use is unrestricted and that “all non-production and production usage” is permitted, with the main carve-out being offering a competing hosted version of the software to third parties. You can run Vault yourself (Community edition, free under the BSL, or licensed Vault Enterprise for extra features and support), or consume it as a managed service called HCP Vault Dedicated, which comes in Development, Essentials, and Standard tiers per HashiCorp’s own documentation.
AWS Secrets Manager is a fully managed, AWS-native secrets store. There is nothing to install or patch — you create a secret through the console, CLI, or SDK, and AWS handles storage, encryption, and (optionally) rotation. It is deeply wired into IAM for access control and into CloudTrail for audit logging of every API call made against a secret, per AWS’s own documentation.
Doppler is a SaaS secrets and configuration manager aimed at development teams who want a single source of truth for environment variables and secrets across local dev, CI, and production, without running any servers. It syncs secrets out to the platforms you already use (cloud providers, CI systems, container platforms) and layers team features — SSO, RBAC, audit logs — on top as you move up its plans.
Pricing Breakdown
Tool
Plan
Price
Notes
HashiCorp Vault
Vault Community (self-hosted)
Free
BSL-licensed; you run and operate it yourself, no HashiCorp SLA or support
HashiCorp Vault
HCP Vault Dedicated – Development
Pay-as-you-go, hourly base cost only (no published dollar rate)
Single-node, 25-client limit, no HA, no HCP SLA; for sandboxing and prototyping
HashiCorp Vault
HCP Vault Dedicated – Essentials
Hourly base cost plus a per-client rate that varies by cluster size/region (no published flat rate)
HA clusters, 99.9% SLA, Silver support; small/medium/large cluster sizes
HashiCorp Vault
HCP Vault Dedicated – Standard
Hourly base plus per-client rate (no published flat rate); annual contracts available via sales
Adds Gold support, performance replication, secrets sync, and Advanced Data Protection
HashiCorp Vault
Vault Enterprise (self-managed)
Custom — contact sales
For teams that want Enterprise features/support on their own infrastructure
AWS Secrets Manager
Pay-as-you-go (only billing model)
$0.40 per secret/month + $0.05 per 10,000 API calls
No tiers; rotation and temporary IAM credentials are included at no extra charge
Doppler
Developer
Free for up to 3 users; $8/user/month thereafter (up to 25 users)
CLI, integrations, service tokens, 3 days of activity log retention, 5 config syncs
Doppler
Team
$21/user/month (up to 500 users); 14-day free trial
Vault: Purpose-built dynamic secrets — database and cloud IAM secrets engines that issue short-lived, auto-expiring credentials rather than static ones, per HashiCorp’s own product documentation.
Vault: Detailed audit logging that records every request whether authentication succeeds or fails, useful for compliance-heavy environments.
AWS Secrets Manager: Simple, predictable flat-rate billing with no separate plan tiers to evaluate, and automatic rotation (managed or Lambda-based) included at no extra cost.
AWS Secrets Manager: Zero infrastructure to run and native IAM/CloudTrail integration for access control and audit trails.
Doppler: Fastest time-to-value of the three — a usable free plan and a straightforward per-seat Team tier with SSO and RBAC well below Vault Enterprise or HCP price points.
Doppler: Built-in automatic rotation integrations for common services (AWS, Azure, GCP, Cloudflare, MongoDB Atlas, OpenAI, SendGrid, Twilio, and others) without custom engineering.
Cons
Vault: The two most price-relevant tiers — Vault Enterprise self-hosted and HCP Vault Dedicated Essentials/Standard usage rates — have no public pricing; budgeting requires a sales conversation.
Vault: Self-hosting the Community edition means you own patching, HA, backup, and upgrade operations yourself.
AWS Secrets Manager: Costs scale linearly with secret count and API call volume, which can add up for high-churn, high-traffic architectures with many services polling secrets.
AWS Secrets Manager: It is a store-and-rotate service for credentials you already provision, not a dynamic-secrets engine that mints brand-new short-lived credentials per request the way Vault’s secrets engines do.
Doppler: Dynamic secrets — Doppler’s closest analog to Vault’s signature feature — are gated to the custom-priced Enterprise plan, and even there only cover AWS IAM and Azure Service Principal today, per Doppler’s own documentation.
Doppler: Team-plan add-ons (custom roles, user groups, higher integration-sync limits) are billed separately at $9/seat/month each, which can push real-world per-seat cost above the headline $21.
Who It’s a Good Fit For
Platform and security teams running multi-cloud or on-prem infrastructure who need genuinely dynamic, short-lived credentials and have the engineering capacity (or budget for HCP/Enterprise) to run Vault properly. AWS-centric engineering teams who want secrets management to disappear into the rest of their AWS bill rather than become a separate procurement line item. Startups and mid-size dev teams who want a working secrets manager today, without a platform engineer dedicated to it, and who value SSO/RBAC arriving at a predictable per-seat price.
Who Should Look Elsewhere
Teams with no spare DevOps bandwidth should be cautious about self-hosting Vault Community — it is free in license cost only. Multi-cloud teams who specifically need dynamic secrets outside AWS IAM/Azure Service Principal will find Doppler’s dynamic-secrets coverage narrow unless they’re already committed to the Enterprise tier. And organizations that need vendor-published, line-item pricing for every tier should budget extra time for HashiCorp’s sales-assisted quoting process on HCP Vault Dedicated and Vault Enterprise.
Bottom Line
There isn’t a single winner here because the three tools are solving overlapping but distinct problems. Vault is still the deepest toolkit for dynamic, policy-gated secrets issuance, now operating under IBM ownership and a Business Source License rather than a fully open license. AWS Secrets Manager is the low-friction default if you’re already an AWS shop. Doppler is the fastest path to a clean, team-friendly secrets workflow for organizations that don’t need Vault’s full secrets-engine depth — as long as you price in the Enterprise tier if dynamic secrets end up mattering to you.
FAQ
Is HashiCorp Vault still open source after the IBM acquisition? No — Vault’s core has shipped under the Business Source License (BSL v1.1) since August 2023, a change HashiCorp made before IBM’s acquisition closed in February 2025. APIs, SDKs, and most provider code remain under the Mozilla Public License 2.0. The BSL still permits free internal and most production use; the restriction targets competitors offering Vault as a hosted service.
Does AWS Secrets Manager support dynamic, auto-generated credentials like Vault? Not in the same sense. Secrets Manager stores and rotates secrets you provision (via managed rotation, managed partner rotation, or Lambda-based rotation), but it isn’t a secrets engine that issues brand-new, short-lived credentials on each request the way Vault’s database or cloud secrets engines do.
Can I use Doppler for free indefinitely? Yes, for small teams — the Developer plan is free for up to 3 users, with per-user pricing of $8/month kicking in beyond that, up to 25 users total, according to Doppler’s pricing page.
Which of these three has the most predictable cost as I scale? AWS Secrets Manager’s flat per-secret-per-month plus per-10,000-API-calls model is the easiest to forecast mathematically, since there are no plan tiers to outgrow. Doppler’s and Vault’s costs instead scale with seats, cluster size, or client count, which require more active monitoring.
Do any of these tools log who accessed a secret and when? Yes, all three offer audit logging: Vault has a dedicated audit-device subsystem that records every request regardless of outcome; AWS Secrets Manager events are captured in AWS CloudTrail; Doppler includes activity logs starting at 3 days of retention on Developer and extending to 90 days on Team and custom retention on Enterprise.
Stripe, PayPal, and Square all publish their standard processing rates directly on their sites, and the headline numbers alone don’t tell the full story — PayPal’s “pay with PayPal” checkout rate is meaningfully higher than its card-only rate, Square’s rate depends heavily on whether the card is tapped in person or typed in online, and Stripe’s base rate hides a stack of optional surcharges for international cards, manual entry, and currency conversion. Here’s what each one actually charges, sourced from their own current pricing pages.
At a Glance
Processor
Standard online rate (US)
In-person rate
Best for
Stripe
2.9% + 30¢ (domestic card, online)
Not Stripe’s primary use case; Stripe Terminal exists separately
Developers building custom checkout flows or software platforms
Businesses that take both in-person and online payments under one account
Short Verdict
For a pure online card transaction, Stripe and Square land at the same headline rate (2.9% + 30¢), while PayPal’s cheaper “standard credit/debit” rate (2.99%) is actually close to both — the real gap opens up when customers check out through PayPal or Venmo’s own wallet rather than a card, which jumps to 3.49% plus a fixed fee. Square’s structure is built around having one account that covers both a physical register and a website, and its in-person rate (2.6% + 10¢) is meaningfully cheaper than any of the three providers’ online rates. Stripe’s base rate is the simplest to reason about, but it carries the most line-item surcharges once you go outside a plain domestic card transaction.
What Each One Actually Charges
Stripe’s base online rate is 2.9% + 30¢ per successful domestic US card transaction. On top of that, Stripe adds: +0.5% for manually entered (card-not-present, typed-in) cards, +1.5% for international cards, and +1% if currency conversion is required — so a manually-entered international transaction needing conversion could stack to roughly 4.9% plus the fixed fee before any other add-ons. Separately, Stripe charges $15 per dispute received (refunded if you win, when using Smart Disputes which instead takes 30% of the disputed amount on a win), $10/month for a custom domain on Checkout, and 1.5% (50¢ minimum) for instant payouts instead of free standard payouts.
PayPal’s rate depends on how the customer pays, not just where the sale happens. Standard credit and debit card payments (where the buyer doesn’t use a PayPal or Venmo balance/login) run 2.99% + a fixed fee. PayPal Checkout, Guest Checkout, and “Pay with Venmo” — i.e., anything routed through PayPal’s or Venmo’s own wallet — run 3.49% + a fixed fee. PayPal’s Pay Later options run 4.99% + a fixed fee. International transactions add a flat 1.50% on top of whichever domestic rate applies, with the fixed fee amount varying by currency (for example 0.39 EUR or 0.39 GBP instead of the US 0.49 USD figure). Micropayments (small-dollar transactions) use a different structure entirely: 4.99% + a much smaller fixed fee (9 cents USD), which can be cheaper than the standard rate for low-value sales.
Square’s rate depends on how the card is presented. Tapped, dipped, or swiped in person: 2.6% + 10¢ — the cheapest per-transaction rate of any option covered here. Keyed-in or card-on-file (card-not-present) transactions: 3.5% + 15¢. Transactions through Square’s own online store or eCommerce API: 2.9% + 30¢, matching Stripe’s online rate exactly. Payment Links (Square’s hosted checkout-link product): 3.3% + 30¢, notably higher than its own online-store rate for what is functionally a similar use case. Square also charges a separate 1.75% fee for Instant Transfers to an external bank account, with standard transfers free.
Pricing Breakdown
Scenario
Stripe
PayPal
Square
Domestic online card
2.9% + 30¢
2.99% + fixed fee (card-only) or 3.49% (PayPal/Venmo checkout)
2.9% + 30¢ (online store)
In-person card
N/A (not primary product)
N/A (not primary product)
2.6% + 10¢
Manually entered / card-not-present
+0.5% surcharge on base rate
Standard rate applies (no separate CNP tier stated)
3.5% + 15¢
International card
+1.5% surcharge
+1.50% on top of domestic rate
Not separately broken out on the page reviewed
Instant payout/transfer
1.5% (50¢ minimum)
Varies by withdrawal method (not detailed here)
1.75%
Pros
Stripe: The most developer-friendly integration path and a predictable base rate, with surcharges that are at least itemized and documented rather than bundled into a vague “it depends.”
PayPal: Near-universal buyer recognition and trust, plus a genuinely cheaper micropayment tier for low-value sales.
Square: The cheapest in-person rate of the three, and a single account that covers physical and online sales without juggling two providers.
Cons
Stripe: Surcharges stack — international, manually-entered, currency-converted transactions can meaningfully exceed the advertised 2.9% + 30¢ headline.
PayPal: The checkout flow buyers actually prefer (PayPal/Venmo wallet) costs sellers half a point more than a plain card transaction — the convenient option isn’t the cheap one.
Square: Its own online-checkout-link product (Payment Links) costs more than its online store rate for a similar use case, and keyed-in transactions carry the highest per-transaction rate of any scenario compared here.
Who It’s a Good Fit For
Choose Stripe if you’re building a custom checkout, marketplace, or software platform and want programmatic control over the payment flow. Choose PayPal if buyer trust and recognition at checkout matters more than shaving fractions of a percent off the rate, or if you process a lot of small-dollar transactions that qualify for the micropayment tier. Choose Square if your business takes payments both in person and online and you want one account, one rate card, and one payout schedule for both.
Bottom Line
At the headline level, Stripe and Square’s online rates are identical and PayPal’s card-only rate is close behind — the differences that actually matter show up in the surcharges and alternate scenarios: international cards, manual entry, PayPal’s own wallet checkout, and instant payouts. Map your actual transaction mix against each provider’s full rate card, not just the number on the pricing page, before choosing.
Teachable, Thinkific, and Kajabi all sell “build and sell your course” software, but they price themselves very differently once you look past the entry-level number: Teachable charges a 7.5% transaction fee on its cheapest tier and 0% above it, Thinkific charges no plan-level transaction fee but has a noticeably higher base price, and Kajabi bundles email marketing and a full website into every tier. This comparison covers each platform’s current plans, pricing, and processing fees as published on their own sites.
At a Glance
Platform
Entry plan (annual)
Transaction fee
Free trial
Best for
Teachable
Starter, $29/mo
7.5% on Starter; 0% on Builder and above (via Teachable Payments)
Trial length unclear — page shows both 7-day and 30-day messaging
Creators who want the cheapest entry point and will upgrade once revenue justifies 0% fees
Thinkific
Start, $82/mo
None at the plan level; Thinkific Payments charges 2.9% processing, third-party gateways add a separate fee
30 days
Creators who want no plan-level transaction fee from day one and don’t mind a higher base price
Kajabi
Basic, $143/mo
No revenue share; card processing 2.9% + 30¢ (Basic), improving to 2.7% + 30¢ on Pro
14 days
Creators who want an all-in-one website, email marketing, and course platform in one subscription
Short Verdict
Teachable is the cheapest way to start selling a course today, but that 7.5% transaction fee on the Starter plan means it’s really a “pay more once you’re making money” model — at meaningful volume, the Builder plan’s 0% fee (at $69/mo annual) usually pays for itself quickly. Thinkific has no plan-level transaction fee on any tier, including its base Start plan, which makes its $82/mo entry price easier to justify once you do the math against Teachable’s 7.5% cut. Kajabi is priced as a bundle: you’re not just buying a course platform, you’re buying email marketing, funnels, and a website builder in the same subscription, which is why its entry price is the highest of the three but may replace two or three other tools you’d otherwise be paying for separately.
What Each One Actually Includes
Teachable‘s Starter plan ($29/mo annual, $39/mo monthly) allows up to 5 products, 1 admin user, 1TB of video storage, AI course-creation tools, and global payments and tax handling — but charges a 7.5% transaction fee on every sale. Builder ($69/mo annual) removes that fee entirely (when using Teachable’s own payment processor), adds an affiliate program and more integrations. Growth ($139/mo annual) adds more admin seats, custom certificates, and removes Teachable’s branding. On top of any plan fee, Teachable’s payment processing runs 2.9% + 30¢ for US cards (3.9% + 30¢ international), separate from the plan-level transaction fee.
Thinkific‘s Start plan ($82/mo annual, $109/mo monthly) includes unlimited courses, live cohorts, quizzes, assignments, certificates, and membership/subscription selling, with no plan-level transaction fee at any tier. Its own processor, Thinkific Payments, charges a flat 2.9% processing fee; using Stripe or PayPal instead adds an extra third-party gateway fee that varies by plan (Thinkific doesn’t list the exact amount on its pricing page). Grow ($164/mo annual) removes Thinkific branding and adds communities, bulk enrollment, and API access; Expand ($374/mo annual) adds much higher video bandwidth, more communities, and revenue sharing across up to 10 partners.
Kajabi‘s Basic plan ($143/mo annual, $179/mo monthly) includes 2,500 contacts, 5 products, one website and one community, unlimited email sends, landing pages, and funnels, plus checkout — Kajabi takes no revenue share on any plan, but its own card processing runs 2.9% + 30¢ on Basic, dropping to 2.8% + 30¢ on Growth and 2.7% + 30¢ on Pro. Growth ($199/mo annual) raises the contact limit to 25,000, adds live cohort courses, advanced automations, and an affiliate program. Pro ($399/mo annual) raises contacts to 100,000, adds a branded mobile app and full API access, and drops the outside-processor fee to 0.5%.
Pricing Breakdown
Plan
Monthly
Annual (per mo)
Transaction/processing fee
Teachable Starter
$39
$29
7.5% + standard card processing
Teachable Builder
$89
$69
0% + standard card processing
Teachable Growth
$189
$139
0% + standard card processing
Thinkific Start
$109
$82
None at plan level; 2.9% via Thinkific Payments
Thinkific Grow
$219
$164
None at plan level; 2.9% via Thinkific Payments
Thinkific Expand
$499
$374
None at plan level; 2.9% via Thinkific Payments
Kajabi Basic
$179
$143
No revenue share; 2.9% + 30¢ card processing
Kajabi Growth
$249
$199
No revenue share; 2.8% + 30¢ card processing
Kajabi Pro
$499
$399
No revenue share; 2.7% + 30¢ card processing
Pros
Teachable: The lowest entry price of the three, with a clear upgrade path once 0% transaction fees make financial sense.
Thinkific: No plan-level transaction fee on any tier, including the entry plan — what you see on the pricing page is the whole plan cost.
Kajabi: Replaces email marketing, funnels, and website-building tools you’d otherwise pay for separately, with processing fees that improve as you move up tiers.
Cons
Teachable: The 7.5% Starter fee stacks on top of standard card processing fees, which can erode margin quickly at low price points before you’re ready to justify the Builder plan’s cost.
Thinkific: The highest entry price of the three for a first-time creator, and third-party gateway fees (Stripe/PayPal) aren’t clearly quantified on its own pricing page.
Kajabi: The highest entry price overall, and the lowest contact/product limits on Basic may force an early upgrade for anyone building an email list alongside their course.
Who It’s a Good Fit For
Choose Teachable if you’re just starting out and want the lowest possible monthly cost while you validate demand, accepting the transaction fee as a cost of testing the waters. Choose Thinkific if you’d rather pay a flat, predictable monthly fee with no percentage cut on sales from day one. Choose Kajabi if you’re planning to run email marketing, landing pages, and a course from one platform rather than stitching together separate tools, and the higher price offsets what you’d otherwise pay for an email service provider and page builder separately.
Bottom Line
There’s no universal winner here — the right platform depends on whether you’re optimizing for the lowest starting cost (Teachable), the most predictable fee structure (Thinkific), or the broadest all-in-one marketing stack (Kajabi). Run your expected sales volume through each platform’s actual fee structure before committing, since the “cheapest” plan on the pricing page isn’t always the cheapest once transaction and processing fees are factored in.
All three major cloud providers now give customers a free dashboard that estimates the carbon emissions behind their cloud bill, and all three tools changed meaningfully in the past year — AWS launched a new standalone console, Microsoft is retiring its original dashboard in favor of a different tool, and Google added a reporting method it didn’t offer before. Here’s what each one actually measures, how to find it, and what’s changing.
Emissions Impact Dashboard retiring March 31, 2027
Resource- and subscription-level emissions; AI-driven reduction recommendations
Free, in the Azure portal; legacy dashboard requires a Power BI Pro license
AWS: Sustainability Console and the Customer Carbon Footprint Tool
AWS’s original tool, the Customer Carbon Footprint Tool (CCFT), lives inside the AWS Billing console and has reported Scope 1, 2, and 3 emissions estimates (using both market-based and location-based calculation methods) broken down by region and service. On March 31, 2026, AWS launched a separate, standalone Sustainability Console that expands on CCFT rather than replacing it: its main addition is that sustainability teams can view emissions data without needing billing permissions, plus customizable visualizations, a configurable fiscal-year start month, CSV report exports, and programmatic access via API and SDK. For a small team, CCFT inside Billing may still be enough; for a dedicated sustainability or ESG function that shouldn’t need finance-team access just to pull emissions numbers, the new console is the more practical entry point.
Google Cloud: Carbon Footprint
Google Cloud’s Carbon Footprint tool is free for all customers and reports Scope 1, 2, and 3 emissions tied to covered Google Cloud services, broken down by service, project, region, and month. Its most recent documented change is dual Scope 2 reporting — showing both market-based and location-based emissions side by side, rather than market-based figures alone — which Google’s own documentation flags as new and describes as giving customers more transparency into how the number is calculated. Data can be exported to BigQuery (incurring Google’s standard storage and query charges) or Sheets for custom analysis, and the tool is integrated with Google’s unattended-project recommender, which estimates the emissions reduction from shutting down idle projects. A third-party sustainability consultancy has reviewed Google’s calculation methodology and found it a reasonable application of the GHG Protocol, according to Google’s own documentation.
Microsoft Azure: Carbon Optimization Replaces the Emissions Impact Dashboard
This is the most consequential change of the three for existing users. Microsoft’s original tool, the Emissions Impact Dashboard (a Power BI app requiring a Power BI Pro license), is being retired effective March 31, 2027 — after that date it will no longer be accessible and technical support ends. Its replacement, Carbon Optimization, is built directly into the Azure portal, is free for all customers, and works at a more granular level: emissions by subscription, resource group, resource, resource type, and location over the past 12 months, exportable via CSV or REST API. It also adds something the old dashboard didn’t: AI-driven recommendations (such as switching to more efficient VM SKUs or shutting down idle resources) with estimated carbon and cost impact shown before you act, plus emissions-equivalent framing (like “smartphones charged”) based on the EPA’s Greenhouse Gas Equivalencies Calculator. Until the 2027 retirement, Microsoft positions the two tools as complementary — the old dashboard for organization-wide reporting, Carbon Optimization for team-level, actionable tracking — but says to export your historical Emissions Impact Dashboard data before it disappears, since Carbon Optimization itself only retains 12 months of data at a time.
Why This Matters Even If You Don’t Have an ESG Mandate
All three tools are free, already enabled, and sitting in a console most teams already have access to — there’s no procurement step to see the numbers for the first time.
Azure’s and Google’s tools both now tie emissions estimates directly to cost-saving actions (idle resource shutdown, right-sizing), which means a sustainability review can double as a cost review.
If your organization reports Scope 3 emissions for any regulatory or customer-disclosure reason, cloud compute is increasingly a named line item, and these tools are the primary way that number gets populated without manual estimation.
Anyone currently relying on Azure’s Emissions Impact Dashboard for recurring reporting has a hard deadline (March 31, 2027) to migrate that workflow to Carbon Optimization or another export path.
Limitations to Know About
Market-based versus location-based emissions figures can differ substantially for the same usage, depending on whether a provider’s renewable energy purchases are counted against your specific usage (market-based) or your region’s actual grid mix is used instead (location-based) — all three providers now surface both methods in some form, but they aren’t interchangeable numbers.
None of these tools audits a third party’s claims independently in real time; they’re self-reported by the cloud provider using its own methodology, published separately from the dashboard itself.
Azure’s Carbon Optimization retains only 12 months of data at a time — long-term historical tracking requires your own regular export process, not reliance on the tool’s built-in history.
Bottom Line
If you run workloads on any of the big three clouds, the carbon-reporting tool is already available to you at no extra cost — the main action item is knowing which one is current. AWS customers get a genuinely new, more accessible console on top of their existing tool. Google Cloud customers get a more transparent Scope 2 breakdown than before. Azure customers have a firm migration deadline: March 31, 2027 is when the old dashboard disappears, and Carbon Optimization is where that reporting needs to move.
Nearly every hosting company claims to be “green” somewhere on its homepage, but the claims range from independently certified renewable-energy purchases to a vague sentence about caring about the planet. GreenGeeks, Kualo, and DreamHost are three of the hosts most commonly recommended as eco-friendly, and they back that label with genuinely different levels of evidence. This comparison looks at what each one actually documents — not just what it advertises — alongside their current shared-hosting pricing.
At a Glance
Host
Entry shared plan price
Green claim
Independently verifiable?
Best for
GreenGeeks
$1.95/mo intro (Lite), $14.95/mo renewal
300% renewable energy match (RECs via Bonneville Environmental Foundation)
Yes — EPA Green Power Partner since 2009, named third-party partner
Buyers who want a documented, named green-energy program
Kualo
$9.99/mo (Solo)
100% renewable energy (US datacenter), Green-e certified; UK datacenter sourced via Open Energy Market; carbon offsets via Ecologi
Yes — Green-e certification and EPA Green Power Partner status named directly
Buyers who want certified renewable power plus active carbon offsetting
General “committed to being a green company” statement; clean-wind program partnerships; efficient cooling and chips
No — no percentage, certification, or named offset program given
Buyers who want low-cost hosting and treat “green” as a nice-to-have, not a verified feature
Short Verdict
GreenGeeks and Kualo both put real, checkable evidence behind their green claims — named certifications, a named third-party partner, and in GreenGeeks’ case a specific multiple (300%) of renewable energy certificates purchased against its actual usage. DreamHost’s green page, by contrast, reads more like a general sustainability mission statement than a documented program: no percentage, no certification body, no named offset partner. If the environmental claim is the reason you’re choosing a host, GreenGeeks and Kualo are the two actually built to survive a fact-check.
What Each One Actually Documents
GreenGeeks states on its own site that it purchases renewable energy certificates (RECs) through the Bonneville Environmental Foundation equal to three times (300%) the electricity it actually draws from the grid for its data centers — the power delivered to each facility still comes from the local grid mix, but the RECs offset it at a 3-to-1 ratio annually. GreenGeeks has been recognized as an EPA Green Power Partner since 2009, and says it has helped plant more than 50,000 trees through a partnership with One Tree Planted (roughly one tree per hosting account). This is one of the more specific, named claims in the budget hosting space.
Kualo makes a split claim: its US datacenter runs on energy it describes as 100% renewable, certified by Green-e (an established US renewable-energy certification body), while its UK datacenter sources every watt from wind, solar, and tidal power procured through the Open Energy Market. Kualo is also a partner member of The Green Web Foundation, a nonprofit that tracks which hosting providers run on green power, and it offsets carbon through Ecologi, a platform that funds verified carbon-removal and -reduction projects. Kualo describes itself as “climate positive” since 2020 and targets “carbon negative” operations by the end of 2030, though it doesn’t hold a specific carbon-neutral certification under that name.
DreamHost’s green-hosting page is comparatively thin on specifics. It cites high-efficiency cooling infrastructure, energy-saving processors “where practical,” participation in unspecified state-level clean-wind programs, and general statements about its data centers drawing from grids that include renewable sources — which describes the regional grid, not a specific purchase commitment by DreamHost. It also lists internal operational choices (remote-first culture, reduced paper use) that reduce DreamHost’s own corporate footprint but say nothing about the servers running your site. The page states DreamHost is “committed to being a green company” without a measurable target, percentage, or named certification.
Pricing Breakdown
Plan
Price
Storage
Sites
Notes
GreenGeeks Lite
$1.95/mo intro, $14.95/mo renewal
25 GB
5
Unmetered traffic, free SSL, free domain year one, 30-day guarantee
GreenGeeks Pro
$3.95/mo intro, $19.95/mo renewal
50 GB
Unlimited
Most popular tier on GreenGeeks’ own page
GreenGeeks Premium
$6.95/mo intro, $31.95/mo renewal
100 GB
Unlimited
Highest resource allocation
Kualo Solo
$9.99/mo (or $99.90/yr)
10 GB
1
Free domain on annual+ terms, daily backups, cPanel included
Kualo Startup
$14.99/mo (or $149.90/yr)
30 GB
Unlimited
Unlimited email accounts
DreamHost Web Hosting Launch
$2.89/mo intro (first year), $10.99/mo renewal
25 GB NVMe
1 (single-site tier)
Free domain and SSL on annual/multi-year terms
Pros
GreenGeeks: A specific, named 300% REC purchase ratio and a long-standing EPA Green Power Partner status make this one of the easier green claims in hosting to actually verify.
Kualo: Combines a certified 100% renewable claim (US), a named certification body (Green-e), and active carbon offsetting (Ecologi) — the most layered verification of the three.
DreamHost: The cheapest entry-level plan of the three by both intro and renewal price, with solid baseline features (NVMe storage, free SSL) regardless of the sustainability angle.
Cons
GreenGeeks: The REC purchase offsets usage after the fact rather than guaranteeing the electricity delivered to the data center is itself renewable — a common structure in the industry, but worth understanding rather than assuming.
Kualo: Pricing starts noticeably higher than GreenGeeks or DreamHost for a single-site plan, and it doesn’t hold a specific named carbon-neutral certification despite the “climate positive” language.
DreamHost: Its green-hosting page gives no percentage, certification, or named renewable-energy purchase program — if the environmental claim matters to your decision, there’s little here to actually check.
Who Should Look Elsewhere
If sustainability isn’t a deciding factor at all, plenty of mainstream hosts (not covered here) may offer better raw performance or support for the price — this comparison is specifically for buyers who want the environmental claim to hold up, not a general “best budget host” ranking. And if you need a managed WordPress or high-traffic hosting tier rather than entry-level shared hosting, check each provider’s higher tiers directly, since the plans compared here are the entry-level shared offerings only.
Bottom Line
GreenGeeks and Kualo both treat their green claims as a feature worth documenting — named certifications, named partners, and in GreenGeeks’ case a specific purchase ratio. DreamHost’s green page, read closely, is closer to a values statement than a verifiable program. If a checkable environmental claim matters to your hosting decision, that difference is the whole story here; price and raw features are a secondary consideration once you’ve filtered for it.
FAQ
Does “100% renewable” mean the electricity hitting the server is renewable? Not necessarily. Most hosts, including the ones here, use renewable energy certificates (RECs) or certified procurement programs that offset grid usage rather than guaranteeing every electron is renewable at the point of use. Green-e certification (Kualo) and REC purchases (GreenGeeks) are standard, recognized mechanisms for this, but they’re accounting constructs, not a direct wire from a solar panel to your server.
Which of these three is cheapest? DreamHost’s Web Hosting Launch plan has the lowest intro and renewal price of the three, but it’s also the one with the weakest documented sustainability claim.
Is A2 Hosting still a green hosting option? A2 Hosting rebranded to Hosting.com in 2025. Hosting.com’s current site makes no renewable-energy or green-hosting claims, so it’s no longer included in green hosting comparisons like this one.
Do any of these offer a money-back guarantee? Yes — GreenGeeks offers 30 days, Kualo offers 60 days. DreamHost’s refund terms weren’t independently confirmed from the pages reviewed here; check DreamHost’s terms directly before buying.
Open a 2-million-line log file in a plain-string-backed editor and type one character at the start. If the editor stores the whole document as one contiguous string or array, that single keystroke can mean copying every byte after your cursor — megabytes of memory movement for one keypress. The rope data structure exists to make that cost disappear. Instead of one giant buffer, a rope represents text as a balanced tree of smaller chunks, so an edit touches only a small, localized part of the tree. This piece explains how ropes actually work, works through a concatenation/split example, and is careful about which real editors use them — because ropes are often credited to editors that, by their own engineering documentation, use something else entirely.
At a Glance
Aspect
Detail
What it solves
Editing, concatenating, and slicing very large strings without rewriting the whole buffer
Core idea
A balanced binary tree whose leaves hold short text chunks; internal nodes cache subtree length
Insert / delete at an arbitrary position
O(log n), vs. O(n) for a flat string/array
Concatenation
O(log n) (often effectively O(1) for the join itself) vs. O(n) to copy two flat strings together
Index / character access
O(log n), vs. O(1) for a flat array — the one place ropes are slower
Confirmed real-world use
Xi editor’s custom xi-rope crate; Helix editor via the ropey crate
Confirmed NOT using a rope
VS Code — uses a “piece tree” (a piece-table variant over a red-black tree), per its own engineering blog
Verdict: a rope is the right structure when a program needs to make frequent, scattered edits to very large sequences of text and can’t tolerate the cost of rewriting the buffer on every keystroke. It is not automatically what every text editor uses — some reach for piece tables or gap buffers instead, which solve a similar problem with different trade-offs — so understanding the mechanism matters more than memorizing which editor uses which name.
The Problem: Editing Big Strings in the Middle
A flat string or character array is the obvious way to represent text, and it’s fine for small documents. Its weakness shows up on mid-document edits: inserting or deleting at position i means shifting every character after it by one slot, O(n) work relative to document length. For a short note that’s imperceptible; for a 50MB log file, an O(n) shift on every keystroke turns typing into visible lag, and the cost grows with the exact dimension — document size — where users most expect smooth performance.
The Rope: A Tree of Text Chunks
The rope was introduced by Hans-J. Boehm, Russ Atkinson, and Michael Plass in their 1995 paper “Ropes: An Alternative to Strings.” The core idea: represent a string as a binary tree where each leaf holds a short, immutable chunk of text, and each internal node records the combined length (and often a “weight” — its left subtree’s length) of everything beneath it. Reading the string in order is an in-order traversal of the leaves; nothing requires the data to be contiguous in memory.
Two operations fall out of this almost for free:
Concatenation of two ropes A and B can be done by creating one new internal node with A as its left child and B as its right child — no copying of the underlying text at all. The new node’s cached length is just A’s length plus B’s length.
Splitting a rope at a given index walks down to the leaf containing that index, splits that one leaf’s chunk into two pieces, and reassembles the tree structure around the split point — touching only the nodes along the path from root to that leaf, not the whole tree.
Insertion in the middle of a rope is then “split, then concatenate”: split at the insertion point into a left and right rope, concatenate the left with a new leaf holding the inserted text, then concatenate that with the right. Deletion reverses this: split out the unwanted range, discard it, concatenate what remains.
Worked Example: Insert in the Middle
Suppose a rope currently holds “Hello world” as two leaves under one root:
Insert “there ” at index 6 (right after “Hello “), so the result should read “Hello there world”. The rope doesn’t touch the “world” leaf at all. It descends to the split point — which happens to fall exactly on the existing leaf boundary here — and attaches a new leaf for “there ” as a sibling of “world” under a fresh internal node:
Only the path from the root to the insertion point was touched — “Hello ” and “world” are reused untouched. On a 500MB document, inserting one word still costs work proportional to tree depth (O(log n)), not document size. Reading it back out in order — “Hello ” + “there ” + “world” — is an in-order traversal, exactly as if it were one flat string.
Why This Beats a Flat Buffer at Scale
The rope’s balanced-tree structure bounds every structural operation by the tree’s depth, not the document’s length. With chunks kept to a bounded size and the tree kept balanced as edits accumulate, depth grows logarithmically with size, so insert, delete, split, and concatenate all land at O(log n) instead of a flat buffer’s O(n). The one place a rope loses to a flat array is random-access indexing — “give me character 4,000,000” — which costs O(log n) in a rope (walking cached subtree lengths down to the right leaf) versus O(1) for direct memory addressing. That’s the real trade: a small, usually unnoticeable cost on indexing in exchange for eliminating the large, very noticeable cost of mid-document edits on huge files.
Which Real Editors Actually Use a Rope — and Which Don’t
This is the part worth getting precisely right, because “editors use ropes” is widely repeated and not uniformly true.
Xi editor (an experimental, now-archived editor from Google/Raph Levien) built its own rope, xi-rope, and documented the rationale in a “Rope science” series. In his xi-editor retrospective, the author compared five text representations — contiguous string, gap buffer, line array, piece table, and rope — and chose the rope because, in his words, “there aren’t any cases where it performs badly,” while a gap buffer or piece table can degrade under certain access patterns. He also notes ropes fit Rust’s ownership model well and suit a narrow but demanding workload: large documents with frequent, scattered small edits.
Helix editor, a modal terminal-based editor in Rust, states directly in its own architecture docs that “the main data structure used for representing buffers is a Rope,” built on the ropey crate, which it re-exports — a confirmed, current example of a rope in production.
VS Code is the case to get right. Its own engineering blog post, “A Summary of Text Buffer Reimplementation,” is explicit that the team moved to what they call a piece tree — a piece-table variant where the document is the original loaded text plus a sequence of edit “pieces,” organized in a red-black tree (not a rope) for fast line lookups. The post never calls this a rope, and the mechanism — pieces referencing original/added buffers, indexed by a red-black tree — differs meaningfully from a rope’s tree of owned text chunks. “VS Code uses a rope” is a common but, per the project’s own documentation, incorrect simplification.
For contrast, GNU Emacs documents its own buffer plainly in its Lisp Reference Manual: a single array with a movable “gap” — a classic gap buffer, not a rope or piece table — fast for edits clustered near one cursor but, like a flat array, slower for edits that jump around. Beyond these, we could not confirm from primary sources which structure other popular editors (Vim, Sublime Text, Zed) use internally today, so we don’t assert it.
Rope vs. the Naive Flat Buffer
Operation
Flat string/array
Rope
Insert/delete at arbitrary position
O(n) — shifts everything after the edit
O(log n) — touches only the root-to-leaf path
Concatenate two documents
O(n) — copy both into one new buffer
O(log n) — link as children of a new node, no copy
Split at a position
O(n) — copy each half into a new buffer
O(log n) — split one leaf, relink ancestors
Random character access
O(1) — direct memory offset
O(log n) — walk cached subtree lengths to the leaf
Memory locality for sequential scans
Excellent — fully contiguous
Good but not contiguous — chunk-by-chunk traversal
Trade-offs
Pros: mid-document insert/delete and concatenation/split run in O(log n) regardless of size; chunks can be shared immutably between tree versions, convenient for undo history and (per xi-editor’s notes) safe cross-thread sharing; no operation ever touches the whole document.
Cons: noticeably more implementation complexity than a flat array or gap buffer; random-access indexing is slower than O(1); tree bookkeeping can make a rope slower than a flat string for short, rarely-edited text; as xi-editor’s retrospective notes, the exact workload a rope suits — huge sequences with many scattered small edits — is fairly narrow outside text editors.
When to Use This
Reach for a rope when building an editor, buffer, or collaborative-editing engine that must handle large documents with edits scattered throughout, not just appended at the end. If editing is overwhelmingly append-only or clusters tightly around one cursor, a gap buffer is simpler and just as fast. If memory efficiency right after loading matters more than mid-document edit speed, a piece table (or piece tree, as VS Code implements it) is worth evaluating first. And whichever buffer you choose, pair it with grapheme-cluster-aware boundary logic for combining marks and emoji — our Unicode for developers piece covers why naive code-point-based cursor movement breaks on real-world text.
Bottom Line
A rope turns a text document into a balanced tree of chunks so that inserting, deleting, concatenating, or splitting costs O(log n) instead of O(n), which is what makes editing a multi-million-line file feel the same as editing a one-line one. It’s a real, well-documented, and still-used technique — Xi editor built one from scratch and Helix uses one today via the ropey crate — but it isn’t universal. VS Code’s own engineering team chose a piece tree instead, and Emacs uses a gap buffer; the right lesson is to match the structure to the access pattern, not to assume every modern editor reaches for the same one.
FAQ
Does VS Code use a rope? No. According to VS Code’s own engineering blog post on its text buffer reimplementation, it uses a “piece tree” — a piece-table variant whose pieces are organized in a red-black tree for fast line lookups. This is a different data structure from a rope, and the post does not describe it as one.
What’s the difference between a rope and a piece table? A rope is a tree of the document’s actual text chunks; every edit restructures part of that tree. A piece table keeps the original file untouched plus append-only “added text,” representing the document as an ordered list (or tree, as in VS Code’s piece tree) of “pieces” pointing into those buffers. It’s memory-efficient right after loading, but needs extra bookkeeping to keep line lookups fast.
Is a gap buffer the same as a rope? No. A gap buffer, which GNU Emacs documents using, is a single array with an empty “gap” that moves to the cursor; edits near the gap are cheap, but moving the gap across the document or editing scattered locations is comparatively expensive. A rope has no single array at all — it’s inherently a tree.
Why is random character access slower in a rope? Finding character i in a flat array is one calculation. In a rope it means walking from the root down, using cached subtree lengths to pick left or right, until reaching the right leaf — a path proportional to tree depth, O(log n). It’s a deliberate trade for cheaper edits.
Are ropes only useful for text editors? They’re mostly associated with editors because “huge sequence, scattered small edits” is exactly an editor’s workload, but the same idea applies to any large, frequently-edited sequence — Rust’s ropey and jumprope crates, for instance, are general-purpose rope libraries usable outside editors.
Expense management software has quietly become corporate-card software: the three biggest names in the category today — Expensify, Ramp, and Brex — all bundle a physical/virtual corporate card with the receipt-capture and approval tooling. That changes how you should compare them, because the “free” tier isn’t really free if it’s subsidized by card interchange revenue rather than your subscription fee. We checked each vendor’s own pricing and help pages directly in November 2026 to see what’s actually self-serve versus what requires a sales call.
If you’re also evaluating core bookkeeping tools alongside expense management, our Best Accounting Software for Freelancers and Small Business comparison covers QuickBooks Online, Xero, and Wave, which is a natural next step once your expense data needs somewhere to land.
At a Glance
Tool
Starting Price
Free Plan?
Best For
Expensify
$5/member/month (Collect, pay-per-use)
Only for a single individual tracking personal expenses — no approvals, payments, cards, or accounting sync
Solo users and small teams who want simple receipt capture without a corporate card program
Ramp
$0/user/month (Free plan)
Yes — a genuinely usable free plan including the corporate card
Small and mid-size businesses that want card issuing, AP automation, and approvals without a subscription fee
Brex
$0/user/month (Essentials)
Yes — free plan includes global corporate cards and core approvals
Startups and companies with international teams that need multi-currency cards and entities
Short Verdict
Ramp and Brex both offer a free, full-featured starting tier built around their own corporate card, which makes either one the better default for a small business that wants expense management and a card program in a single sign-up with no subscription cost. Expensify is different: it’s priced per-member with no card-program requirement, which suits a business that already has a card provider (or no company card at all) and just wants receipt capture, approvals, and accounting sync layered on top. Between Ramp and Brex, Ramp’s free plan is the more AP-automation-focused of the two, while Brex leans toward global/multi-entity teams with cards accepted in 210+ countries even on its free tier.
What It Is: Three Different Business Models
It helps to understand how each company actually makes money, because it explains the pricing structure:
Expensify is a software subscription first. You pay per active or included member for the Collect or Control plan; its own corporate card (the Expensify Card) is optional, and using it unlocks a discount on your subscription rather than being required to use the product at all.
Ramp and Brex are both built around the corporate card as the primary product, with expense management, bill pay, and accounting sync layered on as software. Both can offer a genuinely free software tier because they earn revenue from card interchange fees rather than from your subscription.
Practically, this means Expensify is the better fit if you don’t want to switch your corporate card provider, and Ramp or Brex are the better fit if you’re open to (or actively want) a new corporate card as part of the deal.
Pricing Breakdown (as published, November 2026)
Vendor
Plan
Price
Key Features
Expensify
Free “Submit” workspace
$0
Individual expense tracking only — no approvals, payments, company cards, or accounting integrations
Collect
$5/unique member/month, pay-per-use
Receipt scanning, simple one-step approval workflow, connects to QuickBooks/Xero; no multi-level approvals or multiple card connections
Control
$18/included member/month billed annually (or $36/member/month pay-per-use); discounted to as low as $9–$18/member/month with Expensify Card usage
$15/user/month plus a platform fee based on team size (20% off with annual billing)
Automatic card locking for missing receipts, AI-driven approval recommendations, routing by vendor/department/GL code
Enterprise
Not published — contact sales
Annual billing only; built on top of Plus features
Brex
Essentials
$0/user/month
Unlimited global corporate cards (210+ countries), one local card program, up to 2 entities, accounting integrations, multi-level approval chains, AI custom rules
Premium
$12/user/month
Adds advanced receipt data extraction, local-currency cards in 50+ countries, dynamic spend-limit approval chains, multiple expense policies
Enterprise
Not published — contact sales
Local card issuance/collections/reimbursements/policies on top of Premium
Smart Card
Not published — contact sales
A separate procurement-focused product: merchant card controls and custom approvals
Both Ramp Plus and Expensify Control add a fee on top of the base per-member number — Ramp calls it a “platform fee based on team size” without publishing the exact figure, and Expensify charges extra for any active member above your committed annual subscription size. Neither gives a single clean per-seat number you can multiply by headcount without talking to sales or reading the fine print, so treat the prices above as starting points rather than your final bill.
Pros and Cons
Expensify
Pros: No requirement to adopt a new corporate card; works alongside whatever card program you already have; Collect plan is cheap for a small team that just needs receipt capture and basic approvals.
Cons: The only free option is for a single individual with no approvals, payments, or accounting sync — not usable as a business-wide free plan; Control’s pay-per-use rate ($36/member/month) is the most expensive list price of the three vendors unless you commit to annual billing and use the Expensify Card for a discount.
Ramp
Pros: The free plan is a real, usable business plan (not a stripped-down trial) and already includes OCR invoice extraction, receipt matching, the corporate card, and configurable approval workflows; Plus adds genuinely useful AP routing on top.
Cons: Plus plan’s “platform fee based on team size” isn’t published as a number, making it hard to estimate total cost in advance; Enterprise pricing requires a sales call with no published starting point.
Brex
Pros: Free Essentials tier includes global card acceptance in 210+ countries and up to 2 entities, which is unusually generous for a $0 tier; strong fit for startups with international spend or multiple legal entities from day one.
Cons: Advanced receipt data extraction is reserved for Premium ($12/user/month) and above, not included free; local-currency card issuance beyond one program also requires upgrading; Enterprise and the separate Smart Card product both require contacting sales with no published price.
Who It’s a Good Fit For
Choose Expensify if you want to keep your existing corporate card or bank and bolt on receipt capture, approvals, and accounting sync without switching card providers.
Choose Ramp if you want a genuinely free, full-featured starting plan with a corporate card and AP automation, and you’re comfortable with a per-user fee plus an unpublished platform fee once you outgrow the free tier.
Choose Brex if your business operates across multiple countries or legal entities and you want global card acceptance built into even the free plan.
Who Should Look Elsewhere
Teams that need a hard, all-in dollar figure for a growing headcount should be cautious with Ramp Plus and Expensify Control — both carry fees on top of the base per-member price that aren’t fully published.
Businesses that specifically don’t want to adopt a new corporate card (for banking relationship, credit, or compliance reasons) should default to Expensify rather than Ramp or Brex, since the latter two are built around their own card as the core product.
Anyone needing enterprise-tier pricing published up front, without a sales call, won’t find it at any of the three vendors — Ramp Enterprise, Brex Enterprise, and Brex Smart Card are all quote-only.
Bottom Line
For most small businesses starting from scratch in 2026, Ramp or Brex’s free tier is the lower-friction entry point because it bundles a usable corporate card with real expense-management features at $0/user. Expensify remains the right call specifically when you don’t want to change your card provider, or when your workflow is simpler than a full card program — its Collect plan at $5/member/month is cheap for that narrower use case. Whichever you pick, budget time to get an actual quote for Plus/Control/Premium tiers before committing, since none of the three vendors’ published entry-level numbers are the full story once you add platform fees, overage charges, or a path to the enterprise tier.
FAQ
Which of these three has a truly free plan for a small business?
Ramp and Brex both do — their Free and Essentials plans respectively are full business plans (not single-user trials) that include a corporate card, receipt handling, and approval workflows at $0 per user per month. Expensify’s only free option is a single-individual “Submit” workspace with no approvals, payments, company cards, or accounting integrations, so it doesn’t function as a free plan for a team.
Do I have to switch corporate card providers to use Ramp or Brex?
Their free and entry-level plans are built around issuing you their own corporate card, so yes — you’re expected to use their card for the bundled pricing to make sense. Expensify is the option that layers onto a card program you already have rather than replacing it.
Which vendor publishes exact pricing for its top tier?
None of them. Ramp Enterprise, Brex Enterprise, and Brex Smart Card are all quote-only with no published starting price. Expensify does publish numbers for its Collect and Control plans, but Control’s per-member overage fee above your committed subscription size, and Ramp Plus’s “platform fee based on team size,” are also not spelled out as fixed dollar amounts.
Do all three include receipt scanning/OCR?
Yes, in some form, on their core plans. Expensify includes receipt scanning on Collect; Ramp advertises automated invoice extraction (OCR) for accounts payable and auto-receipt matching on its Free plan; Brex includes automatically generated receipts on Essentials, with more advanced receipt data extraction reserved for its paid Premium tier and above.
Can I use any of these alongside a separate invoicing tool?
Yes — expense management (what your team spends) and invoicing (what you bill clients) are complementary rather than competing categories. If you need the billing side of that picture, see our Best Invoicing & Billing Software for Freelancers comparison.
“Supply chain security” used to mean physical logistics. In software, it now means a specific, practical question: can you prove what’s actually inside the artifact you’re about to deploy, whether any of it is known to be vulnerable, and whether the process that built it was tampered with along the way? Four pieces of free, open-source tooling answer those questions in combination: Syft generates a Software Bill of Materials (SBOM), Grype scans that SBOM for known vulnerabilities, in-toto attests to and verifies the build process itself, and SLSA provides the framework for judging how strong those build-time guarantees actually are. This is an explainer on how they fit together, written and checked directly against each project’s own documentation.
At a Glance
Tool / standard
What it is
Maintainer / governance
License / cost
SBOM (SPDX, CycloneDX)
A structured inventory of a software artifact’s components
SPDX: the Linux Foundation (ISO/IEC 5962:2021). CycloneDX: OWASP Foundation (also ECMA-424)
Free, open standards
Syft
CLI tool/library that generates SBOMs from container images and filesystems
Anchore (open-source project, commercial support optional)
Free, Apache-2.0
Grype
CLI vulnerability scanner that consumes SBOMs (including Syft’s) or scans images/filesystems directly
Anchore (open-source project, commercial support optional)
Free, Apache-2.0
in-toto
Framework/attestation format for recording and verifying each step of a supply chain so tampering is detectable
Cloud Native Computing Foundation (CNCF, graduated project)
Free, open-source
SLSA
A leveled framework (L0–L3) for how trustworthy a build’s provenance is
OpenSSF, under a vendor-neutral cross-organization steering group (Linux Foundation specification)
Free, open specification
Short Verdict
None of these tools compete with each other — they stack. SBOMs (via Syft) tell you what’s in an artifact. Grype tells you whether any of that is a known vulnerability. in-toto tells you whether the process that produced the artifact can be trusted. SLSA tells you how strong that trust actually is, on a scale anyone can audit against. A team adopting software supply chain security in 2026 should expect to run all four pieces together, not pick one.
What an SBOM Is
A Software Bill of Materials is a structured, machine-readable list of every component — open-source library, OS package, language dependency — that makes up a piece of software, roughly analogous to an ingredients list. Two open standards dominate:
SPDX is maintained by the Linux Foundation and is also published as the international standard ISO/IEC 5962:2021. Per spdx.dev, it’s designed to represent systems of software components as SBOMs, and its scope has grown to include AI, data, and security references as well.
CycloneDX is maintained by the OWASP Foundation (with Ecma International’s TC54 committee) and is also published as ECMA-424. Per cyclonedx.org, it’s framed as a “full-stack” BOM standard covering not just software but hardware (HBOM), cryptographic assets (CBOM), AI/ML models, and vulnerability data formats like VEX (Vulnerability Exploitability eXchange).
Neither format is “better” in the abstract — they’re both free, open, and widely supported; which one you use is usually dictated by what your regulator, customer, or downstream scanning tool expects. This is also the natural next step after the risk covered in our earlier piece on AI package hallucinations and slopsquatting: an accurate SBOM is one of the few reliable ways to catch a dependency that shouldn’t be there before it ships.
How Syft Generates SBOMs
Syft is an open-source CLI tool and Go library, maintained by Anchore, that generates an SBOM from a container image, a directory, or an archive. According to the project’s own GitHub page, it supports a wide range of package ecosystems out of the box — Alpine (apk), Debian (dpkg), RPM, Go, Python, Java, JavaScript, Ruby, Rust, PHP, .NET, and more — and can output SPDX, CycloneDX, or its own Syft JSON format, including writing more than one format at once.
# Install Syft
curl -sSfL https://get.anchore.io/syft | sudo sh -s -- -b /usr/local/bin
# Generate an SBOM for a container image, printed as a table
syft alpine:latest
# Generate a CycloneDX-format SBOM for a local project directory
syft ./my-project -o cyclonedx-json
# Write both SPDX and CycloneDX SBOMs to files in one run
syft alpine:latest -o spdx-json=./sbom.spdx.json -o cyclonedx-json=./sbom.cdx.json
Syft is licensed Apache-2.0 and is entirely free to run yourself; Anchore separately sells commercial support and a hosted platform built on top of it, but the open-source tool has no paywall.
How Grype Scans SBOMs for Vulnerabilities
Grype, also maintained by Anchore and also Apache-2.0 licensed, is the matching vulnerability scanner. It can scan a container image or filesystem directly, but it’s designed to work especially well against an SBOM Syft already produced — Grype’s own GitHub page highlights that feeding it a Syft SBOM (rather than re-scanning the raw image) enables faster vulnerability detection, since the inventory step is already done.
# Scan a container image directly
grype alpine:latest
# Scan an existing Syft SBOM instead of re-inventorying the image
grype sbom:./sbom.cdx.json
# Pipe a Syft SBOM straight into Grype
syft alpine:latest -o cyclonedx-json | grype
Per Grype’s documentation, it supports the same broad set of OS and language package ecosystems as Syft (Alpine, Debian, Ubuntu, RHEL, Oracle Linux, Amazon Linux, plus Ruby, Java, JavaScript, Python, .NET, Go, PHP, Rust), and it layers prioritization signals on top of raw CVE matches — EPSS (Exploit Prediction Scoring System) and CISA’s KEV (Known Exploited Vulnerabilities) list — plus support for OpenVEX, so teams can suppress matches they’ve already determined aren’t actually exploitable in their context. In short: Syft answers “what’s in here,” Grype answers “is any of that dangerous, and how urgently.”
What in-toto Adds: Verifying the Build Process Itself
Syft and Grype both operate on the finished artifact. Neither one can tell you whether the build pipeline that produced that artifact was itself compromised — whether an attacker slipped in a malicious step, substituted a dependency mid-build, or tampered with the output before it was signed. That’s the gap in-toto closes.
in-toto is a CNCF graduated project, created and led by Prof. Santiago Torres-Arias at Purdue University under Linux Foundation governance. Per in-toto.io, the framework’s goal is to protect a software product’s integrity “from initiation to end-user installation” — not just the final release step, because, as the project’s own site puts it, a package can already be compromised long before it reaches a repository. It does this by making every step in a supply chain (who ran it, what it did, in what order) transparent and checkable: a supply chain owner can define which steps are expected and by whom, and consumers can verify, after the fact, that the steps that actually happened match that expectation.
A key technical detail, confirmed directly against SLSA’s own blog on the relationship between the two projects: in-toto isn’t only an attestation file format. It defines a lightweight “Statement” envelope that names the artifact in question and a “predicate type” describing the specific claim being made about it — this could be a build-step link, a test result, an SBOM (in SPDX or CycloneDX form), or a SLSA provenance record. On top of that, in-toto also defines a verification model: the supply chain owner signs a layout naming authorized actors and expected steps, and that layout is checked against the attestations actually produced. SLSA’s own framing is explicit: “in-toto isn’t just a format of attestations.”
Where SLSA Fits
SLSA (Supply-chain Levels for Software Artifacts) is not a tool you run — it’s a framework for grading how trustworthy a build’s provenance actually is. It’s developed under OpenSSF by a vendor-neutral, cross-organization steering group (with Google, IBM, Intel, and Red Hat among the listed participants), and published as an open specification under the Community Specification License.
Per slsa.dev’s own level descriptions, the build track has four levels:
L0 — No guarantees. No requirements at all; the implicit baseline for ad hoc or local builds.
L1 — Provenance exists. The build process is consistent and generates provenance describing how the artifact was built, but that provenance may be unsigned and is easy to forge or bypass.
L2 — Hosted build platform. The build runs on dedicated hosted infrastructure, and the platform itself signs the provenance, protecting against post-build tampering.
L3 — Hardened builds. The build platform isolates runs from each other and keeps signing secrets inaccessible even to user-defined build steps, protecting against tampering during the build itself.
Provenance — “what entity built the artifact, what process they used, and what the inputs were” in SLSA’s own words — is the central artifact at every level; higher levels simply make that provenance harder to forge or bypass. And per SLSA’s own blog post explaining the relationship, SLSA Provenance (the predicate at https://slsa.dev/provenance/v1) is itself carried inside an in-toto Statement — SLSA defines what the build claim should contain, and in-toto supplies the signed, verifiable envelope and verification process that claim travels in. This pairs naturally with the CI/CD hardening practices in our earlier pieces on Sigstore, SLSA, and provenance attestation and the broader CI/CD supply-chain security checklist, both of which cover the pipeline-hardening side that complements the artifact-level tooling discussed here.
Comparison Table
Question it answers
Tool/standard
Output
What components are in this artifact?
Syft
SBOM (SPDX, CycloneDX, or Syft JSON)
Are any of those components known-vulnerable?
Grype
Vulnerability match list, prioritized with EPSS/KEV, filterable with VEX
Was the build process itself tampered with?
in-toto
Signed layout + link/attestation metadata, independently verifiable
How strong is the build’s provenance, on a comparable scale?
SLSA
A level (L0–L3) describing build-platform trust, carried as an in-toto-wrapped provenance attestation
Trade-offs
SBOM format choice has real downstream friction. SPDX and CycloneDX are both free and widely accepted, but regulators, customers, and scanning tools don’t always agree on which they expect — generating both (as Syft lets you do in a single command) sidesteps the argument.
An SBOM is a snapshot, not a guarantee. Syft tells you what’s declared in the artifact; it can’t tell you whether the build that produced it was itself compromised — that’s what in-toto and SLSA are for, not a gap in Syft.
Grype’s accuracy depends on database freshness and ecosystem coverage, and no vulnerability scanner eliminates false positives/negatives entirely — EPSS and KEV scoring help triage, but they don’t replace judgment.
in-toto’s guarantees require actually running verification, not just generating attestations. Signing a layout and producing link metadata does nothing if nobody checks the finished chain against it before deploying.
SLSA levels describe build-platform trust, not application security. A SLSA L3 artifact can still contain a vulnerable dependency — that’s precisely why SLSA, Syft, and Grype are complementary rather than substitutes for one another.
Who Should Care
Platform/DevOps teams building CI/CD pipelines who need a repeatable way to produce and scan SBOMs on every build, not just at release time.
Security and compliance teams responding to customer or regulatory SBOM requirements (increasingly common in US federal and critical-infrastructure procurement) who need a free, standards-compliant way to generate them.
Open-source maintainers who want to give downstream users verifiable proof of how a release was built, not just a changelog.
Anyone evaluating AI-generated code or AI coding assistants, where an accurate, automatically generated SBOM is one of the few practical checks against a hallucinated or substituted dependency making it into a shipped artifact.
Bottom Line
None of this tooling costs money, and none of it is optional in any meaningful sense anymore for teams shipping software that others depend on. Syft and Grype are a five-minute CLI install that immediately answers “what’s in this artifact and is any of it dangerous.” in-toto and SLSA are the layer above that, answering the harder question of whether the artifact’s own creation can be trusted — and increasingly, that’s the question customers and regulators are starting to ask for proof of, not just an assurance.
FAQ
Do I have to choose between SPDX and CycloneDX? Not with Syft — it can output both formats from the same scan in one command, so many teams generate both and let downstream consumers pick.
Are Syft and Grype really free? Yes. Both are Apache-2.0 licensed open-source projects maintained by Anchore, installable and runnable with no license key. Anchore sells separate commercial support and a hosted platform, but the CLI tools themselves are not gated.
Can Grype scan something other than a Syft SBOM? Yes — it can scan a container image or filesystem directly without a pre-generated SBOM, though per Anchore’s own documentation, feeding it an existing Syft SBOM is faster since the inventory step is already done.
Is in-toto the same thing as SLSA? No. SLSA defines the specific claim (“provenance”) and a maturity scale (L0–L3) for how trustworthy that claim is; in-toto defines the signed envelope/attestation format that provenance (and other claims, like SBOMs or test results) travels in, plus the layout-based verification model used to check it. SLSA’s own blog is explicit that SLSA provenance is carried inside an in-toto attestation, not a competing format.
What SLSA level should a typical team target first? SLSA’s own materials describe L1 (provenance exists, even if unsigned) as the first on-ramp, moving to L2 (hosted, platform-signed builds) as a realistic target for most CI/CD setups; L3’s isolation and secret-handling requirements are aimed at build platforms themselves, not typical application teams.
Getting a contract signed used to mean printing, scanning, and chasing people down by email. In 2026, the question for most teams isn’t whether to use e-signature software — it’s which platform to standardize on, and whether to pay for workflow automation on top of the signature itself. We compared the three most-searched names in the space — DocuSign, PandaDoc, and Dropbox Sign — directly against their own published pricing pages to see what you actually get at each price point.
All prices below were checked against each vendor’s own pricing page in November 2026. Where a vendor doesn’t publish a number — usually for its top enterprise tier — we say so explicitly rather than guess.
Businesses that want the most widely recognized, broadly integrated e-signature brand
PandaDoc
$19/seat/month (Starter, billed annually); free eSign-only plan available
Yes — 5 documents/month, 5 templates
Teams that want document creation, quoting, and e-signature combined in one tool
Dropbox Sign
$15/month (Essentials, billed yearly)
No ongoing free subscription — only a one-off free single-document signing tool, plus a 30-day trial on paid plans
Individuals and small teams who want simple, inexpensive e-signature without a document builder
Short Verdict
If you need the most trusted name for legal enforceability and you’re willing to pay for it, DocuSign is still the default choice, especially once you need advanced identity verification or Salesforce-grade workflow automation. If you want one tool that builds proposals, quotes, and contracts and collects the signature — with a genuinely usable free tier — PandaDoc is the better all-in-one pick for small and mid-size teams. If all you need is fast, no-frills legally binding signatures at the lowest price, Dropbox Sign wins on cost, particularly for solo users and small teams already living in Dropbox or Google Drive.
What It Is: Comparing Three Different Approaches to E-Signature
These three products solve overlapping but not identical problems:
DocuSign started as a pure e-signature tool and has grown into a broader Intelligent Agreement Management suite. Its core eSignature product is sold in Personal, Standard, Business Pro, and a custom Enhanced/Enterprise tier, with heavier document-workflow and CLM features reserved for its separate, custom-priced IAM products.
PandaDoc leans into document creation first: proposal and quote building, a content library, and approval workflows, with e-signature bundled in. Its separate PandaDoc Sign product exists for people who only want the signature piece.
Dropbox Sign (formerly HelloSign) is the leanest of the three — a straightforward e-signature tool with templates and basic integrations, now sold under the Dropbox brand with tight Dropbox, Google Drive, and Microsoft Word integration.
All three advertise their signatures as legally binding under the U.S. ESIGN Act and comparable frameworks like eIDAS in the EU, and each vendor publishes its own legality/compliance statement (DocuSign at docusign.com/electronic-signature-legality, PandaDoc within its product pages, and Dropbox Sign at sign.dropbox.com/legal). None of the three publishes a side-by-side legal opinion for every jurisdiction, so if you operate in a heavily regulated industry or country, verify with your own counsel — the general ESIGN/eIDAS validity claim is standard across the industry and not unique to any one vendor.
$15/month, billed yearly ($180/year); list price, before any promo
1 user, limited templates (around 5)
Standard
$25/user/month, billed yearly (starts at $600/year for 2+ users)
2+ users, 15 templates, Salesforce integration
Premium
Not published — custom quote
5+ users, unlimited templates
A few things worth flagging explicitly: DocuSign’s Standard and Business Pro per-seat prices are listed identically whether you look at the monthly or annual pricing view on its own page, so confirm your exact annual rate at checkout before committing. Dropbox Sign’s pricing page also runs limited-time promotional discounts (for example, reduced first-year rates) on top of these list prices — we’ve reported list prices here since promotions change frequently and aren’t guaranteed to still be active when you sign up. None of the three vendors publishes a flat dollar figure for their top enterprise tier; all three require a sales conversation for that pricing, which is standard practice across the e-signature category and not a red flag on its own.
Pros and Cons
DocuSign
Pros: The most recognized e-signature brand, which matters for signer trust; broad integration catalog (1,000+); strong identity-verification and audit-trail features; scales up into a full Intelligent Agreement Management platform.
Cons: No permanent free plan, only a 14-day trial; envelope limits are per-year even on paid plans, which can surprise high-volume teams; workflow/approval automation is reserved for Business Pro and above; Business Pro has no self-serve trial, only a demo request.
PandaDoc
Pros: Genuinely useful free tier (5 docs/month); combines proposal/quote building with e-signature so you don’t need a separate document tool; Business tier adds real approval workflows and a content library at a lower price than DocuSign’s equivalent tier.
Cons: Approval workflows are locked behind the Business plan, not available on Starter; per-seat pricing can add up quickly for larger sales teams; the pricing page is inconsistent about whether the free plan includes the drag-and-drop document editor, so confirm before relying on it.
Dropbox Sign
Pros: Lowest list price of the three for a single user; every plan includes a non-editable audit trail; tight integration with Dropbox, Google Drive, Microsoft Word, and (on Standard/Premium) Salesforce.
Cons: No ongoing free subscription plan with templates or multiple users — only a one-off free document-signing tool and a 30-day trial; the pricing page doesn’t break out workflow/approval features by plan, so you may need to ask sales directly; Standard requires at least 2 users, so true solo pricing is the Essentials tier only.
Who It’s a Good Fit For
Choose DocuSign if signer trust and brand recognition matter (e.g., real estate, legal, HR at scale), or if you expect to eventually need advanced compliance, SSO, or CLM-style workflow automation.
Choose PandaDoc if you’re a small business, agency, or sales team that wants to build the document (proposal, quote, contract) and get it signed in the same tool, and you want to start free.
Choose Dropbox Sign if you just need reliable, inexpensive e-signatures with minimal setup, especially if your team already lives in Dropbox or Google Workspace.
Who Should Look Elsewhere
Solo freelancers who sign fewer than 5 documents a month and want to pay nothing long-term should look at PandaDoc’s free eSign plan before paying for DocuSign Personal or Dropbox Sign Essentials.
Teams that need heavy document-approval chains (multi-department sign-off, conditional routing) should budget for DocuSign Business Pro or PandaDoc Business — none of the entry-level plans from any of the three vendors include real approval workflows.
Anyone needing a hard, published enterprise price today rather than a sales call should expect to negotiate — all three vendors keep their top tier behind “Contact Sales.”
Bottom Line
There isn’t a single “best” e-signature tool in 2026 — there’s a best tool for your volume and workflow. DocuSign remains the safest default for brand trust and advanced compliance, but you pay for it and get no free tier. PandaDoc is the strongest value if you want document creation and signing together, especially for teams starting out on its free plan. Dropbox Sign is the cheapest path to legally binding signatures if your needs are simple. Match the plan to your actual monthly document volume rather than the sticker price, since all three vendors cap volume well below “unlimited” on their entry tiers.
FAQ
Is DocuSign, PandaDoc, or Dropbox Sign legally binding?
Yes, all three publish their own statements that their electronic signatures are designed to be legally binding under the U.S. ESIGN Act and UETA, and under frameworks like eIDAS in the EU, provided the signing process meets the legal requirements for consent and intent to sign in your jurisdiction. This is standard across the e-signature industry rather than a differentiator between these three vendors specifically.
Which of the three has a real free plan?
Only PandaDoc has an ongoing free plan with recurring usage (5 documents and 5 templates per month). DocuSign offers a 14-day free trial rather than a permanent free tier. Dropbox Sign offers a free tool for signing a single one-off document plus a 30-day trial on paid plans, but no recurring free subscription.
Do any of these plans include workflow or approval automation on the cheapest tier?
No. In every case, approval/workflow automation is reserved for a mid-tier or higher plan: DocuSign Business Pro and above, PandaDoc Business and above, and (per Dropbox Sign’s own feature list) its higher plans. Budget for at least the second-from-bottom paid tier if approval routing is a requirement.
How much does enterprise-tier pricing cost for each vendor?
None of the three publishes a fixed price for its top tier (DocuSign Enhanced/Enterprise, PandaDoc Enterprise, or Dropbox Sign Premium) — all three require contacting sales for a custom quote. This is normal for enterprise software and isn’t specific to any one of these vendors.
Can I switch between these providers later without losing signed documents?
Completed, signed documents are generally yours to download and store outside any of these platforms (as PDFs with an embedded audit trail), so switching providers doesn’t strand your historical records. What doesn’t transfer automatically is your template library and workflow configuration — budget time to rebuild those in a new tool.
Virtual private networks were built for a world where the network edge was the security boundary. Zero Trust Network Access (ZTNA) platforms replace that model with per-request, identity-aware access to individual applications instead of the network as a whole. In 2026, three vendors dominate the conversation at very different points on the spectrum: Zscaler Private Access (ZPA), an enterprise-grade platform sold through custom quotes; Cloudflare Access, a self-serve product with a genuinely usable free tier; and Twingate, a developer-friendly ZTNA tool built around peer-to-peer connections. We went directly to each vendor’s own site and published materials to compare what they actually say about architecture, features, and price.
At a Glance
Platform
Published pricing
Free tier
Core model
Best for
Zscaler Private Access (ZPA)
Not publicly listed; sold as bundled “platform” packages via quote
None
Cloud-native proxy: Client Connector, App Connector, Service Edge
Large enterprises already in the Zscaler Zero Trust Exchange
Identity- and device-checked per-request access via Cloudflare’s network
Small teams and proof-of-concepts, and teams already on Cloudflare
Twingate
Free (Starter) / $5–$12 per user/month (Teams) / $10 per user/month+ (Business) / Custom (Enterprise)
Up to 5 users and 50 resources
Peer-to-peer (P2P) connections brokered by a lightweight relay, no exposed network perimeter
Startups and engineering teams wanting fast, self-serve setup
Short Verdict
All three replace the classic VPN concentrator with an identity-aware, app-level access model — none of them hand a connected device a routable slot on the corporate LAN. But they serve different buyers. Zscaler is built for large organizations that want ZPA as one module inside a much bigger Zero Trust Exchange and are comfortable negotiating a contract rather than reading a price list. Cloudflare Access is the easiest platform to actually start using today, with a free tier that comfortably covers a small team and transparent per-user pricing once you outgrow it. Twingate sits in between: it is the most “developer-first” of the three, with a peer-to-peer architecture, a real (if small) free tier, and published team/business pricing that undercuts Cloudflare’s pay-as-you-go rate at smaller volumes.
What It Is
All three products are ZTNA: instead of granting a device access to a subnet (as a VPN does), they grant an authenticated identity access to one named application or resource, re-checked on every request or session. None of them require a traditional VPN concentrator sitting at the network edge.
Zscaler Private Access is a cloud-native service inside Zscaler’s Zero Trust Exchange. Per Zscaler’s own ZPA data sheet, a lightweight Client Connector on the user’s device forwards traffic to the nearest Service Edge (Zscaler runs more than 160 points of presence); a lightweight App Connector virtual machine sits in front of the private application and makes an inside-out connection, so the app is never exposed to the public internet; a Service Edge stitches the two tunnels together and enforces policy after the user authenticates through their identity provider. A Private Cloud Controller option extends this on-premises for business continuity if the Zscaler cloud is unreachable.
Cloudflare Access runs on Cloudflare’s global network. According to Cloudflare’s own product page, “Application Connector” software links a private resource to Cloudflare without a publicly routable IP or VM infrastructure, and a device client sends user traffic into Cloudflare’s network, where each request is checked against identity and device posture before access is granted — a textbook identity-aware proxy. Cloudflare explicitly markets Access as a VPN replacement.
Twingate takes a more decentralized approach: rather than funneling all traffic through a single provider-run proxy point, Twingate brokers direct, encrypted peer-to-peer connections between a user’s device and a small software “Connector” placed next to the resource. Twingate’s own pricing page lists split tunneling and peer-to-peer connections as Starter-tier features available even on the free plan.
Pricing Breakdown
This is where the three vendors diverge most sharply, and it’s worth being precise rather than approximate.
Plan
Zscaler ZPA
Cloudflare Access
Twingate
Free tier
None found on zscaler.com
Free — $0 forever, up to 50 users, includes ZTNA, Application Connector software, device client, Secure Web Gateway, Digital Experience Monitoring, and up to 2 read-only CASB API integrations
Starter — free, up to 5 users and 50 resources, with P2P connections, split tunneling, and conditional access
Entry paid tier
“Zscaler Essentials Platform” / “ZPA Clientless Platform” bundles, sold per quote; data sheet states only licensing minimums (e.g. VPN Service Edge add-ons require a 50-user minimum), not dollar prices
Pay-as-you-go — $7 per user/month, billed annually, no user cap; adds chat/ticket support and up to 30 days of log retention
Teams — listed at $5 per user/month with annual billing (15% off), up to 100 users; adds SSO via Google Workspace, SaaS app gating, device posture checks
Mid/upper tier
“Zscaler Private Access Platform” / “Zscaler Platform” bundles — 20 app segments per Zscaler’s own data sheet; still quote-based
Contract — custom annual per-user pricing for teams building toward full SASE/SSE, with phone support and up to 6 months of log retention
Business — $10 per user/month (annual billing), up to 500 users; adds IdP-based user provisioning, Okta/Entra ID SSO, usage-based and just-in-time access
A note on Twingate’s numbers: Twingate’s pricing page shows $5/user/month for Teams and $10/user/month for Business as the annual-billing rate (described as 15% off), while a separate comparison table on the same site shows $12/user/month for Teams/Business, which appears to be the monthly-billing rate. Twingate’s site does not label the two figures side by side as clearly as it could, so if list price matters for your budget, confirm the current monthly vs. annual rate directly on twingate.com/pricing before committing. There is also a $15/month flat-rate “Home” plan capped at 7 users, explicitly for non-commercial/homelab use.
A note on Zscaler: Zscaler does not publish per-user or per-month pricing for ZPA anywhere on zscaler.com. Its own solution brief (“Zscaler Private Access Suites”) describes four SKU-level packaging options — Zscaler Essentials Platform, ZPA Clientless Platform, Zscaler Private Access Platform, and Zscaler Platform — differentiated mainly by app-segment counts (10 vs. 20) and which add-ons are bundled, with actual cost available only through a sales quote. Treat any third-party “per-user cost” figure you see for Zscaler as an estimate, not a published list price.
Yes — Client Connector retrieves posture at config download; risk-based policy engine validates it; Chrome Enterprise Browser integration adds posture signal for unmanaged/BYOD devices
Yes, via third-party endpoint protection integrations checked per request before access is granted
Native device posture checks are a named feature starting on paid tiers (Home and up), per Twingate’s pricing page
App-level vs. network-level access
App-level — users are connected to named applications, never the network; apps are never exposed to the public internet
App-level — per-application, per-network policies enforced per request, with a policy tester tool
App/resource-level — access is scoped to individual resources behind a Connector, not a subnet
Identity provider integration
Users authenticate to the IdP before a tunnel is established; Zscaler’s data sheet names Azure AD, Okta, and Ping as examples (not an exhaustive list)
Supports multiple enterprise and social IdPs simultaneously, plus generic SAML and OIDC connectors
SSO via Google Workspace from the Teams tier; Okta, Entra ID and others from the Business tier, plus IdP-driven user provisioning
Clientless / browser-based access
Yes — clientless web, RDP, SSH, VNC access for third parties and BYOD
Yes — browser-based SSH, VNC, and clientless web access
Primarily client-based (lightweight native app); not positioned as clientless-first
Pros
Zscaler Private Access
Deepest enterprise feature set: AI-assisted app segmentation, Layer 7 AppProtection, DLP, deception technology, and OT/ICS privileged access, all as part of one ecosystem.
Business continuity option (Private Cloud Controller) keeps access working during a cloud outage.
Widely deployed at large scale, with a dedicated on-premises Private Service Edge option.
Cloudflare Access
A genuinely usable free tier (50 users, forever) with core ZTNA, SWG, and DEX included, not just a trial.
Transparent, published pay-as-you-go pricing ($7/user/month) with no minimum user count.
Runs on Cloudflare’s existing global network, which many teams are already using for DNS, CDN, or WAF.
Twingate
Peer-to-peer architecture avoids funneling all traffic through a single central proxy.
Fastest self-serve setup of the three, aimed squarely at engineering teams.
Published, comparatively low per-user pricing at the Teams/Business tiers.
Cons
Zscaler Private Access
No published pricing at all — you cannot self-serve a quote, and many add-ons carry 500-user purchase minimums that don’t fit smaller organizations.
No free tier; evaluating it requires engaging sales for a demo.
Cloudflare Access
The free plan’s DLP and CASB are explicitly “limited”/”up to 2 read-only” integrations — fine for evaluation, not for serious data-protection use.
Standard log retention tops out at 24 hours on Free and 30 days on Pay-as-you-go; longer retention and SIEM export require the Contract tier.
Twingate
The free Starter tier is capped tightly (5 users, 50 resources) — too small for anything beyond a solo developer or a tiny pilot.
Its own marketing pages present two different per-user numbers (annual vs. monthly) without consistently labeling which is which, so double-check the live pricing page before budgeting.
Choose Zscaler ZPA if you’re a large enterprise already standardizing on the Zscaler Zero Trust Exchange, need OT/ICS privileged access or AI-powered automatic app segmentation, and have a procurement process built for negotiated contracts rather than list prices.
Choose Cloudflare Access if you want to start securing internal apps today without a sales call, you’re already using Cloudflare for other services, or your team is under 50 users and the free tier simply covers you.
Choose Twingate if you’re an engineering-led team that wants a fast, developer-friendly rollout, a peer-to-peer architecture appeals to you, and you want transparent (if slightly confusingly labeled) per-user pricing without an enterprise sales cycle.
Who Should Look Elsewhere
Teams with a strict self-serve budget process should think twice about Zscaler — you simply cannot get a number without talking to sales.
Organizations needing heavy DLP, deception, or Layer 7 app-protection out of the box may find Cloudflare’s Free/Pay-as-you-go tiers too light and should budget for Contract — or compare against Zscaler’s bundled add-ons.
Very small teams who need more than 5 users but aren’t ready to pay should look at Cloudflare’s 50-user free tier instead of Twingate’s 5-user Starter plan.
Bottom Line
There is no single “best” ZTNA platform in 2026 — there’s a best fit per budget and buying process. Cloudflare Access is the most approachable starting point for most small-to-mid-size teams because of its real free tier and published pricing. Twingate is the strongest choice for engineering teams that want a peer-to-peer model and self-serve pricing at slightly lower per-user cost than Cloudflare’s pay-as-you-go rate. Zscaler Private Access remains the deepest enterprise platform of the three, but it’s built for organizations that negotiate contracts, not ones comparison-shopping a price list.
FAQ
Does Zscaler Private Access have a free trial? Zscaler’s own site does not advertise a self-serve free tier for ZPA; evaluation is done through a requested demo, not a free account.
How many users can use Cloudflare Access for free? Up to 50 users, with no time limit, according to Cloudflare’s own Zero Trust pricing page.
Is Twingate’s free plan usable for a real small business? It’s capped at 5 users and 50 resources per Twingate’s pricing page, so it fits a solo developer or a very small pilot, not a full small-business rollout — at that point you’d move to the Teams tier.
Do any of these replace a VPN entirely? All three are marketed explicitly as VPN replacements for application access, since none of them grant network-level access the way a VPN concentrator does. Whether you can remove your VPN entirely still depends on other use cases (e.g., site-to-site connectivity) that these ZTNA products don’t target.
Can I mix identity providers across these platforms? Yes — all three support integrating with standard identity providers (SAML/OIDC, Okta, Azure AD/Entra ID, Google Workspace, Ping, etc.), though the specific list and tier requirements differ by vendor as shown in the feature table above.
For most of the last fifteen years, digital marketers measured performance with click-level attribution: a cookie or device ID tracked a person from ad impression to conversion, and dashboards assigned credit touch by touch. That approach is breaking down as third-party cookies and cross-device tracking keep eroding — and in response, a much older measurement method is back in fashion: Marketing Mix Modeling (MMM). In 2026, the clearest sign of that resurgence is that Google and Meta have each released a free, open-source MMM tool — Meridian and Robyn, respectively. This article explains what MMM actually is, how Meridian and Robyn differ, and why neither replaces attribution software so much as offers a different lens entirely.
We’ve covered click-level measurement before in our review of marketing attribution software (Triple Whale vs Northbeam vs Rockerbox). MMM is not a competitor to those tools — it’s a complementary, top-down measurement approach that answers questions attribution software structurally can’t.
At a Glance
Google Meridian
Meta Robyn
Maker
Google
Meta Marketing Science (originally the Facebook/Meta team)
Cost
Free, open-source
Free, open-source (MIT licensed)
Primary language
Python, with Colab notebook examples and a new JAX-based backend
R (CRAN or GitHub); a Python API is in beta and still requires R installed
Statistical approach
Bayesian modeling with causal inference; supports geo-experiment calibration
Ridge regression plus a multi-objective evolutionary algorithm (via the Nevergrad optimizer) for hyperparameter search
Distinctive feature
Meridian GeoX geo-experiment calibration, brand-equity signals (e.g., branded Google query volume), an MCP-based “agentic” toolkit, JAX backend for speed
Automated/semi-automated hyperparameter tuning designed to reduce modeler bias; adstock and saturation-curve estimation; gradient-based budget allocator
Is it a finished product?
Actively maintained library with a changelog and API reference, not a packaged SaaS app
Described by Meta itself as “experimental” and “semi-automated”
Short Verdict
Meridian and Robyn are both free, open-source statistical libraries, not plug-and-play dashboards — using either requires data science resources (Python or R, a data pipeline, someone who understands the output) that a commercial attribution platform’s UI hides from the end user. Meridian leans into Bayesian causal inference and ties cleanly into geo experiments for calibration, attractive to teams that can run lift tests and want rigorous uncertainty estimates. Robyn’s Ridge-regression-plus-evolutionary-algorithm approach is lighter-weight and built to be more automated out of the box, at the cost of the explicit uncertainty quantification Bayesian methods provide. Neither replaces attribution software; both target the budget-allocation and channel-effectiveness questions attribution can’t answer once cookies and device IDs stop working reliably.
What Marketing Mix Modeling Actually Is
MMM is a statistical technique that correlates aggregate marketing spend across channels — TV, paid search, social, out-of-home, radio, and more — with aggregate business outcomes like weekly sales or revenue, typically using regression analysis on months or years of historical data. Critically, MMM doesn’t need to track an individual user’s journey at all. It works entirely with spend-level and outcome-level time series, which is exactly why it’s resistant to the signal loss that’s broken multi-touch attribution (MTA): there’s no cookie to lose and no device ID to match, because the model never looks at individual people in the first place.
That’s also MMM’s core limitation. Because it works at an aggregate level, it typically can’t tell you which specific ad or audience segment drove a specific conversion the way MTA can — it tells you how a channel’s overall spend level tends to move overall outcomes, including diminishing-returns effects (saturation) and carryover effects (adstock) that a simple click report would miss entirely. It’s a budget-planning and strategy tool more than a day-to-day optimization tool.
Why MMM Is Resurging Now
The driver is signal loss. Third-party cookie restrictions, Apple’s App Tracking Transparency, and browser-level privacy changes have all degraded MTA’s ability to stitch a single customer journey across devices and platforms — the exact dependency our Privacy Sandbox cookieless-future piece walks through in more technical detail. MTA also structurally can’t see “dark” research and influence — private communities, word of mouth, offline conversations — that increasingly shape purchase decisions. MMM doesn’t depend on any of that tracking infrastructure, which is precisely why marketers who spent a decade moving away from it are now moving back.
The shift isn’t “MMM replaces MTA” — virtually every credible source on this, including commercial measurement vendors, argues for using both. One useful framing, used by Triple Whale in its own measurement materials, is MTA as a microscope (granular, tactical, short-term) and MMM as a telescope (aggregate, strategic, long-term), with incrementality testing (randomized holdout or geo experiments) acting as the referee when the two disagree.
Google Meridian, in Detail
Meridian is Google’s open-source library for building, running, and analyzing marketing mix models, distributed with Colab notebook examples, a changelog, and an API reference rather than as a hosted product. It uses Bayesian modeling and causal inference, and its newer versions (Meridian is on major version 2.0 as of its current documentation) add several notable capabilities: Meridian GeoX runs geo-based experiments and automatically calibrates the MMM against that causal lift evidence; model-health diagnostics assess how much calibration is improving the model and recommend which channels most need a lift test; “full-funnel” modeling incorporates brand-equity signals, such as branded Google query volume, to capture the indirect effect of upper-funnel brand spend; and an MCP-based “agentic” toolkit lets AI agents help automate parts of the modeling workflow. Google also reports a new JAX computational backend that runs roughly twice as fast and about four times more resource-efficient than the prior version. Meridian is free to use; Google does not publish any licensing fee for the library itself.
Meta Robyn, in Detail
Robyn is Meta Marketing Science’s open-source MMM package, released under the MIT license, meaning the code is free to use, modify, and redistribute. Meta describes it as “experimental” and “semi-automated.” Robyn’s core is an R package (installable from CRAN or GitHub); a Python API exists in beta but still depends on the R package being installed, via a plumber-based bridge. Technically, Robyn combines Ridge regression for the core model with a multi-objective evolutionary algorithm — powered by Meta’s own Nevergrad optimization library — to automate hyperparameter selection, which Meta frames as a way to reduce the subjective, manual tuning bias that older MMM practice relied on. It also includes time-series decomposition to separate trend and seasonality from media effects, models adstock (carryover) and saturation (diminishing returns) curves per channel, and provides a gradient-based optimizer to recommend budget allocation across channels. Meta positions Robyn explicitly as a “privacy-safe” way to make MMM accessible to advertisers of varying sizes and as a contribution to an open-source marketing-science community, rather than as a Meta product tied to Meta’s own ad platforms.
Meridian vs Robyn: The Core Differences
Dimension
Meridian
Robyn
Statistical framework
Bayesian, with explicit uncertainty estimates
Frequentist (Ridge regression) with evolutionary hyperparameter search
Experiment integration
Built-in geo-experiment calibration (GeoX)
Not a built-in feature; external lift tests must be incorporated manually
Ecosystem / language
Python-first, Colab-oriented, JAX-accelerated
R-first, Python API still beta and R-dependent
Automation philosophy
Model-health diagnostics guide the practitioner; newer builds add agentic/MCP tooling
Automated hyperparameter optimization is the headline feature, aimed at reducing manual bias
Brand-effect modeling
Explicit “full-funnel” brand-equity signal support (e.g., branded query volume)
Not highlighted as a distinct capability in Meta’s own documentation
Pros and Cons
Meridian — Pros: free; rigorous Bayesian framework with uncertainty quantification; built-in experiment calibration; actively developed with performance upgrades. Cons: requires Python/data-science skill; no managed hosting or support from Google; steeper learning curve than simpler regression approaches.
Robyn — Pros: free (MIT licensed); automated hyperparameter search lowers the bar to a first working model; well-documented adstock/saturation modeling. Cons: Meta itself labels it “experimental”; primary workflow is R-based with Python still beta; no native experiment-calibration feature.
How Commercial Platforms Position MMM Alongside Attribution
Commercial measurement vendors — including Triple Whale, which we cover in our attribution software comparison — generally don’t ask marketers to choose one measurement method. Triple Whale’s own published framing treats MMM, MTA, and incrementality testing as three complementary inputs: MMM for weekly, top-down budget allocation across channels (including non-click channels like TV, OOH, and audio that MTA can’t see at all), MTA for granular, short-term tactical optimization, and incrementality tests (randomized holdouts or geo-based lift tests) as the experimental check that validates which of the other two to trust when they disagree. Whether a given vendor’s underlying model is a proprietary build, or built on top of open frameworks like Meridian or Robyn, isn’t always disclosed — but the broader market consensus by late 2026 is clearly toward triangulating MMM and attribution together rather than picking a single source of truth.
Who Should Use Which
A data science team with Python expertise that wants to run geo experiments and get calibrated, rigorous budget-allocation estimates should start with Meridian. A team more comfortable in R, or one that wants an automated first pass at hyperparameter tuning without hand-building a Bayesian model, is better served by Robyn. A marketing team without in-house data science resources is generally better served by a commercial platform that packages MMM behind a usable dashboard — at the cost of subscription fees that open-source Meridian and Robyn don’t carry, but with implementation and support handled for you.
Bottom Line
Marketing Mix Modeling isn’t a replacement for attribution software — it’s the privacy-resilient half of a measurement stack that attribution alone can no longer carry on its own as cookies and device identifiers keep eroding. Google’s Meridian and Meta’s Robyn are both free, open-source, and genuinely usable, but they’re statistical libraries for people with data science capacity, not consumer-grade apps. Most marketing teams will either build on one of these two frameworks directly or buy a commercial platform that abstracts the modeling work away — either way, the direction of travel in 2026 is toward combining MMM with attribution and incrementality testing, not toward picking one method and discarding the others.
FAQ
Are Google Meridian and Meta Robyn actually free? Yes. Both are open-source software with no license fee — Meridian is distributed as an open-source library with Colab examples, and Robyn is released under the MIT license. Neither Google nor Meta charges for the code itself; the cost is the engineering and data-science time required to implement and maintain a model.
Is MMM a replacement for multi-touch attribution? No. MMM works on aggregate spend and outcome data and can’t attribute a specific conversion to a specific touchpoint the way MTA can. The two are generally used together, with MMM guiding strategic budget allocation and MTA guiding tactical, channel-level optimization.
What’s the main technical difference between Meridian and Robyn? Meridian uses a Bayesian statistical framework with built-in geo-experiment calibration and is Python-based with a JAX-accelerated backend. Robyn uses Ridge regression combined with an evolutionary algorithm for automated hyperparameter tuning and is primarily an R package, with a beta Python API that still requires R.
Do I need a data science team to use Meridian or Robyn? Realistically, yes. Both are code libraries, not dashboards — Meridian requires Python familiarity and statistical modeling knowledge, and Robyn requires R (or its beta Python bridge) plus an understanding of regression and optimization. Teams without that capacity typically turn to commercial measurement platforms instead.
Why is MMM considered more “privacy-safe” than attribution? Because it models aggregate spend and outcomes over time rather than tracking individual users across devices, MMM has no dependency on cookies, device IDs, or cross-site tracking — the exact mechanisms that privacy regulation and browser changes have been restricting.
Chaos engineering — deliberately injecting failure into a system to see how it responds — has moved from Netflix curiosity to standard SRE practice. In 2026, the three names engineering teams compare most are Gremlin, Chaos Mesh, and LitmusChaos. They are not quite peers: Gremlin is a commercial platform with custom, quote-based pricing, while Chaos Mesh and LitmusChaos are both free, Apache-licensed, CNCF-hosted open-source projects built specifically for Kubernetes. This guide compares what each actually does and who it fits.
At a Glance
Tool
Price
Open Source
Governance
Best For
Gremlin
Custom quote; 30-day free trial, no credit card
No
Commercial company (Gremlin Inc.)
Enterprises wanting a managed platform with reliability scoring, dependency discovery, and reporting
Chaos Mesh
Free
Yes (Apache 2.0)
CNCF Incubating project
Kubernetes-native teams wanting broad fault coverage (network, I/O, kernel, cloud) with CRD-based control
LitmusChaos
Free (core); Enterprise option referenced but unpriced on the project site
Yes (Apache 2.0)
CNCF Incubating project
Kubernetes teams wanting a shared ChaosHub of reusable experiments and GitOps-friendly workflows
Short Verdict
If your team runs on Kubernetes and wants to start chaos testing without a procurement cycle, Chaos Mesh and LitmusChaos are both genuinely free and CNCF-governed, so the choice between them comes down to workflow style: Chaos Mesh favors fine-grained CRDs per fault type with a strong namespace/RBAC-based blast-radius model, while LitmusChaos favors a community ChaosHub of pre-built, shareable experiments plus steady-state “probes.” Gremlin is the choice when you need a managed product with cross-team reliability scoring, dependency mapping, and executive-level reporting — but you’ll need to talk to sales, since no self-serve price list is published.
What Each Tool Is
Gremlin is a commercial chaos engineering and reliability platform. Beyond raw fault injection, it packages dependency discovery, reliability scoring across an organization, disaster-recovery testing, continuous risk detection (like configuration drift), and an early-access “Foresight AI” layer that recommends and re-verifies fixes. Gremlin.com doesn’t publish list prices anywhere; the Gremlin Platform is “priced per service” and Foresight AI is “priced per team,” both behind a sales conversation, with a 30-day no-credit-card trial as the only self-serve option.
Chaos Mesh is a CNCF Incubating open-source project, licensed Apache 2.0, that runs as Kubernetes-native Custom Resource Definitions. Experiments — PodChaos, NetworkChaos, StressChaos, and others — are just Kubernetes objects you apply with kubectl or manage through its bundled dashboard. It deploys to any cluster, including local ones like minikube or kind.
LitmusChaos is also a CNCF-hosted, Apache 2.0 open-source platform, installed via Helm, built around declarative, schedulable “Chaos Experiments” (renamed “Chaos Faults” as of version 3.0) that can be chained in sequence or parallel. Its distinguishing feature is ChaosHub, a public (and in paid Enterprise setups, private) catalog of pre-built, reusable experiments, plus steady-state “probes” that verify a hypothesis before and after a fault runs.
Pricing Breakdown
Plan
Price
What You Get
Gremlin – Free trial
$0 for 30 days
Full access to fault injection experiments, reliability testing/scoring, observability integrations, and implementation support; no credit card required, no auto-conversion to paid.
Gremlin Platform
Custom, “priced per service”
Dependency discovery, fault injection and scenarios, reliability scores, disaster-recovery testing, risk detection, org-wide benchmarking and reporting.
Gremlin Foresight AI
Custom, “priced per team” (early access)
Adds AI-driven resilience recommendations and closed-loop remediation verification on top of an existing platform license.
Chaos Mesh
$0
Full fault-injection catalog (pod, network, DNS, HTTP, I/O, time, stress, kernel, block device, JVM, physical-machine, and cloud faults on AWS/Azure/GCP), dashboard, Workflow and Schedule orchestration — no license cost since it’s self-hosted on your own cluster.
LitmusChaos core
$0
ChaosHub experiments, Helm-based install, scheduling, chaining, probes, Prometheus metrics export, litmus-lite for lightweight local testing.
LitmusChaos Enterprise
Not published; contact via litmuschaos.io
The project site references an Enterprise offering alongside the open-source core, but gives no pricing detail — treat this as a separate commercial conversation, not part of the free project.
Because Gremlin and LitmusChaos Enterprise are both quote-based with nothing published, we aren’t estimating numbers for either — any figure you see elsewhere online for “Gremlin pricing” is almost certainly a third-party estimate, not an official rate card.
Key Feature Comparison
Fault injection breadth: Gremlin groups attacks into Resource (CPU, memory, GPU, I/O, disk, process exhaustion), State (shutdown, time travel, process killer), and Network (blackhole, latency, packet loss, DNS blocking, certificate-expiry checks). Chaos Mesh covers pod, network, DNS, HTTP, I/O, time, stress, kernel, block-device, JVM, physical-machine, and public-cloud (AWS/Azure/GCP) faults. LitmusChaos ships fault definitions through ChaosHub rather than a fixed built-in list, so coverage depends on which hub experiments you pull in.
Kubernetes-native support: Chaos Mesh and LitmusChaos are both built Kubernetes-first — CRDs and Helm charts respectively. Gremlin supports Kubernetes by targeting Deployments, ReplicaSets, StatefulSets, DaemonSets, and Pods directly, alongside its broader bare-metal, multi-cloud, and serverless coverage.
Blast-radius control: Gremlin advertises explicit “blast radius controls and automatic halt conditions” as a safety feature. Chaos Mesh scopes experiments with label/annotation selectors and a namespace allowlist, with RBAC enabled by default. LitmusChaos scopes experiments through its declarative ChaosEngine/ChaosExperiment resources and probes that can gate or report on steady-state health.
Experiment scheduling / GameDay-style workflows: Chaos Mesh has a dedicated Workflow feature (serial or parallel steps, suspend nodes, status checks) plus a Schedule resource for recurring runs. LitmusChaos experiments are described as “declarative, schedulable, and browsable” and can be chained into scenarios. Gremlin’s own marketing pages describe “recommended scenarios” for common failure modes, though neither of the pages we reviewed used the specific term “GameDay” — check Gremlin’s documentation directly if that exact workflow label matters to your evaluation.
Pros and Cons
Gremlin
Pros: Explicit blast-radius and halt-condition safety controls; dependency discovery and org-wide reliability scoring go beyond raw fault injection; covers bare metal, multi-cloud, serverless, and Kubernetes from one product; 30-day no-card trial.
Cons: No published pricing at all — every tier requires a sales conversation; not open source, so you can’t audit or self-host the control plane; overkill for a small team that just wants to kill a pod and watch what happens.
Chaos Mesh
Pros: Completely free and Apache-licensed; very broad fault catalog including kernel- and JVM-level faults most tools skip; CRD-based design fits naturally into existing GitOps/Kubernetes workflows; RBAC on by default.
Cons: Kubernetes-only in practice — no native support for bare-metal or non-Kubernetes infrastructure; you own the operational burden of running and upgrading it yourself; still an Incubating (not Graduated) CNCF project, so governance maturity is a notch below a Graduated project.
LitmusChaos
Pros: Free and Apache-licensed; ChaosHub gives teams a head start with pre-built, shareable experiments instead of writing fault definitions from scratch; probes make it straightforward to assert steady-state before/after a fault; exports Prometheus metrics for existing dashboards.
Cons: The project’s own documentation is thinner on specifics (exact fault catalog, scheduling mechanics) than Chaos Mesh’s; also Incubating-stage CNCF governance; the Enterprise tier is mentioned but entirely unpriced, so budgeting for anything beyond the free core requires a direct inquiry.
Who It’s a Good Fit For
Kubernetes-native platform teams on a budget: Chaos Mesh or LitmusChaos — both are free, CNCF-governed, and designed specifically for your environment.
Teams wanting pre-built, shareable experiment libraries: LitmusChaos, via ChaosHub.
Teams needing kernel, JVM, or cloud-provider-level fault injection on Kubernetes: Chaos Mesh, for its broader built-in catalog.
Enterprises needing org-wide reliability scoring, dependency mapping, and executive reporting across mixed infrastructure (not just Kubernetes): Gremlin, accepting the custom-quote process.
Who Should Look Elsewhere
Teams without any internal platform engineering capacity to self-host and maintain an open-source chaos tool may find Gremlin’s managed model a better operational fit, despite the opaque pricing.
Teams running mostly bare-metal or non-Kubernetes infrastructure get limited value from Chaos Mesh or LitmusChaos, both of which are Kubernetes-first by design.
Teams that need firm, published pricing to get budget approval quickly may be frustrated by both Gremlin’s and LitmusChaos Enterprise’s quote-only models — the open-source cores of Chaos Mesh and LitmusChaos remain the only genuinely zero-cost path.
The Bottom Line
Chaos Mesh and LitmusChaos cover the same ground — free, CNCF-governed, Kubernetes-native chaos engineering — and the choice between them is really a matter of workflow preference: Chaos Mesh’s CRD-per-fault-type model versus LitmusChaos’s ChaosHub-and-probes model. Gremlin sits in a different category entirely: a commercial, broader-than-Kubernetes reliability platform with safety controls and organizational reporting baked in, priced only through direct sales contact. Pair whichever chaos tool you choose with an observability stack that can actually show you what broke — our comparison of Datadog, Grafana Cloud, and New Relic is a reasonable place to start if you don’t already have one in place.
FAQ
Is Gremlin open source? No. Gremlin is a commercial product built by Gremlin Inc. It offers a 30-day free trial with no credit card required, but there is no ongoing free or open-source tier.
Are Chaos Mesh and LitmusChaos really free? Yes, for their core open-source projects. Both are licensed under Apache 2.0 and hosted as CNCF Incubating projects, meaning the software itself carries no license fee — you only pay for the infrastructure you run it on. LitmusChaos’s site also references a separate paid Enterprise offering, but that’s distinct from the free core project.
Do I need Kubernetes to use Chaos Mesh or LitmusChaos? Effectively, yes. Both are built around Kubernetes primitives — Chaos Mesh via Custom Resource Definitions, LitmusChaos via Helm charts and ChaosEngine resources — and are designed to run inside a Kubernetes cluster.
How much does Gremlin actually cost? Gremlin doesn’t publish prices. Its site describes the Gremlin Platform as “priced per service” and Foresight AI as “priced per team,” both requiring a quote request. Any specific dollar figure you see quoted elsewhere is a third-party estimate, not an official number.
What’s the difference between a CNCF “Incubating” and “Graduated” project, and does it matter here? CNCF projects move through Sandbox, Incubating, and Graduated maturity stages as adoption and governance mature. As of this writing, both Chaos Mesh and LitmusChaos are CNCF Incubating projects per their own sites — neither has reached Graduated status yet, which is worth factoring into a long-term tooling bet even though both are already widely used in production.
Sources
gremlin.com/pricing — Gremlin Platform and Foresight AI pricing model, free trial terms
Streaming has pulled enough of the TV audience off linear broadcast that “TV advertising” and “connected TV (CTV) advertising” are converging into one budget line. But buying ad space on a streaming device isn’t like buying a display banner, and the three biggest on-ramps — Roku Ads Manager, Amazon’s DSP (newly folded into Amazon Ads Agent), and YouTube/Google Ads — work in meaningfully different ways. This guide compares how advertisers actually buy on each in late 2026: self-serve versus managed access, what’s known about budgets, targeting depth, and the measurement problems specific to television-sized screens rather than browser tabs.
This is a companion piece to our broader look at DSPs for programmatic advertising (The Trade Desk vs Google DV360 vs Amazon DSP), which covers general-purpose demand-side platforms across every channel. This one narrows in on streaming TV specifically, including the self-serve, platform-native tools a general DSP doesn’t replace.
At a Glance
Platform
Access model
Published minimum spend
Core inventory
Standout targeting
Roku Ads Manager
Self-serve (plus separate managed Programmatic/Brand Studio options)
None published; Action Ads explicitly state “no additional costs or minimums”
The Roku Channel + Roku OS home screen/device inventory
Both: an AI-driven “DVA+” default path and an “advanced settings” toggle for the traditional self-serve/managed DSP experience
None published on advertising.amazon.com; third-party resellers commonly cite $35K–$50K for managed service, unverified by Amazon directly
Prime Video, Twitch, Thursday Night Football, Fire TV, Amazon.com, plus third-party exchanges
Amazon shopping/first-party signals carried into DVA+; Performance+ and Brand+ auto-optimization
YouTube / Google Ads (CTV)
Self-serve via Google Ads; larger/managed buys via Display & Video 360 (DV360)
No published minimum; standard auction-based budgets apply
YouTube on TV screens (smart TVs, set-top boxes, consoles, streaming sticks) plus DV360 CTV exchange inventory
“TV screens” device targeting, Video action campaigns, DV360 audience/category/genre targeting
Short Verdict
None of these three is a strict upgrade over the others — they solve different buying problems. Roku Ads Manager is the easiest on-ramp for a growth marketer who wants to run CTV the way they run paid social, with a self-serve console and no stated minimum. Amazon’s newly rebranded DSP/Ads Agent is the deepest option for brands that already sell on Amazon and want shopping-signal-informed targeting across Prime Video and Fire TV, but it’s mid-transition to an AI-agent interface as of late 2026. YouTube/Google Ads is the default choice for advertisers already running Google/YouTube campaigns who want to extend existing audiences onto the TV screen with minimal new tooling, with DV360 as the upgrade path for more granular CTV controls.
How Each Platform Is Actually Bought
Roku Ads Manager launched as a self-service product aimed specifically at performance marketers who were used to buying search and social but had never touched TV. According to Roku’s own advertiser resources, it lets brands build and launch CTV campaigns — including “Action Ads,” interactive overlays viewers can respond to with their Roku remote — without going through a sales team. A Shopify integration extends this into fully shoppable ads, where a viewer can add an item to cart and check out on the TV screen. Roku states there are “no additional costs or minimums” to get started with Action Ads specifically. Roku also maintains separate “Programmatic solutions” and “Brand Studio” offerings for advertisers who want managed service or custom creative production, though Roku’s public pages don’t spell out exactly how those differ in budget or access from Ads Manager itself.
Amazon’s DSP has historically supported both self-service (advertiser-managed) and managed-service (Amazon-run) access, with managed service typically requiring a larger commitment arranged through an Amazon Ads account executive. That structure changed significantly at Amazon’s unBoxed event on September 29, 2026: Amazon Ads merged its DSP and its sponsored-ads console into one interface, Amazon Ads Agent, with the DSP itself renamed DVA (display, video, audio). The new default path, DVA+, is AI-driven and routes campaigns into either Performance+ (lower-funnel conversions) or Brand+ (video branding and prospecting). Advertisers who want the familiar manual-control experience can still find it behind an “advanced settings” toggle, and a new “Full-Funnel Campaigns” product targets smaller advertisers expanding into streaming TV and audio without channel-specific expertise. Amazon’s own pages don’t publish a minimum spend for DSP/DVA+; figures like $35,000–$50,000 circulate among agencies and resellers, but we couldn’t verify that directly, so treat it as unconfirmed.
YouTube and Google Ads take the most familiar self-serve route for anyone already running search or YouTube video campaigns: CTV is addressed as a device category rather than a separate buying system. Google Ads and DV360 added a “TV screens” device type — covering smart TVs, set-top boxes, gaming consoles, and streaming devices such as Chromecast — letting advertisers adjust bids or creative for the living-room screen specifically, and Video action campaigns have been extended to run there too. For finer control over CTV-specific inventory, audience lists, and deals, DV360’s dedicated Connected TV tools sit one tier up from standard Google Ads.
Targeting: What Each Platform Can Actually Do
Roku: demographics, interests, geography, and streaming or shopping behavior; custom first-party audiences, including excluding existing customers.
Amazon DSP/DVA+: Amazon’s own shopping and streaming signals (Prime Video/Fire TV viewership, purchase and browsing behavior); existing DSP audience segments migrate into DVA+’s advanced mode.
YouTube/Google Ads: device-level TV screens targeting with bid adjustments; DV360 adds Customer Match, third-party audience lists (need a device ad ID like IFA/IDFA/AAID for CTV), category/genre contextual targeting, and demographic targeting Google says is strongest in the U.S. and varies by publisher.
Measurement: Where CTV Gets Genuinely Hard
CTV measurement has structural problems that don’t exist in click-based digital advertising. There’s no click on a TV ad — a viewer can’t tap a 55-inch screen to convert — so every platform infers impact rather than tracking a direct path. Device identifiers (IFAs, IDFAs) differ by manufacturer and app, fragmenting reach and frequency measurement across a household that might see the same ad on a Roku device, a smart TV’s built-in OS, and a game console. Multiple people often watch together on one device, which complicates “unique reach” counts. And because CTV inventory is split across walled gardens (Roku’s own OS, Amazon’s Fire TV and Prime Video, YouTube on TV screens) and third-party exchanges, advertisers rarely get one unified, cross-platform view of frequency or incrementality.
Google is one of the few to publish a controlled study here: a Google/Ipsos lab experiment, cited on Google’s own support pages, found YouTube ads on the TV screen produced an average 47% lift in ad recall and a 35% lift in purchase intent versus a control group — useful directional evidence, though it’s a single vendor-run study rather than independent, cross-platform research. None of the three platforms publishes third-party-audited, apples-to-apples CTV attribution benchmarks, which is the honest state of CTV measurement industry-wide in 2026: better than a black box, still short of the click-level precision marketers got used to on search and social.
Pros and Cons
Roku — Pros: genuinely self-serve, no stated minimum for Action Ads, direct Shopify checkout. Cons: smaller walled-garden inventory than Amazon or YouTube; less public detail on measurement tooling.
Amazon DSP/DVA+ — Pros: unmatched first-party shopping-signal targeting; inventory spans Prime Video, Twitch, live NFL football, and Fire TV. Cons: mid-rebrand uncertainty in late 2026; no published minimum, plus third-party reports of a historically high managed-service threshold.
YouTube/Google Ads — Pros: lowest-friction entry for existing Google/YouTube advertisers; a published lift study backs the format; DV360 adds real CTV-specific controls. Cons: CTV audience/demographic coverage is U.S.-weighted and varies by publisher; combined first-party lists aren’t supported on non-YouTube CTV inventory in DV360.
Who Should Use Which
A DTC or performance team testing CTV for the first time, with a modest budget and no agency, is best served by Roku Ads Manager — built for exactly that self-serve, no-minimum use case. A retail or Amazon-native brand that wants to extend its shopping and browsing audiences onto the big screen should go with Amazon DSP/DVA+, accepting some near-term change-management cost as the interface transitions to its agentic model. A brand already spending heavily in Google Ads or YouTube, especially one wanting a single reporting view across search, video, and TV, should extend into YouTube/Google Ads CTV first and graduate to DV360 for finer-grained targeting or deal-based inventory.
Bottom Line
CTV advertising in 2026 no longer requires a six-figure linear-TV-style commitment to get started — Roku and Google/YouTube both offer genuinely self-serve, low-friction entry points, and even Amazon’s historically higher-touch DSP is being redesigned around a lower-friction, AI-assisted default. The real trade-off isn’t cost of entry anymore; it’s measurement maturity. Pick the platform whose existing audience data and attribution reporting line up with the rest of your stack, and treat published lift or recall studies as directional rather than a substitute for your own incrementality testing.
FAQ
Is there a minimum budget to advertise on Roku, Amazon, or YouTube’s CTV inventory? None of the three publishes a hard minimum on its own advertiser pages as of late 2026. Roku explicitly states no minimum for Action Ads. Amazon and Google don’t state one either, though managed-service tiers (historically on Amazon’s DSP) are commonly reported by agencies to require a larger budget commitment — confirm directly with the platform before assuming a number.
What happened to the Amazon DSP? As of Amazon’s September 29, 2026 unBoxed event, the Amazon DSP was renamed DVA (display, video, audio) and merged with Amazon’s sponsored-ads console into a unified interface called Amazon Ads Agent. The AI-driven DVA+ path is now the default, though an advanced-settings toggle preserves the traditional DSP-style manual experience.
Can I retarget website visitors with CTV ads? Yes, on all three, though the mechanics differ. Roku and Amazon let advertisers upload first-party audience data for custom targeting; Google Ads/DV360 support this via Customer Match and third-party audience lists, though third-party lists need a device ad ID to serve on CTV specifically.
Why not just use a general DSP like The Trade Desk for CTV? Many advertisers do — general-purpose DSPs aggregate CTV inventory across publishers. But platform-native tools give access to first-party inventory, audience signals, and formats (Roku’s Action Ads, Amazon’s shopping signals) a third-party DSP can’t replicate. See our DSP comparison for how general programmatic buying stacks up.
How is CTV measurement different from a web or app ad? There’s no click to track, device IDs fragment across manufacturers and apps, multiple household members often watch on one device, and inventory is split across walled gardens and exchanges — so advertisers rarely get one unified cross-platform frequency or attribution report.
Open almost any relational database’s query planner output and “index” almost always means a B-tree or, more precisely, a B+-tree. That’s not naming coincidence — a structure invented in 1972 for IBM mainframe disks still outperforms most alternatives at the specific job a database index does: keeping billions of sorted keys on block-based storage while answering point lookups and range scans in a handful of I/O operations. This piece is a mechanical deep dive into how B-trees and B+-trees work — node layout, splits, merges, and a worked insertion example — not a storage-engine comparison. For the engine-level trade-off against log-structured merge trees, see our separate LSM Trees vs B-Trees article; this one stays inside the B-tree itself.
At a Glance
Aspect
Detail
What it solves
Keeping sorted keys balanced and searchable on block storage, minimizing I/O per lookup
Core idea
A self-balancing n-ary search tree whose node size matches the storage page size
Search / insert / delete
O(logb n), b in the hundreds — 3-4 reads even for billions of rows
Range scans
O(log n) to find the start, then O(k) across linked leaf nodes
Where it’s used
MySQL InnoDB clustered/secondary indexes, PostgreSQL’s default index type, SQLite, SQL Server, most filesystems
Dominant variant
B+-tree — records live only in linked leaf nodes; internal nodes hold routing keys only
Verdict: the B+-tree is the default on-disk index because it bounds tree height to a handful of levels regardless of table size, handles point and range queries from one structure, and keeps actual data in leaves where sequential access is cheap. It isn’t the best fit for extremely write-heavy workloads, where LSM-trees take over, but for read-heavy and mixed workloads it remains the default for good reason.
The Problem: Searching Sorted Data on Slow Storage
A balanced binary search tree gives O(log2 n) search, but on disk each pointer hop can mean a separate I/O. A binary tree over a billion rows is roughly 30 levels deep — 30 potential random reads for one lookup. B-trees, proposed by Rudolf Bayer and Edward McCreight in 1972, optimize for I/O instead of comparisons: a node holds as many keys and children as fit in one storage page (4-16KB), so each level descended costs exactly one page read, and a branching factor in the hundreds reaches a billion rows in about four levels.
Node Structure and Branching Factor
A B-tree of order m keeps a small set of invariants: every node holds up to m-1 sorted keys; an internal node with k keys has k+1 children; every node except the root stays at least half full (⌈m/2⌉-1 keys), preventing the tree from going sparse and tall; and all leaves sit at the same depth — balance enforced structurally, not by a rebalancing pass like AVL trees use. The order is chosen so one full node fits one page: at 16KB per page and ~20 bytes per key-pointer pair, a node holds 500-800 entries. That choice — size the node to the page — is why B-trees beat binary trees here: tree depth becomes disk reads, and page-sized nodes keep that number tiny.
Insertion and Splitting: A Worked Example
Insertion descends from the root, comparing the new key at each node to pick a child, until it reaches a leaf, then inserts the key in sorted order. If the leaf has room, nothing else changes. If it’s full, it splits, and the split can propagate upward.
Take a one-node, order-4 tree (max 3 keys) that is currently just a full root:
root: [10, 20, 30] (full)
Insert 25. The root overflows to [10, 20, 25, 30]. The split procedure: find the median (25), send everything left of it to a new left node ([10, 20]) and everything right to a new right node ([30]), then move the median key up into a parent — creating a brand-new root, since none existed:
root: [25]
/ \
[10, 20] [30]
The key mechanical insight: a B-tree never grows taller directly. It splits a full node, promotes one key, and only adds a new level when the root itself overflows. Growth happens uniformly from the root down, which is why every leaf always ends up at the same depth. A non-root overflow triggers the identical split one level up, and the promoted key can itself overflow its parent, cascading — rarely — all the way to a new root, but never leaving the tree unbalanced partway through.
Deletion and Merging
Deletion mirrors insertion. Removing a leaf key is trivial if the leaf stays at least half full. If a deletion drops a node below the minimum, the tree first tries to borrow from a sibling that has a key to spare, moving it over through the parent. If no sibling can spare one, it merges the underflowing node with a sibling and pulls the parent’s separating key down into the merge — removing a key from the parent, which can itself underflow and propagate upward, the mirror of a split cascading during insertion. If a merge empties the root, the merged child becomes the new root and the tree shrinks by a level. This symmetry is why B-trees never need an explicit rebalance pass.
Why B+-Trees, Not Plain B-Trees, Run Your Database
A classic B-tree lets any node — internal or leaf — hold a key paired with record data. Databases almost universally use the B+-tree variant instead, with two changes:
Data lives only in leaves. Internal nodes store routing keys only, no record data, so more keys fit per page (shallower tree) and every search walks all the way to a leaf — uniform-cost lookups instead of sometimes stopping early.
Leaves are linked via sibling pointers, so once a range scan finds its starting leaf it just walks sideways instead of re-traversing the tree. That’s an O(log n) descent plus an O(k) linear walk for k results — the mechanism behind cheap BETWEEN and ORDER BY scans.
Both changes target disk-backed indexes specifically: data scattered through internal nodes makes range scans awkward and bloats node size without improving fan-out, while a B+-tree trades a theoretical early-stop for simpler correctness, smaller internal nodes, and cheap ordered iteration — the single most common database access pattern.
How Real Databases Build On This
MySQL InnoDB uses B-tree structures for every index, with one twist for the primary key: InnoDB designates one index as the clustered index (the primary key, or the first NOT NULL UNIQUE index, or a hidden auto-generated row ID), and that index’s leaf pages store the complete row, not a pointer to it. Every other index is a secondary index whose leaf entries hold the indexed column(s) plus a copy of the primary key, so a secondary-index lookup typically costs a second traversal into the clustered index. InnoDB’s default page size is 16KB; ordinary inserts deliberately leave about 1/16 of each page free to absorb future writes (bulk index builds use innodb_fill_factor instead), and InnoDB attempts to merge an underfilled page once its fill drops below MERGE_THRESHOLD (50% by default).
PostgreSQL clusters differently: its B-tree is the default index type, but — unlike InnoDB — the index normally isn’t where row data lives. A leaf page holds pointers (TIDs) into a separate heap table; Postgres doesn’t keep the table physically reordered by the index the way InnoDB does (an explicit, one-time CLUSTER command exists, but writes don’t maintain that order automatically afterward). Per its own source documentation, PostgreSQL’s B-tree access method is “a correct implementation of Lehman and Yao’s high-concurrency B-tree management algorithm,” letting searches and inserts proceed without tree-wide locks; more than 99% of a typical index’s pages are leaves, and since PostgreSQL 13 the engine deduplicates repeated keys by default to shrink indexes on low-cardinality columns.
B+-Tree vs. the Naive Alternatives
Structure
Point lookup
Range scan
Insert/delete
Disk-friendliness
Unsorted heap file
O(n)
O(n)
O(1) append / O(n) delete
Great for writes, terrible for reads
Sorted array
O(log n) compares, O(n) to shift
O(log n + k)
O(n) per insert/delete
Poor — inserts rewrite large regions
Balanced BST (AVL/red-black)
O(log2 n)
O(log2 n + k)
O(log2 n)
Poor — tens of levels, each a potential page fetch
B+-tree
O(logb n), b in the hundreds
O(logb n + k) via linked leaves
O(logb n)
Excellent — node size matches page size
Trade-offs
Pros: shallow, predictable depth at any scale; native support for both point and ordered range queries; self-balancing with no separate rebalance step; decades of production hardening.
Cons: random-order inserts cause splits and leave pages partially empty, bloating the index (why fill-factor/merge-threshold tuning exists); in-place page updates make writes costlier than an LSM-tree’s sequential, buffered writes; internal nodes in a B+-tree duplicate keys that also live in leaves.
When to Use This
Use a B+-tree index — in practice, just your database’s default index type — whenever a workload needs ordered range queries, equality lookups, or sorted iteration, and reads are at least as frequent as writes: primary keys, foreign keys, anything in a frequent WHERE, ORDER BY, or BETWEEN clause. If writes dominate at very high volume (time-series ingestion, event logging), an LSM-tree engine usually fits better — see the LSM Trees vs B-Trees comparison. For in-memory ordered structures with simpler concurrent insert/delete logic, compare against skip lists.
Bottom Line
The B+-tree earns its place as the default relational index because one design decision — sizing nodes to match storage pages — directly minimizes I/O, the actually expensive resource. Keeping data in linked leaf nodes turns both point lookups and range scans into a handful of predictable reads no matter how large the table grows. That mix of guaranteed shallow depth, self-balancing writes, and cheap ordered iteration is why its core mechanics have barely changed in over fifty years.
FAQ
Is a B+-tree the same as a B-tree? No. A B+-tree keeps all record data (or row pointers) in linked leaf nodes and routing-only keys in internal nodes; a plain B-tree can store data in internal nodes and has no leaf-linking requirement. Almost every index you’ll encounter is technically a B+-tree, even when documentation just says “B-tree.”
Why does InnoDB’s clustered index matter for performance? The primary-key tree’s leaves contain the full row, so a primary-key lookup resolves in one traversal. A secondary-index lookup resolves the indexed columns first, then needs a second traversal into the clustered index via the stored primary-key value — why a short primary key keeps secondary indexes smaller and cheaper.
Do B+-trees ever need maintenance? They self-balance on every write, but random-order writes can leave pages partially full. InnoDB (fill factor, merge threshold) and PostgreSQL (fillfactor parameter, REINDEX) both expose tuning to reclaim that wasted space.
Why not just use a hash index for equality lookups? A hash index can beat a B+-tree on pure equality lookups, but hashing destroys key order, so it can’t support range scans or prefix matching — a large share of real queries. That’s why B+-tree is the default and hash indexes are a specialized option (PostgreSQL offers a native hash index type; InnoDB uses hashing only internally, as an adaptive cache in front of its B-trees).
Retrieval-augmented generation (RAG) is the pattern that lets an LLM answer questions using your documents instead of (or in addition to) whatever it memorized during training: you retrieve relevant chunks from an index, stuff them into the prompt, and let the model generate a grounded answer. Three open-source frameworks dominate how developers actually build this in 2026: LangChain, LlamaIndex, and Haystack. They overlap heavily, but they were built with different centers of gravity — and that shows up in how painless each one makes a RAG pipeline versus a general agent. This is a RAG-specific comparison. If you’re choosing a framework for autonomous multi-step agents rather than document retrieval, see our separate comparison of LangGraph, CrewAI, and AutoGen. And if you want the mechanics of how the vector search underneath any of these three actually works, we cover that in our explainer on vector databases and ANN search.
At a Glance
Framework
License
Open Source
Best For
LangChain
MIT
Yes
General-purpose chain and agent orchestration, with RAG as one capability among many; best if you’ll also need tool-calling agents, not just retrieval
LlamaIndex
MIT
Yes
Data-centric, retrieval-first applications where ingesting, indexing, and querying your own documents is the primary job
Haystack
Apache 2.0
Yes
Production NLP/RAG pipelines built by deepset, with an emphasis on modular, serializable pipelines for deployment at scale
Short Verdict
All three are solid, genuinely open-source choices, and the “right” one depends on what your RAG pipeline needs to do beyond retrieval. LlamaIndex is the most retrieval-native of the three — its APIs are built around getting documents in and answers out, with layered high-level and low-level interfaces for customizing the retrieval step. LangChain is the most general-purpose: it treats RAG as one tool an agent can reach for, built on top of LangGraph for orchestration, which makes sense if your end goal is an agent that sometimes retrieves and sometimes does other things. Haystack sits closest to a production-engineering mindset, with serializable, modular pipelines, Kubernetes support, and hybrid retrieval with self-correction loops baked in — a good fit if you’re deploying a RAG system as a long-lived service rather than prototyping an app.
What Each One Is Optimized For
LangChain: Agent and Chain Orchestration First, RAG Included
LangChain’s own documentation frames the framework around `create_agent`, described as “a minimal, highly configurable harness” for composing a model, tools, a prompt, and middleware. Agents built this way run on LangGraph underneath, which provides durable execution, human-in-the-loop support, and persistence. RAG in LangChain is implemented as retrievers and vector store integrations that an agent (or a simpler chain) can call as a tool, rather than being the framework’s sole purpose. That said, LangChain’s retriever and vector-store abstractions are extensive: its current integrations list includes Pinecone, Chroma, Qdrant, Weaviate, Milvus, PGVector, Redis, Elasticsearch, Astra DB, Azure Cosmos DB, Google AlloyDB, FAISS, Neo4j, and dozens more, which makes swapping the underlying store a low-friction decision.
LlamaIndex: Data Indexing and Retrieval First
LlamaIndex describes itself as a framework for building LLM-powered agents and applications “over your own data,” and its documentation is explicit that the framework is built around getting external data into a model at answer time — RAG is its best-known pattern, though the docs now present it as one tool an agent can call rather than the only thing the framework does. Its core primitives are data connectors, indexes, vector stores, and query/chat engines, offered through both a high-level API (documents to answers in a few lines) and a lower-level API for customizing or replacing individual components. For messy source documents, LlamaIndex’s companion product LlamaParse handles complex parsing — scanned PDFs, tables, embedded charts — and feeds parsed output straight into an index. Its documented vector store integrations include Pinecone, Qdrant, Chroma, Weaviate, Milvus, Elasticsearch, and multiple pgvector-based options.
Haystack: Production Pipelines by deepset
Haystack is maintained by deepset GmbH and is described on its own site as “Open Source AI framework for building production-ready, LLM-powered agents and applications,” built around modular components, serializable pipelines, and Kubernetes support for production deployment. Its RAG capabilities are explicitly called out as “Advanced RAG,” including hybrid retrieval and self-correction loops, alongside standardized tool calling for agents and support for multimodal tasks like image processing and audio transcription. Haystack’s document-store integration list is the broadest of the three by raw count: dedicated vector databases (Pinecone, Qdrant, Weaviate, Chroma, Milvus, LanceDB, FAISS, Vespa, Upstash Vector, Amazon S3 Vectors), relational stores with vector support (pgvector, Supabase, AlloyDB, MariaDB, Oracle AI Vector Search, SingleStore), search engines (Elasticsearch, OpenSearch, Solr, Azure AI Search), and several cloud/NoSQL databases (AstraDB, DynamoDB, Azure CosmosDB, MongoDB, Neo4j, and others).
Licensing and Paid Hosted Offerings
Framework
Core License
GitHub Stars (approx.)
Paid Hosted Offering
LangChain
MIT
~149k (langchain-ai/langchain)
LangSmith (observability/evals, free dev tier then $39/seat/mo+) and LangGraph Platform (agent deployment, bundled into LangSmith’s Plus/Enterprise plans)
LlamaIndex
MIT
Widely used; exact star count not independently verified here
LlamaCloud (LlamaParse document parsing/extraction plus a hosted indexing pipeline), free tier of 10,000 credits/month (roughly 1,000 pages), paid tiers beyond that
Haystack
Apache 2.0
~27k (deepset-ai/haystack)
Haystack Enterprise Platform (formerly marketed as deepset Cloud) — cloud or self-hosted deployment, governance/RBAC/audit logging, visual pipeline design, and Forward Deployed Engineer support; also a lighter “Haystack Enterprise Starter” tier
All three frameworks themselves are free and unrestricted open source — none of them gate core RAG functionality behind a license key the way some observability tools do. The commercial products are additive layers: managed deployment, document processing at scale, governance, and support, not a different version of the open-source library. Worth noting precisely: we could not independently verify LlamaIndex’s exact current GitHub star count from its own site in this research pass, so that cell is left general rather than guessed.
Pros and Cons
LangChain
Enormous ecosystem and integration surface — dozens of vector stores, model providers, and tool integrations
Natural fit if your RAG app will grow into a multi-step agent that does more than retrieve-and-answer
LangGraph underneath gives durable execution and human-in-the-loop for free
More moving parts than you need if all you want is straightforward document retrieval
Abstractions have changed significantly across versions, which can mean migration friction on older tutorials and codebases
RAG-specific documentation is spread across a broader agent-first framework rather than presented as a first-class use case
LlamaIndex
Purpose-built abstractions for indexing and querying data, with a genuinely simple high-level API for basic RAG
LlamaParse handles messy real-world documents (scans, tables, charts) better than generic text loaders
Layered API means you can start simple and drop down to custom retrieval logic without switching frameworks
Less natural than LangChain if your end goal is a complex multi-tool agent rather than a data-grounded Q&A system
LlamaCloud’s free tier (10,000 credits/month, ~1,000 pages) is modest for large document sets
Smaller model-provider integration surface than LangChain in some areas, though vector store coverage is comparable
Haystack
Apache 2.0 licensing is unambiguous and permissive, with no separate enterprise-edition carve-out inside the open-source repo
Broadest documented list of document-store/vector-database integrations among the three
Built with production deployment (Kubernetes, serializable pipelines, logging/monitoring) as a first-class concern, not an afterthought
Smaller community and ecosystem than LangChain, meaning fewer third-party tutorials and templates
Pipeline-based mental model has a steeper initial learning curve than LlamaIndex’s “few lines to a working RAG app” approach
The enterprise platform rebrand (deepset Cloud → Haystack Enterprise Platform) means older articles referencing “deepset Cloud” may describe outdated branding
Who It’s a Good Fit For
LangChain fits teams building an agent that needs retrieval as one capability among several (web search, code execution, other tool calls), or teams already invested in the LangChain/LangGraph/LangSmith ecosystem who want RAG without adopting a second framework.
LlamaIndex fits teams whose primary problem is “how do we get an LLM to answer questions accurately from our documents,” especially when those documents are messy (PDFs, tables, scanned files) and parsing quality matters as much as the retrieval algorithm.
Haystack fits teams, especially ones with existing NLP/MLOps practices, who are deploying a RAG pipeline as a durable production service and want modular, inspectable, Kubernetes-friendly pipelines plus an enterprise support path if they need it later.
Who Should Look Elsewhere
If you need a fully autonomous multi-agent system with complex role delegation rather than retrieval-grounded Q&A, none of these three is the primary tool for the job — see our LangGraph vs. CrewAI vs. AutoGen comparison instead, since RAG frameworks assume retrieval is central and agent orchestration is secondary (or absent). If your team has no NLP/ML engineering experience and just wants a no-code RAG chatbot over a handful of PDFs, a hosted no-code platform may get you there faster than adopting any of these three open-source libraries directly.
Code Example: Minimal RAG Query Engine in LlamaIndex
LlamaIndex’s high-level API gets you from a folder of documents to a queryable RAG pipeline in a handful of lines:
from llama_index.core import VectorStoreIndex, SimpleDirectoryReader
# Load documents from a local folder
documents = SimpleDirectoryReader("./data").load_data()
# Build an in-memory vector index over the documents
index = VectorStoreIndex.from_documents(documents)
# Create a query engine and ask a question grounded in your data
query_engine = index.as_query_engine()
response = query_engine.query("What does the Q3 report say about churn?")
print(response)
The Bottom Line
LangChain, LlamaIndex, and Haystack are all permissively licensed, actively maintained, and genuinely capable of building a solid RAG pipeline — the differences are about where each one puts its center of gravity. LangChain is agent-first with RAG as a tool. LlamaIndex is data-and-retrieval-first with agents as an extension. Haystack is production-pipeline-first, built by an NLP company that cares about what happens after your RAG system ships. None of them require a commercial license to use fully; the paid products (LangSmith/LangGraph Platform, LlamaCloud, Haystack Enterprise Platform) all sit on top as optional managed services, not gated versions of the open-source core.
FAQ
Are LangChain, LlamaIndex, and Haystack all free to use commercially?
Yes. LangChain and LlamaIndex are both MIT licensed, and Haystack is Apache 2.0 licensed — all three are permissive open-source licenses that allow commercial use without royalties or a required license purchase. The paid products each vendor sells (LangSmith, LlamaCloud, Haystack Enterprise Platform) are optional hosted/managed add-ons, not different licensing terms on the core framework.
Can I use LangChain and LlamaIndex together?
Yes, and plenty of teams do — for example, using LlamaIndex for document parsing and indexing, then handing retrieved context into a LangChain/LangGraph agent for the rest of the orchestration. They are not mutually exclusive, since both expose standard retriever interfaces.
Which framework is easiest for a first RAG prototype?
Based on each framework’s own documentation, LlamaIndex’s high-level API is explicitly designed to get from documents to answers “in a few lines,” which makes it the fastest on-ramp for a first prototype. LangChain and Haystack both require slightly more setup (chains/agents in LangChain, pipeline definitions in Haystack) before you get a working retrieval loop.
Is deepset Cloud still a thing, or has it been replaced?
As of this research, deepset’s own site markets its commercial hosted/managed offering as the “Haystack Enterprise Platform” (with a lighter “Haystack Enterprise Starter” tier), rather than using the “deepset Cloud” name. If you see “deepset Cloud” referenced elsewhere, treat it as the predecessor branding for what is now sold as the Haystack Enterprise Platform.
Do any of these frameworks require a specific vector database?
No. All three are vector-database agnostic and document dozens of supported stores — Pinecone, Chroma, Qdrant, Weaviate, Milvus, pgvector-based options, Elasticsearch, and more appear across all three frameworks’ integration lists. For background on how the underlying search algorithms (like HNSW and IVF) actually work, see our vector databases and ANN search explainer.
AI training and inference pipelines live or die on how fast and how cheaply a query engine can scan petabytes of data. For years, that meant data teams hand-managed Apache Iceberg or Hudi tables on top of raw S3 buckets, running their own compaction and metadata-cleanup jobs. Amazon S3 Tables, which AWS announced as a fully managed Apache Iceberg offering built directly into S3, is AWS’s bet that open table formats — not proprietary warehouse formats — are the right foundation for AI-scale data lakes, and that managing the operational overhead of those tables is a service AWS should sell rather than a chore customers should own.
At a Glance
Attribute
Detail
What it is
A fully managed Apache Iceberg table service built into Amazon S3, using a new bucket type called a “table bucket”
Who it’s for
Data engineering and analytics teams running large-scale, high-ingest data lakes queried by multiple engines (Athena, EMR, Redshift, Spark) — including AI training and feature-pipeline workloads
Launched
Announced December 3, 2024; regional availability and Glue Data Catalog integration have expanded through 2025–2026 (initially US East N. Virginia, US East Ohio, US West Oregon, “more Regions coming soon”)
Pricing model
Pay-as-you-go: per-GB storage, per-1,000-request charges, plus S3 Tables–specific object monitoring and compaction fees not present on general purpose S3 buckets
Performance claim
AWS states S3 Tables can deliver up to 3x faster query throughput and support up to 10x more transactions per second than tables customers manage themselves on S3
The Verdict
S3 Tables is a sound, if narrow, piece of infrastructure: it takes a specific, well-understood pain point — the constant background maintenance that open table formats like Iceberg require (compaction, snapshot expiration, orphan-file cleanup) — and turns it into a managed service with its own line-item pricing. It’s not a new query engine or a new storage class so much as an operations layer bolted onto S3 specifically for tabular analytics data, which makes it a genuinely useful default for teams already committed to Iceberg, and a non-event for anyone storing unstructured objects, media, or backups.
What It Is
According to AWS’s own December 2024 announcement, Amazon S3 Tables are “fully managed Apache Iceberg tables optimized for analytics workloads” — and AWS describes the launch as the first time a cloud object store has shipped with built-in Apache Iceberg support. The core new concept is the table bucket, a distinct S3 bucket type purpose-built for tabular data rather than arbitrary objects. Table buckets support:
Fast table creation, without manually wiring up a separate catalog and storage layer
Table-level permissions, so access control can be scoped to a specific table rather than only a bucket or prefix
Continuous, policy-driven maintenance — automatic compaction of small files into larger ones, snapshot management, and removal of unreferenced files as data changes over time
Because the tables speak the Apache Iceberg open standard — including row-level transactions, queryable historical snapshots, and schema evolution without rewriting data — any Iceberg-compatible engine, from AWS-native services to third-party tools like Apache Spark or Trino, can read and write them. AWS says this managed maintenance is what produces the throughput and transaction-rate gains over self-managed Iceberg-on-S3 setups.
How It Differs From a Regular S3 Bucket
A general purpose S3 bucket stores objects — files, images, logs, model checkpoints — with no inherent concept of rows, schemas, or transactions. If you wanted an Iceberg table on a general purpose bucket before S3 Tables existed, you (or a tool like a Glue job or an open-source compaction utility) had to run the housekeeping yourself: periodically rewriting small files into larger ones, expiring old snapshots, and deleting orphaned data files so storage costs and query latency didn’t creep up as the table grew. A table bucket does that maintenance automatically and bills for it as a distinct, metered service, while also exposing table-level (not just object- or prefix-level) permissions. In short: a general purpose bucket is a filesystem-like object store; a table bucket is a managed database-like layer for structured, transactional data sitting on the same underlying S3 durability guarantees.
Integration With Glue, Athena, EMR, and Other Engines
AWS’s announcement names Amazon Data Firehose, Athena, Redshift, EMR, and QuickSight as services that can stream, query, and visualize data in S3 Tables. The connective tissue is the AWS Glue Data Catalog, which AWS has continued building out — including a 2026 preview enabling Glue Data Catalog metadata exports to S3 Tables and simplified permissions for S3 Tables and Iceberg materialized views. Practically, this means a team can write Iceberg tables once into an S3 table bucket and then query the same data from Athena for ad hoc SQL, from EMR or Spark for large-scale ETL and feature engineering, and from Redshift for BI — without copying the data into each engine’s own storage format. For AI pipelines specifically, this matters because training and evaluation datasets are frequently assembled by joining and filtering large fact tables across many sources; having one Iceberg-native copy that every engine can read consistently (with the same snapshot and schema state) avoids the classic data-lake problem of multiple, slightly inconsistent copies drifting out of sync.
Pricing and Economics
Pricing comes directly from AWS’s S3 pricing page, which breaks S3 Tables charges into several distinct line items beyond standard storage and request fees:
Charge
Rate (as published)
Standard storage (first 50 TB/month)
$0.0265 per GB (AWS’s own example; example region US West Oregon)
PUT requests
$0.005 per 1,000 requests
GET requests
$0.0004 per 1,000 requests
Object monitoring
$0.025 per 1,000 objects
Compaction (objects processed)
$0.002 per 1,000 objects
Compaction (data processed)
$0.005 per GB
Migration (existing Iceberg/Hive tables)
$0.005 per 1,000 PUT requests + $0.002 per 1,000 source objects per sync (first 500 syncs within 3 months are free)
Cross-Region replication
$0.005 per 1,000 PUT requests + $0.010 per 1,000 table updates + standard inter-Region data transfer rates
AWS’s own worked example — a 1 TB table with a 100 MB average object size in US West (Oregon) — comes to roughly $28.54 per month: about $27.14 in storage, $0.15 in PUT requests, $0.20 in GET requests, $0.26 in object monitoring, and $0.79 combined for compaction. Compaction runs by default unless disabled, so budgeting should assume it’s on. Replication is not available in AWS GovCloud (US) Regions. AWS’s pricing page notes that compaction costs themselves dropped by up to 90% as of a July 2025 update, which matters because compaction — not raw storage — is often the line item that surprises teams with high-ingest, small-file workloads typical of streaming AI feature pipelines.
One caveat worth flagging explicitly: AWS’s public pricing page does not display a clean side-by-side per-GB rate for general purpose S3 Standard storage next to the S3 Tables rate on the same page view, so a precise “S3 Tables costs X% more than a plain bucket” comparison can’t be stated with certainty from the publicly fetched content alone — the extra cost comes specifically from the added object monitoring and compaction fees layered on top of otherwise standard storage and request pricing, not from a materially different base storage rate.
Why This Matters for AI Training and Inference Pipelines
Modern AI workloads — especially large-scale training set construction, feature stores, and retrieval pipelines for retrieval-augmented generation — depend on being able to version, filter, and incrementally update enormous tabular datasets without re-copying everything on every change. Apache Iceberg’s row-level transactions and snapshot model let a pipeline add a day’s new training examples, correct a labeling error, or roll back a bad ingest, all while multiple query engines read a consistent view of the data. Doing this maintenance by hand at scale — compacting millions of small Parquet files produced by streaming ingestion, for instance — is exactly the kind of undifferentiated operational work that becomes a bottleneck as data volume grows. By managing that maintenance as a billed service, AWS is explicitly targeting the operational overhead that sits between “we have the raw data in S3” and “every team’s query engine can efficiently read a governed, up-to-date version of it” — a gap that matters more, not less, as AI data pipelines scale. This storage-layer investment sits alongside AWS’s compute-side AI infrastructure bets, such as the custom Trainium and Inferentia AI chips and the Nitro-based networking stack that feeds data to large GPU and accelerator clusters — a well-governed, consistently updated Iceberg data lake is only useful for AI if the compute layer reading it can keep up.
Pros
Removes manual Iceberg maintenance (compaction, snapshot expiry, orphan-file cleanup) as an engineering burden
Open Iceberg standard means no lock-in to a single AWS query engine — Spark, Trino, and other third-party tools can read the same tables
Table-level permissions give finer-grained access control than bucket- or prefix-level policies alone
AWS reports meaningful throughput and transaction-rate gains over self-managed Iceberg-on-S3 setups
Compaction costs have already been reduced once (up to 90%, per AWS’s July 2025 update), suggesting ongoing cost optimization
Cons
Adds distinct billing line items (object monitoring, compaction) that a plain S3 bucket doesn’t incur
Only useful for tabular, Iceberg-structured data — irrelevant for unstructured objects, media, or general file storage
Regional availability, while expanding, was limited to three US Regions at launch; teams needing other Regions should check current coverage before committing
Glue Data Catalog integration for streaming exports has moved through preview status, meaning parts of the integration surface are still maturing
AWS does not publish a direct side-by-side comparison of S3 Tables storage pricing versus plain S3 Standard storage on the same page, making exact incremental cost estimation harder without a real workload test
Who It’s a Good Fit For
Data engineering teams already standardized on Apache Iceberg, or actively migrating from Hive-style tables, who want AWS to own ongoing table maintenance rather than running their own compaction jobs. It’s a particularly strong fit for high-ingest streaming pipelines (common in AI feature stores and training-data assembly) where small-file proliferation would otherwise require constant manual cleanup, and for organizations that query the same dataset from multiple engines (Athena, EMR/Spark, Redshift) and want one consistent, governed copy.
Who Should Look Elsewhere
Teams storing primarily unstructured data — images, video, model checkpoints, logs, backups — get no benefit from S3 Tables and should stick with general purpose S3 buckets and appropriate storage classes. Organizations already heavily invested in a different open table format’s managed tooling (or a proprietary warehouse that already handles these problems well, like a fully managed Snowflake or BigQuery deployment) may not see enough incremental value to justify re-architecting around S3 Tables specifically, especially while some AWS integrations remain in preview.
The Bottom Line
S3 Tables is AWS formalizing something many data teams were already doing manually — running Apache Iceberg on top of S3 — and selling the maintenance work as a managed, metered service. The pricing is transparent and published directly on AWS’s own pricing page, which is more than can be said for some competing agentic AI pricing models; the trade-off is a handful of new, workload-dependent charges (object monitoring and compaction) on top of otherwise-standard S3 storage and request pricing. For AI-scale data lakes where multiple engines need a consistent, transactionally-correct view of constantly updated tabular data, that trade generally looks worthwhile. For everything else S3 already does well, it’s simply not the right tool.
FAQ
Do I need to migrate all my data to use S3 Tables? No. S3 Tables use a new “table bucket” type specifically for tabular Iceberg data; existing general purpose S3 buckets with unstructured objects are unaffected and can continue as before. AWS also offers a migration path for existing Iceberg or Hive tables into S3 Tables, billed per PUT request and per source object synced, with the first 500 syncs within three months free.
Which query engines can read S3 Tables? Any engine that supports the Apache Iceberg open standard, including AWS services like Athena, Redshift, and EMR, plus third-party tools such as Apache Spark and Trino, via the AWS Glue Data Catalog integration.
Is compaction mandatory, and does it cost extra? Compaction runs by default and is billed separately — $0.002 per 1,000 objects processed plus $0.005 per GB processed, per AWS’s pricing page — though AWS reduced these costs by up to 90% in a July 2025 update.
How is this different from just running Iceberg myself on a regular S3 bucket? You still can — Iceberg is an open format and doesn’t require S3 Tables. The difference is that S3 Tables automates the ongoing maintenance (compaction, snapshot management, orphan-file removal) and adds table-level permissions and faster table creation, as a billed managed service, instead of you running and monitoring that maintenance yourself.
Is S3 Tables available in all AWS Regions? Not initially — it launched in US East (N. Virginia), US East (Ohio), and US West (Oregon), with AWS stating more Regions would follow. Check AWS’s current documentation for up-to-date regional availability before planning a deployment.
If you are running LLM applications in production, you have probably hit the same wall every team hits: it works great in a notebook, and then it goes sideways in the wild and you have no idea why. Was it the prompt? The retrieved context? A model regression? A flaky tool call three steps into an agent trajectory? LLM observability and evaluation platforms exist to answer that question by capturing every call, every chain, and every score so you can debug, test, and monitor like you would any other production system. This guide compares the three platforms developers reach for most in 2026 — LangSmith, Langfuse, and Arize — on pricing, features, and open-source status, using only what each vendor states on its own site as of November 2026.
At a Glance
Tool
Starting Price
Open Source
Best For
LangSmith
Free (Developer plan), then $39/seat/mo on Plus plus usage
No (closed-source product; self-hosted deployment available on Enterprise)
Teams already building with LangChain or LangGraph who want tracing, evals, and prompt tooling in one place
Langfuse
Free (Hobby plan, 50k units/mo), $29/mo Core, $199/mo Pro
Yes — MIT licensed core, self-hostable with no feature gates
Teams that want a fully open-source, self-hostable observability stack with no vendor lock-in
Arize (AX)
Free (AX Free, 25k spans/mo), $50/mo AX Pro
Partially — the underlying Phoenix project is source-available (Elastic License 2.0), free to self-host; Arize AX itself is a closed commercial SaaS/self-hosted product
Teams that want enterprise-grade ML + LLM observability with deep evaluation tooling and an open-source on-ramp via Phoenix
Short Verdict
There isn’t a single winner here — the right pick depends on what you’re already using and how much you care about owning your data. If your stack is built on LangChain or LangGraph, LangSmith’s tracing and evaluation tooling is the path of least resistance, and its free Developer tier covers small projects. If you want an observability layer that is genuinely open source end to end, with no asterisks on the core feature set, Langfuse’s MIT-licensed self-hosted option is the standout — you can run it yourself with unlimited volume and never touch a credit card. If you need the most mature evaluation and monitoring tooling for mixed ML/LLM workloads, or you want a free, no-feature-gated local tracing tool to start with before deciding on a vendor, Arize’s combination of AX (hosted) and Phoenix (self-hosted, source-available) is worth a serious look.
What They Are
LangSmith
LangSmith is LangChain’s observability and evaluation platform, built to trace LLM calls and agent trajectories, run online and offline evaluations, manage prompts, and monitor production usage. It works with LangChain and LangGraph natively but also accepts traces from any framework via OpenTelemetry or its SDKs (Python, TypeScript, Go, Java). Its feature set spans step-by-step tracing with message threading for multi-turn chats, real-time dashboards with cost and latency tracking, LLM-as-judge and code-based online/offline evaluators, dataset and experiment management, and automatic clustering of traces to surface failure patterns. LangSmith is not open source, but LangChain offers managed cloud, bring-your-own-cloud, and self-hosted deployment options for it, and a purpose-built trace database called SmithDB can also be self-hosted inside your own VPC.
Langfuse
Langfuse is an open-source LLM engineering platform covering tracing, prompt management, evaluation, and datasets. Its core is MIT licensed, and according to Langfuse’s own open-source documentation, everything outside the project’s `/ee` (Enterprise Edition) folders — including tracing, evaluations, prompt management, experiments, annotation, and the playground — is MIT licensed and self-hostable with no usage limits. The Enterprise Edition modules (SCIM, extended audit logging, data retention policies) ship as source code too, but require a commercial license key to activate; they’re bundled automatically into Langfuse Cloud. You can self-host via Docker Compose, Kubernetes (Helm charts), or Terraform on AWS, GCP, and Azure, or use the hosted Langfuse Cloud for a managed experience.
Arize (AX and Phoenix)
Arize’s structure is two-layered. Phoenix is Arize’s open(-ish) source tracing, evaluation, experimentation, and prompt-iteration tool — Arize describes it as “fully open-source, free to self-host” with no feature gates, though it’s released under the Elastic License 2.0 (ELv2), a source-available license that is not OSI-approved open source (it restricts, for example, offering Phoenix itself as a competing hosted service). Arize AX is the commercial product built on top: a SaaS (or self-hosted, on Enterprise) platform for OpenTelemetry-compliant tracing, cost/latency/token tracking, multimodal tracing (image, voice, PDF), online/offline evaluations, and unlimited datasets, experiments, and prompts across every paid and free tier.
Pricing and Licensing Breakdown
Platform
Free Tier
Entry Paid Tier
Mid Tier
Enterprise
LangSmith
Developer: $0/seat, up to 5,000 base traces/mo included (pay-as-you-go beyond that), 14-day base trace retention, 1 seat
Plus: $39/seat/mo, up to 10,000 base traces/mo included then pay-as-you-go, unlimited seats at $39 each, access to Agent Server/Engine
— (Plus scales with usage)
Custom pricing, self-hosted/hybrid deployment, custom SSO, support SLA
Langfuse
Hobby: free, no credit card, 50,000 units/mo, 30-day data access, 2 users, 1,000 req/min ingestion
AX Enterprise: custom pricing, unlimited spans, custom retention, SaaS or self-hosted. Phoenix (OSS core) is free to self-host under ELv2 with no volume limits.
A few things worth flagging precisely rather than guessing at: LangSmith’s pricing page does not define what counts as a “unit” the way Langfuse does, and it doesn’t publish a price for upgrading base traces to extended (180-day) retention — that’s quoted case by case. Langfuse’s pricing page similarly does not break “units” down into separate trace/event/observation counts; it’s a single blended ingestion allowance per tier. Arize’s page states span and ingestion limits but does not publish a separate “event” limit, so span volume is the most direct apples-to-apples number available. Where a vendor’s own page didn’t give a number, we left it out rather than estimate.
Pros and Cons
LangSmith
Deepest native integration with LangChain and LangGraph agent tracing
Online and offline evaluators, LLM-as-judge, datasets with automatic versioning, and a playground in one product
Flexible deployment: managed cloud, BYOC, or self-hosted (Enterprise)
Not open source — you can’t inspect or modify the core product
Free tier is capped at a modest 5,000 base traces/month with pay-as-you-go overage beyond that
Full feature set and self-hosting both sit behind paid or Enterprise tiers
Langfuse
MIT-licensed core with no feature gates on self-hosted tracing, evals, prompts, datasets, or the playground
Generous free Hobby cloud tier (50k units/month) with no credit card required
Framework-agnostic: SDKs, OpenTelemetry, and API ingestion work regardless of what you build with
Self-hosting still requires you to run and maintain the infrastructure (Postgres, ClickHouse, Redis, etc.)
Enterprise-only features (SCIM, extended audit logs, retention policies) require a commercial license even if self-hosting
Cloud tiers jump sharply in price from Core ($29) to Pro ($199) to Enterprise ($2,499)
Arize (AX / Phoenix)
Phoenix gives you a genuinely free, locally runnable tracing and eval tool with no feature gates to start
Unlimited users, evaluations, datasets, experiments, and prompts on every AX tier, including Free
Strong roots in ML observability mean mature evaluation and drift-style tooling, not just LLM tracing bolted on
Phoenix’s Elastic License 2.0 is source-available, not an OSI-approved open-source license — read the terms before assuming “open source” means what it does for Langfuse
AX Free and Pro tiers are capped at relatively low span volumes (25k and 50k/month) with short retention (15 and 30 days)
Custom code evaluators are unavailable on Free and Pro tiers per Arize’s own pricing page
Who It’s a Good Fit For
LangSmith fits teams already standardized on LangChain or LangGraph who want tracing, evals, and prompt management without integrating a separate vendor, and who are comfortable paying for traces beyond a small free allowance.
Langfuse fits teams that want full control and the option to self-host without ever hitting a paywall on core functionality — startups cost-conscious about trace volume, regulated teams that need data to stay in-house, and anyone framework-agnostic across LangChain, LlamaIndex, raw API calls, or custom agents.
Arize fits teams that already run ML observability workloads and want LLM tracing in the same place, or anyone who wants to try Phoenix locally for free before committing to a hosted evaluation platform.
Who Should Look Elsewhere
If you need the entire stack — including every enterprise feature — to be free and open source with no commercial license anywhere in the picture, Langfuse’s EE-gated modules and Arize’s ELv2-licensed Phoenix both mean reading the fine print before you build critical infrastructure on the assumption everything is unrestricted. If you need very high trace volumes on a tight budget, compare the per-unit overage costs carefully: Langfuse publishes an $8-per-100k-units overage rate, while LangSmith and Arize price additional volume on request or via a usage calculator.
Code Example: Minimal LangSmith Tracing
Enabling LangSmith tracing for any LangChain run is largely a matter of setting environment variables — no code changes to your chain are required:
import os
os.environ["LANGSMITH_TRACING"] = "true"
os.environ["LANGSMITH_API_KEY"] = "ls_your_key_here"
os.environ["LANGSMITH_PROJECT"] = "my-rag-app"
from langchain_openai import ChatOpenAI
llm = ChatOpenAI(model="gpt-4o-mini")
response = llm.invoke("Summarize the benefits of LLM tracing in two sentences.")
print(response.content)
The Bottom Line
All three platforms solve the same core problem — making opaque LLM behavior inspectable and testable — but they draw the line between “free,” “open,” and “enterprise” in different places. LangSmith trades openness for the tightest LangChain/LangGraph integration. Langfuse trades a steeper jump between paid cloud tiers for a core product you can run yourself forever under MIT. Arize trades a source-available (not fully open-source) license on Phoenix for one of the more mature evaluation toolsets, especially if you’re coming from an ML observability background. Start by asking which constraint matters most to your team — framework lock-in, data residency, or evaluation depth — and let that decide, rather than picking on name recognition alone.
FAQ
Is Langfuse really free to self-host with no limits?
According to Langfuse’s own open-source documentation, yes for the MIT-licensed core: tracing, evaluations, prompt management, experiments, annotation, and the playground are included with no usage caps when you run it yourself. Only the separate Enterprise Edition modules (SCIM, extended audit logging, data retention policies) require a commercial license key, and those are optional add-ons, not part of the base product.
Is Arize Phoenix open source?
Arize markets Phoenix as “fully open-source, free to self-host,” and it is free with no feature gates, but it ships under the Elastic License 2.0, which is a source-available license rather than an OSI-approved open-source license. In practice that mostly affects whether a third party can resell Phoenix as a competing hosted service — it doesn’t change your ability to self-host and use every feature for free.
Can I use LangSmith without using LangChain or LangGraph?
Yes. LangSmith accepts traces from any framework through its SDKs (Python, TypeScript, Go, Java) or via standard OpenTelemetry, though its deepest integrations — automatic tracing of chains, graphs, and tool calls — are built around LangChain and LangGraph.
What exactly counts toward a free-tier limit on each platform?
This differs by vendor and the vendors are not fully consistent in their terminology. LangSmith counts “base traces” (5,000/month free on Developer). Langfuse counts a blended “units” metric (50,000/month free on Hobby) that isn’t broken out into separate trace/event/observation counts on its pricing page. Arize AX counts “trace spans” (25,000/month free on AX Free) plus a separate 1 GB ingestion cap. Always check a vendor’s current usage/billing docs before assuming your workload fits a free tier.
Which one is easiest to switch away from later?
Because Langfuse ingests traces via OpenTelemetry and framework-agnostic SDKs and is MIT licensed end to end for the core, it carries the least lock-in risk — you can self-host, export your data, or migrate without a vendor relationship standing in the way. LangSmith and Arize AX are both closed-source commercial products, though both also support OpenTelemetry ingestion, which keeps your instrumentation code portable even if the backend isn’t.
Most of Nvidia’s recent news cycle has been about the data center: the Blackwell and GB300 GPU architecture, the Vera Rubin platform that follows it, the Spectrum-X and BlueField networking stack tying racks together, and the NIM/Triton software layer that locks developers into Nvidia’s inference tooling. All of that is about training and running AI models inside a data center. Nvidia’s other, less-discussed bet is about getting AI out of the data center entirely and into machines that move through the physical world — robots, autonomous vehicles, and industrial equipment. That bet has three named pieces: Jetson Thor, the compute module that goes inside the robot; Omniverse, the simulation platform that trains and tests it before it touches anything real; and Cosmos, the family of “world foundation models” that generate synthetic training data and reason about physical scenes. This article covers that stack on its own terms, separate from Nvidia’s data-center chip and networking business.
At a Glance
Attribute
Detail
What it is
Nvidia’s “physical AI” stack for robotics and autonomous systems: edge compute (Jetson Thor), simulation (Omniverse), and world foundation models (Cosmos)
Jetson Thor hardware
Jetson T5000 module: Blackwell GPU (2,560 cores), 14-core Arm CPU, 128GB memory, up to 2,070 sparse FP4 TFLOPS, 40–130W power envelope
Omniverse
OpenUSD-based simulation platform with RTX rendering, GPU physics, and sensor simulation for digital twins and robot training environments
Cosmos models
Cosmos 3 Super (64B params), Nano (16B), and Edge (4B) — world foundation models for reasoning, simulation, and synthetic data generation
Who it’s for
Humanoid and mobile robot builders, autonomous vehicle developers, industrial digital-twin teams, edge AI and video-analytics developers
Availability
Jetson AGX Thor Developer Kit generally available at $3,499; Omniverse free for development and production since May 2026; Cosmos models open under the OpenMDW 1.1 license
The verdict: This is a genuinely different business from Nvidia’s data-center franchise, not a rebrand of it. Jetson Thor, Omniverse, and Cosmos target a market — robots and physical systems operating outside a data center, under tight power and latency budgets — where Blackwell-class GPUs and Spectrum-X networking don’t apply directly. The pieces fit together logically (simulate in Omniverse, generate synthetic data and reasoning with Cosmos, deploy on Thor at the edge), and the hardware specs for Jetson Thor are concrete and verifiable. The open question, which no amount of chip or model specification answers, is how many robots actually ship running this stack versus how many pilots stay pilots.
Nvidia’s Other Bet: From Data Centers to the Physical World
Nvidia’s data-center business runs on a simple logic: bigger GPUs, faster interconnect, and software that keeps developers on Nvidia’s tooling. None of that transfers directly to a robot. A humanoid robot or autonomous mobile robot can’t carry a rack of GB300 GPUs or depend on a Spectrum-X fabric — it needs a single module that fits inside a chassis, runs on battery power, and still has enough throughput to fuse camera, lidar, and other sensor data in real time while planning motion. That’s a different engineering problem from scaling a training cluster, and Nvidia has built a separate product line — what it calls “physical AI” — to address it.
The through-line to Nvidia’s data-center business is real but indirect: Jetson Thor’s Blackwell GPU architecture is a scaled-down relative of the same Blackwell generation used in GB300 systems, Cosmos models are trained on data-center-class Nvidia hardware before being distilled down to run at the edge, and Omniverse simulation workloads can themselves run on Nvidia’s data-center GPUs or on RTX workstations. Physical AI depends on the data-center business for training and simulation horsepower, but the product it ships is built for a robot, not a rack.
Jetson Thor: The Robot’s Brain
Jetson Thor is Nvidia’s edge compute module for robotics, built around its current Blackwell GPU generation. The production Jetson T5000 module packs a 2,560-core Blackwell GPU with 96 fifth-generation Tensor Cores, a 14-core Arm Neoverse-V3AE CPU, and 128GB of LPDDR5X memory at 273GB/s — all inside a power envelope Nvidia specifies at 40W to 130W, which matters enormously for anything battery-powered. Nvidia rates the module at up to 2,070 sparse FP4 TFLOPS, and claims up to 7.5x the AI compute and 3.5x the energy efficiency of the previous-generation Jetson AGX Orin module. A smaller, preliminary T4000 variant trades some of that compute and memory for a lower price point.
The module ships inside a Jetson AGX Thor Developer Kit — a $3,499, generally available board that includes a 1TB NVMe drive, 5GbE and QSFP28 (4x25GbE) networking, and Wi-Fi 6E — running JetPack 7 on Ubuntu 24.04 with a unified CUDA 13.0 toolchain shared with Nvidia’s other Arm-based products. On the software side, Nvidia bundles its Isaac robotics stack, Metropolis for video analytics, and Holoscan for sensor processing, and explicitly supports running Isaac GR00T humanoid-robot foundation models and a 7B-parameter Cosmos Reason vision-language model directly on the device. Nvidia’s own benchmarks report sub-200ms time-to-first-token and sub-50ms time-per-output-token running small vision-language models with 16 simultaneous requests on the module — real-time enough for a robot that needs to react, not just report.
Omniverse: Simulating the World Before Robots Touch It
Training or testing a robot’s decision-making in the real world is slow, expensive, and sometimes dangerous. Omniverse is Nvidia’s answer: a set of modular libraries, built on the OpenUSD scene-description format, for constructing simulation-ready 3D environments. Its RTX rendering and sensor-simulation libraries generate synthetic camera, lidar, and radar data from those scenes, while its GPU-accelerated physics engine simulates contacts, collisions, and motion. A “SimReady” validation layer checks that an OpenUSD asset actually meets simulation requirements before it’s used for training or testing, which matters because a visually convincing 3D model that behaves unrealistically under physics teaches a robot the wrong lessons.
Nvidia positions Omniverse across several use cases beyond robot training: industrial digital twins that validate a factory layout before construction, AI “factory” digital twins for testing power and cooling changes in data centers themselves, and autonomous-vehicle simulation for testing perception systems virtually. As of May 2026, Nvidia made Omniverse free for both development and production use, with no NVIDIA AI Enterprise subscription required — support without that subscription is limited to community channels (the NVIDIA Developer Forum and Discord), with paid Enterprise support available separately.
Cosmos: World Foundation Models for Reasoning and Synthetic Data
Cosmos is the newest and most conceptually distinct piece. Nvidia describes it as an open platform of “world foundation models” — models trained to understand and generate physically plausible video and scene data, rather than text. The current generation, Cosmos 3, ships in three sizes built on a Mixture-of-Transformers architecture with separate reasoning and generation pathways: a 64-billion-parameter Super model for maximum physics accuracy, a 16-billion-parameter Nano model sized to run on an Nvidia DGX Station for faster post-training, and a 4-billion-parameter Edge model with a Nemotron-based reasoner meant to run real-time vision-language and world-action tasks directly on edge devices like Jetson Thor.
Cosmos serves three distinct jobs in the physical AI pipeline. As a vision-language reasoner, it interprets objects and intent in a scene for use cases like quality inspection or traffic monitoring. As a world-action backbone, it’s post-trained into robot-specific policy models for particular robot bodies and camera setups. And as a generative simulator, it produces synthetic video of plausible futures from text, image, video, sound, or action inputs — letting teams train on scenarios they can’t easily or safely capture in the real world, including rare edge cases for autonomous vehicles. Nvidia releases the Cosmos world foundation models under the OpenMDW 1.1 open license from the Linux Foundation, and pairs them with supporting tools — Cosmos Curator for dataset curation, Cosmos Transfer for turning Omniverse simulation output into photorealistic synthetic video, and Cosmos Evaluator for scoring synthetic video quality.
How the Three Pieces Fit Together
The intended workflow runs roughly in one direction. A team builds a 3D environment and robot model in Omniverse, using OpenUSD assets and GPU physics to get realistic behavior. Cosmos Transfer can take that simulated scene and generate more varied, photorealistic synthetic video from it — different lighting, weather, or camera angles than the original simulation covered — multiplying the training data available without more simulation time or real-world data collection. Robot policies (including Isaac GR00T models) and reasoning models get trained or post-trained against that combined simulated-and-synthetic data, using Cosmos world-action models as a backbone. The resulting, distilled model then deploys onto a Jetson Thor module inside the actual robot, where it has to run within that device’s 40–130W power budget and real-time latency requirements — a very different environment from the GPU cluster it was trained on.
Physical AI vs. Data-Center AI: Two Different Nvidia Businesses
Dimension
Physical AI stack (Thor / Omniverse / Cosmos)
Data-center AI stack (Blackwell-GB300 / Vera Rubin / Spectrum-X / NIM)
Where it runs
Inside or alongside a robot, vehicle, or edge device
Inside a data center rack or cluster
Power budget
40–130W per module
Multiple kilowatts per server, liquid-cooled racks
Primary job
Real-time perception, reasoning, and motion control on-device
Large-scale model training and high-throughput inference
Key software
Isaac, Omniverse, Cosmos, JetPack/CUDA for Arm
NIM, Triton, CUDA for data-center GPUs, NVLink/NCCL
Business model
Hardware module sales plus mostly-open simulation and model tooling
High-margin GPU and networking hardware plus software subscriptions (AI Enterprise)
Pros and Cons
Pro: A coherent pipeline — simulate, generate synthetic data, deploy to the edge — rather than three disconnected products, with Nvidia’s own tooling (Cosmos Transfer, GR00T) bridging the gaps
Pro: Jetson Thor’s specs (power, memory, compute) are concrete, independently checkable numbers, not just marketing claims about an abstract platform
Pro: Omniverse being free for production use and Cosmos models being released under an open license lowers the barrier for smaller robotics teams to adopt the stack
Con: Real-world robot performance figures (how well a GR00T policy trained this way actually generalizes outside simulation) aren’t independently benchmarked in Nvidia’s own materials
Con: The stack still assumes access to Nvidia data-center GPUs for the Omniverse/Cosmos training and simulation side, so smaller teams face real compute costs upstream of the “free” software
Con: Physical AI is a nascent market; unlike the data-center AI business, there isn’t yet a large base of shipped, revenue-generating robots to validate the pitch at scale
Who Should Pay Attention to This
Robotics companies building humanoid robots, autonomous mobile robots, or manipulation systems are the direct audience — Jetson Thor is explicitly positioned against this exact use case, down to supporting Isaac GR00T models out of the box. Autonomous vehicle teams should care specifically about Cosmos’s synthetic-data generation, since generating varied weather, lighting, and sensor-view scenarios synthetically addresses a real data-scarcity problem in AV development. Industrial and digital-twin teams evaluating simulation platforms should look at Omniverse independent of robotics, since its free production license as of May 2026 changes the cost calculus for building facility or AI-factory digital twins. Investors and analysts tracking Nvidia’s business should treat this as a distinct growth thesis from the data-center GPU story — one with a much smaller current revenue base and a longer path to proof, since it depends on physical products shipping in volume rather than cloud capacity being purchased.
Bottom Line
Jetson Thor, Omniverse, and Cosmos are a real, technically coherent answer to a problem data-center GPUs can’t solve: getting capable AI into machines that have to operate under tight power and latency limits, out in the physical world. The specs behind each piece — Thor’s TFLOPS and power envelope, Cosmos’s parameter counts and licensing, Omniverse’s now-free production license — are concrete and traceable to Nvidia’s own documentation, which is more than can be said for a lot of “robotics AI” marketing. What remains unproven, and unprovable from a specs sheet, is adoption: whether this becomes the default stack robotics companies build on, the way CUDA became the default for data-center AI training, or one of several competing approaches in a market still working out its own foundations.
FAQ
Is Jetson Thor a GPU, or a full computer? It’s a full system-on-module: a Blackwell-architecture GPU, a multi-core Arm CPU, memory, and dedicated video/vision accelerators on one board, sold either as a bare production module (T5000/T4000) or inside a complete Developer Kit with storage, networking ports, and connectors.
Do I need Omniverse and Cosmos together, or can I use just one? They’re designed to complement each other but aren’t strictly dependent. Omniverse works as a standalone simulation and digital-twin platform without Cosmos. Cosmos models can also be used independently for reasoning or synthetic data generation without an Omniverse scene as input, though Nvidia’s intended pipeline feeds Omniverse simulation output into Cosmos Transfer to generate more varied synthetic data.
Is Cosmos free to use? The Cosmos world foundation models themselves are released under the OpenMDW 1.1 open license from the Linux Foundation. Running them at scale for training or generation still requires compute — typically Nvidia data-center GPUs or RTX PRO Blackwell-series hardware — so there’s a real infrastructure cost even though the models are openly licensed.
How is this different from Nvidia’s data-center AI business (Blackwell, Vera Rubin, Spectrum-X)? The data-center stack is about training and serving AI models inside power-rich, liquid-cooled server racks connected by high-speed interconnect. The physical AI stack is about running AI on a power-constrained device that moves through the real world. They share underlying GPU architecture generations and some software (CUDA, Isaac tooling draws on data-center-trained models), but target different products, customers, and revenue models.
What robots actually use this stack today? Nvidia’s own materials cite developer and research use of Jetson AGX Thor for humanoid and mobile robotics development, and reference Isaac GR00T-based humanoid robot models and Isaac Sim-based reinforcement learning workloads (including a cited case where RL training cycles dropped from about 24 hours to under one hour). This piece does not independently verify deployment volumes or named commercial robot products beyond what Nvidia has publicly disclosed.
Phishing is still the entry point for most breaches, and training employees to recognize it has turned into its own software category: security awareness training and phishing simulation platforms. We looked directly at the pricing and product pages for the three names that come up most often in 2026 — KnowBe4, Proofpoint, and Hoxhunt — to see what’s actually published, what requires a sales call, and how the feature sets differ.
The headline finding: this is not a uniformly “contact sales” category the way some security software is. KnowBe4 and Proofpoint both publish real per-seat MSRP pricing on their own sites, with tiers you can actually read before talking to anyone. Hoxhunt is the outlier — its pricing is entirely quote-based, scoped through a call, with no published rate card at all.
At a Glance
Vendor
Published Price
Free Trial
Best For
KnowBe4
Published MSRP, per seat/month, billed on a 3-year term, tiered by seat count (25–50 up to 1001+). Example: $2.40–$3.75/seat/month for 25–50 seats (Foundation/Advanced), down to $1.63–$2.79 for 501–1000 seats.
No free trial of paid product; free “Attack Simulation Test” sandbox tool offered
Buyers who want to compare real tiered pricing before a sales call
Proofpoint
Security Awareness Training is sold as an add-on module (PESA) to Proofpoint Essentials at a published MSRP of $1.00 per active user/month; Essentials email security tiers run $2.75–$5.33/user/month
Not stated on the pages reviewed; demo request offered
Businesses already buying or considering Proofpoint Essentials email security
Hoxhunt
Not published; priced per employee via custom quote after a scoping call
No free trial; demo only
Buyers prioritizing a specific AI-personalized training approach over price transparency
Short Verdict
KnowBe4 is the only one of the three that lets you build a real budget estimate from its own website, with a published per-seat rate card across six seat-count tiers and two training depths (Foundation and Advanced). Proofpoint’s security awareness features are bundled as a specific, separately priced add-on (PESA, $1/user/month) on top of its Essentials email security suite, which makes the most sense if you’re already in the Proofpoint ecosystem or considering it for email security too. Hoxhunt publishes no pricing at all — every quote runs through a 30-minute scoping call — so it’s the hardest of the three to evaluate on cost alone, even though its product pitch (AI-personalized “adaptive” phishing training) is distinctive.
What Each One Is
KnowBe4 is the largest and most established name in this category, built specifically around phishing simulation and security awareness content. Its site lists two training levels — SAT Foundation and SAT Advanced — each with published MSRP pricing in standard volume tiers (25–50, 51–100, 101–250, 251–500, 501–1000, and 1001+ seats, where the top tier requires a custom quote). Per its own site, KnowBe4 offers “year-round unlimited simulated phishing attacks” with templates, a Phish Alert Button, Social Engineering Indicators, Callback Phishing and Simulated Vishing tests, and even USB/QR code simulations. Its training library runs from 200+ modules (Foundation) to 1,000+ (Advanced), and reporting includes 60+ built-in reports, executive reporting, and a proprietary Risk Score from what it calls its SmartRisk Engine. Add-ons like Compliance Plus, Student Edition, and PhishER Plus (for email-based incident response) are priced separately, per seat.
Proofpoint approaches this differently: security awareness training isn’t a standalone flagship product on its small-business pricing sheet, it’s a specific line item. Proofpoint’s published Essentials price list names “Proofpoint Essentials Security Awareness” (SKU PP-ESS-PSAT-A) at $1.00 per active user per month, including simulated phishing and attachment emails plus more than 40 training modules, sold alongside (not folded into) Proofpoint Essentials email security, which itself runs $2.75 to $5.33 per user/month across its Business, Advanced, and Professional tiers. Proofpoint also has a separate, larger enterprise Security Awareness Training product (branded with features like a Satori Phishing Simulation Agent, AI “ThreatFlip” that turns real detected phishing into training material, and a Human Risk Explorer dashboard), but that page does not publish pricing — it’s demo-and-quote.
Hoxhunt positions itself around AI-driven, individually adaptive phishing training rather than one-size-fits-all campaigns — its own description is “personalized phishing training.” Its pricing page states plainly that pricing is per employee and depends on headcount and the capabilities selected, determined on a 30-minute scoping call; no rate card, tiers, or starting price appear anywhere on the page. Hoxhunt’s site highlights an administrator dashboard and reporting tour, plus “Email Incident Response Automation” for managing reported phishing, but doesn’t name specific third-party email security integrations on its pricing page.
Pricing Breakdown
Vendor / Tier
Published Price
Notes
KnowBe4 SAT Foundation, 25–50 seats
$2.40/seat/month
MSRP, billed monthly on a 3-year term, excludes tax; prices as of May 2026
KnowBe4 SAT Advanced, 25–50 seats
$3.75/seat/month
Same billing terms
KnowBe4 SAT Foundation, 501–1000 seats
$1.63/seat/month
Per-seat price drops at higher volume tiers
KnowBe4 SAT Advanced, 501–1000 seats
$2.79/seat/month
Six volume tiers total; 1001+ requires a custom quote
MSRP; security awareness is a separate add-on cost
Proofpoint Security Awareness Training (enterprise product)
Not published
Demo/quote only on the main product page
Hoxhunt
Not published
Fully custom quote, per employee, after a scoping call
Pros
KnowBe4: Genuinely transparent, tiered MSRP pricing you can review without talking to sales; very large training content library (1,000+ modules at the Advanced tier); broad simulated-attack formats including vishing, USB, and QR code tests; mature reporting with a named risk-scoring engine.
Proofpoint: Security awareness pricing is clearly itemized ($1/user/month for Essentials-tier PESA) rather than hidden in a bundle; natural fit if you’re also buying Proofpoint’s email security, since reported-phishing workflows and Proofpoint’s wider security stack are built to work together; the enterprise-tier product adds AI-driven features like ThreatFlip (converting real detected attacks into training simulations).
Hoxhunt: Product positioning around individualized, adaptive training rather than blanket campaigns is a genuinely different approach from blast-style phishing simulations; includes incident-response automation for reported phishing emails.
Cons
KnowBe4: Pricing is billed on a 3-year term, which is a longer commitment than some small businesses want; no free trial of the actual training product, only a limited free phishing-test sandbox; the highest seat tier (1001+) isn’t published either.
Proofpoint: The published MSRP pricing we found applies to the SMB-oriented Essentials bundle; the larger enterprise Security Awareness Training product (with the more advanced AI and risk-scoring features) does not publish pricing at all, so a bigger organization will likely still need a quote; security awareness is an added cost on top of email security, not included.
Hoxhunt: Zero published pricing anywhere, which makes it impossible to compare against KnowBe4’s and Proofpoint’s rate cards without engaging sales; no free trial; feature claims around reporting and integrations are described in general terms on the pricing page rather than itemized.
Who It’s a Good Fit For
Choose KnowBe4 if you want to build a defensible budget estimate before ever talking to a salesperson, and you want the broadest content library and simulated-attack variety (including vishing and physical USB/QR tests) alongside mainstream phishing campaigns.
Choose Proofpoint if you’re already using or evaluating Proofpoint Essentials for email security — the $1/user/month security awareness add-on is a clean, itemized way to bolt training onto an email security purchase you’re likely already making, and the combined reported-phishing workflow benefits from being in one vendor’s stack.
Consider Hoxhunt if the adaptive, individualized training model is specifically what you’re after and you’re comfortable going through a scoping call before knowing the cost — just don’t expect to compare it apples-to-apples with KnowBe4 or Proofpoint on price without that call happening first.
Who Should Look Elsewhere
A business that needs to lock in pricing within a tight budgeting cycle and cannot wait on a sales process should be cautious with Hoxhunt. A business that wants security awareness training folded into one line item rather than itemized separately may find Proofpoint’s structure (email security and PESA sold separately) less convenient than it first appears. And a business unwilling to commit to a 3-year billing term should scrutinize KnowBe4’s standard terms before signing.
Bottom Line
This category is less opaque than reputation suggests — two of the three vendors we checked, KnowBe4 and Proofpoint, publish real per-seat MSRP pricing you can read without a phone call, and only Hoxhunt is fully quote-based. KnowBe4 wins on price transparency and content depth. Proofpoint makes the most sense bundled with its own email security line. Hoxhunt’s distinct adaptive-training pitch may justify the extra step of a scoping call, but you should go in knowing you won’t find a number on the website first.
Security awareness training is only one layer of defense against account compromise — pairing it with strong authentication matters just as much. If you haven’t already, it’s worth reading our breakdowns of the best 2FA apps in 2026 and passkeys vs. two-factor authentication, since even well-trained employees benefit from phishing-resistant login methods as a backstop.
FAQ
Is security awareness training pricing always quote-based? Not always. KnowBe4 and Proofpoint both publish specific MSRP numbers on their own sites — KnowBe4 as tiered per-seat pricing for its SAT Foundation and Advanced products, and Proofpoint as a $1/user/month add-on (PESA) to its Essentials email security line. Hoxhunt is the one of these three that publishes no pricing at all.
Does Proofpoint’s security awareness training come with its email security, or is it extra? It’s extra. Proofpoint’s own Essentials price list lists “Proofpoint Essentials Security Awareness” as a separate SKU (PP-ESS-PSAT-A) at $1.00 per active user per month, sold in addition to the Essentials email security tiers ($2.75–$5.33/user/month).
What’s different about Hoxhunt’s approach to phishing training? Hoxhunt markets itself around personalized, adaptive phishing simulations tailored to the individual rather than identical campaigns sent to everyone, plus automation for handling reported phishing emails. It doesn’t publish how this is priced; you get a quote after a scoping call based on headcount and desired capabilities.
Can I try any of these before buying? None of the three offer a full free trial of their paid training product based on their current sites. KnowBe4 offers a free standalone phishing-test tool (the Attack Simulation Test) rather than a trial of the full platform; Proofpoint and Hoxhunt both offer demos instead of trials.
Does KnowBe4’s pricing require a long-term contract? KnowBe4’s published MSRP pricing is billed monthly on a 3-year term, per its own pricing page (as of May 2026). That’s a longer standard commitment than many SaaS products, so it’s worth confirming current terms directly with KnowBe4 before budgeting.
Oracle has spent the past two years rebuilding its enterprise software pitch around one idea: agents, not just assistants, should run inside the applications businesses already use for finance, HR, supply chain, and customer service. The centerpiece of that effort is Oracle AI Agent Studio, a platform built directly into Oracle Fusion Cloud Applications that lets customers extend Oracle’s own prebuilt agents or design entirely new ones using the company’s enterprise data, security model, and choice of large language models. This article explains what AI Agent Studio actually is, how Oracle prices and packages it, where it fits next to Oracle’s broader database and multicloud strategy, and how it stacks up conceptually against Salesforce Agentforce and Microsoft Copilot Studio.
At a Glance
Attribute
Detail
What it is
A platform inside Oracle Fusion Cloud Applications for building, extending, orchestrating, and governing AI agents and multi-agent teams
Who it’s for
Existing Oracle Fusion Applications customers (ERP, HCM, SCM, CX) and implementation partners; not a standalone product sold outside Fusion
Announced / GA
Announced March 20, 2025 at Oracle CloudWorld London; Oracle has continued expanding it through 2025–2026 releases (e.g., an Agentic Applications Builder)
Embedded agents
Oracle says more than 50 prebuilt agents are already packaged into Fusion Applications, extensible through the Studio
Pricing model
Embedded AI Agent Studio use is included at no additional cost with existing Fusion subscriptions; building unlimited custom agents from scratch requires a separately priced “Custom AI” subscription tied to Fusion’s seat/employee-based licensing. Oracle does not publish self-serve list prices.
LLM choice
Fusion-tuned models (including Llama- and Cohere-based options) or external models; Custom AI adds access to Oracle-built agents powered by OpenAI’s GPT-4 hosted on Azure, with other cloud-hosted models planned
The Verdict
AI Agent Studio is a credible, well-integrated answer to the question every SaaS vendor is now being asked: “where are the agents?” Its strongest asset is also its biggest constraint — deep, native access to Fusion’s data model, APIs, and role-based security — which makes it genuinely useful for Oracle customers but irrelevant to anyone not already running Fusion Applications. The free embedded tier is a smart wedge; the separately priced Custom AI tier, where real differentiation and cost live, is where prospective buyers need to push Oracle hard for specifics, since none are published on the open web.
What It Is
Oracle describes AI Agent Studio as the first platform for designing and deploying AI agents across an entire enterprise application suite, rather than inside a single department’s tool. It ships as part of Oracle Fusion Cloud Applications on Oracle Cloud Infrastructure (OCI) and gives administrators and business users several core capabilities, according to Oracle’s own March 2025 announcement:
Agent template libraries — prebuilt agent templates paired with natural-language prompts that non-developers can configure
Agent team orchestration — multiple agents and people collaborating on multi-step work, with checkpoints and human approvals built in
Agent extensibility — adding documents, tools, prompts, or external APIs to an existing Oracle-built agent rather than starting from scratch
Choice of LLMs — Fusion-optimized models or industry-specific external models
Native Fusion integration — direct, governed access to Fusion business objects, APIs, and knowledge stores
Trust and security inheritance — agents automatically operate under a customer’s existing Fusion role-based access controls and security policies
Validation and testing tooling — delivered test libraries plus monitoring for reliability, explainability, and performance
Oracle’s “Dawn of the AI Enterprise Agent Workforce” page frames this as agents that “closely mimic the way humans work” across finance, HR, supply chain, and customer experience, explicitly positioning the approach against point-solution departmental bots from other vendors.
How It Differs From a Generic Chatbot
The distinction Oracle leans on hardest is that these are not conversational front-ends bolted onto Fusion — they are agents with direct, permissioned access to live Fusion transactions, records, and workflows, able to take multi-step actions (not just answer questions) and hand off work between each other or to a human for approval. A chatbot answers “what’s the status of this purchase order?” An Oracle agent, per the company’s own examples, can run an entire opportunity-to-quote sequence, process a return order, or build a shift schedule, checking in with a manager at defined approval points along the way. The agents also inherit a customer’s existing Fusion security configuration rather than requiring a parallel permissions model, which Oracle positions as a meaningful difference from stand-alone AI tools layered on top of a SaaS suite.
Pricing and Economics: What Oracle Discloses (and Doesn’t)
Oracle’s March 2025 press release states plainly that AI Agent Studio for extending the more-than-50 embedded agents is “available at no additional cost” and works “under existing subscriptions” — a point Oracle has reiterated as it expanded the Studio through 2025 and 2026. That covers extending and orchestrating Oracle’s own prebuilt agents.
Building fully custom agents from scratch, however, falls under a separate offering Oracle calls Custom AI, which the company describes as “a separately priced offering within Oracle Fusion.” According to that page, Custom AI includes unlimited custom agents and agent teams in production, usage that isn’t capped, access to externally hosted models (including an Oracle-built agent powered by OpenAI’s GPT-4 hosted on Azure) without separate API keys, and multimodal agents that handle images, audio, and video. Oracle states this follows the same licensing logic as core Fusion Applications — priced by seats and employees — but does not publish specific dollar figures, per-agent rates, or usage caps on its public pages. Oracle’s own documentation on when a Custom AI Agent Subscription is required likewise describes functional thresholds rather than prices. Any specific quote comes from an Oracle account team and a customer’s existing contract, so treat third-party estimates of “Oracle AI Agent Studio cost” with caution — Oracle itself has not published a self-serve price list.
Example Use Cases
CX: opportunity-to-quote automation, where an agent qualifies a deal and assembles a quote before a sales rep reviews it
SCM: return order processing, where an agent triages a return request, checks policy, and initiates the refund or replacement workflow
HCM: shift scheduling, where an agent builds and adjusts schedules against labor rules and availability, escalating conflicts to a manager
ERP/Finance: Oracle markets additional embedded finance and procurement agents (e.g., invoice matching, close-process assistance) as part of the broader Fusion agent library, though the March 2025 release itself does not detail ERP-specific examples
How It Compares to Agentforce and Copilot Studio
All three platforms share a premise — give enterprises a place to build and govern AI agents that act inside business systems — but they start from different footholds and price very differently in public:
Salesforce Agentforce publishes detailed consumption pricing on its official pricing page: a free Foundations tier, Flex Credits sold at $500 per 100,000 credits (roughly 20 credits per standard agent action), a $2-per-conversation option for customer-facing agents, and per-user licenses ranging from $5 to $550 per user, per month depending on edition. This is the most transparent, self-serve pricing of the three.
Microsoft Copilot Studio uses a pay-as-you-go model billed in “Copilot Credits,” as described on Microsoft’s Azure pricing page. Credit consumption scales with task complexity and the agent’s knowledge sources, but Microsoft does not list a flat per-credit dollar rate on that page, directing buyers to the Azure pricing calculator or a sales contact instead.
Oracle AI Agent Studio is the least transparent of the three on public pricing: embedded agent extension is bundled free into existing Fusion subscriptions, while unlimited custom-agent building is a separately priced, contract-negotiated add-on scaled to seats and employees, with no published rate card.
The practical difference for buyers: Agentforce and Copilot Studio can, in principle, be evaluated and estimated without a sales call (even if real-world bills get complicated fast); Oracle AI Agent Studio’s custom tier cannot be estimated from public information at all.
Pros
Deep native integration with Fusion data, APIs, and existing role-based security — no parallel permissions system to build
More than 50 prebuilt agents already embedded at no extra cost, reducing time-to-value for common finance, HR, supply chain, and CX workflows
Choice of LLMs, including Fusion-tuned and third-party models, rather than a single locked-in model
Built-in orchestration for multi-agent teams with human checkpoints, not just single-turn Q&A
Delivered test libraries and monitoring tools aimed at governance, explainability, and reliability
Cons
No published self-serve pricing for Custom AI — buyers must go through an Oracle account team to get real numbers
Only useful if a company is already running, or planning to run, Oracle Fusion Cloud Applications; it is not a general-purpose agent platform
Oracle’s own materials are promotional and light on independently verifiable performance benchmarks or customer-reported ROI figures
Comparisons to Agentforce and Copilot Studio are harder to make apples-to-apples given the pricing opacity on Oracle’s side
Who It’s a Good Fit For
Existing or committed Oracle Fusion Applications customers — particularly those running ERP, HCM, SCM, or CX modules who want to extend Oracle’s prebuilt agents without standing up a separate AI platform. It also suits organizations that want agent governance to inherit their existing enterprise security model rather than manage a second set of access controls.
Who Should Look Elsewhere
Companies not running Oracle Fusion Applications gain nothing from AI Agent Studio specifically — it is not sold as a standalone product. Organizations that need transparent, self-serve pricing to budget before committing may find Salesforce Agentforce’s published credit and per-conversation rates, or Microsoft’s Azure-calculator-based Copilot Studio estimates, easier to plan around than Oracle’s contract-negotiated Custom AI tier.
Where It Fits in Oracle’s Broader Cloud and AI Strategy
AI Agent Studio doesn’t exist in isolation — it sits on top of infrastructure Oracle has been building out across its stack. The agents run on Oracle Cloud Infrastructure and increasingly tap Oracle Database 23ai‘s native vector search and AI capabilities for retrieval-augmented workflows, while the underlying compute often runs on Exadata and Autonomous Database infrastructure that Oracle has spent years optimizing for self-managing, low-latency transaction processing. Oracle has also been pushing Fusion and its database into other clouds through deals like Oracle Database@AWS, Azure, and Google Cloud, meaning AI Agent Studio’s reach could extend to customers who run Fusion workloads from inside those hyperscaler regions rather than directly on OCI.
The Bottom Line
Oracle AI Agent Studio is a genuinely differentiated move for an ERP/HCM/SCM/CX vendor: it embeds agents where enterprise data and workflows already live, rather than bolting a chatbot onto the side. The free embedded tier lowers the barrier to trying agentic AI inside Fusion, but the real cost — and the real capability ceiling — sits in the separately priced Custom AI tier, where Oracle has chosen not to publish numbers. Anyone evaluating it against Agentforce or Copilot Studio should weigh Oracle’s deeper native integration against its comparative pricing opacity, and get a concrete quote before assuming “included with Fusion” covers what they actually plan to build.
FAQ
Is Oracle AI Agent Studio free? Extending and orchestrating the 50+ agents Oracle already embeds in Fusion Applications is included at no additional cost with an existing Fusion subscription. Building unlimited fully custom agents requires the separately priced Custom AI subscription.
Do I need to already be an Oracle Fusion customer to use it? Yes. AI Agent Studio is built into Oracle Fusion Cloud Applications and is not offered as a standalone product independent of Fusion.
Which AI models power the agents? Oracle offers Fusion-optimized models (including Llama- and Cohere-based options) by default, and customers can bring industry-specific external models. The Custom AI tier adds access to an Oracle-built agent powered by OpenAI’s GPT-4 hosted on Azure, with more cloud-hosted model options planned.
How does this differ from a simple chatbot inside Fusion? The agents take multi-step actions against live Fusion data and APIs — such as processing a return order or building a shift schedule — rather than just answering questions, and they inherit a customer’s existing role-based security rather than operating as a bolted-on layer.
How does Oracle’s pricing compare to Salesforce or Microsoft? Salesforce and Microsoft publish more granular self-serve pricing (Agentforce’s credit and per-conversation rates; Copilot Studio’s pay-as-you-go credit model). Oracle’s Custom AI tier is priced by contract, scaled to seats and employees like core Fusion licensing, with no public rate card.
Typing isn’t always the fastest or most comfortable way to get words onto a screen. Writers drafting long-form pieces, developers who want to stay in flow, and professionals managing RSI or other access needs all have reasons to dictate instead of type. This roundup covers three very different tools built for exactly that: Nuance’s enterprise-grade Dragon Professional (now part of Microsoft), the modern AI dictation app Wispr Flow, and the Dictation feature built into every Mac and iPhone for free. Note that this is specifically about dictating your own writing — emails, documents, code comments, prompts — not about transcribing other people’s meetings, which this site already covered in its Otter.ai vs. Fireflies.ai vs. Fathom comparison. Everything below is pulled from each vendor’s own site as of November 2026.
At a Glance
App
Price
Free Plan?
Platform
Best For
Dragon Professional
Not published; quote-based via Nuance/Microsoft sales
No
Windows only (v16 optimized for Windows 11, works on Windows 10)
Enterprises and regulated industries needing managed, compliance-ready dictation
Wispr Flow
Free tier; Flow Pro $15/mo ($12/mo billed annually)
Yes
Mac, Windows, iPhone, Android
Individual writers, coders, and professionals who dictate across many apps daily
Apple Dictation
Free (built into the OS)
Yes — it’s not a separate purchase
Mac, iPhone, iPad (part of macOS/iOS)
Anyone on Apple hardware who wants basic voice-to-text with zero setup or cost
Short Verdict
If you need centrally managed, Windows-based dictation for a regulated industry — with custom voice commands, macros, and admin controls — Dragon Professional is built for that, though you’ll need to contact sales for pricing since Nuance doesn’t publish it. If you’re an individual who dictates across many apps on whatever device you’re holding, Wispr Flow is the most actively developed option in 2026, with a real free tier and a clear $15/mo Pro price. And if you just want to dictate a quick email or note without installing anything, Apple’s built-in Dictation is free, already on your Mac or iPhone, and good enough for short, casual text — just don’t expect the AI-level polish of Flow or the enterprise controls of Dragon.
What Each App Is
Dragon Professional
Dragon Professional is Nuance’s business dictation and transcription software, now under Microsoft. Per dragon.nuance.com, the current version (v16) is explicitly a Windows product — optimized for Windows 11 and compatible with Windows 10 — and the page makes no mention of a macOS version. (Nuance discontinued Dragon for Mac years ago, so Windows is effectively the only desktop option today.) Nuance’s own claims on that page include recognition accuracy of “up to 99%… right from first use” and dictation speeds “3 times faster than typing.” Beyond plain dictation, Dragon Professional supports live and recorded transcription (including batch-processing existing audio files via its Auto Transcribe Folder Agent), custom voice commands and multi-step macros for boilerplate text, and centralized deployment through the Nuance Management Center for template distribution, usage reporting, and license management. The page targets financial services, education, and health and human services, and positions Dragon as a way to reduce outsourced transcription, populate CRM records from client conversations, and keep compliance documents current. A separate Dragon Anywhere Mobile app extends dictation to phones, though the main Dragon Professional page doesn’t detail coding-by-voice workflows or give a specific supported-language list — it only links out to regional (UK, Germany, France, Spain, Italy, Australia/NZ) versions of the site.
Wispr Flow
Wispr Flow is a newer, AI-driven dictation app designed to work in any text field on Mac, Windows, iPhone, or Android, with no per-app plugins required. According to wisprflow.ai, the free plan gives new users 2,000 words per week with no credit card required, while Flow Pro removes the word cap entirely. Flow’s core pitch is that it does more than transcribe: it strips filler words, adds punctuation, auto-formats text, and can even catch a mid-sentence correction — turning “let’s meet at 5… actually 6pm” into “Let’s meet at 6pm” — in real time. It supports more than 100 languages with automatic language detection or manual selection, learns names and specialized jargon through a personal dictionary, and lets users set up voice-triggered Snippets that expand into saved text like email signatures or boilerplate replies. The company states Flow adapts writing style per app (formal for email, casual for messaging), and names Cursor and ChatGPT as supported targets for dictating code and prompts, with a dedicated “vibe coding” resource page. A separate Notetaker feature (Mac and Windows only) handles meeting transcription for Zoom, Google Meet, Teams, and Slack huddles — that’s the meeting-notes use case our Otter.ai/Fireflies/Fathom article already covers, so this piece focuses on Flow’s writing-dictation side. Vendor-stated performance claims include “4x faster than your keyboard” (220 words per minute dictated versus 45 wpm typed) and case-study figures like “90% faster message output” for one user — numbers from Wispr’s own marketing and case studies, not independently audited benchmarks. The site also states Flow doesn’t sell user data and lists SOC 2 Type II, ISO 27001, and HIPAA compliance.
Apple Dictation
Dictation is the speech-to-text feature built into macOS and iOS/iPadOS, documented at support.apple.com. Apple’s own description is simple: “With Dictation, you can speak to enter text anywhere you can type it.” On the Mac, you turn it on in Keyboard settings and trigger it with the Microphone key, a keyboard shortcut, or the Edit menu’s Start Dictation command; on Apple silicon Macs you can even keep typing while dictating. You can speak punctuation marks and emoji names aloud, and say “new line” or “new paragraph” for basic formatting. Apple’s support documentation doesn’t publish an accuracy percentage; instead, it describes a correction flow where ambiguous words are underlined and clickable so you can pick an alternative or redictate. Availability varies by language and region — Apple points users to its feature-availability pages rather than listing every supported language on the Dictation help page itself — and Keyboard settings let you check whether dictation on your device is processed on-device or sent to Apple’s servers, with an optional, separate setting to share audio samples with Apple. Dictation has no session time limit beyond stopping automatically after 30 seconds of silence, though it’s unavailable while Voice Control is active. Apple’s accessibility materials also describe the related Voice Control feature (iPhone, iPad, Mac, Apple Vision Pro, and CarPlay) for navigating and commanding a device by voice, including a “Swift mode” for dictating code in Xcode — a separate feature from basic Dictation, aimed more at hands-free device control than long-form writing.
Volume licensing with Nuance Management Center for admin control, templates, and reporting
Flow Pro for Teams (centralized billing) and Flow Enterprise (SSO, audit logs, data-retention controls, custom pricing)
N/A
Pros
Dragon Professional: Deep enterprise controls (templates, macros, centralized license management); vendor-stated accuracy figures are high; strong fit for compliance-heavy, document-intensive industries.
Wispr Flow: Works across virtually any app on four platforms; real free tier to try before paying; clear, published pricing; actively adds features like self-correction and per-app style adjustment.
Apple Dictation: Completely free with no account or app install; built into hardware most people already own; includes an on-device processing option for privacy-conscious users.
Cons
Dragon Professional: Windows-only, with no current Mac version; no public pricing, so you can’t compare cost without contacting sales; the vendor’s own site doesn’t document coding-by-voice workflows or a specific language list.
Wispr Flow: Unlimited dictation requires a subscription; several of its most dramatic productivity claims (90% faster output, specific dollar savings) come from vendor case studies rather than independent testing; the vendor explicitly warns that AirPods/Bluetooth earbuds can hurt recognition accuracy.
Apple Dictation: No stated accuracy benchmark to compare against competitors; no custom vocabulary/dictionary, voice snippets, or app-specific style adjustment the way Flow offers; dictation stops automatically after 30 seconds of silence, which interrupts long, thoughtful pauses.
Who It’s a Good Fit For
Dragon Professional fits organizations in finance, healthcare, legal, or education that need centrally managed dictation, custom macros, and compliance-friendly deployment on Windows machines.
Wispr Flow fits individual writers, developers, and professionals who dictate frequently across many apps and devices and want a modern, AI-assisted experience with a free tier to test first.
Apple Dictation fits anyone who occasionally dictates short text on a Mac or iPhone and doesn’t want to install anything or pay for a feature they’ll use lightly.
Who Should Look Elsewhere
Mac-only users who need professional-grade dictation software should look past Dragon Professional, since Nuance’s current product page is Windows-specific with no macOS option listed.
Anyone who dictates heavily every day and finds Apple’s 30-second silence cutoff and lack of custom vocabulary limiting should consider Wispr Flow’s free tier before paying for anything.
If what you actually need is automatic meeting transcription and summaries rather than dictating your own writing, see this site’s separate meeting-notes app comparison instead — that’s a different job than the three tools covered here.
Bottom Line
There’s no single “best” here because these three tools serve different budgets and platforms. Dragon Professional is the enterprise choice for Windows shops that need managed deployment and are willing to go through a sales conversation for pricing. Wispr Flow is the best all-around option for individual professionals in 2026: it’s cross-platform, has a real free tier, publishes its pricing, and is the only one of the three actively marketing AI-level writing polish on top of raw transcription. Apple Dictation remains the right call when the bar is simply “free, already installed, good enough” — which, for plenty of quick emails and notes, it is.
FAQ
Does Dragon Professional run on a Mac?
No. Nuance’s current Dragon Professional product page is explicitly a Windows product (optimized for Windows 11, compatible with Windows 10) and doesn’t list a macOS version. Dragon for Mac was discontinued by Nuance years ago.
How much does Dragon Professional cost?
Nuance doesn’t publish a price on its Dragon Professional page; it directs prospective buyers to contact sales for licensing, which typically follows a volume/enterprise model.
Is Wispr Flow actually free to try?
Yes. Wispr Flow’s free plan gives 2,000 words per week with no credit card required, before you’d need to upgrade to Flow Pro ($15/mo, or $12/mo billed annually) for unlimited dictation.
Is Apple’s built-in Dictation as accurate as Dragon or Flow?
Apple doesn’t publish an accuracy figure for Dictation, so a direct numeric comparison against Dragon’s stated “up to 99%” claim or Flow’s speed claims isn’t possible from vendor materials alone. In practice, reviewers generally treat Apple Dictation as fine for short, casual text and less capable than dedicated tools for long-form or technical dictation — but that’s a usage observation, not a vendor-verified statistic.
Can any of these dictate code, not just prose?
Wispr Flow explicitly names code editors and AI coding tools (Cursor, ChatGPT) as supported use cases and has a dedicated resource page on “vibe coding.” Apple’s Voice Control includes a “Swift mode” for dictating code in Xcode, which is a related but separate feature from standard Dictation. Dragon Professional’s own page doesn’t describe a coding-by-voice workflow.
Google Cloud does not sell a Tensor Processing Unit (TPU). It sells a stack. Over the past few weeks this site has looked at the individual pieces of that stack in detail: the 9,216-chip Ironwood TPU pod, the Jupiter data center network that wires those chips together, the Pathways software that schedules training jobs across them, and the Axion Arm CPUs that handle everything that isn’t a matrix multiply. Google’s own name for the bundle that contains all of it, plus Nvidia GPUs, storage, and a battery of open-source frameworks, is AI Hypercomputer. This article is about the bundle itself: why Google packages these parts together, what it actually includes, and how it is sold, rather than a deep dive on any single component.
At a Glance
Attribute
Detail
What it is
Google Cloud’s branded, vertically-integrated AI infrastructure offering — compute, storage, networking, and software sold as one system rather than separate line items
Compute options
Google TPUs (Ironwood, plus older Trillium-generation chips) and Nvidia GPU virtual machines (A4 with B200 GPUs; A5X with Vera Rubin GPUs arriving later in 2026)
Networking & storage
Jupiter data center network, Cross-Cloud Network backbone, Titanium security offload, Google Cloud Managed Lustre and Cloud Storage Rapid for high-throughput I/O
Software layer
Pathways and Pallas for training, JAX/XLA and optimized PyTorch and TensorFlow, GKE and Cluster Director for orchestration, vLLM and GKE Inference Gateway for serving
Who it’s for
AI labs and enterprises training or serving large models, robotics and simulation teams, platform teams that want a turnkey cluster instead of assembling one
Availability
Generally available today on Google Cloud; newer pieces (TPU-based inference instances, Vera Rubin-based A5X VMs) are rolling out through 2026 on a pay-as-you-go, committed-use, or spot basis
The verdict: AI Hypercomputer is less a product than a sales category — Google’s way of saying “stop shopping for chips, networking, and schedulers separately, and buy the whole thing from us, tuned to work together.” The individual pieces (Ironwood, Jupiter, Pathways) are each genuinely differentiated. The packaging is Google’s answer to the fact that a fast chip sitting behind a slow network, managed by a generic scheduler, wastes money. Whether that packaging is worth paying for depends entirely on whether a buyer would otherwise integrate those pieces well on their own — and for most teams below frontier-lab scale, they would not.
What “AI Hypercomputer” Actually Means
Google introduced the AI Hypercomputer name in December 2023, alongside the TPU v5p announcement, to describe what it called “a groundbreaking supercomputer architecture” built on systems-level codesign rather than component-by-component upgrades. The pitch was explicit about the problem it was solving: generative AI model sizes had grown roughly tenfold in parameters per year for five straight years, training runs for the largest models could stretch across months, and treating compute, storage, networking, and software as independent purchases created bottlenecks that no single faster chip could fix on its own.
The metric Google uses to justify the bundling is “goodput” — the share of a cluster’s theoretical compute that actually turns into useful training or inference progress, after accounting for stalls, checkpoint overhead, network contention, and hardware failures. A chip can have excellent peak FLOPS on a spec sheet and still deliver poor goodput if the network around it is slow or the scheduler restarts jobs badly after a failure. Google’s argument for AI Hypercomputer is that optimizing goodput requires owning and tuning the whole stack, not just the accelerator.
Compute: TPUs and Nvidia GPUs, Sold Side by Side
The detail that often gets lost in TPU-versus-GPU framing is that Google Cloud sells both under the same AI Hypercomputer umbrella. On the TPU side, Ironwood pods scale to thousands of chips for training and inference. On the GPU side, Google offers A4 virtual machines built on Nvidia B200 GPUs today, with A5X virtual machines based on Nvidia’s next-generation Vera Rubin platform positioned to arrive later in 2026 — Google says it will be “among the first” cloud providers to offer Vera Rubin NVL72 instances once that hardware ships.
That dual-track compute lineup is a deliberate business choice, not an oversight. Some customers’ training code, libraries, or existing CUDA investments make Nvidia GPUs the practical choice regardless of TPU price-performance; others are comfortable with JAX or PyTorch/XLA and want Google’s custom silicon economics. AI Hypercomputer lets Google capture both groups of customers under one contract, one support relationship, and — where workloads allow — one orchestration layer, rather than forcing a single hardware bet.
The Fabric Underneath: Jupiter Networking and Storage
Compute is only as useful as the network that connects it. The original AI Hypercomputer announcement named the Jupiter data center network specifically as part of the “performance-optimized hardware” layer, alongside liquid cooling and high-density rack design. Google’s broader Cross-Cloud Network backbone — which it says over 65% of the Fortune 100 already use, moving more than 27 exabytes of data per month — sits above Jupiter for traffic that needs to move between regions, clouds, or on-premises systems. Google’s custom Titanium offload chips add a hardware root of trust so that security and networking processing happen off the host CPU, which matters when thousands of machines are packed into one training job.
On storage, AI Hypercomputer documentation points to Google Cloud Managed Lustre and Cloud Storage Rapid as the high-throughput options meant to keep data-hungry accelerators fed, reducing the I/O stalls that would otherwise show up as lost goodput. Google’s public materials describe these as positioned for AI workloads but don’t publish detailed AI Hypercomputer-specific throughput numbers, so the storage layer is best understood as “fast enough not to bottleneck the accelerators” rather than a headline feature in its own right.
The Software Layer: GKE, Pathways, JAX, and XLA
The software layer is where the “sold as one system” framing is most concrete. Google Kubernetes Engine (GKE), built on open-source Kubernetes, is positioned as the default orchestrator and is described as supporting clusters up to roughly 130,000 nodes; Cluster Director and Slurm integration serve teams that prefer a traditional HPC-style scheduler instead, with pre-deployment health checks and always-on cluster monitoring. For training specifically, Pathways and the Pallas kernel layer coordinate work across many TPU or GPU hosts as a single logical job — the mechanics of which this site already covered when it looked at Pathways and multi-slice training in isolation.
Framework support runs through JAX, PyTorch, and TensorFlow, with JAX and PyTorch both compiled through OpenXLA so the same model code can target TPUs or GPUs without a rewrite. Google also points to “TorchTPU” native PyTorch support as an attempt to remove what it calls the TPU learning curve for teams that don’t want to learn JAX at all. On the serving side, vLLM, GKE Inference Gateway, and a model-loading cache (Google’s “Rapid Cache”) handle inference-specific concerns like time-to-first-token and fast model cold-starts — separate problems from training throughput, but bundled under the same AI Hypercomputer name.
How Google Sells It: Consumption Models
AI Hypercomputer is not a flat-rate product; it is a pricing framework layered on top of standard Compute Engine billing. Google advertises Spot VMs for batch or fault-tolerant jobs at discounts of up to 91% off on-demand pricing, a Dynamic Workload Scheduler that can cut costs up to 50% for jobs with flexible start times (with separate Flex Start and Calendar modes), and committed-use discounts of up to 50% for customers willing to commit to sustained usage. There is no published flat price for “AI Hypercomputer” itself — pricing is quote-based and depends entirely on which accelerators, commitment level, and consumption mode a customer chooses.
Packaged Stack vs. Assemble-It-Yourself
Dimension
AI Hypercomputer (Google Cloud)
Self-assembled / multi-vendor infrastructure
Hardware sourcing
Single vendor relationship covering TPUs and Nvidia GPUs
Often multiple vendors for chips, networking gear, and storage
Integration work
Google pre-tunes the stack; customer mainly configures, doesn’t integrate
Customer or systems integrator owns tuning compute, network, and storage together
Flexibility
Constrained to Google Cloud’s supported accelerators and regions
Can mix any vendor’s hardware, including on-premises
Time to first training run
Fast — provisioning and orchestration are largely pre-built
Slower — cluster design and validation happen before any training starts
Cost model
Pay-as-you-go, spot, or committed-use discounts on a cloud bill
Capital expenditure for owned hardware, or negotiated multi-vendor cloud contracts
Pros and Cons
Pro: Removes the integration burden of matching accelerators, networking, and schedulers — a real cost for teams without a dedicated infrastructure org
Pro: Covers both TPU and Nvidia GPU paths, so a customer isn’t locked into one chip architecture at the account level
Pro: Consumption flexibility (spot, committed-use, Dynamic Workload Scheduler) gives real levers to control cost on large jobs
Con: “AI Hypercomputer” is a marketing umbrella, not a single SKU — there is no one price or one thing to buy, which makes vendor comparison harder
Con: Ties a customer’s performance-optimized experience to Google Cloud specifically; moving a Pathways- or GKE-tuned workload elsewhere requires real rework
Con: Most of the published performance and ROI figures are Google’s own benchmarks or customer testimonials, not independently verified results
Who Should Pay Attention to This
Teams training or serving large models who currently stitch together compute, networking, and orchestration themselves are the clearest fit — the pitch is specifically that doing this in-house wastes goodput that a pre-tuned stack would capture. Platform and infrastructure leads evaluating cloud AI spend should care because the consumption-model choices (spot vs. committed-use vs. Dynamic Workload Scheduler) can change total cost by tens of percent on large training runs. Robotics and simulation teams are worth calling out separately: Google’s own materials cite a humanoid-robot reinforcement-learning workload where cycle time dropped from roughly 24 hours to under one hour running on GPU VMs with Nvidia Isaac Sim, which signals that AI Hypercomputer is being positioned beyond pure LLM training. Teams already committed to a specific chip vendor or running at a scale too small to benefit from cluster-level tuning have less reason to care about the packaging itself, even if they still use individual Google Cloud services.
Bottom Line
AI Hypercomputer is Google Cloud’s attempt to sell integration, not just hardware. The underlying components — Ironwood TPUs, Nvidia GPU instances, the Jupiter network, Pathways, GKE — are each real and independently useful, and several of them hold up well against competitors on their own technical merits. What AI Hypercomputer adds on top is Google’s claim that pre-tuning those pieces together produces more usable compute per dollar than buying them separately would. That claim is plausible and consistent with how large-scale ML infrastructure actually behaves, but it is also unverifiable from the outside without running the comparison yourself — which is, not coincidentally, exactly the kind of commitment Google’s pricing and consumption options are designed to make easier to start.
FAQ
Is AI Hypercomputer a single product you can buy? No. It’s Google Cloud’s name for a bundle of compute, networking, storage, and software offerings that are designed and sold together. There is no single AI Hypercomputer SKU or flat price; customers configure and pay for the specific accelerators, consumption model, and services they use.
Does Google Cloud sell Nvidia GPUs as well as its own TPUs under this umbrella? Yes. AI Hypercomputer explicitly includes Nvidia GPU virtual machines (A4 with B200 GPUs, with A5X based on Nvidia’s Vera Rubin platform planned for later in 2026) alongside Google’s own Ironwood and earlier-generation TPUs.
How is this different from just renting a TPU or GPU VM on Google Cloud? Renting a VM gets you the accelerator. AI Hypercomputer is Google’s framing for the fact that the VM is pre-paired with a tuned network (Jupiter), orchestration (GKE or Cluster Director), and frameworks (JAX/XLA, optimized PyTorch) designed to reduce the gap between a chip’s theoretical performance and what a real training or inference job actually achieves.
Is this comparable to what AWS or Microsoft Azure offer? Directionally, yes — all major clouds now sell integrated AI infrastructure stacks rather than bare accelerators. The specific components differ: Google’s version centers on its own TPU silicon plus Nvidia GPUs, the Jupiter network, and Pathways/GKE, while competitors combine their own custom silicon or Nvidia hardware with their own networking and orchestration layers. This article does not attempt a side-by-side benchmark against those offerings, since Google does not publish comparative figures.
What is “goodput,” and why does Google keep mentioning it? Goodput is the share of a cluster’s theoretical compute capacity that produces actual training or inference progress, after subtracting time lost to network stalls, checkpointing, restarts, and failures. It’s the metric Google uses to justify bundling hardware and software together, since a fast chip behind a slow or poorly orchestrated system can still produce low goodput.
Small businesses that issue company laptops and phones eventually run into the same question: how do you enroll, configure, secure, and — when a device is lost or an employee leaves — wipe dozens or hundreds of endpoints without a dedicated IT department doing it by hand? Mobile device management (MDM) software is the answer, and three names dominate the conversation in 2026: Jamf, Microsoft Intune, and Kandji (which rebranded to Iru in October 2025). We pulled pricing and feature details directly from each vendor’s own site to see how they actually compare for a small business buyer, and the honest answer is that the field has shifted in ways that matter.
The single biggest thing to understand before you shop: Jamf is still built almost entirely around Apple hardware, Microsoft Intune is cross-platform by design because it’s part of the Microsoft 365 and Entra ecosystem, and Kandji — long marketed as the “Apple-only” alternative to Jamf — has itself moved to cross-platform management under its new Iru brand. If your business is a mixed fleet of Windows and Mac, that last point changes the calculus considerably.
At a Glance
Vendor
Published Price
Free Trial
Platform Focus
Best For
Jamf (Jamf for Mac / Jamf Now)
Jamf for Mac: $12.50/device/mo (25-device minimum, billed annually). Jamf Now: from $4/device/mo for under 25 employees; first 3 devices free.
14-day trial advertised site-wide; Jamf Now free for up to 3 devices
Apple only (macOS, iOS, iPadOS, tvOS; Jamf for Mobile adds Android)
Apple-only or Apple-majority small businesses
Microsoft Intune
Plan 1: $8/user/mo standalone, or bundled into Microsoft 365 Business Premium at $22/user/mo (with Teams). Plan 2 add-on: $4/user/mo. Intune Suite: $10/user/mo.
Trial links shown for Plan 2 and add-ons; not explicitly stated for Plan 1
Businesses already on Microsoft 365 with mixed-OS fleets
Kandji (now Iru)
Not published; custom quote based on modular licensing (computers managed, mobile devices enrolled, SSO users)
14-day free trial offered for Endpoint Management and related modules
Cross-platform as of its Iru rebrand (Apple, Windows, Android); Apple remains its historical strength
Apple-heavy businesses that want room to add Windows/Android later
Short Verdict
If every device in your office has an Apple logo on it, Jamf’s purpose-built Apple tooling and Jamf Now’s small-business pricing (starting at $4/device/month, with the first three devices free) make it the easiest entry point. If your small business already runs Microsoft 365 — and most do — Intune is effectively “free” in the sense that it’s bundled into Microsoft 365 Business Premium at $22/user/month alongside email, Office apps, and Entra ID security, and it’s the only one of the three with genuine first-class support for Windows alongside Apple and Android. Kandji’s 2025 rebrand to Iru muddies its old “simple Apple MDM” positioning: it now markets itself as a cross-platform identity-and-endpoint platform with AI-driven compliance automation, but it no longer publishes per-device pricing, so you’ll need a sales call to know what it costs.
What Each One Is
Jamf has built its entire business around Apple device management since before Apple Business Manager existed in its current form. Jamf’s current small-business lineup includes Jamf Now (aimed at organizations under 25 employees, with per-device pricing starting at $4/month), and the Jamf Business Plan/”Jamf for Mac” and “Jamf for Mobile” tiers for larger Apple fleets, priced at $12.50 per macOS device per month (with mobile pricing requiring a sales conversation). Jamf’s pitch is depth: zero-touch provisioning for Mac, iPhone, iPad, and Apple TV, automated security baselines tied to industry benchmarks, and app lifecycle management through Self Service+.
Microsoft Intune is Microsoft’s cloud-based endpoint management service, sold standalone or as part of Microsoft 365 and Enterprise Mobility + Security bundles. Because it’s built into the same identity layer (Microsoft Entra ID) that powers Microsoft 365 sign-in, Intune’s biggest practical advantage for a small business is that it isn’t a separate purchase if you’re already paying for Microsoft 365 Business Premium — device management, compliance policies, and app protection are already included at $22/user/month (with Teams) or $18.79/user/month (without). Buy it standalone and Intune Plan 1 runs $8/user/month, with Plan 2 ($4 more) and the full Intune Suite ($10/user/month) adding advanced analytics, remote help, and endpoint privilege management.
Kandji built its reputation as the design-forward, Apple-only alternative to Jamf, popular with startups that wanted modern MDM without Jamf’s enterprise complexity. That changed in October 2025, when the company announced it was rebranding to Iru and repositioning as a broader “identity security and management” platform. According to Iru’s own site, the platform now explicitly covers Apple, Windows, and Android endpoints, plus workforce identity and compliance automation features. The pricing page no longer lists a flat per-device rate; it describes “modular licensing” scaled to computers managed, mobile devices enrolled, and SSO users, available only via custom quote.
Pricing Breakdown
Plan
Price (as published)
Notes
Jamf Now
From $4/device/month
For businesses under 25 employees; first 3 devices free; Apple only
Jamf for Mac
$12.50/device/month
Billed annually, 25-device minimum
Jamf for Mobile
Not published
“Contact Us” — 25-device minimum, billed annually
Intune Plan 1 (standalone)
$8/user/month
Also included in Microsoft 365 E3/E5 and EMS E3/E5
Intune Plan 2 (add-on)
+$4/user/month
Requires Plan 1
Intune Suite
$10/user/month
Bundles advanced add-ons
Microsoft 365 Business Premium
$22/user/month (with Teams)
Includes Intune, Entra ID, Office apps, email — no separate MDM line item
Kandji / Iru
Custom quote only
Scaled by devices managed, mobile devices enrolled, SSO users; no published rate card as of this writing
Pros
Jamf: Deepest Apple-specific tooling of the three; Jamf Now is genuinely built for small teams with transparent entry pricing and a free tier for up to 3 devices; strong app lifecycle and Self Service experience for end users.
Microsoft Intune: True cross-platform support (Windows, macOS, iOS/iPadOS, Android, Linux) from a single console; often effectively “already paid for” if you’re on Microsoft 365 Business Premium; tight integration with Entra ID conditional access and Microsoft 365 compliance tools; published, transparent per-user pricing.
Kandji / Iru: Still carries Kandji’s reputation for a clean admin UI and fast time-to-setup (“fully configured in a few hours” per Iru’s own site); has expanded beyond Apple-only to cover Windows and Android, so a growing small business isn’t boxed in; adds AI-assisted compliance automation and an “Adaptive Evidence Map” for audit readiness.
Cons
Jamf: Apple-only — a non-starter the moment you have Windows PCs in the fleet; Jamf for Mobile and full Jamf Pro enterprise pricing aren’t published, so budgeting requires a sales call; the $12.50/device/month Mac rate has a 25-device minimum that may not suit the smallest teams.
Microsoft Intune: Licensing is genuinely confusing — Plan 1, Plan 2, Intune Suite, and bundled-in-M365 versions all have different capabilities, and the page itself warns that pricing “may vary by Microsoft agreement”; several advanced features (Remote Help, Endpoint Privilege Management, Advanced Analytics) are separate paid add-ons on top of Plan 1.
Kandji / Iru: No public pricing at all as of this writing, which makes it hard to even shortlist against Jamf and Intune without engaging sales; the October 2025 rebrand and platform expansion mean reviews and comparisons written before late 2025 describe a narrower, Apple-only product that no longer fully reflects what’s being sold today.
Who It’s a Good Fit For
Choose Jamf if you’re an all-Apple shop — a design agency, a dev shop standardized on MacBooks, a retail business running iPads at the point of sale — and you want management tooling built specifically around how Apple devices actually work, with Jamf Now as a low-cost on-ramp for very small teams.
Choose Microsoft Intune if your business already runs on Microsoft 365, especially Business Premium, or if your fleet is a realistic mix of Windows and Apple devices. The fact that device management, conditional access, and compliance policy are already part of a subscription you’re probably paying for anyway is hard to beat on cost-per-value for a small business.
Consider Kandji / Iru if you liked Kandji’s Apple-first simplicity but want a platform that won’t force a switch later as you add Windows or Android devices — just budget time for a sales conversation, since there’s no self-serve pricing to compare against a credit card swipe with Jamf Now or Intune.
Who Should Look Elsewhere
A business that needs to budget precisely without a sales call should be cautious with Kandji/Iru, since nothing is published. A mixed-OS shop should think twice about Jamf, since it offers no meaningful Windows management. And a very small, all-Apple team that doesn’t want to touch Microsoft 365 licensing at all may find Jamf Now simpler to reason about than Intune’s multi-tier plan structure.
Bottom Line
There’s no universal winner here — the right MDM for a small business in 2026 depends almost entirely on what’s already in your device closet and your software stack. Jamf remains the specialist for Apple-only fleets. Microsoft Intune is the practical default for anyone already paying for Microsoft 365, and the only one of the three with real cross-platform parity out of the box. Kandji’s transformation into Iru is the wild card: it’s now chasing the same cross-platform, identity-plus-endpoint positioning as Intune, but without Intune’s Microsoft 365 bundling advantage or Jamf’s transparent small-business pricing — so get a quote before you assume it fits your budget.
If compliance reporting and audit readiness are a bigger driver for your business than device management itself, it’s worth also reading our comparison of Vanta, Drata, and Secureframe for SOC 2 and ISO 27001 automation, since MDM enrollment and device compliance policies are typically one control area those platforms check for.
FAQ
Is Kandji still called Kandji? No — as of October 2025, Kandji rebranded to Iru. The product still manages Apple devices but the company now also markets Windows and Android endpoint management and identity features under the Iru name. Some retailers, documentation, and update feeds still reference “Kandji” during the transition.
Can I use Microsoft Intune to manage Mac and iPhone devices, or is it Windows-only? Intune manages Windows, macOS, iOS/iPadOS, Android, and Linux from one console. It’s genuinely cross-platform, not a Windows tool with bolted-on Apple support.
Do I need to buy Intune separately if I already have Microsoft 365 Business Premium? No. Microsoft 365 Business Premium (currently $22/user/month with Teams, billed annually) includes Intune for device management, so a small business already on that plan doesn’t pay for MDM as a separate line item.
Does Jamf support Android or Windows devices at all? Jamf for Mobile extends to Android for mobile threat defense and device management, but Jamf’s core product line — Jamf Pro, Jamf Now, Jamf for Mac — is built for Apple’s operating systems (macOS, iOS, iPadOS, tvOS, visionOS, watchOS). It has no meaningful Windows desktop management.
Why doesn’t Kandji/Iru publish pricing anymore? Its current pricing page describes “modular licensing” that scales with computers managed, mobile devices enrolled, and SSO users, available only through a custom quote. This is a change from the simpler, more transparent per-device pricing MDM buyers may remember from Kandji’s earlier years.
If you spend your day jumping between apps, files, and snippets of text, a keyboard launcher can save you dozens of clicks an hour. Three names dominate the conversation in 2026: Raycast and Alfred on the Mac, and Microsoft’s free PowerToys Run on Windows. They solve the same basic problem — get to anything without touching the mouse — but they take very different approaches to pricing, extensibility, and platform support. Here’s how they actually compare, based on what each vendor states on its own site as of November 2026.
At a Glance
App
Starting Price
Free Plan?
Platform
Best For
Raycast
Free; Pro from $10/mo ($96/yr)
Yes
macOS (native); Windows app also available
Mac users who want an extensible launcher with optional AI features
Alfred
Free; Powerpack one-time upgrade from £34
Yes (core app)
macOS only
Mac users who prefer a one-time purchase over a subscription
PowerToys Run
Free
Yes (fully free and open source)
Windows only
Windows users who want a free, no-subscription launcher
Short Verdict
These three aren’t really head-to-head rivals in the way the headline suggests — they’re the default launcher pick for whichever operating system you’re on. On the Mac, Raycast is the more modern, AI-leaning option with a free tier generous enough for most people and a Pro subscription for power users; Alfred is the veteran, with a free core app and a one-time Powerpack purchase for its famous Workflows automation system. On Windows, PowerToys Run is the obvious choice simply because it’s the only one of the three available there — and it costs nothing, since it’s an open-source module of Microsoft’s PowerToys utility suite.
What Each App Is
Raycast
Raycast started as a Mac-only “Spotlight replacement” built around a Store of community and first-party extensions, and it has grown into a broader productivity hub. According to raycast.com, the free plan includes the core launcher, Quicklinks, a calculator, Snippets, basic Window Management, and access to thousands of extensions with developer tooling to build your own. Clipboard History on the free plan is capped at three months of history; Raycast Pro removes that cap, adds Raycast AI (with a monthly AI-credit allowance and the ability to bring your own API key), custom Window Management commands, Cloud Sync, Dictation, custom themes, and a translator. Higher Pro-tier plans (Plus and Max) add access to top-tier AI models. Notably, Raycast has also shipped a public Windows app — distributed via the Microsoft Store and WinGet — that covers the launcher, file search, clipboard history, snippets, Quicklinks, a calculator/emoji picker, hotkeys, Quick AI/AI Chat, and even a game launcher for Steam, Epic, Battle.net, and GeForce Now. Raycast’s own site describes Cloud Sync as still “upcoming” on Windows, so the Windows build is newer and not yet at full feature parity with the Mac version.
Alfred
Alfred is the longest-running of the three and remains macOS-only, supporting macOS 10.14 and later on both Intel and Apple Silicon. Per alfredapp.com, the core app — app launching, file search, web search, and basic Snippets — is “free for you to download and use forever, with no strings attached.” The paid Powerpack upgrade is what long-time Mac users actually associate with Alfred: it unlocks Workflows (chains of hotkeys, keywords, and actions, including workflows shared by the community), custom themes, and other extras. Alfred’s free tier also includes a searchable Clipboard History covering text, images, file paths, and hex color codes. At the time of writing, Alfred 6 is in preview with no firm release date beyond “this autumn,” and the current stable release is Alfred 5.
PowerToys Run
PowerToys Run is a module inside Microsoft’s free, open-source PowerToys utility collection for Windows, documented at learn.microsoft.com. It’s a quick launcher (default hotkey Alt+Space) for apps, files, running processes, calculator and unit-conversion queries, system commands (shutdown, lock, empty recycle bin, and more), hash/GUID generation, and web searches — all through a modular plugin system where each plugin has its own activation prefix (for example, = for the calculator or ? for Windows Search). Microsoft’s documentation also flags that PowerToys Run is “getting a v2 upgrade,” pointing to a newer, related tool called Command Palette as its evolution. As of this writing, Microsoft Learn’s Command Palette page doesn’t explicitly state that it replaces or retires PowerToys Run, and PowerToys Run itself remains available and documented — so treat “Command Palette is the successor” as a direction Microsoft is heading in, not a completed migration.
Pricing Breakdown
Plan
Raycast
Alfred
PowerToys Run
Free tier
Core launcher, extensions, Snippets, basic Window Management, 3-month Clipboard History
Powerpack: one-time from £34 (Single License) or £59 (Mega Supporter, includes free lifetime upgrades) — unlocks Workflows and themes
None — no paid tier exists
Higher tiers
Plus ($20/mo, $192/yr) and Max ($50/mo, $480/yr) add top-tier AI models; Teams plans also available
Alfred Remote (iOS companion) sold separately; no published family-pack price
N/A
Pros
Raycast: Generous free tier; large extension store; built-in AI features for Pro subscribers; now available on Windows too, so teams with mixed OS setups can use one tool.
Alfred: One-time Powerpack purchase instead of a subscription; mature Workflows ecosystem with a large community library; lightweight and fast on older Macs.
PowerToys Run: Completely free and open source; no account or sign-in required; actively maintained by Microsoft as part of PowerToys; modular plugins keep searches fast and specific.
Cons
Raycast: AI features and unlimited clipboard history require a subscription; the Windows build is newer and still missing some Mac features like Cloud Sync.
Alfred: No official Windows version; Powerpack is a separate purchase on top of the free app, and its price isn’t shown in US dollars on the main site (it’s listed in GBP); window-management features are not a headline capability the way they are for Raycast.
PowerToys Run: Windows-only, so it’s no help on a Mac; Microsoft’s own documentation signals it may eventually be superseded by Command Palette, which could mean slower future development for Run itself.
Who It’s a Good Fit For
Raycast fits Mac users who want extensions, AI-assisted actions, and don’t mind paying a monthly fee once they outgrow the free tier — and, increasingly, mixed Mac/Windows teams that want one launcher across both.
Alfred fits Mac users who’d rather pay once than subscribe, and who want deep, scriptable Workflows without recurring costs.
PowerToys Run fits any Windows user, full stop — there’s no cost barrier, and it’s the closest Windows equivalent to what Spotlight, Raycast, or Alfred do on a Mac.
Who Should Look Elsewhere
If you’re on Windows and want deep AI-chat integration baked into your launcher today, Raycast’s Windows build is catching up but isn’t yet at full Mac parity — check its changelog before assuming a Mac-only feature exists there.
If you want window-snapping and tiling as a primary feature rather than a search tool, none of these three markets that as its core focus; Raycast offers basic and Pro-tier custom Window Management commands, but dedicated window managers may serve you better.
If a one-time cost matters more than a subscription and you’re not on a Mac, PowerToys Run is already free — there’s no Alfred-style purchase decision to make on Windows.
Bottom Line
Your operating system decides most of this comparison for you. On Windows, PowerToys Run is a safe, zero-cost default, with Microsoft signaling that Command Palette is where future launcher development is headed. On the Mac, the choice is really about business model and ecosystem: Alfred rewards you once and lets you own the automation layer outright, while Raycast’s subscription buys you a faster-moving product with AI built in and, as of 2026, a genuine (if still-maturing) presence on Windows as well.
FAQ
Is PowerToys Run really free, with no paid upgrade?
Yes. Microsoft’s own documentation describes it as a free, open-source utility distributed as part of the PowerToys suite, with no premium tier.
Can I use Alfred or Raycast on Windows?
Alfred is macOS-only with no Windows version. Raycast, however, now ships a public Windows app (via the Microsoft Store or WinGet) alongside its original Mac app, though some features such as Cloud Sync are still listed as upcoming on Windows.
Do I need the paid tier to get extensions or workflows?
No. Raycast’s free plan includes access to its extension store, and Alfred’s free app includes basic Snippets; Alfred’s advanced Workflows automation specifically requires the paid Powerpack upgrade, while Raycast’s AI features and unlimited clipboard history specifically require a Pro subscription.
Is PowerToys Run being replaced by Command Palette?
Microsoft’s documentation describes Command Palette as PowerToys Run’s “v2” evolution, but as of this writing PowerToys Run is still documented and available. Treat Command Palette as the direction Microsoft is heading, not a confirmed retirement date for Run.
Which one has AI features built in?
Only Raycast, among these three, advertises built-in AI: Raycast AI and AI Chat are available on paid Pro plans (and above) on both Mac and Windows. Alfred and PowerToys Run, per their own sites, don’t list AI chat or generation features.
Encryption at rest protects data on disk. TLS protects data on the wire. Neither protects data while a program is actually computing on it in RAM — at that point, it typically sits in plaintext, visible to the host operating system, the hypervisor, and anyone with sufficiently privileged access to the physical machine, including the cloud provider running it. Confidential computing closes that specific gap using hardware-enforced trusted execution environments (TEEs): isolated regions of a CPU where code and data stay encrypted and inaccessible to everything outside the enclave, including a compromised or merely curious host. It’s no longer a research curiosity — Intel TDX, AMD SEV-SNP, and AWS Nitro Enclaves are all shipping in production cloud infrastructure today, and real applications like Signal’s backend already depend on it.
At a Glance
Attribute
Detail
What it protects
Data in use — while it’s being actively processed in memory, not just stored or transmitted
Core mechanism
A trusted execution environment (TEE): hardware-enforced isolation that hides a workload’s memory and execution even from the hypervisor and host OS
How trust is verified
Attestation — a cryptographic proof that specific, unmodified code is running inside a genuine, correctly-configured TEE before you hand it anything sensitive
Standards body
Confidential Computing Consortium (CCC), an open community under the Linux Foundation with 40+ member organizations
Major implementations
Intel SGX (process-level) and TDX (VM-level); AMD SEV-SNP (VM-level); AWS Nitro Enclaves (isolated companion VM); ARM TrustZone / CCA
Known production use
Signal’s backend has run on confidential-computing-backed secure enclaves since 2021; Signal’s earlier private contact discovery service specifically used Intel SGX
Short Verdict
Confidential computing is the right tool when your threat model specifically includes the infrastructure operator — a cloud provider, a hypervisor bug, or a malicious insider with root access to the host — and you need a technical guarantee, not just a contractual one, that they can’t read the data your workload is processing. It is the wrong tool to reach for as a general security upgrade: enclaves add real performance and engineering overhead, attestation infrastructure has to be built and verified correctly to mean anything, and the space has genuinely different maturity levels depending on whether you need process-level isolation (SGX, with real production history but also real vulnerabilities) or can accept the coarser, easier-to-adopt VM-level model (TDX, SEV-SNP, Nitro Enclaves) that most 2026 cloud confidential-computing products actually ship.
The Problem: Data in Use Is the Gap Encryption Doesn’t Cover
Security teams have had mature answers for data at rest (disk and database encryption) and data in transit (TLS) for decades. Data in use — the state a value is in from the moment it’s decrypted into memory to process it until it’s either discarded or re-encrypted — has historically had no equivalent default protection. In a public cloud, that gap is specifically the host’s hypervisor, kernel, and anyone with administrative access to the physical machine: all of them can, in principle, read a VM’s memory directly, regardless of how well the data was encrypted before it arrived or after it leaves. The Confidential Computing Consortium frames the category’s purpose plainly: “Confidential Computing protects data while it’s in use,” closing the one state storage and network encryption leave open.
How Trusted Execution Environments Actually Isolate a Workload
A TEE is a hardware-enforced enclave: a CPU feature that carves out an isolated execution context whose memory is encrypted and access-controlled by the processor itself, not by software running alongside it. The Confidential Computing Consortium describes this plainly — hardware-enforced enclaves create isolated execution contexts that keep running workloads hidden even from the hypervisor and cloud provider. Implementations differ meaningfully in what, exactly, gets isolated:
Intel SGX works at the process level: a single application creates an enclave inside its own address space, and the operating system, hypervisor, and every other process — even other enclaves — are explicitly untrusted. This gives the tightest isolation boundary, but it requires rewriting or specially porting an application to the SGX programming model, and comes with real memory-size limits that make lifting legacy software over painful.
Intel TDX moves the boundary up to an entire virtual machine, running in a new processor mode (SEAM) that reuses some SGX-derived attestation machinery, but trusts the guest OS and its configuration rather than isolating individual processes within it. The trade: far fewer performance and memory constraints, and legacy applications can run largely unmodified inside a “trust domain” instead of being rewritten against a special enclave API.
AMD SEV-SNP takes the same VM-level approach as TDX on AMD hardware: encrypting a virtual machine’s memory and adding integrity protection (the “SNP,” Secure Nested Paging, addition) so the hypervisor can’t tamper with guest memory contents or page mappings without detection, not just read them.
AWS Nitro Enclaves takes a structurally different approach: rather than a CPU-level encrypted-memory mode, it carves an isolated, hardened companion virtual machine out of an EC2 instance using the Nitro Hypervisor. AWS’s own documentation is specific about the isolation: the enclave has no persistent storage, no interactive shell access (you cannot SSH in), and no external network connectivity — it can only talk to its parent instance over a local secure socket — and the parent instance itself, including root or admin users on it, has no access to the enclave’s memory or data.
Every one of these mechanisms depends on attestation to be useful in practice: a cryptographic proof, generated by the hardware itself, that specific code — unmodified, with a verifiable measurement/hash — is actually running inside a genuine, correctly-configured TEE. AWS documents this concretely for Nitro Enclaves: AWS Key Management Service has built-in attestation support, so you can write a key policy that only releases a cryptographic key to an enclave whose measurement matches an expected, approved value — meaning a tampered or substituted workload simply can’t get the key, rather than relying on anyone noticing after the fact.
Real-World Use: Signal’s Backend and Private Contact Discovery
Signal is one of the most concrete, publicly documented production users of confidential computing. According to Microsoft’s own customer case study, Signal has hosted its back-end services in secure enclaves on Azure confidential computing since scaling up in 2021, citing the platform’s availability and reliability. Separately, and earlier, Signal’s own engineering blog detailed a specific use of Intel SGX for private contact discovery — the problem of letting Signal’s server tell a user which of their phone contacts also use Signal, without the server itself ever learning the user’s full contact list. Signal’s 2017 technical preview post describes running that matching logic inside an SGX enclave specifically so the server operator (Signal itself) couldn’t see the contact data it was processing, only the enclave could — a direct, concrete example of a TEE being used to make a service provider’s own infrastructure unable to read its users’ sensitive data, not just unwilling to.
Comparing the Major TEE Implementations
Implementation
Isolation granularity
Programming model impact
Maturity note
Intel SGX
Process-level (single application enclave)
Requires porting to a special enclave programming model; real memory limits
Longest production history (Signal’s 2017 contact discovery); also the most documented history of discovered vulnerabilities; Intel has deprecated it on consumer-platform CPUs
Intel TDX
VM-level (whole “trust domain”)
Minimal — legacy apps largely run unmodified inside the VM
Newer; reached smaller cloud providers starting around 2024; fewer long-running public case studies than SGX
AMD SEV-SNP
VM-level, with added integrity protection against hypervisor tampering
Minimal — standard VM workloads, no special enclave API
Documented in AMD’s own technical papers as an explicit strengthening of earlier SEV generations against active, not just passive, attacks
AWS Nitro Enclaves
Isolated companion VM carved from an EC2 instance
Low — runs as a separate, constrained Linux VM communicating over a local socket
No extra charge beyond normal EC2/KMS usage; tightly integrated with AWS KMS attestation-based key policies
Trade-offs
Process-level isolation (SGX) gives the strongest guarantee — even a compromised OS can’t read the enclave — but at real engineering cost: a special programming model, tight memory constraints, and a track record that includes a meaningful number of discovered side-channel vulnerabilities over the technology’s lifetime.
VM-level isolation (TDX, SEV-SNP, Nitro Enclaves) is dramatically easier to adopt — often requiring little or no application rewrite — but trusts a larger piece of software (the whole guest OS) than a process-level enclave does, and that larger trusted surface is the direct cost of the easier adoption path.
Attestation is not optional scaffolding — it’s the mechanism that makes any of this trustworthy to a third party. A TEE whose attestation you don’t actually verify (or whose key release isn’t gated on a specific, checked measurement) provides isolation from some threats but no cryptographic proof to anyone else that the isolation is real.
None of these guarantees survive every attack class — side-channel attacks exploiting shared hardware resources (caches, speculative execution) have repeatedly targeted SGX specifically, which is part of why the industry’s center of gravity has shifted toward the coarser but simpler VM-level model for most new deployments.
Bottom Line
Confidential computing turns “trust us” into “verify this” for the one part of the data lifecycle — active computation — that encryption at rest and in transit were never designed to cover. AWS Nitro Enclaves, Intel TDX, and AMD SEV-SNP have made this practical at the VM level with comparatively little application rewriting, which is why they’re the default entry point for most 2026 cloud confidential-computing offerings; Intel SGX remains the tightest isolation model and has real production history (Signal’s own contact-discovery design among the most concrete public examples), but at a real adoption and vulnerability-surface cost that’s pushed much of the industry toward the coarser VM-level alternatives instead. None of this matters without attestation actually being verified by whoever’s trusting it — the hardware isolation is necessary, but the cryptographic proof that the right code is running inside it is what makes the guarantee meaningful to anyone outside the enclave itself.
FAQ
Is confidential computing the same thing as encryption? No. Encryption at rest and in transit protect stored and transmitted data; confidential computing specifically protects data while it’s being actively computed on, in memory, using hardware-enforced isolation rather than cryptographic transformation of the data itself at that stage.
Can a cloud provider read data inside a TEE on its own infrastructure? The entire design goal is no — AWS’s own Nitro Enclaves documentation states explicitly that the parent instance, including its root or admin users, has no access to an enclave’s memory or data. The guarantee is only as strong as the specific implementation’s track record, though, which is why attestation and ongoing vulnerability disclosure matter.
What’s the real difference between Intel SGX and Intel TDX? SGX isolates at the level of a single process/application inside a specialized enclave programming model with tighter memory limits; TDX isolates an entire virtual machine with far fewer constraints, trusting the guest OS rather than isolating individual processes within it — trading some isolation granularity for dramatically easier adoption of existing software.
Does using a TEE protect against every attack? No. Side-channel attacks exploiting shared CPU resources like caches or speculative execution have repeatedly been demonstrated against SGX specifically, and the Confidential Computing Consortium itself notes that causality and isolation guarantees generally assume non-Byzantine, non-adversarial hardware behavior — a TEE narrows the attack surface significantly, it doesn’t eliminate every possible attack vector.
“Low-code” in 2026 no longer just means dragging form fields onto a canvas — Microsoft Power Apps, OutSystems, and Appian have all folded AI-assisted app generation directly into their platforms, while their underlying pricing and governance models remain as different from each other as ever. This piece compares what each vendor’s own pricing and product pages actually state, not what resellers or comparison sites estimate on their behalf, because two of the three publish no enterprise dollar figures at all.
At a Glance
Platform
Published pricing model
Free tier
AI app generation
Microsoft Power Apps
Premium: $20/user/month (standard), $12/user/month at a 2,000-seat minimum, billed annually. Rising to $22 / $14 on January 1, 2027. Free Developer Plan for building/testing only.
Developer Plan (free) — build and test, but production users need Premium or pay-as-you-go
Microsoft 365 Copilot chat inside apps (GA for model-driven apps, public preview for canvas apps)
OutSystems
Quote-based. No published dollar figures; priced by “Application Objects” (screens, tables, API methods) and non-anonymous end users across dev/test/production environments.
Personal Edition — free, development-only, up to 100 internal users, no uptime SLA
Quote-based, three named tiers (Standard, Advanced, Premium), priced “per user, per month, per app.” No dollar figures published.
Appian Community Edition — free access to a dedicated Appian platform instance, plus a free trial
AI Actions with monthly caps by tier: 200K (Standard), 500K (Advanced), 1M (Premium)
Short Verdict
Only Microsoft publishes real enterprise dollar figures for its platform tier — $20 or $12 per user per month for Power Apps Premium, depending on seat count — while OutSystems and Appian both keep paid enterprise pricing behind a sales conversation, driven by usage metrics (Application Objects and end users for OutSystems; users, apps, and AI Actions for Appian) rather than a flat per-seat rate. All three now sell an AI-assisted “prompt to app” story, but they differ sharply in who the platform is built for: Power Apps leans hardest into citizen developers already inside the Microsoft 365 ecosystem, OutSystems targets professional developers building complex, governed systems at scale, and Appian sits closest to traditional BPM/case-management territory with the most AI-usage metering built directly into its pricing tiers.
Microsoft Power Apps: Microsoft 365-Native, Per-User Pricing
Microsoft’s current official pricing page lists a free Developer Plan (three developer environments, 750 automation flows a month) for building and testing only — production users need a paid license. The paid tier is simply called Premium: $20 per user per month on standard terms, or $12 per user per month with a 2,000-license minimum arranged through Microsoft sales, both billed annually. Microsoft has already announced that both prices rise by $2 on January 1, 2027 — to $22 and $14 respectively — while existing subscriptions keep their current price through the end of their current term. Microsoft separately sells a Dataverse database capacity add-on at $40 per GB per month for teams that outgrow their plan’s included storage.
The platform’s licensing history is genuinely more tangled than “one price”: Microsoft previously sold a separate “per-app” plan (cheaper for a user who only needs one specific app rather than unlimited apps), and officially discontinued it for new customers on January 2, 2026 — though it later clarified the SKU would return for purchase through the Cloud Solution Provider (CSP) channel specifically. Existing Enterprise Agreement and CSP customers were explicitly told they face no disruption and can keep renewing; only new MPSA customers were given a 60-day migration window after their current agreement ends. Some Microsoft 365 and Dynamics 365 subscriptions also bundle limited Power Apps capability directly, which is Microsoft’s own stated reason the per-app/per-user split exists at all — to let organizations mix licenses across users who already have some entitlement through another Microsoft product and users who need the standalone Premium plan.
On governance, Power Apps’ story is tightly coupled to the rest of Power Platform (Dataverse security roles, environment-level data loss prevention policies, and Microsoft Entra ID) rather than a bespoke low-code governance layer — a natural fit for organizations already standardized on Microsoft 365 and looking for citizen-developer tools their IT team can govern with the same identity and compliance tooling they already run.
OutSystems: Quote-Based, Sized by Application Complexity
OutSystems publishes no dollar pricing at all on its official pricing page. Instead, it names two offerings: the “OutSystems Agentic Systems Platform” as its recommended paid tier, and “OutSystems Personal Edition” as a genuinely free option for individual learning — development-only, hosted on OutSystems Cloud, business-hours (8×5) support, up to 100 internal users, and explicitly no uptime guarantee. The paid tier starts at a minimum of 100 internal users and adds optional paid add-ons: 24×7 support, a 99.95% uptime upgrade over the included 99.5%, SOC 2 Type II and PCI DSS certifications, and additional runtime environments.
What actually drives the quote is OutSystems’ own documented metric: “Application Objects” — screens, database tables, and API methods counted across your apps — combined with the number of non-anonymous end users. OutSystems states a typical medium-sized application runs to roughly 150 Application Objects, giving prospective buyers at least a rough mental model for scoping cost before talking to sales, even without a published rate card. OutSystems markets itself explicitly toward professional developers building and governing complex, mission-critical systems at scale, with its 2026 AI push framed around agentic development rather than citizen-developer simplicity: prompt-to-app generation, building and governing AI agents alongside traditional apps, an “Agent Workbench” for coordinating agents and apps together, and a “Mentor” agentic coding tool aimed at professional developers rather than end users building their own simple apps. (Note: we found no OutSystems-published product or pricing tier actually named “Genie” as of this writing — if that naming exists, it isn’t on the official pricing or product pages reviewed here, so treat any reference to it with caution until confirmed directly with OutSystems.)
Appian: Named Tiers, Still Quote-Based, with AI Metered by Tier
Appian’s official pricing page is more structured than OutSystems’ but equally free of dollar figures: three named tiers — Standard, Advanced, and Premium — each explicitly priced “per user, per month, per app,” with the page inviting a free trial or a sales conversation for an actual quote rather than listing a rate. What differs concretely between tiers is usage ceilings, not features in a binary sense: Standard includes 5 RPA bots, a single external data source, one portal per app, and a monthly AI Action cap of 200,000; Advanced raises that to 25 bots, unlimited portals, and 500,000 AI Actions a month; Premium removes the RPA bot cap and record-row limit entirely and raises the AI Action ceiling to 1,000,000 a month. Appian backs its Standard/Advanced/Premium cloud service with a published SLA of 99.8–99.99% uptime and a Recovery Point Objective of one minute, with Recovery Time Objective as low as four minutes on higher tiers.
Crucially, Appian Community Edition — described on the official pricing page as free access to a dedicated Appian platform instance — does still exist as of this writing, alongside a separate free trial offer for prospective enterprise customers. Appian’s governance story leans on its roots in business process management and case management: process models, SLAs, and audit trails are first-class platform concepts rather than add-ons, which fits its positioning closer to regulated, process-heavy enterprise workflows than to broad citizen-developer self-service. Appian also publishes an explicit service commitment — the “Appian Guarantee” — promising a first application delivered within 8 weeks or less, a framing aimed squarely at enterprise buyers evaluating implementation risk up front.
Citizen Developers vs. Professional Developers
All three vendors now claim to serve both audiences, but their center of gravity differs. Power Apps remains the most citizen-developer-friendly of the three by default, because its canvas-app model and deep Microsoft 365/Teams integration let a business user build a working app with minimal governance friction — the trade-off being that scaling those apps into mission-critical, highly governed systems typically means layering on Power Platform’s environment and DLP tooling deliberately, not something the citizen-developer experience enforces by default. OutSystems is positioned the other way: its Application Object-based pricing and emphasis on professional developers, agentic coding assistance, and enterprise-grade runtime options (on-premises, private cloud, sovereign/regulated cloud) target teams building and maintaining complex systems with dedicated engineering ownership. Appian sits between the two in audience but closest to OutSystems in governance seriousness, with its process-and-case-management heritage, tiered RPA and AI-Action ceilings, and BPM-flavored audit and SLA guarantees aimed at enterprise IT and operations teams rather than ad hoc business-user app building.
Comparison
Dimension
Power Apps
OutSystems
Appian
Pricing transparency
Published per-user dollar amounts
Quote-based; sized by Application Objects + end users
Quote-based; three tiers differentiated by usage caps
Free option
Developer Plan (build/test only)
Personal Edition (dev-only, 100 users, no SLA)
Community Edition (dedicated free instance) + free trial
Primary audience
Citizen developers inside Microsoft 365
Professional developers, enterprise-scale systems
Enterprise BPM/case management teams
AI app generation
Copilot chat embedded in apps (GA/model-driven, preview/canvas)
Price transparency alone should rule out exactly none of these platforms — it mainly tells you how each vendor prefers to sell. Power Apps is the easiest to budget for from a public page alone and the most natural fit if you’re already deep in Microsoft 365; OutSystems and Appian both require an actual sales conversation to get real enterprise numbers, but publish enough about how those numbers are derived (Application Objects and end users; or tiered users/apps/AI-Action caps) to scope a rough estimate first. The more consequential decision is audience and governance fit: pick Power Apps for citizen-developer breadth inside a Microsoft shop, OutSystems for professional-developer-owned systems that need to scale and be governed rigorously, and Appian for process-heavy, compliance-conscious enterprise workflows where BPM-style audit trails and SLAs matter as much as the app-building experience itself.
FAQ
Is the Power Apps per-app plan gone for good? It was officially end-of-sale for new customers starting January 2, 2026, with existing Enterprise Agreement and CSP customers unaffected and able to keep renewing. Microsoft later clarified the SKU would become purchasable again through the CSP channel specifically — check current availability with a Microsoft licensing partner before assuming either way.
Does Appian still offer a free Community Edition in 2026? Yes, as of this writing Appian’s official pricing page still lists Community Edition — free access to a dedicated Appian platform instance — separately from its paid Standard/Advanced/Premium tiers and its free trial offer.
Why don’t OutSystems and Appian publish enterprise prices? Both vendors price enterprise deployments against usage metrics that vary enormously by customer — Application Objects and end users for OutSystems, and users/apps/AI-Action volume across named tiers for Appian — which they state cannot be reduced to one list price, unlike Power Apps’ flat per-user-per-month figure.
Which platform is cheapest for a small team just getting started? All three offer a genuinely free way to start: Power Apps’ Developer Plan, OutSystems’ Personal Edition, and Appian’s Community Edition. None of the three free tiers is meant for production use with real end users at scale, so “cheapest to start” and “cheapest to run in production” are different questions that require getting an actual quote for the latter from OutSystems and Appian.
In a distributed system, there is no single clock everyone agrees on — network delay means two events on different machines can arrive “out of order” relative to wall-clock time, and two machines’ local clocks drift regardless. But a database or application still needs to answer a narrower, more useful question than “what time did this happen”: did event A causally influence event B, or could they have happened independently of each other? Leslie Lamport’s 1978 paper gave distributed systems their first rigorous tool for this — logical clocks — and a decade later, Colin Fidge and Friedemann Mattern independently extended the idea into vector clocks, which can actually detect when two events are concurrent rather than merely ordering everything into one arbitrary sequence. Both ideas predate, and directly underlie, the conflict-resolution logic in systems like Amazon’s Dynamo and Riak.
At a Glance
Mechanism
What it is
Can it detect concurrency?
Lamport timestamp
A single integer counter per process, incremented on every local event and on message receipt
No — only gives a one-way “happened-before” implication, plus an arbitrary total order via tie-breaking
Vector clock
An array of one counter per process, merged via element-wise maximum on message receipt
Yes — two events are concurrent exactly when neither vector is less-than-or-equal to the other
Short Verdict
Lamport timestamps are the cheapest possible tool for giving a distributed system a consistent, partial causal ordering: one integer per process, incremented on every event. Their real limitation is that a smaller timestamp never proves causation — it only proves the reverse implication holds, so two differently-timestamped events might be causally related or might simply be concurrent, and a Lamport clock alone cannot tell you which. Vector clocks fix exactly this gap by keeping a full array of counters instead of one, at the cost of O(n) space and message overhead per event, where n is the number of processes — a cost real systems like Amazon’s Dynamo accepted deliberately, and one Riak later worked to shrink with dotted version vectors.
The Problem: Ordering Events Without a Shared Clock
Lamport’s 1978 paper, “Time, Clocks, and the Ordering of Events in a Distributed System,” published in Communications of the ACM, starts from a deliberately weak but precise relation: event A “happens-before” event B if you can get from A to B either by following the normal sequence of events within a single process, or by following a message from the moment it’s sent to the moment it’s received (and the relation is transitive across both). Two events that aren’t connected by any such chain are concurrent — neither happened before the other, and no amount of waiting resolves that, because there’s no causal link between them to resolve. The practical problem this creates: a system that needs to order operations (apply updates in a sensible sequence, detect conflicting concurrent writes, or debug what actually led to what) can’t just compare wall-clock timestamps, because clock drift and network delay make physical time an unreliable stand-in for the happened-before relation Lamport defined.
Lamport Timestamps: One Counter, Two Rules
Lamport’s solution is a logical clock: every process keeps a single integer counter, governed by two rules.
Before any local event, including sending a message, a process increments its own counter. A sent message carries the sender’s counter value at send time.
On receiving a message, a process sets its counter to the larger of its current value and the value carried in the message, then increments it by one.
This guarantees one direction cleanly: if A happens-before B, then A’s Lamport timestamp is strictly less than B’s. It does not guarantee the reverse. If timestamp(A) < timestamp(B), A and B might be causally related, or they might simply be concurrent events that happened to get stamped in that order — the counter alone can’t distinguish the two cases. Lamport’s paper addresses this by adding an arbitrary tie-breaking rule (commonly, process ID) to turn the partial order into a total order suitable for things like mutual exclusion — but that total order is a convenience for the system, not evidence of actual causality between every pair of events in it.
Vector Clocks: An Array Instead of a Scalar
Vector time was developed independently by multiple researchers in the early-to-mid 1980s, but Colin Fidge and Friedemann Mattern’s 1988 papers are the ones credited with establishing the name “vector clock” and formalizing its properties. The mechanism replaces Lamport’s single counter with a vector of n counters, one per process in the system, following rules that generalize Lamport’s:
All vectors start at all-zero.
On an internal event (including sending a message), a process increments only its own entry in its own vector.
A sent message carries a copy of the sender’s full vector at send time.
On receiving a message, a process increments its own entry, then sets every other entry in its vector to the maximum of its current value and the corresponding value in the received vector.
Comparing two vectors gives you exactly what a Lamport timestamp can’t: vector V1 is “less than” vector V2 if every entry in V1 is less than or equal to the corresponding entry in V2, and at least one entry is strictly smaller — and that comparison is precisely equivalent to “the event behind V1 happened-before the event behind V2.” If neither vector is less-than-or-equal to the other, the two events are provably concurrent: no message, direct or indirect, connects them. That two-way guarantee — not just an implication in one direction — is the entire reason vector clocks exist on top of Lamport’s simpler mechanism.
A Minimal Implementation in Python
This shows the increment/merge/compare mechanics directly, using a dict keyed by process ID rather than a fixed-size array, which is the common approach when the set of participating processes isn’t fixed in advance.
class VectorClock:
def __init__(self, process_id):
self.process_id = process_id
self.clock = {process_id: 0}
def local_event(self):
self.clock[self.process_id] = self.clock.get(self.process_id, 0) + 1
return dict(self.clock)
def send_event(self):
# sending is itself a local event; the returned snapshot
# is what gets attached to the outgoing message
return self.local_event()
def receive_event(self, received_clock):
self.clock[self.process_id] = self.clock.get(self.process_id, 0) + 1
for pid, value in received_clock.items():
self.clock[pid] = max(self.clock.get(pid, 0), value)
return dict(self.clock)
def compare(v1, v2):
"""Return 'before', 'after', or 'concurrent'."""
keys = set(v1) | set(v2)
le = all(v1.get(k, 0) <= v2.get(k, 0) for k in keys)
ge = all(v1.get(k, 0) >= v2.get(k, 0) for k in keys)
if le and v1 != v2:
return "before"
if ge and v1 != v2:
return "after"
return "concurrent"
a = VectorClock("A")
b = VectorClock("B")
msg = a.send_event() # A: {A: 1}
b.receive_event(msg) # B: {A: 1, B: 1}
a_event2 = a.local_event() # A: {A: 2}
b_event2 = b.local_event() # B: {A: 1, B: 2}
print(compare(a_event2, b_event2)) # "concurrent" — neither happened-before the other
The property to notice: after the message exchange, A’s second local event and B’s second local event are provably concurrent, even though B’s vector “knows about” A’s first event. A Lamport timestamp could only have given A_2 and B_2 two different integers and left you guessing whether that difference meant anything.
Real-World Use: Conflict Resolution in Dynamo-Style Databases
Amazon’s Dynamo, the design later described in the 2007 paper that inspired Riak, Voldemort, and (less directly) Cassandra, used vector clocks specifically to let writes happen concurrently on different replicas without a central coordinator, while still being able to tell afterward whether two versions of an object genuinely conflict or whether one simply supersedes the other. When a client reads an object, Dynamo can return multiple versions along with their vector clocks if it detects they’re concurrent rather than causally ordered — pushing conflict resolution up to the application (or a merge function) instead of silently picking a winner and losing data. Riak inherited this model directly and, for a time, exposed vector clocks to clients as opaque tokens to return on subsequent writes so the system could tell which version a client’s update was actually based on.
That same Dynamo-style design also surfaced vector clocks’ most-cited operational problem: in a system with many short-lived or frequently-reassigned client/actor identities, the vector can grow an entry for every actor that ever wrote the object, even long after that actor stopped existing, bloating storage indefinitely unless old entries are pruned. Riak’s later move to dotted version vectors was a direct response to this growth problem, aiming to keep the same causality-tracking guarantees with a more compact representation. Not every distributed database makes this trade at all — Cassandra, notably, does not use vector clocks, instead resolving conflicting writes with a simpler last-write-wins policy based on client-supplied timestamps, accepting a real risk of silently discarding concurrent updates in exchange for avoiding vector clocks’ bookkeeping and growth overhead entirely.
Lamport Timestamps vs. Vector Clocks
Dimension
Lamport Timestamp
Vector Clock
Space per event
O(1) — a single integer
O(n) — one entry per participating process
Detects concurrency?
No — only a one-way happened-before implication
Yes — exactly captures happened-before and concurrent in both directions
Produces a total order?
Yes, with an arbitrary tie-break (e.g. process ID)
Not directly — comparison can return “incomparable” (concurrent)
Conflict detection in optimistic/multi-master replication (Dynamo, Riak)
Growth concern
None — fixed size forever
Can grow with the number of distinct writers over an object’s lifetime
Trade-offs
Lamport timestamps are nearly free but structurally incomplete: cheap enough to attach to every message, but they cannot, even in principle, distinguish “causally related” from “merely concurrent” when timestamps differ.
Vector clocks are exact but not free: every message carries O(n) data, and every process must track an entry for every other process it has ever communicated with (directly or transitively), which is the specific cost Dynamo-style systems accepted for correct conflict detection.
Unbounded actor growth is a real operational risk for vector clocks in systems with many ephemeral writers, which is what pushed Riak toward dotted version vectors rather than abandoning causality tracking altogether.
Neither mechanism survives Byzantine failures: both assume processes report their own clock state honestly, and causality detection is not achievable with any vector-clock variant if participants can behave arbitrarily or maliciously.
Bottom Line
Lamport’s logical clock answered a narrower question than it’s often given credit for: it orders events consistently with causality, but it cannot tell you when causality is absent. Vector clocks, developed independently by Fidge and Mattern a decade later, close that exact gap at the cost of per-process bookkeeping that grows with the number of participants — a cost Amazon’s Dynamo and early Riak paid deliberately so that concurrent writes could be detected and resolved explicitly instead of silently overwritten. If you only need a consistent ordering for debugging, logging, or simple coordination, a Lamport timestamp is the cheaper, sufficient tool. If your system allows concurrent writes to the same data from multiple replicas and needs to know, after the fact, whether two versions genuinely conflict, a vector clock (or one of its more compact descendants) is doing real, necessary work that a scalar counter structurally cannot do.
FAQ
If A’s Lamport timestamp is smaller than B’s, did A cause B? Not necessarily. Lamport’s relation only guarantees the implication in one direction: if A happened-before B, A’s timestamp is smaller. A smaller timestamp on its own doesn’t prove causation — A and B could simply be concurrent events that got stamped in that order.
How exactly do vector clocks detect concurrency? Two events are concurrent precisely when their vectors are incomparable — neither vector is less-than-or-equal to the other in every entry. That incomparability is mathematically equivalent to there being no message chain, direct or indirect, connecting the two events.
Who actually invented vector clocks? Vector time was apparently developed independently by several researchers in the early 1980s, but Colin Fidge and Friedemann Mattern’s 1988 papers are the ones conventionally cited for establishing the name “vector clock” and its formal mathematical properties.
Why doesn’t Cassandra use vector clocks? Cassandra resolves conflicting writes with a simpler last-write-wins approach based on client-supplied timestamps rather than tracking causality per write. This avoids vector clocks’ bookkeeping and unbounded-growth concerns, at the cost of being able to silently discard one of two genuinely concurrent updates instead of surfacing the conflict.
Adobe Lightroom, Snapseed, and CapCut all edit photos or video on a phone, but they come from three very different places: a subscription-first professional RAW editor, a completely free Google-made photo editor with no upsells at all, and a video-first app with an unusually complicated free-vs-paid split. We checked each vendor’s current pricing and feature pages directly.
At a Glance
App
Price
Free tier
Primary focus
Platforms
Adobe Lightroom
From $11.99/mo (Lightroom 1TB plan, annual billing)
Yes, basic editing with limited AI tools
Non-destructive RAW photo editing with cloud sync
iOS, Android, Windows, macOS, Web
Snapseed
Free — no subscriptions, purchases, ads, or watermarks
Yes, fully featured, no premium tier exists
General-purpose photo editing with 30+ pro tools
iOS, Android (no desktop/web app)
CapCut
Free tier; Pro $19.99/mo or $179.99/yr
Yes, but with caveats on watermarks and cloud storage
Video editing, with photo/image tools included
iOS, Android, Windows, macOS, Web
Short Verdict
These three aren’t quite apples-to-apples — Lightroom and Snapseed are photo editors, while CapCut is primarily a video editor with image tools bundled in — but they’re the three apps people actually compare when picking a single mobile editing app to live on their phone. Snapseed is the easy pick if you only edit photos and don’t want to pay anything, ever: it’s genuinely free with no subscription anywhere in the app. Lightroom is the pick for serious photographers who shoot RAW and want non-destructive editing synced across devices, but it starts at $11.99/month for cloud storage and full functionality. CapCut is the pick if video is your main need, but its free-vs-Pro split is the least transparent of the three — even CapCut’s own help pages are vague about exactly what the free tier includes.
What Each App Is
Adobe Lightroom is Adobe’s cloud-based, non-destructive photo editor, with mobile apps on iOS and Android plus desktop apps on Windows and macOS, all syncing through Adobe’s cloud. It includes AI-assisted tools like sky/subject selection, noise reduction (Denoise), and generative removal, layered on top of traditional RAW editing controls. A free tier exists with basic editing tools, though premium AI features and meaningful cloud storage require a paid plan.
Snapseed is Google’s free photo editor, originally built by Nik Software. It got its first major redesign in years with Snapseed 4.0 in 2026, which brought a refreshed interface to both Android and iOS (ending a period where some features were iOS-first) along with tools like One-Touch Masking for selecting subjects or backgrounds, auto/manual Adjust controls, and a Snapseed Camera mode with Pro controls for ISO, shutter speed, and focus. Google’s own update notes are explicit that its 30-plus pro tools and filters come with no subscriptions, purchases, ads, or watermarks.
CapCut, from ByteDance, is a mobile-first video editor with photo and image editing tools included. It markets a free plan and a paid CapCut Pro tier, but the exact boundary between them is one of the least transparent of any app in this comparison — CapCut’s own help content says watermark-free exports and resolution limits on the free tier “depend on the features you use and your app version,” rather than stating a fixed rule.
Pricing Breakdown
Plan
Price
What you get
Lightroom (1TB)
$11.99/mo, annual billing
Lightroom only, 1TB of cloud storage, full editing toolset
Photography (1TB)
$19.99/mo, annual billing
Lightroom and Photoshop, 1TB of cloud storage
Creative Cloud Pro (All Apps)
$34.99/mo for 3 months, then $69.99/mo, annual billing
20+ Adobe apps including Lightroom, more storage
Snapseed
Free
All 30+ tools and filters, no subscription tier exists at all
CapCut Free
$0
Core editing tools; watermark-free export and maximum resolution are not clearly guaranteed and vary by feature, app version, and account, per CapCut’s own help content
CapCut Pro
$19.99/mo or $179.99/yr
~1TB cloud storage, background remover, motion tracking, noise reduction, AI video/music/image generation, and guaranteed access to premium assets without a watermark; Pro’s listed benefits explicitly include 4K/60fps export
CapCut Team
From roughly $24.99/mo (varies by region/promotion)
Everything in Pro, shared across a team workspace
A sourcing note on CapCut specifically: some third-party trackers claim both Free and Pro can export up to 8K, while CapCut’s own help pages describe free-tier resolution as unpublished and variable, and list 4K/60fps as a specific Pro benefit. We couldn’t resolve that contradiction from CapCut’s own materials, so check the export panel in your own account before assuming either figure.
Adobe Lightroom
Pros
True non-destructive RAW editing with professional-grade controls
Cloud sync keeps edits consistent across phone, tablet, and desktop
AI tools (Denoise, Select Sky/Subject, Generative Remove) are genuinely useful, not gimmicks
Available on essentially every platform, including native desktop apps
Cons
No tier here is free in any meaningful sense once you need real cloud storage — $11.99/month minimum
Photoshop isn’t included until the $19.99/month Photography plan
The jump to Creative Cloud Pro’s $69.99/month ongoing rate (after a 3-month $34.99 intro) is steep if you only use Lightroom
Snapseed
Pros
Completely free, with Google’s own materials explicitly ruling out subscriptions, purchases, ads, and watermarks
30+ professional-grade tools and filters, including One-Touch Masking and a manual Pro camera mode
Got a genuine 2026 refresh (Snapseed 4.0) rather than being abandoned software
Cons
No desktop or web app — mobile only, on iOS and Android
No RAW cloud sync across devices the way Lightroom offers
Being free and Google-maintained, feature development has historically been slower and less frequent than Adobe’s release cadence
CapCut
Pros
Strong, approachable video editing toolset with AI features (background remover, AI video, AI image generation) bundled into Pro
Available across mobile, desktop, and web
Pro’s cloud storage (~1TB) and 4K/60fps export are clearly stated benefits
Cons
The free tier’s watermark and resolution behavior is genuinely unclear even from CapCut’s own help documentation
CapCut ended its free cloud storage allowance in August 2024, so free users must pay to store projects online at all
Advanced AI tools (background remover, motion tracking, AI video/music/image generation) are Pro-exclusive, and Pro costs more than either Lightroom plan at $19.99/month
Who It’s a Good Fit For
Lightroom fits anyone who shoots RAW and wants professional, non-destructive editing synced across every device they own. Snapseed fits anyone who wants strong photo editing on their phone and refuses to pay for it, ever. CapCut fits anyone whose main need is video editing with AI assistance, as long as they’re prepared for some ambiguity about exactly what the free tier includes.
Who Should Look Elsewhere
If you want zero cost with zero ambiguity, skip CapCut’s free tier and use Snapseed instead for photo work — its free status is unambiguous where CapCut’s isn’t. If you need desktop-grade RAW editing and don’t want a subscription at all, none of these three will satisfy you; Lightroom requires a paid plan for meaningful cloud storage and full functionality.
Bottom Line
These three solve different problems well. Lightroom is the serious photographer’s tool and the only one of the three with a real subscription cost baked into any useful tier. Snapseed is the best free photo editor here, full stop, with no fine print. CapCut is the strongest free-to-paid video editor of the group, but go in expecting to test your own account’s actual limits rather than trusting a single published number for the free tier.
FAQ
Is Snapseed really completely free? Yes. Google’s own release notes for Snapseed 4.0 explicitly state its tools and filters come with no subscriptions, purchases, ads, or watermarks, and no premium tier exists in the app.
Does CapCut’s free plan add a watermark to exports? It depends. CapCut’s own help content says watermark-free export varies by the specific features and assets used and your app version — some templates add an ending logo clip, and some free-tier premium assets can add a watermark. Pro guarantees watermark-free exports with full access to premium assets.
What’s the cheapest way to get Lightroom? The standalone Lightroom (1TB) plan at $11.99/month (annual billing) is Adobe’s entry point; it doesn’t include Photoshop, which requires stepping up to the $19.99/month Photography plan.
Can CapCut export in 8K on the free plan? Unclear. CapCut’s own help pages don’t publish a free-tier resolution cap and list 4K/60fps specifically as a Pro benefit, while some third-party sources claim both tiers support 8K. Check your own account’s export panel rather than relying on either claim.
Sources
Adobe — official Creative Cloud photography plan comparison page
Google/Snapseed — official Snapseed 4.0 update coverage via 9to5Google
CapCut — official CapCut help and resource pages on pricing, free-tier limits, and the Standard vs. Pro comparison
Ask a database or a network switch “how many times have I seen this?” at a volume of millions of events per second, and storing a running count for every distinct key becomes its own scaling problem — the moment the number of distinct keys stops fitting in memory, exact per-key counters stop being an option. Count-Min Sketch solves this the same way Bloom filters and HyperLogLog solve adjacent problems: trade a small, bounded, one-directional error for a fixed, sublinear amount of memory. Introduced by Graham Cormode and S. Muthu Muthukrishnan in a 2003/2005 paper, it now ships as a first-class probabilistic data type in Redis Stack and underlies frequency-estimation and heavy-hitter detection in streaming systems well beyond it.
At a Glance
Attribute
Detail
What it is
A probabilistic structure that estimates how many times each distinct item has occurred in a stream
What it guarantees
Estimates are never below the true count; error is one-directional (over-counting only), bounded and tunable
Core structure
A w-column, d-row array of counters, each row paired with its own independent hash function
Error bound
Width w = ⌈e/ε⌉, depth d = ⌈ln(1/δ)⌉ gives additive error at most ε × (total count), with probability at least 1 − δ
Typical use cases
Heavy-hitter / top-K detection, per-item frequency estimation over high-volume streams, network traffic measurement
Origin
Graham Cormode & S. Muthu Muthukrishnan, “An Improved Data Stream Summary: The Count-Min Sketch and its Applications,” Journal of Algorithms, 2005 (first presented 2003)
Short Verdict
Count-Min Sketch is the right tool when you need “roughly how many times has X happened” over a stream too large to hold one exact counter per distinct key, and you specifically care most about the high-frequency items — it is a poor fit for counting rare, long-tail items precisely, since its error is large relative to small true counts. Redis ships it as a production data type with O(1) updates and queries, and its own documentation is explicit that counts below a configurable error-based threshold should be treated as noise, not signal. In exchange for that limitation, the whole structure’s memory stays fixed regardless of how many distinct items flow through it, and separate sketches merge by simple cell-wise addition.
The Problem: Counting Everything in a High-Cardinality Stream
A hash map from item to count answers “how many times has this occurred?” exactly, but its memory grows linearly with the number of distinct items — tracking per-second request counts for every distinct client IP, every distinct product SKU sold, or every distinct URL requested at a CDN edge node means the map itself can dwarf the data you actually care about, which is usually just the handful of items occurring far more often than the rest. Cormode and Muthukrishnan’s 2005 paper frames this as a “data stream summary” problem: you see a long stream of items once, can’t afford to store it all, and need a compact structure that still answers frequency and “point” queries afterward with a provable error bound rather than a hopeful approximation.
How It Works: A Grid of Counters and d Independent Hashes
The structure is a two-dimensional array of counters with w columns and d rows, where each row has its own independent hash function mapping any item to one of the w columns.
Update (increment): when item i arrives, for every row j compute column k = h_j(i), and increment that single cell by one. An item touches exactly d cells — one per row — regardless of how many distinct items exist.
Query (estimate): to estimate the count of item i, compute the same d cells again and return the minimum value across all of them — the “min” in Count-Min.
Taking the minimum is what makes the structure’s error one-directional. Hash collisions can only ever make a cell’s count too high — never too low — because every other item that happens to hash into the same column in a given row only adds to that cell, never subtracts. So any individual cell for item i is at least as large as i’s true count, and the minimum across d independently-hashed rows is the tightest such overestimate the structure can produce. That is also why Count-Min Sketch never underestimates: the reported value is always ≥ the true count, and the only question is by how much.
Cormode and Muthukrishnan’s paper gives the sizing that controls how much: setting w = ⌈e/ε⌉ (e is Euler’s number, ≈2.718) and d = ⌈ln(1/δ)⌉ guarantees the estimate exceeds the true count by at most ε times the sum of all counts added so far (the total stream size), with probability at least 1 − δ. Concretely, more columns (larger w) tighten the error bound ε; more rows (larger d, more independent hash functions) tighten the failure probability δ. Both dials cost memory directly — the structure is exactly w × d counters — which is the same precision-for-space trade that runs through every probabilistic structure in this family.
A Minimal Implementation in Python
This mirrors the update/query mechanism directly — it is not a production implementation, which would use faster hashing and careful overflow handling for the counters.
import hashlib
class CountMinSketch:
def __init__(self, width=2000, depth=7):
self.width = width
self.depth = depth
self.table = [[0] * width for _ in range(depth)]
def _hash(self, item, row):
# one independent hash per row, salted by the row index
key = f"{row}:{item}".encode("utf-8")
digest = hashlib.sha256(key).digest()
return int.from_bytes(digest[:8], "big") % self.width
def add(self, item, count=1):
for row in range(self.depth):
col = self._hash(item, row)
self.table[row][col] += count
def estimate(self, item):
return min(
self.table[row][self._hash(item, row)]
for row in range(self.depth)
)
cms = CountMinSketch(width=2000, depth=7)
for _ in range(10_000):
cms.add("checkout_api")
for _ in range(12):
cms.add("rare_debug_endpoint")
print(cms.estimate("checkout_api")) # at least 10,000, close to it
print(cms.estimate("rare_debug_endpoint")) # a poor, noisy estimate — too few true occurrences
The key properties to notice: memory is fixed at width × depth counters no matter how many distinct items flow through, both add and estimate are O(depth) per call rather than scaling with the number of distinct items seen, and two sketches built with the same width and depth merge by simply summing their tables cell-by-cell — no need to touch either original stream.
Real-World Use: Redis’s Count-Min Sketch
Redis ships Count-Min Sketch as a first-class probabilistic data type with six commands documented on redis.io. CMS.INITBYDIM creates a sketch with explicit width and depth; CMS.INITBYPROB creates one from a target error rate and error probability instead, computing width as w = 2/error internally; CMS.INCRBY increments one or more items’ counts (by an amount that can be negative); CMS.QUERY returns the current estimate for one or more items; CMS.MERGE combines several sketches into one; and CMS.INFO reports a sketch’s width, depth, and total count. Redis’s own documentation is explicit about the trade-off’s practical shape: counts can only be over-estimated, never under-estimated, and it recommends computing a threshold (error rate × total count so far) below which returned counts should be treated as unreliable noise rather than a real signal — its own worked example shows that a uniform distribution of similarly-sized counts is a poor fit for the structure, while a skewed distribution with a smaller number of genuinely “heavy” items works well, which is exactly the shape of most real traffic and sales data.
That skewed-distribution fit is also why Count-Min Sketch’s best-known applications are heavy-hitter and top-K detection problems: identifying which handful of network flows, API keys, or URLs account for a disproportionate share of traffic, without keeping an exact counter for every long-tail item that only shows up once or twice. Cormode and Muthukrishnan’s original paper frames this class of problem — frequent items over a data stream — as a central motivating application, alongside point queries and range queries, and later work (cited on the structure’s reference pages) has applied the same sketch to tasks like NLP frequency estimation and detecting repeated password-guessing attempts without storing every attempt.
Count-Min Sketch vs. Bloom Filter vs. HyperLogLog
These three sit in the same family of fixed-memory probabilistic structures, but they answer three genuinely different questions, and picking the wrong one for your question is the most common mistake.
Structure
Question it answers
Error direction
Supports deletion?
Bloom filter
“Have I seen this exact item before?” (membership)
False positives only, never false negatives
No (Counting Bloom Filter variant adds it)
HyperLogLog
“How many distinct items have I seen in total?” (cardinality)
Statistical error in either direction around the true count
Not applicable — no per-item concept
Count-Min Sketch
“How many times has this specific item occurred?” (frequency)
Over-estimates only, never under-estimates
No in the standard form; some variants allow controlled decrements
Wikipedia’s own treatment notes that a Count-Min Sketch can be viewed as a kind of counting Bloom filter, but the two are sized on different principles: a counting Bloom filter is typically sized to the number of elements actually inserted, while Count-Min Sketch’s width and depth are sized directly from the target error rate ε and failure probability δ, independent of how many distinct items you expect — which is exactly why it tolerates an unknown or unbounded number of distinct keys more gracefully.
Trade-offs
One-directional error only: every estimate is greater than or equal to the true count, never less — useful when a false “zero” would be worse than an inflated number, but it means you can never fully trust a reported count without knowing the error bound.
Bad for uniform, low-frequency distributions: Redis’s own documentation shows that when most items have similar, modest counts, the error-based noise threshold ends up higher than the real counts themselves, making every estimate useless.
Excellent for skewed, heavy-hitter distributions: when a small number of items dominate the volume (the common case for real traffic, sales, and request data), the sketch stays accurate for exactly the items you’re most likely to care about.
Mergeable and O(1): constant-time updates and queries per operation, and merging two same-shaped sketches is a simple cell-wise sum — a major advantage for sharded or distributed counting pipelines.
Bottom Line
Count-Min Sketch fills a specific gap that Bloom filters and HyperLogLog don’t: fast, fixed-memory frequency estimation per distinct item, with a mathematically guaranteed, one-directional error. Cormode and Muthukrishnan’s original analysis gives exact formulas for sizing the structure to a target error rate and confidence, and Redis’s production implementation turns that into six commands any application can call directly. If your data is dominated by a long tail of rare, similarly-sized items, this is the wrong structure — the noise threshold will swallow everything. If you need to know which handful of items are hammering your system the hardest, out of a stream too large to count exactly, it’s close to the standard answer.
FAQ
Can Count-Min Sketch ever underestimate a count? No. By construction, every cell an item maps to can only be incremented by that item or by a colliding item — never decremented in the standard form — so the minimum across all of an item’s cells is always greater than or equal to its true count.
How do I know whether to trust a given estimate? Redis’s documentation recommends computing a threshold equal to your configured error rate multiplied by the sketch’s total count so far (available via CMS.INFO), and treating any estimate below that threshold as unreliable noise rather than a real count.
Is this the same as a counting Bloom filter? They’re closely related — a Count-Min Sketch can be viewed as a form of counting Bloom filter — but they’re sized differently: a counting Bloom filter is typically sized to the expected number of distinct elements, while Count-Min Sketch’s dimensions come directly from the target error rate and confidence level, independent of cardinality.
Can two Count-Min Sketches be merged without re-processing the original streams? Yes, as long as they share the same width and depth (and hash functions). Redis’s CMS.MERGE command combines multiple sketches by summing corresponding cells, producing a mathematically valid sketch of the combined stream.
Picking a mobile calendar app in 2026 mostly comes down to three questions: do you want to pay anything, do you need it to run on Android, and how much do you care about typing “lunch with Sam Friday at noon” instead of tapping through a date picker. Google Calendar, Fantastical, and Outlook Calendar answer those three questions very differently, and we checked each vendor’s current feature and pricing pages before writing this.
At a Glance
App
Price
Natural-language entry
Platforms
Widgets
Google Calendar
Free
Yes, built into Quick Add, free
Android, iOS, Web (no native desktop app)
Yes, more mature on Android than iOS
Fantastical
Free core app; Premium $6.99/mo or $56.99/yr individual, $10.49/mo or $89.99/yr family
Yes, free even without Premium
iOS, iPadOS, macOS, watchOS, Windows (no Android)
Yes, included free
Outlook Calendar
Free with any Microsoft account; deeper AI features increasingly require Microsoft 365 Copilot
Basic; richer AI scheduling is being moved behind Copilot
Windows, Mac, iOS, Android, Web
Yes
Short Verdict
Google Calendar is still the easiest “just works, costs nothing” option, especially if you’re already in Gmail and Android. Fantastical is the best-designed and most feature-rich of the three for typing in events and managing multiple calendar sets, and it’s genuinely free for most of that — but it has no Android app at all, which rules it out for mixed-device households or teams. Outlook Calendar is the one to pick if you need one calendar that runs natively on every major desktop and mobile OS, though Microsoft has been quietly moving some of its newer AI scheduling features behind a paid Microsoft 365 Copilot add-on rather than including them free.
What Each App Is
Google Calendar is bundled free with every Google Account and Google Workspace subscription. It has native apps for Android and iOS and a full-featured web app, but no dedicated native desktop app for Windows or Mac — you use it through a browser. Its Quick Add feature has long supported typing a plain-English sentence to create an event.
Fantastical, from Flexibits, started as an Apple-only calendar app for iOS, iPadOS, and macOS, and added a native Windows app in 2024 — a real shift for a tool that was exclusively Apple for most of its life. It still has no Android app. The free version covers core calendar and reminder functions, including natural-language event entry and one calendar set; Fantastical Premium unlocks unlimited calendar sets, Proposed Times (meeting polls), travel time, a 10-day weather forecast, and Apple Watch support.
Outlook Calendar ships free with any Microsoft account via the Outlook web app and mobile apps, and comes bundled for Microsoft 365 subscribers. It has true native apps across Windows, Mac, iOS, and Android. Microsoft has recently retired some free calendar-adjacent AI features — for example, the “Meeting Insight” panel that surfaced related files and emails on an event is being retired by early September 2026, replaced by a “Prepare for this meeting” AI summary feature that requires a Microsoft 365 Copilot license.
Pricing Breakdown
Plan
Price
Notes
Google Calendar
Free
No paid tier exists for the calendar app itself; it’s included with any Google Account
Unlimited calendar sets, Proposed Times, travel time, 10-day weather, Apple Watch support, 14-day free trial
Fantastical Family Premium
$10.49/mo or $89.99/yr
Same Premium features shared across up to 5 family members
Fantastical Team Premium
Price shown only at checkout on Flexibits’ own site
Adds Single Sign-On and scheduling openings with multiple hosts
Outlook Calendar (basic)
Free
Included with any Microsoft account
Outlook Calendar (Microsoft 365 Copilot features)
Requires a Microsoft 365 Copilot add-on
Newer AI scheduling/summary features, such as the “Prepare for this meeting” replacement for Meeting Insight, are being gated behind Copilot rather than included free
One sourcing note: Flexibits’ own pricing page doesn’t display these dollar figures until you reach checkout. The Individual and Family numbers above come from two independent third-party price trackers that agree with each other; confirm the current figure in-app before subscribing.
Google Calendar
Pros
Completely free with no premium tier to upsell into
Deep integration with Gmail and Google Workspace — automatic Meet links, Gmail event detection
Available everywhere via the web, plus native Android and iOS apps
Cons
No native desktop app for Windows or Mac — it’s a browser tab or an installed web app
Syncing non-Google calendars (iCloud, Exchange) is more friction-prone than Fantastical’s native multi-account handling
iOS widget options are more limited than Android’s
Fantastical
Pros
Natural-language entry and widgets are both free, not Premium-gated
Calendar Sets — grouping and toggling calendars by context — are a genuinely distinctive feature
Added a native Windows app in 2024, breaking out of its historical Apple-only lock-in
Consistently well-reviewed interface across Mac and iOS
Cons
Still no Android app — a hard blocker for mixed-device households or teams
Premium features (Proposed Times, travel time, extended weather, Apple Watch support) require a subscription on top of an otherwise capable free app
Team plan pricing isn’t shown on Flexibits’ own pricing page until checkout
Outlook Calendar
Pros
Free with any Microsoft account, and bundled for Microsoft 365 subscribers
True native apps across Windows, Mac, iOS, and Android — the widest desktop OS coverage of the three
Deep integration with Outlook email, Teams meetings, and Microsoft 365 scheduling assistant
Cons
Microsoft is moving some calendar-adjacent AI features (like the Meeting Insight replacement) behind a paid Microsoft 365 Copilot add-on rather than keeping them free
Natural-language entry is less consistently available across all Outlook clients than Google Calendar’s or Fantastical’s
The ongoing classic-to-“new Outlook” transition has created some feature inconsistency between app versions
Who It’s a Good Fit For
Google Calendar fits anyone in the Google or Android ecosystem who wants a zero-cost calendar with no upsells at all. Fantastical fits Apple households and teams (now also Windows users) who want the best-designed calendar app and don’t mind a small subscription for scheduling polls and deeper calendar-set control. Outlook Calendar fits anyone already inside Microsoft 365 or Exchange for work, or anyone who specifically needs one calendar app that runs natively on every major desktop and mobile OS.
Who Should Look Elsewhere
Any household or team with Android phones should skip Fantastical entirely — there is no Android client. Anyone who wants Google Calendar’s free convenience but also needs a true native desktop app should look at Outlook Calendar instead, since Google Calendar has none.
Bottom Line
There’s no single best calendar app here, only a best fit. Pick Google Calendar for free and simple, Fantastical for the most polished experience if you’re Apple-first (or now Windows-friendly) and don’t need Android, and Outlook Calendar if cross-platform desktop coverage and Microsoft 365 integration matter more than anything else.
FAQ
Is Fantastical free? Partially. The core app — including natural-language entry and widgets — is free. Proposed Times/scheduling polls, travel time, extended weather, and Apple Watch support require Fantastical Premium, around $6.99/month for an individual or $10.49/month for a family plan, per independent price trackers since Flexibits’ own page only shows numbers at checkout.
Does Fantastical run on Android? No. As of this review, Fantastical supports iOS, iPadOS, macOS, watchOS, and Windows, but not Android.
Is Google Calendar’s natural-language entry as good as Fantastical’s? Both let you type a plain-English sentence to create an event. Neither vendor publishes a head-to-head accuracy benchmark against the other, so treat this as rough feature parity rather than a clear win for either side.
Is Outlook Calendar’s AI scheduling free? Increasingly, no. Microsoft is retiring the free “Meeting Insight” feature by early September 2026 and replacing it with a “Prepare for this meeting” AI summary that requires a Microsoft 365 Copilot license.
Sources
Google Calendar — official Google Calendar and Workspace pages
Fantastical — official Flexibits pricing and feature pages, cross-checked against independent price trackers since exact dollar figures only appear at checkout
Outlook Calendar — Microsoft Message Center and Windows Central reporting on the Meeting Insight retirement and Copilot-gated replacement
Digital asset management (DAM) software is supposed to answer a simple question — where is the latest, approved version of this logo, photo, or video, and who’s allowed to use it — at a scale where a shared folder stops working. Bynder and Brandfolder are both dedicated DAM platforms. Canva Enterprise is something different: a design tool with brand-governance features layered on top. All three have one thing in common, confirmed directly on each vendor’s own pricing page: none of them will tell you a price until you talk to sales.
At a Glance
Tool
Pricing model
Free tier
Core strength
Best for
Bynder
Custom quote, fully modular
No (free consultation only)
AI-powered DAM core plus 170+ prebuilt integrations
Larger marketing/brand orgs building out a MarTech stack
Brandfolder
Custom quote, two named tiers (Premium, Enterprise)
No (demo only)
Video AI tagging, document OCR, BI reporting connector
Teams managing large video or image libraries
Canva Enterprise
Custom quote, sits above Canva Pro/Teams
No (Canva itself has a separate free design tier, but Enterprise doesn’t)
Brand Kits, Brand Templates, and Brand Controls bolted onto a design tool
Teams already standardized on Canva that want basic brand governance
Short Verdict
None of these three will give you a number before a sales call, so the real decision isn’t about price — it’s about how much dedicated DAM you actually need. Bynder and Brandfolder are purpose-built asset-management platforms with metadata, rights management, and (for Brandfolder) AI video tagging as their reason for existing. Canva Enterprise is a design platform first; its brand-asset governance — locked fonts and colors, shared brand kits, template locking — is a layer on top of Canva Pro and Teams, not a standalone DAM. If your team doesn’t already live inside Canva, it’s the wrong starting point for a true DAM evaluation.
What Each Tool Is
Bynder markets itself around an “AI-powered DAM” core — asset organization, access and usage-rights control, and internal/external sharing — that’s included in every custom package. On top of that core, Bynder sells optional modules: Bynder AI, Asset Workflow, Content Workflow, Studio, Print Brand Templates, CX Omnichannel, Analytics, and an Integration Marketplace with 170+ connectors. Its own pricing page states plainly that every customer gets “a custom-made package tailored to their business needs,” with cost driven by user count, storage, your existing MarTech stack, and which modules you pick.
Brandfolder, now owned by Smartsheet, offers two named plans — Premium and Enterprise — though neither shows a price on its own pricing page. Premium includes asset analytics, OCR-based document intelligence, bulk upload/update tools, SSO/SAML, and Video AI (auto-tagging, scene detection, speech-to-text, text extraction). Enterprise adds custom automation, finer multi-brand/multi-team permissions, enterprise creative tooling like editable metadata and colorspace conversion, a BI data connector, and a vanity URL.
Canva Enterprise sits above Canva’s Pro and Teams/Business tiers and is sold as a custom quote via “Get a quote” or “Book a demo” — confirmed via Canva’s own enterprise page behavior and a G2 pricing listing that shows “Contact Vendor for Pricing” for the Enterprise row. Rather than a dedicated asset repository, it adds brand governance to the design tool: Brand Kits for storing fonts, logos, and colors; Brand Templates for reusable branded layouts; and Brand Controls that let admins lock off-brand fonts, colors, and elements across a team.
Pricing Breakdown
Plan
Price
What you get
Bynder (any package)
Custom quote
AI-powered DAM core, rights management, SSO, 24/7 support, and your choice of optional modules (Workflow, Studio, Analytics, Integration Marketplace, etc.)
Brandfolder Premium
Custom quote
Asset analytics, document OCR, bulk asset operations, SSO, availability/expiration controls, Video AI
Brandfolder Enterprise
Custom quote
Everything in Premium, plus custom automation, granular multi-brand permissions, BI connector, colorspace conversion, vanity URL
Canva Enterprise
Custom quote
Everything in Canva Pro/Teams, plus Brand Templates, Brand Controls, a higher brand-kit cap, and per-member access levels
A note on that brand-kit cap: some third-party trackers report Canva Pro allows up to 100 brand kits and Enterprise up to 300, but we found the exact current figures inconsistently reported across sources. Confirm the current numbers directly with a Canva rep rather than relying on any single blog post, including this one.
Bynder
Pros
Modular pricing lets you buy only the add-on modules you actually need rather than one fixed bundle
AI-powered DAM core and SSO are included in every package, not held back as upsells
170+ prebuilt integrations plus APIs and SDKs for custom builds
Cons
Zero public pricing anywhere, not even a “starting at” figure, so budgeting before a sales call is guesswork
Modular structure means your final cost depends heavily on which add-ons you pick, adding negotiation complexity
No free trial — only a free consultation call, which is not the same thing
Brandfolder
Pros
A clearer two-tier structure (Premium, Enterprise) than Bynder’s fully modular approach
Video AI (auto-tagging, scene detection, speech-to-text) stands out for teams with large video libraries
Enterprise’s BI data connector and colorspace conversion target larger creative operations specifically
Cons
Also fully quote-only, with no published starting price for either tier
The exact feature split between Premium and Enterprise isn’t fully itemized publicly, so you won’t know everything you’re missing until you talk to sales
Now part of Smartsheet, a work-management company, so its roadmap depends on fitting Smartsheet’s broader strategy rather than DAM alone
Canva Enterprise
Pros
Built on the same editor many teams already use for Pro or Teams, so there’s no new design tool to learn
Brand Controls let admins lock fonts, colors, and off-brand elements — a design-guardrail angle neither Bynder nor Brandfolder frames the same way
Scales brand kits up from Pro’s cap for agencies managing multiple client brands
Cons
It’s a design platform with brand governance added on, not a dedicated DAM — don’t expect Bynder- or Brandfolder-grade metadata, rights management, or video AI tagging
Also quote-only; Canva’s enterprise page routes every visitor to a demo request rather than showing a price
Reported brand-kit caps vary between third-party sources, so verify current limits directly with Canva
Who It’s a Good Fit For
Bynder fits larger marketing or brand organizations that need a true enterprise DAM with heavy rights management and plan to connect it into a broader MarTech stack. Brandfolder fits teams managing large video or image libraries who want built-in AI tagging and OCR without a separate tool. Canva Enterprise fits teams already standardized on Canva for design who mainly need brand governance — locked fonts and colors, shared brand kits — rather than a full DAM.
Who Should Look Elsewhere
If you need a published price to put in a budget request before engaging sales, none of these three will give you one — expect a multi-step sales process for all three. If you need deep enterprise DAM capability and your team isn’t already using Canva day-to-day, Canva Enterprise is the wrong starting point; it’s not a substitute for a dedicated DAM like Bynder or Brandfolder.
Bottom Line
Treat this as two different shopping lists wearing the same “custom quote” label. Bynder and Brandfolder compete directly as dedicated DAM platforms, and the choice between them comes down to whether you value Bynder’s modular, integration-heavy approach or Brandfolder’s named Premium/Enterprise tiers with strong video AI. Canva Enterprise is worth evaluating only if your team already lives inside Canva and wants brand governance rather than a ground-up DAM.
FAQ
Does any of these three publish a public price? No. Bynder, Brandfolder, and Canva Enterprise are all quote-only as of this review, confirmed directly on each vendor’s own pricing or enterprise page.
Is Canva Enterprise the same as Canva Pro or Teams? No. Enterprise sits above both and specifically adds brand governance features like Brand Controls, template locking, and a higher brand-kit cap.
Which tool has the most explicit video-asset intelligence? Brandfolder’s Video AI — auto-tagging, scene detection, speech-to-text, and text extraction — is the most clearly documented video-AI feature set among the three, per Brandfolder’s own pricing page.
Can I try any of these for free? No. Each vendor’s path starts with a demo or consultation call rather than a self-serve free trial.
Sources
Bynder — official pricing page
Brandfolder — official pricing page
Canva Enterprise — official enterprise page, cross-checked against a G2 Canva pricing listing showing “Contact Vendor for Pricing” for Enterprise
“Vibe coding” — a term Andrej Karpathy popularized in February 2025 to describe building software by describing what you want in natural language and accepting the AI’s output without closely reading the code — has gone from a tongue-in-cheek tweet to a dictionary entry (Merriam-Webster added it in 2025) to a genuine product category. Replit Agent, Lovable, and Bolt.new (built by StackBlitz) are the three platforms most associated with the term: each takes a prompt and produces a working, deployed full-stack app rather than a code suggestion inside an existing editor. That’s a meaningfully different product than an AI coding assistant like GitHub Copilot or Cursor — those help a developer write code faster inside code they already understand; these three are built so a prompt can skip that step entirely. We checked each vendor’s current pricing page and the public security research around this category before writing this piece.
At a Glance
Platform
What It Produces
Entry Paid Price
Free Tier
Underlying Stack
Replit Agent
Full-stack apps built and run inside Replit’s own cloud workspace, with built-in hosting and a database
Core: $20/mo ($18/mo annual)
Limited free usage on Replit’s free plan; Core’s $20 includes model credit
Replit’s own runtime/hosting, Agent orchestrates multiple models
Lovable
Full-stack web apps wired to a Supabase backend (auth, database, storage) by default
Pro: from $25/mo (100 monthly credits)
5 daily credits, capped around 30/month
Supabase for backend/auth/database; React-based frontend
Bolt.new
Full-stack apps built and run in-browser via WebContainers, with one-click deploy
StackBlitz’s WebContainers (runs Node.js in-browser); deploys to Netlify/other hosts
Short Verdict
All three platforms do what they advertise: a plain-language prompt becomes a running, deployed application faster than almost any traditional workflow. Replit Agent is the most “full environment” of the three, since Replit already provided cloud dev environments before adding an agent on top. Lovable is the most backend-opinionated, wiring every app to Supabase by default, which is also the source of its most serious documented security incident. Bolt.new is the fastest to a deployed URL because it runs entirely in-browser via WebContainers rather than provisioning a remote environment. None of the three should be treated as producing production-ready code without a security review — the evidence on that point, covered below, is specific and sourced, not just vibes-based skepticism.
What Each Platform Actually Produces
Replit Agent operates inside Replit’s existing cloud workspace product, so an app it builds is already running in a real, persistent environment with its own storage and networking — there’s no separate “deploy” step conceptually distinct from where the code already lives. Agent usage draws on a shared pool of model credit included in each paid plan ($20 worth on Core, $100 on Pro), and Replit’s own pricing page explicitly notes that “Agent is powered by large language models and may occasionally make mistakes” — a disclosure most AI-assistant vendors bury deeper in their terms.
Lovable generates a React-based frontend wired to a Supabase project by default, which means every Lovable app inherits Supabase’s authentication, Postgres database, and file storage out of the box rather than requiring the user to configure a backend separately. That default wiring is also exactly where Lovable’s most significant public security incident originated (see below). Pricing runs on a credit system: each AI action (a UI tweak, a new feature, an auth flow) consumes a fractional credit, with Lovable’s own examples ranging from 0.50 credits for “make the button gray” to 1.20 credits for “add authentication with sign up and login.”
Bolt.new, built by StackBlitz, is the most architecturally distinct of the three: it runs the generated app’s Node.js runtime directly inside the browser using StackBlitz’s WebContainers technology, rather than provisioning a remote VM or container. That’s what lets it go from prompt to a working, previewable app almost instantly, and why its usage is metered in “tokens” (covering reading your prompt and project files, planning, and writing code) rather than a flat per-message credit. Unused paid-plan tokens roll over for up to two months while a subscription stays active; free-plan tokens do not roll over.
Pricing Breakdown
Platform / Tier
Price
Notes
Replit Core
$20/mo, $18/mo billed annually
Up to 30 hours chat / 60 projects on Free Mode, plus $20 toward more powerful models
Replit Pro
$100/mo, $90/mo billed annually
More Free Mode usage, $100 toward top-tier models plus $100 in additional credits, up to 15 collaborators, 28-day database rollback
Replit Enterprise
Custom
SSO, SCIM, audit logs, single-tenant/private networking, dedicated support
Lovable Free
$0
5 daily credits, capped around 30/month total
Lovable Pro
From $25/mo (100 credits) scaling to roughly $2,250/mo (10,000 credits)
Credit packs scale linearly; higher packs trade a worse per-credit rate for more total usage
Lovable Business
From $50/mo (100 credits), roughly double the Pro price at every credit tier
Adds team collaboration features on top of the same credit scale as Pro
Lovable Enterprise
Custom
Volume-based credit pricing
Bolt.new Free
$0
1,000,000 tokens/mo, 300,000 daily limit, Bolt branding on deployed apps
Bolt.new Pro
$25/mo billed monthly
10,000,000+ tokens/mo, no daily limit, no branding, custom domains, up to 100MB uploads
Bolt.new Teams
$30/member/mo billed monthly
Centralized billing, access management, private NPM registry support
Lovable’s credit pricing is the least linear of the three: its per-credit cost rises as you buy more at the Pro tier in some published breakdowns, which makes a heavy-usage team’s actual monthly bill harder to predict from the sticker price alone than either Replit’s or Bolt’s flatter, token/hour-based plans.
What the “Vibe Coding” Critique Is Actually About
The discourse around vibe coding isn’t just generic “AI code can be wrong” skepticism — there’s specific, documented evidence tied to this exact category of tool. The clearest example is Lovable’s own CVE-2025-48757: because Lovable wires apps to Supabase by default, a significant share of apps generated on the platform shipped without Supabase’s Row Level Security (RLS) enabled on their database tables — meaning an app’s entire dataset could potentially be read or modified by anyone who found the right API endpoint, no authentication required. A scan covering 1,645 Lovable-generated apps found 303 vulnerable endpoints spread across 170 of them, a concrete, reproducible number rather than a vague warning, and the issue was severe enough to receive its own CVE identifier.
Independent of that specific incident, Replit Agent has also been directly tested in controlled security research: Tenzai had five agentic coding tools — including Replit — build three identical applications from identical prompts, and found 69 vulnerabilities across the resulting 15 apps. The most consistent failure pattern wasn’t classic injection flaws (no agent produced an exploitable SQL injection or XSS in that test) but access-control and business-logic gaps: every one of the five agents introduced a server-side request forgery (SSRF) vulnerability in a dedicated SSRF test, and researchers called improper authorization on API endpoints “one of the most common issues” across all five tools. Four of five agents also allowed negative-quantity orders when a prompt didn’t explicitly forbid it — a logic flaw no static scanner reliably catches, because nothing about it is syntactically wrong.
A broader, less rigorously documented data point comes from Apiiro, a code-security vendor, whose research (reported via secondary coverage rather than a fully public methodology) claims AI-assisted developers introduce roughly ten times more security vulnerabilities than non-AI-assisted ones, with the largest single increase in privilege-escalation-related flaws. Apiiro’s own framing — “AI is fixing the typos but creating the timebombs” — is a useful summary of the pattern across all of this research: vibe-coding tools are measurably good at producing code that runs and looks syntactically correct, and measurably worse at the parts of security that require understanding intent rather than syntax, like who should be allowed to call a given endpoint. Treat the specific “10x” figure as a vendor-reported headline rather than an independently replicated statistic, since the underlying sample size and method weren’t published in full.
Pros and Cons
Replit Agent
Pros: fully integrated cloud workspace means no separate hosting step, generous collaborator limits on Pro, transparent model-credit allocation.
Cons: tied to Replit’s own runtime rather than a portable standard container; included in the Tenzai study’s finding of widespread access-control gaps across agentic tools.
Lovable
Pros: fastest path to a working backend (auth, database, storage) because Supabase wiring is automatic; granular per-action credit pricing for light usage.
Cons: that same default Supabase wiring was the direct cause of a CVE affecting hundreds of real deployed apps; credit pricing scales less predictably than the other two at higher usage.
Bolt.new
Pros: fastest to a live preview via in-browser WebContainers, flat and predictable token-based pricing, generous free-tier token allowance.
Cons: free-tier apps carry visible Bolt branding; WebContainers’ in-browser execution model has different resource/scaling characteristics than a traditional server-side deploy, which can matter for heavier backend workloads.
Who It’s a Good Fit For
Choose Replit Agent if you want the generated app to live in a persistent, full-featured cloud workspace rather than exporting to separate hosting. Choose Lovable if you specifically want a Supabase-backed app scaffolded fast — and you commit to auditing Row Level Security on every table before shipping. Choose Bolt.new if speed to a shareable preview matters most and you’re comfortable with an in-browser execution model. All three are strongest for prototypes, internal tools, and MVPs where a human developer will review and harden the output before it handles real user data.
Who Should Look Elsewhere
Teams building anything that handles sensitive user data, payments, or regulated information should not ship any of these three platforms’ output straight to production without an independent security review — the Lovable CVE and the Tenzai study’s access-control findings are specific, documented reasons, not generic caution. Teams that need an AI pair-programmer inside code they already understand and maintain — rather than a tool that generates a whole new app from a prompt — are better served by an AI coding assistant like GitHub Copilot or Cursor than by any of these three “vibe coding” platforms.
Bottom Line
Vibe coding in 2026 genuinely works for what it’s built for: turning a plain-language description into a running application faster than a human typing it out by hand. What it does not reliably do, across all three platforms and backed by named, documented incidents and studies rather than general skepticism, is get access control and business logic right by default. That’s a solvable problem with review and scanning — the same playbook that applies to any AI-generated code — but it’s not solved by the platforms themselves yet, and the Lovable CVE in particular shows what happens when that gap reaches production at scale.
FAQ
Who coined the term “vibe coding”? Andrej Karpathy, in a widely shared February 2025 post describing a style of coding where you “fully give in to the vibes” and accept AI-generated code without close review. The term was added to Merriam-Webster’s dictionary later that year.
Was the Lovable security issue theoretical or did it affect real apps? It affected real, deployed apps. The issue has a published CVE (CVE-2025-48757), and an independent scan found 303 vulnerable endpoints across 170 of 1,645 Lovable-built apps checked, caused by missing Supabase Row Level Security.
Do these tools produce code with classic flaws like SQL injection? Not necessarily — in the Tenzai study of five agentic tools including Replit, none of the generated apps contained an exploitable SQL injection or XSS vulnerability. The failures were concentrated instead in access control and business logic: every agent tested introduced an SSRF flaw, and authorization gaps on API endpoints were described as one of the most common issues.
Is the claim that AI-assisted coding produces “10x more vulnerabilities” solid? It comes from Apiiro, a security vendor, via secondary press coverage rather than a fully published methodology and sample size, so treat it as a vendor-reported figure worth taking seriously rather than an independently verified statistic.
RingCentral, Dialpad, and 8×8 all sell the same basic thing — a cloud business phone system with calling, video meetings, and messaging under one app — but they’ve taken very different approaches to telling you what it costs. Two of the three publish a clear per-seat price ladder right on their websites. The third stopped doing that in 2023 and now sends every visitor straight to a sales call. We checked each vendor’s own pricing page directly before writing this.
At a Glance
Tool
Entry price (per user/mo)
Public pricing?
Built-in AI
Best for
RingCentral (RingEX)
$20 (annual) / $30 (monthly)
Yes, three published tiers
AI Virtual Assistant (AVA) included from Core; AI Receptionist and ACE as add-ons
Teams that want a mature, published tier ladder with heavy meeting capacity
Dialpad (Connect)
$15 (Standard)
Yes, published on the Connect pricing page
AI transcripts, call recaps, and PII redaction included even at the entry tier
Budget-conscious teams that want AI transcription without an upgrade
8×8 (Work)
Not published
No — quote-only since late 2023
Unclear without a quote
Only worth evaluating if you’re already collecting quotes from multiple vendors
Short Verdict
If you want to see a real number before you talk to anyone, this comparison is really between RingCentral and Dialpad. RingCentral publishes three tiers (Core, Advanced, Ultra) with a clear feature ladder and the deepest AI add-on catalog of the three. Dialpad undercuts it on entry price — $15/user/month for its Connect Standard plan, the cheapest published rate here — and bakes AI transcription and call summaries into that base tier rather than reserving them for a higher plan. 8×8 is the odd one out: it quietly stopped listing prices on its own site at the end of 2023, and every current source we checked, including 8×8’s own pricing page, routes visitors to a sales conversation instead of a number. That makes it effectively impossible to compare 8×8’s cost against the other two without a quote in hand.
What Each Tool Is
RingCentral sells RingEX, a cloud phone system bundling unlimited domestic calling, HD video meetings (up to 300 participants even on the entry tier), SMS, and an AI Virtual Assistant. Its pricing page shows three core tiers plus a separate, quote-only “AI Customer Engagement Bundle” that layers in a full AI receptionist and conversation-intelligence suite.
Dialpad actually sells three separate product lines rather than one: Connect (the plain business-phone product most comparable to RingCentral and 8×8), Sell (an AI-powered sales dialer), and Support (an AI contact-center product). For a fair side-by-side with RingCentral and 8×8, this review focuses on Connect, which is Dialpad’s core phone system.
8×8 sells “8×8 Work” as part of a broader voice, video, chat, and contact-center platform. Historically it published tiered plans (X2, X4, X6, and so on), but its own pricing page no longer shows any of those figures — it directs every visitor to request a quote instead.
Pricing Breakdown
Plan
Price
What you get
RingCentral Core
$20/user/mo annual, $30 monthly
AVA AI assistant, unlimited domestic calling, on-demand call recording, 100 toll-free minutes, 25 SMS users/mo, HD meetings up to 300 participants
RingCentral Advanced
$25/user/mo annual, $35 monthly
Everything in Core, plus CRM integrations, multi-site support, reporting, 1,000 toll-free minutes
RingCentral Ultra
$35/user/mo annual, $45 monthly
Everything in Advanced, plus unlimited storage, real-time insights, device analytics, 10,000 toll-free minutes
RingCentral AI Customer Engagement Bundle
Contact sales
Everything in Ultra, plus AI Receptionist, ACE conversation intelligence, coaching and deal scoring
Dialpad Connect Standard
$15/user/mo
Unlimited calls, HD calls and meetings, real-time transcripts, instant call summaries, built-in messaging
Dialpad Connect Pro
$25/user/mo
Everything in Standard, plus key CRM integrations and 24/7 support
Dialpad Connect Enterprise
Contact sales
Everything in Pro, plus SSO, user access controls, unlimited office locations, 99.9% uptime SLA
8×8 Work (all tiers)
Contact sales
8×8 stopped publishing prices in late 2023; its own pricing page no longer lists any tier or dollar figure for Work
RingCentral
Pros
Transparent, published per-seat pricing across three real tiers, not just an entry price
High meeting capacity — 300 participants — even on the cheapest Core tier
Broad add-on catalog: Rooms, Webinar, Push to Talk, and a standalone RingCX contact center
AI Virtual Assistant ships standard from Core, not reserved for a top tier
Cons
Monthly (non-annual) billing costs noticeably more — $30/user vs. $20 annual on Core
The full AI Customer Engagement Bundle is quote-only, hiding the top-end price
RingCentral’s own trial page gives conflicting numbers for how many users and lines the 14-day free trial covers
Unlimited storage and real-time insights require jumping all the way to Ultra
Dialpad
Pros
Cheapest published entry price of the three: $15/user/month for Connect Standard
AI transcripts, call recaps, and PII redaction are included at the base tier, not gated behind an upgrade
Separate, purpose-built product lines (Connect, Sell, Support) instead of one bundle trying to do everything
Cons
Dialpad’s most AI-forward features (Live Coach, Quality Management, Workforce Management) live in the pricier Sell and Support products, not in Connect
Enterprise-tier Connect pricing (SSO, access controls) is quote-only
The pricing page doesn’t state a minimum seat count or spell out the monthly-vs-annual discount percentage
8×8
Pros
Positions itself as one login for voice, video, chat, and contact center rather than splitting products the way Dialpad does
Advertises a 30-day free trial, longer than RingCentral’s 14 days
Long-established VoIP vendor with broad enterprise contact-center experience
Cons
No public per-seat price anywhere on 8×8’s own site as of this review — pricing has been quote-only since the end of 2023
Third-party trackers disagree with each other on what 8×8 currently charges, and most explicitly flag their own figures as outdated or unverified
The free trial excludes hot desking, SSO, voicemail transcription, and integrations
Who It’s a Good Fit For
RingCentral fits mid-size and larger teams that want a mature, published tier ladder and are willing to pay more for high meeting capacity and a growing AI add-on suite. Dialpad fits budget-conscious small teams and startups that want transparent entry pricing with AI transcription built in from day one, plus sales or support teams that specifically want Dialpad’s dedicated Sell or Support products. 8×8 only makes sense if you’re already running a multi-vendor RFP and don’t mind a sales process before you see a number.
Who Should Look Elsewhere
If you need to build a budget estimate before anyone will take a sales call, 8×8 is the wrong starting point — you cannot get a number without talking to its team first. If your main priority is the single lowest published per-seat price, RingCentral’s Core tier at $30/month billed monthly is the most expensive of the three transparent options; compare it against Dialpad’s $15 Connect Standard tier for the same basic use case before committing.
Bottom Line
Dialpad wins on transparent, AI-inclusive entry pricing. RingCentral wins on breadth — more tiers, more add-ons, more meeting capacity — if you’re willing to pay for it. 8×8 can’t be fairly scored on price at all right now, because it’s the only one of the three that won’t tell you what it costs without a sales conversation. Get a live quote from 8×8 before ruling it in or out, and don’t trust any third-party number you see for it without checking it against 8×8 directly.
FAQ
Does 8×8 publish its pricing anywhere? No. As of this review, 8×8’s own pricing page shows no dollar figures for any tier and routes every visitor to a quote request. It reportedly stopped publishing prices publicly at the end of 2023.
Which of these three is cheapest for a 10-person team? Based on published pricing, Dialpad’s Connect Standard at $15/user/month is the lowest entry price of the three. 8×8 can’t be compared on price without a quote.
Do any of these have a permanently free plan? No. All three offer a free trial only — 14 days for RingCentral, 30 days for 8×8 — with no permanent free tier.
Are AI features included standard, or do they cost extra? RingCentral’s AVA and Dialpad’s AI transcripts/call recaps are included at their entry tiers. RingCentral’s and Dialpad’s more advanced AI add-ons (AI Receptionist, Live Coach, Workforce Management) cost extra or require a higher tier. 8×8’s current AI feature set can’t be confirmed without a quote.
Sources
RingCentral — official plans and pricing page
Dialpad — official pricing page
8×8 — pricing availability confirmed as quote-only via multiple independent trackers (Tech.co, JoinSecret, Costbench), since 8×8’s own pricing page returns no dollar figures
Every application throws errors in production, and the question isn’t whether you’ll need an error-tracking tool but which one actually tells you what broke, how often, and whether it’s getting worse — before a support ticket does. Sentry, Rollbar, and Bugsnag (recently rebranded by its parent company SmartBear as “Insight Hub”) are three of the longest-running names in this category, and in 2026 they’ve diverged more than they’ve converged: one publishes every price on a self-serve page, and two push almost all meaningful plan details behind a sales conversation. We checked each vendor’s current pricing page before writing this comparison.
Essentials: scales 10K–50M occurrences/mo; no public dollar price
No — Essentials and Advanced show no listed price; quote required
Teams that want flexible occurrence-based scaling and are willing to talk to sales for pricing
Bugsnag (SmartBear Insight Hub)
1 user, 7,500 events/mo, 7-day retention
Select: scales 50K–3M events/mo; no public dollar price
No — Select and Preferred both show “starting at $0” with no actual figure
Teams already standardized on SmartBear’s broader testing/observability stack
Short Verdict
Sentry is the only one of the three that lets you see a real price before talking to anyone — its Team and Business tiers are both self-serve with a monthly or annual dollar figure published directly on the pricing page. Rollbar and Bugsnag both gate their paid tiers behind “contact us” once you move past the free plan, publishing only the usage ranges (occurrences, events, replays) rather than what any of it costs. If transparent, no-sales-call pricing matters to you, that alone may decide this comparison before you look at a single feature.
What Each Tool Actually Is
Sentry started as an open-source error tracker and has grown into a broader application-monitoring platform, adding performance tracing, session replay, and — more recently — “Seer,” an AI layer that performs root-cause analysis and can draft a fix for a flagged issue. Every tier includes ownership rules (auto-assigning errors to the engineer whose commit introduced them), suspect-commit detection, and release health tracking; higher tiers add anomaly detection, SAML/SCIM SSO, and a signed BAA for regulated teams.
Rollbar focuses more narrowly on error monitoring itself, with real-time grouping of occurrences into deduplicated items, deploy and version tracking, and — on its higher tiers — Rollbar Analyze, a query layer (RQL) plus a Metrics API for building custom error-trend dashboards. Rollbar’s pricing is structured entirely around monthly “occurrences” (individual error events) and a separate “credits” allowance that scales with plan tier, rather than Sentry’s flatter per-tier error quota.
Bugsnag was acquired by SmartBear and, as of the company’s “Insight Hub” rebrand announcement, is being folded into a broader developer-observability product under that new name — though its dedicated pricing page at the time of writing still displays “Bugsnag” branding without the Insight Hub name attached. Its core differentiators are stability scoring (a single health metric blending crash-free users and sessions) and, on its Preferred tier, “System Metrics” that pull in device-level CPU, memory, and rendering data alongside the error itself — useful specifically for mobile and client-side crash diagnostics.
Pricing Breakdown
Tool / Tier
Price
Notes
Sentry Developer (Free)
$0
1 user, 5,000 errors/mo, 5M spans, 50 replays, 10 dashboards, 30-day retention, no API access
Sentry’s pricing page is the only one of the three where every number above the free tier is a dollar figure you can act on without a form submission. Rollbar’s and Bugsnag’s pages instead show usage-range sliders (occurrences, events) with no price attached — which makes a true apples-to-apples cost comparison between all three impossible to complete from public information alone; budgeting for Rollbar or Bugsnag at any real scale requires a sales conversation first.
Pros and Cons
Sentry
Pros: fully transparent self-serve pricing at every tier, broadest feature set (errors + performance tracing + session replay + AI root-cause triage in one product), large ecosystem of SDKs and integrations.
Cons: Seer’s AI features add extra cost on top of the base plan and were mid-transition to new credit-based pricing at the time of writing; the Developer (free) tier’s 5,000-error cap is tighter than Rollbar’s or Bugsnag’s free-tier equivalents in absolute event count.
Rollbar
Pros: flexible occurrence-based scaling from 10K to 50M+ per month without changing product tier, Rollbar Analyze gives genuine custom-query access to error trends, a real 14-day full-access trial of the Advanced tier.
Cons: no public price above the free tier, so budgeting requires sales contact; fewer built-in performance/tracing features than Sentry’s broader platform.
Bugsnag (SmartBear Insight Hub)
Pros: stability-score health metric is genuinely useful for mobile/client teams, System Metrics (device CPU/memory/rendering) is a differentiator for crash diagnostics, broadest free-tier platform/SDK support (50+ platforms).
Cons: no public price at any paid tier, shortest free-tier data retention of the three (7 days vs. 30 for Sentry and Rollbar), and the in-progress Insight Hub rebrand means the product’s name and positioning may shift again on short notice.
Who It’s a Good Fit For
Choose Sentry if you want to see a real price today, sign up without a sales call, and get performance tracing and session replay bundled with error tracking rather than bought separately. Choose Rollbar if your error volume is highly variable and you want occurrence-based scaling plus a genuine query layer (RQL) for building custom error-trend reporting, and you’re fine negotiating price directly. Choose Bugsnag/Insight Hub if you need deep mobile or client-side crash diagnostics with device-level telemetry, or you’re already a SmartBear customer for testing tools and want one vendor relationship.
Who Should Look Elsewhere
Teams that need to budget precisely before committing, with no sales call in the process, should be cautious with Rollbar and Bugsnag above the free tier, since neither publishes a self-serve dollar price — Sentry is the only one of the three that fully supports that requirement. Teams needing more than 30 days of error retention on a free plan should skip Bugsnag’s 7-day free tier. And teams that specifically want deep performance tracing alongside error tracking, not just crash/exception monitoring, will find Sentry’s broader platform a better fit than either Rollbar’s or Bugsnag’s narrower error-first focus.
Bottom Line
All three tools do the core job — catching, grouping, and surfacing errors with enough context to fix them — competently. The real differentiator in 2026 isn’t feature depth so much as how each vendor sells: Sentry treats price as something you should be able to see without talking to anyone, while Rollbar and Bugsnag treat it as something to negotiate once you’re past the free tier. If pricing transparency is itself a requirement for your team, that alone makes Sentry the default; if it isn’t, compare the free tiers directly against your actual error volume before starting a sales conversation with the other two.
FAQ
Is Bugsnag now called “SmartBear Insight Hub”? SmartBear announced the Insight Hub rebrand as part of a broader developer-observability push, but as of this writing Bugsnag’s own public pricing page still displays Bugsnag branding without an Insight Hub name change applied — expect the naming to be in transition.
Which tool has the most generous free tier? By raw event/error count, Bugsnag’s free tier (7,500 events/mo) is slightly larger than Sentry’s (5,000 errors/mo) and Rollbar’s (5,000 occurrences/mo), but Bugsnag’s free-tier retention is shortest at 7 days versus 30 days for the other two.
Can I get an exact price for Rollbar or Bugsnag without contacting sales? Not from their public pricing pages as published — both show usage ranges (occurrences or events) for their paid tiers with no dollar amount attached, unlike Sentry, which lists its Team and Business prices directly.
Do any of these tools include AI-assisted fixes? Sentry’s Seer feature performs AI root-cause analysis and can draft a fix, available from the Team tier up at extra cost; the vendor’s pricing page notes new credit-based Seer pricing was rolling out. Rollbar’s and Bugsnag’s public pricing pages do not list a comparable AI-fix feature.
Native advertising — the “recommended articles” and “you might also like” widgets at the bottom of news and blog pages — is still a multi-billion-dollar corner of digital advertising, run by a small number of content-discovery networks that pay publishers for ad real estate and sell that reach to advertisers. Before comparing Taboola, Outbrain, and MGID on their merits, there’s a corporate-structure fact worth getting straight, because it’s easy to get wrong: there is no merged “Taboola-Outbrain” company. That’s a different, older story than what actually happened.
At a Glance
Spec
Taboola
Outbrain (now Teads)
MGID
Current corporate status
Independent public company (Nasdaq: TBLA)
Acquired Teads from Altice in Feb. 2025; renamed itself “Teads Holding Co.” (Nasdaq: TEAD) effective June 10, 2025 — the Outbrain name is retired at the corporate level
Independent, privately held
Self-serve advertiser signup
Yes, via its “Realize” performance advertising platform
Not published on its current official page; “Contact Us” is the primary call to action
Yes, confirmed on MGID’s own site
Published minimum spend
None published; third-party guides commonly cite $50–$300/day as a practical starting budget
None published
$50 minimum campaign budget; $100 minimum account deposit (both stated on MGID’s own blog)
Best for
Large-scale premium publisher reach (CNN, NBC News, Business Insider feeds)
Advertisers who also want Teads’ video/outstream and CTV inventory alongside native
Advertisers wanting the lowest-cost entry point and granular self-serve control
Correcting the Record: Taboola and Outbrain Did Not Merge
Taboola and Outbrain did attempt to merge once — announced in October 2019, in a deal that would have combined the two into a roughly $2 billion company under the Taboola name. That deal collapsed in September 2020 after nearly a year of negotiations, reportedly over price disagreements and regulatory scrutiny in the UK and Israel, and the two companies have operated as separate competitors ever since. There has been no subsequent Taboola-Outbrain merger.
What did happen, and what easily gets confused with a “Taboola-Outbrain merger,” is this: Outbrain acquired Teads — a separate video and outstream advertising company previously owned by Altice — in a roughly $1 billion deal that closed in February 2025. Outbrain then formally changed its own corporate name to “Teads Holding Co.,” effective June 10, 2025, with a new Nasdaq ticker (TEAD) replacing its old one (OB), per the company’s own investor-relations press release. In short: Outbrain is now legally and operationally Teads. Taboola was not involved in that transaction and remains a separate, independent public company. Advertisers and publishers who built campaigns or placements under the “Outbrain” name should expect that brand to be retired or absorbed into Teads’ platform going forward, even though many comparison articles (including some written in 2026) still refer to “Outbrain” out of habit.
What Each Platform Is
Taboola runs the content-recommendation widgets on a large roster of premium publisher sites, including NBC News, Business Insider, and USA Today, reaching what the company has claimed is over 500 million daily active users across its network. Advertisers bid to appear in those widgets on a CPC basis, targeted by audience, device, geography, and interest signals Taboola builds from its publisher network’s traffic. In 2024–2025, Taboola expanded its platform under the “Realize” brand, positioning itself as a broader performance-advertising platform for the open web rather than only a native-widget network.
Outbrain (now operating as Teads) historically ran a comparable content-recommendation network on publishers like CNN and Sky News, competing directly with Taboola for the same “recommended for you” ad slots. Since absorbing Teads’ video, outstream, and connected-TV advertising technology, the combined company’s current official marketing centers on the “Teads Ad Manager” platform and leans toward broader omnichannel (native plus video plus CTV) advertiser engagements rather than a narrowly self-serve native-only product — its current official advertiser page funnels visitors to “Contact Us” rather than a public self-serve signup flow.
MGID is an independent native advertising network that has stayed out of the Taboola/Outbrain consolidation story entirely, positioning itself as a self-serve-friendly alternative with a lower cost of entry. MGID’s own materials describe an auction-based CPC model, a “Reachmeter” planning tool for estimating impression volume, built-in retargeting and automated CPA-target bidding, and a free account manager available to help new advertisers size campaigns and budgets.
Pricing and Minimum Spend
Platform
Minimum deposit / budget
Pricing model
Self-serve?
Taboola (Realize)
No published hard minimum; third-party guides commonly suggest $50/day as a practical starting campaign budget and roughly $300/day to fully exit the learning phase, but these are not figures Taboola publishes itself
No published minimum on its current official page; the platform doesn’t publish a fixed minimum, and third-party estimates of a $250/day practical starting point are industry commentary, not a stated platform rule
CPC auction
Not clearly advertised as self-serve on its current official page; “Contact Us” is the primary funnel
MGID
$50 minimum campaign budget (daily or overall); $100 minimum account deposit; a $650+ deposit is MGID’s own suggested starting point for a meaningful test
CPC auction (illustrative optimal CPC cited by MGID is around $0.12, highly GEO- and vertical-dependent); CPM available for specific formats
Yes, clearly self-serve with an account manager available at no extra cost
How Native Ad Networks Actually Work
On the publisher side, a site installs a content-recommendation widget (typically below an article) and gets paid for the traffic it sends into the network, usually on a revenue-share basis. On the advertiser side, you upload a “story” — a headline, thumbnail image, and destination URL designed to look like an editorial recommendation rather than a traditional banner ad — and bid on a cost-per-click basis to have it surfaced in those widgets across the publisher network. All three platforms optimize placement using algorithms that weigh predicted click-through and downstream engagement, which means campaigns typically need a real “learning phase” of spend and data before cost-per-click or cost-per-acquisition stabilizes — a dynamic every guide to these platforms, including vendor-neutral and MGID’s own content, describes consistently.
Pros and Cons
Taboola — Pros: largest premium publisher roster among the three; genuine self-serve option plus managed service for bigger budgets; “Realize” platform expansion adds broader performance-ad formats beyond classic native widgets. Cons: no published minimum spend makes early budgeting a guessing game; third-party estimates suggest real competitiveness requires meaningfully more than a token daily budget.
Teads (formerly Outbrain) — Pros: inherits Teads’ video/outstream and CTV inventory, giving advertisers a broader cross-format buy than a native-only network; still reaches a comparable premium publisher roster to Taboola. Cons: its current official page is oriented toward “Contact Us” rather than an obvious self-serve signup, which raises the effective barrier to entry versus Taboola or MGID for small advertisers; the 2025 rebrand means some of its older self-serve tooling and documentation under the Outbrain name may be in flux.
MGID — Pros: the only one of the three with a clearly published, low minimum deposit ($100) and campaign budget ($50); free account-manager support for new advertisers; strong self-serve tooling (Reachmeter, CPA Tune automated bidding, multiple tracking integrations). Cons: smaller premium publisher roster than Taboola or Teads; traffic quality and brand safety require more hands-on vetting than on the two larger, more curated networks.
Who It’s a Good Fit For
Choose Taboola if you want the largest reach across premium, recognizable publisher brands and are comfortable testing budget upward without a published minimum to anchor on. Choose Teads (formerly Outbrain) if you want native placement bundled with video, outstream, or CTV inventory as part of a broader cross-format buy, and you’re comfortable starting that relationship through a sales conversation rather than instant self-serve signup. Choose MGID if you want the lowest, most clearly published cost of entry, direct self-serve control, and free account-manager help sizing your first test campaign.
Who Should Look Elsewhere
Advertisers who need precise, upfront budget certainty before committing any spend may be frustrated by all three platforms’ lack of a hard published minimum (MGID aside, which does publish one) — expect to treat your first few hundred to few thousand dollars as a genuine, non-refundable learning-phase test rather than a guaranteed-performance buy. Publishers evaluating which network to install should note that choosing between these three is a separate decision from the advertiser-side comparison in this piece, and generally comes down to fill rate and RPM testing specific to a given site’s traffic.
Bottom Line
Taboola and Teads (the company formerly known as Outbrain) remain the two largest premium-publisher native networks, operating as fully independent competitors rather than a merged entity — the 2019 merger attempt between Taboola and Outbrain fell apart in 2020, and Outbrain’s 2025 transformation was a separate acquisition of Teads, not a Taboola tie-up. MGID remains the clearest self-serve, lower-budget alternative to both, with published minimums the other two don’t offer. Whichever you choose, budget your first campaign as a real test of cost-per-click and conversion economics on your specific offer rather than assuming headline reach numbers translate directly into performance.
FAQ
Did Taboola and Outbrain merge? No. They attempted to merge in 2019–2020 and that deal was called off. In 2025, Outbrain separately acquired Teads and renamed its own corporate entity to Teads Holding Co. — an unrelated transaction that didn’t involve Taboola.
Is “Outbrain” still a brand I can advertise under? The parent company is now legally Teads Holding Co. (Nasdaq: TEAD) as of June 2025. Advertisers should check the current official site for how legacy Outbrain-branded placements and tools are being transitioned, since the company’s own marketing now centers on the Teads name.
What’s the real minimum budget to test a native campaign? Only MGID publishes a hard number ($50 minimum campaign budget, $100 minimum deposit). Taboola and Teads don’t publish minimums; third-party guides suggest budgeting at least a few hundred dollars for a real test on either platform, but treat that as an estimate, not an official figure.
Do these platforms disclose when content is a paid ad? Yes — native advertising widgets from all three are required to carry disclosure labels such as “Promoted,” “Sponsored,” or “Ads by [network],” per self-regulatory native-advertising guidelines and increasingly explicit consent and disclosure rules in jurisdictions like the EU.
Sources
Teads Investor Relations — “Outbrain Completes Change of Corporate Name to Teads” (June 2025 press release)
MarketingDive — “Taboola, Outbrain merger collapses, ending bid to form rival to walled gardens” (Sept. 2020)
Teads — “Outbrain Completes the Acquisition of Teads” (Feb. 2025)
Issue tracking is the one tool an engineering team touches on every single ticket, every sprint, every pull request. Unlike a general project-management app, a developer-focused tracker has to work inside the actual software delivery loop: backlogs that feed sprints, roadmaps that survive reprioritization, and — critically — a two-way link to the commits, branches, and pull requests that close the loop. Jira, Linear, and GitHub Issues represent three very different answers to that problem: Jira’s deep, configurable workflow engine; Linear’s fast, opinionated single-tool experience; and GitHub Issues, the free tracker that lives inside the same platform as your code, CI, and pull requests. We checked each vendor’s current pricing pages before writing this comparison.
At a Glance
Tool
Starting Paid Price
Free Tier
CI/CD & PR Integration
Best For
Jira
$9.70/user/mo (Standard, 1–100 users)
Up to 10 users, 2GB storage, 100 automation runs/mo
Smart Commits, native Bitbucket integration, GitHub/GitLab via Atlassian’s official app, branch-and-commit linking in the issue view
Large engineering orgs with multi-team workflows, compliance needs, and custom processes
Linear
$10/user/mo (Basic, billed yearly)
Unlimited members, 2 teams, 250 issues
Native two-way GitHub/GitLab sync — PRs auto-link to issues, issues auto-move through workflow states on PR open/merge
Product-engineering teams who want sprints, backlog, and PR status in one fast tool
GitHub Issues
$0 — bundled free with every GitHub plan
Unlimited issues, Projects boards, and milestones on Free, Team ($4/user/mo), and Enterprise ($21/user/mo)
Git-native: closing keywords in commits/PRs auto-close issues, GitHub Projects boards built from the same issues, GitHub Actions can react to issue/PR events directly
Teams who already live in GitHub and want zero context-switching between code and tracker
Short Verdict
If your team’s pain point is specifically the handoff between issues and code — sprints that stall because nobody can tell which PR closes which ticket, or roadmaps that drift out of sync with what’s actually merged — the right tool depends on where your workflow already lives. GitHub Issues is free and wins on git-native integration by definition: the issue tracker and the code host are the same product, so there’s no sync to break. Linear wins on speed and opinionated sprint/backlog hygiene for teams willing to adopt its workflow as-is. Jira wins when the org is big enough, or compliance-bound enough, that configurable workflows and audit trails matter more than minimal setup.
What Each Tool Actually Is
Jira (Atlassian) is the industry-standard, enterprise-configurable issue tracker, and every plan includes unlimited projects and work items, Scrum and Kanban boards, and — starting with Standard — automation rules, custom permission schemes, and audit logs. For engineering workflows specifically, Jira’s Smart Commits let a developer reference, transition, or log time against an issue directly from a git commit message (e.g. PROJ-123 #done #time 2h Fixed the race condition), and Atlassian’s own GitHub for Jira and GitLab for Jira apps add branch-and-PR visibility straight into the issue view — you can see every linked branch, commit, and pull request, including its merge status, without leaving Jira.
Linear takes the opposite design approach: a deliberately narrow, keyboard-first interface with a workflow that’s largely pre-decided for you (triage, backlog, in progress, in review, done). Its GitHub and GitLab integrations are native and two-way: opening a PR that references an issue (via branch name or a magic word in the description) automatically links it and moves the issue to “In Review,” and merging the PR moves the issue to “Done” — no Smart Commit syntax to remember, because the state transition is wired into the PR lifecycle itself rather than the commit message.
GitHub Issues is the free, built-in tracker on every GitHub repository, and it is structurally different from the other two: it isn’t a separate product syncing with your code host, it is your code host. Closing keywords (Fixes #42, Closes #42) in a commit message or PR description auto-close the referenced issue the moment that PR merges into the default branch — the same mechanism Jira and Linear have to build integrations to approximate. GitHub Projects (included free) turns a filtered view of your Issues and PRs into a Kanban board, backlog, or roadmap with custom fields, and GitHub Actions can trigger directly off issue and PR events (labeled, opened, closed) for custom sprint automation without a third-party integration layer at all.
Sprints, Backlogs, and Roadmaps: How the Three Compare
Jira: Scrum and Kanban boards are built-in on every plan; Advanced Roadmaps (multi-project, dependency-aware timeline planning) is a Premium-tier feature. This is the deepest sprint/backlog tooling of the three, with burndown charts, velocity reports, and cross-team dependency tracking out of the box.
Linear: Cycles (Linear’s name for sprints) and a prioritized backlog are core to the product on every paid tier, with automatic cycle rollover and a clean, opinionated backlog-grooming flow. Linear Insights (Business tier and up) adds built-in velocity and cycle reporting; there’s no dedicated multi-project roadmap tool as deep as Jira’s Advanced Roadmaps.
GitHub Issues: Sprints and roadmaps aren’t native concepts — you build them yourself inside GitHub Projects using iteration fields, custom views, and saved filters. This is more flexible but requires more setup than Jira’s or Linear’s pre-built sprint model, and there’s no built-in burndown/velocity chart without a third-party Action or export.
Pricing Comparison
Plan
Jira
Linear
GitHub (covers Issues + everything else)
Free
$0 — up to 10 users, 2GB storage, 100 automation runs/mo, basic boards
The framing that matters here: Jira’s and Linear’s prices are for the issue tracker alone. GitHub’s per-user price is for the entire platform — source control, Actions CI/CD, Codespaces, and (on Enterprise) Copilot — with Issues as one included feature rather than a separate line item. A team already paying for GitHub Team or Enterprise seats is getting its issue tracker at effectively $0 marginal cost; a team on GitHub Free gets a fully-featured tracker with zero cost at all, which neither Jira’s nor Linear’s free tiers fully match once you need more than 10 users or more than 250 issues.
Pros and Cons
Jira
Pros: unmatched workflow configurability, Advanced Roadmaps for multi-team dependency planning, Smart Commits and dedicated GitHub/GitLab apps for code linking, deepest third-party marketplace of any tracker.
Cons: commit-message syntax (Smart Commits) is an extra habit to enforce across a team; free tier caps at 10 users with no roles/permissions; setup and admin overhead is real.
Linear
Pros: native two-way PR sync with automatic state transitions, fast keyboard-first UI, generous free tier for small teams, clean built-in cycle/backlog workflow.
Cons: no Jira-depth multi-project roadmap tool; less workflow customization for teams with unusual processes; SSO limited to Google below Enterprise.
GitHub Issues
Pros: genuinely free and git-native — no sync layer between tracker and code because they’re the same product; closing keywords and Actions give CI/CD-level automation without a third-party app; GitHub Projects boards are flexible and free.
Cons: no built-in sprint/velocity/burndown reporting; building a real roadmap or sprint cadence takes manual Projects configuration; weaker for non-engineering stakeholders (support, sales, legal) who need a simpler, less code-centric view than GitHub provides.
Who It’s a Good Fit For
Choose GitHub Issues if your whole engineering org already lives on GitHub and you want the issue tracker, the PR review, and the CI/CD pipeline wired together natively with nothing to configure or pay for separately. Choose Linear if you want a fast, opinionated sprint/backlog workflow with automatic PR-driven state transitions and you’re comfortable adapting your process to the tool. Choose Jira if you need configurable workflows across multiple teams, compliance features like audit logs, or Advanced Roadmaps-level dependency planning across projects that span more than just engineering.
Who Should Look Elsewhere
Teams that need their issue tracker to serve non-technical stakeholders — support, sales, or leadership views with no git context at all — will find GitHub Issues too code-centric and should look at Jira or Linear instead. Teams on GitLab, Bitbucket, or self-hosted git can’t use GitHub Issues at all. And teams that want zero setup and zero per-seat cost at real scale (more than 10 users, unlimited issues, actual automation) will find that Jira’s and Linear’s free tiers run out quickly, while GitHub’s stays free well past that point as long as you don’t need Team/Enterprise-only features like Codespaces or SSO.
Bottom Line
This isn’t really a three-way popularity contest — it’s a question of where your code already lives. If it’s on GitHub and your team is engineering-only, GitHub Issues removes an entire category of sync problems for free. If you need fast, opinionated sprint hygiene with clean PR-driven automation across a product-engineering org, Linear is purpose-built for that. If you’re coordinating multiple teams, need compliance features, or have workflows too irregular for either tool’s defaults, Jira’s configurability is still worth its setup cost. Run a real sprint in each tool’s free tier against your actual backlog before committing — the switching cost in migrated history and retrained habits is the real price of this decision, not the sticker price.
FAQ
Is GitHub Issues really free, or only for public repos? It’s free on private repositories too, on every GitHub plan including the free one — unlimited issues, Projects boards, and milestones are included. You only pay if you need other GitHub features (Codespaces, SSO, more CI/CD minutes), not for Issues itself.
Does Jira get cheaper per user as my team grows? Yes — Atlassian’s published pricing tables show per-user list prices declining in tiers as total user count rises, from $9.70/user/month at 1–100 users on Standard down to a few dollars per user at the highest volume tiers.
Can Linear or GitHub Issues replace Jira’s Advanced Roadmaps for multi-team dependency planning? Not out of the box. Linear has no equivalent multi-project roadmap tool, and GitHub Projects can approximate one with custom fields and views but has no built-in cross-team dependency visualization — both require more manual setup than Jira’s Premium-tier roadmapping.
Which tool integrates most tightly with pull requests? GitHub Issues, by construction — the issue and the PR are on the same platform, so closing keywords work natively with no third-party app. Linear is a close second with native two-way GitHub/GitLab sync and automatic status transitions. Jira requires its official GitHub/GitLab/Bitbucket apps or Smart Commit syntax to get comparable visibility.
Every business backup strategy built on object storage eventually runs into the same three-way decision: Backblaze B2, Wasabi, or AWS S3. All three speak the S3 API, so the same backup software — Veeam, restic, rclone, Duplicati, Arq, Synology Hyper Backup — can point at any of them with a config change. What actually differs is the economics: how storage is priced per class, what egress (download) costs when you need to restore after an incident, minimum retention rules, and the durability guarantees each vendor puts in writing. This piece compares what each vendor’s own pricing pages state today, not list prices from memory.
At a Glance
Spec
Backblaze B2
Wasabi
AWS S3 (Standard)
Base storage price
$6.95/TB/month
$7.99/TB/month flat
$23/TB/month (first 50TB)
Egress (download)
Free up to 3x avg. storage/month, then $0.01/GB
$0 — no egress fees at all
First 100GB/month free, then $0.09/GB tiering down to $0.05/GB
Minimum retention
None
90 days (Pay As You Go); 30 days (Reserved Capacity)
None for Standard; 30–180 days for IA/Glacier tiers
Durability (vendor-stated)
99.999999999% (11 nines)
99.999999999% (11 nines)
99.999999999% (11 nines)
S3-API compatible
Yes
Yes
Native
Best for
Lowest blended cost for active backup + occasional restores
Predictable flat-fee storage with zero egress anxiety
Deepest feature set, tiering, and ecosystem integration
Short Verdict
If your backup software just needs cheap, reliable, S3-compatible storage and you occasionally need to pull large restores, Backblaze B2 or Wasabi will beat AWS S3 on total cost by a wide margin — egress is where S3 gets expensive fast during an actual disaster-recovery event. Between the two challengers, Wasabi’s flat $7.99/TB with zero egress fees is the simplest to budget for predictable, always-on backup jobs; Backblaze B2’s $6.95/TB base rate plus free egress up to 3x your stored volume is cheaper for shops that restore more selectively and want pay-as-you-go flexibility without a 90-day minimum retention clock. AWS S3 still wins when you need its storage-class tiering (Glacier Deep Archive at under $1/TB/month for cold archives), tight integration with other AWS services, or your backup tool is specifically optimized for S3 lifecycle policies.
What Each Platform Is
Backblaze B2 is S3-compatible object storage built by Backblaze, the same company behind the well-known consumer backup product, but B2 is a separate business-grade storage service with its own API, console, and billing. It’s commonly paired with backup tools like Veeam (as an immutable backup target), restic, rclone, and Synology/QNAP NAS backup integrations, and is also usable as a direct drop-in replacement for S3 buckets in scripts and apps.
Wasabi is a storage-only cloud vendor — it has no compute, no CDN, no AI services, just S3-compatible buckets. That focus is also its pricing pitch: one flat per-TB rate with no egress or API request fees of any kind, which Wasabi states plainly on its own pricing page. It’s widely used behind backup software (Veeam is an official “Alliance Partner” integration) and by media/surveillance workloads that move large files in and out frequently.
AWS S3 is the original and still-dominant object storage service, with the deepest storage-class ladder of the three: Standard, Standard-IA, Glacier Instant Retrieval, Glacier Flexible Retrieval, and Glacier Deep Archive, each with a different storage price, retrieval fee, and minimum retention period. Most major backup software (Veeam, Commvault, Rubrik, Druva) has native, first-class S3 integration, and S3 is the default target for countless CI/CD and application backup scripts already running in AWS.
Free up to 3x average monthly storage, then $0.01/GB; free via Cloudflare, Fastly, bunny.net, and other partner CDNs
$0 always, per Wasabi’s own pricing page
First 100GB/mo free (account-wide), then $0.09/GB up to 10TB, $0.085/GB next 40TB, $0.07/GB next 100TB, $0.05/GB beyond 150TB
API / request fees
Classes A–C free (pay-as-you-go); Class D (downloads via API) $0.004 per 10,000 calls after 2,500 free/day
$0 — no API request fees
GET: $0.0004 per 1,000 requests (Standard); PUT/other request classes priced separately on AWS’s site
The number that matters most for business continuity planning isn’t the storage rate — it’s what a real restore costs. Pulling back 10TB after an incident is free on Wasabi, costs roughly $70–$100 on Backblaze B2 (depending on how much you’d already downloaded that month against the 3x-free allowance), and costs roughly $900 on AWS S3 Standard egress pricing (after the first 100GB). That gap is the whole argument for using B2 or Wasabi as a secondary/DR backup target even for organizations that otherwise live on AWS.
Pros and Cons
Backblaze B2 — Pros: lowest base storage rate of the three; generous free-egress allowance for routine restore testing; no minimum retention period; native Veeam immutability support. Cons: no intermediate/cold storage tier for B2 proper (Overdrive requires a multi-petabyte commitment); smaller global footprint than AWS.
Wasabi — Pros: genuinely zero egress and API fees, which makes cost modeling trivial; flat rate regardless of region; Reserved Capacity Storage can push the effective rate lower on multi-year commitments. Cons: 90-day minimum retention on Pay As You Go means early deletions still get billed for the full 90 days; no storage-class tiering for colder, cheaper archival.
AWS S3 — Pros: unmatched storage-class ladder for tiering hot backups down to sub-$1/TB cold archives; deepest ecosystem and native support in nearly every enterprise backup tool; strongest compliance/certification paper trail. Cons: by far the most expensive egress of the three, which punishes exactly the scenario — a real restore — that backup exists for; Glacier tiers carry retrieval fees and minimum-duration penalties on top of storage cost.
Who It’s a Good Fit For
Choose Backblaze B2 if you want the lowest everyday cost with flexibility to delete or shrink backups at will, and you expect to test-restore periodically without worrying about a big surprise bill. Choose Wasabi if budget predictability matters more than flexibility — a flat per-TB number with zero egress fees is easy to put in a budget line and defend to finance, especially for video/surveillance or large media backup sets that get pulled back often. Choose AWS S3 if you’re already deep in the AWS ecosystem, need Glacier-tier pricing for long-term cold archives well under $1/TB/month, or your backup software’s lifecycle-policy automation is built specifically around S3’s storage classes.
Who Should Look Elsewhere
Organizations that need frequent, unpredictable large-scale restores (e.g., regular DR drills across many terabytes) should think twice before standardizing on AWS S3 Standard as the primary backup target, given its egress pricing. Organizations that need object storage with heavy compute or CDN integration baked into the same vendor are better served by AWS or another full-stack cloud provider rather than Wasabi, which deliberately offers storage only.
Bottom Line
For most businesses using dedicated backup software against S3-compatible object storage, Backblaze B2 and Wasabi are the more defensible defaults purely on egress economics — the cost of actually restoring data, which is the entire point of a backup. AWS S3 remains the right call when you need its storage-class depth or you’re backing up data that already lives in AWS and rarely needs to leave it. Run the numbers against your own expected restore frequency and volume before committing, since that one variable swings the total cost comparison more than the base storage rate does.
FAQ
Can I use Veeam, restic, or rclone with all three? Yes. All three expose an S3-compatible API, and Veeam, restic, rclone, Duplicati, and most other backup tools support any S3-compatible endpoint by changing the endpoint URL and credentials.
Which one is cheapest for pure storage with no restores? Backblaze B2 at $6.95/TB/month is the lowest base rate of the three, slightly under Wasabi’s $7.99/TB/month flat rate, and far under AWS S3 Standard’s $23/TB/month (though AWS’s Glacier Deep Archive at $0.99/TB/month is cheaper than either for true cold, rarely-touched data).
Does Wasabi really have zero egress fees with no catch? Wasabi’s own pricing page states no fees for egress or API requests. The real-world caveat isn’t egress — it’s the 90-day minimum storage duration on the Pay As You Go plan, which bills for 90 days even if you delete data sooner.
What does “11 nines” durability actually mean? 99.999999999% annual durability means, statistically, that if you stored 10 million objects for 10,000,000 years, you’d expect to lose roughly one object. All three vendors state this same figure for their standard storage class; it describes the odds of losing data to the storage system itself, not protection against accidental deletion or ransomware, which is why immutability/versioning settings in your backup software still matter.
This site has already covered Go’s concurrency model in depth — goroutines, channels, and the scheduler — and separately compared garbage collection across Java, Go, and Python at a conceptual level. Neither piece is about a specific Go release. Go 1.26, which shipped in February 2026, is worth its own look: it changes the garbage collector’s default behavior, adds two small but genuinely new language capabilities, rewrites a core toolchain command, and quietly ships post-quantum-ready TLS defaults. This piece sticks to what actually shipped in Go 1.26 itself, per the official release notes.
At a Glance
Fact
Detail
Release
Go 1.26, released February 2026, six months after Go 1.25
Headline runtime change
Green Tea GC (experimental in Go 1.25) is now the default garbage collector
Claimed GC improvement
10–40% reduction in GC overhead for GC-heavy programs; a further ~10% on newer amd64 CPUs (Intel Ice Lake / AMD Zen 4+) via vector instructions
Language changes
new(expr) now accepts an initializing expression; generic types can now refer to themselves in their own type-parameter list
Toolchain change
go fix rewritten into a “modernizers” framework built on go vet‘s analysis engine; cmd/doc removed in favor of go doc
Bootstrap requirement
Building Go 1.26 from source requires Go 1.24.6 or later
Short Verdict
Go 1.26 is a solid, unglamorous point release in the best Go tradition — no breaking changes to the language’s compatibility promise, but a default garbage-collector swap that should measurably help GC-heavy services with zero code changes, plus a handful of small ergonomic wins (initializing new(), self-referential generics) that Go developers have quietly wanted for years. The most consequential change for infrastructure teams specifically may be the least flashy one: Go’s TLS stack now defaults to hybrid post-quantum key exchange, which is a meaningful, no-effort step toward the same quantum-safe migration enterprises like IBM are pushing at the hardware and software layer (covered separately on this site).
Green Tea GC Becomes the Default
The biggest runtime change in Go 1.26 is that Green Tea, an experimental garbage-collector redesign introduced in Go 1.25, is now the default collector for every Go 1.26 program. Per the official release notes, the Go team expects a 10% to 40% reduction in GC overhead for real-world, GC-heavy programs. On newer amd64 hardware specifically — Intel Ice Lake or AMD Zen 4 and later — Green Tea gets a further roughly 10% reduction on top of that, because it uses vector instructions to scan small objects faster. Teams that need to roll back to the old collector can still do so by building with GOEXPERIMENT=nogreenteagc, but that escape hatch is expected to be removed entirely in Go 1.27, so Green Tea is clearly intended as permanent, not a toggle. Notably, Go 1.26 does not change the tuning knobs around the collector — GOGC and GOMEMLIMIT work exactly as before; it’s the collector’s internal algorithm that changed, not the controls you use to steer it.
Two Small Language Changes
Go 1.26 adds two language capabilities, both small in scope but each closing a long-standing gap. First, the built-in new function now accepts an expression specifying the variable’s initial value, not just a type. The release notes specifically call out optional pointer fields in serialization code as the motivating case:
type Person struct {
Name string `json:"name"`
Age *int `json:"age"` // age if known; nil otherwise
}
func personJSON(name string, born time.Time) ([]byte, error) {
return json.Marshal(Person{
Name: name,
Age: new(yearsSince(born)),
})
}
Before Go 1.26, getting a pointer to a computed value like this required an intermediate variable and a helper function; new(expr) collapses that into one line. Second, generic types can now refer to themselves within their own type-parameter list, which was previously disallowed:
type Adder[A Adder[A]] interface {
Add(A) A
}
func algo[A Adder[A]](x, y A) A {
return x.Add(y)
}
This pattern — a type constraint that references the type parameter it’s constraining — comes up in generic algorithms that need to guarantee a type can operate on itself (an Add method that takes and returns the same type, for example), and Go’s type checker previously rejected it outright.
Toolchain and Module Changes
go fix was rewritten and is now the home for “modernizers” — a suite of fixers that update code to current Go idioms and library APIs, built on the same analysis framework as go vet. It also includes a source-level inliner that honors //go:fix inline directives. The old, historical fixers that previously lived in go fix were removed.
go mod init now defaults to an older go directive version than the toolchain running it: a toolchain numbered 1.N.X writes go 1.(N-1).0 into go.mod, and a pre-release toolchain writes go 1.(N-2).0. In practice, Go 1.26 writes go 1.25.0 by default; running go get go@version after init changes it.
cmd/doc and go tool doc were deleted.go doc remains and takes the same flags and arguments.
pprof‘s web UI now defaults to the flame-graph view instead of the graph view, which is still available under View → Graph.
Security and Runtime Details Worth Knowing
Hybrid post-quantum TLS key exchange is now on by default. The SecP256r1MLKEM768 and SecP384r1MLKEM1024 hybrid key exchanges — combining classical elliptic-curve key exchange with the NIST-standardized ML-KEM post-quantum algorithm — are enabled by default in Go’s TLS stack, with no configuration required.
A new crypto/hpke package implements RFC 9180 Hybrid Public Key Encryption, including post-quantum hybrid key-encapsulation mechanisms.
Faster cgo calls: baseline call overhead is reduced by roughly 30%.
Heap base address randomization on 64-bit platforms, a security hardening measure specifically for programs using cgo.
An experimental goroutine leak profile (GOEXPERIMENT=goroutineleakprofile), served at /debug/pprof/goroutineleak, which the Go team intends to enable by default in Go 1.27.
io.ReadAll is about twice as fast and uses roughly half the memory in typical cases.
New errors.AsType, a generic, type-safe version of errors.As, and a new log/slog.NewMultiHandler that invokes multiple handlers at once.
Go 1.25 vs. Go 1.26 at a Glance
Area
Go 1.25
Go 1.26
Garbage collector
Green Tea GC available as an opt-in experiment
Green Tea GC is the default; opt-out removed in Go 1.27
new()
Type only — no initializing expression
Accepts an initializing expression
Generics
A type could not reference itself in its own type-parameter list
Self-referential generic type parameters are allowed
TLS defaults
Classical key exchange by default
Hybrid post-quantum key exchange (ML-KEM-based) enabled by default
go fix
Limited set of historical, hardcoded fixers
Rewritten “modernizers” framework plus a source-level inliner
Trade-offs
Pros
Cons
Green Tea GC’s 10–40% overhead reduction is essentially free performance for any GC-heavy service that upgrades
The Go team’s own 10–40% GC figure is a general expectation across “real-world” programs, not a guaranteed result for any specific workload
Post-quantum TLS defaults require no code or configuration changes to adopt
Go 1.26 is the last release supporting macOS 12 Monterey and the ELFv1 ABI on linux/ppc64, so some older deployment targets need planning before the next upgrade
Self-referential generics and initializing new() are small but genuinely useful ergonomic fixes with no downside for existing code
Building Go 1.26 from source requires a relatively recent bootstrap toolchain (Go 1.24.6+), which can matter for older build pipelines
Who It’s Relevant For
Any team running Go services in production, particularly latency- or throughput-sensitive ones where GC pause time matters, should treat the Green Tea GC default as reason enough to test an upgrade. Teams writing generic library code that previously hit Go’s self-referential-generics restriction, and anyone maintaining code with a lot of optional pointer fields (common in JSON-heavy APIs), will get immediate, direct benefit from the two language changes.
Who Should Look Elsewhere (or Wait)
Teams still deploying to macOS 12 Monterey or relying on the ELFv1 ABI on linux/ppc64 should treat Go 1.26 as their last release on those targets and plan the migration before moving to Go 1.27. Anyone depending on cmd/doc directly (rather than go doc) or on one of the historical go fix fixers that got removed will need to adjust tooling before upgrading.
Bottom Line
Go 1.26 doesn’t change the language in any way that breaks Go’s compatibility promise, but it’s a meaningfully useful release: a default GC that should reduce overhead for most programs with zero code changes, two small language features that close real gaps, a rewritten go fix aimed at keeping codebases current, and post-quantum-ready TLS defaults that quietly move the entire Go ecosystem a step closer to the same quantum-safe posture enterprises are being pushed toward at the hardware level. For most teams, it’s a low-risk, genuinely worthwhile upgrade.
FAQ
Do I need to change any code to benefit from Green Tea GC? No. It’s the new default garbage collector in Go 1.26; existing programs get it automatically on upgrade, with no code changes required. It can be disabled with a build flag if needed, though that option is expected to disappear in Go 1.27.
Does Go 1.26 change how GOGC or GOMEMLIMIT work? No. The official release notes describe no changes to those tuning variables; what changed is the garbage collector’s internal scanning algorithm, not the controls used to configure it.
What’s “self-referential generics” in plain terms? It means a generic type’s type parameter can now be constrained by a type that itself references that same type parameter — useful for patterns like an interface requiring a method that both takes and returns the implementing type. Go 1.25 and earlier rejected this at compile time; Go 1.26 allows it.
Is Go 1.26’s post-quantum TLS support related to IBM’s quantum-safe cryptography work? They’re separate efforts solving the same underlying problem. Go 1.26 enables hybrid post-quantum key exchange (based on the NIST-standardized ML-KEM algorithm) by default in its TLS stack; IBM’s Guardium Cryptography Manager and its z17/LinuxONE hardware, covered separately on this site, address quantum-safe migration at the enterprise cryptographic-inventory and mainframe-hardware level. Both ultimately rely on the same NIST-standardized algorithms.
Sources
The Go Blog — Go 1.26 Release Notes (go.dev/doc/go1.26)
The Go Blog — Go 1.26 announcement (go.dev/blog/go1.26)
Related reading on this site: Go’s Concurrency Model Explained (Goroutines, Channels, and the Go Scheduler), Garbage Collection Explained (Java, Go, and Python), The Go Programming Language in 2026, and IBM’s Quantum-Safe Cryptography Push.
IBM’s quantum story usually gets told as a race to build a fault-tolerant quantum computer — Nighthawk, Loon, and the 2029 Starling target, covered separately on this site. There’s a second, less flashy quantum story running in parallel at IBM: defending today’s encrypted data against the quantum computers of tomorrow. That’s quantum-safe (post-quantum) cryptography, and IBM has spent years positioning itself as a lead contributor to the new NIST standards and the enterprise software that helps organizations actually migrate to them. This piece is about that defensive side — distinct from IBM’s quantum-computing roadmap and from the broader Power11/watsonx enterprise-AI stack covered elsewhere on this site.
At a Glance
Fact
Detail
The core risk
“Harvest now, decrypt later” — adversaries collect encrypted data today and decrypt it once a sufficiently powerful quantum computer exists
NIST standards
FIPS 203 (ML-KEM, from Kyber), FIPS 204 (ML-DSA, from Dilithium), and FIPS 205 (SLH-DSA, from SPHINCS+), finalized August 13, 2024
IBM’s role
IBM researchers co-designed the CRYSTALS-Kyber and CRYSTALS-Dilithium algorithms that became ML-KEM and ML-DSA; IBM also contributed to SPHINCS+, the basis for SLH-DSA
IBM’s enterprise software
Guardium Quantum Safe (October 2024) → Guardium Cryptography Manager (October 2025, with certificate-lifecycle and database-encryption features from November 2025)
Hardware milestone
Post-quantum cryptography “now standard” on IBM z17 and LinuxONE Rockhopper 5 systems, generally available August 12, 2026
Short Verdict
IBM’s quantum-safe push is a genuinely substantive, multi-year effort rather than a marketing afterthought: it co-designed the algorithms NIST actually standardized, and it has shipped two generations of enterprise software to help organizations find and fix vulnerable cryptography, now backed by hardware that makes post-quantum algorithms the default on its newest mainframes. What IBM has not done — and, to its credit, does not claim to have done — is put a hard date on when a quantum computer capable of breaking today’s encryption will actually exist. That timeline remains genuinely uncertain, which is precisely why IBM’s own messaging focuses on starting the migration now rather than waiting for a deadline that hasn’t been set.
Why “Harvest Now, Decrypt Later” Is the Real Urgency
The threat model driving all of this isn’t “a quantum computer will break my encryption tomorrow.” It’s that today’s RSA- and elliptic-curve-based encryption (the math underlying most current key exchange and digital signatures) is vulnerable to a sufficiently powerful quantum computer running Shor’s algorithm — and that an adversary doesn’t need that computer to exist today to benefit. They can intercept and store encrypted traffic now, and decrypt it retroactively once such a machine exists. For data that needs to stay confidential for years or decades — health records, financial transactions, government and defense communications — that means the migration window has already started, regardless of exactly when a cryptographically relevant quantum computer (CRQC) arrives. IBM’s own public materials describe this dynamic explicitly but, notably, give no specific date for when a CRQC might exist, consistent with the broader research community’s position that the timeline remains genuinely uncertain.
IBM’s Role in the Actual NIST Standards
This isn’t a case of IBM riding someone else’s standard. On August 13, 2024, NIST finalized its first three post-quantum cryptography standards: FIPS 203 (the Module-Lattice-Based Key-Encapsulation Mechanism, ML-KEM, based on the CRYSTALS-Kyber algorithm), FIPS 204 (the Module-Lattice-Based Digital Signature Algorithm, ML-DSA, based on CRYSTALS-Dilithium), and FIPS 205 (the Stateless Hash-Based Digital Signature Algorithm, SLH-DSA, based on SPHINCS+). IBM Research was a co-developer of both CRYSTALS-Kyber and CRYSTALS-Dilithium and also contributed to SPHINCS+, meaning IBM-originated cryptographic work underpins two of the three finalized standards and informed the third. IBM’s research materials describe this as the product of “a long history in creating and implementing cryptography” and years of direct collaboration with NIST’s standardization process, though NIST itself has also said a fully standardized set of algorithms for every quantum-safe use case (particularly some key-exchange and signature scenarios) is still not complete, meaning this is an evolving standards landscape rather than a single finished checklist.
From Guardium Quantum Safe to Guardium Cryptography Manager
IBM’s enterprise tooling for this problem has shipped in two distinct generations. In October 2024, IBM launched Guardium Quantum Safe as part of its broader Guardium Data Security Center, offering visibility into an organization’s cryptographic posture: discovering which systems use RSA, DSA, or ECC (all considered quantum-vulnerable), mapping that against internal, external, and regulatory requirements, and consolidating findings into a single dashboard. A year later, in October 2025, IBM introduced Guardium Cryptography Manager, which goes further than visibility alone. It maps every encryption key and certificate to the specific IT assets it protects across hybrid and multi-cloud environments, uses a generative-AI engine to analyze cryptographic data and recommend remediation, assigns enterprise risk scores with audit-ready reporting, triggers automated remediation workflows for weak or expired certificates, integrates with HashiCorp Vault PKI for key and certificate lifecycle operations, and can monitor and start encryption on major enterprise databases agentlessly — without installing software on each database server. Certificate-lifecycle management and database-encryption features specifically became available starting in November 2025. IDC’s Heather West, cited in coverage of the Cryptography Manager launch, called this “the long-term transition toward quantum resilience” — and IBM’s own Institute for Business Value research, cited in the same reporting, found that only 30% of organizations have completed even a basic cryptographic inventory, which is the necessary first step before any actual migration can happen.
Guardium Quantum Safe vs. Guardium Cryptography Manager
Dimension
Guardium Quantum Safe (2024)
Guardium Cryptography Manager (2025)
Primary job
Discover and assess cryptographic posture
Actively manage and remediate cryptographic assets
Key/certificate mapping
Not a core focus
Maps every key/certificate to the assets it protects
Remediation
Flags risk; manual follow-up required
Automated remediation workflows for weak/expired certificates
Database encryption
Not included
Agentless monitoring and encryption enablement (from Nov. 2025)
AI component
Not described as AI-driven
Generative-AI analysis and remediation recommendations
Post-Quantum Crypto Reaches IBM’s Newest Hardware
The software side meets the hardware side in IBM’s z17 mainframe and LinuxONE Rockhopper 5 systems, where post-quantum cryptography is now a standard feature rather than an add-on, alongside Crypto Discovery & Inventory capabilities that give security teams a consolidated view of cryptographic posture across the enterprise — the same “know what you have before you can fix it” principle Guardium Cryptography Manager applies in software. These z17 single-frame and rack-mount configurations, along with LinuxONE Rockhopper 5 and LinuxONE 5 Express, became generally available on August 12, 2026, putting IBM’s quantum-safe defaults into production enterprise hardware rather than leaving the capability as an optional software layer.
Trade-offs
Pros
Cons
IBM co-designed two of the three actual NIST-finalized algorithms (ML-KEM, ML-DSA), not a proprietary alternative to the standard
Full standardization of every quantum-safe use case (particularly some signature and key-exchange scenarios) is still not complete per NIST, so the landscape keeps evolving
Post-quantum crypto is now a standard, not optional, feature on IBM’s newest mainframe hardware (z17, LinuxONE Rockhopper 5)
Benefits are strongest for organizations already on IBM Z/LinuxONE or already budgeting for a Guardium deployment; it’s not a universal, platform-agnostic fix
Guardium Cryptography Manager automates remediation, not just detection, closing a real gap most organizations have (only 30% have completed a crypto inventory, per IBM’s own IBV data)
No specific, dated timeline exists (from IBM or the broader research community) for when a cryptographically relevant quantum computer will exist, which can make urgency harder to communicate internally
Who It’s Relevant For
Organizations in regulated industries — financial services, healthcare, government, defense — handling data that needs to remain confidential for years or decades, where “harvest now, decrypt later” is a genuine long-horizon risk rather than an abstract one. It’s also directly relevant to any enterprise running IBM Z, LinuxONE, or a hybrid-cloud estate large enough that a manual cryptographic inventory isn’t realistic.
Who Should Look Elsewhere
Smaller organizations with short data-retention requirements and limited regulatory exposure may reasonably treat this as a lower near-term priority, given the absence of a firm CRQC timeline. Teams that have already standardized on a different vendor’s cryptographic-inventory and PKI tooling (cloud-native key management services, for instance) will likely find more value evaluating NIST’s standards directly against their existing stack rather than adopting IBM’s Guardium suite specifically.
Bottom Line
IBM’s quantum-safe cryptography effort is one of the more substantive, standards-grounded stories in its infrastructure portfolio: real contributions to the NIST algorithms that actually got finalized, two real generations of enterprise software built around them, and now default support in its newest mainframe hardware. The honest caveat, which IBM itself doesn’t try to paper over, is that nobody — IBM included — can say precisely when the threat this is all defending against will fully materialize. That uncertainty is exactly the argument IBM makes for starting the inventory and migration work now, while the cost of doing so is still manageable.
FAQ
What does “quantum-safe” or “post-quantum” cryptography actually mean? It refers to cryptographic algorithms designed to remain secure even against an attacker with a sufficiently powerful quantum computer, as opposed to current RSA/ECC-based cryptography, which quantum computers running Shor’s algorithm are expected to eventually break.
Did IBM invent the new NIST post-quantum standards? IBM researchers co-designed CRYSTALS-Kyber and CRYSTALS-Dilithium, which became NIST’s finalized ML-KEM (FIPS 203) and ML-DSA (FIPS 204) standards in August 2024, and contributed to SPHINCS+, the basis for SLH-DSA (FIPS 205). These were collaborative efforts involving multiple research institutions, not solely IBM’s work, but IBM was a significant, named co-developer.
What’s the difference between Guardium Quantum Safe and Guardium Cryptography Manager? Guardium Quantum Safe (2024) focuses on discovering and assessing an organization’s cryptographic posture. Guardium Cryptography Manager (2025) builds on that with active management: mapping keys and certificates to assets, AI-driven remediation recommendations, automated workflows, and agentless database encryption.
Is post-quantum cryptography mandatory on IBM’s latest hardware? IBM describes post-quantum cryptography as now “standard” on z17 and LinuxONE Rockhopper 5 systems, generally available since August 12, 2026, meaning it ships as a built-in capability rather than a separate purchase, though specific configuration and migration still requires enterprise planning.
When will a quantum computer be able to break current encryption? There is no confirmed, agreed-upon date. IBM’s own public materials and independent analysts (including IDC) describe this as a long-term, uncertain transition rather than giving a specific year, which is why “harvest now, decrypt later” risk is framed as already active regardless of the exact timeline.
Sources
IBM Research — Quantum-Safe Cryptography and Migration (research.ibm.com/topics/quantum-safe-cryptography-and-migration)
NIST — FIPS 203, 204, and 205 finalized post-quantum cryptography standards (August 13, 2024)
IBM Newsroom — “IBM Advances Secure AI, Quantum Safe Technology with IBM Guardium Data Security Center” (October 22, 2024)
The Quantum Insider — “IBM Unveils AI-Driven Cryptography Manager to Tackle Quantum Data Risks” (October 8, 2025)
The Quantum Insider — “IBM Adds Post-Quantum Security Features to New z17 and LinuxONE Systems” (July 2026, covering August 12, 2026 general availability)
Related reading on this site: IBM’s Path to Fault-Tolerant Quantum Computing (Nighthawk, Loon, and the 2029 Starling Target), IBM’s Telum II and the z17, IBM Power11 Explained, and IBM watsonx.governance and watsonx.data Explained.
Most coverage of AWS’s AI infrastructure, including our own on this site, focuses on either the custom silicon underneath it (Trainium, Inferentia, Graviton) or the general-purpose model platforms sitting on top (Bedrock and SageMaker as model-hosting services). Between those two layers sits a problem neither one solves: once a prototype AI agent works in a notebook, what actually keeps it running securely, debugged, and scaled when real users and real tool calls hit it in production? Amazon Bedrock AgentCore is AWS’s answer, and it’s infrastructure in the fullest sense — compute, identity, memory, and observability purpose-built for autonomous agents rather than for serving a model’s inference endpoint. This piece is specifically about that layer, distinct from our earlier look at Bedrock and SageMaker’s general AI developer services and from AWS’s Nitro/EFA networking stack.
At a Glance
Fact
Detail
What it is
A managed platform for deploying, securing, and operating AI agents in production, framework- and model-agnostic
General availability
October 2025 (per AWS’s official “now generally available” announcement)
Supported frameworks
LangChain, OpenAI Agents SDK, Claude Agent SDK, Strands Agents SDK, or custom frameworks
Consumption-based, no upfront commitment; most components billed per vCPU-hour, per GB-hour, or per 1,000 API calls/tokens
2026 feature rollout
Policy GA (March 2026), AgentCore Harness GA (June 2026), AgentCore Payments GA (August 2026)
Short Verdict
AgentCore is AWS correctly identifying that the hard part of production AI agents isn’t building one — it’s securing tool access, managing memory and identity across sessions, and debugging an agent’s actual decision path when it misbehaves. AWS has built a genuinely modular, pay-as-you-go set of managed services for exactly that, and it works with agents built on other vendors’ frameworks and models, not just Bedrock’s own. The trade-off is that this is a fast-moving, feature-by-feature rollout (several core pieces only reached general availability in the months since its October 2025 launch), and the vendor-cited performance numbers in AWS’s own marketing haven’t been independently verified.
The Problem AgentCore Is Built to Solve
AWS’s own framing of AgentCore is direct: building an agent is fast, but connecting it securely to internal systems, debugging unexpected behavior, and scaling it reliably are what actually slow teams down. That’s a different problem from hosting a model for inference, which is what Bedrock’s foundation-model catalog and SageMaker’s training/hosting tools are built for. An agent isn’t just a model call — it’s a model plus a loop of tool calls, memory lookups, and multi-step decisions, each of which needs its own security boundary, its own debugging trail, and its own way of scaling independently of the underlying model.
What’s Actually Inside AgentCore
Runtime — executes agent code in isolated microVMs, billed per vCPU-hour and per GB-hour of memory consumed, with support for long-running sessions beyond what a typical serverless function allows.
Gateway — handles authentication and access control for an agent’s connections to MCP (Model Context Protocol) servers, internal APIs, knowledge bases, and Lambda functions, so tool access is governed centrally rather than hardcoded per agent.
Identity — issues OAuth tokens and API keys an agent uses to act on a user’s behalf; AWS does not charge separately for Identity when it’s used through Runtime or Gateway.
Memory — split into short-term memory (billed per GB ingested, retrieved, and stored) and long-term memory (billed per 1,000 records stored and retrieved monthly), letting an agent recall context across sessions rather than starting fresh every call.
Observability — surfaces the actual steps an agent took, which tools it called, and where its reasoning went off track, billed through Amazon CloudWatch rather than a separate AgentCore charge.
Evaluations — lets teams test agent behavior against real traffic rather than only synthetic test cases.
Browser and Code Interpreter — sandboxed environments that let an agent browse the web or execute code safely, billed on the same per-vCPU-hour/per-GB-hour model as Runtime.
Policy — enforces access policies verified through automated reasoning, the same formal-verification technology AWS already uses behind IAM and S3 access controls; it reached general availability in March 2026.
Pricing, Component by Component
Component
Billing Unit
Rate (per AWS’s published pricing page)
Runtime (microVMs, on-demand)
Per vCPU-hour / per GB-hour
$0.0895 per vCPU-hour; $0.00945 per GB-hour
Browser / Code Interpreter
Per vCPU-hour / per GB-hour
$0.0895 per vCPU-hour; $0.00945 per GB-hour (same rate as Runtime)
Gateway
Per 1,000 API invocations
$0.005 per 1,000 invocations; Search API $0.025 per 1,000; tool indexing $0.02 per 100 tools/month
Identity
Per 1,000 OAuth tokens/API keys
$0.010 per 1,000; free when used through Runtime or Gateway
Memory (short-term)
Per GB ingested/retrieved/stored
$1.00 per GB ingested; $0.20 per GB retrieved; $0.10 per GB-month stored
Memory (long-term)
Per 1,000 records/month
$0.75 per 1,000 records (built-in); $0.25 per 1,000 (self-managed); $0.50 per 1,000 retrievals
New AWS customers get up to $200 in free-tier credits, and AWS notes that Identity usage carries no separate charge when accessed through Runtime or Gateway. As with any consumption-based service, actual monthly cost depends heavily on session length, memory volume, and how many tool calls an agent makes — there’s no flat per-agent price.
A Fast-Moving Rollout, Not a Single Launch
AgentCore reached general availability in October 2025, but several of its components have continued rolling out piece by piece since then: Policy reached general availability in March 2026, the AgentCore Harness (a packaging/runtime wrapper) in June 2026, and AgentCore Payments — letting agents initiate and manage payments on a user’s behalf — in August 2026. That cadence is worth flagging for anyone evaluating the platform today: a feature absent six months ago may now be GA, and the reverse is also possible for newer previews that haven’t yet reached general availability.
Vendor-Cited Results (Treat as Marketing, Not Independent Benchmarks)
AWS’s own AgentCore marketing cites a Signal65 comparison claiming 75% less time spent on infrastructure and integrations versus custom development, 5.2x faster deployment, and 2.1x faster end-to-end agent development versus building the equivalent infrastructure in-house. It also names specific customers: Cox Automotive scaling from zero to 17 production agents in under a year, Druva resolving 68% of support issues without human intervention, and Thomson Reuters reporting 70% automation in platform engineering. These are AWS-published, customer-attributed figures rather than independently audited benchmarks, and none of the underlying methodology is public, so they should be read as directional case studies rather than guaranteed outcomes for any other team’s workload.
AgentCore vs. Building It Yourself
Dimension
Self-Built Agent Infrastructure
Bedrock AgentCore
Identity & tool access
Custom auth code per integration, or a shared internal gateway you build and maintain
Managed Gateway and Identity services with centralized policy enforcement
Memory across sessions
Usually a self-managed vector store or database, wired in manually
Built-in short-term and long-term Memory services, billed by usage
Debugging agent behavior
Custom logging, often incomplete for multi-step tool-calling traces
Purpose-built Observability showing the agent’s actual step-by-step trace
Framework lock-in
Depends entirely on what you build
Framework-agnostic: LangChain, OpenAI Agents SDK, Claude Agent SDK, Strands, or custom
Cost model
Fixed infrastructure cost regardless of usage
Pay-per-use across every component, no minimum commitment
Trade-offs
Pros
Cons
Framework- and model-agnostic by design — works with Claude, OpenAI, or custom agent frameworks, not only Bedrock-hosted models
A relatively young platform; several core components reached GA only within the last year, so maturity varies by component
Granular, consumption-based pricing avoids paying for idle agent infrastructure
Granular pricing also means cost is harder to forecast than a flat per-seat or per-agent price
Security and policy enforcement (Gateway, Identity, Policy) centralizes what’s otherwise built ad hoc per team
Vendor-cited performance and ROI figures are AWS’s own marketing, not independently verified
Who It’s Relevant For
Teams that have already validated an AI agent prototype and are hitting the production wall — needing secure tool access, persistent memory, and real debugging visibility — and that want to avoid building and maintaining that infrastructure themselves. It’s especially relevant for teams already on AWS and working with multiple agent frameworks rather than a single vendor’s SDK.
Who Should Look Elsewhere
Teams still in early prototyping, where the overhead of learning a multi-component managed platform outweighs the benefit, and teams fully committed to a different cloud’s native agent stack, where switching costs would exceed what AgentCore saves. Simple, single-tool agents with no multi-session memory requirement may also not need most of what AgentCore offers.
Bottom Line
AgentCore fills a real, specific gap in AWS’s AI stack: not model hosting, not custom silicon, but the operational layer that keeps an agent secure, debuggable, and scalable once it leaves the prototype stage. Its framework-agnostic design and granular pricing are genuine differentiators, and its October 2025 general availability plus steady 2026 feature rollout (Policy, Harness, Payments) show AWS treating this as a priority rather than a one-off launch. The honest caveat is that it’s still maturing component by component, and its headline ROI figures come from AWS’s own case studies rather than independent benchmarking.
FAQ
Does AgentCore require using Bedrock’s foundation models? No. AWS markets it as model-agnostic, supporting agents built on Claude, OpenAI models, or others, through frameworks like LangChain, the OpenAI Agents SDK, the Claude Agent SDK, or Strands.
When did AgentCore become generally available? AWS’s official announcement states Amazon Bedrock AgentCore became generally available in October 2025.
How is AgentCore priced? Consumption-based with no upfront commitment, billed component by component — for example, Runtime and sandboxed execution (Browser, Code Interpreter) by vCPU-hour and GB-hour, Gateway by API invocation, Identity by token/key issued, and Memory by data ingested, retrieved, and stored.
What’s the difference between AgentCore and the earlier “Bedrock and SageMaker” AI developer tools? Bedrock’s foundation-model catalog and SageMaker cover model access, fine-tuning, and hosting. AgentCore is a separate, newer layer specifically for operating autonomous agents in production — identity, memory, tool-access security, and observability for the agent loop itself, not for serving a model endpoint.
Sources
AWS — “Amazon Bedrock AgentCore is now generally available” (aws.amazon.com/about-aws/whats-new/2025/10/amazon-bedrock-agentcore-available)
AWS — “Policy in Amazon Bedrock AgentCore is now generally available” (March 2026)
AWS — “AgentCore Harness is now generally available” (June 2026)
AWS — “AgentCore payments is now generally available” (August 2026)
Related reading on this site: Beyond the Chips: What Amazon Bedrock and SageMaker Actually Offer AWS’s AI Developers, Inside AWS’s AI Networking Stack (Nitro System and EFA), and AWS’s Custom Silicon Economics (Trainium vs. Nvidia GPUs).
Nvidia’s AI data center story usually gets told through GPUs: Blackwell’s transistor count, GB300 rack power draw, or the NVLink Fusion/UALink interconnect fight over how chips talk to each other inside a rack. Underneath all of that sits a less-discussed layer that determines whether a data center full of GPUs behaves like one coordinated supercomputer or like a pile of expensive, underused silicon: the network connecting racks to each other, and the processors that keep that network’s overhead off the CPU. That layer is Nvidia’s Spectrum-X Ethernet platform and its BlueField data processing units (DPUs). This piece stays specifically there, distinct from Blackwell’s GPU architecture and the NVLink Fusion/UALink scale-up interconnect fight covered elsewhere on this site.
At a Glance
Component
What It Is
Key Fact (Nvidia-stated)
Spectrum-X
Nvidia’s Ethernet networking platform purpose-built for AI data centers
Switches, SuperNICs/DPUs, and software “tuned and validated” together; Nvidia claims 1.6x the network performance of off-the-shelf Ethernet
BlueField-3 DPU
Current mainstream data processing unit, paired with Spectrum-X as a “SuperNIC”
Extension of Spectrum-X for linking multiple data centers as one “AI super-factory”
Nvidia claims 1.9x higher NCCL performance in cross-data-center scenarios
Short Verdict
Spectrum-X and BlueField are Nvidia’s answer to a problem GPUs alone can’t solve: once you’re past the handful of GPUs connected directly by NVLink inside a rack, something has to move data between racks and offload the networking, storage, and security bookkeeping that would otherwise eat into CPU and GPU time. Spectrum-X is Nvidia’s case that Ethernet — not just InfiniBand — can do that job at AI scale, provided the switches, DPUs, and software are co-designed rather than assembled from generic parts. It’s a credible, commercially shipping platform with real customers, but several of its headline performance figures are Nvidia’s own benchmarks without disclosed methodology, and it’s explicitly a complement to, not a replacement for, Nvidia’s other networking options.
What a DPU Actually Offloads
Nvidia describes a DPU as “a programmable infrastructure processor” combining a general-purpose CPU, a high-speed network interface, and dedicated hardware acceleration engines, built to offload infrastructure services from the host server’s main CPU. BlueField is Nvidia’s DPU line. Per Nvidia’s own product documentation, BlueField offloads three categories of work: networking (software-defined networking, distributed routing, and overlay/underlay networking, with BlueField-3 rated at 400 Gb/s and BlueField-4 at 800 Gb/s), storage (RDMA, NVMe-over-Fabrics, and GPUDirect Storage, covering block, file, and object storage), and security (in-silicon threat detection, workload isolation, and runtime protection, including out-of-band monitoring that Nvidia says continues even if the host server itself is compromised).
Concretely, BlueField-3 packs 16 general-purpose Arm Cortex-A78 cores and roughly 22 billion transistors, first disclosed by Nvidia in 2022 with broader availability through 2023–2024. BlueField-4, the newer generation Nvidia now positions as its “gigascale AI factory” platform, roughly triples that to about 64 billion transistors and doubles network throughput to 800 Gb/s. The practical effect in both cases is the same: instead of the host CPU spending cycles on packet processing, encryption, and storage protocol handling, that work happens on the DPU, freeing the CPU (and, more importantly in a GPU-dense server, the time otherwise spent waiting on the CPU) for the workload itself.
What Spectrum-X Actually Is
Spectrum-X is not a single product but a platform: a specific combination of switches, network adapters, and software that Nvidia sells and supports as a unit rather than letting customers assemble from off-the-shelf parts. Per Nvidia’s current product page, the switch side spans the SN5000, SN5610, and SN6000 series, with the newest SN6600 offering 128 ports of 800G OSFP and the SN6800 packing 512 such ports into a 5U chassis, built on Nvidia’s Spectrum-6 ASIC rated at 102.4 Tb/s per chip using 200G SerDes — double the per-lane bandwidth of the prior generation. On the server side, Spectrum-X pairs with “SuperNICs”: BlueField-3 for Hopper-generation GPU systems, ConnectX-8 (800 Gb/s via dual 400G links over PCIe Gen 6) for Blackwell-generation systems, and ConnectX-9 (1,600 Gb/s per GPU via four 200G SerDes lanes) for the newer Vera Rubin NVL72 platform. Software glue includes DSX Air for pre-deployment network simulation, Minerva for telemetry and AIOps aimed at maximizing what Nvidia calls “AI factory yield,” and an open network operating system built on SONiC and Cumulus Linux rather than a fully closed stack.
Nvidia’s central performance claim, stated on its own Spectrum-X product page, is that the platform accelerates AI network performance “by 1.6x over off-the-shelf (OTS) Ethernet.” The page links to a supporting resource but does not publish the test methodology, so this figure should be read as a vendor-stated claim, not an independently verified benchmark. The same caution applies to Spectrum-XGS’s claimed 1.9x higher NCCL (Nvidia’s GPU collective-communication library) performance in cross-data-center scenarios, and to claims around Nvidia’s silicon-photonics switch variant (5x better power efficiency and 5x longer sustained AI application runtime versus pluggable-transceiver networks) — all are Nvidia’s own published figures, not third-party benchmarks.
Spectrum-X vs. InfiniBand: Nvidia’s Own Framing
Crucially, Spectrum-X does not replace Nvidia’s InfiniBand (Quantum) networking — the two are sold side by side, and Nvidia is explicit about when it recommends each. Nvidia’s own guidance (via its Nvidia Networking perspectives/FAQ content) positions InfiniBand as the choice for dedicated AI training and inference superclusters, where the goal is a proven, maximum-performance fabric in which “every GPU must act like part of one coordinated system.” Spectrum-X is instead positioned for AI clouds and multi-tenant environments — deployments where operators want Ethernet-standard tooling, skills, and interoperability, plus the performance isolation needed when many customers share the same physical fabric. In both cases, Nvidia’s consistent message is to avoid generic, unoptimized Ethernet for AI workloads; the company’s recommended architecture layers NVLink for scale-up within a rack, InfiniBand or Spectrum-X for scale-out across a cluster, and Spectrum-XGS when an “AI factory” spans multiple buildings or data centers.
Networking Approaches Compared
Fabric
Best Suited For (per Nvidia)
Standards Basis
NVLink / NVLink Fusion
Scale-up: GPU-to-GPU inside a rack
Nvidia proprietary (with an emerging licensing path for partners)
InfiniBand (Quantum)
Dedicated, maximum-performance training superclusters
InfiniBand Trade Association standard, Nvidia-dominated supply
Spectrum-X Ethernet
AI clouds, multi-tenant GPU infrastructure, teams standardized on Ethernet
Standard Ethernet (IEEE), with Nvidia’s RoCE extensions, congestion control, and telemetry layered on top
Spectrum-XGS
Linking multiple data centers into one “AI super-factory”
Extension of Spectrum-X for metro/long-haul distances
The “AI Factory” Pitch
Spectrum-X and BlueField are also the connective tissue in Nvidia’s broader “AI factory” framing — the idea that a modern AI data center should be engineered and operated like a factory producing tokens, not a traditional enterprise data center running assorted applications. Minerva’s telemetry is explicitly pitched around factory-style yield metrics (GPU-hours, uptime, token production), and DSX Air lets operators simulate and validate a network design before it’s built, the way a factory line gets modeled before construction. BlueField also underpins Nvidia Sentry, an out-of-band security layer Nvidia says keeps monitoring AI agents and infrastructure even if the host server itself is compromised — folding security into the same DPU that already handles networking and storage offload rather than bolting it on separately.
Trade-offs
Pros
Cons
Lets operators stay on standards-based Ethernet rather than a fully proprietary fabric, easing hiring, tooling, and interoperability
Headline performance figures (1.6x, 1.9x NCCL, 5x power efficiency) are Nvidia’s own benchmarks; no public third-party validation or disclosed methodology was found
DPU offload (BlueField-3/4) frees host CPU cycles for the actual workload instead of packet, storage, and security processing
Still a largely Nvidia-controlled stack (switches, SuperNICs, and software tuned specifically for Nvidia GPUs), reducing vendor flexibility versus a fully generic multi-vendor Ethernet build
Explicitly positioned as a lower-friction complement to InfiniBand for multi-tenant AI clouds, not a forced either/or choice
Best-fit use case (multi-tenant AI clouds) differs from dedicated training superclusters, where Nvidia itself still recommends InfiniBand
Who It’s Relevant For
Cloud providers and large enterprises building or operating multi-tenant GPU infrastructure, where Ethernet skills, standards compliance, and the ability to isolate performance between tenants matter as much as raw throughput. It’s also relevant to anyone evaluating why a GPU cluster’s real-world training throughput falls short of its on-paper FLOPS — the network fabric and the CPU-offload layer are frequently where that gap lives.
Who Should Look Elsewhere
Teams running dedicated, single-tenant training superclusters where Nvidia itself points toward InfiniBand instead, and teams who want vendor-neutral networking rather than a GPU vendor’s own tuned stack — AWS’s Nitro System and Elastic Fabric Adapter (covered separately on this site) is the clearest example of a hyperscaler building a comparable but independent offload-and-fabric layer.
Bottom Line
Spectrum-X and BlueField are Nvidia’s bet that the networking layer underneath AI GPUs matters as much as the GPUs themselves — and that Ethernet, properly tuned and paired with DPU offload, can serve AI-cloud-scale deployments that don’t need (or want) a fully proprietary InfiniBand fabric. The platform is real, shipping, and used in production (Nvidia cites its own 100,000-GPU Hopper system, built for xAI, as a reference deployment). The caveat is standard for any vendor’s own performance marketing: treat the specific multiplier claims as directional until independently reproduced, and recognize that Spectrum-X is one tool in a toolbox that still includes NVLink, InfiniBand, and Spectrum-XGS, each aimed at a different scale of the same problem.
FAQ
Is Spectrum-X the same as InfiniBand? No. Spectrum-X is Nvidia’s Ethernet-based platform; InfiniBand (Quantum) is a separate fabric Nvidia sells for dedicated training superclusters. Nvidia recommends each for different deployment types rather than treating one as a strict successor to the other.
What’s the difference between BlueField-3 and BlueField-4? BlueField-3 is a 400 Gb/s DPU with 16 Arm Cortex-A78 cores and about 22 billion transistors, generally available since 2023–2024. BlueField-4 doubles throughput to 800 Gb/s and roughly triples transistor count to about 64 billion, aimed at larger-scale “AI factory” deployments.
Does Spectrum-X only work with Nvidia GPUs? Spectrum-X is marketed and tuned specifically around Nvidia’s GPU platforms (Hopper, Blackwell, Vera Rubin) and their corresponding SuperNICs, though the underlying switches speak standard Ethernet and can interoperate with non-Nvidia Ethernet equipment.
Are Nvidia’s Spectrum-X performance claims independently verified? Not as far as this research could confirm. The 1.6x off-the-shelf-Ethernet figure and Spectrum-XGS’s 1.9x NCCL figure appear on Nvidia’s own product pages without a published third-party benchmark or disclosed test methodology, so they should be treated as vendor claims.
Nvidia Networking FAQ/perspectives content on InfiniBand vs. Spectrum-X selection (perspectives.nvidia.com)
Related reading on this site: Nvidia’s Data Center AI Empire (Blackwell GPUs and CUDA), NVLink Fusion and UALink Explained, Nvidia’s Vera Rubin Platform Explained, and Inside AWS’s AI Networking Stack (Nitro System and EFA).
Most coverage of Google’s AI infrastructure — including our own, on this site — gravitates toward the hardware: TPU chip specs, the Jupiter network’s optical circuit switches, the Axion CPU. That hardware is necessary but not sufficient. A 9,216-chip superpod is just an inert pile of silicon until something tells it which part of a model runs where, what happens when a chip fails mid-training-run, and how a single Python program can coordinate work across thousands of accelerators spanning multiple physical pods. That “something” is Pathways, Google’s orchestration system, together with JAX and a scaling technique called Multislice — the software layer that actually turns racks of TPUs into one coherent training system. This piece stays specifically at that layer.
At a Glance
Component
What It Is
Problem It Solves
JAX
Google’s NumPy-style array computation library with composable function transforms, compiled via XLA/OpenXLA
Lets researchers write array/tensor math that compiles to efficient code for CPUs, GPUs, and TPUs
Pathways
A distributed runtime and resource-management system, described in a 2022 paper (Barham et al.) and now generally available on Google Cloud
Lets one client program (“single-controller”) orchestrate and schedule work across thousands of accelerators, instead of requiring every process to run an identical copy of the program (“multi-controller”/SPMD)
Multislice
A Google Cloud technology (announced August 2023) for scaling a single training run across more TPU chips than one physical slice/pod contains
Removes the hard ceiling on training-run size that a single ICI-connected slice imposes, by having the XLA compiler generate communication over the slower data-center network (DCN) between slices
Short Verdict
Pathways is the more fundamental shift of the two: it replaces the traditional “every process runs the same program in lockstep” (SPMD) model that JAX and TensorFlow traditionally relied on with a single-controller model, where one Python client describes the whole computation as a graph and a distributed runtime handles placement, scheduling, and failure recovery. Multislice is the more immediately practical payoff for anyone training at scale on Google Cloud: it’s the specific mechanism that lets a training run span more chips than fit in one physical TPU slice, by having the compiler automatically generate network traffic between slices rather than requiring developers to hand-write cross-slice communication code. Together, they’re why Google can plausibly offer TPU clusters reaching “hundreds of thousands” of chips for a single training job, and why a hardware failure partway through a massive run doesn’t necessarily mean restarting from scratch.
The Core Idea: Single-Controller vs. Multi-Controller
To understand why Pathways exists, it helps to understand the model it replaces. In the traditional SPMD (single program, multiple data) approach that JAX and TensorFlow have long used, every process in a distributed job runs its own copy of the same Python program and owns its own accelerators for the entire run. Every accelerator executes the same instructions in lockstep and coordinates through collective operations like AllReduce — no single process has visibility into, or control over, what’s happening across the whole job. That works well when a job really is one uniform program running the same computation everywhere. It works less well for more irregular workloads: a reinforcement-learning loop with a separate sampler, reward model, and trainer; a mixture-of-experts model that activates different “expert” sub-networks for different inputs; or elastic training that needs to add or remove hosts mid-run without restarting everything.
Pathways takes a different approach: a single-controller model. One client program describes the entire computation — its component operations, which devices should run them, and how data flows between them — and a distributed runtime underneath handles the actual placement, scheduling, and data movement. Google’s own description of the architecture breaks it into distinct pieces: a resource manager (the control plane, which allocates accelerators, monitors worker health, and handles scheduling and error reporting), a client that implements an Interim Framework Runtime (IFRT) interface and coordinates with the resource manager, workers that run on the TPU VMs and actually execute compiled programs, and a sidecar server co-located with each worker to run user Python code physically close to the accelerators and cut data-transfer latency. Google’s original 2022 Pathways paper reported close to 100% accelerator utilization on standard SPMD computations across 2,048 TPUs — meaning the new architecture doesn’t sacrifice throughput on the workloads SPMD already handled well, while opening up computation patterns SPMD couldn’t express cleanly, like asymmetric pipeline parallelism.
The practical benefits Google highlights for this architecture go beyond raw flexibility. Because the client targets virtual devices rather than specific physical chips, compilation can begin before physical hardware is even provisioned. Because the resource manager, not a fixed process-to-device mapping, tracks what’s healthy, a lost host doesn’t necessarily kill the whole job — the resource manager can remap work onto healthy chips and keep the run going, which is the architectural basis for what Google calls elastic training. And because a central scheduler sees the entire job’s operations, it can give every program a consistent execution order, avoiding the kind of deadlocks or stalls that come from independently-scheduled, conflicting collective operations across processes that can’t see each other.
Multislice: Scaling Past a Single Pod
Multislice, which Google announced at Google Cloud Next in August 2023, solves a more concrete, immediate problem: a single TPU slice — the group of chips connected directly by the fast inter-chip interconnect (ICI) — has a hard size ceiling. Before Multislice existed, a training run was capped at whatever the largest available ICI-connected slice offered. Multislice removes that ceiling by letting one training run span multiple slices, either within a single pod or across physically separate pods, communicating over Google’s ordinary data-center network (DCN) rather than ICI for the inter-slice portion of the job. In a typical data-parallel setup, activations stay on the fast ICI network exactly as they would in single-slice training, while gradient synchronization crosses the slower DCN between slices — and because DCN bandwidth per chip is the scarcer resource at that point, a larger ICI domain (more chips tightly coupled within a single slice) reduces how much DCN bandwidth is needed per unit of useful computation, which is why slice size and interconnect design both matter to how far Multislice scales efficiently.
Critically, developers don’t hand-write the cross-slice communication. Google’s XLA compiler generates the DCN-crossing collective operations automatically and decomposes them into hierarchical steps, overlapping that communication with computation where possible. The configuration surface for this is a mesh that separates parallelism within a slice (ICI) from parallelism across slices (DCN):
# Simplified from Google's Multislice documentation: separate
# parallelism strategies for the fast intra-slice (ICI) network
# and the slower inter-slice (DCN) network.
dcn_parallelism = [
config.dcn_data_parallelism,
config.dcn_fsdp_parallelism,
config.dcn_tensor_parallelism,
]
ici_parallelism = [
config.ici_data_parallelism,
config.ici_fsdp_parallelism,
config.ici_tensor_parallelism,
]
if multi_slice_env:
mesh = mesh_utils.create_hybrid_device_mesh(ici_parallelism, dcn_parallelism)
else:
mesh = mesh_utils.create_device_mesh(ici_parallelism)
Google’s own published figures from the Multislice announcement illustrate the payoff: compared to a baseline system with small 8-chip ICI domains, TPU v5e’s 256-chip ICI domain enables up to 2x higher peak FLOPs without hitting communication bottlenecks, and TPU v4’s larger 3,072-chip ICI domain enables up to 24x higher peak FLOPs under the same comparison — both figures from Google’s internal benchmarking at the time of the 2023 announcement, and both specifically about how much larger an effective training cluster Multislice’s design permits versus smaller-ICI-domain alternatives, not a claim about any particular model’s end-to-end training speed.
How This Shows Up in Reliability, Not Just Scale
It’s tempting to treat Pathways and Multislice purely as scaling technology, but Google’s own materials on cluster reliability for trillion-parameter models describe a three-layer resilience model where the orchestration software is explicitly one of the layers, not an afterthought bolted onto the hardware. At the infrastructure layer, superpods provide the physically available, connected capacity (with Google modeling topological availability — for example, roughly 130 of 144 cubes available in a given superpod for 95% of a month — to size training jobs against realistic, not ideal, hardware availability). At the framework layer, Google names JAX and Pathways specifically as the pieces that reconfigure around a failed node or hot-swap it out to keep a training job progressing, rather than forcing a full restart. At the application layer, auto-checkpointing and multi-tier checkpointing preserve training state to minimize how much progress is lost when something does fail. That middle layer — JAX and Pathways actively managing failure, not just scale — is the direct, practical reason the single-controller architecture matters beyond raw throughput numbers: a resource manager that already tracks every chip’s health is the same piece of software that can remap a job around a dead one.
Trade-Offs
Pros: single-controller orchestration genuinely expands what parallelism patterns are practical to express (asymmetric pipelines, RL loops with heterogeneous component programs) without sacrificing throughput on standard SPMD workloads; Multislice removes a hard scaling ceiling without requiring developers to write custom cross-slice networking code; the same resource-management layer that enables scale also directly enables fault tolerance.
Cons: this entire stack is Google Cloud– and JAX/XLA-specific — there’s no portable equivalent for teams on other clouds or committed to PyTorch-first workflows (PyTorch/XLA support on TPUs exists but is less natively integrated than JAX’s); Multislice’s DCN-crossing communication is inherently slower than intra-slice ICI traffic, so efficiency still depends on having a sufficiently large ICI domain within each slice to amortize that cost, meaning the technique has real, not infinite, scaling limits; and Google’s own published performance multiples (2x, 24x) are internal benchmarks from the 2023 announcement, not independently reproduced figures.
Who This Matters To
This is most directly relevant to ML infrastructure engineers and researchers already working in JAX on Google Cloud TPUs, who need to understand why their training job is configured around separate ICI and DCN parallelism dimensions, or why Pathways enables elastic training rather than requiring a full restart after a lost host. It’s also useful context for anyone evaluating Google’s AI infrastructure claims against Nvidia’s or AWS’s: Google’s single-controller/Pathways approach and Nvidia’s NVLink-based “one giant GPU” abstraction (see our coverage of Ironwood’s pod architecture) solve related but distinct problems — one is about software-level job orchestration and fault tolerance, the other is primarily about hardware-level interconnect topology.
Who Should Look Elsewhere
Readers looking for TPU chip specifications, FLOPS figures, or pricing should see our existing coverage of Google’s TPU chips and Ironwood superpod architecture, which this piece deliberately doesn’t repeat. Readers looking for the data-center networking layer that connects whole superpods to each other — Jupiter, Google’s optical-circuit-switching fabric — should see our dedicated piece on that topic; Pathways and Multislice sit a layer above it, at the job-orchestration and compiler level, not the physical network fabric itself. And teams not using JAX or not training on Google Cloud TPUs will find little of this directly actionable, since both Pathways and Multislice are specific to that stack.
Bottom Line
The chips and the network get the headlines, but Pathways and Multislice are the layer that actually decides whether a pile of TPUs behaves like one coherent training system or a loose collection of separately-managed machines. Pathways’ single-controller model is the more architecturally significant piece — it’s what lets one program orchestrate thousands of accelerators and recover from failures without a full restart — while Multislice is the concrete mechanism that turns that architecture into “your training run isn’t capped at the size of one physical pod.” Neither is portable outside Google’s JAX/XLA/TPU stack, which is the real trade-off for teams weighing Google Cloud against Nvidia- or Trainium-based alternatives: real orchestration sophistication, in exchange for real platform lock-in.
FAQ
What is Pathways, in one sentence? It’s Google’s distributed runtime and resource-management system that lets a single client program orchestrate computation across thousands of TPU accelerators using a “single-controller” model, instead of requiring every process to run an identical copy of the program.
How is Pathways different from Multislice? Pathways is the underlying orchestration architecture (single-controller job execution and fault recovery). Multislice is a more specific Google Cloud technology, built on top of that general approach, that lets one training run span multiple physical TPU slices by routing inter-slice communication over the data-center network.
Does Pathways replace JAX? No — Pathways runs JAX (and OpenXLA-compiled) programs; it’s the distributed execution layer underneath, not a replacement for the array-computation library researchers actually write code in.
Can Multislice training span TPUs in different physical locations? Google’s Multislice technology connects slices over the data-center network, and Google’s separate materials on scaling to the largest clusters describe connecting whole superpods — and, at the largest scale, multiple data centers — via its broader data-center networking layer; the specific latency and bandwidth trade-offs of doing so depend on the physical distance and network path involved, which Google does not fully break out in public documentation.
Is this specific to Google Cloud, or does it work elsewhere? It’s specific to Google Cloud TPUs. Pathways and Multislice are Google-built systems tied to TPU hardware and the JAX/XLA software stack; there’s no equivalent product that runs this exact architecture on other clouds or accelerator types.
Mobile scanning apps turned “scan a document” from a trip to a flatbed scanner into a 10-second phone camera job — crop, enhance contrast, and spit out a searchable PDF. Adobe Scan, Microsoft Lens, and Genius Scan are three of the most installed options, but they take very different approaches to what’s free and what isn’t. Here’s what each one’s own official pages actually say.
At a Glance
Spec
Adobe Scan
Microsoft Lens
Genius Scan
Base app cost
Free to download
Free, no in-app purchases listed
Free (“Basic” tier, unlimited use)
Paid tier
Premium features via Adobe Acrobat subscriptions
None — entirely free
Ultra: $39.99/year
OCR / searchable PDF
Included free; advanced recognition on Premium
Included free (text recognition built in)
Ultra only
Best for
Users already in the Adobe/Acrobat ecosystem
Anyone who wants a fully free scanner with no upsell
Users who want cloud backup/sync and don’t mind a modest annual fee
Short Verdict
Microsoft Lens is the simplest story: it’s free, full stop, with no subscription tier or in-app purchase at all according to its own App Store listing. Adobe Scan is also free to download and use for basic scanning, but its more advanced capabilities (combining files, converting formats, advanced editing) are gated behind an Adobe Acrobat subscription rather than a standalone Scan-only plan, so the real cost depends on which Acrobat tier you need. Genius Scan sits in between: its free Basic tier is genuinely unlimited for straightforward scanning, and its $39.99/year Ultra tier is a modest, clearly priced step up for OCR, cloud backup, and device sync — no ambiguity about what you’re paying for.
What Each App Is
Adobe Scan is Adobe’s mobile scanning app, built to turn a phone photo into a cleaned-up PDF and feed it into the broader Acrobat/Reader ecosystem. The app itself is free to download, and Adobe’s own help pages describe it as “completely free,” with additional capabilities — combining files, converting documents to other formats, password-protecting PDFs, and advanced editing across devices — coming from an Adobe Acrobat Pro (or similar) subscription rather than a Scan-specific upgrade.
Microsoft Lens (formerly Office Lens) is Microsoft’s free scanning app for turning whiteboards, documents, business cards, and photos into cropped, enhanced images or PDFs, with built-in text recognition and direct export to OneNote, Word, PowerPoint, or OneDrive. Its official App Store listing shows no in-app purchases or subscription tiers of any kind.
Genius Scan, from The Grizzly Labs, is a dedicated document-scanning app with automatic edge detection, perspective correction, and PDF creation, structured around three clearly named, clearly priced tiers on its own official pricing page: a free Basic tier, a paid Ultra tier, and a per-license Teams tier for organizations.
Pricing Breakdown
Plan
Price
What you get
Adobe Scan (app)
Free
Fast, unlimited scanning; automatic cropping and enhancement; basic PDF creation
Adobe Acrobat Standard
$14.99/mo (annual plan)
Core PDF editing/conversion tools that extend what Scan can do with a captured document
Adobe Acrobat Pro
$19.99/mo annual, or $29.99/mo monthly
Combine files, convert formats, password-protect PDFs, advanced editing across devices
Adobe Acrobat Studio
$24.99/mo annual, or $34.99/mo monthly
Adobe’s top individual tier, adding further AI and content tools on top of Pro
Microsoft Lens
Free
Document, whiteboard, and business-card scanning; built-in OCR; export to OneNote/Word/PowerPoint/OneDrive — no paid tier exists
Genius Scan Basic
Free
Fast, high-resolution scanning; unlimited use; full privacy (no account required)
Genius Scan Ultra
$39.99/year
Adds OCR, export to major cloud providers, enhanced security/organization, unlimited cloud backups, device sync, and web access
Genius Scan for Teams
$20–$40/license/year, with volume discounts
Everything in Ultra, plus centralized license management and enforced settings
One thing worth flagging directly: Adobe Scan’s own App Store listing also shows a confusing set of separate in-app purchase line items (several different “Adobe Scan Plus” and “Adobe Scan Premium” prices ranging from roughly $4 to $70, without clearly stating which billing period each covers), which didn’t match the clean, documented tiers on Adobe’s main Acrobat pricing page. Because that App Store listing conflicts with itself, we’re not treating those individual figures as reliable and have reported only the Acrobat subscription tiers that Adobe’s own pricing page documents clearly — if you’re specifically comparing an in-app “Adobe Scan Premium” purchase rather than a full Acrobat plan, check the current price inside the app before paying, since we could not get a consistent number for it from Adobe’s own sources.
Pros and Cons
Adobe Scan
Pros: free core scanning with no limits; output integrates directly with Acrobat/Reader and the wider Adobe ecosystem; upgrade path to full PDF editing if you already need Acrobat.
Cons: the pricing story for “premium” scanning features is genuinely confusing — Adobe’s own App Store listing shows inconsistent in-app purchase prices, and real added value mostly comes from a separate Acrobat subscription rather than a simple Scan upgrade.
Microsoft Lens
Pros: completely free with no upsell at all; tight integration with OneNote, Word, PowerPoint, and OneDrive for anyone already in the Microsoft 365 ecosystem; includes OCR at no cost.
Cons: no cloud backup/sync service of its own beyond OneDrive; fewer dedicated document-management features (tagging, organization) than Genius Scan’s paid tier.
Genius Scan
Pros: the clearest, most consistent pricing of the three — a free Basic tier and one named Ultra tier at $39.99/year with no ambiguity; dedicated Teams tier for organizations needing centralized license management.
Cons: OCR and cloud backup are both locked behind the paid Ultra tier, unlike Microsoft Lens, which includes OCR for free; no ecosystem integration as deep as Adobe’s or Microsoft’s.
Who It’s a Good Fit For
Choose Adobe Scan if you already use or plan to use Acrobat for PDF editing, and want scanning to feed directly into that workflow.
Choose Microsoft Lens if you want a fully free scanner with built-in OCR and you’re already working inside Microsoft 365 (OneNote, Word, OneDrive).
Choose Genius Scan if you want a dedicated, privacy-focused scanner with simple, predictable annual pricing for OCR and cloud backup.
Who Should Look Elsewhere
Anyone who wants scanning folded into a broader backup strategy — not just document capture — should look at a dedicated backup tool instead; see our Backblaze vs Acronis vs IDrive comparison for that separate need. And if the real goal is organizing scanned documents into a searchable personal archive with backlinks and tags rather than just capturing them, a personal knowledge management tool may serve better than any dedicated scanner app alone.
Bottom Line
If cost certainty matters most, Microsoft Lens is the easy, zero-risk pick — it’s free with no in-app purchases to navigate. Genius Scan is the next-clearest option: a free tier that’s genuinely usable, and one named $39.99/year upgrade if you want OCR and backup. Adobe Scan is worth choosing specifically for its Acrobat integration, but go in expecting the “premium scanning” pricing story to be murkier than either competitor’s — the real upgrade is an Acrobat subscription, not a simple Scan-only purchase.
FAQ
Is Adobe Scan really free?
Yes, to download and use for basic scanning — Adobe’s own pages state the app is “completely free to download.” More advanced PDF capabilities (combining files, converting formats, advanced editing) require an Adobe Acrobat subscription, which is priced separately from the Scan app itself.
Does Microsoft Lens have any hidden costs or subscriptions?
No. Its official App Store listing shows it as Free with no in-app purchases or subscription tiers of any kind — it’s one of the few mobile scanning apps with no paid upgrade path at all.
What exactly does Genius Scan Ultra add over the free Basic tier?
Per Genius Scan’s own pricing page, Ultra ($39.99/year) adds OCR text recognition, export to major cloud storage providers, enhanced security and document organization, unlimited cloud backups, cross-device sync, and web access — all absent from the free Basic tier.
Why doesn’t this article give one single “Adobe Scan Premium” price?
Because Adobe’s own sources don’t agree on one. Its App Store listing shows multiple differently priced “Adobe Scan Plus” and “Adobe Scan Premium” in-app purchase options without clearly stating each one’s billing period, while Adobe’s main pricing page documents only full Acrobat subscription tiers. Rather than guess which App Store figure is current, we’ve reported the clearly documented Acrobat tiers and flagged the in-app listing as inconsistent.
Ask an AI coding assistant for a Python snippet, and there’s a real, measured chance it will tell you to pip install a package that doesn’t exist. That’s not a hypothetical: the peer-reviewed USENIX Security 2025 study that first measured this at scale found that 19.7% of over 2.2 million AI-generated code samples recommended at least one non-existent package, and attackers have already started registering those exact hallucinated names with malicious payloads inside them, waiting for someone to copy-paste the AI’s suggestion. Security researchers call this “slopsquatting” — a term coined by Seth Larson, developer-in-residence at the Python Software Foundation — and in 2026 it’s one of the more concrete, quantifiable risks specific to AI coding assistants, distinct from the general “review AI code carefully” advice that applies to everything else an LLM writes.
At a Glance
Fact
Detail
What it is
An attacker registers a package name that LLMs are observed to hallucinate (invent) when generating code, so that developers who copy-paste AI-suggested install commands pull real, attacker-controlled malware
Term coined by
Seth Larson, developer-in-residence at the Python Software Foundation, by analogy with “typosquatting”
Original measured rate (2024/2025)
19.7% of 2.23 million AI-generated code samples across 16 models contained at least one hallucinated package (Spracklen et al., USENIX Security 2025)
2026 frontier-model rate
3.6%–5.0% of package mentions and 2.2%–3.4% of generations hallucinated across five 2026 frontier models, per an independent replication study
Real-world exploitation observed
At least 23 AI-hallucinated package names were found to have previously hosted actual malware before registries removed them; researchers observed roughly 1% of hallucinated names get registered by someone within six months of exposure
Primary defenses
Package-existence verification before install, committed and hash-verified lockfiles, SCA/allowlist tooling, human review of AI-suggested dependencies
What Slopsquatting Actually Is
Slopsquatting is a supply-chain attack that depends entirely on a quirk of how LLMs generate code: when asked to solve a problem, a model will sometimes invent a plausible-sounding package name that doesn’t exist — the kind of name a real package in that ecosystem might have — because the model is predicting statistically likely tokens, not looking anything up. If a developer (or an autonomous coding agent) trusts that suggestion and runs pip install or npm install on it, nothing happens — unless an attacker has already registered that exact name on PyPI or npm with malicious code inside it. At that point, the “nothing exists here” gap an LLM hallucinated into existence becomes a real, exploitable foothold. This is distinct from typosquatting (registering a misspelled variant of a real package name) because the attacker isn’t guessing at human typos — they’re exploiting a documented, measurable pattern in how specific LLMs fail, often by generating large volumes of code with those models first to find out exactly which fake names they tend to invent.
What the Research Actually Found
The foundational study here is Spracklen et al.’s “We Have a Package for You! A Comprehensive Analysis of Package Hallucinations by Code Generating LLMs,” presented at USENIX Security 2025. The researchers generated 2.23 million code samples in Python and JavaScript across 16 different models and found that 440,445 of them (19.7%) recommended at least one hallucinated package, comprising 205,474 unique fabricated names. The breakdown matters for anyone picking a model: commercial models averaged a 5.2% hallucination rate versus 21.7% for open-source models — open-source models hallucinated roughly four times as often — and the best-performing individual model, GPT-4 Turbo, hallucinated in 3.59% of samples, while the best open-source model tested, DeepSeek at 1.3B parameters, still hallucinated 13.63% of the time. Python (15.8%) hallucinated less than JavaScript (21.3%) on average, though a model’s tendency to hallucinate correlated across both languages.
Two findings from that study are specifically what makes slopsquatting practical as an attack rather than just an annoyance. First, persistence: when the researchers reran the same prompt 10 times against the same model, 43% of hallucinated package names reappeared in all 10 runs, and 58% reappeared more than once — meaning a meaningful share of hallucinations aren’t one-off flukes, they’re reliable, repeatable outputs an attacker can specifically target by querying the same models themselves. Second, specificity: 81% of distinct hallucinated names were produced by only one model, meaning each model has its own, largely distinct set of fabricated names — which is exactly the kind of fingerprint that lets an attacker generate a target list by simply querying popular coding models at scale and registering whatever they consistently invent.
A 2026 independent replication, run against five current frontier models across 199,840 Python and JavaScript generations, found the rate has narrowed but not disappeared: 3.6%–5.0% of package mentions and 2.2%–3.4% of full generations were hallucinated, which the paper’s authors describe as “the 2026 frontier sits at the level of 2024’s commercial models” — in other words, today’s best models have converged toward where 2024’s best commercial models already were, rather than solving the problem outright, and the gap between open-weight and closed models that the original study found has also largely disappeared. The same 2026 study used an accidental six-month public exposure of its own hallucinated-name list as a natural experiment and found that about 1% of hallucinated names were registered by someone within that window — at the same rate whether or not the list had been published, suggesting opportunistic registration happens regardless of visibility. Most concerning: the researchers found at least 23 of the hallucinated names they tested had previously hosted actual malware that package registries had already removed, and one hallucinated name was registered with malware during the study’s own run window.
How This Differs From General “AI Code Security” Advice
Broader frameworks like OWASP’s AI Security Verification Standard treat AI-generated dependencies as one item among many requiring human review and automated scanning — useful, but not specific to this failure mode. Slopsquatting is narrower and more mechanical: it doesn’t require the AI-generated code itself to have a logic bug, a missing authorization check, or any of the subtler mistakes general AI-code-security guidance focuses on. The entire attack succeeds or fails on one yes/no question — does this exact package name exist, and if so, is it the real one — which is why the mitigations below are comparatively simple and mechanical compared to, say, reviewing AI-generated authentication logic.
Real-World Mitigations
Verify package existence and provenance before install. Before running an install command an AI assistant suggested, confirm the package actually exists in the target registry, was registered well before your project started, and has a publisher with an established track record — a newly registered package with no history is a meaningful red flag regardless of how plausible its name sounds. Commercial tools like Socket, Snyk, and Aikido automate this check and can be wired directly into CI.
Commit lockfiles and verify them on every install. A lockfile pins exact versions and content hashes for every dependency, including transitive ones, so a build can’t silently pull in a different package than the one a human actually reviewed and approved. The critical step most teams skip is verifying the lockfile’s hashes during automated installs — not just having a lockfile, but enforcing it:
# Python: install only exact, hash-verified versions from requirements.txt
# requirements.txt must list a --hash=sha256:... entry for every package
pip install --require-hashes -r requirements.txt
# Node.js: install exactly what's in package-lock.json; fails if it's out of sync
npm ci
# A requirements.txt line with a pinned hash looks like this:
# requests==2.32.3 \
# --hash=sha256:70761cfe03c773ceb22aa2f671b4757976145175cdfca038c02654d061d6dc6
pip install --require-hashes refuses to install anything that isn’t in the lockfile with a matching hash, and npm ci (as opposed to npm install) refuses to modify package-lock.json at all — both turn “the AI suggested a new package” into a build failure that demands a human decision, rather than a silent, successful install.
Regenerate dependency trees from an approved lockfile, not from scratch. If an AI coding agent or assistant proposes adding a new dependency, that addition should go through the same review and approval step as any other dependency change — updating the lockfile deliberately — rather than letting an agent run an uncontrolled install command directly against a live environment.
Restrict what autonomous coding agents can install. For agents with any package-management ability, allowlist specific, pre-approved packages and route anything else to human review; if that isn’t practical for your workflow, disable automated package installation in agentic environments entirely until you can add that gate.
Flag newly registered packages in CI. Configure software composition analysis (SCA) tooling to flag any dependency registered in the 30–90 days before it was first introduced into your codebase — this window catches both slopsquatting and more conventional typosquatting without needing to know in advance which specific name is fake.
Trade-Offs
Pros: the core mitigations (hash-verified lockfiles, package-existence checks, CI allowlisting) are mechanical, automatable, and don’t require judging AI-generated logic — they’re genuinely effective against this specific, narrow attack vector and most teams can adopt them without a major process overhaul.
Cons: strict hash verification and lockfile enforcement can slow down legitimate dependency updates and requires deliberate process for adding anything new; newly-registered-package flagging produces false positives for genuinely new, legitimate libraries; and no mitigation here helps if a developer runs an AI-suggested install command manually, outside of CI, on a personal or unmanaged machine.
Who This Matters Most For
Teams using AI coding assistants or autonomous coding agents with any ability to run install commands — whether that’s a human copy-pasting Copilot/Claude/Cursor suggestions or an agent executing pip install autonomously as part of a task — are the direct audience here, especially teams working in ecosystems (Python and JavaScript specifically are the best-studied) and especially teams using open-source or self-hosted models, which the original research found hallucinate roughly four times as often as leading commercial models.
Who Should Look Elsewhere
Teams looking for broader guidance on reviewing AI-generated code in general — authorization logic, injection vulnerabilities, secrets handling — should look at OWASP’s AI-assisted secure coding guidance or a SAST tool comparison instead; this piece deliberately stays narrow on the package-hallucination problem specifically. Teams whose build pipelines already enforce hash-verified lockfiles and have no path for agents to run arbitrary installs have likely already closed most of this attack surface and may get more value focusing elsewhere.
Bottom Line
Slopsquatting is one of the more precisely measured risks in the AI-coding-assistant landscape: researchers can and have quantified exactly how often specific models invent package names, how persistently they repeat the same fabrications, and how often attackers have already weaponized the gap. The rate has improved — 2026’s best frontier models hallucinate at roughly a quarter the rate of 2024’s open-source models — but it hasn’t gone away, and the fix isn’t waiting for models to improve further. It’s treating every AI-suggested dependency as unverified until a lockfile, a hash check, or a human confirms it’s real.
FAQ
Who coined the term “slopsquatting”? Seth Larson, developer-in-residence at the Python Software Foundation, coined it by analogy with “typosquatting,” to describe attackers registering package names that AI models are observed to hallucinate.
How common is package hallucination today? The original 2024/2025 USENIX study found a 19.7% overall rate across 16 models. An independent 2026 replication against five current frontier models found 3.6%–5.0% of package mentions hallucinated — lower, but still a real, non-trivial rate, and roughly equivalent to where 2024’s best commercial models already stood.
Has slopsquatting actually been exploited, or is it theoretical? It’s been observed in practice. Researchers found at least 23 AI-hallucinated package names that had previously hosted real malware before being removed from registries, and one hallucinated name was registered with malware during a 2026 study’s own observation window.
Does using a lockfile fully solve this problem? It substantially reduces the risk for anything going through an enforced CI pipeline (via hash verification and commands like npm ci or pip install --require-hashes), but it doesn’t protect a developer who manually runs an AI-suggested install command outside that pipeline, on a personal machine or in an ad hoc script.
Are open-source models worse than commercial ones for this specific risk? Yes, according to the original research: open-source models averaged a 21.7% hallucination rate versus 5.2% for commercial models — roughly four times higher — though the gap has narrowed in more recent model generations per the 2026 replication study.
Every SaaS product eventually has to answer the same question: when customer A and customer B both use the same application, how much of the underlying infrastructure do they actually share? Get this wrong and you either burn money running near-empty dedicated databases for every small customer, or you build a shared system fragile enough that one noisy tenant degrades everyone else’s experience. AWS’s own SaaS architecture guidance frames this as a spectrum of tenant isolation models — commonly called silo, pool, and bridge — and the choice shapes a SaaS company’s costs, operational complexity, and compliance posture for years.
At a Glance
Model
What It Means
Best For
Silo (database-per-tenant)
Each tenant gets its own dedicated database (or full stack)
Regulated industries, large enterprise tenants, strict per-tenant compliance or customization needs
Pool (shared schema)
All tenants share one database/schema, separated by a tenant ID column on every row
High tenant counts, cost-sensitive SaaS, consumer-scale multi-tenancy
Bridge (hybrid)
A mix — some tenants or resources pooled, others siloed
AWS Well-Architected SaaS Lens and the AWS “SaaS Tenant Isolation Strategies” and “SaaS Storage Strategies” whitepapers
—
Short Verdict
There is no universally “correct” multi-tenancy model — AWS’s own whitepaper on tenant isolation is explicit that the right strategy depends on your domain, compliance requirements, and the specific AWS (or non-AWS) services involved. The pooled, shared-schema model is the cheapest to run at scale and the fastest to onboard new tenants into, but it demands rigorous application-level isolation logic and accepts some risk of one tenant’s load affecting another’s. The silo, database-per-tenant model gives the strongest isolation and the simplest compliance story, at the cost of running — and paying for — essentially duplicate infrastructure per tenant. Most mature SaaS companies end up somewhere in between: a bridge model that pools most tenants for efficiency while siloing the handful that need dedicated resources for contractual, regulatory, or performance reasons.
The Silo Model: Database-per-Tenant
In a silo model, each tenant gets dedicated resources — commonly a dedicated database, sometimes a dedicated full application stack — so nothing is physically shared between tenants. This is the most isolated design available short of running entirely separate installations. Its appeal is straightforward: a noisy or misbehaving tenant can’t degrade another tenant’s performance because they aren’t sharing the same database connections, disk I/O, or compute; a compliance auditor asking “show me this one customer’s data boundary” gets the simplest possible answer; and per-tenant cost attribution is trivial because the infrastructure is already split by tenant. The cost of that isolation is operational: provisioning, migrating, patching, and monitoring N databases instead of one scales linearly (or worse) with tenant count, and onboarding a new tenant means standing up new infrastructure rather than inserting a row.
The Pool Model: Shared Schema
In a pool model, tenants share the same underlying resources — the same database, often the same tables — and isolation is enforced logically rather than physically, typically through a tenant identifier column present on every row and enforced by application code, row-level security policies, or both. AWS’s whitepaper on tenant isolation strategies describes the trade-off plainly when discussing pooled resources generally: “the concepts and tradeoffs of pool isolation tend to be similar for most resources… you’ll find yourself balancing the available isolation mechanisms with the efficiency of having a resource that is shared by tenants.” That’s the whole trade in one sentence — pooling is efficient precisely because it avoids duplicating infrastructure per tenant, and the price of that efficiency is that isolation has to be actively engineered and verified rather than coming for free from physical separation.
The same AWS guidance notes that when a pooled approach proves genuinely difficult for a particular resource, teams are pushed toward either a silo model for that resource specifically, or toward “application-enforced isolation” — meaning the isolation guarantee has to be implemented and maintained correctly in your own code, which is a real and ongoing engineering cost rather than a one-time infrastructure decision.
A Minimal Illustration: Enforcing Pool Isolation
This is a simplified sketch of the application-level discipline a pooled model requires: every query must be scoped to a tenant, with no code path that can accidentally omit the filter.
class TenantScopedRepository:
"""Wraps a shared table and refuses to run any query
without an explicit tenant_id filter."""
def __init__(self, db_connection, table_name):
self.db = db_connection
self.table_name = table_name
def find_by_id(self, tenant_id, record_id):
if not tenant_id:
raise ValueError("tenant_id is required for every pooled query")
query = (
f"SELECT * FROM {self.table_name} "
f"WHERE tenant_id = %s AND id = %s"
)
return self.db.execute(query, (tenant_id, record_id))
def list_all(self, tenant_id):
if not tenant_id:
raise ValueError("tenant_id is required for every pooled query")
query = f"SELECT * FROM {self.table_name} WHERE tenant_id = %s"
return self.db.execute(query, (tenant_id,))
def insert(self, tenant_id, record):
if not tenant_id:
raise ValueError("tenant_id is required for every pooled query")
record = {**record, "tenant_id": tenant_id}
columns = ", ".join(record.keys())
placeholders = ", ".join(["%s"] * len(record))
query = f"INSERT INTO {self.table_name} ({columns}) VALUES ({placeholders})"
return self.db.execute(query, tuple(record.values()))
Notice what this code is actually doing: it’s manually re-implementing, at the application layer, the isolation boundary that a silo model gets for free from using physically separate databases. That’s the real cost of pooling — not just a column on every table, but a discipline that every single query path has to honor, forever, with no second line of defense if a developer forgets the filter. (Row-level security features in databases like PostgreSQL can enforce this boundary at the database layer instead of relying purely on application code, which is why many production pooled systems combine both.)
The Bridge (Hybrid) Model
Few real SaaS products are purely siloed or purely pooled end to end. The bridge model combines both: a common pattern is pooling standard-tier tenants into shared infrastructure for cost efficiency while giving premium, enterprise, or regulated tenants their own dedicated database or stack, often as a paid tier feature in its own right. This lets a SaaS company keep its cost structure sane for its long tail of small customers while still being able to sign the handful of large enterprise or regulated customers whose procurement or compliance teams require dedicated infrastructure as a contractual condition. The cost of the bridge model is architectural: the system now has to actually support two (or more) isolation strategies simultaneously, which means more code paths, more operational runbooks, and more ways for a new engineer to get the isolation boundary wrong.
Comparison
Factor
Silo
Pool
Bridge
Isolation strength
Strongest — physical separation
Weakest by default — logical only, enforced by code/policy
Varies by tenant tier
Cost efficiency at scale
Worst — infrastructure scales with tenant count
Best — infrastructure shared across all tenants
Mixed — pays silo cost only for tenants who need it
Onboarding speed
Slowest — new infrastructure per tenant
Fastest — new tenant is just new rows
Depends on which tier a new tenant lands in
Compliance/audit story
Simplest to explain and prove
Hardest — requires demonstrating logical controls work correctly
Simple for siloed tenants, harder for pooled ones
Operational complexity
High at scale (many databases to patch/monitor)
Low (one system to operate) but high engineering discipline required
Highest — two or more models to build, test, and operate at once
Trade-offs
Silo isolation removes an entire category of “did we isolate tenant data correctly” risk, but multiplies infrastructure, patching, and monitoring overhead by tenant count.
Pool isolation is the cheapest and fastest to operate at scale, but AWS’s own guidance is explicit that it requires ongoing engineering effort to keep isolation correct — there’s no free physical boundary to fall back on.
A bridge model lets a SaaS company serve very different customer segments economically, but it means maintaining more than one isolation strategy in the same codebase and organization simultaneously.
None of these models is fixed forever: AWS’s guidance frames isolation choice as something that can and often does vary resource-by-resource within a single SaaS product, not a single company-wide decision made once.
Bottom Line
Multi-tenant architecture isn’t a single switch between “shared” and “dedicated” — it’s a spectrum, and AWS’s own SaaS guidance treats it as a decision made per resource and per tenant tier, not once for the whole product. Start from what actually drives the decision for your product: if compliance or large-enterprise contracts demand dedicated infrastructure for some customers, build a bridge from day one rather than retrofitting it later. If your growth model depends on onboarding large numbers of small or mid-size tenants cheaply, invest early in rigorous, verifiable pool isolation rather than treating a shared tenant_id column as sufficient on its own. The companies that get this wrong usually don’t pick the wrong model outright — they pick a reasonable model and then under-invest in the isolation discipline it actually requires.
FAQ
Is pooled multi-tenancy inherently less secure than database-per-tenant? Not inherently — but it shifts where the isolation guarantee lives, from the infrastructure layer to the application (and, if used, database row-level security) layer, which means it has to be actively engineered and tested rather than assumed from physical separation.
Can a SaaS company switch from pooled to siloed later for a specific customer? Yes, and this is exactly what the bridge model is for — many SaaS products start fully pooled and add siloed infrastructure as an option for specific large or regulated customers without rearchitecting the whole system.
Does AWS recommend one model over the others? No. AWS’s whitepaper guidance frames the choice as dependent on domain, compliance requirements, deployment model, and the specific services involved, explicitly noting there’s no single ideal strategy that fits every resource in every SaaS product.
What’s the single biggest risk in a pooled, shared-schema design? A code path that queries or writes to the shared table without a tenant filter — whether from a missed check, a background job, an admin tool, or a new engineer unfamiliar with the convention. That single omission is the entire failure mode pooled isolation has to guard against on every query, forever.
A quick note before this comparison starts: Pocket, long a default pick in this category, was shut down by its owner Mozilla — the shutdown was announced in May 2025 and the service stopped working by October 2025, so it’s no longer a live option to compare. In its place, we’ve swapped in Readwise Reader, which has absorbed a lot of Pocket’s former user base and takes a notably different approach from either Instapaper or Raindrop.io. Here’s how Instapaper, Raindrop.io, and Readwise Reader compare today.
At a Glance
Spec
Instapaper
Raindrop.io
Readwise Reader
Entry paid price
Premium: $5.99/mo or $59.99/yr
Pro: $2.99/mo or $27.99/yr (App Store pricing)
$9.99/mo billed annually, or $12.99/mo billed monthly
Free plan?
Yes — unlimited saving, limited notes/summaries
Yes — unlimited bookmarks and collections
30-day free trial, no permanent free tier
Core focus
Minimalist reading experience for articles
General-purpose bookmarking with folders/tags
Reading plus spaced-repetition highlight review
Best for
Readers who want a clean, distraction-free article view
People organizing bookmarks across many sources, not just articles
Readers who want to actually retain and resurface what they’ve saved
Short Verdict
Instapaper is still the simplest and cheapest of the three, and its free tier is genuinely usable if you only save a handful of articles a month. Raindrop.io is the best general-purpose bookmarking tool — it treats your saves as a searchable, taggable library rather than just a reading queue, and its Pro tier is the cheapest paid option here. Readwise Reader is the priciest by a meaningful margin, but it’s solving a different problem than the other two: it’s built around actually reviewing and retaining your highlights over time with spaced repetition, not just storing articles to read later.
What Each Tool Is
Instapaper is a dedicated read-it-later app: save an article from any browser or app, and it strips the page down to a clean, distraction-free reading view with adjustable fonts and themes, available offline. It’s stayed close to its original, narrow focus for over a decade rather than expanding into general bookmarking or note-taking.
Raindrop.io is a general bookmark manager first and a reading tool second — it organizes saved links (articles, videos, images, anything with a URL) into collections and tags, with full-text search across saved pages, PDFs, and even YouTube transcripts on the paid tier. It’s the closest of the three to a “second brain” for links rather than a pure reading queue.
Readwise Reader, from the makers of the Readwise highlight-review service, combines a read-it-later inbox (articles, PDFs, EPUBs, tweets, YouTube transcripts, newsletters) with built-in highlighting and Readwise’s spaced-repetition review system, which resurfaces your past highlights over time instead of letting them disappear into storage once you’re done reading.
Pricing Breakdown
Plan
Price
What you get
Instapaper Free
$0
Unlimited article saving; 5 notes/mo; 10 AI summaries/mo (iOS/web, not Android); title-only mobile search
Instapaper Premium
$5.99/mo or $59.99/yr
Unlimited notes and summaries; full-text search including archived articles; PDF reading; AI voice playback; Kindle digests
Raindrop.io Free
$0
Unlimited bookmarks, collections, and devices; collaboration with others; 100 MB/mo file uploads
Raindrop.io Pro
$2.99/mo or $27.99/yr (App Store listing)
AI assistant; full-text search across bookmarks, PDFs, EPUBs, and YouTube transcripts; permanent page archive; broken-link checker; 10 GB/mo file uploads
Readwise Reader (30-day free trial)
$0 for 30 days
Full access to Reader and Readwise highlight/review features during the trial
Readwise Reader — annual
$9.99/mo billed yearly
Full Reader + Readwise subscription; 50% student/non-profit/military discount available on request
Readwise Reader — monthly
$12.99/mo billed monthly
Same features as annual, billed month to month
Instapaper’s prices come from its own App Store listing, which matches independent pricing trackers. Raindrop.io doesn’t expose plain-text pricing on its own marketing pages (raindrop.io/pro and raindrop.io/pro/buy are JavaScript-rendered and didn’t return dollar figures when fetched directly), so the $2.99/mo and $27.99/yr figures above come from Raindrop’s own iOS App Store listing instead — a first-party source, just a different page than the marketing site. Readwise’s figures come directly from readwise.io/read.
Pros and Cons
Instapaper
Pros: cheapest paid tier of the three; clean, focused reading experience with few distractions; works well for Kindle users via email digests.
Cons: no real retention or review system — once you’ve read an article, it’s just archived, not resurfaced; free tier’s note and summary limits are tight.
Raindrop.io
Pros: genuinely unlimited free tier for bookmarks and collections; works for any kind of link, not just articles; strong search once you’re on Pro.
Cons: reading experience is more basic than Instapaper’s or Reader’s — it’s a bookmark manager that can display articles, not an article-reading app first; official pricing page is hard to verify directly (we used the App Store listing instead).
Readwise Reader
Pros: the only one of the three built around actually retaining what you read, via spaced-repetition highlight review; handles the widest range of content types (tweets, newsletters, EPUBs, YouTube).
Cons: by far the most expensive of the three, with no permanent free tier — just a 30-day trial; the highlight-review workflow is a real habit to build, and it’s overkill if you just want a simple reading queue.
Who It’s a Good Fit For
Choose Instapaper if you want the cheapest, simplest way to save and read articles distraction-free.
Choose Raindrop.io if you’re organizing more than just articles — videos, product links, references — into a searchable, taggable library.
Choose Readwise Reader if you genuinely want to retain and resurface what you read, not just archive it, and you’re willing to pay a premium and build a review habit for that.
Who Should Look Elsewhere
If you already use a personal knowledge management tool like Obsidian or Logseq for backlinked notes, you may not need a separate read-it-later app’s highlight system — see our Notion vs Obsidian vs Logseq comparison for that adjacent decision. And if your main need is simply tracking tasks and to-dos rather than saved reading material, none of these three is the right tool — see our to-do list app comparison instead.
Bottom Line
For most people who just want a tidy, affordable reading queue, Instapaper or Raindrop.io’s free or low-cost paid tiers will cover it — Instapaper if articles are your main content type, Raindrop.io if you’re bookmarking a wider mix of links. Readwise Reader is worth its higher price specifically if retention is the point: if you keep forgetting what you’ve read and want a system that actively brings old highlights back to you, it’s solving a problem the other two don’t attempt to solve at all.
FAQ
Is Pocket still a usable alternative?
No. Mozilla announced it was shutting down Pocket in May 2025, and the service stopped operating by October 2025. Any comparison still listing Pocket as an active option is out of date.
Which of these three has a real permanent free plan?
Instapaper and Raindrop.io both offer permanent free tiers with unlimited saving. Readwise Reader offers only a 30-day free trial, with no permanent free tier after that.
Can I import my old Pocket saves into any of these?
Instapaper, Raindrop.io, and Readwise Reader all support general bookmark/CSV or HTML import, which is the standard way people moved their data off Pocket before it shut down. Check each app’s current import documentation for the exact supported file format, since specifics can change.
Does Raindrop.io’s official pricing page show exact dollar amounts?
Not when accessed as a plain page — Raindrop’s marketing pricing pages are JavaScript-rendered and didn’t return plain-text prices during our research. We sourced the specific $2.99/mo and $27.99/yr figures from Raindrop’s own iOS App Store listing instead, which is still a first-party source. Confirm the live price on raindrop.io/pro/buy or in your app store before subscribing.
We’ve already covered the Blackwell/GB300 die itself, the Vera Rubin platform that follows it, and the broad NVLink/InfiniBand/Spectrum-X networking stack that ties Nvidia’s racks together. This piece goes narrower and newer: NVLink Fusion, the 2025 program that lets non-Nvidia chips plug into NVLink, and UALink, the rival open standard a coalition of Nvidia’s biggest customers and competitors built specifically because they didn’t want to depend on NVLink at all. Both are, at their core, answers to the same question — who gets to control the wires between AI chips — and they point in opposite directions.
At a Glance
Technology
Type
Scope
Headline bandwidth (as published)
Status
NVLink (6th gen)
Proprietary, Nvidia-only
GPU-to-GPU and CPU-to-GPU, chip-to-chip and rack-scale
3,000 GB/s per GPU per Nvidia’s NVLink product page; 3.6 TB/s per GPU per Nvidia’s NVLink Fusion page (the two Nvidia pages disagree — see note below)
Shipping with Vera Rubin, launched at CES, January 2026
NVLink Fusion
Licensing program built on NVLink-C2C
Lets third-party CPUs/XPUs attach to Nvidia GPUs, switches, and racks
Not separately specified; inherits NVLink/NVLink-C2C figures
Announced around Computex, May 2025
UALink 200G 1.0
Open standard (UALink Consortium)
Accelerator-to-accelerator, within a pod
800 Gbps per link (per the Consortium’s own 1.0 spec overview)
Specification released April 2025
Short Verdict
NVLink Fusion and UALink are both reactions to the same industry anxiety — that Nvidia’s interconnect, not just its GPUs, has become a lock-in point — but they solve it in opposite ways. NVLink Fusion keeps Nvidia in the center: it opens NVLink’s wiring to outside CPUs and custom accelerators, but on Nvidia’s protocol, inside Nvidia’s MGX rack architecture. UALink removes Nvidia from the center entirely: it’s a standard written by a consortium that explicitly includes several of Nvidia’s biggest rivals and customers (AMD, Broadcom, Google, Intel, Meta, Microsoft, and others), designed so that nobody needs an Nvidia license to build an accelerator that talks to other accelerators at high bandwidth. As of this writing, NVLink Fusion has named real silicon partners across CPUs, custom accelerators, and optical interconnects, while UALink has a published 1.0 specification but we found no public confirmation yet of shipping hardware built to it.
NVLink Fusion: Opening the Wiring, Not the Standard
Nvidia’s own NVLink Fusion page describes it as “high-bandwidth, low-latency connective technology and IP” that lets hyperscalers and AI-native companies attach custom XPUs and CPUs to Nvidia’s AI infrastructure using the MGX rack-scale architecture. Mechanically, it extends NVLink-C2C — the same chip-to-chip coherent link Nvidia uses internally to join a Grace CPU to Blackwell GPUs inside one “Superchip” module — outward to partner silicon instead of only Nvidia’s own dies.
Nvidia’s page names partners across several categories via its partner logos, without labeling each one explicitly: likely CPU partners include Arm, Intel, Fujitsu, and SiFive; custom silicon and IP partners include Alchip, Astera Labs, GUC, Marvell, MediaTek, Samsung, Cadence, and Synopsys; optical interconnect partners include Ayar Labs, Lightmatter, and Marvell; and Amazon’s Annapurna Labs is named specifically as the first partner working with Nvidia on NVHBM, a custom high-bandwidth-memory design. Contemporary tech press coverage around the May 2025 announcement (Computex season) described the pitch in similar terms — Nvidia selling the connective tissue of its racks separately from the GPUs themselves, so a hyperscaler could, in principle, pair a custom CPU or AI accelerator with Nvidia GPUs, switches, cooling, and power in one rack rather than building a fully separate non-Nvidia system.
The business logic is straightforward: even a hyperscaler building its own custom AI accelerator (as Google, Amazon, and Microsoft already do) still often wants Nvidia GPUs in the same data center for other workloads. NVLink Fusion lets Nvidia capture rack-level revenue and relevance even in a system built around someone else’s primary compute chip — a hedge against the scenario where custom silicon erodes Nvidia’s core GPU sales.
UALink: An Open Standard Built Specifically to Not Need Nvidia
UALink (Ultra Accelerator Link) is run by the UALink Consortium, whose promoter group — per the press release linked from the Consortium’s own site — includes AMD, Broadcom, Cisco, Google, Hewlett Packard Enterprise, Intel, Meta, and Microsoft. That list is notable less for who’s in it than for who isn’t: Nvidia. The Consortium describes UALink as “an open industry Interconnect standard meeting market demand for advanced AI Accelerator-to-Accelerator communication,” explicitly positioned as a standard any accelerator vendor can build to without licensing proprietary IP from a single company.
The Consortium released its UALink 200G 1.0 specification in April 2025. Per the Consortium’s own specification overview document, the standard delivers 800 Gbps per link, supports up to 1,024 accelerators in a single pod, and targets “the latency of PCIe switches” while claiming 93% effective peak bandwidth under deterministic performance conditions. The 1.0 spec’s initial focus is direct load, store, and atomic memory operations between accelerators — the same class of operation NVLink handles for Nvidia’s own GPUs. Notably, the specification document itself doesn’t mention NVLink by name or make a direct head-to-head comparison; the “open alternative to a proprietary interconnect” framing comes from how the Consortium and industry press describe UALink’s purpose, not from language in the spec itself.
NVLink’s Generation History: 1 Through 6
To see how far NVLink has come, and why Nvidia now treats it as valuable enough to license out, it helps to look at the full generational arc. Nvidia’s own current nvlink product page only documents the three most recent generations in detail; figures for the earlier generations below come from secondary sources (chiefly Wikipedia’s NVLink entry) rather than from Nvidia’s own currently published materials, so treat those three rows as reasonably well-established industry history rather than Nvidia-confirmed figures.
Generation
Associated architecture
Bandwidth per GPU
Source confidence
NVLink 1.0
Pascal (P100), 2016
160 GB/s
Secondary source only (not on Nvidia’s current site)
NVLink 2.0
Volta (V100), 2017
300 GB/s
Secondary source only
NVLink 3.0
Ampere (A100), 2020
600 GB/s
Secondary source only
NVLink 4.0
Hopper (H100), 2022
900 GB/s
Confirmed directly on Nvidia’s current NVLink page
NVLink 5.0
Blackwell, 2024
1,800 GB/s
Confirmed directly on Nvidia’s current NVLink page
NVLink 6.0
Vera Rubin, launched CES January 2026
3,000 GB/s per Nvidia’s NVLink page; 3.6 TB/s per Nvidia’s NVLink Fusion page
Confirmed on Nvidia’s own site, but the two Nvidia pages disagree with each other — see below
A Genuine Conflict in Nvidia’s Own Published Numbers
Worth flagging directly rather than papering over: Nvidia’s own NVLink product page states that a 6th-generation NVLink Switch delivers 216 TB/s of aggregate bandwidth across a 72-GPU NVL72 domain, with 3,000 GB/s (3 TB/s) per GPU. Nvidia’s separate NVLink Fusion page, however, states that “NVLink 6 with the NVLink Switch Chip provides 260 TB/s” in a 72-accelerator domain, with each XPU connected at 3.6 TB/s. Those are two different numbers, from two different pages, both currently published by Nvidia, for what appears to be the same underlying NVL72-class system. We could not resolve this discrepancy from Nvidia’s public materials — it may reflect different measurement conventions, different specific rack configurations, or simply a page that hasn’t been updated to match the other. Nvidia also explicitly labels its NVLink 6 specifications as “preliminary and subject to change,” which may partly explain the mismatch. Either way, don’t treat either figure as the single definitive number without checking Nvidia’s current page yourself, and expect both to keep moving before Vera Rubin hardware is broadly deployed.
NVLink/NVLink Fusion vs. UALink: Where They Actually Compete
Dimension
NVLink / NVLink Fusion
UALink 200G 1.0
Governance
Controlled by Nvidia; Fusion extends access via licensing/partnership, not open standardization
Governed by a multi-vendor consortium (AMD, Broadcom, Cisco, Google, HPE, Intel, Meta, Microsoft, and others)
Who can build hardware against it
Nvidia and named Fusion partners, under Nvidia’s program
Any vendor, per the Consortium’s stated open-standard positioning
Published bandwidth
Up to 3,000–3.6 TB/s per GPU (6th gen, figures conflict between Nvidia’s own pages)
800 Gbps per link, bondable across multiple links per accelerator
Maximum scale (as published)
72-GPU NVL72 domain for rack-scale switch fabric
Up to 1,024 accelerators per pod, per the Consortium’s 1.0 overview
Deployment status
Shipping (NVLink itself, in Blackwell/Vera Rubin systems); Fusion partner hardware not yet broadly confirmed as shipping
Specification published (April 2025); we found no public confirmation of UALink-compliant hardware shipping yet
Trade-offs
NVLink’s raw per-GPU bandwidth figures, even taking the lower of Nvidia’s two conflicting 6th-gen numbers, are well above UALink 200G 1.0’s published 800 Gbps-per-link figure — though the two aren’t directly comparable without knowing how many UALink links a given accelerator bonds together, which the spec allows.
NVLink Fusion gives partners access to Nvidia’s mature, already-deployed rack ecosystem (MGX, NVLink Switch, cooling, power) today; UALink gives adopters independence from any single vendor’s roadmap, at the cost of building on a newer, less battle-tested standard.
The UALink promoter list reads like a who’s-who of companies with their own custom AI silicon ambitions (Google TPUs, Amazon’s chips via its own ecosystem ties, Microsoft Maia, Meta’s MTIA) — their interest in an open standard is also, transparently, an interest in not paying an Nvidia toll for accelerator-to-accelerator bandwidth.
Nvidia’s willingness to open NVLink at all, via Fusion, is itself a signal that the company sees enough competitive pressure from efforts like UALink to prefer “we’ll license you in” over “build something else entirely.”
Bottom Line
NVLink Fusion and UALink are both, in their own way, acknowledgments that interconnect bandwidth — not just GPU FLOPS — has become a strategic chokepoint in AI infrastructure. Nvidia’s answer is to sell access to its own wiring rather than let an open standard take that layer away from it; a large coalition of its biggest customers and rivals built UALink specifically so they wouldn’t have to ask. Neither has fully proven itself yet: NVLink Fusion has named partners but limited public evidence of shipped, in-production hardware as of this writing, and UALink has a real published specification but, as far as we could confirm, no broadly deployed hardware built to it yet either. Watch this space over the next year — whichever one ships real, benchmarked hardware first will have a meaningful head start in setting the next default for how AI accelerators talk to each other beyond a single chip.
FAQ
Is NVLink Fusion the same thing as NVLink? No. NVLink is Nvidia’s interconnect technology itself; NVLink Fusion is a licensing/partnership program that extends NVLink-C2C chip-to-chip connectivity to non-Nvidia CPUs and custom accelerators, built around Nvidia’s MGX rack architecture.
Who is building UALink, and is Nvidia involved? The UALink Consortium’s promoter group, per its own press materials, includes AMD, Broadcom, Cisco, Google, Hewlett Packard Enterprise, Intel, Meta, and Microsoft. Nvidia is not listed among the promoters.
Which has higher bandwidth, NVLink or UALink? On a per-GPU/per-accelerator basis, Nvidia’s published NVLink 6 figures (3,000–3.6 TB/s, depending on which Nvidia page you read) are well above UALink 200G 1.0’s published 800 Gbps per link — though UALink accelerators can bond multiple links, and the two technologies aren’t tested under identical conditions, so direct comparison should be treated cautiously.
Why do two different Nvidia pages give different NVLink 6 bandwidth numbers? We don’t know for certain — it may reflect different rack configurations, measurement methods, or simply pages that haven’t been reconciled. Nvidia itself labels its NVLink 6 specifications as preliminary and subject to change.
Is UALink hardware available to buy yet? We found no public confirmation of shipping UALink-compliant hardware as of this writing; the Consortium has published its 200G 1.0 specification, but turning a specification into deployed silicon typically takes considerably longer.
“CDN” and “edge compute” get used almost interchangeably now, but they’re not the same purchase decision. A classic content delivery network caches your static assets — images, video, CSS, JS, API responses — at points of presence close to your visitors and absorbs traffic spikes and DDoS attacks before they ever reach your origin server. That’s a different product from running your own code at the edge, which this site covers separately in our Edge Computing Platforms comparison (Cloudflare Workers vs. Fastly Compute vs. Vercel Edge Functions). This piece is about the older, simpler job: getting your existing content delivered fast, everywhere, and kept online under attack. Three names dominate that conversation — Cloudflare, Fastly, and Akamai — and they price, size, and position themselves very differently.
At a Glance
CDN
Entry Pricing
Published Network Size
Pricing Transparency
Cloudflare
Free tier available; Pro $20/mo (annual) or $25/mo (monthly); Business $200/mo (annual) or $250/mo (monthly)
348 cities across 8 regions; 100+ countries; 13,000+ network interconnections
Fully published self-serve pricing
Fastly
First 100 GB/month and first 1M requests/month free; then usage-based per-GB/per-region pricing; preconfigured packages from $1,500/month
114 live city locations (some with multiple PoPs); network capacity reported as 655 Tbps (Sept 30, 2026 stat) or 622 Tbps elsewhere on Fastly’s own site — the two figures disagree
Fully published usage-based pricing plus package tiers
Cloudflare is the easiest CDN to start with today: a genuinely free tier with unmetered DDoS protection, fully published pricing up through its Business plan, and a network Cloudflare describes as spanning 348 cities. Fastly is the usage-based, transparent-pricing option for teams who want to see exactly what each gigabyte and request costs across regions, with a smaller but still substantial city footprint and packages that scale into enterprise territory. Akamai is the oldest and, by its own published figures, the largest network of the three by PoP count — but it publishes no self-serve pricing anywhere, which means every Akamai CDN deal starts with a sales conversation rather than a pricing page.
What Each One Actually Is
Cloudflare
Cloudflare’s CDN sits in front of a site at the DNS level and caches content across a network it describes, on its own network page, as 348 cities spanning 8 regions, with 100+ countries and 13,000+ network interconnections. A separate Cloudflare blog post from April 2026 puts total provisioned external interconnection capacity at 500 Tbps across 330+ cities — a different city count than the main network page, which is a reminder that these self-reported figures are snapshots, not a single frozen number. Plans run Free ($0/month) through Pro, Business, and a custom-quoted Contract tier, with the plan comparison listing “Unmetered DDoS Protection” on every tier, including Free.
Fastly
Fastly’s Full Site Delivery product bills bandwidth per GB, broken out by region, with the first 100 GB and the first 1 million requests free every month. Fastly’s own network map page lists 114 live city locations (several marked as having multiple individual PoPs, so the true PoP count exceeds the city count) with four more cities listed as “coming soon.” On network capacity, Fastly’s site states two different figures in different places — “655 Tbps of connected global capacity” as of September 30, 2026 in one stats panel, and “622 Tbps” in its network-map teaser elsewhere on the same site — which we’re flagging here rather than picking one, since both appear on Fastly’s own pages.
Akamai
Akamai is the longest-established of the three, and its CDN business is bundled into a much larger security and cloud-computing portfolio. Akamai’s own “Global Infrastructure” page states its network spans 4,000+ edge PoPs, 1,200+ networks, and 130+ countries, with over 1 petabit per second of edge capacity. Consistent with most of Akamai’s enterprise product line, there is no published price list for its CDN anywhere on Akamai’s own site — every deployment is quoted individually, which our research also confirmed is true of Akamai’s adjacent App & API Protector and Prolexic DDoS products.
Pricing Breakdown
Tier/Plan
Cloudflare
Fastly
Akamai
Free / entry tier
Free plan, $0/month, includes unmetered DDoS protection
First 100 GB bandwidth + first 1M requests free every month
None published
Mid-tier self-serve
Pro: $20/mo annual or $25/mo monthly; Business: $200/mo annual or $250/mo monthly
Usage-based: e.g. $0.12/GB (Europe/North America, 100GB–10TB tier), dropping to $0.08/GB on the next 10TB; other regions range up to $0.28/GB
Not metered on paid plans; Free tier has no published request cap
First 1M requests/month free, then $0.01 per 10,000 (1M–100M tier), $0.0095 per 10,000 (next 100M)
Not published
Pros
Cloudflare: genuinely usable free tier with unmetered DDoS protection included from day one; fully transparent self-serve pricing through Business; very large published city/network footprint.
Fastly: fully itemized, usage-based pricing that scales predictably with actual traffic; a real free monthly allowance, not just a trial; packaged tiers give a clear jump-off point for growing traffic.
Akamai: the largest published PoP count of the three (4,000+) and the longest operating history in the CDN market, with security and performance products that go well beyond basic content delivery.
Cons
Cloudflare: its own pages give inconsistent city counts across different publications (348 vs. 330+), so treat exact figures as approximate; advanced compliance and SLA features are gated behind the Business tier and above.
Fastly: smaller published city footprint than Cloudflare or Akamai; its own site states two conflicting network-capacity figures (655 Tbps vs. 622 Tbps); jump from the free allowance to a $1,500+/month package is a bigger step than Cloudflare’s $20/month Pro tier.
Akamai: zero public pricing anywhere, for the CDN or its adjacent security products, which makes it effectively impossible to budget for without a direct sales engagement.
Who It’s a Good Fit For
Cloudflare fits startups, small sites, and teams who want strong default performance and DDoS protection immediately, with a clear self-serve upgrade path as compliance or SLA needs grow. Fastly fits teams that want precise, predictable, usage-based billing and are comfortable reading a per-region rate card, especially those already weighing Fastly’s Compute platform for edge logic alongside its CDN. Akamai fits large enterprises with high, globally distributed traffic — particularly those with strict compliance or security requirements — who are prepared to go through a sales and contracting process rather than self-serve signup.
Who Should Look Elsewhere
Teams that want to budget precisely before writing a line of code should be cautious with Akamai, since no number is available until a sales conversation happens. Teams that want the absolute largest published PoP footprint and don’t need Cloudflare’s broader product ecosystem might find Fastly’s smaller city count a limiting factor. And teams that specifically need to run custom code at the edge — not just cache static assets — should look at our separate edge computing platforms comparison rather than treating any of these three purely as CDNs.
Bottom Line
For most teams starting out, Cloudflare’s combination of a real free tier, included DDoS protection, and transparent self-serve pricing makes it the easiest on-ramp. Fastly is the right call when you want granular, usage-based cost visibility and are prepared to read a regional rate card closely. Akamai remains the default choice for large enterprises that value its network scale and broader security portfolio enough to go through a custom quoting process — but it’s not a CDN you can price-compare on a spreadsheet without talking to sales first.
FAQ
Is Cloudflare’s free CDN tier actually usable for a production site? Cloudflare’s own plan comparison lists unmetered DDoS protection as included on the Free plan, alongside core CDN caching — it’s a genuine free tier, not a time-limited trial, though features like PCI DSS 4.0 compliance and an uptime SLA are reserved for Business and above.
Why doesn’t Akamai publish CDN pricing? Akamai’s enterprise sales model, consistent across its CDN, WAF, and DDoS protection (Prolexic) product lines, relies on custom quotes tailored to traffic volume, feature set, and contract term rather than a published self-serve rate card.
How is this different from the Cloudflare Workers vs. Fastly Compute vs. Vercel comparison on this site? That piece compares edge compute platforms — where you run your own custom code at the network edge. This piece compares the same companies’ (and Akamai’s) classic CDN products — caching and delivering static assets and absorbing traffic/DDoS load, with no custom code involved.
Which CDN has the biggest network? By published PoP count, Akamai claims the largest footprint at 4,000+ edge PoPs, versus Cloudflare’s 348 cities and Fastly’s 114 live city locations. PoP count and city count aren’t directly comparable metrics, though, since a single city can host multiple PoPs.
An estimated 250 billion lines of COBOL are still running in production today, by a widely cited 2021 TechChannel survey figure that both IBM and most of the trade press continue to reference. Every vendor with a stake in enterprise software — IBM, Google, AWS, and a wave of startups — now has an “AI agent” pitch for modernizing that code, whether that means explaining it, rewriting it in Java, or migrating it off the mainframe entirely. The pitches are consistent; the actual, independently measured performance of these agents on real legacy code is a lot more mixed than the marketing suggests, and 2026 is the first year there’s hard benchmark data to check the claims against.
At a Glance
Approach
What It Does
Representative Tools
Maturity
Code understanding / documentation
Uses an LLM to read legacy code and generate plain-language explanations, business-rule extraction, and dependency maps
IBM watsonx Code Assistant for Z, Google’s Mainframe Assessment Tool (MAT), Swimm
Most mature — lower risk, no code changes, used as a first step before any rewrite
Deterministic (like-for-like) modernization
Restructures code/data to a new platform while requiring provably identical outputs for identical inputs
Google’s Dual Run (parallel-run verification), Mainframe Connector (data migration)
Moderate — well-suited to regulated, high-stakes systems where behavior can’t change
Agentic rewrite / translation
Multi-agent systems that translate COBOL to Java (or another target language) and review their own output
Persistent Systems’ coder/reviewer multi-agent system, Google Antigravity (agentic harness)
Least mature — independent benchmarks show current agents solving well under half of real-world legacy tasks
Short Verdict
AI agents are genuinely useful for the first, lowest-risk part of legacy modernization — reading 50-year-old COBOL and producing documentation, dependency maps, and business-rule extraction that would otherwise require retiring subject-matter experts to explain line by line. They are considerably less reliable once you ask them to autonomously rewrite or migrate that code: the first independent benchmark built specifically for this task, Factory’s LegacyBench (announced April 1, 2026), found the best-performing model-agent combination solved only 42.5% of its legacy coding tasks overall, and just 34.8% of its COBOL-specific tasks — compared with the same models scoring above 70% on modern-code benchmarks like SWE-bench Verified. Treat vendor claims about full autonomous migration with real skepticism, and treat AI-assisted code understanding as the safer, more defensible place to start.
Why COBOL Modernization Is Hard — With or Without AI
Google’s own engineering materials on mainframe modernization are unusually candid about why this problem resists simple automation: it “isn’t a pure code-to-code conversion problem.” The hard parts are tightly coupled data and logic (COBOL programs often embed business rules directly in record layouts and file structures that have no modern equivalent), transaction scenarios that span legacy utilities and protocols with no modern documentation, undefined application boundaries after decades of ad hoc patches — commonly described as “spaghetti code” — and intricate sequential batch workflows that assume mainframe-specific execution guarantees. None of that is a language-translation problem an LLM can solve by pattern-matching COBOL syntax to Java syntax; it requires understanding what the code is actually for, which is exactly where AI coding tools have historically been weakest.
What the Major Players Are Actually Shipping
IBM positions watsonx Code Assistant for Z as an AI-agent layer specifically for explaining mainframe code in natural language and automatically refactoring COBOL applications into modular business services — notably, IBM frames this as something that increases the need for mainframes rather than eliminating them, since the goal is adding AI-assisted capability to systems that stay on Z hardware rather than migrating off it entirely.
Google Cloud offers a more staged toolchain: its Mainframe Assessment Tool (MAT) reverse-engineers legacy code for dependency visualization, automated business-rule extraction, and documentation, connecting into agentic workflows via MCP. From there, Google supports two distinct modernization patterns — a “Rewrite/Reimagine” path using Gemini models and its Antigravity agentic harness (with optional human-in-the-loop governance) for applications where new business logic justifies a rebuild, and a “Deterministic” path for applications that must produce bit-for-bit identical behavior after modernization. The deterministic path’s key safeguard is Dual Run: it executes live production workloads on both the old mainframe and the new Google Cloud environment simultaneously, comparing outputs continuously until logic and data equivalence are proven — which is a meaningfully more conservative approach than trusting an agent’s rewrite on the strength of a code review alone.
Third-party and specialist vendors round out the toolchain: Swimm pairs static analysis with LLMs specifically for business-rule extraction and dependency mapping (the documentation step, not code rewriting), and Persistent Systems has built a multi-agent system that explicitly separates roles — a “coder” agent translates COBOL to Java, and a separate “reviewer” agent checks that output for errors and optimization opportunities before a human sees it, an architecture that mirrors the broader industry pattern of using one AI agent to generate code and a second, independent one to critique it rather than trusting a single model’s self-review.
What Independent Benchmarks Actually Show
Vendor case studies are, understandably, selective. The more useful signal comes from Factory’s LegacyBench, an independent benchmark (published by an AI coding-agent company, so its own incentives are worth keeping in mind) built specifically because existing coding benchmarks like SWE-bench and Terminal-Bench test only modern languages and don’t reflect legacy work at all. LegacyBench covers six legacy language families — COBOL (46% of tasks), Java 7 (32%), BASIC, C89, Fortran, and Assembly — across three task types: bug fixing, implementing new functionality, and migrating code to other languages.
Model / Agent
Overall Pass Rate
COBOL-Specific Result
Notable Strength / Weakness
GPT-5.3-Codex
42.5% (highest overall)
34.8%
Weak specifically on C
Gemini-3.1-Pro
38.7%
No language below 29.7%
Most balanced profile across all six languages; 81.0% on BASIC
Opus 4.6
Tied highest on Java 7 (54.2%)
18.1% (its lowest result)
34.3% on C
GLM-5
40.6% on Java 7
Not separately reported as highest/lowest
Tied-best Fortran migration score (67%); 0% on Assembly bug fixing
The headline comparison in Factory’s own announcement is the one worth sitting with: these same models score above 70% on modern-code benchmarks like Terminal-Bench 2 and SWE-bench Verified, but the best agent on LegacyBench still solves fewer than half of its legacy tasks. That gap is the honest current state of the technology — AI agents aren’t incapable of legacy code work, but they are measurably, substantially worse at it than at the modern software engineering tasks most benchmarks (and most marketing) are built around.
A Minimal Example of the Documentation-First Approach
The lower-risk, higher-maturity use case — having an AI agent explain a COBOL paragraph rather than rewrite it — looks roughly like this in practice: a short COBOL paragraph computing an interest accrual, and the kind of structured, plain-language extraction a documentation-focused tool is designed to produce from it.
COMPUTE WS-INTEREST = WS-PRINCIPAL * WS-RATE / 1200
IF WS-INTEREST > WS-MAX-INTEREST
MOVE WS-MAX-INTEREST TO WS-INTEREST
MOVE "Y" TO WS-CAPPED-FLAG
END-IF
A documentation-generation tool’s output for this snippet should read something like: “Computes monthly interest as principal times annual rate divided by 1,200 (converting an annual percentage rate to a monthly decimal amount). If the result exceeds a configured maximum, the interest is capped at that maximum and a flag is set.” That’s a comprehension task — turning code into a verifiable business-rule statement a human reviewer can check against the actual requirement — which is precisely the kind of task LegacyCodeBench and similar comprehension-focused benchmarks report much higher, more reliable scores on than autonomous rewriting tasks.
Trade-Offs
Pros: AI-assisted documentation and business-rule extraction can compress months of manual code archaeology (especially valuable as the pool of COBOL-literate engineers shrinks through retirement) into days; deterministic/parallel-run approaches like Dual Run let you validate an AI-assisted rewrite against the real production system before cutting over, rather than trusting code review alone.
Cons: independent benchmarks show current agents solving well under half of realistic legacy coding tasks autonomously, with COBOL specifically among the weaker categories for at least one leading model; vendor case studies citing speed or cost improvements are typically unquantified or self-reported, and none of the major vendors’ own modernization blog posts in our research included independently verifiable statistics for time or cost savings.
Who This Is a Good Fit For
Organizations with large COBOL estates and a shrinking pool of engineers who actually understand them are the clearest beneficiaries of the documentation and business-rule-extraction tools today — that’s the use case with the most mature tooling and the least downside risk, since nothing in production changes. Organizations in regulated industries (banking, insurance, government) that need to modernize without changing behavior should look specifically at deterministic/parallel-run approaches rather than agentic rewrites, given how much verification those regulated environments require regardless of which tool wrote the new code.
Who Should Look Elsewhere
Teams hoping to fully automate a COBOL-to-Java migration with minimal human review should treat that as a 2026-and-beyond aspiration, not a current capability — LegacyBench’s sub-50% pass rates for the best available agents are a direct, independently measured counterpoint to “fully autonomous migration” pitches. Teams without the budget or appetite for a multi-month pilot (most vendors here, including Google, explicitly structure their offering around a pilot engagement — an automated scan of one application followed by a modernization workshop) should expect this to be a longer engagement than a straightforward SaaS purchase.
Bottom Line
AI agents have made real progress on the comprehension side of legacy modernization — reading COBOL and producing documentation, dependency maps, and extracted business rules is a task where current tools are genuinely useful. Autonomous rewriting and migration is a different story: the first purpose-built independent benchmark for this exact problem shows even the best current models solving fewer than half of realistic legacy-code tasks, and specifically struggling with COBOL. The responsible way to use AI in a legacy modernization program in 2026 is to lean hard on it for understanding and documentation, use deterministic parallel-run verification wherever behavior must stay identical, and keep a human reviewer firmly in the loop for anything an agent rewrites — not to expect it to migrate your mainframe unsupervised.
FAQ
How much COBOL is actually still in use? A widely cited 2021 TechChannel survey estimate puts it at around 250 billion lines in production, a figure IBM and much of the trade press continue to reference as the current best public estimate.
Can AI agents fully automate COBOL-to-Java migration today? Not reliably, based on independent benchmark results. Factory’s LegacyBench found the best model-agent combination tested solved 42.5% of legacy coding tasks overall and 34.8% of COBOL-specific tasks, versus over 70% on modern-code benchmarks like SWE-bench Verified for the same models.
What’s the safest way to start a COBOL modernization effort with AI? Begin with AI-assisted code comprehension and documentation — extracting business rules and dependency maps from existing code — rather than autonomous rewriting. This is the most mature, lowest-risk application of the technology and doesn’t touch production behavior.
What is “Dual Run” and why does it matter? It’s Google Cloud’s approach to deterministic modernization: running the same production workload on both the old mainframe and the new target environment simultaneously and comparing outputs until they’re proven equivalent, rather than relying on code review alone to catch behavioral differences introduced during a rewrite.
Does using AI mean a company can get rid of its mainframe? Not necessarily, and IBM explicitly argues the opposite for its own customers — that AI-assisted modernization increases the value of keeping workloads on Power/Z systems by adding new AI-driven capability to them, rather than being primarily a tool for migrating off the platform.
Uptime monitoring is one of the cheapest insurance policies a website owner can buy — a few dollars a month to find out your site is down before a customer tells you. UptimeRobot, Pingdom, and Better Stack all do the core job (ping your site, alert you when it fails), but they price and package that job very differently in 2026. Here’s what each one’s own pricing page actually shows.
At a Glance
Spec
UptimeRobot
Pingdom
Better Stack
Free plan
Yes — 50 monitors, 5-min checks, 1 status page
14-day free trial only, no permanent free tier
Yes — 10 monitors/heartbeats, 1 status page
Entry paid price
Solo: $13/mo ($12/mo annual)
Usage-based via a quantity calculator; no fixed published tier
Responder license: $34/mo ($29/mo annual)
Fastest check interval
15 seconds (Scale plan)
Not published; configurable via the quote calculator
30 seconds (uptime), 1 second (heartbeats)
Best for
Budget-conscious teams wanting fast checks without a quote call
Teams that also want page-speed and real-user monitoring bundled in
Teams that want monitoring, incidents, on-call, and status pages in one product
Short Verdict
UptimeRobot is the simplest, most transparently priced of the three — every tier’s price and limits are on one page, with no sales call required even at the Team or Scale level. Pingdom (now part of SolarWinds) is the odd one out: its public pricing page has moved to a quantity-based calculator with no fixed, published dollar amount for a given tier, which makes it harder to budget for sight-unseen, though it’s the only one of the three with built-in page-speed and real-user monitoring alongside uptime checks. Better Stack is the best fit if you want monitoring bundled with incident response, on-call scheduling, and status pages under one roof rather than stitched together from separate tools — its base Responder license plus monitor add-ons is more of an à la carte model than UptimeRobot’s flat tiers.
What Each Tool Is
UptimeRobot is a dedicated uptime and status-page monitoring tool: HTTP, port, ping, keyword, API, UDP, DNS, and SSL/domain-expiry checks, with alerting through email, SMS, and integrations like Slack and PagerDuty. It’s built to be self-serve end to end — every plan’s price, check interval, and monitor count is listed plainly on its pricing page.
Pingdom, owned by SolarWinds, splits its product into Synthetic Monitoring (the classic uptime/transaction/page-speed checks) and Real User Monitoring (RUM, which measures actual visitor traffic rather than running scheduled checks). Both are sold through quantity-based sliders on Pingdom’s pricing page — you pick a tier of uptime checks, advanced checks, and SMS credits, or a tier of monthly pageviews for RUM — rather than choosing from a short list of named plans with fixed prices.
Better Stack bundles uptime and heartbeat monitoring with incident management, on-call scheduling, and status pages into one connected product, rather than selling monitoring as a standalone SKU. Its pricing is built around a paid “Responder” license (which unlocks the full incident/on-call/status-page toolkit) plus separate add-ons for extra monitors, heartbeats, and status page features.
Pricing Breakdown
Plan
Price
Key limits
UptimeRobot Free
$0
50 monitors, 5-min checks, 1 basic status page, 3 months data retention
UptimeRobot Solo
$13/mo monthly, $12/mo annual
60-sec checks, 3 status pages with own domain, 12 months retention
Tiers from 10 up to 30,000 uptime checks, plus separate advanced-check and SMS allowances
Pingdom Real User Monitoring
Usage-based via calculator, not fixed-listed
Tiers from 100K up to 1B+ monthly pageviews
Better Stack Free
$0
10 monitors/heartbeats, 1 status page, Slack/email alerts
Better Stack Responder license
$34/mo monthly, $29/mo annual
Incidents, on-call, monitoring, status pages; unlimited phone/SMS alerts; unlimited team members
Better Stack add-on: +50 uptime monitors
$25/mo monthly, $21/mo annual
Stacks on top of the Responder license
Better Stack add-on: extra status page
$15/mo monthly, $12/mo annual
1 included free; each additional page is billed separately
Worth being direct about: Pingdom’s own pricing page no longer publishes fixed dollar figures for named tiers — it’s an interactive calculator with quantity sliders for uptime checks, advanced checks, SMS, and RUM pageviews, and the specific price depends on where you set those sliders. We’re not able to quote a single “Pingdom costs $X/month” figure because Pingdom itself doesn’t publish one; use its calculator or talk to SolarWinds sales for an exact number before comparing against UptimeRobot’s or Better Stack’s flat tiers.
Pros and Cons
UptimeRobot
Pros: fully transparent, self-serve pricing at every tier; generous free plan (50 monitors); fast 15-second checks on Scale without needing an Enterprise quote.
Cons: no built-in real-user monitoring or page-speed testing the way Pingdom offers; the jump from Solo to Team (roughly 3x) is steep if you only need slightly more than 10 monitors.
Pingdom
Pros: the only one of the three with native Real User Monitoring alongside synthetic uptime checks; transaction and page-speed monitoring is more mature than either competitor’s.
Cons: no fixed, published price for a given tier — you have to use the calculator or talk to sales to know what you’ll actually pay; no permanent free plan, only a time-limited trial.
Better Stack
Pros: bundles monitoring with incidents, on-call, and status pages so you’re not paying for three separate tools; unlimited team members on the paid Responder license; sub-second heartbeat checks.
Cons: à la carte add-on pricing (extra monitors, extra status pages, white-labeling) can add up quickly compared with UptimeRobot’s simpler flat tiers; the base Responder license is priced around incident response, not monitoring alone, so a team that only wants uptime checks may be paying for more than it needs.
Who It’s a Good Fit For
Choose UptimeRobot if you want simple, fast, transparently priced uptime and status-page monitoring with no sales call.
Choose Pingdom if you also need real-user and page-speed monitoring and don’t mind using a calculator or talking to sales to get an exact price.
Choose Better Stack if your team wants monitoring tied directly into incident response, on-call rotations, and status pages, not just a ping-and-alert tool.
Who Should Look Elsewhere
A team that already runs a full observability platform for logs, metrics, and traces may find uptime-only monitoring redundant — see our Datadog vs Grafana Cloud vs New Relic comparison if synthetic checks are just one piece of a bigger monitoring need. Anyone who specifically needs Pingdom’s exact cost locked in before budgeting should not treat the figures here as final — only its own calculator or a sales conversation will give a firm number.
Bottom Line
For most small sites and solo site owners, UptimeRobot’s flat, published pricing and generous free tier make it the easiest starting point. Pingdom earns its place specifically when real-user and page-speed monitoring matter as much as basic uptime — just budget time to run its pricing calculator rather than expecting a sticker price. Better Stack is the strongest pick when monitoring needs to plug directly into how your team actually responds to incidents, not just detect that something broke.
FAQ
How much does Pingdom actually cost per month?
Pingdom no longer lists fixed per-tier prices on its public pricing page — it uses an interactive calculator where you select quantities of uptime checks, advanced checks, SMS credits, or RUM pageviews, and the price is calculated from those selections. There’s no single published number to quote; use the calculator on pingdom.com or contact sales for your specific configuration.
Which of these three has the fastest check interval?
Better Stack’s heartbeat monitoring supports up to 1-second check resolution, the fastest of the three for that specific feature. For standard uptime checks, UptimeRobot’s Scale plan offers 15-second checks, and Better Stack’s uptime monitoring goes down to 30 seconds. Pingdom doesn’t publish a specific check-interval figure on its pricing page.
Do any of these offer a permanent free plan?
UptimeRobot and Better Stack both offer permanent free tiers (50 monitors and 10 monitors/heartbeats respectively, with no credit card required). Pingdom offers only a 14-day free trial, with no permanent free tier.
Is Better Stack’s Responder license required just to monitor uptime?
No — Better Stack’s free plan includes basic uptime monitoring and heartbeats without a paid license. The $34/mo ($29/mo annual) Responder license is what unlocks the full incident management, on-call, and unlimited phone/SMS alerting features on top of monitoring.
Before you can optimize a page’s conversion rate, you need to see how people actually use it — where they click, how far they scroll, and where they get stuck. Hotjar, Microsoft Clarity, and FullStory have long been the three most-recommended tools for exactly that: heatmaps and session replay. But one major thing changed in this category that a lot of comparison articles haven’t caught up to yet — Hotjar, as an independent product, doesn’t really exist anymore.
At a Glance
Tool
Free plan
Entry paid price
Session replay on free tier
Best for
Hotjar (now Contentsquare)
200,000 sessions/month, 1 month data, 1 project
Growth from $39/month (shown discounted from $49)
Yes — 5% of sessions, max 10,000, 1 month access
Teams fine with Hotjar’s identity and features living on inside a larger Contentsquare platform
Microsoft Clarity
Free forever, no traffic cap stated
None — there is no paid tier
Yes, included in the free product
Anyone who wants heatmaps and session recordings at zero cost with no catch
FullStory
30,000 sessions/month, 12 months retention, up to 10 users
Custom quote only (Business/Advanced/Enterprise analytics tiers)
Yes, included in FullStoryFree
Teams that outgrow a basic heatmap tool and need deeper product analytics, dashboards, and AI-assisted insight (StoryAI)
Short Verdict
Microsoft Clarity is the easiest recommendation if budget is the main concern: it’s genuinely free with no stated traffic cap and no paid tier gating features behind a paywall. Hotjar’s identity has been absorbed into Contentsquare — new accounts can no longer even be created on hotjar.com — and the resulting Contentsquare Free plan is actually more generous on session volume than Hotjar’s old free plan ever was, which is a rare case of a product getting better specs after being acquired. FullStory remains the deepest tool of the three once you move past simple heatmaps into full product analytics, debugging, and AI-assisted session insight, but every paid tier requires a sales conversation rather than a published price.
What Each One Actually Is (and the Hotjar/Contentsquare Change)
Here’s the detail worth leading with: Contentsquare’s own page confirms that “Hotjar is now Contentsquare,” that “the two platforms have merged into a single, more powerful experience intelligence platform,” and explicitly states “it’s no longer possible to create a new account on Hotjar.” Visiting hotjar.com now redirects directly to a Contentsquare landing page, and hotjar.com/pricing redirects straight to contentsquare.com/pricing. Existing Hotjar customers log in through Contentsquare’s own login page. Practically, this means a 2026 “Hotjar” comparison is really a Contentsquare comparison — the Hotjar brand survives mainly as a product-line name (heatmaps and session replay now sit under Contentsquare’s “Experience Analytics” product) rather than as a separate company or a separately purchasable product.
Contentsquare’s Experience Analytics (the direct descendant of Hotjar) offers a free tier with 200,000 monthly sessions, one month of data access, one project, and replays, heatmaps, and funnels included. That’s a significant jump from Hotjar’s old free plan, which Contentsquare’s own page describes as having capped out at 35 sessions per day and 20 survey responses per month. The paid Growth tier starts at $39/month (shown marked down from $49) and scales with session volume up into the 240,000+/month range, adding 13 months of data access, 3 projects, and zone-based heatmaps. Pro and Enterprise tiers require a demo and custom pricing.
Microsoft Clarity is Microsoft’s free user-behavior analytics tool, offering heatmaps, session recordings, and dashboards. Its own pricing page headline is simply “It’s free, forever,” and its homepage states it’s “built to grow with your business” with “no limits on traffic.” There’s no paid tier, no feature gate, and no session cap stated anywhere we could find on Microsoft’s own pages — a genuinely unusual position in this category, where every other major competitor monetizes through session-volume limits.
FullStory takes the opposite approach from Clarity: a capable permanent free plan (FullStoryFree) as the entry point, with every meaningful upgrade path routed through a sales conversation rather than a published price. FullStoryFree includes 30,000 sessions per month, 12 months of data retention, up to 10 users, Session Replay, basic analytics, and debugging tools — notably more generous retention than either Hotjar’s old or new free tiers. Paid analytics tiers (Business, Advanced, Enterprise) all require requesting a demo, as do its separate Workforce (internal tool-adoption analytics) and Anywhere (data warehouse/activation) products.
Pricing Breakdown
Product
Plan
Price
Key limits/inclusions
Contentsquare (Hotjar)
Free
$0/month, forever
200,000 sessions/mo, 1 month data, 1 project, replays/heatmaps/funnels included
Form analysis, higher session replay capture (up to 100%), advanced features
Microsoft Clarity
Free (only tier)
$0, forever
No stated traffic limit; heatmaps, session recordings, dashboards
FullStory
FullStoryFree
$0/month
30,000 sessions/mo, 12 months retention, up to 10 users; Session Replay, basic analytics, debugging
FullStory
Business / Advanced / Enterprise
Custom quote only — “Request pricing & demo”
Dashboards, StoryAI, deeper product analytics; exact feature gating by tier not published
Pros
Hotjar/Contentsquare: A free tier that’s now more generous than Hotjar’s standalone free plan ever was, plus a published, if higher, Growth starting price for teams that outgrow it.
Microsoft Clarity: Genuinely free with no session cap stated anywhere on Microsoft’s own pages — the only tool of the three with zero pricing friction at any scale.
FullStory: The most generous free-tier data retention (12 months) of the three, plus the deepest paid feature set once you need product analytics and AI-assisted insight (StoryAI) rather than just heatmaps.
Cons
Hotjar/Contentsquare: Existing Hotjar users are now Contentsquare customers whether they chose that transition or not — “no longer possible to create a new account on Hotjar” means the standalone product is effectively gone.
Microsoft Clarity: Being free means no dedicated account manager, enterprise SLA, or the deeper product-analytics and AI features that paid competitors like FullStory offer.
FullStory: Every paid tier is hidden behind “contact sales,” so there’s no way to self-serve budget for an upgrade the way Contentsquare’s published Growth price allows.
Who It’s a Good Fit For
Pick Microsoft Clarity if you want heatmaps and session recordings with zero budget approval needed and don’t require enterprise support or deep product analytics. Pick Contentsquare (what used to be Hotjar) if you want a free tier with generous session volume and a clear, published path to a paid plan as you grow. Pick FullStory if you’re past basic heatmaps and need genuine product analytics, long data retention, and are prepared to go through a sales conversation to get there.
Who Should Look Elsewhere
If you specifically want the standalone “Hotjar” product and brand as it existed a few years ago, that option no longer exists — you’ll be a Contentsquare customer either way, so evaluate the merged platform on its current merits rather than Hotjar’s old reputation. Teams that want transparent, self-serve pricing at every tier (not just the entry tier) should be cautious with FullStory, since nothing beyond its free plan is published.
Bottom Line
The most important finding in this comparison isn’t a pricing detail — it’s that “Hotjar” as an independently branded, independently purchasable product is gone, folded into Contentsquare’s Experience Analytics line as of this research. For most people comparing heatmap tools for CRO work in 2026, the realistic three-way choice is: free-forever with no frills (Microsoft Clarity), free-with-a-generous-paid-upgrade-path (Contentsquare/Hotjar), or free-to-start-then-sales-gated-for-everything-else (FullStory). None of the three is a wrong choice, but go in knowing which of those three trade-offs you’re actually signing up for.
FAQ
Is Hotjar still a separate product from Contentsquare? No. Contentsquare’s own page states the two platforms have merged, and new accounts can no longer be created directly on hotjar.com — hotjar.com now redirects to Contentsquare.
Is Microsoft Clarity really free with no catch? Based on Microsoft’s own pricing and homepage copy (“It’s free, forever,” “no limits on traffic”), yes — there is no paid tier at all for Clarity.
Does FullStory have any published pricing beyond the free plan? No — every tier above FullStoryFree (Business, Advanced, Enterprise, plus the separate Workforce and Anywhere products) requires requesting a demo and custom quote.
Which has the most generous free tier by session volume? Contentsquare’s current free plan, at 200,000 sessions/month, well above FullStory’s 30,000/month — though Microsoft Clarity’s free tier has no stated session cap at all, which arguably makes it the most generous by that specific measure.
Which has the longest data retention on its free plan? FullStoryFree, at 12 months, versus 1 month on Contentsquare’s free tier.
Verifying that a large piece of data hasn’t been tampered with usually means re-checking all of it — unless you can summarize that data into a single, small value that changes the instant anything underneath it changes. That’s exactly what a Merkle tree does: a binary tree of hashes where every leaf hashes a piece of data, every parent hashes its children, and a single root hash at the top stands in for the integrity of everything below it. The idea predates the modern internet — it comes from a 1979 patent by cryptographer Ralph Merkle — and it now quietly verifies every Git commit, every Bitcoin block, and large portions of how distributed databases detect when replicas have drifted apart.
At a Glance
Attribute
Detail
What it is
A tree of hashes where each leaf hashes a data block and each parent hashes the concatenation of its children
What the root proves
A single value that summarizes every leaf — changing any leaf changes the root
Verification cost
O(log n) hashes to prove one leaf belongs, instead of re-checking all n leaves
Ralph C. Merkle, US Patent 4,309,569, “Method of providing digital signatures,” filed September 5, 1979
Short Verdict
A Merkle tree solves one specific problem extremely well: proving a piece of data belongs to a larger, already-agreed-upon set without transmitting or re-checking the whole set. Git uses that property to detect the tiniest change anywhere in a repository’s history from a single commit hash. Bitcoin uses it so a lightweight client can verify one transaction is in a block without downloading the entire block. Distributed databases use it to compare two replicas’ entire datasets by comparing a handful of hashes instead of every row. If what you actually need is a plain checksum of one file, a Merkle tree is overkill — its value shows up specifically when you need to verify or compare a large, structured collection of things cheaply and incrementally.
How a Merkle Tree Works
Ralph Merkle’s 1979 patent, “Method of providing digital signatures,” filed September 5, 1979 and granted January 5, 1982, describes the construction directly: a binary tree of one-way function values, where each leaf is the one-way function (a hash) applied to one data item, and each parent node is computed by applying the one-way function to its two children. The topmost value — the root — summarizes every leaf beneath it, and the patent’s point is that only this single root value needs to be authenticated or stored; everything else can be regenerated or supplied on demand.
Verifying that one specific leaf belongs under a given root doesn’t require the whole tree. The patent describes sending just that leaf’s value along with the sibling values on the path from its leaf up to the root — what it calls the “authentication path.” The verifier recomputes the hashes along that path and checks the result matches the already-trusted root. For n total leaves, that path has about log₂ n values, which is why verifying one item in a million-leaf tree takes roughly 20 hash computations, not a million.
A Minimal Merkle Tree in Python
This builds a tree bottom-up from a list of data blocks and generates an authentication (Merkle) proof for one leaf — the two operations that matter in practice.
import hashlib
def h(data):
return hashlib.sha256(data).digest()
def build_tree(leaves):
"""Return every level of the tree, leaves first, root last."""
level = [h(leaf) for leaf in leaves]
levels = [level]
while len(level) > 1:
if len(level) % 2 == 1:
level = level + [level[-1]] # duplicate the odd one out
next_level = [h(level[i] + level[i + 1]) for i in range(0, len(level), 2)]
levels.append(next_level)
level = next_level
return levels
def merkle_proof(levels, index):
"""Sibling hashes needed to verify the leaf at `index` against the root."""
proof = []
for level in levels[:-1]:
sibling_index = index ^ 1 # flip the last bit to get the sibling
sibling_index = min(sibling_index, len(level) - 1)
proof.append(level[sibling_index])
index //= 2
return proof
def verify_proof(leaf, index, proof, root):
current = h(leaf)
for sibling in proof:
if index % 2 == 0:
current = h(current + sibling)
else:
current = h(sibling + current)
index //= 2
return current == root
blocks = [b"tx1", b"tx2", b"tx3", b"tx4", b"tx5"]
levels = build_tree(blocks)
root = levels[-1][0]
proof = merkle_proof(levels, 2) # prove "tx3" belongs
print(verify_proof(b"tx3", 2, proof, root)) # True
print(verify_proof(b"tx9", 2, proof, root)) # False -- tampered data fails
The proof list is exactly the “authentication path” from Merkle’s patent: a handful of sibling hashes that let any verifier recompute the root from a single leaf without ever seeing the other leaves’ contents.
Real-World Uses
Git’s object model is a Merkle structure even though Git’s own documentation doesn’t use that term. Per the Git Internals chapter of the official Pro Git book, Git stores three object types: blobs (raw file contents, no filename), trees (directory entries — mode, type, SHA-1, and filename — each pointing to a blob or another tree), and commits (a pointer to one top-level tree, plus parent commit(s), author, and message), all addressed by the SHA-1 hash of their own content. Because a tree’s hash is computed from the hashes of the blobs and subtrees it contains, and a commit’s hash is computed from its tree’s hash plus its parent’s hash, changing a single byte in any file changes that file’s blob hash, which changes its containing tree’s hash, which changes every commit hash built on top of it. That’s the Merkle-tree guarantee in practice: Git’s content-addressable object graph makes silent tampering with repository history detectable by comparing hashes, not by re-diffing entire file trees.
Bitcoin’s own whitepaper, Section 7, states the mechanism explicitly: “transactions are hashed in a Merkle Tree, with only the root included in the block’s hash.” Pairs of transaction hashes are combined into intermediate hashes, which combine up to a single Merkle root that goes into the block header. Section 8, “Simplified Payment Verification,” builds directly on this: a lightweight client that only stores block headers can request a “Merkle branch” — the same authentication path Merkle’s patent describes — linking one transaction to the block that contains it, without downloading or verifying every other transaction in that block.
Distributed databases use the same structure for a different purpose: detecting divergence between replicas cheaply. Rather than comparing every row between two copies of a dataset, a database can build a Merkle tree over each replica’s data and compare just the root hashes first — if they match, the replicas are identical; if not, walking down to the mismatched subtree pinpoints exactly which range of data differs, without transferring the rest. This “anti-entropy” repair pattern, used in systems like Amazon’s Dynamo and Apache Cassandra, turns an O(n) full-dataset comparison into an O(log n) walk down the branches that actually disagree.
This connects naturally to two other structures covered on this site: the per-node hashing in a Merkle tree is a direct application of the hashing ideas behind consistent hashing, and the anti-entropy comparison pattern above is the same kind of “summarize before you check” trick that a Bloom filter uses to skip unnecessary disk reads.
Merkle Trees vs. Plain Hashing
Factor
Single Hash of Everything
Merkle Tree
Verifying one item belongs
Requires the entire dataset to recompute the hash
Requires only O(log n) sibling hashes (the authentication path)
Detecting what changed
Tells you something changed, not what or where
Walking down from a mismatched node narrows down exactly which leaf differs
Comparing two large datasets
Must compare everything, or trust a single top-level hash with no further detail
Compare roots first, then walk down only the branches that disagree
Update cost
Entire hash must be recomputed from scratch
Only the path from the changed leaf to the root needs recomputation
Trade-offs
Overhead for small datasets: building and maintaining a tree structure is unnecessary complexity if you only ever need to checksum one small blob.
Security depends entirely on the underlying hash function: a Merkle tree’s guarantees are only as strong as collision resistance in the hash it uses (Git’s historical use of SHA-1, for instance, is why the project has worked on a transition to SHA-256).
Odd leaf counts and tree shape require a defined convention (as in the duplicate-last-leaf handling above), and different systems make different choices here, which means two systems’ root hashes for conceptually “the same” data aren’t necessarily comparable unless they use identical construction rules.
Big win for incremental verification and comparison: proving membership or detecting a specific point of divergence costs O(log n) instead of O(n), which is the entire reason it’s used in Git, Bitcoin, and distributed-database repair.
Bottom Line
Ralph Merkle’s 1979 construction solved a narrow problem — authenticating one item against a large, already-trusted set cheaply — and that narrow solution turned out to generalize extraordinarily well. Git uses it to make its entire commit history tamper-evident from a single hash. Bitcoin uses it so lightweight clients can verify a transaction without trusting or downloading a full block. Distributed databases use it to find exactly where two replicas diverge without comparing every row. In every case, the appeal is the same: a small, fixed-size summary (the root) that changes the instant anything underneath it changes, paired with a logarithmic-cost way to prove or disprove that a specific piece of data belongs under that summary.
FAQ
Is a Merkle tree the same thing as a hash tree? Yes — “Merkle tree” and “hash tree” are used interchangeably for this structure; the name credits Ralph Merkle’s 1979 patent describing it.
Does Git actually call its object model a Merkle tree? Git’s own documentation describes blobs, trees, and commits linked by content-derived SHA-1/SHA-256 hashes without using the term “Merkle tree,” but the structure it describes — parent hashes derived from child hashes, all the way up to a single commit hash — matches Merkle’s construction exactly.
How does Bitcoin’s Merkle root make “lightweight” clients possible? Per the Bitcoin whitepaper’s Section 8, a client that only stores block headers (which include the Merkle root) can request a short “Merkle branch” proving one transaction is included in a block, without downloading or verifying every other transaction in it.
Why do databases use Merkle trees for replica repair instead of just comparing all the data? Comparing two full datasets row by row is expensive at scale. Comparing Merkle tree roots first, then walking down only the branches whose hashes disagree, finds the actual point of divergence in roughly logarithmic time instead of linear time.
Playwright, Cypress, and Selenium are all free, open-source browser automation frameworks — none of them charge for the core testing tool itself. So “pricing” in this comparison isn’t about license fees; it’s about the optional cloud services each ecosystem offers for running tests at scale, plus the real cost of engineering time each framework demands. In 2026, Playwright has become the default recommendation for new projects, Cypress remains a strong developer-experience choice for teams already invested in it, and Selenium is still the only one of the three with first-class support across virtually every language and browser combination in existence.
At a Glance
Framework
Core Tool Cost
Cloud/Scaling Cost
Best For
Key Specs
Playwright
Free, open source (Microsoft)
Playwright Workspaces (Azure): consumption-based, billed per minute of cloud browser time; 100 free test minutes on a 30-day trial
New projects wanting modern, fast, multi-browser E2E testing with strong auto-waiting and parallelization built in
Native support for Chromium, Firefox, and WebKit; official bindings for JavaScript/TypeScript, Python, Java, and .NET
Cypress
Free, open source core
Cypress Cloud: Free Starter tier; Team $799/year (~$67/mo); Business $3,199/year (~$267/mo); Enterprise custom
Teams that prioritize developer experience, time-travel debugging, and an opinionated, batteries-included test runner
JavaScript/TypeScript only; runs inside the browser’s run loop; Chromium family plus Firefox and experimental WebKit
Selenium
Free, open source (no paid tier at all)
No official Selenium cloud product; third-party grids like BrowserStack, Sauce Labs, or LambdaTest are separate paid services
Teams needing the broadest language/browser support, real legacy-browser testing, or strict vendor-neutral, standards-based automation
W3C WebDriver + newer WebDriver BiDi protocol support; official bindings for Java, Python, C#, Ruby, JavaScript, and Kotlin
Short Verdict
For a brand-new end-to-end test suite in 2026, Playwright is the easiest default to recommend: it’s free, fast, auto-waits for elements without flaky manual sleeps, and tests real engine coverage (Chromium, Firefox, and WebKit/Safari) out of the box in any of four languages. Cypress is still an excellent choice if your team is JavaScript-only and values its debugging experience and Cypress Cloud’s dashboard — but you’ll likely pay for Cypress Cloud once you outgrow the free Starter tier’s 500 monthly test results. Selenium remains essential when you need language flexibility beyond JS/Python/Java/.NET, must test against real, specific legacy browser versions, or want a vendor-neutral, W3C-standard protocol that isn’t tied to any single company’s roadmap.
What Each One Is
Playwright is Microsoft’s open-source browser automation framework, built by many of the same engineers who originally built Google’s Puppeteer. It controls browsers through each engine’s own remote-debugging protocol rather than the W3C WebDriver spec, which is part of why it can automate Chromium, Firefox, and WebKit (Safari’s engine) with one unified API. Its signature features are auto-waiting (actions wait for elements to be actionable before executing, cutting down on flaky timing-based failures), built-in parallelization across workers, browser contexts that act like isolated incognito sessions for fast test isolation, and a trace viewer that records a full timeline — DOM snapshots, network, console — for debugging failed runs after the fact.
Cypress takes a different architectural approach: instead of driving the browser externally, the Cypress test runner executes inside the same run loop as the application under test, in the browser itself. That gives it tight, fast access to the DOM and network layer and powers its well-regarded time-travel debugging (hovering over a command in the Command Log shows a DOM snapshot at that exact point in the test). The trade-off is that this architecture historically limited Cypress to Chromium-family browsers and Firefox, with WebKit support still experimental; it’s also JavaScript/TypeScript-only, with no official Python, Java, or C# bindings.
Selenium is the oldest of the three (its WebDriver component dates to the mid-2000s) and the only one built around an open, vendor-neutral standard: the W3C WebDriver protocol, which browser vendors themselves help maintain. Selenium 4 added native WebDriver BiDi (bidirectional) protocol support, closing much of the capability gap with Playwright and Cypress for things like network interception and real-time browser events, and an updated Selenium Grid for distributing tests across machines. Selenium’s biggest practical advantage is breadth: official language bindings for Java, Python, C#, Ruby, JavaScript, and Kotlin, and the ability to drive real, specific versions of virtually any browser that ships a WebDriver-compatible driver — including older enterprise browser versions Playwright and Cypress don’t target.
A Quick Code Comparison
The same basic test — load a page, click a button, assert on resulting text — looks like this in each framework’s default JavaScript/TypeScript style:
Playwright’s and Cypress’s locator APIs (getByRole, cy.contains) favor resilient, user-facing selectors by default; raw Selenium code more often reaches for XPath or CSS selectors directly, though Selenium 4’s relative locators (RelativeLocator.with(...)) narrow that gap if you use them deliberately.
Pricing Breakdown
Plan
Price
Notes
Playwright (core framework)
$0
Apache 2.0 license; self-host and run anywhere
Playwright Workspaces (Azure cloud browsers)
Billed per minute, consumption-based, region-dependent rate not published as a flat figure
30-day free trial includes 100 test minutes; use the Azure pricing calculator for a rate specific to your region
Cypress core
$0
MIT license; self-host and run anywhere, including fully offline
Cypress Cloud Starter
$0
Up to 10 users, 500 test results/month, 100 AI “prompt executions”/month, 30-day data retention
Cypress Cloud Team
$799/year (~$67/month)
Up to 50 users, 120,000 test results/year, 9,000 prompt executions/year, 90-day retention, Flake Detection and Jira integration
Cypress Cloud Business
$3,199/year (~$267/month)
Adds Spec Prioritization, Auto Cancellation, Re-run Optimization, SSO
Cypress Cloud Enterprise
Custom
Unlimited users, 1.8M test results/year, premium support
Selenium (framework + Grid)
$0
Apache 2.0 license; no official paid tier of any kind
Third-party clouds for Selenium (BrowserStack, Sauce Labs, LambdaTest, etc.)
Varies by vendor
Separate commercial products, not part of the Selenium project itself — pricing and features vary widely and should be evaluated independently
Pros and Cons
Playwright
Pros: true multi-engine coverage (Chromium, Firefox, WebKit) in one API; strong auto-waiting reduces flakiness; built-in parallel test execution and a genuinely useful trace viewer; multi-language support
Cons: younger ecosystem than Selenium’s, so some niche enterprise integrations and legacy-browser scenarios are better covered elsewhere; its own cloud offering (Playwright Workspaces) is a newer, Azure-specific product rather than a mature, long-established dashboard
Cypress
Pros: excellent developer experience and debugging (time-travel, real-time reloads); Cypress Cloud’s free Starter tier is genuinely usable for small teams; large existing plugin ecosystem
Cons: JavaScript/TypeScript only; browser engine support is narrower than Playwright’s (WebKit remains experimental); its in-browser architecture makes certain multi-tab and cross-origin scenarios harder than in Playwright
Selenium
Pros: broadest language support of the three; vendor-neutral W3C standard with no single company steering its roadmap; the only realistic choice for testing against many specific legacy or niche browser versions; enormous existing enterprise adoption and tooling
Cons: no built-in auto-waiting (you write explicit waits or risk flaky tests); slower out-of-the-box developer experience than Playwright or Cypress; running tests at scale requires either self-managing Selenium Grid or paying a third-party cloud vendor, since there’s no first-party Selenium cloud
Who It’s a Good Fit For
Choose Playwright for new projects, polyglot teams, or anyone who wants real cross-engine (including WebKit/Safari) coverage without juggling multiple tools.
Choose Cypress if your team is all-in on JavaScript/TypeScript and values its debugging workflow and dashboard more than broad browser-engine coverage.
Choose Selenium if you need non-JS language bindings (Java, Python, C#, Ruby), must test specific legacy browser versions, or want a standards-based tool with no single vendor’s commercial interests attached to its core roadmap.
Who Should Look Elsewhere
Teams that need to automate truly old or niche browsers (certain enterprise intranet environments still standardize on older engines) should stick with Selenium rather than Playwright or Cypress, neither of which targets that use case. Teams wanting a single-vendor, all-in-one commercial platform (test management, reporting, and execution in one subscription) may find all three frameworks are really just the execution layer and should budget for an additional reporting/orchestration product regardless of which one they pick. And teams specifically needing non-English-language or mobile-native app testing (rather than mobile web) should look beyond all three to dedicated mobile automation tools like Appium, which is a separate project despite sharing WebDriver heritage with Selenium.
Bottom Line
None of these three tools cost anything to start using, so the real decision is architectural fit, not budget. Playwright has the strongest claim to being the modern default in 2026 thanks to genuine multi-engine support and low-flakiness design; Cypress remains a well-loved, JS-only option with a mature paid cloud dashboard once you need one; and Selenium, despite being the oldest of the three, is still indispensable wherever language breadth, legacy-browser coverage, or vendor neutrality matter more than out-of-the-box developer experience.
FAQ
Is Playwright free? Yes, the core Playwright framework is completely free and open source (Apache 2.0). Microsoft’s optional Playwright Workspaces cloud service, for running tests on managed cloud browsers, is billed separately on a consumption basis.
Does Cypress support languages other than JavaScript? No — Cypress tests are written in JavaScript or TypeScript only. There are no official Python, Java, or C# bindings, unlike Playwright and Selenium.
Is there an official Selenium cloud service? No. The Selenium project itself offers only the free, self-hosted Selenium Grid for distributing tests across machines. Commercial cloud grids (BrowserStack, Sauce Labs, LambdaTest, and others) are independent third-party products built on top of WebDriver, not part of the Selenium project.
Can Playwright and Selenium both test Safari? Playwright tests against WebKit, the open-source engine Safari is built on, which is a close but not pixel-for-pixel identical proxy for real Safari. Selenium can drive real Safari on macOS directly via Apple’s own SafariDriver, which is a meaningfully different guarantee for teams that need to validate against the actual shipping browser.
Which one is fastest? Benchmarks vary by test suite and are easy to design unfairly in either direction, so we’re not citing a specific head-to-head number here. In general, Playwright’s and Cypress’s tighter integration with the browser (versus Selenium’s WebDriver round-trips) tends to produce faster raw execution, while Selenium’s overhead is more noticeable on large suites run without Grid-based parallelization.
A family password manager is a different buying decision than a personal one: the question isn’t just “is the vault secure,” it’s “can my partner recover their account at midnight, can I give my teenager their own login without seeing my own passwords, and what happens the day someone loses their phone.” 1Password, Dashlane, and NordPass all sell a dedicated multi-person family plan, and all three structure that plan differently around member counts, shared access, and recovery. This comparison is specifically about those family/personal multi-user plans — not the business or team tiers these same vendors sell, and not passkey/passwordless platforms, which are a separate category covered elsewhere on this site.
At a Glance
Password Manager
Family plan price
Members included
Free plan?
Best for
1Password Families
$4.49/mo billed annually (promo, first 12 months); $5.99/mo regular
Up to 5 family members
No (14-day free trial instead)
Households wanting organizer-assisted account recovery and guest vault sharing
Dashlane Friends & Family
Reported around $7.49/mo, billed annually (see pricing note below)
Up to 10 members
No (Dashlane discontinued its free plan; 14-day trial on paid plans)
Larger households or friend groups wanting the highest member count
NordPass Family
$3.69/mo billed annually (1-year plan)
Up to 6 members
Yes, a permanent single-user Free plan exists (not a family feature)
Budget-conscious families wanting the lowest per-month cost
A Note on Pricing Verification
1Password’s own pricing page gave us a clean, direct figure for Families. Dashlane’s and NordPass’s own marketing pages, however, render their pricing dynamically and partly blocked automated access during our research, so for those two we cross-checked independent, third-party price-tracking sources instead of pulling the number directly off the vendor’s page. For NordPass, two independent trackers agreed on the 1-year Family price ($3.69/month) but disagreed on the discounted 2-year rate ($2.79/month vs. $2.32/month) — since those two sources conflict, we’re reporting only the 1-year figure both agree on and leaving the multi-year promotional rate out. For Dashlane, we have one third-party source (security.org) citing $7.49/month for Friends & Family; the structural details that source gave (10 members, “VPN for the plan manager only,” no built-in dark web monitoring) matched what we could independently confirm on Dashlane’s own site, which gives us reasonable confidence in that figure, but we’re flagging it as not pulled directly from Dashlane’s own displayed price. Always confirm the live price on each vendor’s checkout page before buying, since promotional pricing changes frequently.
Short Verdict
1Password Families is the strongest pick if account-recovery mechanics matter to you: a family organizer can recover a locked-out member’s account, members can generate their own recovery codes, and an Emergency Kit exists as a last-resort fallback — a genuinely thought-through answer to “what if someone forgets their master password.” Dashlane’s Friends & Family plan covers the most people (up to 10) at the highest price of the three, which makes it a reasonable fit for an extended family or a friend group splitting the cost, provided you don’t need built-in dark web monitoring, which its comparison table doesn’t list for that tier. NordPass Family is the value play: the lowest confirmed monthly price of the three, for 6 members, from a company (Nord Security) that also sells NordVPN and NordLocker if you want to consolidate subscriptions with one vendor.
What Each One Actually Is
1Password Families, per 1Password’s own pricing page, includes up to 5 family members, unlimited shared vaults, 5 guest accounts for sharing with people outside the family plan, and 1GB of document storage per user. Family-specific recovery is handled through 1Password’s own support documentation: a designated family organizer can recover another member’s account if they’re locked out, members can generate personal recovery codes as a self-service option, and an Emergency Kit (a printable document holding your account details) is the fallback if every organizer is locked out simultaneously. 1Password explicitly recommends naming more than one organizer, since an organizer cannot recover their own account.
Dashlane Friends & Family covers up to 10 members, each with what Dashlane’s own site describes as “a private account,” plus unlimited secure sharing between members. One detail worth flagging for families specifically: Dashlane’s own comparison table lists VPN access as “for the plan manager only” on this tier, not for every member, and doesn’t show dark web monitoring as included at this tier the way it does for some other plans. Dashlane discontinued its free plan in September 2025, so there’s no permanently free option left for a family that wants to try before paying — only the 14-day trial on paid tiers.
NordPass Family covers up to 6 members. NordPass is the only one of the three with a genuinely permanent free tier, though that free tier is single-user and not the family feature itself — it’s relevant mainly if a family member wants to try NordPass solo before the household upgrades to Family. NordPass is part of the same corporate family as NordVPN, which can matter if you’re already a Nord Security subscriber and want to manage one relationship instead of three.
Pricing Breakdown
Plan
Price
Members
Key family features
1Password Individual
Regular pricing not separately confirmed on the page we reviewed; Families is the relevant comparison point here
1
Baseline for comparison only
1Password Families
$4.49/mo (promo, annual, first 12 months) / $5.99/mo regular
Reported ~$7.49/mo billed annually (third-party source; see pricing note above)
Up to 10
Unlimited secure sharing, private accounts per member, VPN limited to the plan manager, 14-day trial
NordPass Premium (individual)
Reported as low as ~$1.29–$1.99/mo depending on term (third-party sources; not independently confirmed from NordPass’s own live page)
1
Baseline for comparison only
NordPass Family
$3.69/mo billed annually (1-year plan, confirmed by two independent sources)
Up to 6
Shared/family vault access; exact feature list not independently confirmed from NordPass’s own page during this research
Pros
1Password: The most clearly documented family-recovery mechanism of the three — organizer-assisted recovery, self-service recovery codes, and an Emergency Kit fallback, all described directly in 1Password’s own support docs.
Dashlane: Covers the most people per plan (up to 10), making the effective per-person cost competitive for a large household or extended family splitting the bill.
NordPass: The lowest confirmed monthly price among the three for a multi-person plan, plus a genuine permanent free single-user tier for anyone who wants to test the product first.
Cons
1Password: Covers fewer members (5) than Dashlane’s 10 for a higher per-member cost at the family tier.
Dashlane: No permanent free plan anymore (discontinued September 2025), VPN access is restricted to the plan manager rather than every family member, and dark web monitoring isn’t listed as included at this tier.
NordPass: We could not independently confirm its family-plan feature set (shared vault mechanics, recovery options) from NordPass’s own live pricing page during this research, since the page didn’t load directly — treat feature claims beyond price and member count with that caveat until you verify them yourself on nordpass.com.
Who It’s a Good Fit For
Choose 1Password Families if you specifically want a well-documented answer to “what happens when someone forgets their password or loses a device” — the organizer-recovery and Emergency Kit system is the most mature of the three. Choose Dashlane Friends & Family if you’re splitting a plan across more than 5 people, such as a multi-generational household or several friends sharing costs, and you don’t need every member to have VPN access. Choose NordPass Family if monthly price is the deciding factor and you’re comfortable with a slightly less-documented feature set, or if you already use other Nord Security products.
Who Should Look Elsewhere
None of these three is built for business or workplace team password management — if you need admin provisioning, SSO integration, or compliance reporting for employees, look at these same vendors’ Business/Teams tiers instead (covered separately on this site), not their family plans. Likewise, if your priority is specifically passkey and passwordless enterprise authentication rather than a shared household vault, that’s a different product category — see our separate comparison of passkey and passwordless platforms.
Bottom Line
For most families, the decision comes down to how many people need a seat and how much you value a documented recovery process over raw price. 1Password’s family-recovery tooling is the most transparent and mature of the three, based on its own support documentation. Dashlane fits larger groups willing to pay more per plan to cover more people. NordPass is the cheapest confirmed option, which makes it the default budget pick, with the caveat that we could verify less about its specific family feature set than we could for the other two.
FAQ
What happens if a family member forgets their master password? With 1Password, a designated family organizer can recover that member’s account, or the member can use a personal recovery code; an Emergency Kit is the final fallback if every organizer is locked out. Dashlane’s and NordPass’s specific family-recovery mechanics weren’t independently confirmed in our research — check each vendor’s support documentation directly before relying on a specific recovery path.
Can kids have their own logins without seeing my passwords? All three plans give each family member their own private account/vault by design — Dashlane’s own site specifically describes “a private account” per member. Granular parental controls beyond basic vault separation weren’t a feature we could confirm for any of the three during this research.
Which plan fits the most people? Dashlane Friends & Family, at up to 10 members, versus 6 for NordPass Family and 5 for 1Password Families.
Is there a free family plan? No — all three require a paid subscription for multi-person family features. NordPass offers a permanent free plan, but it’s single-user only.
Do these overlap with business password manager plans from the same companies? No — this comparison covers each vendor’s consumer family/personal multi-user plan specifically. All three vendors also sell separate Business or Teams tiers aimed at employees and workplace admin controls, which are a different product with different pricing.
Counting the exact number of unique visitors to a website, unique IP addresses hitting an API, or unique items in a billion-row log sounds like it should require storing every distinct value you’ve seen. For small sets that’s fine — a hash set does the job. At billions of items, storing every distinct value becomes its own infrastructure problem: a precise count of a billion unique 64-bit values needs gigabytes just to hold the set. HyperLogLog solves this by giving up exactness for a tiny, fixed memory footprint: Redis’s implementation estimates cardinality up to very large counts using no more than 12 kilobytes, with a documented error rate of about 0.81%.
At a Glance
Attribute
Detail
What it is
A probabilistic algorithm that estimates the number of distinct elements (cardinality) in a multiset
What it guarantees
No exact count — a statistical estimate with a bounded, tunable standard error
Theoretical accuracy
Relative error of about 1.04/√m, where m is the number of registers (Flajolet et al., 2007)
Redis implementation
Up to 12 KB per HyperLogLog key, standard error of 0.81%, supports up to 2^64 counted elements
Typical use cases
Unique visitor counts, unique query counts, distinct IP/user counts at very high volume
Origin
Flajolet, Fusy, Gandouet, Meunier, “HyperLogLog: the analysis of a near-optimal cardinality estimation algorithm,” AofA 2007 / DMTCS Proceedings
Short Verdict
HyperLogLog is the right tool when you need an approximate distinct count at a scale where an exact one is impractical, and the wrong tool the moment you need an exact answer or the ability to list the actual members. It can’t tell you who visited your site, only roughly how many distinct visitors there were. In exchange for giving that up, it holds its memory footprint essentially flat regardless of whether you’re counting thousands or billions of items — Redis’s own documentation states its implementation uses at most 12 KB per key, with a standard error of 0.81%, independent of how many elements have actually been added.
The Problem: Counting Distinct Items at Scale
The naive way to count unique items is to put every item into a set and read off its size. This is exact, but the set’s memory grows linearly with the number of distinct items — counting a billion unique 64-bit values this way means storing something close to a billion 64-bit values, which is gigabytes of memory for a single count. If you need to track unique visitors across millions of separate time windows, pages, or customers simultaneously, that cost multiplies by every window you’re tracking.
The HyperLogLog algorithm, introduced by Philippe Flajolet, Éric Fusy, Olivier Gandouet, and Frédéric Meunier in a 2007 paper presented at the Conference on Analysis of Algorithms (AofA), is the end point of a line of research — starting with earlier algorithms like LogLog — aimed at estimating cardinality using a fixed, small amount of memory regardless of the true cardinality. Their paper reports that with m = 2048 registers, 32-bit hashing, and 5-bit registers, HyperLogLog can estimate cardinalities “largely beyond 10^9” with roughly 2% accuracy while using only about 1.5 KB of memory — several orders of magnitude less than storing the actual set.
How It Works: Hashing, Leading Zeros, and Harmonic Means
The core trick behind HyperLogLog (and its LogLog predecessor) rests on a simple observation about random bit strings. If you hash every item to a uniformly random bit string, the probability that a given hash starts with exactly k leading zero bits is 1/2^(k+1). So if you’ve hashed n distinct items, the maximum number of leading zeros you’ve observed across all of them gives you a rough signal about how large n probably is — more items means a better chance that at least one hash got a long run of leading zeros purely by chance.
A single such observation is a very noisy estimator, so the algorithm splits incoming items across many independent “buckets” (registers) using a few bits of each hash to choose the bucket, and tracks the maximum leading-zero count seen in each bucket separately. HyperLogLog’s specific contribution over earlier LogLog variants is to combine the per-bucket estimates using a harmonic mean rather than LogLog’s geometric mean, which the original paper shows pushes accuracy very close to the theoretical limit for this class of algorithm: a standard error of about 1.04/√m, where m is the number of registers (buckets) used. More registers means a tighter estimate, at the cost of more memory — the classic precision-for-space trade that defines every probabilistic structure covered on this site.
A Minimal Implementation in Python
This is a simplified version of the core idea — enough to show the mechanism (hashing, bucket assignment, leading-zero tracking, and harmonic-mean estimation), not a production-grade implementation, which needs bias correction for small and very large cardinalities that the original paper derives separately.
import hashlib
import math
class HyperLogLog:
def __init__(self, b=10):
self.b = b # number of bits used to pick a bucket
self.m = 1 << b # number of buckets (registers)
self.registers = [0] * self.m
# bias-correction constant for the harmonic-mean estimator
self.alpha = 0.7213 / (1 + 1.079 / self.m)
def _hash(self, item):
digest = hashlib.sha256(item.encode("utf-8")).digest()
return int.from_bytes(digest[:8], "big")
def add(self, item):
h = self._hash(item)
bucket = h & (self.m - 1) # low b bits select the bucket
remaining = h >> self.b
leading_zeros = 1
while remaining & 1 == 0 and leading_zeros < 64 - self.b:
remaining >>= 1
leading_zeros += 1
self.registers[bucket] = max(self.registers[bucket], leading_zeros)
def count(self):
harmonic_sum = sum(2.0 ** -r for r in self.registers)
raw_estimate = self.alpha * self.m * self.m / harmonic_sum
return round(raw_estimate)
hll = HyperLogLog(b=10)
for i in range(100_000):
hll.add(f"user:{i}")
print(hll.count()) # approximately 100,000, within a few percent
The key properties to notice: memory is fixed at m registers regardless of how many items are added, adding an item is O(1), and merging two HyperLogLogs that share the same number of registers is just a register-wise maximum — no need to touch the original data at all.
Real-World Uses: Redis
Redis ships HyperLogLog as a first-class data type accessed through three commands documented on redis.io: PFADD adds elements and runs in constant time and space, PFCOUNT returns the approximate cardinality of one or more keys, and PFMERGE combines several HyperLogLogs into one destination key — exactly the register-wise-maximum merge the math above implies, which runs in O(n) in the number of HLLs being merged, not the number of items ever added to them. Redis’s documentation states the structure uses “12k bytes in the worst case, or a lot less if your HyperLogLog has seen very few elements,” with a standard error of 0.81%, and supports counting up to 2^64 distinct elements. Because an HLL is stored as an ordinary Redis string internally, it can be read and written with GET/SET like any other string value, which makes it trivial to back up or transfer between instances.
The constant-size merge property is what makes HyperLogLog genuinely useful for analytics pipelines beyond a single counter: you can maintain a separate HLL per hour, merge 24 of them into a daily estimate, and merge 30 daily HLLs into a monthly one, all without re-reading a single original event — a property that plain exact-counting sets simply don’t offer at this cost.
HyperLogLog sits in the same family of space-efficient probabilistic structures as the Bloom filter covered elsewhere on this site — both trade a bounded, known error rate for memory that’s orders of magnitude smaller than an exact structure would need, though they answer different questions: a Bloom filter answers “have I seen this exact item before?” while HyperLogLog answers “how many distinct items have I seen in total?”
Trade-offs
No exact count, ever: even with a tiny error rate, HyperLogLog can never return the precisely correct cardinality, and that error is probabilistic, not a worst-case bound.
No membership queries or enumeration: you can ask “how many distinct items?” but never “was this specific item one of them?” or get the list back.
Accuracy is tunable, not free: more registers (higher m) means a tighter error bound but proportionally more memory — Redis fixes this trade-off internally, but a custom implementation has to choose it explicitly.
Mergeable without the original data: once items are summarized into registers, several HLLs merge into one in time proportional to the number of structures, not the number of items ever counted — a major operational advantage for distributed counting.
Bottom Line
HyperLogLog is the standard answer to “how many distinct things happened” when the honest alternative is either an expensive exact count or no count at all. Flajolet and colleagues proved it gets within a hair of the theoretical best accuracy achievable for any algorithm using this little memory, and Redis’s production implementation turns that math into a practical 12-KB data type with sub-1% error that any application can use with three commands. If you need to know exactly who or what was counted, or need a guaranteed-exact number for billing or compliance, this is the wrong tool. If you need “roughly how many unique X” at a volume where storing every X is itself the problem, it’s close to the best tool available.
FAQ
How accurate is Redis’s HyperLogLog in practice? Redis’s own documentation states a standard error of 0.81%, described elsewhere on the same page as “less than 1%” — meaning a true count of 1,000,000 would typically be estimated within roughly 8,100 of the real value, though individual results vary statistically.
Can I get the list of items HyperLogLog counted? No. The structure only ever produces a cardinality estimate; it discards the specific items entirely during insertion and cannot enumerate, reconstruct, or test membership of what it counted.
Why “HyperLogLog” specifically, and not just “LogLog”? The 2007 paper by Flajolet, Fusy, Gandouet, and Meunier builds on the earlier LogLog algorithm but replaces its geometric-mean estimator with a harmonic mean, which the authors show achieves accuracy close to the theoretical optimum for this class of algorithm while using less memory than LogLog needed for the same accuracy.
Can two HyperLogLogs be merged without re-processing the original data? Yes — this is one of its most useful properties. Redis’s PFMERGE command combines multiple HLL keys into one by taking the maximum value in each corresponding register, which produces a mathematically correct estimate for the union of the original sets without touching the original items.
NordVPN, ExpressVPN, and Surfshark are the three VPNs most likely to show up at the top of every “best VPN” list in 2026, and for good reason: all three now back up their no-logs claims with repeated independent audits, all three ship apps for essentially every platform, and all three are priced to compete hard for long-term subscribers. The real differences come down to price structure, device limits, and exactly what gets bundled in at each tier. Here’s what each one actually charges and includes, based on their current pricing pages.
At a Glance
VPN
Lowest advertised price
Month-to-month price
Simultaneous devices
Money-back guarantee
Latest no-logs audit
NordVPN
$3.49/mo (Basic, 2-year plan)
$14.99/mo
10
30 days
Deloitte, 6th audit (per TechRadar reporting)
ExpressVPN
$2.99/mo (Basic, 2-year plan)
No standalone monthly plan listed on its order page
10
30 days
KPMG, 2025 (23rd audit overall)
Surfshark
$2.49/mo (Starter, ~27-month term)
Separate monthly billing available (price not shown on the page we reviewed)
Unlimited
30 days
Deloitte, June 2025 (ISAE 3000)
All three prices above are introductory rates for new customers on long-term plans; each renews at a higher rate, which we break out in the pricing tables below.
Short Verdict
Surfshark is the easiest recommendation for households, because it’s the only one of the three with no device limit at all — one subscription genuinely covers every phone, laptop, and streaming box a family owns. NordVPN sits in the middle: its Complete and Prime tiers bundle in a desktop ad blocker and other extras on top of the VPN itself, at a modest premium over its Basic plan. ExpressVPN is the most expensive of the three at every tier, but it has the longest continuous public audit history of the group, with its 2025 KPMG audit reported as its 23rd independent review. None of the three publishes a definitive, verifiable list of which streaming services it unblocks at any given moment — that changes constantly as platforms update their blocking — so if a specific service matters to you, use each provider’s money-back window to test it yourself before committing to a multi-year plan.
What Each VPN Actually Is
NordVPN, from Nord Security, is one of the longest-running consumer VPN brands and the anchor product of a company that also sells NordPass and NordLocker. Its pricing page lists three tiers — Basic, Complete, and Prime — all covering 10 simultaneous device connections. According to NordVPN’s pricing page, an ad blocker is not included on Basic but is included on Complete and Prime (desktop only), while scam and phishing protection is included on every tier. NordVPN’s own blog reports repeated independent no-logs audits, with TechRadar’s coverage describing the most recent as the sixth such confirmation.
ExpressVPN is owned by Kape Technologies and has spent years building a reputation around transparency reporting and frequent third-party audits. Its order page lists three tiers — Basic, Advanced, and Express Pro — covering 10, 12, and 14 simultaneous devices respectively, all sold as 2-year plans with four bonus months folded into the advertised term. ExpressVPN’s own blog post on its 2025 KPMG review states this was its 23rd independent audit, which — if accurate — would make it the most heavily and repeatedly audited of the three providers covered here.
Surfshark, also now part of the same corporate family as Nord Security following a 2022 merger but still operated as a distinct brand, differentiates itself primarily on device limits and bundled extras. Surfshark’s pricing page advertises three tiers — Starter, One, and One+ — all permitting unlimited simultaneous device connections, with One and One+ adding features like antivirus and an “Alert” data-breach monitoring tool on top of the core VPN (Starter’s inclusion of these was unclear from the comparison table on Surfshark’s own page at the time of writing). Surfshark published a Deloitte-conducted, ISAE 3000-standard no-logs assurance report in June 2025, covering its standard, static, and multiport VPN servers.
Pricing Breakdown
Plan
Monthly equivalent
Billed today (promo)
Renews at (per year)
NordVPN Basic (2-yr)
$3.49/mo
$94.23 for 27 months
$139.08/yr
NordVPN Complete (2-yr)
$3.99/mo
$107.73 for 27 months
$219.48/yr
NordVPN Prime (2-yr)
$6.99/mo
$188.73 for 27 months
$296.28/yr
ExpressVPN Basic (2-yr)
$2.99/mo
$83.72 for 28 months
$99.95/yr on renewal
ExpressVPN Advanced (2-yr)
$4.49/mo
$125.72 for 28 months
$119.95/yr on renewal
ExpressVPN Express Pro (2-yr)
$7.49/mo
$209.72 for 28 months
$199.95/yr on renewal
Surfshark Starter (~27 mo)
$2.49/mo
$67.23 for the promo term
$511.65 (stated regular/renewal total on the page)
Surfshark One (~27 mo)
$2.49/mo
$67.23 for the promo term
$538.65 (stated regular/renewal total)
Surfshark One+ (~27 mo)
$3.99/mo
$107.73 for the promo term
$616.95 (stated regular/renewal total)
All three companies also sell shorter 1-month and/or 1-year terms at higher monthly rates than the multi-year plans shown above; NordVPN’s page explicitly lists a $14.99/month no-commitment Basic option, for example. VAT or local sales tax may apply on top of any of these prices depending on your location, and all figures here are in USD as listed on each company’s own site at the time of research.
Pros
NordVPN: Clear three-tier structure, scam/phishing protection on every plan including the cheapest one, and a well-documented independent audit history behind its no-logs claim.
ExpressVPN: The deepest and most frequent public audit record of the three (23rd audit as of its 2025 KPMG review, per its own blog), plus higher per-plan device allowances (up to 14 on Express Pro) than NordVPN’s flat 10.
Surfshark: Unlimited simultaneous devices on every tier — the only one of the three with no device cap — making it the simplest option for a multi-person household or someone with many smart-home and streaming devices.
Cons
NordVPN: The ad blocker is desktop-only even on the plans that include it, and the cheapest Basic tier leaves it out entirely.
ExpressVPN: The most expensive of the three at every comparable tier, and its order page doesn’t advertise a plain no-commitment monthly option the way NordVPN does.
Surfshark: The comparison table on Surfshark’s own pricing page was ambiguous about which extras (antivirus, Alert) are actually included on the entry-level Starter tier versus One and One+ — confirm this directly on their site before assuming Starter includes everything.
Who It’s a Good Fit For
Surfshark is the clearest pick for larger households or anyone trying to cover a long list of devices (phones, laptops, a streaming box, a router) without worrying about hitting a connection limit. NordVPN suits someone who wants a well-known brand with a long audit track record and is happy to pay a bit more for bundled extras like the ad blocker on its Complete and Prime tiers. ExpressVPN fits a buyer for whom audit frequency and transparency reporting are the deciding factor, and who is willing to pay a premium for it.
Who Should Look Elsewhere
Budget-focused shoppers who don’t need more than a handful of devices covered may find NordVPN’s or ExpressVPN’s entry tiers cost more per device than Surfshark’s unlimited-device Starter plan. Anyone who wants certainty about unblocking a specific streaming service before paying should be cautious with all three — none of their pricing pages make verifiable, specific streaming-access guarantees, and unblocking ability shifts over time as platforms update their own blocking.
Bottom Line
There’s no single best VPN among these three — the honest answer depends on how many devices you need covered and how much weight you put on audit history versus price. Surfshark wins on raw device flexibility, ExpressVPN wins on audit frequency and transparency, and NordVPN sits in a well-balanced middle position with a long track record of its own. All three back their no-logs claims with real, named independent auditors (Deloitte for NordVPN and Surfshark, KPMG for ExpressVPN) rather than just marketing language, which is a meaningfully higher bar than many smaller VPN brands clear. Use the 30-day money-back window every one of them offers to actually test your specific use case — streaming, torrenting, travel — before committing to a multi-year plan.
FAQ
Which of the three is cheapest? On advertised introductory pricing, Surfshark’s Starter and One plans and ExpressVPN’s Basic plan are closely matched around $2.49–$2.99/month on long-term billing. Renewal pricing changes this picture, so compare the full-term renewal cost, not just the splashy headline rate.
Which one allows the most devices? Surfshark, with no stated device limit on any plan. NordVPN caps every tier at 10 devices; ExpressVPN scales from 10 to 14 depending on tier.
Have these VPNs actually been audited, or is “no-logs” just marketing? All three have published real third-party audit results: NordVPN and Surfshark through Deloitte, and ExpressVPN through KPMG (and historically other firms), per their own blogs and independent tech press coverage. That’s a genuine, verifiable claim, though an audit covers a point in time and specific scope rather than guaranteeing every future configuration forever.
Do any of them guarantee access to specific streaming services? No — none of the three pricing or marketing pages we reviewed made a specific, dated guarantee for any named streaming platform. Unblocking ability changes frequently as streaming platforms update their own geo-blocking.
Is there a free trial? None of the three advertises a free trial on the pages we reviewed; all three instead offer a 30-day money-back guarantee on new subscriptions.
Small businesses picking a website builder in 2026 usually narrow the field to three names fast: Wix, Squarespace, and Webflow. All three let you launch a professional-looking site without writing code, but they sit at different points on the ease-of-use-versus-control spectrum, and their 2026 pricing has shifted enough that older comparisons are out of date. We pulled current plan tiers and prices directly from each vendor’s own pricing page to see where they actually land today.
At a Glance
Spec
Wix
Squarespace
Webflow
Entry paid plan
Light, $17.77/mo (annual)
Basic, $19/mo (annual) / $25/mo (monthly)
Basic, $15/mo (annual) / $25/mo (monthly)
Free plan?
Yes, Wix subdomain
No permanent free plan (14-day trial)
Yes, Starter — webflow.io subdomain only
Best known for
Drag-and-drop design freedom, AI site generator
Designer-quality templates, built-in AI tools
Pixel-level control with a visual canvas that outputs real CSS
Online store fee
Varies by plan’s eCommerce tier
2% on Basic, 0% from Core up
No native store transaction fee on Site plans (separate Ecommerce plans exist)
Best for
Small businesses wanting maximum visual control
Portfolios, creative brands, boutique stores
Agencies and businesses wanting designer-grade, custom layouts
Short Verdict
Wix is still the easiest way for a small business owner to get a decent-looking site live fast, especially with its AI site generator doing the first draft. Squarespace trades some layout freedom for guardrails and remains the strongest choice when visual polish matters more than pixel-perfect customization — its 0% store transaction fee from the Core plan up is also a genuine saving for anyone selling products. Webflow is the odd one out: it’s not really built for a non-technical owner editing the site solo, but if you’re working with a designer or agency, or want a site that looks genuinely custom rather than template-based, its visual canvas that exports real, clean code is hard to match at this price point.
What Each One Is
Wix is a fully hosted, drag-and-drop builder where elements sit freely on a canvas instead of inside a fixed template grid. It leans on design freedom, a large app marketplace, and an AI site generator that can produce a draft site from a text prompt — a genuine time-saver for a small business that just needs something live quickly.
Squarespace builds sites from a smaller set of professionally designed templates with a more opinionated editor. You get less granular freedom than Wix, but a more consistently polished result by default, which is why it’s long been the default for photographers, restaurants, and creative small businesses that want to look expensive without a dedicated designer.
Webflow is a visual builder aimed higher up the skill curve: you design on a canvas much like Wix’s, but every element maps to real HTML and CSS underneath, and the tool is built to produce genuinely custom layouts rather than template variations. Webflow restructured its Site plans in May 2026, consolidating the old Basic, CMS, and Business tiers so the lineup now runs Starter (free) → Basic → Premium → Team (a new, higher-priced plan for growing teams) → Enterprise.
Pricing Breakdown
Plan
Price (billed annually, per month)
Key limits
Wix Free
$0
Wix subdomain, Wix branding, limited storage
Wix Light
$17.77/mo
2 GB storage, free custom domain for 1 year
Wix Core
$29.77/mo
50 GB storage, basic eCommerce tier
Wix Business
$39.77/mo
100 GB storage, standard eCommerce tier
Wix Business Elite
$159.77/mo
Unlimited storage, advanced eCommerce and dev tools
Squarespace Basic
$19/mo annual, $25/mo monthly
2% store transaction fee, 7% digital content fee, 2 contributors
Squarespace Core
$29/mo annual, $39/mo monthly
0% store fee, 5% digital content fee, unlimited contributors, free year of Google Workspace
Squarespace Plus
$49/mo annual, $65/mo monthly
0% store fee, 1% digital content fee, reserved cart, countdown timer
Squarespace Advanced
$99/mo annual, $139/mo monthly
0% fees on everything, high-traffic checkout, lowest card processing rate
300 static pages, 10 GB bandwidth/mo, custom domain, no CMS
Webflow Premium
$25/mo annual, $39/mo monthly
20,000 CMS items, 40 CMS collections, bandwidth tier from 50 GB up to 2.5 TB/mo
Webflow Team
From $2,500/mo (annual contract)
100 CMS collections, 10 seats, localization — platform-level plan for growing teams
Two things worth flagging before you budget: Wix’s pricing page explicitly states quoted rates exclude tax and vary by location, and the company has adjusted plan prices more than once in 2026, so treat the figures above as the published rate at time of writing and confirm the live number for your region. Webflow’s new plan structure (Starter/Basic/Premium/Team/Enterprise) took effect for new purchases from May 13, 2026, with existing sites migrating on their next renewal — if you’re quoted older “CMS” or “Business” plan names, you’re looking at legacy pricing that’s being phased out.
Pros and Cons
Wix
Pros: fastest path from zero to a live site, especially with the AI generator; large app marketplace; built-in booking and events tools useful for service businesses.
Cons: free plan carries visible Wix branding; moving a finished Wix site to another platform later is difficult since there’s no standard export path; pricing has changed more than once this year.
Squarespace
Pros: strongest default design quality out of the box; unlimited bandwidth on every plan; 0% store transaction fees from Core up; AI content tools bundled into every tier.
Cons: less granular layout control than Wix or Webflow; no permanent free plan, only a 14-day trial; digital content/membership fees only disappear entirely on the priciest Advanced tier.
Webflow
Pros: genuinely custom, agency-grade layouts rather than template variations; exports clean, semantic code; the free Starter plan is a real sandbox for learning the tool before paying.
Cons: steepest learning curve of the three for a non-technical small business owner; the free plan is development-only (no custom domain); 2026’s plan restructuring means prices and limits are in flux through the rest of the year.
Who It’s a Good Fit For
Choose Wix if you want to be live quickly, value drag-and-drop freedom, and might use built-in booking, events, or a large app marketplace.
Choose Squarespace if you’re a creative or service brand where visual polish matters most and you sell a modest volume of products or digital content.
Choose Webflow if you’re working with a designer or developer and want a site that looks genuinely custom, or you’re a small agency building sites for clients.
Who Should Look Elsewhere
A solo owner with no design background and no plan to hire help will likely find Webflow’s learning curve frustrating compared to Wix or Squarespace. A business planning a high-volume online store with complex inventory and shipping rules will eventually outgrow all three general-purpose builders and should look at a dedicated eCommerce platform instead. And if you want full ownership of your content with an open migration path, WordPress.com’s Business plan is worth comparing against all three — see our Wix vs Squarespace vs WordPress.com comparison for that angle specifically.
Bottom Line
For most small businesses without in-house design or development help, it comes down to Wix versus Squarespace: Wix for maximum hands-on control and speed, Squarespace for a more polished result with less effort and better store economics. Webflow is the right call specifically when you have design or development support and want a site that doesn’t look like a template — not when you need to build and maintain everything solo. Whichever you pick, budget for annual billing; all three charge noticeably more month-to-month.
FAQ
Which is cheapest for a simple small-business site?
Webflow’s Basic plan at $15/mo (annual) is the lowest paid entry point among the three, though it has no CMS. Wix’s Light plan at $17.77/mo and Squarespace’s Basic at $19/mo (annual) are close behind. All three also offer a free tier, but Wix’s is the only one of the three with a genuinely usable permanent free plan for a live (if branded) site.
Do any of these charge a transaction fee on sales?
Squarespace charges 2% on store sales on its entry Basic plan, dropping to 0% from Core up (a separate declining digital-content fee applies through the Advanced tier). Webflow’s Site plans don’t carry a native store transaction fee, though Webflow sells separate Ecommerce plans for stores. Wix’s fee treatment depends on which eCommerce feature tier is attached to your plan — check the live pricing page for specifics.
Can I switch builders later without losing my content?
Not easily with any of these three. Wix and Squarespace are both closed, proprietary site architectures with no standard export-and-rebuild path, and while Webflow lets you export code, reassembling that export into another CMS still takes real developer work. If platform lock-in is a major concern, an open-source option is worth weighing before you build.
Is Webflow’s free plan usable for a real small-business site?
Not for a live site facing customers. Webflow’s Starter plan is capped at 2 static pages, 1 GB of bandwidth, and a webflow.io subdomain with no custom domain support — it’s meant for learning the tool and prototyping, not for publishing a business’s actual website.
Every API needs documentation, but “documentation” now means three different things depending on which tool you pick: a spec-authoring workflow (Swagger/OpenAPI and SwaggerHub), a docs-as-code publishing platform (Redocly), or a design-first collaboration suite that’s in the middle of being absorbed into a bigger platform (Stoplight). All three sit on top of the same underlying standard — the OpenAPI Specification — but they solve different parts of the problem, and in 2026 the competitive picture is more tangled than it looks because of an acquisition that’s reshaping two of these three tools from the inside.
At a Glance
Tool
Starting Price
Free Tier
Best For
Key Specs
Swagger / OpenAPI tools
Free (Swagger Editor, Swagger UI, Swagger Codegen are open source)
Yes — the core tools have no paid tier at all
Teams that just need to author, validate, and render an OpenAPI 3.x document without a hosted platform
Supports OpenAPI 3.2 (released September 2025); SwaggerHub is the commercial hosted layer on top
SwaggerHub (SmartBear)
Not published as self-serve tiers; quote-based via SmartBear sales
No published free collaborative tier as of this writing
Teams that want hosted, versioned OpenAPI authoring with team collaboration, now converging into SmartBear’s broader “API Hub”
Being consolidated with Stoplight’s capabilities under SmartBear’s API Hub umbrella following SmartBear’s 2023 Stoplight acquisition
Redocly
$249/month (Pro), billed annually ($2,988/year)
No free collaborative tier; open-source Redoc renderer is free
Teams that want a polished, Git-based docs site with strong theming and governance (linting, style guides)
Scale tier $729/month ($8,748/year); Enterprise is custom
Stoplight
Not published as self-serve tiers; being folded into SmartBear API Hub
Teams already using Stoplight Studio for design-first API modeling, during the SmartBear transition
SmartBear announced its agreement to acquire Stoplight on August 22, 2023; its commercial product is being merged into API Hub rather than sold as a fully separate product going forward
Short Verdict
If you just need to write and preview an OpenAPI document, the free, open-source Swagger tools (Editor, UI, Codegen) still do the job with zero cost and zero lock-in. If you want a genuinely good-looking, Git-native documentation site with strong linting and governance, Redocly is the clearest, most transparently priced option of the three. If you’re evaluating Stoplight or SwaggerHub today, the more important fact than any feature comparison is that both are owned by SmartBear and are actively converging into a single product called API Hub — so the real decision isn’t “Stoplight vs. SwaggerHub,” it’s “do we want SmartBear’s consolidated platform, and are we comfortable buying into a product that’s mid-merger.”
What Each One Actually Is
Swagger / OpenAPI. “Swagger” is the original name of what’s now the OpenAPI Specification (OAS), the open, Linux Foundation-governed standard for describing REST APIs in a machine-readable YAML or JSON document. The free Swagger tooling — Swagger Editor (browser-based spec authoring with live preview), Swagger UI (renders a spec as interactive, “try it out” documentation), and Swagger Codegen (generates client SDKs and server stubs from a spec) — remains open source and free to self-host. OpenAPI 3.2, released in September 2025, is a backward-compatible update to 3.1 that added hierarchical tags, native streaming media types, a new safe-but-body-carrying QUERY HTTP method, OAuth 2.0 Device Authorization Flow support, and clearer example formatting. None of that requires a paid product — you can write a 3.2 document in a text editor and render it with the free Swagger UI.
SwaggerHub is SmartBear’s commercial, hosted layer on top of the open Swagger tools: versioned spec storage, team collaboration, style validation, and an integrated mock server and domain registry. Crucially, SmartBear has been restructuring its product lineup — SwaggerHub Portal was folded into a product called “API Hub for Portal” in early 2025 and later simply renamed “Swagger Portal,” and SmartBear’s broader messaging now frames SwaggerHub’s capabilities, plus Stoplight’s, as part of one unified “API Hub.” If you’re pricing this out today, expect to go through a SmartBear sales conversation rather than a self-serve checkout page — the company’s current pricing pages route to a trial request or a sales contact rather than publishing fixed per-seat numbers.
Redocly is a docs-as-code platform built around the open-source Redoc rendering engine. Instead of a web-based editor, Redocly’s model is Git-first: you write OpenAPI/Markdown/Markdoc content in your own repository, Redocly builds and hosts the site, and pull requests get preview deployments. It layers on API linting (via the open-source Redocly CLI and its ruleset engine), an API catalog for organizations managing many specs, SSO, and — new in its current plans — an AI Assistant for both doc readers and an “Agent” feature for automated PR reviews.
Stoplight began as a design-first API platform: a visual spec editor (Stoplight Studio), a mock server (Prism), a linter (Spectral), and a documentation renderer (Elements) — the last three of which are open source and still maintained. SmartBear announced a definitive agreement to acquire Stoplight on August 22, 2023, explicitly framing the deal as bringing design, documentation, and governance capabilities into SmartBear’s platform so that, in SmartBear’s own words, “developers no longer need to choose between these tools.” In practice, that means Stoplight’s commercial product is being absorbed into API Hub rather than continuing indefinitely as a fully independent product line with its own roadmap and pricing page.
Pricing Breakdown
Plan
Price
Notes
Swagger Editor / UI / Codegen
$0
Open source (Apache 2.0); self-hosted, no account required
SwaggerHub (all tiers)
Not published — contact SmartBear sales
SmartBear’s current product and pricing pages for SwaggerHub/API Hub route to a trial signup or sales contact rather than listing fixed self-serve prices as of this writing
Redocly Pro
$249/month, billed annually ($2,988/year)
Unlimited seats and readers; 3 projects (additional projects $390/year each); mock server, custom domain, MCP server for docs
Adds SCIM, audit logs, data residency, single-tenant options, SLA-backed support
Stoplight (all tiers)
Not published — being integrated into SmartBear API Hub
Historical Stoplight pricing was per-user with per-month billing, but the standalone pricing page no longer lists fixed tiers; open-source Spectral, Prism, and Elements remain free
We checked each vendor’s current, live pricing page directly rather than relying on third-party aggregator sites, several of which list specific SwaggerHub and Stoplight numbers that are explicitly flagged by those same aggregators as unverified or years out of date. Redocly’s numbers above come straight from its own pricing page. For SwaggerHub and Stoplight, both of SmartBear’s live pricing surfaces currently route to a trial-request or sales-contact flow rather than displaying fixed self-serve tiers — a direct consequence of the ongoing Stoplight-into-API-Hub consolidation — so if exact current per-seat pricing matters for your budgeting, request a quote directly from SmartBear rather than trusting a third-party number.
Pros and Cons
Swagger / OpenAPI (open tools)
Pros: completely free, no vendor lock-in, huge ecosystem of compatible tooling, supports the current OpenAPI 3.2 spec
Cons: no built-in hosting, team collaboration, or governance — you assemble those yourself or pay for SwaggerHub/another platform
SwaggerHub
Pros: tight integration with the Swagger tooling developers already know; backed by SmartBear’s broader API quality and testing portfolio (ReadyAPI, Pactflow)
Cons: pricing requires a sales conversation; the product is actively being restructured into API Hub, which creates near-term roadmap and migration uncertainty for existing customers
Redocly
Pros: transparent published pricing, polished default theming, strong Git-based workflow with PR previews, genuinely useful linting via its open-source CLI
Cons: no free collaborative tier — the cheapest paid plan is $249/month; per-project add-on costs can accumulate for organizations with many separate APIs
Stoplight
Pros: strong design-first visual editor for teams that prefer modeling a spec visually over hand-writing YAML; its open-source components (Spectral linting, Prism mocking, Elements rendering) are mature and widely adopted independently of the commercial product
Cons: the standalone commercial product’s long-term shape is unclear while it’s being merged into API Hub; new customers evaluating it today are effectively evaluating SmartBear’s broader platform, not a standalone Stoplight
Who It’s a Good Fit For
Choose the free Swagger/OpenAPI tools if you want zero cost, zero lock-in, and you’re comfortable wiring up your own hosting and review workflow.
Choose Redocly if you want a docs-as-code workflow with clean, published pricing and don’t mind paying from day one — it’s the most straightforward of the three to budget for.
Choose SwaggerHub or Stoplight only after talking to SmartBear directly about current pricing and the API Hub migration timeline — both are reasonable choices if you’re already invested in SmartBear’s ecosystem (ReadyAPI, Pactflow, etc.) and want one vendor relationship.
Who Should Look Elsewhere
Teams that need a free, self-serve collaborative editor with multiple seats and no sales call should look at other hosted OpenAPI editors in the market before assuming SwaggerHub or Stoplight will have an accessible entry-level price — neither currently publishes one. Teams that want the absolute lowest cost and are willing to self-host should stick with the open Swagger tools rather than paying for any hosted platform at all. And teams specifically wary of buying into a product mid-acquisition should treat Stoplight’s standalone future as an open question rather than a settled one, since SmartBear’s own public statements frame it as being absorbed into API Hub rather than continuing as a fully separate roadmap.
Bottom Line
The “Swagger vs. Redocly vs. Stoplight” framing undersells how much has changed since these three tools were cleanly distinct competitors. Swagger/OpenAPI is the free, open foundation all of this sits on, and that hasn’t changed. Redocly has pulled ahead on pricing transparency and polish for teams that want a dedicated docs platform. Stoplight and SwaggerHub, meanwhile, are both owned by SmartBear and are being merged into a single “API Hub” product — which means the real 2026 decision for anyone evaluating either one isn’t a feature checklist, it’s whether you’re comfortable adopting a platform that’s actively consolidating two previously separate tools into one.
FAQ
Is Swagger the same thing as OpenAPI? Historically yes — “Swagger” was the original name of the specification before it was donated to the Linux Foundation and renamed the OpenAPI Specification in 2016. “Swagger” now refers to SmartBear’s branded tooling (Swagger Editor, Swagger UI, SwaggerHub) built around that open standard.
Are Stoplight and SwaggerHub the same product now? Not fully merged as of this writing, but they are converging. SmartBear acquired Stoplight (agreement announced August 22, 2023) and has since been integrating its capabilities, along with SwaggerHub’s, into a product it calls API Hub.
What’s new in OpenAPI 3.2? Released in September 2025, it’s a backward-compatible update to 3.1 adding hierarchical tags, native streaming media type support, a new QUERY HTTP method for safe searches with a request body, OAuth 2.0 Device Authorization Flow security support, and refined example fields.
Can I use Redoc (the open-source renderer) without paying Redocly? Yes — Redoc itself is open source and free to self-host for basic spec rendering. The paid Redocly plans add hosting, Git-based workflows, linting-as-a-service, team collaboration, and the newer AI features.
Why can’t I find published prices for SwaggerHub or Stoplight? Both vendors’ current live pricing pages direct visitors to a free trial signup or a sales contact rather than listing fixed self-serve tiers, which appears to reflect SmartBear’s ongoing restructuring of both products into its unified API Hub offering.
Balanced trees — red-black trees, AVL trees, B-trees — get their O(log n) guarantees from careful bookkeeping: rotations, rebalancing, parent pointers, and color bits that have to be updated correctly on every insert and delete. Skip lists get the same expected O(log n) behavior from something much simpler: a coin flip. Invented by William Pugh in 1990 as an explicitly probabilistic alternative to balanced trees, the skip list trades a worst-case guarantee for a much simpler implementation — and that trade-off turned out to be exactly what two of the most widely deployed storage systems in the industry wanted. Redis uses a skip list to back every sorted set. LevelDB and RocksDB use one to hold every write before it reaches disk.
At a Glance
Attribute
Detail
What it is
A linked list with multiple “express lane” layers, used to search, insert, and delete in expected O(log n) time
How balance is achieved
Randomized level assignment (a coin flip per node) instead of rotations or rebalancing rules
Expected time complexity
O(log n) search, insert, and delete
Worst case
O(n), but no specific input sequence can force it — the randomness is independent of insertion order
Space overhead
About 1.33 pointers per node on average, with the recommended p = 1/4
Real-world uses
Redis sorted sets (ZSET), LevelDB and RocksDB memtables
Origin
William Pugh, “Skip Lists: A Probabilistic Alternative to Balanced Trees,” Communications of the ACM, June 1990
Short Verdict
A skip list isn’t trying to beat a balanced tree on worst-case guarantees — it can’t, and it doesn’t claim to. What it offers instead is an ordered structure with expected logarithmic search, insert, and delete, implemented with plain forward pointers and a random number generator instead of rotation logic, parent pointers, or color bits. That simplicity is precisely why Redis chose it for sorted sets and why LevelDB chose it for the in-memory write buffer every key passes through before it’s flushed to disk: both systems needed fast ordered inserts into a structure that also supports cheap, correct concurrent reads, and a skip list delivers that with far less code than a balanced tree would.
The Problem: Fast Search in a Linked List
A plain sorted linked list supports O(log n) search in theory — except it doesn’t, because you can’t binary-search a linked list. There’s no way to jump to the middle element without walking every node before it, so search, insert, and delete are all O(n). Arrays solve this by supporting random access, but then insertion in the middle requires shifting every subsequent element. Balanced trees solve it by keeping a tree structure that self-corrects on every modification, at the cost of rotation logic that’s notoriously easy to get wrong.
Pugh’s 1990 paper poses a different question: what if a linked list had extra pointers that let a search skip over large chunks of it, the way an express train skips local stops? That’s literally the mechanism. A skip list is a series of linked lists stacked on top of each other. The bottom layer contains every element in sorted order, like an ordinary linked list. Each layer above it contains a randomly chosen subset of the layer below, so a search can start at the top, move right as far as possible without overshooting, then drop down a level and repeat — covering large distances quickly near the top and refining the position near the bottom.
How Randomized Leveling Works
The key design decision is how many levels each node gets, and Pugh’s answer is to decide it randomly at insertion time, independent of how many elements are already in the list. Each new node starts at level 0. A biased coin is flipped with success probability p; as long as it comes up heads, the node’s level increases by one, up to a fixed maximum. Pugh’s paper recommends p = 1/4 for general use, noting that p = 1/2 trades a bit of extra memory for lower variance in search time — a tuning choice, not a correctness requirement.
Because node height is chosen independently of insertion order, no sequence of inserts can deliberately produce a degenerate skip list the way a sorted sequence of inserts can produce a degenerate unbalanced binary tree. The structure can still get unlucky — the paper is explicit that the worst case is O(n) — but Pugh’s analysis shows the probability of a search taking much longer than O(log n) falls off exponentially, which is why “expected” rather than “guaranteed” logarithmic time is an acceptable trade in practice. With p = 1/4, the expected number of forward pointers per node works out to about 1.33, since a node has one pointer at level 0 for certain and a geometrically-decreasing chance of further pointers above that.
A Minimal Skip List in Python
This implementation shows the two operations that matter: randomized level assignment on insert, and the level-by-level descent that both search and insert rely on.
import random
class Node:
def __init__(self, value, level):
self.value = value
self.forward = [None] * (level + 1)
class SkipList:
def __init__(self, max_level=16, p=0.25):
self.max_level = max_level
self.p = p
self.level = 0
self.head = Node(None, max_level)
def _random_level(self):
lvl = 0
while random.random() < self.p and lvl < self.max_level:
lvl += 1
return lvl
def insert(self, value):
update = [self.head] * (self.max_level + 1)
node = self.head
for i in range(self.level, -1, -1):
while node.forward[i] and node.forward[i].value < value:
node = node.forward[i]
update[i] = node
new_level = self._random_level()
if new_level > self.level:
for i in range(self.level + 1, new_level + 1):
update[i] = self.head
self.level = new_level
new_node = Node(value, new_level)
for i in range(new_level + 1):
new_node.forward[i] = update[i].forward[i]
update[i].forward[i] = new_node
def search(self, value):
node = self.head
for i in range(self.level, -1, -1):
while node.forward[i] and node.forward[i].value < value:
node = node.forward[i]
node = node.forward[0]
return node is not None and node.value == value
sl = SkipList()
for v in [3, 1, 4, 1, 5, 9, 2, 6]:
sl.insert(v)
print(sl.search(5)) # True
print(sl.search(7)) # False
The update array is the detail that makes insertion work: as the search descends, it records the rightmost node reached at every level, so once the new node’s random level is known, splicing it in at each relevant level is a constant-time pointer update rather than another full pass over the list.
Real-World Uses: Redis and LevelDB
Redis’s own documentation for sorted sets describes the underlying structure as “a dual-ported data structure containing both a skip list and a hash table,” which is why a Redis ZSET supports both O(log(N)) insertion by score (via the skip list) and O(1) lookup of a member’s current score (via the hash table) at the same time. Redis documents ZADD as costing O(log(N)) and range queries like ZRANGE as O(log(n) + m), where m is the number of elements returned — exactly the profile a skip list provides: logarithmic positioning plus a cheap linear walk once you’re there, which is ideal for leaderboard and ranking use cases where you frequently need “the top N” or “everyone between rank X and Y.”
LevelDB, Google’s embedded key-value store, uses a skip list for an entirely different reason: as the in-memory MemTable that absorbs every write before it’s flushed to disk as an immutable sorted file. LevelDB’s own skiplist.h source comments describe the node’s height as chosen so that it “increase[s] height with probability 1 in kBranching” with kBranching set to 4 — the same geometric-level idea from Pugh’s paper, just named differently. The comments also note that “the contents of a Node except for the next/prev pointers are immutable after the Node has been linked into the SkipList,” which is precisely what makes the structure safe for concurrent, lock-free reads while a single writer inserts — a property a balanced tree’s in-place rotations don’t offer nearly as cleanly. RocksDB, Meta’s fork of LevelDB, inherited the same design for its own memtable.
This pairs naturally with ideas covered elsewhere on this site: LevelDB’s skip-list memtable is the entry point for the exact write-then-flush-then-compact pipeline described in our LSM-trees vs. B-trees piece, and once data lands on disk as an SSTable, systems like Cassandra use a Bloom filter to decide whether that file is even worth checking.
Skip Lists vs. Balanced Trees
Factor
Skip List
Balanced Tree (e.g. red-black)
Balancing mechanism
Randomized node height, decided once at insertion
Deterministic rotations and recoloring on every insert/delete
Worst case
O(n), vanishingly unlikely, independent of input order
O(log n), guaranteed by construction
Implementation complexity
Low — forward pointers and a random level generator
Higher — multiple rotation cases to implement correctly
Concurrent reads during writes
Straightforward, since existing nodes aren’t mutated in place on insert
Harder, since rotations restructure existing nodes
Range queries
Natural — walk the bottom-level linked list
Natural via in-order traversal, but requires tree-aware iteration logic
Trade-offs
No hard worst-case guarantee: a vanishingly unlucky sequence of coin flips can still degrade to O(n), which matters for systems with strict real-time latency requirements.
Memory overhead is probabilistic, not fixed: a node’s pointer count depends on its random level, so total memory use varies run to run, even for the same dataset.
Requires a decent random number generator: a poor one can bias level distribution and erode the expected-time guarantees the structure depends on.
Simplicity is the main win: no rotation logic, no color bits, and — as LevelDB’s design shows — existing nodes stay immutable on insert, which simplifies safe concurrent reads.
Bottom Line
Skip lists prove that a probabilistic structure can match a deterministic one’s expected performance with a fraction of the implementation complexity. That’s not a theoretical curiosity: it’s the exact reasoning Redis’s engineers applied when they needed an ordered structure for sorted sets, and the exact reasoning behind LevelDB’s choice of memtable, where immutable-once-inserted nodes make concurrent reads safe without a maze of locking around tree rotations. If you need guaranteed worst-case bounds — a hard real-time system, for instance — a balanced tree still wins. If you need an ordered structure that’s simple to implement correctly, supports fast range queries, and plays well with concurrent readers, a skip list is usually the better trade.
FAQ
Are skip lists actually used in production, or just a teaching tool? They’re in production at serious scale: Redis’s sorted set type and LevelDB/RocksDB’s memtable both use skip lists as their core structure, not as a simplification for textbooks.
What probability p should I use for level assignment? Pugh’s paper recommends p = 1/4 for general use as a good balance of time and space; p = 1/2 uses more memory per node but reduces the variance of search times, which can matter if consistent latency matters more than average memory use.
Can a skip list’s performance degrade to O(n) in practice? Theoretically yes, but Pugh’s analysis shows the probability shrinks exponentially as n grows, and — critically — no adversarial insertion order can force it, unlike an unbalanced binary search tree fed sorted input.
Why does Redis use a skip list instead of a balanced tree for sorted sets? Redis’s own documentation says sorted sets pair a skip list with a hash table specifically to get O(log(N)) ordered operations and O(1) score lookups together, and the simpler skip-list implementation was a deliberate engineering trade-off over a more complex balanced-tree structure.
3-year capacity subscription (All/Partial/No Upfront), plus usage-based charges for OS and AWS services
Workloads that must run fully on-premises for latency, data residency, or local processing reasons
AWS Local Zones
AWS-operated infrastructure in metro areas, close to population centers
Standard AWS pay-as-you-go, no hardware to buy or host
Latency-sensitive workloads that don’t need to be physically on-prem, just closer to end users
Short Verdict
Both of these exist to solve the same underlying problem — standard AWS Regions are sometimes too far away, physically or organizationally, for a given workload — but they solve it in opposite directions. Outposts brings AWS’s own hardware and APIs into a building you control, for workloads that genuinely cannot leave your premises. Local Zones do the opposite: AWS runs the infrastructure itself, just in smaller facilities placed in or near major metro areas, so you get lower latency to end users without hosting anything yourself. If you need true on-prem, it’s Outposts; if you just need to be geographically closer to users or specific local data-processing requirements without owning hardware, it’s Local Zones.
What Each One Actually Is
AWS Outposts
Outposts racks are physical AWS-built and AWS-maintained server racks, shipped to and installed in your own data center or a colocation facility you control, running the same EC2, EBS, and (for Outposts specifically) S3-on-Outposts APIs you’d use in a normal AWS Region. Per AWS’s own pricing page, you buy rack capacity on a three-year subscription — with All Upfront, Partial Upfront, or No Upfront payment options — and that subscription price includes delivery, installation, infrastructure maintenance, and software patches and upgrades; capacity can be increased over time by upgrading. Billing starts 24 hours after installation, once capacity is available for launching instances. On top of the base subscription, you pay usage-based charges per instance for the operating system and for AWS services like RDS, ECS, EKS, and EMR running on the Outpost, separate from the underlying EC2/EBS charges already covered by the subscription. Ordering an Outpost requires an AWS Enterprise Support subscription. Data transfer between the Outpost and its parent AWS Region, and between the Outpost and your local network or the internet via the Local Gateway, is free; transfer from the parent Availability Zone to the Outpost is priced as standard in-Region transfer.
AWS Local Zones
Local Zones are AWS infrastructure deployments placed in or near large population and industry centers, specifically to put compute and storage closer to end users without requiring a full AWS Region’s worth of infrastructure in that metro area. Unlike Outposts, there’s no hardware for you to host or own — Local Zones are entirely AWS-operated, and you use them through the same AWS pay-as-you-go pricing you’d use in any Region, with no capacity subscription or three-year commitment involved.
Trade-offs
Outposts gives you the strongest guarantee — data and compute genuinely never leave your building — but it’s a real multi-year capital-style commitment with AWS Enterprise Support required, not a tool you spin up for a short-term project.
Local Zones are much simpler to adopt (ordinary pay-as-you-go billing, no hardware, no term commitment), but they only exist in the specific metro areas AWS has chosen to deploy them, so they’re not a substitute for Outposts if your actual requirement is on-premises hosting rather than just lower latency.
Who It’s a Good Fit For
AWS Outposts fits regulated industries and specific latency-critical, on-premises use cases — manufacturing floors, hospitals, government facilities — where compliance or physical-latency requirements mean workloads genuinely cannot run in a public cloud Region at all. AWS Local Zones fit consumer-facing applications (gaming, media, real-time collaboration) that need lower latency to users in specific large metro areas, without any appetite for managing physical infrastructure themselves.
Bottom Line
Start by asking whether your workload has to physically stay on your own premises. If yes, that’s Outposts, and budget for a multi-year subscription and Enterprise Support. If you just need to be closer to users in a specific metro area with none of the hosting burden, Local Zones get you there on standard AWS billing with no long-term commitment.
FAQ
Do I need to buy hardware for AWS Local Zones?
No. Local Zones are entirely AWS-operated; you use them with standard pay-as-you-go AWS billing, with no hardware to purchase or host yourself. That’s the core difference from Outposts.
What happens if I don’t renew my Outposts subscription at the end of the term?
Per AWS’s pricing documentation, if you don’t notify AWS at the end of the three-year term, the Outpost renews automatically on a monthly basis at the No Upfront rate for that configuration.
Is AWS Enterprise Support required for Outposts?
Yes. AWS’s own pricing page states an AWS Enterprise Support subscription is required to order an Outpost.
Oracle’s infrastructure headlines in 2026 have mostly been about Exadata, OCI GPU capacity, and multicloud database deals — but Oracle Health, the healthcare IT business built around its 2022 acquisition of Cerner, has been running its own, much less publicized AI rollout inside electronic health record software that a large share of U.S. hospitals already use every day.
What the Clinical AI Agent Actually Does
Oracle Health’s Clinical AI Agent started with automated clinical note generation and, per an August 19, 2026 Oracle announcement, has since expanded into three additional areas:
Professional fee coding: the agent analyzes patient-visit conversations and suggests charge codes directly in the orders workflow, with clinicians reviewing and confirming before submission.
Dictation: clinicians can dictate into any text field in the EHR, with the agent transcribing speech to text in real time for review and editing.
Chart review: the agent pulls relevant context from across a patient’s record — medical history, lab results, medications — and summarizes it before or during a visit, rather than requiring a clinician to click through multiple screens.
Oracle’s release explicitly frames these as assistive, not autonomous: clinicians remain responsible for reviewing, editing, and signing all documentation, and coding decisions stay with qualified professionals rather than the agent. The company ties these updates to order-creation capabilities it announced earlier, in February 2026, describing the pieces as working together as one system rather than as separate point features.
The Adoption Number Oracle Is Citing
Oracle’s August 2026 release states that automated note generation alone has saved physicians more than 400,000 hours across U.S. health organizations in the nearly two years since it launched. That figure is Oracle’s own reported number, not an independently audited study, and the release doesn’t name specific hospitals or health systems using the tool — so it should be read as a vendor-reported adoption metric rather than a peer-reviewed outcome.
Why This Matters for the Former Cerner Business
Oracle bought Cerner for $28.3 billion in 2022, inheriting a large, entrenched, but technologically dated EHR platform competing against Epic Systems, which has long dominated the large-hospital segment of the U.S. EHR market. Documentation burden — the hours clinicians spend on notes, coding, and chart review rather than patients — is one of the most consistently cited sources of physician burnout in U.S. healthcare, and it’s also one of the most visible, easily demonstrated places for an AI feature to show value to a hospital’s purchasing committee. Embedding an AI agent directly into documentation, coding, and chart review is Oracle Health’s most concrete answer yet to the broader question of whether AI investment can help it win back EHR market share from Epic, rather than just modernizing its infrastructure underneath an unchanged product.
What’s Still Unclear
Oracle’s announcement doesn’t disclose pricing for the Clinical AI Agent, which specific hospital systems have adopted the newer coding/dictation/chart-review features (as opposed to the broader note-generation feature it’s been shipping longer), or independent data on documentation-time savings beyond Oracle’s own reported hours figure. As with most enterprise healthcare IT, expect any serious evaluation of this tool to require a direct conversation with Oracle Health rather than a self-serve trial.
FAQ
Does the Clinical AI Agent make billing or diagnostic decisions on its own?
No. Oracle’s own release states that clinicians review, edit, and sign all documentation, and that coding decisions remain with qualified professionals — the agent suggests and summarizes, but doesn’t finalize these decisions itself.
How long has this feature existed?
Per Oracle’s August 2026 release, note generation specifically has been in use for nearly two years; coding, dictation, and chart review are newer additions announced in 2026, building on order-creation features Oracle introduced in February 2026.
Is this related to the former Cerner platform?
Oracle Health is the business built from Oracle’s 2022 acquisition of Cerner; Oracle’s own announcement doesn’t use the Cerner name directly, but the Clinical AI Agent runs inside the Oracle Health EHR platform that originated from that acquisition.
While most of IBM’s AI infrastructure headlines in 2026 have centered on Power11 CPUs, the Telum II mainframe chip, and the Spyre accelerator, IBM has quietly kept running its other long-term infrastructure bet: a concrete, dated roadmap to large-scale fault-tolerant quantum computing. IBM laid out that roadmap in detail alongside its November 2025 unveiling of two new processors, Nighthawk and Loon, and it now has a named target — a system called Starling, due in 2029.
Nighthawk: A New Qubit Lattice
Nighthawk is a 120-qubit processor built on a square lattice, where each qubit connects directly to four nearest neighbors — up from the two or three neighbors each qubit got on the heavy-hex lattice IBM’s prior Heron chips used. Per IBM’s own blog, Nighthawk currently runs circuits of around 5,000 gates, similar to Heron, but the denser connectivity gives it roughly 16 times Heron’s effective circuit depth for comparable error rates. IBM expects Nighthawk to reach 15,000-gate circuits by 2028, and plans to link up to nine Nighthawk modules together using new “l-couplers” to reach 1,080 qubits by 2028.
Loon: Proving Out the Error-Correction Code
Loon, also unveiled in 2025, adds “c-couplers” that connect qubits farther apart than nearest neighbors on the same chip — a specific feature needed for IBM’s planned quantum low-density parity-check (qLDPC) error-correction codes, which require longer-range connections than a simple grid provides. IBM describes Loon as a proof-of-concept vehicle for those codes rather than a processor meant to run large workloads itself.
The Full Roadmap to 2029
IBM’s published timeline runs year by year:
2025: Loon, proving out qLDPC-code building blocks.
2026: Kookaburra, the first module designed to store information in a qLDPC memory and process it with an attached logical processing unit; IBM also expects to demonstrate quantum advantage by the end of 2026, with quantum computers acting as accelerators alongside classical HPC rather than standalone replacements.
2027: Cockatoo, intended to demonstrate entanglement between separate modules using a new universal adapter.
2028: Starling-stage hardware demonstrates magic state injection across multiple linked modules, alongside Nighthawk reaching 1,080 qubits.
2029: Starling itself — a large-scale, fault-tolerant quantum computer IBM plans to operate in Poughkeepsie, New York, capable of running circuits of 100 million gates across 200 logical qubits.
Why Bivariate Bicycle Codes
The error-correction scheme underpinning Starling is what IBM calls a bivariate bicycle code. Its specific “gross” code, denoted [[144,12,12]], encodes 12 logical (error-corrected) qubits using 144 data qubits plus 144 syndrome qubits — 288 physical qubits total. IBM’s own claim is that this needs roughly 10 times fewer physical qubits than the surface code (the error-correction scheme most competing quantum efforts have focused on) for comparable error-correction performance, which is the central economic argument behind IBM’s whole roadmap: fault tolerance is mostly a qubit-overhead problem, and a more efficient code means a physically smaller, more buildable machine. IBM pairs this with a decoder called Relay-BP, which it says achieves a 5x to 10x reduction in decoding resource needs compared with other leading decoders, and which can run on FPGAs or ASICs rather than requiring large dedicated HPC clusters just to interpret error syndromes in real time.
Quantum as an HPC Accelerator, Not a Replacement
IBM’s framing throughout this roadmap treats quantum processors as accelerators that plug into classical high-performance computing, not as standalone machines that replace it. IBM points to software for orchestrating quantum and HPC resources together, and a new C API meant to integrate Qiskit more directly into HPC environments, as part of the same effort. This mirrors, in a different domain, the same “heterogeneous compute” logic behind IBM’s Spyre AI accelerator attaching to Power and mainframe systems: specialized silicon bolted onto a classical compute fabric rather than standing entirely alone.
Bottom Line
IBM’s quantum roadmap is now a genuinely dated, milestone-by-milestone plan rather than a vague long-term aspiration — Nighthawk and Loon shipping in 2025, Kookaburra and an expected quantum-advantage demonstration in 2026, Cockatoo in 2027, and Starling, the named fault-tolerant target, in 2029. The bet underneath all of it is that a more qubit-efficient error-correction code (bivariate bicycle codes) makes fault tolerance reachable with hardware IBM can plausibly build this decade, rather than requiring the much larger qubit counts surface-code approaches are often assumed to need.
FAQ
What is IBM’s fault-tolerant quantum computer called?
IBM calls it Starling, targeted for 2029 and planned to run in Poughkeepsie, New York, capable of 100-million-gate circuits across 200 logical qubits.
How many qubits does Nighthawk have?
Nighthawk is a 120-qubit processor on a square lattice; IBM plans to link up to nine Nighthawk modules to reach 1,080 qubits by 2028.
Does IBM expect quantum computers to replace classical supercomputers?
No. IBM’s own framing describes quantum processors as accelerators that plug into classical HPC infrastructure, with dedicated software and a new C API for integrating Qiskit into HPC environments, rather than standalone replacements.
Nvidia’s annual GPU cadence moved from Hopper to Blackwell in 2024, and the successor to Blackwell — announced at Computex 2024 and detailed in full at CES in January 2026 — is Vera Rubin, named for astrophysicist Vera Rubin, whose work provided key evidence for dark matter. It’s not just a new GPU: Nvidia is shipping it as a platform of multiple co-designed chips, the same way Blackwell shipped alongside Grace CPUs and NVLink switches.
Six Chips, One Platform
Per Nvidia’s own developer blog, the Vera Rubin platform launched with six new chips: the Vera CPU, the Rubin GPU, an NVLink 6 switch, a ConnectX-9 SuperNIC, a BlueField-4 DPU, and a Spectrum-6 Ethernet switch. A March 2026 update added a seventh chip to the platform. This is Nvidia’s now-familiar playbook: rather than selling a GPU alone, it sells the CPU, the GPU, the networking silicon, and the switches as one designed-together system, which is also how it captures value across the entire rack rather than just the chip.
The Numbers That Matter
According to Nvidia’s own published specs:
Compute: the Rubin GPU delivers 50 petaflops of NVFP4 inference and 35 petaflops of NVFP4 training performance, versus 10 petaflops for each on Blackwell — roughly a 3.5x and 5x jump respectively on Nvidia’s own per-chip figures (note this uses NVFP4, a 4-bit floating-point format, so it isn’t directly comparable to performance figures quoted in other precisions).
Memory: up to 288 GB of HBM4 per GPU, with up to 22 TB/s of aggregate memory bandwidth — roughly 2.8x Blackwell’s HBM3e bandwidth, by Nvidia’s account.
Transistors: the Rubin GPU packs 336 billion transistors across 224 streaming multiprocessors.
Networking: NVLink 6 provides 3.6 TB/s of bidirectional bandwidth per GPU — double the prior generation — and in a full NVL72 rack, all 72 GPUs connect in an all-to-all topology through NVLink 6 switch trays.
Rack-scale numbers: a single NVL72 compute tray delivers 200 petaflops of NVFP4, and a “Vera Rubin Superchip” (two Rubin GPUs plus one Vera CPU) delivers 100 petaflops of NVFP4.
Vera CPU: up to 1.5 TB of LPDDR5X system memory at up to 1.2 TB/s.
Nvidia’s own marketing also cites up to 10x higher inference throughput, 10x lower cost per token, and a quarter as many GPUs needed for training versus the prior generation, though the company’s blog post doesn’t spell out the exact test conditions behind those multiples, so they should be read as Nvidia’s own framing rather than independently verified benchmarks.
Timeline and What’s Next
Nvidia announced Vera Rubin at Computex 2024 and gave full technical detail at CES in January 2026. Independent reporting indicates the hardware entered full production around May 2026 and deployment around September 2026, consistent with Nvidia’s stated annual-cadence roadmap. Nvidia has also already announced two chips beyond Rubin: Rubin Ultra (described as effectively two Rubin dies connected together, roughly doubling Rubin’s performance to 100 sparse petaflops NVFP4), targeted for 2027, and Feynman as the architecture after that. As of late October 2026, Nvidia and Oracle also announced plans to expand Vera Rubin deployments to multi-gigawatt scale and bring the Vera CPU specifically to Oracle Cloud Infrastructure, underscoring how quickly hyperscalers are committing to the platform even as it’s still rolling out.
Why the Platform Framing Matters
The six-to-seven-chip framing isn’t just marketing color. NVLink 6’s doubled bandwidth and the all-to-all NVL72 topology are what let 72 physical GPUs behave, for many workloads, like one much larger logical accelerator — which is precisely the property large language model training and inference at frontier scale depends on. Nvidia’s moat has never really been the GPU silicon alone; it’s the combination of that silicon with CUDA, NVLink, and now an entire rack-scale system that competitors have struggled to match piece for piece, let alone as an integrated whole.
FAQ
Is Rubin a single chip or a platform?
Rubin is the name of the GPU specifically; “Vera Rubin” refers to the full platform of co-designed chips, which per Nvidia’s developer blog launched with six chips and gained a seventh in March 2026.
How much faster is Rubin than Blackwell?
By Nvidia’s own published specs, Rubin’s per-GPU NVFP4 figures are 50 petaflops inference and 35 petaflops training, versus 10 petaflops each for Blackwell — though these are vendor-reported numbers in a specific low-precision format, not independently benchmarked comparisons.
What comes after Rubin?
Nvidia has already announced Rubin Ultra, targeted for 2027 and described as roughly double Rubin’s performance, followed by an architecture Nvidia calls Feynman.
Not applicable — resizes pods, doesn’t change replica count
KEDA
Number of pod replicas (drives the HPA) or Jobs
Any external event source: queue depth, DB rows, cloud API metrics, and more
Yes — its own operator handles 0-to-1 scaling
Short Verdict
These three aren’t three competing choices for the same job — they solve three different scaling problems and are frequently used together. HPA scales replica count based on CPU/memory or custom metrics, but it can’t go below one replica and typically watches only CPU and memory out of the box. VPA doesn’t touch replica count at all; it resizes the CPU and memory requests/limits of pods you already have, based on observed usage. KEDA doesn’t replace HPA — it feeds HPA metrics from practically any event source (a queue’s depth, a database’s row count, a cloud provider’s own metrics) and is the only one of the three that can scale a workload all the way down to zero when there’s nothing to do.
How Each One Actually Works
Horizontal Pod Autoscaler (HPA)
A control loop in the controller manager runs on a fixed interval (15 seconds by default), reads metrics for a workload’s pods, and computes a desired replica count: roughly desiredReplicas = ceil(currentReplicas × currentMetricValue / desiredMetricValue). It skips small changes within a tolerance band (10% by default) to avoid flapping, and respects a configurable stabilization window (300 seconds by default on scale-down) to avoid thrashing. The autoscaling/v2 API supports five metric types: Resource (CPU/memory, the common case, requiring metrics-server), ContainerResource (per-container usage), Pods (a custom per-pod metric), Object (a metric from another object, like an Ingress), and External (a metric from outside the cluster, such as queue depth — though in practice, External metrics are most often supplied by something like KEDA rather than wired up manually).
VPA addresses a different problem: pods whose requested CPU/memory is poorly sized — either over-provisioned (wasting cluster capacity) or under-provisioned (risking throttling or OOM kills). It watches actual usage over time and recommends, or automatically applies, new resource requests and limits. Because changing a running pod’s resource requests typically requires recreating it, VPA’s “Auto” update mode causes pod restarts when it resizes — a meaningful operational trade-off compared to HPA’s non-disruptive replica changes.
KEDA
KEDA runs three components in the cluster: keda-operator (manages the HPA lifecycle and handles 0-to-1 scaling specifically), keda-metrics-apiserver (serves external metrics to the HPA through the Kubernetes API server), and keda-admission-webhooks (validates KEDA resources). Its core concept is the “scaler” — a connector to an external event source — and it ships with built-in scalers for a long list of queues, databases, and cloud services, plus support for writing custom ones. Crucially, KEDA doesn’t replace HPA for scaling above one replica; it manages scaling between zero and one itself, then hands off to the standard HPA mechanism above that, feeding it the external metric values HPA alone couldn’t see.
How They Combine in Practice
A common real-world setup actually layers these: KEDA scales a queue-processing workload from zero up based on queue depth (via its own ScaledObject, which creates and manages an HPA behind the scenes), while VPA separately tunes the CPU/memory requests of those same pods so they’re neither wasting capacity nor getting throttled. HPA and VPA can in principle fight each other if both target CPU/memory on the same workload — one changing replica count while the other changes per-pod resources — so most guidance is to pick one axis per metric: let HPA own horizontal scaling on a given metric, and let VPA own sizing on a different, non-overlapping signal, or stagger their responsibilities carefully.
Bottom Line
Use HPA as the default for CPU/memory-driven horizontal scaling above one replica. Add VPA when you specifically need to right-size pod resource requests rather than replica count — and expect pod restarts when it acts. Add KEDA when your scaling signal isn’t CPU/memory at all (a queue, a database, a cloud metric) or when you need true scale-to-zero, since neither HPA nor VPA can do that alone.
FAQ
Can HPA scale a deployment to zero replicas?
No. HPA’s minReplicas has a practical floor of 1; it has no built-in mechanism for scaling to zero. KEDA’s operator specifically handles the 0-to-1 transition that HPA can’t.
Does VPA change how many pods are running?
No. VPA only changes the CPU and memory requests/limits of existing pods; it doesn’t add or remove replicas. That’s HPA’s and KEDA’s job, not VPA’s.
Does KEDA replace the Horizontal Pod Autoscaler?
No. KEDA manages the HPA and supplies it with external metrics; above one replica, scaling still happens through the standard HPA mechanism that KEDA has configured and fed, per KEDA’s own documentation.
Pay-per-component: web ACL + rules + rule groups + requests inspected
$5/web ACL/month + $1/rule/month + $0.60 per million requests
Fully published, itemized pricing
Akamai App & API Protector
Custom quote
No public pricing
Quote-only
Short Verdict
These three sit at genuinely different points on the pricing spectrum, and the spectrum itself is the story. Cloudflare bundles WAF protection into every plan tier, including the free one — you get a managed ruleset and unmetered DDoS protection at $0, with paid tiers adding compliance certifications and SLAs rather than gating the WAF itself. AWS WAF is fully metered and itemized: every web ACL, every rule, every rule group, and every million requests inspected has its own published per-unit price, which makes it transparent but means your bill scales directly with how complex your rule setup gets. Akamai App & API Protector publishes nothing — it’s a pure enterprise, quote-only sale, consistent with Akamai’s broader positioning as a CDN/security platform built around custom contracts rather than self-serve plans.
What Each One Actually Is
Cloudflare WAF
Cloudflare’s WAF sits at the edge of its global network and inspects HTTP(S) traffic before it reaches your origin, using a combination of a free managed ruleset and custom rules you write yourself. It’s included on every plan: Free ($0/month), Pro ($20/month billed annually, or $25/month billed monthly), Business ($200/month annually, or $250/month monthly), and a custom annually-billed Contract tier. What changes between tiers isn’t WAF access itself but surrounding guarantees: lossless image optimization and PCI DSS 4.0 compliance only appear from Pro/Business up, and an uptime SLA with service credits only kicks in at Business and above.
AWS WAF
AWS WAF attaches to CloudFront, an Application Load Balancer, API Gateway, or AppSync, and charges separately for every structural piece you create: $5.00 per web ACL per month (prorated hourly), $1.00 per rule per month, and $1.00 per month for each rule group or managed rule group added to a web ACL, plus $0.60 per million requests inspected. Exceeding the default 1,500 web ACL capacity units costs an extra $0.20 per million requests per additional 500 WCUs, and inspecting request bodies beyond the default size limit adds $0.30 per million requests per additional 16 KB. Bot Control, Fraud Control, CAPTCHA, and challenge actions are billed separately on top of this. Requests blocked by AWS’s own DDoS managed rule group aren’t charged.
Akamai App & API Protector
Akamai’s product combines WAF, bot management, and API security into one offering delivered across Akamai’s CDN edge network. Consistent with most of Akamai’s enterprise security line, there is no published price list anywhere on Akamai’s own site — every deployment is quoted individually based on traffic volume, feature set, and contract term.
Trade-offs
Cloudflare is the easiest to start with at zero cost, but a security-conscious team will likely need the Business tier or above for PCI DSS 4.0 compliance and an uptime SLA — the free WAF alone may not satisfy a compliance checklist.
AWS WAF gives you precise, predictable per-unit costs, but a complex rule setup with many managed rule groups and high request volume can add up quickly in ways that are easy to underestimate before you build it.
Akamai is built for large, high-traffic enterprises already on Akamai’s CDN, but with zero public pricing, it’s effectively impossible to budget for without a sales conversation first.
Who It’s a Good Fit For
Cloudflare WAF fits startups and small-to-midsize teams that want strong default protection immediately, scaling into compliance features as they grow. AWS WAF fits teams already running their application behind CloudFront, an ALB, or API Gateway who want granular, usage-based billing tightly integrated with the rest of their AWS bill. Akamai App & API Protector fits large enterprises with high, globally distributed traffic that are already Akamai CDN customers and want WAF, bot management, and API security bundled under one enterprise contract.
Bottom Line
If you want to start protecting a site today at no cost, Cloudflare’s free-tier WAF is the fastest path. If you’re already deep in AWS and want itemized, usage-based pricing, AWS WAF fits cleanly into that bill. If you’re evaluating Akamai, budget time for a sales conversation — there’s no public number to anchor expectations around.
FAQ
Does Cloudflare charge extra for its WAF?
No. Cloudflare’s WAF and its free managed ruleset are included on every plan, including the free $0 tier; paid tiers add compliance and SLA features rather than gating WAF access itself.
What’s the cheapest way to run AWS WAF?
Minimize the number of web ACLs and custom rules, and prefer AWS-managed rule groups where possible, since every web ACL costs $5/month and every rule costs $1/month regardless of how much traffic it inspects.
Is there any published starting price for Akamai App & API Protector?
No. As of this writing, Akamai publishes no pricing for this product on its own website; every deployment requires contacting Akamai directly for a quote.
Mutexes are the easy answer to “how do multiple threads touch the same data safely,” but they come with a cost: any thread that can’t get the lock simply stops, and if the thread holding the lock gets preempted, descheduled, or crashes mid-critical-section, every other thread waiting on it stalls too. Lock-free data structures solve the same safety problem without ever making a thread wait for another thread to finish — and the mechanism that makes that possible, in nearly every real implementation, is a single hardware instruction: compare-and-swap.
What Compare-And-Swap Actually Does
Compare-and-swap (CAS) is an atomic CPU instruction with three inputs: a memory location, an expected old value, and a new value. The hardware checks, as one indivisible operation, whether the memory location still holds the expected old value; if it does, it writes the new value and reports success, and if it doesn’t (because some other thread changed it first), it reports failure and changes nothing. No lock is taken at any point — the atomicity comes directly from the CPU, not from blocking other threads.
The standard pattern built on top of CAS is “read, compute, try to commit, retry on failure”:
def atomic_increment(counter):
while True:
old_value = counter.load()
new_value = old_value + 1
if counter.compare_and_swap(old_value, new_value):
return new_value
# else: another thread won the race, retry with a fresh read
Every thread doing this is making genuine progress on every attempt, even the failed ones — a failed CAS only happens because some other thread’s CAS just succeeded. That’s the core guarantee of lock-freedom: the system as a whole always makes progress, even though any individual thread could, in a worst case, keep losing the race indefinitely.
Lock-Free vs. Wait-Free vs. Obstruction-Free
These terms get used loosely, but they describe a strict hierarchy of guarantees:
Obstruction-free: a thread running completely alone (no contention) is guaranteed to finish in a bounded number of steps. Under contention, it might never finish.
Lock-free: the system as a whole is guaranteed to make progress — at least one thread always succeeds eventually — but no individual thread is guaranteed to ever succeed; it can theoretically keep losing CAS races forever (this is called “starvation,” and is a real, if rare, risk in practice).
Wait-free: every individual thread is guaranteed to finish in a bounded number of steps, regardless of what any other thread does. This is the strongest guarantee and the hardest to implement; wait-free algorithms exist for specific structures but are far less common than lock-free ones.
Most of what’s loosely called “lock-free programming” in production systems — lock-free queues, lock-free hash tables, lock-free linked lists — is lock-free in this specific technical sense, not wait-free.
The ABA Problem
CAS has a well-known correctness trap called the ABA problem. CAS only checks that a memory location’s value matches what you expect — it has no way to know whether that value changed and changed back in between your read and your CAS. Concretely: thread 1 reads a pointer pointing at node A, gets preempted; thread 2 removes A, frees it, and later allocates a new node that happens to get the same memory address and value, call it A again; thread 1 resumes and its CAS succeeds because the value matches A — even though the actual node it was targeting was freed and replaced in between. The fix is usually to pair every pointer with a version counter (a “tagged pointer” or “stamped reference”) and CAS the pair together, so a value can never silently reappear as itself without the version also changing.
Why Reach for This At All
Lock-free structures earn their complexity in a specific situation: high-contention, low-latency paths where a blocked thread is unacceptably expensive — think a shared counter or queue hit by many threads per microsecond, a real-time audio or trading pipeline that can’t tolerate priority inversion (a low-priority thread holding a lock a high-priority thread needs), or kernel and allocator internals where a deadlocked lock could hang the whole system. They are not generally a free performance win: CAS retries under heavy contention can burn more CPU cycles than a well-tuned mutex would, and lock-free code is considerably harder to write correctly and reason about than lock-based code. Most application code should reach for a mutex, a well-tested concurrent collection from the standard library, or message-passing concurrency (channels, actors) long before reaching for hand-rolled CAS loops.
Bottom Line
Lock-free data structures trade the simplicity of “one thread at a time” for a guarantee that no thread ever blocks waiting on another — built almost entirely on the atomic compare-and-swap instruction and a retry loop. That guarantee is valuable in specific high-contention, latency-sensitive contexts, and is paid for with real correctness hazards (the ABA problem chief among them) and implementation difficulty that make it a specialist’s tool rather than a default.
FAQ
Is lock-free code always faster than using a mutex?
Not always. Under heavy contention, repeated failed CAS attempts can waste more CPU time than a mutex would, which blocks waiting threads instead of spinning. Lock-free structures tend to win specifically when avoiding blocking (not raw throughput) is the priority.
What’s the difference between lock-free and wait-free?
Lock-free guarantees the overall system keeps making progress, but an individual thread could theoretically keep losing races and never finish. Wait-free guarantees every individual thread finishes in a bounded number of steps regardless of other threads — a strictly stronger and harder-to-achieve property.
What is the ABA problem in one sentence?
It’s the failure mode where a memory location’s value changes away from A and back to A between a thread’s read and its CAS, causing the CAS to wrongly succeed as if nothing had happened in between; it’s typically fixed by pairing the value with a version counter.
Every time a search box suggests a word before you finish typing it, a router decides which of a million possible next hops matches an IP address, or a DNS resolver walks from a top-level domain down to a specific subdomain, there’s a decent chance a trie or one of its compressed cousins is doing the work underneath. These structures all trade some memory for something hash tables can’t give you: ordered, prefix-aware lookups.
What a Trie Actually Is
A trie (the name comes from “retrieval,” usually pronounced “try” to avoid confusion with “tree”) is a tree where each edge represents one character, or more generally one symbol, of a key. A path from the root to a node spells out a prefix; nodes marked as “end of word” spell out complete keys stored in the structure. Every key that shares a prefix with another key shares the same path through the tree up to the point where they diverge — which is exactly what makes prefix search cheap: once you’ve walked “cat,” every word starting with “cat” lives in the subtree hanging off that node, with no need to compare full strings one at a time.
This is the structural advantage a plain hash table doesn’t have. A hash table can tell you in O(1) whether “category” is in the set, but it has no notion of “everything that starts with cat” — you’d have to scan every key. A trie answers that query by walking three characters down from the root and returning the whole subtree.
class TrieNode:
def __init__(self):
self.children = {}
self.is_end_of_word = False
class Trie:
def __init__(self):
self.root = TrieNode()
def insert(self, word):
node = self.root
for ch in word:
if ch not in node.children:
node.children[ch] = TrieNode()
node = node.children[ch]
node.is_end_of_word = True
def starts_with(self, prefix):
node = self.root
for ch in prefix:
if ch not in node.children:
return False
node = node.children[ch]
return True
The cost of this is memory. A naive trie allocates a node for every character of every key, even when a long stretch of the tree has only one child per node — a single unbranching chain spelling out a long common suffix or prefix with no actual decision points.
Radix Trees: Compressing the Chains
A radix tree (also called a compressed trie, or PATRICIA trie in one common variant) solves the memory problem by merging any node that has exactly one child into its parent, storing the merged characters as a single edge label instead of one node per character. Where a plain trie might need six single-character nodes to store “tomato” after branching off from “tom,” a radix tree stores a single edge labeled “ato.” This cuts node count dramatically for sparse keyspaces — typical of real-world data like URLs, file paths, or IP prefixes, where branching points are rare relative to total key length.
This compression is exactly why radix trees (sometimes called “radix tries” or, in networking contexts, “patricia tries”) show up in two very specific, very load-bearing places:
IP routing tables. A router’s forwarding table needs to find the longest matching prefix for a destination address among potentially hundreds of thousands of CIDR blocks, on every packet, at line rate. A radix tree keyed on the binary representation of the address lets the router walk bit-by-bit (or byte-by-byte) down the tree and naturally find the longest matching prefix along the way, without scanning the whole table.
DNS resolution and domain-name indexes. Domain names are inherently prefix/suffix structured (subdomain.domain.tld), so radix-tree-like structures are a natural fit for indexing zones and walking from a TLD down to a specific host efficiently.
Autocomplete: Where Tries Show Up Every Day
Autocomplete and typeahead search are the most visible everyday use case. Given a partial query, the system needs “every known string with this prefix,” ranked somehow — exactly the operation a trie is built for. In practice, production autocomplete systems usually layer ranking metadata onto trie nodes (popularity scores, recency) so that the “top N completions” query can short-circuit without enumerating an entire subtree, and many large-scale systems use a radix tree or a hybrid structure (sometimes paired with a separate ranking index) rather than a naive character-by-character trie, specifically to control memory at scale.
Tries vs. Hash Tables vs. Balanced Trees
Hash tables win on raw point-lookup speed (average O(1)) and are simpler to implement, but offer no ordering and no prefix queries without a full scan.
Balanced binary search trees (red-black, AVL) give you ordered iteration and range queries in O(log n), but comparisons are on whole keys, not shared prefixes, so they don’t exploit prefix structure the way a trie does.
Tries and radix trees give you prefix queries natively and lookup cost that scales with key length rather than the number of keys stored — which is a genuine advantage when keys are long and share structure, and a genuine disadvantage (extra memory, pointer-chasing) when they don’t.
Bottom Line
Reach for a trie or radix tree specifically when your access pattern is prefix-shaped — autocomplete, routing tables, DNS, file-path indexes, spell-checkers — and reach for a hash table or balanced tree when it isn’t. The radix tree’s compression trick (merging single-child chains into one edge) is what makes the structure practical at the scale real routers and real autocomplete systems actually operate at, rather than a textbook curiosity.
FAQ
Is a radix tree the same thing as a PATRICIA trie?
PATRICIA (Practical Algorithm To Retrieve Information Coded In Alphanumeric) trie is a specific, well-known variant of a radix tree that operates on binary keys bit by bit; the terms are often used loosely as synonyms but PATRICIA specifically refers to the binary-radix case.
Why not just use a hash table for autocomplete?
A hash table can tell you if an exact string exists, but it gives you no efficient way to find “everything starting with this prefix” — you’d need to scan every stored key. A trie’s structure makes prefix lookup a simple tree walk instead.
Do real routers actually use radix trees today?
Longest-prefix-match lookups for IP routing have long relied on trie-based structures (including radix and multibit trie variants); modern high-speed routers often combine these ideas with additional hardware-level optimizations for line-rate lookups, but the underlying prefix-tree concept remains foundational to how the lookup problem is solved.
Monthly credits: 100K+ synthetic records, or 2M+ Transform/PII-detection records, or 1.5M Navigator characters
No published self-serve paid tier — additional credits require contacting sales
Custom quote
Tonic.ai (Fabricate)
$0/mo, $5 in monthly credits, Tonic Cloud, Discord support
Plus: $29/mo, $25 in monthly credits plus pay-as-you-go overage
Custom quote; Tonic also sells separate Structural and Textual products, both custom-priced
MOSTLY AI
Free forever, capped at 2 credits/day (up to 25/month), 1 active chat, SaaS only
No dollar price published — Cloud Marketplace (AWS) and Custom Deployment tiers are both “contact for pricing”
Custom Deployment with unlimited usage, SSO, on-prem or private cloud
Short Verdict
Of the three, Tonic.ai’s Fabricate product is the only one with an actual self-serve dollar price above free: $0 to start, $29/month for the Plus tier. Gretel and MOSTLY AI both run on a credits model where the free tier is clearly defined — Gretel measures it in records and characters, MOSTLY AI in a simple daily/monthly credit cap — but neither publishes a dollar figure for what comes next; both require talking to sales once you outgrow the free allotment. All three are selling the same underlying idea: generate statistically realistic fake data that preserves the structure and relationships of real data (for ML training, testing, or compliance) without exposing the real records.
What Each Platform Actually Is
Gretel
Gretel’s free “Getting Started” tier gives you a monthly credit allotment usable across several of its tools: Workflows (high-quality synthetic record generation, 1 credit = 5 minutes of API duration), Transform, PII detection, or the Navigator inference API (1 credit = 100,000 input/output characters). The free tier is capped at 2 concurrent workers. Credits reset monthly and don’t roll over. Beyond the free allotment, Gretel’s pricing page gives only a heading — “Upgrade to power your most critical use cases” — with no listed quantities or prices; its FAQ confirms additional credits require contacting sales.
Tonic.ai
Tonic.ai actually spans three distinct products with separate pricing. Fabricate (synthetic data generation) has a genuinely public, self-serve price ladder: Free ($0/month, $5 in monthly credits, no card required) and Plus ($29/month, $25 in monthly credits plus pay-as-you-go overage), both running on Tonic Cloud, with a custom Enterprise tier above that. Structural (de-identifying structured/database data) and Textual (de-identifying unstructured/text data) are both sold separately, entirely on custom or usage-based enterprise quotes with no public dollar figures.
MOSTLY AI
MOSTLY AI’s public pricing page lists three tiers without naming dollar amounts for any of them: a Free tier (forever free, capped at 2 credits per day up to 25 per month, one active chat, SaaS-only), a Cloud Marketplace tier deployed through AWS Marketplace into your own AWS environment (one platform installation, unlimited usage, SSO support), and a Custom Deployment tier for on-prem or private-cloud installs (unlimited usage, SSO, at least one platform installation). Actual pricing for the two paid tiers requires using the page’s “View pricing plans” link or contacting sales directly.
Trade-offs
Gretel’s free tier is generous and clearly quantified, making it easy to prototype, but there’s no visible self-serve path past it — every larger use case routes to a sales conversation.
Tonic.ai is the only one of the three with a real credit-card-and-go paid tier ($29/month Plus), but that pricing applies only to its Fabricate product; its Structural and Textual de-identification products are both enterprise-quoted separately.
MOSTLY AI’s free tier is the most restrictive of the three on a daily basis (2 credits/day cap) but is explicitly “forever free,” and its paid tiers add real deployment flexibility (your own AWS account, or fully on-prem) rather than just more credits.
Who It’s a Good Fit For
Gretel fits teams that want to prototype synthetic-data workflows quickly using a generous, well-defined free tier before committing to a paid conversation. Tonic.ai fits teams whose main need is synthetic test data generation (Fabricate) and who want an actual self-serve paid tier, or larger enterprises that also need structured/unstructured data de-identification as separate, dedicated products. MOSTLY AI fits regulated or security-conscious organizations that specifically want the option to deploy entirely inside their own AWS account or on-premises rather than relying on a vendor-hosted SaaS.
Bottom Line
Start with whichever free tier matches your use case — Gretel for record/character-based prototyping, Tonic Fabricate if you want a real credit-card paid tier waiting at $29/month, MOSTLY AI if on-prem or your-own-cloud deployment is a requirement from day one. Expect a sales conversation for anything beyond entry-level usage with all three.
FAQ
Which of these three has a real self-serve paid plan?
Only Tonic.ai’s Fabricate product publishes a specific self-serve paid price: $29/month for its Plus tier. Gretel and MOSTLY AI both require contacting sales for pricing beyond their free tiers.
Can I deploy any of these fully on my own infrastructure?
MOSTLY AI explicitly offers a Custom Deployment tier for on-prem or private-cloud use. Tonic’s Structural and Textual products also support Cloud or self-hosted deployment on their Enterprise tiers.
Do free-tier credits roll over month to month?
Gretel’s FAQ states free monthly credits reset each month and do not roll over. Tonic.ai and MOSTLY AI’s pages do not explicitly address rollover for their free tiers.
Pro $20/mo, Max $100/mo, Team $500/mo (early access), Enterprise custom — all for optional cloud/hosted model access
Developers who want a scriptable local-model runtime with an optional cloud tier
LM Studio
Free, includes local models via llama.cpp/MLX and the Bionic agent
Bionic+ $20/mo, Pro $100/mo, Teams custom — for hosted models and expanded web search
Users who want a polished GUI plus an agent that can also reach hosted models
Jan
Free and open source, full stop
None required — can optionally connect your own API keys for ChatGPT, Claude, or Gemini
Users who want a fully open-source app with no paid tier at all
Short Verdict
Running an open model on your own machine is free with all three tools — that part of the pitch holds up. Where they diverge is what you get if you want more than your laptop’s GPU can deliver. Ollama is the developer-first, CLI-and-API-driven runtime with optional paid cloud tiers layered on top for access to larger hosted models. LM Studio wraps the same core idea (llama.cpp and MLX under the hood) in a more consumer-facing GUI and its own Bionic agent, with its own paid cloud add-ons. Jan is the purist’s choice: free and open source with no subscription tier published at all, though it can optionally call out to paid hosted APIs (ChatGPT, Claude, Gemini) if you bring your own key.
What Each Tool Actually Is
Ollama
Ollama is a command-line-first tool (with a GitHub repo carrying over 186,000 stars) for pulling and running open models locally on macOS, Windows, and Linux, with a simple REST API that’s become a de facto standard other tools build against. Running models locally has no subscription cost and is, per Ollama’s own pricing page, “always unlimited.” On top of that free local runtime, Ollama sells optional cloud tiers: Pay-as-you-go ($0 base, pay per token for cloud-hosted models), Pro ($20/month, $60 in monthly usage credits, access to larger Pro models), Max ($100/month, $300 in credits), and Team ($500/month early-access price, unlimited users, $1,000 in shared credits), plus a custom Enterprise tier.
LM Studio
LM Studio packages local-model running behind a desktop GUI, built on llama.cpp and MLX runtimes, and now centers its pitch on “Bionic,” its agent for working with open models on agentic tasks. The Free tier ($0) includes the Bionic agent, local models, offline voice transcription, and device linking across up to five devices, with limited web search. Bionic+ ($20/month) adds US-hosted open-source models, discounted bulk tokens, and full web search with page extraction. Pro ($100/month) adds five-times the usage limits and early feature access. A Teams tier offers centralized, pooled or seat-based billing with no published price.
Jan
Jan describes itself as “Free & open source” and positions itself as an open alternative to ChatGPT: a desktop app that runs open models locally or, if you supply your own API key, connects out to hosted models from OpenAI, Anthropic, or Google. There’s no subscription tier on Jan’s own side — any cost you incur comes from the API keys you bring, not from Jan itself.
Trade-offs
Ollama is the closest thing to an industry-standard local-model API, which matters if you’re wiring it into other tools, but its cloud tiers (Pro/Max/Team) exist specifically to get you off your own hardware for bigger models — read the fine print before assuming “local” and “free” always go together once you touch those tiers.
LM Studio has arguably the most polished GUI of the three and bundles an agent experience, but its free tier’s web search is explicitly “limited,” with full search gated behind the $20/month Bionic+ tier.
Jan has no paid tier to evaluate at all, which simplifies the decision, but also means less corporate backing behind features like a managed cloud-hosting option — you’re more on your own for infrastructure beyond your local machine.
Who It’s a Good Fit For
Ollama fits developers who want a scriptable, API-first local runtime they can build other tools on top of, with an optional paid cloud escape hatch for bigger models. LM Studio fits users who want a friendlier GUI and an agent experience out of the box, and who don’t mind paying for expanded web search and hosted models. Jan fits anyone who wants a fully open-source app with zero subscription pressure, especially if they’re comfortable bringing their own API keys for occasional hosted-model use.
Bottom Line
All three are free to start and genuinely useful for running open models on your own hardware. Pick Ollama if you’re building on top of it programmatically, LM Studio if you want the most polished all-in-one GUI and agent, and Jan if you want to stay entirely within open-source tooling with no paid tier in the picture.
FAQ
Do I need to pay to run models locally with any of these?
No. Local model execution is free with Ollama, LM Studio, and Jan. Paid tiers on Ollama and LM Studio apply only to optional cloud-hosted models and expanded features, not to running open models on your own hardware.
Is Ollama open source?
Ollama’s client is distributed via a public GitHub repository (github.com/ollama/ollama) with over 186,000 stars; check that repository directly for its current license terms before relying on a specific license for commercial use.
Can Jan connect to Claude or ChatGPT instead of a local model?
Yes. Jan can connect to hosted models including ChatGPT, Claude, and Gemini if you provide your own API key for those services; Jan itself charges nothing for this.
$0.18/hr for 2-core (scales up), $0.07/GB-month storage; 120 free hours/mo on Free plan, 180 on Pro
Teams already on GitHub wanting disposable, pay-as-you-go cloud dev environments
Gitpod / Ona
Ona’s cloud or your own VPC
No public pricing — sales-only as of 2026
Teams wanting AI software-engineering agents plus standardized cloud dev environments, self-hosted or managed
Local Dev Containers
Your own machine, via VS Code or any devcontainer-compatible editor
Free — open specification, no hosting cost
Developers who want reproducible environments without paying for cloud compute
Short Verdict
All three of these build on the same underlying idea — a reproducible, declarative development environment defined in code (typically a devcontainer.json file) — but they diverge sharply on where that environment actually runs and what it costs. GitHub Codespaces runs it in GitHub’s cloud with clear, published per-hour and per-GB pricing. Gitpod has, in 2026, rebranded to Ona and repositioned itself around AI software-engineering agents rather than cloud IDEs alone; its pricing page now redirects straight to a sales contact form with no public numbers. Running Dev Containers locally — via the VS Code Dev Containers extension or any compatible tool — costs nothing beyond your own machine, at the cost of using your own CPU, RAM, and disk instead of someone else’s.
What Each Option Actually Is
GitHub Codespaces
Codespaces spins up a containerized VS Code (or JetBrains Gateway, or terminal-only) environment in GitHub’s cloud, defined by a devcontainer.json in the repo. Compute is billed per hour by machine size — $0.18/hour for a 2-core instance, scaling linearly up to $2.88/hour for 32 cores — and storage is billed at $0.07 per GB-month. Free personal accounts get 120 core-hours and 15 GB-months per month; GitHub Pro gets 180 core-hours and 20 GB-months. Organization and Enterprise accounts get no free Codespaces quota by default and pay the metered rate from the first hour.
Gitpod / Ona
Gitpod’s pricing page now redirects to ona.com, where the product is described as “mission control for software projects and software engineering agents” and, notably, as “Part of OpenAI.” The sign-in flow still runs through app.gitpod.io, and Ona still offers standardized cloud development environments, but the pitch has shifted toward AI agents handling engineering tasks end-to-end, deployable either in Ona’s own cloud or inside a customer’s VPC. There is no published pricing page — every plan requires contacting sales, with the intake form asking for company size (1 to 1,001+ engineers) and cloud provider.
Local Dev Containers
The Dev Containers specification itself (devcontainer.json, maintained as an open standard) just describes a container-based development environment: base image, extensions, ports, post-create commands. Run it locally with Docker Desktop, Podman, or OrbStack and the VS Code Dev Containers extension, and you get the exact same reproducible environment Codespaces and Ona use — just on your own hardware, for free, with no per-hour or per-GB bill.
Trade-offs
GitHub Codespaces has the clearest, most self-serve pricing of the three and needs zero local setup, but costs scale directly with usage and the free quota disappears entirely for organization accounts.
Gitpod/Ona is now positioned more as an AI-agent platform than a plain cloud IDE, and with pricing fully hidden behind a sales form, it’s a harder tool to evaluate casually compared to its earlier self-serve tiers.
Local Dev Containers cost nothing and keep everything on your own machine, but you’re responsible for your own compute capacity, and there’s no built-in way to hand a teammate an instant, identical cloud environment the way Codespaces or Ona can.
Who It’s a Good Fit For
GitHub Codespaces fits teams already living on GitHub who want disposable, pay-as-you-go cloud environments with predictable, published costs. Gitpod/Ona fits organizations evaluating AI software-engineering agents alongside standardized dev environments and willing to go through a sales conversation to get there. Local Dev Containers fit individual developers and smaller teams who want reproducibility without a recurring cloud bill, and who are comfortable running Docker locally.
Bottom Line
If you just want reproducible environments, start with local Dev Containers — it’s free and uses the same spec the paid clouds run on. Move to Codespaces once you need on-demand cloud capacity with transparent pricing, and only evaluate Gitpod/Ona if you’re specifically interested in its AI-agent direction and are prepared to talk to sales to see numbers.
FAQ
Did Gitpod get acquired?
Gitpod’s pricing and sales pages now operate under the Ona brand, whose site describes itself as “Part of OpenAI.” Sign-in still runs through the original app.gitpod.io domain.
Is the Dev Containers spec tied to any one vendor?
No. devcontainer.json is an open specification used by VS Code, GitHub Codespaces, Gitpod/Ona, and other compatible tools — the same container definition can run locally or in any of these clouds.
Do GitHub organization accounts get free Codespaces hours?
No. Per GitHub’s billing documentation, free Codespaces quotas apply only to personal accounts (120 hours on Free, 180 on Pro); organization and enterprise accounts are billed from the first hour.
Enterprise only, starts at $16K/year minimum, scales with team size
Large orgs needing cross-repo search, code insights, and AI agents over proprietary code
GitHub Code Search
Public GitHub + your private repos
Free, built into GitHub
Anyone already on GitHub who needs fast, syntax-aware search with no setup
grep.app
~1M+ public GitHub repos only
Free, no account needed
Quick ad-hoc searches of open-source code, no login required
Short Verdict
These three tools aren’t really competing for the same budget line. GitHub Code Search and grep.app are both free and solve “find this string or pattern across a pile of code” — one scoped to GitHub’s own index (public plus whatever private repos you can see), the other to roughly a million public repositories, no login required. Sourcegraph is a different animal entirely: as of 2026 it’s gone fully enterprise, with a published starting price of $16,000 a year, and it bundles search with AI code intelligence (its Cody-descended Deep Search), code insights, batch changes across repos, and an MCP server for wiring it into Claude Code, Cursor, Codex, and other agentic coding tools.
What Each Tool Actually Is
Sourcegraph
Sourcegraph indexes your organization’s own codebases — across every repo and every code host you connect — and layers search, symbol navigation, code monitoring, and “batch changes” (large-scale automated refactors) on top. Its pricing page lists a single Enterprise plan starting at $16,000/year, billed as a minimum annual contract that scales with team size, with volume pricing available at larger scale. It explicitly supports both single-tenant cloud and fully self-hosted deployment, which matters for teams with strict data-residency requirements. AI credits for Deep Search and Cody-style assistance are included per user and can be pooled org-wide, though the exact credit allotment per user isn’t published.
GitHub Code Search
GitHub’s own code search is built directly into github.com at no additional cost beyond whatever GitHub plan you’re already on (including the free tier). It supports exact-match and regex-style queries, language and path filters, and symbol search, and it indexes both public repositories and any private repositories your account can already see. Because it’s native to GitHub, there’s zero setup: no indexing pipeline to run, no separate login.
grep.app
grep.app is a small, free, independently run search engine over roughly a million public GitHub repositories. It’s built for the specific case of “how do other open-source projects use this API or pattern” — fast regex search with syntax highlighting, filterable by language and repo, with no account, no rate-limited API key, and no private-repo access at all. A community CLI (grep-app-cli) and an editor extension also wrap its search for use outside the browser.
Trade-offs
Sourcegraph is the only one of the three built for searching and governing your own private, multi-repo, multi-host codebase at enterprise scale — but at a $16K/year minimum, it’s not a tool you adopt casually, and smaller teams will find it hard to justify without a genuine cross-repo search or large-scale refactor problem.
GitHub Code Search is free and already where most teams’ code lives, but it only sees what your GitHub account can see — it’s not built for searching across code hosted on GitLab, Bitbucket, or an internal server alongside GitHub.
grep.app is the fastest way to answer “how does the rest of open source do this,” but it’s public-only: no private repos, no org-wide indexing, and no code intelligence beyond text and regex matching.
Who It’s a Good Fit For
Sourcegraph fits engineering organizations with dozens or hundreds of repositories across multiple code hosts who need unified search, code insights, and AI agents that understand the whole codebase — and who have budget for an enterprise contract. GitHub Code Search fits essentially everyone else whose code already lives on GitHub and who just needs fast, free search with no new tool to adopt. grep.app fits individual developers researching how a library or pattern is used across the open-source ecosystem, independent of where their own code lives.
Bottom Line
Start with GitHub Code Search or grep.app — both are free and solve most day-to-day searches instantly. Reach for Sourcegraph only once you have a genuine multi-repo, multi-host, enterprise-scale search or refactor problem that’s worth a five-figure annual budget line.
FAQ
Is there a free or self-serve tier of Sourcegraph?
As of 2026, Sourcegraph’s public pricing page lists only its Enterprise plan starting at $16,000/year; it does not publish a free self-serve tier.
Can grep.app search my company’s private code?
No. grep.app only indexes public GitHub repositories; it has no mechanism for private-repo access.
Does GitHub Code Search work across GitLab or Bitbucket repos?
No. It only indexes repositories hosted on GitHub itself, public or private, that your account can access.
Teams that want a CDP built on an event pipeline, with a free trial to start
Monthly Tracked Users (MTU), custom volume
Connections pricing partially published; full CDP (Unify + Engage) is quote-only
Rokt mParticle
Retail and loyalty brands wanting audience activation tied to Rokt’s ad network
Custom quote
No public pricing
Tealium
Enterprises that want tag management and a CDP from one vendor
Custom quote, typically annual contract
No public pricing
Short Verdict
All three customer data platforms compared here are sold the same way: nobody lists a price on their website, and every serious deployment ends with a sales call. Twilio Segment is the most self-serve-friendly of the three, with a free trial for its Connections product and a published (if not fully itemized) pricing page based on Monthly Tracked Users. Rokt mParticle — the former mParticle, now repositioned under Rokt’s ad-tech umbrella since its 2024 acquisition — leans hardest into audience activation for retail and loyalty programs. Tealium remains the choice for teams that want tag management (its original product) and a CDP bundled under one contract. None of this is a knock against any of them; it’s simply how enterprise CDP buying works in 2026.
What Each Platform Actually Is
Twilio Segment
Segment started as an event-collection pipeline (“Connections”) that routes customer events from your app or site to hundreds of downstream destinations — analytics tools, ad platforms, warehouses. Twilio acquired it in 2020. The full CDP tier adds Unify (identity resolution that stitches anonymous and known profiles into one record) and Engage (audience building and journey orchestration). Segment is the most developer-centric of the three: it ships SDKs, a public API, Functions for custom transforms, and Reverse ETL to push warehouse data back out to tools.
Rokt mParticle
mParticle built its name on mobile and omnichannel data collection with strong identity resolution. After Rokt’s 2024 acquisition, the product was rebranded Rokt mParticle and repositioned around what the company calls a “performance CDP”: a hybrid real-time-and-warehouse architecture paired with an mParticle Agent for building audiences conversationally, plus packaged “Performance Accelerators” (Match Boost, Audience Expansion, Household Reach, Predictive Audiences) aimed at turning first-party data directly into acquisition and retention campaigns rather than just routing events.
Tealium
Tealium’s roots are in tag management (Tealium iQ) — the system that lets marketing teams add and control third-party scripts on a site without touching code. It layered a CDP (Customer Data Hub, AudienceStream, EventStream) on top of that same data layer, so a Tealium customer is often buying both tag governance and audience building in one contract rather than starting from a greenfield CDP decision.
Pricing: What’s Actually Public
This is the section where honesty matters more than a tidy table. As of this writing:
Twilio Segment publishes a pricing page for its standalone Connections product, billed by custom MTU volume with unlimited seats and invoice billing; the full Customer Data Platform tier (Connections + Unify + Engage) says only “contact us for plan and add-on pricing.” No flat per-seat or per-MTU dollar figure for the full CDP is published on twilio.com.
Rokt mParticle’s official platform page lists no pricing at all — only “talk to an expert” and “contact us” links.
Tealium’s pricing page is the same: no published tiers or dollar amounts. Third-party vendor-pricing trackers (not Tealium itself) estimate enterprise contracts in the tens of thousands to several hundred thousand dollars per year depending on data volume, but that figure comes from aggregator sites, not from Tealium, so treat it as a rough directional estimate rather than a quote.
If your organization is budgeting for a CDP, the realistic first step with any of these three is a scoping call, not a self-serve checkout — Segment included, once you move past its entry-level Connections tier.
Trade-offs
Segment is the easiest to pilot cheaply and the most API/developer-friendly, but the jump from Connections to the full CDP (identity resolution and audiences) is where cost and complexity both step up.
Rokt mParticle is strongest when your real goal is activating audiences into paid acquisition — especially if you’re open to Rokt’s broader ad network — but it’s a heavier commitment to evaluate since almost nothing about scope or cost is self-serve.
Tealium makes the most sense when you already depend on Tealium iQ for tag management and want one vendor and one data layer for both jobs, rather than running a CDP alongside a separate tag manager.
Who It’s a Good Fit For
Twilio Segment fits engineering-led teams that want to start with a lightweight, well-documented event pipeline and grow into identity resolution later. Rokt mParticle fits retail, travel, and loyalty brands whose main CDP use case is turning customer data into acquisition and lifecycle campaigns, particularly if they’re already Rokt advertising customers. Tealium fits enterprises — often regulated or large-catalog retail — that want tag governance and a CDP under a single long-term contract and don’t mind a heavier, more sales-led buying process from day one.
Bottom Line
There is no cheap, self-serve way to compare these three on price — budget a scoping conversation with each before you commit, and use the free trial on Segment’s Connections tier to validate the data-pipeline mechanics before you negotiate the bigger CDP contract with any of the three.
FAQ
Does Segment have a free plan?
Segment’s FAQ mentions a free trial for the standalone Connections product; the full CDP tier is quote-only with no published free tier.
Is mParticle still called mParticle?
Its official branding today is “Rokt mParticle,” reflecting Rokt’s 2024 acquisition of the company; the product still carries the mParticle name in the combined brand.
Can I get exact CDP pricing without a sales call?
Not from any of the three vendors’ own websites as of this writing — all three require contacting sales for a quote once you move past Segment’s entry-level Connections pricing.
Influencer marketing platforms handle creator discovery, outreach, contracting, and payment at scale — but almost none of them publish a simple price list the way most SaaS tools do. Of the three biggest names, only GRIN currently lets you see exact numbers without booking a call. Here’s what that means for brands shopping this category in 2026.
Free (20% fee on wallet deposits); Starter $200/mo (10% fee)
Flat monthly fee + a declining management fee on ad/gifting spend
Yes — full self-serve price list
Brands that want to see exact costs before talking to sales
Upfluence
Not published — custom quote after a sales call
Fixed platform fee by module, not a percentage of creator sales
No
Brands running structured, multi-module creator programs with dedicated budget
Short Verdict
GRIN is the only one of the three you can price out entirely on your own, and its tiered structure — a flat monthly fee plus a management fee that drops from 20% to 5% as you commit to a higher tier — is unusually transparent for this category. Aspire and Upfluence both require a sales conversation before you see a number, which is standard for enterprise creator-marketing software but makes early-stage budget comparison difficult. Upfluence is at least explicit that its fee is a fixed platform charge rather than a cut of creator payouts, which is a meaningfully different economic model from GRIN’s declining-percentage structure.
What Each Platform Actually Is
Aspire (formerly AspireIQ) is positioned as an enterprise creator-marketing platform covering discovery, UGC licensing, affiliate/influencer payouts, and campaign management. Its public site offers an “Enterprise” overview and demo request rather than a pricing or plans page, and third-party buyer reports consistently describe it as a sales-led, custom-quoted product with no self-serve tier.
GRIN sells five tiers, each combining a flat monthly fee with a management fee charged on top of money you deposit into your GRIN wallet for creator payments. Free costs nothing but carries a 20% fee on deposits and caps you at 2 live campaigns and 10 total gifted products. Starter ($200/mo) drops the fee to 10% and removes the campaign cap. Growth ($500/mo, 7% fee) adds support for multiple brands on one account. Scale ($1,500/mo, 5% fee) raises gifting and search volume further. Enterprise is custom-quoted with an annual agreement. GRIN states creators keep 100% of what they’re paid — the fee is charged to the brand, not deducted from creator payouts.
Upfluence organizes its offering around three capability tiers rather than price points: “Find Creators” (search and outreach at scale), “Scale Creator Programs” (adds AI-assisted campaign launch, e-commerce integrations, affiliate tracking, and a creator marketplace), and “Run Programs on Autopilot” (adds end-to-end AI campaign management, global payouts, and tax/invoicing support via Upfluence Pay). Upfluence states explicitly that it charges a fixed platform fee rather than a percentage of creator sales, with no mandatory setup fee and a minimum 12-month term on annual contracts.
Pricing Comparison
Plan Tier
Aspire
GRIN
Upfluence
Entry
No published tier — quote only
Free: $0/mo + 20% fee on deposits — 2 campaigns, 10 gifts total
Find Creators: custom quote — creator search and outreach
Run Programs on Autopilot: custom quote — adds full AI automation, global payouts, Upfluence Pay
Top
Enterprise — fully custom
Scale: $1,500/mo + 5% fee — 1,000 gifts/mo, 120,000 searches/mo; Enterprise above that is fully custom
No self-serve top tier — all pricing requires a sales call
GRIN’s management fee is non-refundable even if wallet funds go unspent, and paid partnership or affiliate campaigns require a minimum $250 wallet deposit (gifting-only campaigns don’t). Upfluence requires at least an initial sales call even to start a free trial. Neither Aspire nor Upfluence publishes a minimum contract value, so brands should budget for an enterprise-style sales cycle with either platform.
Trade-offs
Aspire pros: established enterprise feature set covering UGC licensing and affiliate payouts alongside influencer discovery, widely used by larger consumer brands.
Aspire cons: zero public pricing information, making it impossible to shortlist on cost alone before a sales conversation.
GRIN pros: the only fully self-serve, transparently priced option of the three, with a management fee that declines as spend commitment rises; creators keep 100% of payouts.
GRIN cons: the combination of a flat fee plus a percentage fee on deposits makes total cost harder to predict than a pure per-seat SaaS price, especially at the Free tier’s 20% rate.
Upfluence pros: a fixed-fee model (not a cut of creator sales) and built-in global payout/tax handling via Upfluence Pay on its top tier.
Upfluence cons: no public pricing at all, and a mandatory 12-month minimum term on annual contracts commits you before you’ve seen a competitor’s number.
Who Each Platform Is a Good Fit For
Choose Aspire if you’re a larger brand already evaluating enterprise creator-marketing suites and UGC licensing is as important to you as influencer discovery itself.
Choose GRIN if you want to see real numbers and start small — its Free and Starter tiers let you test the platform with a real budget before any sales conversation.
Choose Upfluence if you’re ready to commit to a 12-month program and specifically want a fixed-fee pricing model rather than one tied to a percentage of creator spend.
Bottom Line
If price transparency matters to you at all in this category, GRIN is the obvious starting point simply because it’s the only one of the three that will show you numbers without a sales call. That doesn’t make it automatically the cheapest or the best fit — Aspire’s and Upfluence’s enterprise features may justify their sales-led pricing for larger programs — but it does mean most brands should get a GRIN quote first to establish a cost baseline before evaluating the two platforms that require a call just to see a price.
FAQ
Why don’t Aspire and Upfluence publish pricing? Both are positioned as enterprise B2B software sold through a sales-led process, where pricing is customized to the brand’s campaign volume, creator count, and which modules they license — a common pattern in enterprise martech that GRIN’s self-serve model deliberately departs from.
Does GRIN take a cut of what creators are paid? No. GRIN’s official pricing page states that creators keep 100% of their earnings; GRIN’s management fee is charged to the brand on top of wallet deposits, not deducted from creator payouts.
Is Upfluence’s fee based on a percentage of sales? No. Upfluence’s official pricing page states its fee structure is a fixed platform fee rather than a percentage of creator sales, which differs from GRIN’s declining-percentage model on deposits.
Can I try any of these platforms for free? GRIN offers a genuinely free tier with real (if limited) functionality. Upfluence offers a free trial, but only after an initial sales call. Aspire’s public site offers a demo request rather than a self-serve trial.
Mainstream webmail providers scan and index your messages to run their business; encrypted-first providers build around not being able to read your mail at all. Proton Mail, Tuta, and Mailbox.org all offer end-to-end encryption and zero-access storage, but they differ sharply on jurisdiction, pricing structure, and how much encryption actually covers. Here’s how their 2026 plans compare.
At a Glance
Provider
Entry Paid Price
Free Tier
Jurisdiction
Best For
Proton Mail
$2.49/mo billed annually (Mail Plus, 15GB)
1GB storage, 1 address
Switzerland
Users wanting the most polished app plus a wider privacy suite (VPN, Drive, Pass)
Tuta
~€3.60/mo (Revolutionary, 20GB) — per third-party price tracking; confirm on tuta.com
1GB storage, no custom domain
Germany
Budget-conscious users wanting strong encryption without extra apps
Mailbox.org
€3–4/mo billed annually (Standard, 20GB mail + 10GB Drive)
No permanent free tier (trial only)
Germany
Users wanting a traditional IMAP/webmail experience with full groupware (calendar, contacts, Office)
Short Verdict
Proton Mail has the most polished apps and the broadest ecosystem — its paid tiers bundle a VPN, cloud storage, and a password manager, not just email. Tuta is the cheapest meaningfully encrypted option and encrypts more metadata (including subject lines) by default than Proton on its free tier, but its smaller team means a thinner feature set overall. Mailbox.org is the odd one out: it doesn’t do full end-to-end encryption by default the way Proton and Tuta do — it relies more on PGP and at-rest encryption — but it offers the most traditional, IMAP-compatible groupware experience of the three, which matters if you need standard email-client compatibility.
What Each Provider Actually Is
Proton Mail, based in Switzerland, is built on zero-access encryption — Proton holds the encrypted data but not the keys to read it. Free gives 1GB and one address. Mail Plus ($2.49/mo annual) raises that to 15GB, 10 addresses, and 1 custom domain. Proton Unlimited ($6.49/mo annual) bundles 500GB of combined storage, 15 extra addresses, 3 custom domains, and access to Proton’s other apps (VPN, Drive, Pass password manager, Calendar) under one subscription. Business tiers are priced per user per month separately from the personal plans.
Tuta, based in Germany, encrypts not just message bodies but also subject lines, contacts, and calendar entries by default — a step further than Proton’s free tier. Free includes 1GB of storage and no custom domain. Revolutionary adds roughly 20GB of storage, 3 custom domains, and 15 extra aliases; Legend scales that to around 500GB storage, 10 custom domains, and 30 aliases, per Tuta’s own feature comparison. Tuta runs frequent promotions (its site currently advertises up to 12 months free on annual billing), so always check the live page rather than assuming a fixed price.
Mailbox.org, also based in Germany, is structured more like traditional business email with privacy add-ons than a default end-to-end-encrypted inbox — encryption is typically applied via OpenPGP for message content, with encrypted-at-rest storage, rather than Proton’s or Tuta’s always-on end-to-end model. Light (€1/mo) is a minimal 2GB mailbox with no Drive storage. Standard (€3–4/mo) adds 20GB of mail storage and 10GB of Drive storage. Premium (€9–12/mo) raises that to 50GB mail and 100GB Drive, plus extra alias allowances. Business service packages (Silver/Gold/Platinum) scale up to unlimited mailboxes for organizations.
Pricing Comparison
Plan Tier
Proton Mail
Tuta
Mailbox.org
Free
$0 — 1GB, 1 address
$0 — 1GB, no custom domain
No permanent free tier
Entry paid
Mail Plus: $2.49/mo (annual) — 15GB, 10 addresses, 1 domain
From $7.99/user/mo — separate business tiers with higher storage/domain limits
Business plans sold separately from personal tiers
Business packages: €1–€12/user/mo plus Silver/Gold/Platinum service tiers (€25–€250/mo) for larger mailbox counts
Tuta’s own pricing page did not render exact plan prices during this review, and its site shows frequent limited-time promotions (currently advertising up to 12 months free on annual billing), so the figures above are sourced from third-party price tracking rather than Tuta’s page directly — confirm the live number on tuta.com before subscribing.
Trade-offs
Proton Mail pros: the most polished mobile/desktop apps of the three, and paid tiers bundle a full privacy suite (VPN, Drive, password manager) rather than just email.
Proton Mail cons: the free tier’s 1GB storage is the tightest of the three relative to what paid tiers offer, and the full Unlimited suite costs more than Tuta’s or Mailbox.org’s equivalent tiers.
Tuta pros: encrypts subject lines and calendar data by default even on free, and its paid tiers are consistently the cheapest of the three for comparable storage.
Tuta cons: a much smaller app/feature ecosystem than Proton (no bundled VPN or password manager), and its own pricing page is harder to read exact figures from than its competitors’.
Mailbox.org pros: the most traditional, IMAP/SMTP-compatible groupware experience — useful if you need standard email client support, shared calendars, and Office document integration.
Mailbox.org cons: encryption is less consistently end-to-end by default than Proton’s or Tuta’s model, and there’s no permanent free tier to try it risk-free.
Who Each Provider Is a Good Fit For
Choose Proton Mail if you want the most polished, feature-rich experience and are willing to pay a bit more for a bundled privacy suite beyond just email.
Choose Tuta if budget and metadata encryption (subject lines, calendar) matter most and you don’t need Proton’s wider app ecosystem.
Choose Mailbox.org if you need a traditional, IMAP-compatible business email experience with groupware features, and full end-to-end encryption by default is less critical than compatibility with existing email clients and workflows.
Bottom Line
For most individuals specifically seeking encrypted email, it comes down to Proton versus Tuta: Proton for polish and a wider app suite, Tuta for the lowest price at comparable storage. Mailbox.org is a different kind of product — better thought of as privacy-conscious business email with groupware, not a direct end-to-end-encryption competitor to the other two — and it’s the right choice specifically when IMAP compatibility and shared calendars matter more than default end-to-end encryption.
FAQ
Is Mailbox.org fully end-to-end encrypted like Proton or Tuta? Not by default. Mailbox.org relies more heavily on OpenPGP for message content and encryption at rest, rather than Proton’s or Tuta’s always-on end-to-end encryption model, so the privacy guarantees differ even though all three market themselves as privacy-focused.
Which provider’s free plan is most generous? Mailbox.org does not offer a permanent free plan. Between Proton Mail and Tuta, both free tiers are capped at 1GB of storage and one address with no custom domain, per their official pricing pages.
Does Proton Mail include a VPN? Only on the Proton Unlimited plan ($6.49/mo annual) and above, which bundles Proton VPN, Proton Drive, and Proton Pass alongside Mail. The cheaper Mail Plus tier does not include VPN access.
Where are these companies legally based, and does it matter? Proton is based in Switzerland; Tuta and Mailbox.org are both based in Germany. All three operate under their respective national and EU data-protection laws, which is a meaningful factor for users specifically avoiding US-based providers subject to different legal data-request frameworks.
Identity theft protection services bundle a similar core — credit monitoring, dark web scanning, identity restoration, and insurance reimbursement — but price and structure that bundle very differently. Aura folds in a VPN, antivirus, and password manager at every tier; LifeLock (now sold under Norton) leans on its reimbursement guarantees; and Identity Guard splits its tiers by how much credit monitoring and family coverage you need. Here’s how their 2026 plans and pricing actually compare.
At a Glance
Service
Entry Individual Price
Identity Theft Insurance
Bundled Extras
Best For
Aura
$12/mo billed annually (Individual)
$1M (Individual), up to $5M (Family)
VPN, antivirus, password manager, data removal — all plans
People who want security tools bundled in, not just monitoring
1-bureau credit report/score, identity restoration specialists — all plans
Buyers who want clearly tiered reimbursement limits and Norton’s brand backing
Identity Guard
$7.50/mo billed annually (Value Individual)
$1M (Value/Total), up to $5M (Ultra)
Password manager, safe browsing, mobile app — all plans
Budget buyers who only need basic breach and dark web monitoring
Short Verdict
Aura packs the most security software into every tier — VPN, antivirus, and a password manager are included even on its cheapest Individual plan, which the other two don’t match without upgrading. LifeLock’s tiering is the clearest to compare on paper, with explicit reimbursement caps rising from $1.05 million on Core to $3 million on Total, and the backing of Norton’s broader security brand. Identity Guard is the cheapest entry price of the three, but its lowest Value tier skips 3-bureau credit monitoring and several monitoring categories that Total and Ultra include — and its own pricing page shows signs of not having been refreshed for 2026, so verify current numbers directly with the company before buying.
What Each Service Actually Is
Aura sells three household-based tiers rather than per-feature add-ons: Individual (1 adult, 10 devices), Couple (2 adults, 20 devices), and Family (5 adults, unlimited kids and devices). Every tier, including Individual, bundles 3-bureau credit monitoring, instant credit lock, antivirus, a VPN, a password manager, data-broker removal, and unused-account cleanup. Family adds child identity and SSN monitoring, child credit freeze, and parental controls. A separate Kids plan (parental controls only, no identity insurance) is sold apart from the identity-theft tiers.
LifeLock, now marketed primarily under the Norton umbrella, sells Core, Advanced, and Total tiers across Individual, 2-Adult, and 2-Adults-+-Kids household sizes. Core includes 1-bureau credit monitoring and 2 monitored accounts; Advanced steps up to 3-bureau monitoring and 5 monitored accounts; Total adds unlimited account alerts and the highest reimbursement limits. Norton also sells combined “Norton 360 with LifeLock” bundles (Select and Ultimate Plus) that fold in Norton’s antivirus and VPN alongside LifeLock’s identity monitoring.
Identity Guard sells Value, Total, and Ultra tiers, each offered in Individual and Family variants. Value covers breach, dark web, high-risk transaction, bank account, and USPS address-change monitoring, but its own feature list does not include 3-bureau credit monitoring, monthly credit scores, or an annual credit report — those appear starting on Total. Ultra adds the highest stated insurance coverage (“up to $5M”) and is Identity Guard’s recommended tier.
Pricing Comparison
Plan Tier
Aura
LifeLock (Norton)
Identity Guard
Entry
Individual: $12/mo annual ($15 monthly) — $1M insurance, full security suite
Individual Core: $10.42/mo annual ($124.99/yr) — 1-bureau monitoring, up to $1.05M
Value (Individual): $7.50/mo annual promo ($107.88/yr renewal) — basic breach/dark web monitoring
All three list introductory annual rates that renew higher — LifeLock states its renewal prices directly on its pricing page, while Identity Guard’s page shows separate “Save 16%” and “Save 50%” promotional rates alongside a stated renewal price, which is worth double-checking at checkout since promotional pricing changes frequently. Aura’s monthly-vs-annual gap is the most consistent of the three, running about 20–36% cheaper on an annual plan across all three household sizes.
Trade-offs
Aura pros: the only one of the three bundling a full VPN, antivirus, and password manager into every tier including the cheapest; simple three-tier household structure is easy to compare.
Aura cons: spam call protection is inconsistently listed as Family-only or an add-on across the pricing page, which is worth clarifying with support before purchase.
LifeLock pros: the clearest tiered reimbursement structure of the three, Norton’s long-standing brand and large customer base, explicit stolen-funds reimbursement caps rising to $1M on Total.
LifeLock cons: Core’s 2-bureau credit monitoring and 2-account alert cap are thin compared to Aura’s or Identity Guard’s entry tiers; VPN and antivirus require the separate Norton 360 bundles rather than being included in standalone LifeLock plans.
Identity Guard pros: the lowest promotional entry price of the three, and its Ultra tier states the joint-highest insurance coverage ($5M) alongside Aura’s Family plan.
Identity Guard cons: its Value tier skips 3-bureau credit monitoring entirely, and its public pricing/plans page shows a 2025 copyright notice and promotional codes referencing prior years — confirm current prices directly before buying.
Who Each Service Is a Good Fit For
Choose Aura if you want one subscription that replaces several separate tools — VPN, antivirus, password manager — alongside identity monitoring, especially for a couple or family.
Choose LifeLock if you want the most explicit, clearly tiered reimbursement guarantees and prefer a long-established brand, and you’re fine buying antivirus/VPN separately through a Norton 360 bundle if you want them.
Choose Identity Guard only for its cheapest Value tier if your needs are limited to basic breach and dark web alerts — step up to Total or Ultra (or look at Aura/LifeLock instead) if you want real credit monitoring bundled in.
Bottom Line
Aura offers the most consistent value at the entry tier because it doesn’t make you choose between identity monitoring and basic security software — you get both from the cheapest plan up. LifeLock is the safer choice if reimbursement caps and brand trust matter more to you than bundled software. Identity Guard can be the cheapest option on paper, but its lowest tier is noticeably thinner than the other two’s entry plans, and its pricing page’s apparent staleness means you should get a live quote rather than trust the listed numbers at face value.
FAQ
Do these services actually prevent identity theft? No identity theft service can prevent theft outright — they monitor for signs of it (dark web mentions, new accounts, credit inquiries) and provide insurance reimbursement and restoration support after the fact, per each company’s own plan descriptions.
Which service includes a VPN and antivirus by default? Aura is the only one of the three that bundles a VPN, antivirus, and password manager into every tier, including its cheapest Individual plan, per its official pricing page. LifeLock requires a separate Norton 360 bundle for antivirus/VPN, and Identity Guard includes only a password manager and safe browsing, not a full VPN or antivirus suite.
How much is each service’s insurance coverage? Aura offers up to $1M (Individual) to $5M (Family); LifeLock offers up to $1.05M (Core) to $3M (Total); Identity Guard states up to $1M (Value/Total) to “up to $5M” (Ultra) — all figures per each company’s own published plan pages.
Do prices shown renew at the same rate? No. All three advertise discounted first-term or annual rates that renew higher — LifeLock and Identity Guard both state specific renewal prices on their pricing pages, so check the renewal rate, not just the introductory rate, before subscribing.
Async video has become a real substitute for meetings — a 90-second screen recording often replaces a 30-minute call. Loom popularized the category, Vidyard pushes hardest into sales-team video analytics, and ScreenPal (formerly Screencast-O-Matic) undercuts both on price while keeping a surprisingly capable AI tier. Here’s how their 2026 pricing compares, including where each vendor stops publishing numbers.
At a Glance
Tool
Entry Paid Price
Free Tier
AI Features
Best For
Loom
$18/user/mo (Business)
25 videos, 5-min recordings, 720p, up to 50 members
Teams standardizing on a single polished async-video tool
Vidyard
Starter tier price not published
15 AI videos, 5 recordings/mo, 30 min max, no hosting
Video Agent add-on (unlimited AI videos, automated delivery), price not published
Sales teams wanting video analytics and CRM integration
ScreenPal
$4.00/mo billed annually (Deluxe)
15-min recordings, 10 hosted videos
ScreenPal AI on Max tier ($10/mo annual): auto-captions, AI narration, AI video generator
Budget-conscious individuals and small teams needing unlimited recording
Short Verdict
ScreenPal is the clear budget winner — its Deluxe tier at $4/month (annual) already removes the free plan’s recording-length and hosting caps, undercutting Loom’s Business tier by more than 75%. Loom remains the most polished and widely adopted of the three, and its Business+AI tier’s meeting-notes and recap features are genuinely useful for teams replacing real meetings with video. Vidyard is the hardest to evaluate on price alone: its free tier is the most restrictive of the three (just 5 recordings a month, capped at 30 minutes, with no hosting), and its paid Starter tier’s price isn’t published anywhere on its own pricing page.
What Each Tool Actually Is
Loom is the category-defining async video tool, now owned by Atlassian. Starter (free) caps at 25 total videos, 5-minute recordings, and 720p resolution across up to 50 workspace members. Business removes those caps entirely, adds 4K recording, Loom branding removal, password-protected videos, and engagement insights. Business+AI layers on auto-generated meeting notes, recap emails, summaries, chapters, and filler/silence removal. Enterprise adds SAML SSO, SCIM, custom data retention, and a 99.95% uptime SLA.
Vidyard is built for revenue teams — sales reps and marketers who send personalized video and track exactly who watched how much of it. Its free tier allows 15 AI-generated videos and 5 recorded videos a month (30-minute cap), with no video hosting included. Starter adds unlimited recording, full video analytics, branded sharing pages, and CTA templates, but Vidyard’s own pricing page does not disclose a dollar figure for it — only a “10% off” promotional label. Teams and Enterprise tiers add CRM/marketing-automation integrations and SSO, both quoted by invoice only.
ScreenPal is the budget-friendly option, with a free tier capped at 15-minute recordings and 10 hosted videos. Deluxe removes those caps and adds a full video editor and AI speech-to-text captions. Max adds ScreenPal AI: auto-captions and transcription, AI text-to-speech narration, an AI video generator, and unlimited quizzes/polls. Team Business layers on collaboration tools, team management, and SAML-based SSO, with a minimum of 3 creators.
Pricing Comparison
Plan Tier
Loom
Vidyard
ScreenPal
Free
$0 — 25 videos, 5-min cap, 720p, 50 members
$0 — 15 AI videos, 5 recordings/mo, 30-min cap, no hosting
$0 — 15-min recordings, 10 hosted videos
Entry paid
Business: $18/user/mo — unlimited videos/length, 4K, no branding
Starter: price not published — unlimited recording, analytics, branded pages
Deluxe: $4.00/mo (annual) — unlimited recording/hosting, full editor, AI captions
Mid
Business+AI: $24/user/mo — AI meeting notes, recaps, summaries
Loom’s annual billing saves up to 17% versus monthly. ScreenPal’s Team Business tier is already discounted 20% for annual billing on its public page. Vidyard is the only one of the three where a core paid tier’s price is simply absent from the public pricing page — budget for a sales call if you want an exact number.
Trade-offs
Loom pros: the most polished recording and editing experience of the three, strong AI meeting-notes features, broad brand recognition that makes shared links easy for recipients to trust.
Loom cons: the most expensive entry paid tier of the three by a wide margin, and AI features require the pricier Business+AI tier rather than being bundled into Business.
Vidyard pros: the deepest video analytics and CRM/sales-tooling integration of the three, purpose-built for tracking viewer engagement on outbound sales video.
Vidyard cons: the most restrictive free tier of the three, and its core paid tier’s price isn’t published — a real transparency gap compared to Loom and ScreenPal.
ScreenPal pros: by far the cheapest unlimited-recording tier of the three, and AI captioning/narration arrives at a much lower price point than Loom’s AI tier.
ScreenPal cons: smaller brand recognition and a less mature sales/marketing integration ecosystem than Vidyard, and its monthly (non-annual) pricing isn’t published for every tier.
Who Each Tool Is a Good Fit For
Choose Loom if your team wants the most polished, widely recognized async video tool and is willing to pay a premium for it, especially once AI meeting-notes features are part of the decision.
Choose Vidyard if you’re a sales or marketing team that specifically needs viewer-level video analytics and CRM integration, and you’re comfortable getting a quote rather than self-serving a price online.
Choose ScreenPal if cost is the deciding factor and you don’t need Vidyard’s sales analytics or Loom’s brand polish — its Deluxe and Max tiers deliver most of the same core recording and AI-captioning functionality for a fraction of the price.
Bottom Line
For most internal team communication, ScreenPal’s Deluxe or Max tier delivers nearly everything Loom’s Business tier does at a fifth of the price, and the gap is hard to justify unless your team specifically values Loom’s polish or its AI meeting-notes features. Vidyard only makes sense once video is tied directly to sales pipeline and you need to know exactly who watched what — otherwise, get a quote before assuming it fits your budget, since its own pricing page won’t tell you.
FAQ
How much does Vidyard’s Starter plan actually cost? Vidyard’s official pricing page does not list a dollar figure for its Starter tier — it shows only a “10% off” promotional label with no base price, so an exact number requires contacting Vidyard directly.
Does ScreenPal offer AI captioning on its cheapest paid plan? Basic AI speech-to-text captions are included starting on ScreenPal’s Deluxe tier ($4.00/mo, annual), per its official pricing page; the fuller ScreenPal AI suite (auto-captions, AI narration, AI video generator) requires the Max tier ($10.00/mo, annual).
What’s the recording-length limit on each free plan? Loom’s free Starter plan caps individual recordings at 5 minutes; ScreenPal’s free plan caps at 15 minutes; Vidyard’s free plan caps recorded videos at 30 minutes but limits you to 5 recordings a month and offers no video hosting.
Do any of these require a minimum number of seats? ScreenPal’s Team Business tier requires a minimum of 3 creators, per its official pricing page. Loom’s and Vidyard’s published tiers don’t state a seat minimum for their core paid plans.
Slack and Microsoft Teams are the default choices for workplace chat, but Discord has quietly become a real third option for startups, open-source projects, and creator-led businesses that want a faster, more casual tool than either. Their pricing models aren’t directly comparable — Slack and Teams sell seat-based business tiers with admin and compliance controls, while Discord sells individual cosmetic/perk subscriptions on top of a server model that was built for communities, not org charts. Here’s what that actually means for a team choosing between them in 2026.
At a Glance
Tool
Entry Paid Price
Free Tier
Admin/Compliance Controls
Best For
Slack
$7.25/user/mo billed annually (Pro)
90-day message history, up to 10 apps
SSO/SCIM from Business+ ($15/user/mo)
Businesses standardizing on integrations and searchable history
Microsoft Teams
$4.00/user/mo (Teams Essentials)
No standalone free business tier at this pricing level
Built into Microsoft 365 admin center across all paid tiers
Organizations already running Microsoft 365
Discord
$2.99/mo per person (Nitro Basic) — not a team/business plan
Full-featured free servers with no user cap
None native — relies on third-party bots and manual roles
Communities, open-source projects, and informal or dev-first teams
Short Verdict
Slack remains the most polished pure-chat experience with the deepest third-party app ecosystem, but SSO and SCIM don’t arrive until Business+ at $15/user/month. Microsoft Teams is the default if you’re already paying for Microsoft 365 — Teams Essentials at $4/user/month undercuts Slack’s Pro tier, and most organizations get Teams bundled into a Business Basic or Standard license they already hold. Discord is the outlier: its free tier is genuinely more generous than Slack’s or Teams’, with unlimited message history and no user cap, but it has no enterprise admin console, no SSO, and no compliance certifications built for regulated businesses — Nitro is a personal cosmetic subscription, not a business license.
What Each Tool Actually Is
Slack charges per user per month with four tiers. Free caps message history at 90 days and limits apps/integrations to 10. Pro removes those caps and adds group huddles and external Slack Connect messaging. Business+ adds SAML SSO, SCIM provisioning, data residency controls, full message export, and AI search. Enterprise+ adds unlimited Slackbot usage, multiple SAML configurations, audit logs, legal holds, native DLP, and information barriers — priced at $45/user/month with annual billing, per Slack’s published pricing page.
Microsoft Teams is sold both as a standalone product and bundled into Microsoft 365. Teams Essentials ($4/user/mo) covers meetings up to 30 hours and 300 participants with 10GB storage, but no Office apps. Microsoft 365 Business Basic ($7/user/mo) bundles Teams with web/mobile Office apps, business email, and 1TB of storage. Business Standard with Copilot ($23.50/user/mo) adds desktop Office apps and built-in Copilot AI. Teams Phone (cloud calling) is a separate add-on starting at $10/user/month, and Teams Premium (advanced meeting features) adds another $10/user/month.
Discord doesn’t sell seats or business licenses at all — every server is free to create and join, with no cap on members, channels, or message history. What it sells is Nitro, an individual subscription that unlocks personal perks: custom emoji everywhere, larger file uploads (50MB on Basic, 1GB on full Nitro), HD video streaming, and custom profile themes. None of this touches team administration — permissions, moderation, and integrations on a Discord server are handled through manually configured roles and third-party bots rather than a built-in enterprise admin console.
Pricing Comparison
Plan Tier
Slack
Microsoft Teams
Discord
Free
$0 — 90-day history, 10 apps, 1:1 huddles only
No equivalent standalone free business tier
$0 — unlimited members, channels, and history on any server
Entry
Pro: $7.25/user/mo (annual) — unlimited history/apps, group huddles
Teams Essentials: $4.00/user/mo — meetings up to 300 participants, 10GB storage
Nitro Basic: $2.99/mo per person — custom emoji, 50MB uploads (personal perk, not a seat license)
Mid
Business+: $15/user/mo (annual) — SSO/SCIM, data residency, AI search
Business Basic: $7.00/user/mo — Office web/mobile apps, 1TB storage, Teams included
Nitro: $9.99/mo per person — 1GB uploads, HD streaming, custom themes (still personal, not a team license)
Business Standard with Copilot: $23.50/user/mo — desktop Office apps + built-in Copilot AI
No business/enterprise tier exists
Slack’s monthly (non-annual) billing costs more across the board — $8.75/user for Pro and $18/user for Business+ — and the company runs a limited-time 50% discount for the first three months on monthly plans. Microsoft’s Teams Phone cloud-calling add-ons range from $10 to $34 per user per month depending on calling-plan minutes, which neither Slack nor Discord offers as a native feature at all.
Trade-offs
Slack pros: the largest third-party app marketplace of the three, well-regarded search and thread UX, flexible Slack Connect for cross-company channels.
Slack cons: SSO/SCIM gated behind Business+, and per-user pricing climbs quickly once you need Enterprise+ compliance features.
Microsoft Teams pros: deep Office/SharePoint/OneDrive integration, often already paid for inside an existing Microsoft 365 contract, strong video/meeting feature set.
Microsoft Teams cons: calling features require separate add-on licenses that get expensive fast, and the plan matrix (Essentials vs Business Basic vs Business Standard) is confusing to compare without a Microsoft rep.
Discord pros: genuinely unlimited free tier, fast and informal real-time chat and voice, strong for distributed open-source or dev-first teams already comfortable with it.
Discord cons: no SSO, no admin console or audit logs, no compliance certifications aimed at regulated industries, and Nitro doesn’t actually buy any team-management capability.
Who Each Tool Is a Good Fit For
Choose Slack if integrations and search matter more than cost, and you’re willing to pay for Business+ once you need SSO or compliance controls.
Choose Microsoft Teams if your organization already runs on Microsoft 365 — the marginal cost of adding Teams-based chat is usually lower than adding Slack on top of an existing Microsoft contract.
Choose Discord if you’re a community, open-source project, or small informal team that doesn’t need enterprise admin controls and wants a free, fast, voice-and-text-friendly space — not as a replacement for Slack or Teams in a regulated or compliance-sensitive business.
Bottom Line
Slack versus Teams is a real head-to-head for most businesses, and the honest tiebreaker is usually what you already pay for: if Microsoft 365 is in place, Teams is close to free; if it isn’t, Slack’s Pro tier is the easier sell at $7.25/user/month. Discord isn’t really competing in that decision — it’s the right tool when the “team” in question is a community, a side project, or a small technical group that would find Slack’s or Teams’ enterprise machinery like overkill, not when you need the admin, audit, and compliance tooling those two were actually built to sell.
FAQ
Does Discord have a business or team plan? No. Discord’s only paid consumer offering is Nitro, an individual subscription for cosmetic and utility perks (custom emoji, larger uploads, HD streaming). It has no seat-based business tier, SSO, or admin console comparable to Slack or Microsoft Teams.
Is Microsoft Teams free if I already have Microsoft 365? Teams is included in most Microsoft 365 Business plans, including Business Basic ($7/user/mo) and Business Standard with Copilot ($23.50/user/mo), per Microsoft’s official comparison page, so there’s no separate Teams license fee on top of those bundles.
When do I need Slack’s Business+ plan instead of Pro? As soon as you need SAML-based SSO, SCIM user provisioning, data residency controls, or compliance exports, since Slack’s Pro tier doesn’t include any of those, per Slack’s official pricing page.
Does Slack or Teams offer phone calling? Microsoft Teams does, through its separate Teams Phone add-ons ($10–$34/user/month depending on calling plan). Slack’s published pricing page does not list a native PSTN phone-calling product.
Survey tools split into roughly two camps: conversational form builders optimized for completion rates, and research platforms built for statistical rigor at enterprise scale. Typeform, SurveyMonkey, and Qualtrics sit at three different points on that spectrum — and their pricing reflects it, from clearly published per-response tiers down to a research platform that won’t publish a price list at all.
At a Glance
Tool
Entry Paid Price
Response Cap
Free Tier
Best For
Typeform
$39/mo monthly, $28/mo billed annually (Basic)
100 responses/mo on Basic; 10,000/mo on Business
Limited free plan (no paid-tier limits specified)
Marketing teams and small businesses that want high-converting, conversational forms
50,000 responses/year on Team Advantage; 100,000/year on Team Premier
Basic free plan with limited features
Teams running frequent NPS, market research, or HR surveys with built-in analysis
Qualtrics
No public price list — custom quote only
Custom per contract
No free tier for the Enterprise platform
Large enterprises and research teams needing advanced experience-management features
Short Verdict
Typeform wins on form design and completion rates for short, high-conversion surveys, but its response caps are the tightest of the three and extra capacity means jumping a full plan tier. SurveyMonkey is the more transparent, better-value option for teams that need real survey volume — its published annual response allowances (50,000–100,000/year) are easy to budget against. Qualtrics plays a different game entirely: it’s a full experience-management platform with statistical and research tooling the other two don’t attempt, but you cannot get a price without talking to sales, which rules it out for teams that need to self-serve a budget decision.
What Each Tool Actually Is
Typeform is built around conversational, one-question-at-a-time forms designed to maximize completion rates. Basic includes AI form creation, conditional logic, webhooks, and integrations but caps at 100 responses/month and 1 user. Plus removes Typeform branding and adds a custom subdomain. Business adds drop-off analytics, conversion tracking, and priority support. A separate Growth Flow tier adds enriched responses, Smart Insights, and CRM-style contact automation aimed at marketing teams running lead-gen forms rather than simple surveys.
SurveyMonkey is the most traditional survey tool of the three, with a seat-based Team plan structure rather than Typeform’s response-based tiers. Team Advantage includes unlimited surveys and questions, premium themes, payment collection, statistical significance testing, and AI-assisted thematic analysis. Team Premier adds white-label branding, advanced logic, block randomization, multilingual surveys, crosstabs, and phone support. Both require a minimum of 3 users; Enterprise drops that minimum to 5 and adds SSO, regional data residency, and centralized billing.
Qualtrics is an experience-management (XM) platform that goes well beyond simple surveys — covering customer experience, employee experience, brand tracking, and market research with advanced statistical modeling, text analytics, and predictive scoring. It has never published a standard price list; every deployment is quoted individually based on response volume, user seats, and which XM modules (CX, EX, Strategy & Research) a buyer licenses.
Pricing Comparison
Plan Tier
Typeform
SurveyMonkey
Qualtrics
Entry
Basic: $28/mo (annual) — 100 responses/mo, 1 user, AI form creation
SurveyMonkey charges $0.15 for each response beyond a plan’s annual allowance, which is a published, predictable overage rate. Typeform’s overage policy is less explicit on its public pricing page — exceeding a plan’s monthly response cap generally forces an upgrade to the next tier rather than a per-response charge. Qualtrics gives no public basis for comparison at all; third-party buyer reports consistently describe enterprise contracts running into the tens of thousands of dollars per year, but Qualtrics itself does not confirm or publish that figure.
Trade-offs
Typeform pros: the best-designed, highest-converting survey and form experience of the three, strong AI-assisted form creation, good for lead-gen and marketing use cases beyond plain research surveys.
Typeform cons: the tightest response caps of the three at every tier, and a big price jump (Business to Growth Flow) for teams that need marketing automation features.
SurveyMonkey pros: transparent, published pricing and response allowances; strong built-in statistical tools (significance testing, crosstabs, thematic AI analysis) without needing a research-specialist platform.
SurveyMonkey cons: a 3-user minimum on paid team plans means solo users and very small teams pay for seats they may not need; design and branding flexibility trail Typeform.
Qualtrics pros: the deepest experience-management and statistical feature set of the three, purpose-built for enterprise CX/EX programs and academic-grade research.
Qualtrics cons: no public pricing at all, which makes it impossible to budget without a sales conversation, and third-party reports describe it as consistently the most expensive of the three.
Who Each Tool Is a Good Fit For
Choose Typeform if your priority is a polished, high-converting form or short survey — lead capture, event registration, quick feedback — and your monthly response volume stays under a few thousand.
Choose SurveyMonkey if you run recurring research, NPS, or HR surveys at real volume and want transparent, self-serve pricing with solid statistical tooling built in.
Choose Qualtrics only if you’re a large organization running a formal experience-management program across CX, EX, or market research, have budget authority to negotiate an enterprise contract, and need capabilities (advanced text analytics, predictive XM, academic-grade statistics) the other two don’t offer.
Bottom Line
For most small-to-mid-size teams, this comes down to Typeform versus SurveyMonkey, not either of them versus Qualtrics. Pick Typeform for design and conversion, SurveyMonkey for volume and built-in analysis. Qualtrics belongs on the shortlist only once you’re already running a dedicated research or CX function with a procurement process that can absorb a custom enterprise quote — trying to compare it to a credit-card self-serve tool on price isn’t really possible given its sales-only pricing model.
FAQ
Why doesn’t Qualtrics publish its pricing? Qualtrics has never maintained a public price list; every quote is customized to a buyer’s response volume, user count, and which experience-management modules (CX, EX, Strategy & Research) they license, per the company’s own sales process as described on its site and corroborated by multiple independent buyer-pricing reports.
What happens if I exceed my SurveyMonkey response limit? SurveyMonkey’s published pricing page states that additional responses beyond a plan’s annual allowance cost $0.15 each.
Can I use Typeform or SurveyMonkey for free? Both publish a free plan on their pricing pages, though with meaningful limits on response volume, branding, and features compared to the paid tiers; neither page lists the exact free-tier response cap in detail.
Is SurveyMonkey priced per user or per response? SurveyMonkey’s Team plans are priced per user per month (3-user minimum), with a separate annual response allowance (50,000 or 100,000, depending on tier) shared across the whole team account, per its official pricing page.
Every growing support team eventually outgrows a shared inbox and has to pick a real help desk platform. Zendesk, Freshdesk, and Intercom are three of the most widely deployed options, but they start from different premises: Zendesk is the enterprise-grade, highly configurable ticketing standard; Freshdesk undercuts it on price while matching most of the core workflow; and Intercom has rebuilt itself around its Fin AI agent, pricing much of its value on resolutions rather than seats alone. Here’s how their 2026 pricing and features actually compare.
At a Glance
Tool
Entry Paid Price
Free Tier
AI Agent
Best For
Zendesk
$19/agent/mo (Support Team, annual)
None — paid only
5 automated resolutions/agent/mo on Suite Team; extra at $1.50–$2.00 each
Larger support orgs wanting deep configurability and omnichannel routing
Freshdesk
$19/agent/mo (Growth, annual)
None — paid only (free trial)
Freddy AI Agent, 500 sessions included on Growth; extra at $49/100 sessions
Small-to-mid teams wanting Zendesk-like features at a lower price
Intercom
$19/seat/mo (Essential, promotional)
None — paid only
Fin AI Agent, from $0.99 per resolved conversation, no seat required
Teams that want to lean heavily on AI resolution instead of scaling headcount
Short Verdict
Freshdesk is the most cost-predictable of the three at small scale — its Growth plan matches Zendesk’s Support Team price but already includes an AI agent allowance. Zendesk remains the safer pick once you need serious customization: skills-based routing, a sandbox, and granular permission schemes arrive by its Suite Professional and Enterprise tiers. Intercom is the odd one out because its AI agent, Fin, is priced per resolved conversation rather than bundled — which can be cheaper than hiring more agents, or more expensive than either competitor, depending entirely on your ticket volume.
What Each Tool Actually Is
Zendesk is built around its Suite plans, which bundle ticketing, a knowledge base, omnichannel messaging and live chat, and telephony starting at the Team tier. Suite Professional adds Admin Copilot, an app builder, skills-based routing, and IVR phone trees. Suite Enterprise+Copilot layers on intelligent triage, generative AI for voice, approval workflows, a sandbox, and custom agent roles. A cheaper “Support Team” tier ($19/agent/mo) exists for teams that only need email/ticketing without the full omnichannel suite.
Freshdesk (by Freshworks) mirrors Zendesk’s structure at a lower price point. Growth includes the Freddy AI Agent with 500 sessions/month, a shared inbox, customer portal, and basic analytics. Pro adds multilingual support, custom dashboards, multiple SLA policies, and external collaborators. Enterprise adds Freddy AI Insights, skill-based routing, a sandbox, audit logs, and IP allowlisting. Freddy AI Copilot is a $29/agent/month add-on on Pro and Enterprise.
Intercom restructured its whole pricing model around Fin, its AI agent. Essential, Advanced, and Expert are seat-based tiers that unlock progressively more inbox and automation features (Advanced adds a workflow builder and round-robin assignment; Expert adds SSO, HIPAA support, and multibrand messaging), but Fin itself is billed separately at a per-outcome rate starting at $0.99, whether or not you buy any seats. Live chat and the Messenger widget are free and unlimited across all plans — only the inbox/ticketing side and Fin usage cost money.
Pricing Comparison
Plan Tier
Zendesk
Freshdesk
Intercom
Entry
Support Team: $19/agent/mo (annual) — email/ticketing, routing, automations
Fin AI Agent (standalone): from $0.99/resolved outcome, no seats required
Zendesk’s Copilot add-on (AI assistance for agents, separate from the customer-facing AI agent) is priced at $50/agent/month on top of any Suite tier. Freshdesk’s AI Agent sessions beyond a plan’s included allowance cost $49 per additional 100 sessions on every tier. Intercom doesn’t disclose whether its headline seat prices assume monthly or annual billing on its public pricing page, so get a written quote before budgeting.
Trade-offs
Zendesk pros: the deepest third-party app marketplace and integration ecosystem of the three, mature omnichannel routing, and enterprise features (sandbox, custom roles, approval workflows) that scale to very large support orgs.
Zendesk cons: no free tier, AI resolutions beyond the included allowance add up fast ($1.50–$2.00 each), and full omnichannel capability requires jumping to Suite Team or above.
Freshdesk pros: closest feature-for-price match to Zendesk, Freddy AI Agent sessions are bundled from the entry tier, and Enterprise undercuts Zendesk’s equivalent tier by a wide margin.
Freshdesk cons: smaller app ecosystem than Zendesk, and AI Copilot for agents is a flat $29/agent/month add-on regardless of usage.
Intercom pros: Fin’s per-outcome pricing can be dramatically cheaper than adding headcount for high-volume, repetitive queries, and live chat/Messenger are free and unlimited on every tier.
Intercom cons: the highest seat prices of the three at the Advanced and Expert tiers, per-outcome AI billing is harder to forecast than a flat seat price, and the pricing page leaves billing frequency ambiguous.
Who Each Tool Is a Good Fit For
Choose Zendesk if you run a larger, multi-channel support operation and need deep customization, a mature marketplace of integrations, and enterprise governance features you’re willing to pay for.
Choose Freshdesk if you want most of Zendesk’s workflow at a lower total cost, especially at the Enterprise tier, and your team doesn’t need Zendesk’s broadest integration marketplace.
Choose Intercom if a large share of your support volume is repetitive enough that an AI agent can resolve it without a human, and you’re comfortable budgeting a variable, usage-based AI cost instead of a flat per-agent price.
Bottom Line
None of these three is a bad choice at the entry tier — Zendesk and Freshdesk are priced identically at $19/agent/month, so the decision there comes down to ecosystem and future scaling needs rather than cost. Intercom is the platform most worth a serious trial if your support volume is high enough that AI resolution economics matter more than seat count. Whichever you pick, run your actual recent ticket volume through each vendor’s calculator before committing to an annual contract — AI resolution and overage costs are where real monthly bills diverge most from the sticker price.
FAQ
Is there a free plan for any of these help desks? No. All three require a paid plan or a time-limited free trial; none offers a permanently free tier the way some smaller help desk tools do.
How does Intercom’s Fin AI agent pricing actually work? Fin is billed per resolved conversation (“outcome”) starting at $0.99, independent of seat count, per Intercom’s official pricing page. It can be bought standalone without any seat-based plan, which is different from Zendesk’s and Freshdesk’s bundled-session models.
Which platform is cheapest for a 10-agent team? At list price, Zendesk’s Support Team and Freshdesk’s Growth plan are tied at $19/agent/month (annual billing). Intercom’s Essential tier is currently also listed at $19/seat/month, but only as a promotional price for new customers — its standard list price is $29/seat/month.
Do these tools charge extra for AI features? Yes, in different ways. Zendesk charges $1.50–$2.00 per AI resolution beyond a plan’s allowance plus $50/agent/month for its agent-facing Copilot. Freshdesk charges $49 per 100 extra Freddy AI Agent sessions plus $29/agent/month for Freddy Copilot. Intercom’s Fin is priced per outcome from $0.99, on top of any seat costs.
DoubleVerify, Integral Ad Science (IAS), and Adloox all sell the same basic promise to advertisers and agencies: verify that an ad actually ran where it was supposed to, was seen by a real person, and didn’t appear next to content that would embarrass the brand. None of the three publish a public rate card, and that’s normal for this category rather than a red flag — enterprise ad verification is priced and negotiated per contract, typically as a fee layered on top of media cost inside a DSP. We’re not going to invent numbers these vendors don’t publish; instead, here’s what’s actually confirmed about how each one works, how they’re priced, and one major ownership change worth knowing about before you shortlist Adloox.
At a Glance
Platform
Pricing model
Core coverage
Best for
DoubleVerify (DV)
Quote-based; billed as a CPM-style fee layered on top of media spend inside DSPs like DV360
Fraud/invalid traffic, viewability, brand suitability, attention, plus outcome measurement (attribution, MMM, incrementality) via DV Rockerbox
Advertisers who want verification and outcome/attribution measurement from the same vendor
Integral Ad Science (IAS)
Quote-based; fee varies by which brand safety controls you enable, billed per control type inside the DSP
Brand safety/suitability, contextual targeting, ad fraud, viewability, plus IAS Agent and coverage across CTV, social, open web, mobile, audio, and commerce media
Advertisers who want granular control over exactly which brand safety filters they pay for
Adloox
Quote-based; now sold and supported as part of Peer39 following Peer39’s June 2026 acquisition of Adloox
Brand safety/suitability verification, invalid traffic (IVT) detection, and viewability, including expanded coverage on Meta/Instagram campaigns
Agencies and advertisers who want contextual-brand-safety and verification data unified in one interface, now via Peer39
Short Verdict
The honest answer on pricing is that none of these three publish one, and for enterprise ad verification that’s the norm, not a transparency failure — fees are typically billed as a per-impression (CPM-style) charge that stacks on top of the media cost itself, confirmed through Google’s own Display & Video 360 documentation for both DoubleVerify and IAS, and both vendors have reportedly raised those fees during 2026. The real differentiator right now isn’t price, it’s structure: DoubleVerify bundles verification with its own attribution/outcome-measurement stack; IAS lets you pay only for the specific brand safety controls you turn on; and Adloox is no longer a fully independent company — it was acquired by Peer39 in June 2026, and its verification and fraud-detection tools are now being folded into Peer39’s own contextual-targeting platform.
What It Is / How It Works
Ad verification and brand safety platforms sit between an advertiser’s DSP (or the ad platform directly) and the actual ad placement, measuring three things in real time or near-real time: whether the impression was delivered to a real person rather than a bot (fraud/invalid traffic detection), whether it was actually visible on screen for a meaningful duration (viewability), and whether the surrounding content is appropriate for the brand (brand safety/suitability, usually scored against categories like violence, adult content, or misinformation). These scores can be used two ways: passively, for post-campaign reporting, or actively, to automatically block bids on inventory that fails the brand’s chosen thresholds before the ad ever serves — which is the main reason these fees are usually layered directly into DSP billing rather than sold as a separate subscription.
How Pricing Actually Works (and Why There’s No Rate Card)
Vendor
What’s confirmed about pricing
DoubleVerify
Google’s own Display & Video 360 help documentation confirms DV’s “standard verification pre-bid rate card” was updated in April 2025, describing it only as a “marginal increase” to CPM rates “for some solutions,” with no figures published and advertisers directed to contact DoubleVerify directly for current rates.
Integral Ad Science
Google’s DV360 documentation confirms IAS fees are based on which brand safety controls are enabled — using multiple rating-category exclusions counts as one fee, but combining category exclusions with suspicious-activity exclusion and/or a viewability threshold bills each control type separately. Separately, Adweek reported in late 2026, citing sources with direct knowledge, that IAS was raising prices on its brand safety solutions effective November 1, with no public dollar figures disclosed.
Adloox
No independent pricing data was published prior to its 2026 acquisition by Peer39, and Peer39 has not published a public rate card either; pricing for Adloox’s tools is now handled through Peer39’s standard enterprise sales process.
We’re stating this plainly rather than guessing: enterprise ad verification is priced per contract, usually negotiated based on spend volume and which modules (fraud, viewability, brand safety, attention) you turn on, and none of the three vendors above publish a self-serve rate card the way a SaaS tool would. Treat any specific CPM figure you see quoted elsewhere online as unverified unless it comes with a dated source from the vendor or a platform like DV360’s own documentation.
Feature Comparison
Capability
DoubleVerify
IAS
Adloox
Brand safety / suitability
Yes, via the “Verify” pillar of DV’s Media AdVantage Platform
Yes, Brand Safety & Suitability plus Contextual Targeting
Yes, including expanded coverage on Meta/Instagram campaigns as of 2026
Fraud / invalid traffic detection
Yes
Yes, named “Ad Fraud” and “Ad Verification”
Yes, IVT detection, now integrated into Peer39’s reporting interface
Viewability measurement
Yes
Yes
Yes
AI-driven optimization
DV Scibids AI, plus the new DV Authentic AdVantage for walled-garden video platforms
IAS Agent (described as campaign-insight surfacing)
Not described independently; now positioned alongside Peer39’s contextual data products
Outcome / attribution measurement
DV Rockerbox (attribution, marketing mix modeling, incrementality)
Not a core focus; IAS positions itself primarily around media quality rather than outcome measurement
Not a core focus
Channel coverage
Programmatic display/video, CTV, social, and walled-garden video via DV Authentic AdVantage
CTV & Video, Social Platforms, Open Web, Mobile & In-App, Digital Audio, Commerce Media
Programmatic (via DV360 integration) and Meta/Instagram
Ownership status (2026)
Independent, publicly traded company
Independent company; Adweek reported it may be exploring a sale
Acquired by Peer39 on June 9, 2026; team and products now operate under Peer39
Pros and Cons
DoubleVerify pros: one of the few vendors that pairs verification with genuine outcome/attribution measurement (DV Rockerbox) rather than stopping at media quality; broad channel coverage including walled-garden video.
DoubleVerify cons: no public pricing; Google’s own documentation confirms rate increases without disclosing the new figures, so budgeting requires a direct quote.
IAS pros: granular, à la carte billing by control type means you aren’t necessarily paying for brand safety features you don’t use; strong, named coverage across CTV, social, audio, and commerce media.
IAS cons: reported November 2026 price increase with no public figures; Adweek’s reporting that IAS may be weighing a sale introduces some uncertainty about the vendor’s direction.
Adloox pros: verification and fraud-detection tools are now backed by Peer39’s contextual data infrastructure, with Peer39 explicitly promising no disruption to existing DV360 or Meta implementations.
Adloox cons: no longer an independent company as of June 2026, which means its product roadmap and brand identity are now tied to Peer39’s decisions rather than standing alone.
Who It’s a Good Fit For
DoubleVerify fits advertisers who want verification and post-campaign attribution/outcome measurement from a single vendor relationship rather than stitching two tools together. IAS fits buyers who want fine-grained control over exactly which brand safety filters they’re billed for, and who are comfortable negotiating given the vendor’s reported late-2026 price increase. Adloox fits agencies already using Peer39 for contextual targeting who want verification and fraud detection folded into that same reporting interface, since Peer39 has stated existing Adloox implementations won’t need to change.
Who Should Look Elsewhere
Smaller advertisers without a dedicated media-buying or ad-ops team may find all three vendors’ enterprise sales and quote process disproportionate to their spend, and should look at lower-cost, self-serve fraud-detection tools instead.
Anyone who needs a locked-in, self-serve published price before committing budget should expect none of these three to offer one — plan for a sales conversation as part of the evaluation timeline, not a checkout page.
Teams specifically evaluating Adloox as a fully independent vendor should factor in that it’s now part of Peer39 as of mid-2026, which may affect long-term roadmap and support decisions even though current implementations are unaffected.
Bottom Line
None of these three platforms will give you a number on a pricing page, and that’s expected for enterprise ad verification rather than a knock against any of them — the honest move is to say so plainly, which is what we’ve done here, rather than publish a guessed CPM rate. What should actually drive your shortlist is structure: DoubleVerify if you want verification plus attribution in one vendor, IAS if you want to pay only for the specific controls you enable, and Adloox if you’re already in or open to Peer39’s ecosystem — just go in aware that Adloox stopped being a standalone company in June 2026.
FAQ
Why don’t DoubleVerify, IAS, or Adloox publish pricing? Ad verification fees are typically negotiated per contract and billed as a CPM-style charge layered on top of media spend inside a DSP, varying by spend volume, which modules are enabled, and the specific deal — there’s no standard “seat” or “plan” the way SaaS tools sell, which is why none of the three publish a self-serve rate card.
Is it true that Adloox was acquired? Yes — Peer39 announced its acquisition of Adloox on June 9, 2026. Peer39 has stated there will be no disruption to existing customer engagements, reporting, or campaign operations, and that Adloox customers won’t need to change their DV360 or Meta implementations.
Did IAS or DoubleVerify really raise prices in 2026? Adweek reported, citing sources with direct knowledge, that IAS raised prices on its brand safety solutions effective November 1, 2026, communicated to clients through in-platform notices on partner DSPs. Separately, Google’s own DV360 documentation confirms DoubleVerify updated its standard verification rate card in April 2025 with a “marginal increase” to some CPM rates. Neither disclosure includes specific dollar figures.
Do these tools work outside of Display & Video 360? Yes — all three integrate with multiple DSPs and, in IAS’s and Adloox’s case, directly with social platforms like Meta; DV360 is simply the platform whose own public documentation happens to confirm the most detail about how DoubleVerify’s and IAS’s fees are structured.
Running paid social at any real scale usually means outgrowing Meta’s and TikTok’s native ad managers within the first few campaigns — the reporting is thin, bulk creation is clumsy, and there’s no good way to automate “pause this ad set if cost-per-result climbs past X.” AdEspresso, Revealbot, and Madgicx all exist to fill that gap, but they take noticeably different approaches to pricing and automation depth. One housekeeping note up front: Revealbot rebranded to Birch in 2026, and its official pricing URL now redirects there — we’ve kept the familiar “Revealbot” name in this comparison since that’s what most advertisers still search for, but the product and pricing below are current under the Birch brand.
At a Glance
Tool
Starting price
Free plan
Best for
AdEspresso
Starter $49/mo (capped at $1,000/mo in managed ad spend); Plus $99/mo (uncapped)
No — 14-day free trial only
Smaller Facebook/Instagram-only advertisers who mainly want easier split testing and bulk ad creation
Revealbot (now Birch)
Essential $49/mo ($540/yr annually); Pro $99/mo ($1,090/yr annually)
No — 14-day free trial, full features, no credit card required
Teams that want rules-based automation across Meta, Google, Snapchat, and TikTok in one tool
Madgicx
Base subscription not published — revealed inside the app based on your monthly ad spend tier; Tracking Pro add-on confirmed at $49/mo
No — 7-day free trial with full feature access
E-commerce advertisers who want AI-driven automation plus first-party, server-to-server conversion tracking in the same platform
Short Verdict
Revealbot/Birch is the most straightforward on price — its $49 and $99 monthly tiers are published as fixed figures on its own site, and it’s the only one of the three confirmed to natively manage Google, Snapchat, and TikTok alongside Meta rather than Meta alone. AdEspresso is the simplest entry point if you’re Facebook/Instagram-only and mainly want better split testing, though its own pricing page blocks automated access, so we leaned on two independent pricing trackers that agree with each other. Madgicx is the hardest to price-shop up front since its core subscription cost only appears after you select an ad-spend tier inside the app itself — a legitimate quote-based model, not a vendor oversight, but one you should budget extra time for before committing.
What It Is / How It Works
All three are ad-management layers that sit on top of your existing ad accounts (Meta, Google, TikTok, Snapchat) rather than replacing them — you still own the campaigns and spend directly with each platform, and these tools connect via API to add automation, reporting, and bulk workflows the native ad managers don’t offer well. AdEspresso’s core identity is split-testing and guided campaign creation. Revealbot/Birch’s core identity is if-this-then-that automation rules (“pause this ad if CPA exceeds $40 for 2 days”) plus multi-platform reporting. Madgicx leans hardest into AI: automated budget/bid optimization, audience and creative analytics, and — through its Tracking Pro add-on — first-party, server-side conversion tracking that’s increasingly important as browser-based pixel tracking degrades.
Pricing Breakdown
Plan
Price
Notable limits / features
AdEspresso Starter
$49/mo
Capped at $1,000/mo in managed ad spend; split testing; unlimited ad accounts; Facebook/Instagram only
AdEspresso Plus
$99/mo
Uncapped ad spend; performance triggers, bulk creation, approval workflows, up to 15 seats, white-label reports
AdEspresso Enterprise
From $259/mo
API access, mandatory approvals, Salesforce integration, unlimited seats, dedicated consultant
Revealbot/Birch Essential
$49/mo, or $540/yr billed annually
Reports and activity dashboard, Workspaces overview, post boosting, Slack integration
Revealbot/Birch Pro
$99/mo, or $1,090/yr billed annually
Adds automated rules and strategies, Explorer, Launcher, custom audience builder, integrations with Google Sheets, AppsFlyer, and Hyros
Revealbot/Birch Enterprise
Custom — contact sales
Higher usage limits, onboarding/tech-setup help, premium support
Madgicx Pro Complete (with AI)
Not a published fixed figure — shown inside the app after you select your monthly ad-spend band (tiers run from under $1K to $30K+ in spend)
Automation, targeting, analytics, and ad management bundled together; billed monthly, quarterly, or annually
Madgicx Tracking Pro (add-on)
$49/mo
Server-to-server Facebook ad tracking, enhanced conversions with Click ID support, real-time first-party conversion data
A note on sourcing: AdEspresso’s own pricing page blocks automated fetching (robots.txt), so the Starter/Plus/Enterprise figures above are corroborated by two independent pricing-tracking sites that agree on all three numbers as of November 2026. Madgicx’s Pro Complete price is genuinely not published as a fixed number anywhere on its own site — the company discloses it only inside the app once you pick an ad-spend band — which is a deliberate pricing model, not a gap in our research; its Tracking Pro add-on price, by contrast, is a published, confirmed $49/month figure.
Pros and Cons
AdEspresso pros: simplest entry price; dedicated split-testing interface; unlimited ad accounts even on the Starter tier.
AdEspresso cons: Facebook and Instagram only — no Google, TikTok, or Snapchat support on any tier; Starter caps managed ad spend at $1,000/month.
Revealbot/Birch pros: fixed, published pricing with no ad-spend-based surprises; covers four platforms (Meta, Google, Snapchat, TikTok) instead of one; 14-day trial with full feature access and no credit card required.
Revealbot/Birch cons: automation rules — arguably the product’s core feature — are reserved for the Pro tier, not Essential; recent rebrand to “Birch” may confuse advertisers searching for the old name.
Madgicx pros: AI automation spans budgeting, targeting, and creative analytics in one subscription; server-side tracking add-on addresses real, current attribution gaps; 7-day trial includes full feature access.
Madgicx cons: no published base price, so you can’t comparison-shop it against AdEspresso or Revealbot/Birch without first entering the app and your spend level; pricing scales with ad spend rather than staying flat.
Who It’s a Good Fit For
AdEspresso fits a smaller advertiser who’s Facebook/Instagram-only and mainly wants better split testing and bulk ad creation without a steep learning curve. Revealbot/Birch fits a team running paid social and search together that wants rules-based automation and a flat, predictable monthly price regardless of spend level. Madgicx fits e-commerce brands at meaningful ad spend who want AI-driven optimization and first-party tracking bundled together, and who are comfortable requesting a quote rather than seeing a sticker price up front.
Who Should Look Elsewhere
Advertisers running meaningful budgets on Google Ads, TikTok, or Snapchat alongside Meta should skip AdEspresso entirely, since it only supports Facebook and Instagram.
Anyone who needs a guaranteed flat monthly price regardless of how much they spend on ads should be cautious with Madgicx’s spend-tiered model and lean toward AdEspresso or Revealbot/Birch instead.
Very small advertisers under roughly $1,000/month in spend who want the cheapest possible automation layer may find AdEspresso’s Starter tier or Revealbot/Birch’s Essential tier more cost-effective than Madgicx’s spend-based pricing.
Bottom Line
There’s no single best social media ad management tool in 2026 — there’s a best fit for your platform mix and how much certainty you need about price. Revealbot (now officially Birch) offers the most transparent, fixed pricing and the broadest platform coverage of the three. AdEspresso is the simplest and cheapest way in if you’re Meta-only. Madgicx asks you to trade price transparency for deeper AI automation and built-in server-side tracking — reasonable if you’re already spending enough on ads that the automation pays for itself, less so if you just want to know the monthly bill before you sign up.
FAQ
Did Revealbot actually change its name? Yes — as of 2026, Revealbot’s own pricing URL (revealbot.com/pricing) redirects to bir.ch/pricing, confirming the product now operates under the “Birch” brand, even though the underlying Facebook/Meta ads automation product is the same one most advertisers know as Revealbot.
Why doesn’t Madgicx publish a flat monthly price? Madgicx’s own pricing page states its Pro Complete plan price is shown “inside the app” and scales across ad-spend bands from under $1,000/month to $30,000+/month, rather than publishing one number for every customer — a deliberate usage-based pricing model rather than an oversight.
Can I use more than one of these tools at once? Technically yes, since all three connect via API rather than replacing your native ad accounts, but running two automation tools against the same campaigns risks conflicting rules (for example, two tools both trying to adjust the same ad set’s budget), so most advertisers pick one as the primary automation layer.
Does any of these tools replace Meta Ads Manager entirely? No. All three are management/automation layers on top of your existing Meta, Google, TikTok, or Snapchat ad accounts — you still need an active ad account with each platform, and billing for the ad spend itself still goes through the platform, not through AdEspresso, Revealbot/Birch, or Madgicx.
Our earlier piece on the Go programming language introduced goroutines and channels and showed a basic worker-pool pattern. This one goes a level deeper: how does the Go runtime actually schedule hundreds of thousands of goroutines onto a handful of OS threads, what guarantees do channels really give you when goroutines run concurrently, and how does select let a goroutine wait on several channels at once? These mechanics are what make Go’s concurrency model more than just “lightweight threads with a nicer syntax” — and they’re also where the model’s real sharp edges live.
At a Glance
Concept
What it is
Goroutine (G)
A function running concurrently, with its own small, growable stack — not an OS thread
OS thread (M)
What the Go runtime calls a “machine” — the real kernel thread that actually executes instructions
Processor (P)
A runtime-managed context, up to GOMAXPROCS of them, that holds a local run queue of goroutines ready to execute
Work stealing
When a P’s local queue is empty, it steals goroutines from another P’s queue instead of going idle
Async preemption
Since Go 1.14, the runtime can interrupt a long-running goroutine mid-loop, not just at function calls
Memory model
Defines exactly which operations are guaranteed to be visible across goroutines (“happens before”)
Short Verdict
Go’s concurrency model earns its reputation by combining three things that are each unremarkable alone but genuinely useful together: goroutines that cost a few kilobytes instead of a full OS thread stack, a scheduler that multiplexes them with work-stealing so idle cores don’t sit idle, and a small set of channel operations with memory-model guarantees precise enough to build correct synchronization without a mutex. None of it is magic — the Go FAQ is upfront that the scheduler “is not perfect,” and the memory model’s own advice is “if you must read the rest of this document to understand the behavior of your program, you are being too clever.” The mechanics are worth knowing specifically because they explain where things break: goroutine leaks, GOMAXPROCS misconfiguration in containers, and data races on plain variables that look fine until they aren’t.
Why Goroutines Are Cheap: the Short Version
Go’s own FAQ describes a goroutine as a coroutine multiplexed onto a set of OS threads: “When a coroutine blocks, such as by calling a blocking system call, the run-time automatically moves other coroutines on the same operating system thread to a different, runnable thread so they won’t be blocked. The programmer sees none of this, which is the point.” The cost structure is what makes this practical at scale — a new goroutine starts with just a few kilobytes of stack, which the runtime grows and shrinks automatically, and Go’s own documentation states the CPU overhead per function call averages about three cheap instructions. The FAQ’s own conclusion: “It is practical to create hundreds of thousands of goroutines in the same address space. If goroutines were just threads, system resources would run out at a much smaller number.”
The Scheduler: G, M, and P
The Go runtime’s scheduler implementation is commonly described using three letters — G, M, and P — a shorthand that comes from the runtime’s own source code and the engineering writeups around it, rather than a term you’ll find spelled out in the beginner-level Go docs. It’s worth understanding because it explains exactly how “multiplexed onto OS threads” actually happens:
Letter
Stands for
Role
G
Goroutine
A single concurrent function call and its stack — the unit of work being scheduled
M
Machine
An actual OS thread that executes code; the runtime creates and parks these as needed
P
Processor (context)
A scheduling context, capped at GOMAXPROCS, that must be held by an M before it can run a G; each P keeps a local run queue
An M can only execute Go code while holding a P, and the number of Ps — not the number of Ms — determines how many goroutines can run truly in parallel at once. When a goroutine makes a blocking system call, the runtime detaches the P from that M so another M can pick it up and keep making progress, which lines up with the FAQ’s description of moving blocked coroutines aside automatically. When a P’s own local run queue runs dry, it doesn’t go idle — it steals goroutines from another P’s queue, a technique generally known as work-stealing scheduling, so work spreads across available cores instead of piling up behind one busy P.
GOMAXPROCS: Controlling How Many Ps Exist
Go’s FAQ states that “the number of CPUs available simultaneously to executing goroutines is controlled by the GOMAXPROCS shell environment variable, whose default value is the number of CPU cores available.” You can also set it from code:
package main
import (
"fmt"
"runtime"
)
func main() {
fmt.Println("default GOMAXPROCS:", runtime.GOMAXPROCS(0))
// Limit parallel execution to 4 OS threads.
runtime.GOMAXPROCS(4)
fmt.Println("updated GOMAXPROCS:", runtime.GOMAXPROCS(0))
}
The FAQ is also clear that this setting only governs parallelism, not concurrency: “GOMAXPROCS only affects how many goroutines can actually execute at once; arbitrarily more may be blocked in system calls.” Setting it to 1 doesn’t stop you from spawning goroutines — it just forces them to take turns on a single OS thread instead of running simultaneously. This matters more than it sounds: older Go runtimes sometimes read a container’s host CPU count instead of its actual CPU limit/cgroup quota, over-provisioning Ps relative to the CPU the container was actually allowed to use — a real-world reason this setting shows up in production tuning discussions rather than just scheduler theory.
Preemption: Stopping a Goroutine That Won’t Yield
For its first several years, Go’s scheduler could only preempt a goroutine at specific safe points, mostly function calls — a tight loop with no function calls inside it could starve the scheduler or stall garbage collection. Go 1.14’s release notes record the fix: “Goroutines are now asynchronously preemptible. As a result, loops without function calls no longer potentially deadlock the scheduler or significantly delay garbage collection.” The same release notes flag a side effect worth knowing if you’re doing low-level systems work in Go: “on Unix systems, including Linux and macOS systems, programs built with Go 1.14 will receive more signals than programs built with earlier releases,” which can surface as more EINTR failures from slow system calls that code using syscall or golang.org/x/sys/unix needs to handle by retrying.
select: Waiting on Multiple Channels at Once
A single channel receive blocks until something arrives. select is how a goroutine waits on several channel operations simultaneously and reacts to whichever one is ready first. Per the Go language specification, if more than one case could proceed, one is chosen by uniform pseudo-random selection — not source order — and a default case runs only when nothing else is ready, making the whole statement non-blocking:
package main
import (
"context"
"fmt"
"time"
)
func fetch(ctx context.Context, results chan<- string) {
select {
case <-time.After(200 * time.Millisecond):
results <- "data fetched"
case <-ctx.Done():
// The caller cancelled or the deadline passed first.
return
}
}
func main() {
ctx, cancel := context.WithTimeout(context.Background(), 100*time.Millisecond)
defer cancel()
results := make(chan string, 1)
go fetch(ctx, results)
select {
case r := <-results:
fmt.Println(r)
case <-ctx.Done():
fmt.Println("timed out:", ctx.Err())
}
}
This pattern — racing a real result against a timeout or cancellation signal through select — is the standard way Go code bounds how long it waits on a concurrent operation, and it’s the same mechanism the standard library’s own context package is built around.
The Memory Model: What Channels Actually Guarantee
Goroutines running concurrently can each see a different, stale view of shared memory unless something establishes an explicit ordering between them — what the Go memory model calls “happens before.” The model spells out specific channel guarantees: a send is synchronized before the corresponding receive completes; on an unbuffered channel, a receive is synchronized before the corresponding send completes; closing a channel is synchronized before a receive that returns because the channel is closed; and for a channel with capacity C, the kth receive is synchronized before the (k+C)th send completes. That last rule is exactly what makes a buffered channel usable as a counting semaphore:
package main
import "sync"
// limit caps how many goroutines run concurrently.
var limit = make(chan struct{}, 3)
func process(id int, wg *sync.WaitGroup) {
defer wg.Done()
limit <- struct{}{} // acquire a slot
defer func() { <-limit }() // release it
// ... do work with at most 3 goroutines active at once ...
}
func main() {
var wg sync.WaitGroup
for i := 0; i < 10; i++ {
wg.Add(1)
go process(i, &wg)
}
wg.Wait()
}
The memory model is equally specific about what doesn’t give you a guarantee: checking a plain boolean variable in a busy-wait loop has no happens-before edge at all, so the compiler and runtime are free to never let the reading goroutine observe the write. The memory model’s own busy-wait example using a plain bool is documented as broken for exactly this reason — it “may print the empty string… or never terminate” — and its closing advice is blunt: “If you must read the rest of this document to understand the behavior of your program, you are being too clever. Don’t be clever.”
Trade-offs
Cheap goroutines are still not free — spawning millions without a bound (a worker pool, a semaphore channel like the one above) can exhaust memory even though each one is individually tiny.
A goroutine blocked forever on a channel that nothing will ever write to or read from is a classic leak; select with a cancellation case (as shown above) is the usual fix, not a substitute for actually closing channels when producers finish.
Work-stealing and async preemption make the scheduler good at avoiding starvation in the common case, but Go’s own FAQ concedes it “is not perfect,” and GOMAXPROCS tuning is a real, occasionally necessary escape hatch — especially in containers with CPU limits below the host’s full core count.
The memory model’s guarantees are specific to the operations it documents (channels, sync.Mutex, sync/atomic, sync.Once); reasoning about anything outside those primitives from first principles is how subtle data races get introduced.
Bottom Line
Goroutines, channels, and select are the parts of Go’s concurrency model every tutorial shows. The GMP scheduler, work-stealing, async preemption, and the memory model’s happens-before rules are the parts that explain why those primitives behave the way they do under load — and they’re exactly what you need once you’re debugging a goroutine leak, a CPU-throttled container, or a data race that only shows up under go test -race. None of it replaces careful design, but it does explain which shortcuts are actually safe.
FAQ
What do G, M, and P stand for in the Go scheduler? Goroutine, Machine (an OS thread), and Processor (a scheduling context capped at GOMAXPROCS that holds a local run queue). This terminology comes from the Go runtime’s own implementation and the engineering writing around it, not from a single official beginner-facing document.
Does raising GOMAXPROCS always make my program faster? No. It only raises the ceiling on how many goroutines can run in true parallel; a program that isn’t actually parallelizable, or that spends more time synchronizing than computing, won’t benefit and can even slow down from added context-switching overhead.
When did Go gain asynchronous goroutine preemption? Go 1.14, released in February 2020. Before that, a tight loop with no function calls could block the scheduler or delay garbage collection indefinitely.
Does an unbuffered channel guarantee the receiver sees the sender’s writes? Yes, per the Go memory model: a send on a channel is synchronized before the corresponding receive completes, and for an unbuffered channel, the receive is also synchronized before the send completes — so any plain variable written before the send is guaranteed visible after the receive.
Keeping dependencies patched used to mean a developer periodically running an audit command and opening pull requests by hand. In 2026, that job is increasingly handled by an autonomous agent that watches your manifests, opens its own pull requests, and — in the more advanced tools — uses AI to explain or even help resolve the breaking changes a version bump introduces. Renovate, Dependabot, and Mend are the three names that come up most often, but they’re not quite the same kind of product: Renovate is an open-source automation engine, Dependabot is GitHub’s native built-in bot, and Mend is a commercial AppSec vendor that now owns and sells a hosted version of Renovate alongside its own scanning platform. We checked each vendor’s current pricing and documentation before writing this comparison.
At a Glance
Tool
Starting Price
Free Plan
Best For
Key Specs
Renovate
Free (open source, self-hosted or via the Mend-hosted app)
Yes — the entire open-source project, AGPL-3.0 licensed
Teams on any Git host wanting highly configurable, automated dependency PRs
Yes — security and version updates included free on Free, Team, and Enterprise
GitHub-native teams wanting zero-setup, built-in dependency PRs
Native GitHub integration, security updates triggered by the dependency graph, version updates via a repo config file
Mend (AppSec / Renovate Enterprise)
Mend Renovate Enterprise up to $250/developer/year standalone; Mend AppSec up to $1,000/developer/year
No free self-serve tier for the commercial platform (demo-only)
Enterprises wanting Renovate’s automation plus AI-assisted triage, SCA, and SAST in one vendor
Hosted Renovate at scale, Mend SCA/SAST, AI-generated fix suggestions, AI-aware code scanning for AI-assistant output
Short Verdict
Dependabot is the easiest starting point for any team already on GitHub — it’s free, requires almost no setup, and now groups updates and lets you write auto-triage rules on paid GitHub plans. Renovate is the more powerful, more configurable option, especially if you’re not on GitHub or want fine-grained control over scheduling, grouping, and which ecosystems get updated how — and it’s free whether you self-host it or run the community GitHub App. Mend is the one to reach for when you want dependency updates bundled with a full AppSec platform (SCA, SAST, AI-aware scanning) under a single enterprise contract, at real recurring cost.
What Each One Is and How It Works
Renovate is an open-source automation bot (AGPL-3.0) that scans your manifests (package.json, go.mod, requirements.txt, Dockerfile, and dozens more) and opens pull requests when a newer version is available, following rules you define in a JSON/JSON5 config file committed to the repo. It supports more than 90 package managers and lets you group updates (e.g., “bundle all patch-level updates into one weekly PR”), schedule when PRs are opened, and set automerge rules for low-risk updates. You can self-host the OSS version on any CI runner, or run it via the Mend-hosted “Mend Renovate” GitHub App, which is free for public repos and available through GitHub Marketplace for private ones.
Dependabot is built directly into GitHub. Its security updates trigger automatically from GitHub’s dependency graph and Dependabot alerts — when a known vulnerability is published for a dependency you use, Dependabot opens a PR bumping to a patched version, with no configuration required beyond enabling alerts. Its separate version-update feature (configured via a dependabot.yml file) handles routine non-security upgrades on a schedule you set. Both are included free on every GitHub plan; the main things gated to paid Team/Enterprise plans are custom auto-triage rules for alerts and the dependency review GitHub Action.
Mend sells two relevant things here: a hosted, enterprise-scale version of Renovate (Mend Renovate Enterprise), and its own software composition analysis (SCA) engine as part of the broader Mend AppSec platform. The pitch for pairing them is that Renovate handles the mechanical “open a PR to bump this version” work, while Mend’s AI-powered layer adds context — flagging which updates actually close an exploitable vulnerability versus which are routine, and in Mend’s AppSec tier, extending AI-aware scanning to catch issues in code generated by AI coding assistants like Cursor, Windsurf, or Copilot.
Autonomous Patching as a Security Workflow
What makes this category “agentic” rather than just “automated” is the growing amount of judgment these tools now exercise without a human in the loop at every step: deciding which updates are safe to automerge, grouping dozens of minor bumps into one reviewable PR instead of dozens of separate notifications, and — in Mend’s case — using AI to prioritize which outdated dependency actually matters because it’s both vulnerable and reachable in your code, versus one that’s outdated but never called. None of the three tools eliminates the need for a human to review a major-version bump that could break the build; what they remove is the manual effort of noticing an update exists in the first place and drafting the PR. A representative Renovate configuration for grouping low-risk updates and scheduling them off-hours looks like this:
Sold as an add-on to AppSec or standalone, per Mend’s pricing page.
Mend’s pricing page presents all three figures as “up to” ceilings rather than flat list prices, and states explicitly that hosting, services, and custom agreements can add cost — so treat these as the upper bound you’d negotiate down from, not a guaranteed quote.
Pros and Cons
Renovate
Pros: free and open source, works across GitHub, GitLab, Bitbucket, Azure DevOps, and more, extremely configurable grouping/scheduling, huge package-manager coverage
Cons: self-hosting means you own the runner/infrastructure and upgrade cadence; configuration depth is also a learning curve — the JSON config can get complex fast
Dependabot
Pros: zero setup cost, free on every plan including private repos, tightly integrated with GitHub’s dependency graph and security alerts, no separate infrastructure to run
Cons: GitHub-only, less configurable grouping/scheduling than Renovate out of the box, advanced triage rules require a paid GitHub plan
Mend
Pros: pairs dependency automation with a full AppSec platform and AI-powered prioritization/fix suggestions, hosted Renovate at enterprise scale with support, AI-aware scanning extends to AI-assistant-generated code
Cons: real recurring per-developer cost with no self-serve free tier for the commercial platform, pricing given only as “up to” ceilings rather than a fixed quote, most value realized only if you buy into the broader AppSec bundle rather than Renovate alone
Who It’s a Good Fit For
Choose Dependabot if you’re already on GitHub and want dependency patching working with literally zero extra infrastructure.
Choose Renovate if you need cross-platform support, more granular scheduling/grouping than Dependabot offers, or you’re not on GitHub at all.
Choose Mend if you want dependency automation bundled into a single enterprise AppSec contract with AI-assisted prioritization and support, and you have budget for a per-developer annual license.
Who Should Look Elsewhere
Teams that need vulnerability scanning and dependency updates to be just one module inside a much broader cloud-native security platform (container scanning, IaC, runtime detection) may be better served evaluating a cloud security platform’s bundled SCA module instead of any single-purpose tool here. And teams with a very small number of repos and infrequent dependency churn may find that a simple scheduled CI job running npm audit or pip-audit and opening PRs manually is genuinely sufficient, without adopting a dedicated bot at all.
Bottom Line
For most GitHub-based teams, Dependabot’s free, zero-setup updates are the right default, with Renovate as the upgrade path once you need more control than Dependabot’s configuration allows or you’re not on GitHub. Mend makes the most sense once dependency patching is one line item inside a larger enterprise AppSec purchase rather than something you want to solve on its own.
FAQ
Is Renovate the same company as Dependabot? No. Renovate is an independent open-source project (now stewarded with Mend’s involvement as a maintainer/sponsor of the hosted app), while Dependabot is built and owned by GitHub. They’re separate codebases solving a similar problem differently.
Is Dependabot really free on private repositories? Yes — per GitHub’s own pricing page, Dependabot security updates and version updates are included on the Free, Team, and Enterprise plans alike; only the more advanced auto-triage rules and dependency review Action require a paid Team or Enterprise plan.
Can I run Renovate for free on private repos? Yes, by self-hosting the open-source project yourself on your own CI infrastructure; the free Mend-hosted GitHub App is specifically for public repositories, with private-repo hosting sold through Mend’s commercial Renovate Enterprise tier.
Do these tools auto-merge updates without any human review? Only if you configure them to. All three support automerge rules for low-risk update types (like patch-level bumps that pass CI), but none of them force automerge by default — it’s an opt-in policy decision your team makes.
Does using one of these tools replace the need for a SAST/SCA scanner? No. Dependency-update bots patch known-outdated or known-vulnerable packages; they don’t scan your own first-party code for vulnerabilities the way a SAST tool does, and Mend’s own platform treats automated updates (Renovate) and vulnerability scanning (Mend SCA/SAST) as separate, complementary modules rather than substitutes for each other.
Our earlier look at AWS’s Nitro System covered how Amazon virtualizes full EC2 instances with offload hardware. Firecracker solves a narrower, different problem: how do you run a single customer’s function or container with VM-grade isolation, when that workload might live for a few hundred milliseconds and you need to start thousands of them per second? AWS open-sourced its answer in November 2018, and it’s now the virtualization layer underneath both AWS Lambda and AWS Fargate. Here’s how it actually works, based on AWS’s own documentation and its original open-source announcement.
At a Glance
Thing
What AWS states
What it is
Open-source virtual machine monitor (VMM) built on Linux KVM, purpose-built for short-lived, multi-tenant workloads
Used by
AWS Lambda (sandboxes for customer function code) and AWS Fargate (container tasks, running on bare-metal EC2)
Boot time
Under 125 ms per microVM, per AWS’s 2018 announcement
Memory overhead
Less than 5 MiB per microVM
Implementation language
Rust, chosen for memory safety
License / availability
Apache 2.0, open-sourced November 27, 2018; also usable outside AWS
Pricing model
Not sold directly — it’s the infrastructure underneath Lambda and Fargate billing, not a separately priced product
Short Verdict
Firecracker is a genuinely different point on the isolation-versus-speed curve than either containers or traditional VMs: it keeps hardware-virtualization isolation — a real boundary enforced by the CPU, not just kernel namespaces — while booting in under 125 milliseconds and adding under 5 MiB of memory overhead per instance. That combination is specifically why AWS trusts it to run arbitrary, untrusted customer code in Lambda at the density and speed serverless pricing depends on. The trade-off isn’t really a downside so much as a scope limit: Firecracker provides minimal, Lambda-managed snapshot-based lifecycle management, not a general-purpose VM platform you’d reach for outside this kind of multi-tenant, short-lived workload.
What a MicroVM Actually Is
AWS’s Lambda documentation defines a MicroVM as “a resource that represents an isolated compute environment for a single tenant, user session, or job.” Each one runs its own guest kernel (Amazon Linux 2023, in Lambda’s case) and receives requests over inbound HTTPS. Firecracker itself, the underlying technology, is AWS’s open-source virtual machine monitor: it uses the Linux kernel’s built-in KVM virtualization to launch VMs, but strips the device model down to a minimal, emulated set — none of the legacy hardware emulation a general-purpose hypervisor carries for compatibility with arbitrary guest operating systems.
That minimalism is the entire point. A traditional VM boots a full guest OS against an emulated BIOS, disk controller, network card, and more, which is part of why VM boot times are measured in seconds. A container skips virtualization entirely and shares the host kernel, which is fast but means the isolation boundary is kernel namespaces and cgroups — weaker than hardware virtualization if the kernel itself has a bug. Firecracker’s microVM keeps the hardware-virtualization boundary but throws out everything a guest doesn’t need:
Container
MicroVM (Firecracker)
Full VM
Kernel
Shares host kernel
Runs its own guest kernel
Runs its own guest kernel
Isolation boundary
Kernel namespaces and cgroups
Hardware virtualization (KVM)
Hardware virtualization (KVM)
Device model
Not applicable
Minimal, emulated virtio devices only
Full emulated hardware
Typical startup
Fast (no boot)
Under 125 ms; near-instant from a snapshot
Slow — full OS boot
Memory overhead
Low
Under 5 MiB per instance
Hundreds of MiB or more
AWS’s framing in its 2018 open-source announcement was direct about the gap it was trying to close: existing virtualization technology wasn’t built for the short-lived, event-driven nature of serverless workloads, and AWS wanted VM-level isolation combined with the small footprint and agility people expect from containers and functions — not a compromise between the two, but genuinely both.
Snapshot-Based Launch: Why Lambda Feels Instant
Even a 125 ms boot is too slow if you need it on every single invocation, so AWS Lambda’s MicroVMs don’t actually boot from scratch at request time — they launch from a pre-built snapshot. Per AWS’s documentation, the sequence runs like this:
Lambda provisions a fresh MicroVM from your base image.
It runs your Dockerfile build instructions.
It starts your application via ENTRYPOINT or CMD.
If you’ve defined a /ready lifecycle hook, Lambda waits for an HTTP 200 before proceeding.
Lambda then captures a full snapshot of disk and memory, including running processes.
At actual invocation time, Lambda restores that snapshot instead of repeating the build — AWS describes the result as “near-instant launch and resume,” though it doesn’t publish a specific restore-latency figure. The same mechanism works in reverse: after an idle period, or on an explicit suspend-microvm call, a running MicroVM checkpoints its memory and disk state and moves to a suspended state that incurs no compute charges, ready to resume later from exactly where it left off.
State
Meaning
PENDING
Resources allocating, snapshot loading
RUNNING
Accepting traffic; the /run hook has completed
SUSPENDING / SUSPENDED
Checkpointing in progress / state preserved, no compute charges
TERMINATING / TERMINATED
Running the /terminate hook / terminal state
AWS’s docs flag one failure path worth knowing: if the /run hook fails or times out, a MicroVM can go straight from PENDING to TERMINATING without ever reaching RUNNING — so production code needs real error handling in that hook, not an assumption that startup always succeeds.
The Security Model — and Its One Real Gotcha
Each MicroVM is scoped to a single tenant, user session, or job, and AWS documents separate, independently configurable network connectors governing inbound and outbound traffic. The default connector allows inbound port access with JWE-based authentication, shell access, and public internet egress; you can define your own connector to route egress through a specific VPC instead. Build-time and run-time traffic can even go through different connectors.
The gotcha is a direct consequence of the snapshot model: because the snapshot captures whatever state existed at the end of the build, anything generated during the build — a unique ID, a secret, an open network connection — is baked into every single MicroVM later restored from that same image version. AWS’s documentation explicitly warns against generating unique IDs, secrets, or network connections at build time for exactly this reason:
FROM <base-image-from-lambda-managed-images>
COPY app/ /app/
RUN pip install -r /app/requirements.txt
# Do NOT generate per-instance secrets or unique IDs here --
# this build step runs once, and its state is captured in the
# snapshot shared by every MicroVM restored from this image.
CMD ["python", "/app/server.py"]
The fix is to generate per-instance secrets and connections inside the /run lifecycle hook, which executes fresh each time a MicroVM actually starts serving traffic, rather than once at build time.
Where Firecracker Actually Runs
AWS’s open-source announcement names two services built on Firecracker. AWS Lambda uses it as the foundation for the sandboxes that execute customer function code. AWS Fargate uses it for container tasks: those tasks previously ran as Docker containers inside dedicated EC2 VMs, and moved to running as Firecracker microVMs directly on EC2 bare-metal instances — keeping the hardware-level isolation between tasks that customers expect from separate VMs, without paying for a full EC2 instance per task. AWS’s announcement also mentioned an early containerd integration prototype, letting Firecracker slot into existing container tooling, though that was explicitly a prototype rather than a shipped feature at launch.
Trade-offs
Firecracker isn’t a product you buy or configure directly on most AWS services — it’s infrastructure Lambda and Fargate manage for you, so the control you get is whatever those services’ own APIs (lifecycle hooks, network connectors) expose.
The snapshot model’s main pitfall — build-time state leaking into every MicroVM instance — is easy to trip over if you’re used to containers, where per-instance initialization normally happens at container start, not at image build.
AWS’s published boot-time (under 125 ms) and memory-overhead (under 5 MiB) figures come from its own 2018 announcement rather than an independent benchmark, and newer figures for current Lambda/Fargate performance aren’t broken out separately from the services’ own published numbers.
Firecracker is open source and usable outside AWS, but running it yourself means owning the orchestration (image management, networking, snapshotting) that Lambda and Fargate otherwise handle for you.
Who Should Care
If you’re building on Lambda or Fargate, you’re already using Firecracker whether you think about it or not — the practical relevance is mainly in understanding the lifecycle hooks and the build-time-state pitfall above. If you’re building your own multi-tenant platform that needs to run untrusted code from many customers with strong isolation and fast cold starts, Firecracker (or a Firecracker-based platform) is a legitimate building block to evaluate directly, separate from AWS’s own managed services.
Bottom Line
Firecracker is the answer to a specific question: how do you give every customer invocation VM-grade isolation without paying VM-grade boot times or memory overhead for it. A minimal KVM-based device model gets the boot time and memory down; snapshot-based launch and suspend gets the latency down further by skipping the build step entirely at request time. It’s not a general-purpose virtualization platform, and it’s not something most AWS customers configure directly — but it’s the reason Lambda can isolate millions of concurrent, untrusted function invocations without each one costing what a real VM would.
FAQ
Is Firecracker the same thing as the Nitro System? No. Nitro is AWS’s offload hardware and hypervisor for virtualizing full EC2 instances. Firecracker is a separate, open-source VMM that runs microVMs — including, for Fargate, on top of bare-metal EC2 instances — purpose-built for short-lived, multi-tenant workloads like Lambda functions and Fargate tasks.
Can I use Firecracker outside AWS? Yes. AWS open-sourced it under the Apache 2.0 license in November 2018, and it’s usable as a standalone virtual machine monitor on any Linux host with KVM support.
Why does Lambda feel faster than booting a real VM? Lambda doesn’t boot a MicroVM from scratch on every invocation. It restores a pre-built snapshot of disk and memory captured after your container image’s build and startup already ran once, which AWS describes as a near-instant launch and resume.
What’s the biggest mistake developers make with Lambda MicroVMs? Generating per-instance secrets, unique IDs, or network connections during the container build. Because the build’s end state is captured in the shared snapshot, anything created then gets reused by every MicroVM later restored from that image version — AWS’s documentation specifically recommends generating those values inside the /run lifecycle hook instead.
A single user click can fan out across a dozen microservices before a response comes back — an API gateway, an auth service, three data services, a cache, a queue. When that request is slow or fails, the question “where, exactly, did it go wrong” used to require correlating timestamps across a dozen separate logging systems by hand. Distributed tracing solves this by stitching every hop of a request into one connected trace, and in 2026 that stitching runs almost entirely on two standards that didn’t exist a decade ago: OpenTelemetry, the CNCF’s vendor-neutral instrumentation framework, and the W3C’s Trace Context specification, the header format that lets that trace survive crossing between services built by different teams on different vendors’ tooling. We’ve already compared the observability platforms you’d send this data to; this piece is about the open standard that gets the data there in the first place.
At a Glance
Standard
What it defines
Governed by
What it answers
OpenTelemetry
APIs, SDKs, a Collector, and semantic conventions for generating and exporting traces, metrics, and logs
Cloud Native Computing Foundation (CNCF); formed from a 2019 merger of OpenTracing and OpenCensus
“How do I instrument my code once and send telemetry to any backend?”
W3C Trace Context
The traceparent and tracestate HTTP headers that carry a trace’s identity between services
World Wide Web Consortium (W3C Recommendation, November 2021)
“How does a trace survive crossing from one vendor’s/team’s service to another’s?”
The short version: OpenTelemetry is the instrumentation layer that generates and exports telemetry from your code; Trace Context is the narrow but critical wire-format piece that makes a trace ID survive a network call between two independently built services. OpenTelemetry’s traces use Trace Context under the hood, which is exactly why a trace can flow unbroken from your API gateway through a dozen different backend services and vendors without anyone having to agree on a shared tracing vendor first.
What a distributed trace actually is
A trace represents one request’s full journey through a system, built from spans — one span per unit of work (an HTTP call, a database query, a function invocation). Each span has a start time, duration, and a parent span, which is what lets tools reconstruct the whole call tree: gateway calls auth, auth calls the user database, gateway then calls the recommendations service, which calls a cache and falls through to another database on a miss. Without a shared identifier threading through all of that, a request’s spans would just be disconnected log lines across a dozen systems with no way to group them back together. That’s the specific problem both standards exist to solve, at two different layers.
OpenTelemetry: one instrumentation layer, any backend
OpenTelemetry describes itself as an observability framework and toolkit for generating, exporting, and collecting telemetry data — explicitly not a backend itself; storage and visualization are left to whatever tool you send the data to. It formed in 2019 from the merger of two competing earlier projects, OpenTracing and OpenCensus, which the CNCF’s own documentation frames as both having independently identified the same gap: no standard way to instrument code once and have it work across vendors. Its core pieces:
APIs define how applications generate telemetry, independent of any particular backend.
Language SDKs implement those APIs and the specification, handling the actual export logic for a given language runtime.
The Collector is a standalone proxy process that receives, processes (batches, filters, redacts), and exports telemetry — so your application code doesn’t need to know or care where the data ultimately lands.
Semantic conventions standardize attribute names (like http.method or db.system) so a span generated by one team’s Python service and another team’s Go service describe the same kind of operation the same way.
OpenTelemetry covers three signal types — traces, metrics, and logs — under one specification and one wire protocol (OTLP), which is the practical reason it displaced vendor-specific SDKs: instrument once with OpenTelemetry, and you can point the Collector at Datadog, Grafana’s Tempo/Mimir/Loki stack, New Relic, or an open-source backend without re-instrumenting a single line of application code.
W3C Trace Context: making a trace survive crossing a boundary
Before this spec existed, every tracing vendor propagated trace identity between services its own proprietary way. The W3C’s own framing of the problem it solves is blunt: in a multi-vendor environment, traces from different vendors couldn’t be correlated, traces broke at vendor boundaries, intermediaries dropped vendor-specific metadata they didn’t recognize, and cloud platforms had no standard header to even look for. Trace Context fixes this with two HTTP headers.
The traceparent header carries the request’s position in its trace, in a fixed, fast-to-parse format:
traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01
Fields, left to right:
version 2 hex chars - currently "00"; "ff" is forbidden
trace-id 32 hex chars - identifies the entire trace; all zeros is invalid
parent-id 16 hex chars - identifies the calling span; all zeros is invalid
trace-flags 2 hex chars - rightmost bit is "sampled"; other bits reserved (0)
Every service that receives this header and makes a further downstream call generates a new parent-id for its own outgoing span while keeping the same trace-id — that’s the entire mechanism that lets a backend reassemble a hundred disconnected-looking log lines into one coherent request tree.
The companion tracestate header carries vendor-specific data as comma-separated key/value pairs, so a tracing vendor can stash its own metadata on a span without breaking interoperability with everyone else’s. The specification requires implementations to propagate at least 512 characters of tracestate and allows up to 32 list members; when truncation is unavoidable, whole entries are dropped — oversized ones first — rather than corrupting what remains. As the spec itself puts it, trace context is deliberately “split into two individual propagation fields supporting interoperability and vendor-specific extensibility” — one field for universal correlation, one field for whatever extra a specific vendor needs.
How the two standards fit together
Layer
Question it answers
Lives where
OpenTelemetry API/SDK
How does my application code generate a span in the first place?
Inside your application’s process, per language
W3C Trace Context
How does that span’s trace ID survive an HTTP call to another service?
On the wire, as HTTP headers
OpenTelemetry Collector
Where does all this data go, and how is it batched/filtered/redacted first?
A separate process, usually one per host or cluster
Observability backend
How do I search, visualize, and alert on this data?
Datadog, Grafana stack, New Relic, or a self-hosted backend — a separate choice entirely
Trade-offs
Pros: instrumenting once with OpenTelemetry avoids vendor lock-in at the code level — switching observability backends becomes a Collector configuration change, not a re-instrumentation project. Trace Context being a W3C standard, rather than a single vendor’s format, means a trace generated in your services can stay intact even through third-party APIs, CDNs, and managed cloud services that have adopted the same header.
Cons: OpenTelemetry’s breadth (three signal types, many languages, a Collector with its own configuration surface) is genuinely more to learn than a single vendor’s proprietary agent, and its own documentation is explicit that it is not a backend — you still need to choose and operate one. Trace Context also only standardizes propagation; it says nothing about sampling decisions, span naming, or what gets recorded, which is why semantic conventions exist as a separate, still-evolving piece of the OpenTelemetry specification.
Who should adopt this, and when
If you’re building a new service today, instrumenting with the OpenTelemetry SDK from day one is close to a default best practice at this point — it costs little extra over a vendor-specific agent and keeps your options open on the backend. If you’re already running a proprietary tracing agent and considering a switch, check whether it can ingest OTLP directly (most major observability vendors, including the ones we’ve covered in our platforms comparison, support it) before committing to a rip-and-replace instrumentation project. If your services already cross team or vendor boundaries — microservices owned by different teams, calls out to managed cloud APIs, a service mesh sitting between everything — verifying that Trace Context propagation isn’t being silently dropped by a proxy or load balancer in the path is worth an explicit check, since a single hop that strips the header will fracture every trace that passes through it.
Bottom line
OpenTelemetry and W3C Trace Context solve two different, complementary problems: OpenTelemetry standardizes how telemetry gets generated and exported so you’re not locked into one vendor’s instrumentation, and Trace Context standardizes the handful of bytes that have to survive a network hop for a trace to stay connected across that boundary at all. Together they’re why “distributed tracing” went from an expensive, vendor-locked capability a decade ago to something close to table stakes for any microservices architecture in 2026 — and why the choice of observability backend (which we cover separately) has become decoupled from the choice of how you instrument your code.
FAQ
Do I need both OpenTelemetry and Trace Context, or can I pick one? They’re not alternatives — OpenTelemetry’s tracing implementation uses the W3C Trace Context format internally for HTTP propagation. Adopting OpenTelemetry’s SDK means you get Trace Context propagation largely for free.
What replaced OpenTracing and OpenCensus? OpenTelemetry. The CNCF’s own documentation describes it as formed from a 2019 merger of those two earlier, competing projects, which had separately converged on the same unmet need for a vendor-neutral instrumentation standard.
What’s OTLP? The OpenTelemetry Protocol — the wire format the SDKs and Collector use to transmit traces, metrics, and logs, independent of whichever backend ultimately receives them.
Does Trace Context guarantee every service actually gets traced? No — it only standardizes how trace identity propagates once a trace exists. If any single hop in a request path doesn’t forward the traceparent header (an older proxy, a misconfigured gateway), the trace breaks at that point regardless of how well-instrumented the services on either side are.
How does this relate to the observability platforms I’d actually use? OpenTelemetry and Trace Context are the instrumentation and propagation layer; Datadog, the Grafana (LGTM) stack, and New Relic are backends you send that telemetry to for storage, search, and alerting. Our observability platforms comparison covers that backend decision; this piece covers what feeds it.
Static Application Security Testing (SAST) tools scan source code for vulnerability patterns before anything ships — and in 2026, a growing share of that source code is AI-generated or AI-assisted. That matters for SAST vendors specifically: a tool that only flags obviously bad patterns won’t catch the subtler mistakes that large language models reliably introduce (missing authorization checks, prompt-injection-adjacent string concatenation, reused secrets copied from training data patterns). Semgrep, Checkmarx One, and GitHub Advanced Security (GHAS) are three of the most widely deployed SAST platforms, and each has leaned into AI differently — not just to find bugs, but to triage and fix them. We checked each vendor’s current pricing and product pages before writing this comparison. For background on the underlying risk this category addresses, see our walkthrough of OWASP’s guidance on securing AI-generated code and our review checklist for AI-generated code security.
At a Glance
Tool
Starting Price
Free Plan
Best For
Key Specs
Semgrep
Free up to 10 contributors; Teams from $30/contributor/month
Yes — Free Edition, up to 10 contributors, 10 repos, AI-powered triage included
Teams wanting fast, open-core SAST with transparent per-seat pricing
Rule-based semantic pattern matching, open-source engine (Semgrep OSS) plus hosted platform, Semgrep Assistant AI triage/autofix
Checkmarx One
Custom — no public price, quoted per package
No self-serve free tier; demo-only
Large enterprises wanting a single modular AppSec platform (SAST+SCA+DAST+ASPM)
Modular packages (Essentials/Professional/Enterprise), Fusion AI correlation engine, Triage Assist and Remediation Assist AI features
Semgrep is the easiest to start with and the most transparent on price — its free tier genuinely covers small teams, and its AI assistant is included at every tier rather than gated behind a separate add-on. Checkmarx One is built for large, regulated enterprises that want one platform covering SAST, SCA, DAST, and posture management together, but you’ll go through a sales cycle to find out what it costs. GitHub Advanced Security is the most natural fit if your code already lives on GitHub — its CodeQL engine and Copilot Autofix sit directly in the pull-request flow, at a clearly published per-committer price.
What Each One Is and How It Works
Semgrep is built around an open-source pattern-matching engine (Semgrep OSS) that understands code structure, not just text, so a rule can match “any call to this function where an argument isn’t sanitized” across several languages with one syntax. The hosted Semgrep AppSec Platform layers a dashboard, supply-chain (SCA) and secrets scanning, and Semgrep Assistant — an AI layer that explains findings in plain language, suggests fixes, and auto-triages likely false positives, consuming “AI credits” that scale with your plan.
Checkmarx One is a long-established enterprise SAST vendor’s unified platform, combining SAST, software composition analysis, API security, and application security posture management (ASPM) under one roof, sold in modular packages (Essentials, Professional, Enterprise) rather than a flat per-seat price. Its AI layer — marketed as Fusion, Triage Assist, and Remediation Assist — correlates findings across scanners, ranks them by exploitability, and generates candidate fixes for developers to review, drawing from a shared prepaid “Checkmarx Credits” balance rather than unlimited usage.
GitHub Advanced Security bundles GitHub’s security products — now sold as separable add-ons, GitHub Code Security and GitHub Secret Protection — on top of GitHub’s free CodeQL semantic analysis engine and Dependabot. CodeQL treats code as a queryable database, so a single query can find every place a tainted input reaches a dangerous sink across an entire codebase. Copilot Autofix, GitHub’s AI remediation layer, reads a CodeQL alert and proposes a fix as a normal code suggestion inside the pull request, which a human still has to review and accept before it merges.
Catching Vulnerabilities in AI-Generated Code
All three vendors now explicitly position part of their AI messaging around AI-written code specifically — not because SAST engines need a different detection method for LLM output (a SQL injection pattern is a SQL injection pattern regardless of who typed it), but because AI assistants tend to reproduce certain mistakes at higher volume: missing input validation copied from a plausible-looking but incomplete example, hardcoded credentials pattern-matched from public training data, and authorization checks omitted because the model wasn’t given enough context about who should be allowed to call a given function. Mend.io, Semgrep, and Checkmarx all now market AI-code-aware scanning as a named feature (Mend calls it “AI-generated code security”; Checkmarx lists an “AI Inventory” and “LLM Scanner”), and GitHub’s Copilot Autofix closes the loop by proposing a fix in the same AI-assisted workflow that may have introduced the bug. The practical takeaway for teams is the same across all three tools: none of them replace human review, and all three work best wired directly into CI so that AI-generated pull requests get scanned before merge, not after.
A minimal example of the kind of pattern-based rule Semgrep (or a similarly structured CodeQL query) would flag, whether the code was written by a person or an AI assistant:
rules:
- id: flask-sql-injection-string-format
languages: [python]
severity: ERROR
message: >
User input is concatenated directly into a SQL query string.
Use parameterized queries instead.
patterns:
- pattern: $CURSOR.execute("..." + $INPUT + "...")
- pattern-not: $CURSOR.execute("...", (...))
Pricing Breakdown
Plan
Price
Notes
Semgrep Free Edition
$0
Up to 10 contributors, up to 10 repos (10 private), 60 total AI credits, GitHub/GitLab auth only (no SSO).
Semgrep Teams
Starting at $30/contributor/month for Code (SAST); SCA add-on $30/contributor/month; Secrets add-on $15/contributor/month
Adds SSO, up to 500 private repos, 20 AI credits per developer/month, priority support.
Semgrep Enterprise
Custom, contact sales
Unlimited repos, 50 AI credits per developer/month, custom AI model provider, on-prem SCM support, dedicated account manager.
Checkmarx One (all tiers)
Custom, contact sales — no public list price
Priced per package (Essentials/Professional/Enterprise) and tailored to deployment (SaaS vs. self-hosted) and developer count; the Fusion/Triage/Remediation offering bundles 10 free contributing-developer SAST licenses.
GitHub Code Security
$30 per active committer, per month
Includes CodeQL-based SAST and Copilot Autofix suggestions; “active committer” means anyone who commits to a private repo with the feature enabled in a given month.
GitHub Secret Protection
$19 per active committer, per month
Secret scanning and push protection; sold separately from Code Security since GitHub split GHAS into standalone products.
GitHub public repos
$0
CodeQL, Dependabot, and secret scanning are free on public repositories regardless of plan.
Checkmarx’s lack of public pricing is a genuine feature of how the vendor sells, not a gap in our research — the company’s own pricing page confirms quotes are custom and handled through sales, typically returned within one business day.
Pros and Cons
Semgrep
Pros: transparent published pricing, genuinely useful free tier, open-source core you can run entirely offline, AI triage/autofix included at every paid tier rather than a separate SKU
Cons: less breadth than Checkmarx across DAST/ASPM/container security; AI credits are metered and can run out on heavy-use teams on lower tiers
Checkmarx One
Pros: broadest single-platform coverage (SAST, SCA, API security, DAST, ASPM, secrets), mature enterprise support and compliance track record, modular packages let you add capability incrementally
Cons: no public pricing or self-serve trial, so budgeting requires a sales conversation; AI features are credit-metered and gated by package tier in ways that the vendor’s own FAQ is inconsistent about
GitHub Advanced Security
Pros: lives natively inside the PR workflow developers already use, CodeQL is a mature and well-documented engine, Copilot Autofix proposes fixes as ordinary suggested changes, free for public repos
Cons: ties you to GitHub as your source-code host, per-active-committer pricing for private repos can get expensive at scale, narrower scope (no built-in DAST or full ASPM) compared to Checkmarx
Who It’s a Good Fit For
Choose Semgrep if you want predictable, published pricing and a free tier that actually works for a small team, with AI triage included rather than upsold separately.
Choose Checkmarx One if you’re a large or regulated enterprise that wants one vendor covering SAST, SCA, DAST, and posture management, and you have the budget and procurement process for a custom contract.
Choose GitHub Advanced Security if your code already lives on GitHub and you want security findings and AI-suggested fixes to show up directly in the same pull requests your team already reviews.
Who Should Look Elsewhere
Teams that need deep dynamic (DAST) or interactive (IAST) testing as a primary requirement, rather than static analysis, should weigh Checkmarx’s bundled DAST against a dedicated DAST specialist. Teams hosting code outside GitHub (GitLab, Bitbucket, self-hosted Git) can’t use GitHub Advanced Security at all and should compare GitLab’s own built-in SAST or a host-agnostic tool like Semgrep or Checkmarx instead. And budget-constrained teams that can’t clear Checkmarx’s sales process or GHAS’s per-committer cost at their headcount should start with Semgrep’s free tier or its open-source CLI before evaluating anything paid.
Bottom Line
None of these three tools “solve” AI-generated code risk by themselves — they’re pattern- and data-flow-based scanners that happen to be good at catching the kinds of mistakes AI assistants make at scale, provided they’re wired into CI and reviewed by a human. Semgrep offers the clearest path from free to paid, Checkmarx offers the broadest enterprise platform behind a custom quote, and GitHub Advanced Security offers the tightest workflow integration if you’re already a GitHub shop.
FAQ
Do these tools specifically detect “AI-generated” vulnerabilities differently from human-written ones? No — the underlying detection methods (pattern matching, data-flow/taint analysis) don’t distinguish code by who or what wrote it. What’s changed is vendor marketing and some added context features (like Mend’s “AI-generated code security” and Checkmarx’s “AI Inventory”) aimed at flagging code that came from an AI assistant so teams can apply extra scrutiny or policy.
Is Semgrep’s free tier usable for a real team, or is it just a trial? It’s a genuine permanent free tier, not a time-limited trial — up to 10 contributors and 10 repositories, with Semgrep’s own AI-powered detection and triage included, per Semgrep’s published pricing page.
Why doesn’t Checkmarx publish prices? Checkmarx sells modular packages tailored to deployment model (SaaS vs. self-hosted), module selection, and developer count, and states on its own pricing page that quotes go through sales rather than a self-serve checkout.
Is Copilot Autofix the same thing as GitHub Advanced Security? No — Copilot Autofix is an AI remediation feature that works with CodeQL alerts generated by GitHub Code Security (one of the two products that replaced the older single “GitHub Advanced Security” bundle). You need Code Security enabled to get CodeQL alerts for Autofix to act on.
Can I use more than one of these tools together? Yes, and many teams do — for example, running GitHub Advanced Security for native PR-level checks on GitHub-hosted repos while also running Semgrep for custom organization-specific rules, or layering Checkmarx’s ASPM over multiple scanners’ output for a single risk view.
This is not a guide about collaborative document editing — if you’re comparing Notion, Google Docs, and Coda for team documents, see our separate collaborative document editing comparison. This article is about personal knowledge management (PKM): building a linked, searchable second brain out of your own notes, using backlinks and knowledge graphs rather than folders and shared docs. Notion, Obsidian, and Logseq approach that problem in three very different ways, and the right pick depends heavily on whether you want your notes to live in the cloud or on your own disk.
At a Glance
Tool
Price
Free Plan
Best For
Key Specs
Notion
$10/seat/month (Plus)
Yes — unlimited pages for solo use
People who want databases, pages, and light PKM in one cloud workspace
Backlinks and a basic graph view exist but are secondary to Notion’s page/database model
Obsidian
Free core app; Sync add-on $4/user/month (annual)
Yes — the entire core app, no limits, no account needed
People who want local-first, plain-Markdown notes with a serious backlink graph
Notes stored as local Markdown files; graph view, backlinks, and plugins are core, not add-ons
Logseq
Free and open-source
Yes — the entire app
People who want an outliner-style, block-based PKM tool with no subscription at all
If backlinks and a knowledge graph are the main reason you’re shopping for a PKM tool, Obsidian is the strongest pick: it stores your notes as plain Markdown files on your own device, builds its entire interface around linking ideas together, and the core app costs nothing — you only pay if you want Obsidian’s own sync or publishing service instead of a free alternative like Git or a synced folder. Logseq is the right call if you want that same local-first, link-everything philosophy but prefer an outliner (block-based, journal-first) way of writing over Obsidian’s page-based Markdown editor, and you want the entire tool, not just the core, to be free and open-source. Notion is worth choosing only if you want PKM as one feature inside a broader workspace that also handles project tracking, wikis, and databases — its backlinks and graph view work, but they’re clearly secondary to its page-and-database model, and real PKM power users tend to outgrow it.
What “Personal Knowledge Management” Actually Means Here
PKM tools are built around the idea that your notes become more useful when they’re densely linked to each other rather than filed into folders. You write a note, link it to related notes with a double-bracket reference, and over time a graph of connected ideas emerges that you can browse visually or search by connection rather than by folder location. This is a different job than collaborative document editing (real-time co-writing a shared doc with a team) or project management (tracking tasks and deadlines) — though Notion blurs those lines by trying to do all three at once.
Obsidian and Logseq were both built specifically around this linking model and store your data as local files you control — Obsidian in standard Markdown files organized by page, Logseq in an outliner format organized by block and daily journal entries. Notion stores everything in its own cloud database and added backlinks and a basic graph view later, as a feature layered onto its page-and-database architecture rather than the foundation of it.
“Free without limits”; notes stored locally, no telemetry collected
Sync (optional)
$4/user/month annual, or $5/month monthly
Encrypted cross-device sync, version history, shared vaults
Publish (optional)
$8/site/month annual, or $10/month monthly
Publish notes to the web with a custom theme
Commercial license
$50/user/year
Required for for-profit organizational use beyond personal use
Catalyst (one-time)
$25
Early access to betas, optional, supports development
Because Obsidian’s vault is just a folder of Markdown files, you can skip the paid Sync service entirely and sync your vault with iCloud, Dropbox, Syncthing, or a private Git repository at no extra cost — a meaningful difference from Notion and Logseq’s cloud-hosted approaches.
Logseq (official site): the desktop and mobile apps are free and open-source, with no subscription required to use the core product, consistent with its stated positioning as a “privacy-first, open-source platform for knowledge management and collaboration.” Logseq has discussed a paid sync/cloud service in the past, but we could not verify current, specific pricing for any such add-on directly from the vendor’s own site at the time of writing — if a paid Logseq Sync tier matters to your decision, confirm current pricing directly on logseq.com before relying on a third-party figure.
Pros and Cons
Notion — Pros: polished UI, databases and PKM in one tool, strong template ecosystem. Cons: backlinks/graph view are an afterthought, your data lives in Notion’s cloud by default, gets expensive once a team needs Business-tier features.
Obsidian — Pros: free core app with no limits, plain-Markdown files you fully own, huge community plugin ecosystem, graph view is central to the product. Cons: steeper learning curve than Notion, mobile experience depends on plugins, paid Sync/Publish are optional but add cost if you want Obsidian’s own hosted services.
Logseq — Pros: entirely free and open-source, outliner/journal-first workflow suits daily-notes habits, local-first by default. Cons: smaller plugin ecosystem than Obsidian, less polished UI, sync/cloud offering details are harder to pin down than Obsidian’s.
Who It’s a Good Fit For — and Who Should Look Elsewhere
Choose Obsidian if you want the deepest backlink/graph experience, plan to accumulate years of notes, and want to own your files outright rather than trust them to a vendor’s cloud. Choose Logseq if that same local-first philosophy appeals to you but you prefer a daily-journal, block-based outliner over Obsidian’s page-based Markdown editing, and you want the tool itself (not just a free tier) to be fully open-source. Choose Notion if PKM is a secondary need and you’d rather have one tool that also handles project databases, wikis, and light team collaboration — just go in knowing its backlinks and graph view won’t satisfy someone who wants PKM to be the main event. None of these three is the right tool if your actual need is real-time collaborative document editing for a team — that’s a different job, covered in our document editing comparison linked above.
Bottom Line
For serious personal knowledge management built around backlinks and a knowledge graph, Obsidian and Logseq both beat Notion on philosophy and cost — Obsidian for its plugin ecosystem and page-based Markdown, Logseq for being fully open-source and journal-first. Notion remains a fine choice only if PKM is a nice-to-have feature inside a broader workspace tool you already use for other things.
FAQ
Can I use Obsidian or Logseq without paying anything, ever? Yes for personal use. Obsidian’s core app is free without limits for individuals (a paid commercial license applies to for-profit organizational use), and Logseq’s entire app is free and open-source for everyone.
Do I need Obsidian Sync to use Obsidian on multiple devices? No — Sync is an optional, paid convenience. You can sync your vault folder yourself with iCloud, Dropbox, Syncthing, or Git at no additional cost.
Is Notion’s graph view as useful as Obsidian’s? It covers the basics (seeing linked pages visually), but Obsidian’s graph and backlinking are more central to daily use and have a much larger plugin ecosystem built around extending them.
What’s the real difference between Obsidian and Logseq? Obsidian organizes notes as traditional pages written in Markdown; Logseq is block-based and outliner-style, built around a daily journal you link ideas into as you write, rather than separate standalone pages.
Why isn’t Evernote or OneNote in this comparison? We cover those cloud-first, search-oriented note apps separately — see our existing Evernote vs OneNote vs Obsidian comparison. This article focuses specifically on backlink-driven, local-first PKM tools instead.
We’ve already covered watsonx.ai and IBM’s Granite model family — the part of IBM’s AI platform developers actually touch when they pick and prompt a model. But “watsonx” is IBM’s name for a three-product stack, and the other two pieces do the work that makes watsonx usable by a regulated enterprise rather than just a developer: watsonx.data, which supplies the governed data lakehouse AI systems actually query, and watsonx.governance, which tracks, audits, and polices every model and agent once it’s running. Here’s what each one actually does and costs, verified against IBM’s own product and pricing pages.
At a Glance
Product
What it does
Pricing model
watsonx.data
Open, hybrid data lakehouse — Presto, Spark, OpenSearch, and Cassandra engines over Iceberg/Hive/Delta Lake tables
Consumption-based (per-resource-unit) or flat monthly subscription; BYOC and on-prem are quote-based
Published starting prices per plan, described by IBM as “indicative”; enterprise software pricing is quote-based
watsonx.ai (for context)
Model catalog, tuning, and deployment platform — covered in our earlier piece
Consumption-based on IBM Cloud or on-prem as a Service
Best for
Regulated enterprises (finance, healthcare, government) running multiple AI systems — including third-party ones — that need a single governed data and compliance layer underneath them
Short Verdict
watsonx.data and watsonx.governance answer two different questions enterprises ask once an AI pilot becomes something that touches real decisions: where does the data actually live, and who’s accountable when a model is wrong or out of compliance. watsonx.data’s open-table-format approach (Iceberg, Hive, Delta Lake, with zero-copy access) is a reasonable bet against vendor lock-in. watsonx.governance’s pitch — that it can govern AI systems built outside IBM’s own stack, not just watsonx models — is the more differentiated piece, and IBM backs it with real analyst recognition (2026 Gartner Magic Quadrant, IDC MarketScape, Forrester Wave placements). Both products publish real starting prices, which is unusual for enterprise AI tooling, but IBM is explicit that those numbers are indicative and vary by region — treat them as a budgeting starting point, not a quote.
watsonx.data: The Lakehouse Underneath watsonx
IBM describes watsonx.data as an “open, hybrid data lakehouse” — a single logical layer that lets different query engines work against the same stored data rather than copying it into each engine’s own format. The product page lists Apache Iceberg, Hive, and Delta Lake as the open table formats it supports, and emphasizes “zero-copy access” to avoid duplicate data copies sitting in multiple systems. It ships in three deployment modes: a fully managed SaaS option, self-managed software, and “BYOC” (bring your own cloud), where you run the software in a cloud account you already pay for.
Rather than one generic query engine, watsonx.data routes different workloads to the engine suited to the job:
Engine
What it’s for
Presto
Distributed SQL for interactive BI and analytics, with federation across sources; a GPU-accelerated version is in technical preview
Spark
Distributed data processing for data engineering, large-scale model training, and AI/ML pipelines
OpenSearch
Combined vector and keyword search for generative-AI and retrieval applications
Cassandra
Distributed NoSQL for fast reads/writes in operational and GenAI applications
Governance is built into the same layer: IBM states that access controls, policies, lineage, and data-quality signals apply consistently across all of that distributed data, regardless of which engine is querying it. IBM’s product page doesn’t spell out the exact API-level integration between watsonx.data and watsonx.ai, but case studies IBM cites — such as giving watsonx Orchestrate agents shared context pulled from watsonx.data — point to the lakehouse acting as the common data source multiple watsonx tools draw from.
watsonx.data Pricing
Plan
Starting price
Notes
Pay Per Use
$1.00 USD per Resource Unit (RU)
AWS-deployed instance; consumption-based, metered per second with a 1-minute minimum
Subscription
$83.30 USD per month
AWS-deployed instance; fixed monthly cost instead of metered consumption
BYOC / on-prem
Quote-based
Pay for the software only and run it on infrastructure/credits you already have; on-prem supports IBM Power and Fusion HCI
Underneath the two headline plans, IBM meters compute in Resource Units at specific published rates: lakehouse compute runs 2.0–5.5 RU/hour depending on tier, vector-search tiers run 1.25–16.50 RU/hour, and Cassandra ranges from 341 RU/month (on-demand Starter) up to 1,467,489 RU/year for a one-year committed Extra Large cluster. Core support services add a flat 3.0 RU/hour per account on top of compute. All of these figures are IBM’s published list prices; IBM states they’re indicative, vary by country, exclude taxes, and depend on local product availability — so they’re a real starting point for a budget, not a final number.
watsonx.governance: Governing AI You Didn’t Build Yourself
watsonx.governance is IBM’s AI governance product, and its core pitch is scope: IBM positions it to oversee AI systems across an enterprise’s entire environment, including models and agents built on other vendors’ platforms, not only watsonx deployments. IBM groups its capabilities into four themes:
Visibility: a “governance graph” mapping relationships among AI systems, risks, controls, and policies across the organization, including detection of unapproved “shadow AI” usage.
Control: automated policy enforcement, regulatory obligation mapping, and automatic capture of compliance evidence.
Accountability: real-time tracking of business outcomes and risk signals tied back to specific AI systems.
Continuous monitoring: ongoing checks for compliance issues, operational problems, and emerging risk across the AI lifecycle, mapped to frameworks including the EU AI Act, NIST AI standards, and ISO 42001.
IBM also layers AI-native assistants into the product itself to help onboard new use cases and automate governance workflows, and integrates governance with IBM OpenPages for broader governance, risk, and compliance (GRC) work, plus connectors into Azure, AWS, and Slack. IBM cites its own placement in the 2026 Gartner Magic Quadrant for AI Governance Platforms, the IDC MarketScape, and The Forrester Wave for AI Governance Solutions as third-party validation, alongside customer-reported results — Infosys cites a 150% gain in operational efficiency across more than 2,700 AI use cases, and Careerforce Pro cites an 85%-plus reduction in time-to-hire. Both figures are vendor-reported customer results, not independently audited numbers, so treat them as directional case studies rather than guaranteed outcomes.
watsonx.governance Pricing
Plan
Starting price
Deployment
Included
Model management
$0.64 (unit not stated on the page)
IBM Cloud
1 basic instance, 1 module, 1 concurrent user
Risk & Compliance: Basic
$3,500/month
IBM Cloud
1 basic instance, 1 module, 1 concurrent user
Risk & Compliance: Advanced
$6,450/month
Enterprise software
1 advanced instance, 1 module, 1 concurrent user
watsonx.governance on AWS
$42,000 (period not stated)
AWS Cloud
1 basic instance, 5 AI use cases, 12,000 evaluations, 25 concurrent users
IBM sells additional instances, modules, and concurrent users as add-ons on the Risk & Compliance plans, and additional use cases (in packs of 10) on the AWS plan. Enterprise software pricing is based on virtual processor core (VPC) count, with no starting figure published — that tier requires a quote. As with watsonx.data, IBM labels these prices “indicative” and routes buyers toward a live demo or a conversation with its AI governance team to finalize a plan.
Any engine/data regardless of which model consumes it
Explicitly scoped to govern AI outside IBM’s own platform too
Entry pricing
Consumption-based
$1/RU pay-per-use or $83.30/month subscription
From $0.64 (unit unstated) up to $42,000 for the AWS bundle
Trade-offs
watsonx.data’s product page doesn’t explain the specific technical integration with watsonx.ai beyond customer case studies — teams evaluating the stack as a unit will need IBM’s documentation or a sales engineer to confirm exactly how data flows between the two.
watsonx.governance’s customer-success figures (Infosys, Careerforce Pro) are vendor-reported, not independently audited — useful as directional evidence, not as a guaranteed ROI case.
Published prices on both products are explicitly labeled “indicative” and vary by country — real procurement will still involve a quote, especially for BYOC, on-prem, and enterprise-software tiers.
watsonx.data’s Resource Unit pricing has enough tiers and add-on metering (compute, vector, Cassandra, support) that estimating a realistic monthly bill takes real modeling, not just the two headline numbers.
Who It’s a Good Fit For
watsonx.data fits teams that want to avoid locking their data into one engine’s proprietary format, and that already run a mix of BI, Spark, and search/vector workloads against the same underlying data. watsonx.governance fits enterprises in regulated industries — especially ones already juggling AI systems from multiple vendors — that need one place to answer “which AI systems do we have, what are they doing, and can we prove it to a regulator.” Teams with only a single, simple AI deployment and no multi-vendor sprawl are less likely to need governance tooling at this scale yet.
Bottom Line
watsonx.ai gets the attention because it’s the part developers touch directly, but watsonx.data and watsonx.governance are arguably the more enterprise-specific bets IBM is making: an open lakehouse that avoids engine lock-in, and a governance layer explicitly built to watch AI systems IBM didn’t build. Both publish real starting prices — rare in this market — but both also route serious buyers toward a quote once BYOC, on-prem, or enterprise tiers come into play.
FAQ
Do I need watsonx.ai to use watsonx.data or watsonx.governance? No. Both are positioned as standalone products — watsonx.data as a general lakehouse, and watsonx.governance as explicitly able to monitor AI systems built on other vendors’ platforms.
What open table formats does watsonx.data support? IBM’s pricing page lists Apache Iceberg, Hive, and Delta Lake under its open lakehouse architecture.
What compliance frameworks does watsonx.governance map to? IBM states it maps governance initiatives to frameworks including the EU AI Act, NIST AI standards, and ISO 42001.
Are IBM’s published prices final? No. IBM explicitly labels the listed starting prices for both products as “indicative,” noting they vary by country, exclude taxes and duties, and depend on local availability — final pricing for most tiers requires contacting IBM.
Zoom, Google Meet, and Cisco Webex all offer a free tier capped around 40 minutes and 100 participants, which makes them look interchangeable until you compare what the paid tiers actually unlock — and how openly each vendor prices them. We checked pricing and limits directly against each vendor’s current site, including the Google Workspace admin documentation for Meet’s exact per-user pricing.
At a Glance
Tool
Entry Paid Price
Free Plan
Best For
Key Specs
Zoom
$14.16/host/month (Pro, billed annually)
Yes — 40 min limit, 100 participants
Teams whose main need is video meetings and webinars specifically
30-hour meeting length on paid tiers, AI meeting summaries, up to 1,000 participants on Enterprise
Yes, with a personal Google account — 60 min group call limit, 100 participants
Teams already using Gmail, Docs, and Calendar who want Meet bundled in
24-hour meeting length on all paid tiers, up to 500 participants on Business Plus
Cisco Webex
Contact sales — no public monthly price for the paid tier
Yes — 40 min limit, 100 attendees
Enterprises that already run Cisco networking/collaboration gear and need custom contracts anyway
Up to 1,000 attendees on the paid tier, FedRAMP-authorized security, AI Assistant included
The Verdict
For most small and mid-sized businesses, Zoom is still the easiest recommendation: its Pro tier is transparently priced, meeting length jumps to 30 hours, and the interface is the one most external meeting guests already know. If your company already runs on Google Workspace, paying extra for Zoom rarely makes sense — Meet is already included at a lower effective price once you’re paying for Workspace anyway, and the integration with Calendar and Gmail is tighter than any third-party tool can match. Cisco Webex is the odd one out: its free tier is genuinely competitive, but the paid tier has no public price at all, which makes it a harder sell unless you’re already a Cisco shop with an account rep who can quote you a number.
What These Tools Actually Do
All three host video calls with screen sharing, recording, and (increasingly) AI-generated summaries, but they come bundled differently. Zoom is sold as a standalone product (now rebranded “Zoom Workplace,” bundling chat, mail, and calendar around the core meeting product), so you pay for it directly regardless of what other software you use. Google Meet is not sold on its own for businesses — it’s a feature inside a Google Workspace subscription that also includes Gmail, Drive, Docs, and Calendar, so its “price” is really the Workspace price. Cisco Webex sits between the two: it’s sold as its own product, but Cisco pushes larger customers toward custom-quoted “Webex Suite” contracts rather than publishing a flat per-user rate, which is typical of Cisco’s broader enterprise sales model.
All Workspace editions allow meetings up to 24 hours long. There’s no Meet-only consumer plan for businesses — a free personal Google account can still use Meet, but with a 60-minute limit on group calls of three or more people.
Unlimited meetings capped at 40 minutes, up to 100 attendees, local recording, advanced noise cancellation
Webex Suite (paid)
Not published — “Let’s talk,” contact sales
Up to 1,000 attendees, no stated meeting time limit, unlimited cloud recording, FedRAMP-authorized security, AI Assistant included
Unlike Zoom and Google Workspace, Cisco does not publish a flat monthly or annual per-user rate for its paid Webex tier on its public pricing page as of this writing — pricing is quote-based, which is worth factoring into any comparison on cost alone.
Pros and Cons
Zoom — Pros: transparent pricing, familiar to nearly every external meeting guest, long meeting durations even on Pro. Cons: yet another subscription if you already pay for Google Workspace or Microsoft 365.
Google Meet — Pros: included in a subscription you may already have, tightest Calendar/Gmail integration, strong participant caps relative to price. Cons: can’t be bought as a standalone product for teams not on Workspace.
Cisco Webex — Pros: genuinely strong free tier, FedRAMP authorization matters for government/regulated buyers. Cons: no public price for the paid tier, which makes quick cost comparisons impossible without contacting sales.
Who It’s a Good Fit For — and Who Should Look Elsewhere
Choose Zoom if meetings and webinars are your primary need and you want a product you pay for and control directly, independent of your email provider. Choose Google Meet if you’re already on or planning to adopt Google Workspace — paying separately for Zoom or Webex on top of Workspace is hard to justify for most small teams. Choose Cisco Webex primarily if you’re a larger organization already in the Cisco ecosystem (networking gear, Webex Calling, FedRAMP requirements) where a quoted enterprise contract is normal procurement anyway; it’s a weaker fit for a small business trying to compare costs quickly online. If day-to-day text chat, not video, is your bigger pain point, see our related comparison of team chat apps: Slack vs Microsoft Teams vs Discord.
Bottom Line
Zoom wins on pricing transparency and meeting length; Google Meet wins on bundled value if you’re already paying for Workspace; Cisco Webex’s free tier is solid but its paid tier asks you to call sales before you can even compare the cost.
FAQ
Can I use Google Meet without a Google Workspace subscription? Yes, with a free personal Google account, but group calls with three or more people are capped at 60 minutes, versus 24 hours on any paid Workspace edition.
Why doesn’t Cisco Webex show a price for its main paid plan? Cisco sells Webex’s higher tiers through a quote-based enterprise sales process rather than public self-serve pricing, which its own pricing page confirms by directing visitors to “contact sales.”
Which tool supports the most meeting participants? At the entry paid tier, Google Workspace’s Business Plus (500 participants) outpaces Zoom Pro (100) and Zoom Business (300) at a lower price point; Webex’s paid tier and Zoom Enterprise both scale to around 1,000.
Do all three include AI meeting summaries? Zoom includes limited AI summaries even on its free Basic tier and unlimited summaries from Pro up. Webex includes an AI Assistant on its paid tier. Google Meet’s AI note-taking (via Gemini) is tied to specific Workspace editions and add-ons, which is worth confirming for your exact plan.
Is Microsoft Teams a video conferencing tool too? Teams includes video calling, but it’s typically evaluated alongside chat and collaboration features rather than as a standalone meeting tool — see our team chat comparison linked above for that angle.
Mailchimp is the email marketing tool most small businesses have already heard of, but it’s not the cheapest, and it’s no longer the obvious default once you compare its current pricing line by line against Brevo and MailerLite. This comparison is aimed squarely at small businesses sending regular newsletters and promotional campaigns — not creators monetizing an audience (that’s Kit’s niche) or e-commerce stores that need deep automation (that’s Klaviyo’s). We pulled every figure below from each vendor’s own pricing page.
At a Glance
Tool
Entry Paid Price
Free Plan
Best For
Key Specs
Mailchimp
$13/month (Essentials, up to 500 contacts, first 12 months)
Yes — 250 contacts, 500 sends/month
Small businesses that want templates and integrations over rock-bottom price
300+ integrations, generative AI on Standard+, up to 1M+ contact tiers
Brevo
From $9/month (Starter, 5,000 emails/month)
Yes — 300 emails/day, no contact cap stated
Businesses that want email, SMS, and a basic CRM under one login
Unlimited contacts on every paid tier (you pay for sends, not list size), built-in Sales CRM add-on
MailerLite
From $12/month (Comfort, at 500 subscribers)
Yes — 250 subscribers, 2,500 sends/month
Small businesses and solo marketers who want the simplest editor at the lowest price
Built-in landing pages and websites, 50+ automation steps on Comfort, unlimited sending on Power (fair-use)
The Verdict
For most small businesses sending a newsletter and the occasional promotion to a list under a few thousand people, MailerLite is the best value: its Comfort tier starts at $12/month, the editor is simple without feeling limited, and basic automation, forms, and even a landing page builder are included from the entry paid tier. Brevo is the strongest pick if you also want SMS campaigns or a lightweight sales CRM bundled in, because its pricing is based on emails sent rather than contacts stored — useful if you have a large list you email infrequently. Mailchimp remains a reasonable choice mainly for its template library and integration breadth, but its free plan has shrunk to 250 contacts and its paid tiers cost noticeably more than the other two for comparable list sizes.
What These Tools Actually Do
All three let you build an email list, design campaigns with a drag-and-drop editor, and automate simple sequences like welcome emails or abandoned-cart reminders. The real difference is in pricing logic and scope. Mailchimp and MailerLite price primarily around how many contacts you store, which punishes you for keeping a large list even if you rarely email all of it. Brevo instead prices around how many emails you send per month, with no contact cap on paid tiers — a meaningfully different model if your list is large but your sending cadence is light. Mailchimp has also expanded furthest beyond pure email, with a broader (and pricier) marketing-automation positioning, while Brevo has pushed into SMS, WhatsApp, and a built-in sales CRM, and MailerLite has stayed the most tightly focused on email, forms, and simple websites.
Pricing Breakdown
Mailchimp (official pricing page), prices shown for the lowest contact tier and the first 12 months:
Tier
Price
Seats
Notes
Free
$0/month
1
250 contacts, 500 sends/month or 250/day, 1 audience, no automation flows
Essentials
$13/month
3
Up to 4-step automation flows, branding removable, 24/7 chat support
Standard
$20/month
5
Up to 200 automation flows, generative AI included, custom reporting
Mailchimp’s listed prices are introductory rates for the first 12 months at the 0–500 contact tier; the page does not clearly display the ongoing renewal rate, and prices scale up automatically as your contact count grows. A 14-day free trial is available on paid tiers.
150,000 emails/month at entry; WhatsApp, advanced e-commerce, AI segmentation
Enterprise
Custom
Aimed at 1M+ contacts; SSO/SAML, dedicated IP, custom data integrations
All Brevo paid tiers are priced by monthly email volume rather than contacts stored, and annual billing saves 10% versus monthly. Brevo also sells a separate “Sales” CRM add-on (Sales Essentials / Sales Advanced) bundled with the Starter and Standard tiers.
10x your subscriber tier in monthly sends, 50 automations, 10 forms/sites
Power
$25
$22.50
Unlimited seats, automations, sites, and sending (fair-use policy)
Enterprise
Custom
Custom
200,000+ subscribers, dedicated success manager
MailerLite’s paid prices scale up as your subscriber count grows past the 500 tier shown here. Paid plans include a 14-day trial of premium features with no credit card required.
Pros and Cons
Mailchimp — Pros: largest integration library, polished templates, AI tools on Standard. Cons: shrunk free tier, pricing climbs fastest of the three, renewal pricing isn’t transparent on the page.
Brevo — Pros: unlimited contacts on every paid tier, SMS/WhatsApp and a bundled CRM, strong value if your list is large but sending is light. Cons: large price jump from Standard to Professional, exact figures require checking the live page since currency/region can change what renders.
MailerLite — Pros: cheapest entry paid tier, clean editor, built-in landing pages and a basic website builder. Cons: fewer enterprise-grade features, smaller integration ecosystem than Mailchimp.
Who It’s a Good Fit For — and Who Should Look Elsewhere
Choose MailerLite if you’re a small business or solo marketer on a tight budget who wants one simple tool for email, a landing page, and light automation. Choose Brevo if you have a large contact list you don’t email constantly, or if you want SMS and a basic CRM without adding another subscription. Choose Mailchimp if you’re already embedded in its template and integration ecosystem, or you need its specific AI and reporting features on the Standard tier and the price difference isn’t a dealbreaker. None of these three is built for serious e-commerce automation at scale — stores with real order-flow complexity should look at a platform like Klaviyo instead (see our Klaviyo review), and teams whose main bottleneck is tracking deals rather than sending newsletters need a CRM, not an email platform.
Bottom Line
MailerLite offers the best price-to-feature ratio for a typical small business newsletter; Brevo is the better pick if your list is large or you want SMS and CRM bundled in; Mailchimp is worth the premium mainly for its templates and integrations, not its pricing.
FAQ
Which of the three has the best free plan? Brevo’s free plan has no stated contact cap, only a 300-emails-per-day sending limit, which can suit a small list better than Mailchimp’s 250-contact cap or MailerLite’s 250-subscriber cap.
Do these tools charge for unsubscribed or bounced contacts? Policies vary and change over time — check each vendor’s current FAQ before importing a large list, since Mailchimp and MailerLite price around stored contacts.
Can I send SMS campaigns with any of these? Brevo supports SMS and WhatsApp natively. Mailchimp offers SMS/MMS as an add-on on Standard and Premium. MailerLite does not list native SMS sending on its pricing page.
Is there a usable free trial if I’m not ready to commit? Yes for all three — Mailchimp and MailerLite both offer 14-day trials of paid features, and Brevo’s free plan itself has no time limit, only a daily sending cap.
What happened to ConvertKit? ConvertKit rebranded to Kit and remains focused on creators monetizing a following (newsletters, courses, digital products) rather than general small-business marketing — a different use case than the three tools compared here.
Load testing tools split into two camps: ones built around a scripting language developers already know, and ones that layer a managed cloud and reporting platform on top of an open-source core. k6, Gatling, and Locust each represent a slightly different version of that split — k6 is JavaScript/TypeScript-first with a polished managed cloud, Gatling is Scala-based with a paid Enterprise tier for distributed runs and reporting, and Locust is pure Python and stays closer to “bring your own infrastructure.” We checked each project’s current pricing and docs pages before writing this comparison.
At a Glance
Tool
Starting Price
Free Plan
Best For
Key Specs
k6
Free (open source core); Grafana Cloud k6 Pro from $19/month + $0.15/VUh
Yes — 500 VU-hours/month on Grafana Cloud, plus the fully free open-source CLI
Teams already using Grafana/Prometheus wanting JS-based scripting and a managed cloud option
Scripts in JavaScript/TypeScript, Go binary, single-binary distributed-load support via k6 Operator
Gatling
Community Edition free (local use); Enterprise from €99/month (~€89/month billed annually)
Yes — Community Edition, open source, local-only runs
Teams wanting Scala/Java/Kotlin DSL scripting with professional reporting and distributed runs
Akka/Scala-based engine, async non-blocking architecture, HTML reports, Enterprise adds cloud injectors and CI integrations
Locust
Free (fully open source)
Yes — the entire tool; no paywalled tier from the core project
Python teams wanting to write load-test scenarios as ordinary Python code
Python-based, gevent-powered concurrency, distributed via master/worker nodes, web UI for live stats
Short Verdict
k6 is the best default if you want a modern scripting experience and the option to buy a managed cloud/reporting layer without switching tools. Gatling is the strongest pick when you need polished, shareable HTML/PDF-style reports and your team is comfortable in the JVM/Scala world, though its real distributed-testing power sits behind the paid Enterprise tier. Locust wins on simplicity and cost for Python-centric teams: it is genuinely free with no commercial tier gating core features, but you’ll assemble your own reporting and distributed-infrastructure story.
What Each One Is and How It Works
k6, originally built by Load Impact and now developed under Grafana Labs, is an open-source load-testing tool written in Go with test scripts authored in JavaScript or TypeScript. Tests define virtual users (VUs) that execute scripted HTTP (or gRPC/WebSocket) requests in loops, with built-in thresholds that can fail a CI build when a p95 latency or error-rate target is missed. The open-source CLI is free and runs anywhere; Grafana Cloud k6 adds hosted result storage, trend dashboards, and the ability to generate load from multiple geographic regions without managing your own load generators.
Gatling is built on Scala and Akka (now Pekko), with a DSL that can also be written in Java or Kotlin via Gatling’s newer language bindings. Its asynchronous, non-blocking architecture is designed to generate high load from a single machine with a comparatively small memory/thread footprint. The free Community Edition runs entirely locally and produces detailed HTML reports. Gatling Enterprise (formerly FrontLine) adds a web console for scheduling and comparing runs, distributed load generation across multiple injectors, and longer/larger test allowances measured in virtual users and test-duration hours.
Locust is a Python framework where load-test “users” are defined as plain Python classes with tasks decorated to represent user behavior. It uses gevent for lightweight concurrency, so a single process can simulate large numbers of concurrent users without one OS thread per user. Locust ships with a web UI for watching request rates and response times live during a run, and scales out via a master/worker model across multiple machines. The core project is maintained as open source with no paid tier; a hosted “Locust Cloud” offering from the Locust maintainers was in development as of our research and wasn’t fully live with published pricing at the time of writing.
Pricing Breakdown
Plan
Price
Notes
k6 open source
$0
Full scripting engine and CLI, run on your own infrastructure.
Grafana Cloud k6 Free
$0
500 virtual-user-hours (VUh) per month, community support, no credit card required.
Grafana Cloud k6 Pro
$19/month platform fee + $0.15 per VUh (covers 500 VUh, then pay-as-you-go; per-VUh rate decreases with volume)
Adds 8×5 email support.
Grafana Cloud k6 Enterprise
Custom, $25,000/year minimum
Annual commit, premium support, choice of Public Cloud, Federal Cloud, or Bring Your Own Cloud, scaling to up to 1 million concurrent VUs.
Gatling Community Edition
$0
Local use only, minimal distributed/reporting features.
Up to 180,000 VUs, 5 hours of testing, 3 load generators, 10 seats, distributed testing, professional support.
Gatling Enterprise
Custom, contact sales
Custom VUs, hours, load generators, seats; all integrations and premium support.
Locust (core)
$0
Fully open source, no paid tier for the testing engine itself; you provide your own compute for distributed runs.
Gatling’s enterprise prices are published in euros rather than US dollars on its pricing page; we’ve shown both the monthly and the effective annual-billed monthly rate as listed, without converting currencies, since exchange rates move independently of the vendor’s own pricing.
Pros and Cons
k6
Pros: JavaScript/TypeScript scripting is familiar to most web teams, strong native integration with Grafana/Prometheus dashboards, clean CI-friendly thresholds and exit codes
Cons: distributed load generation at real scale pushes you toward the paid Cloud tiers; VUh-based billing takes some getting used to for cost forecasting
Gatling
Pros: efficient non-blocking engine generates heavy load from modest hardware, detailed and genuinely readable HTML reports out of the box, DSL now available in Java/Kotlin as well as Scala
Cons: Community Edition’s single-machine, local-only limitation means serious distributed testing requires paying for Enterprise; Scala-first heritage can be a learning curve for teams with no JVM background
Locust
Pros: completely free with no feature-gated commercial tier, test scenarios are ordinary Python so they’re easy to version, review, and extend; live web UI is useful during exploratory runs
Cons: reporting is more basic than Gatling’s out of the box; you own the work of provisioning and scaling master/worker nodes for large distributed tests; no official vendor-backed managed cloud with published pricing as of this writing
Who It’s a Good Fit For
Choose k6 if your team already lives in Grafana/Prometheus and wants JS/TS scripting with a straightforward path to managed, geo-distributed load if you need it later.
Choose Gatling if you want the most polished reports and your organization is willing to pay for Enterprise once you outgrow single-machine local testing — especially in JVM-heavy shops.
Choose Locust if your team is Python-first, you want zero licensing cost, and you’re comfortable owning your own distributed-infrastructure and reporting setup.
Who Should Look Elsewhere
Teams that need protocol coverage well beyond HTTP/WebSocket/gRPC — heavy legacy enterprise protocol testing, for instance — may be better served by a commercial suite like Apache JMeter with its large plugin ecosystem, or dedicated vendor tools built for that protocol. Teams wanting a fully no-code, click-to-record load-testing experience with minimal scripting of any kind should also look at managed SaaS alternatives built around recorders rather than code, since all three tools here assume you’re comfortable writing test scripts.
Bottom Line
All three tools can realistically load-test the same API. The decision mostly comes down to language fit and how much you’re willing to pay for managed distribution and reporting: k6 for JS-first teams wanting an easy upgrade path, Gatling for JVM teams wanting the best reports and willing to pay for Enterprise distribution, and Locust for Python teams that want to stay free and own their own infrastructure.
FAQ
Is k6 free to use for CI load testing? Yes. The open-source k6 CLI is free and can run entirely inside your own CI pipeline; Grafana Cloud k6 is an optional paid add-on for hosted results, trends, and distributed/geo load.
Does Gatling’s free Community Edition support distributed load testing? No — per Gatling’s own pricing page, the Community Edition is described for local use, with distributed testing and multiple load generators reserved for the paid Enterprise tiers.
Is Locust really free, with no paid tier required for core features? Yes — Locust’s core engine is open source with no commercial license gating its scripting, execution, or master/worker distribution features. A hosted cloud offering from its maintainers exists but was still described as in-progress at the time of our research, without a published price.
Which tool is easiest for a team with no load-testing experience? Locust’s Python syntax and k6’s JavaScript syntax are both generally considered more approachable than Gatling’s Scala DSL for teams without a JVM background, though Gatling’s Java/Kotlin bindings narrow that gap.
Can I switch between these tools later without re-architecting my tests? Not directly — test scripts are tool-specific (JS for k6, Scala/Java/Kotlin DSL for Gatling, Python for Locust), so migrating means rewriting scenarios, though the underlying concepts (virtual users, ramp-up stages, thresholds) map fairly cleanly across all three.
Oracle’s AI coverage tends to gravitate toward two things: Database 23ai’s vector search and Oracle’s multicloud database deals. There’s an older, less-hyped piece of Oracle engineering that both of those stories quietly depend on: Exadata, the hardware-software system Oracle has sold for over 15 years, and Autonomous Database, the managed service built on top of it. Exadata is the reason Oracle can claim database performance numbers that a generic cloud VM running Oracle Database on commodity storage can’t match — not through a faster CPU, but through moving part of the database engine itself into the storage layer. Here’s what that actually means, verified against Oracle’s own architecture documentation.
At a Glance
Thing
What it is
Exadata
Engineered system pairing Oracle Database software with purpose-built storage servers and an RDMA network fabric
Key mechanism
Smart Scan: pushes SQL filtering and column projection down to storage servers, so only matching rows/columns travel back to the database tier
Autonomous Database
Oracle’s managed cloud database service, built on Exadata infrastructure, that automates tuning, patching, scaling, and failover
Deployment options
Serverless (OCI public cloud, pay-per-use), Dedicated Infrastructure, Exadata Cloud@Customer (your data center), plus multicloud on AWS/Azure/Google Cloud
Pricing model
Serverless is usage-based with a free tier and 30-day trial; Dedicated and Cloud@Customer are quote-based; Oracle publishes no list price for Exadata hardware itself
Best for
Oracle Database shops running large OLTP/analytics workloads who want storage-layer acceleration without re-architecting queries
Short Verdict
Exadata’s core idea — run part of the database engine on the storage hardware itself, and connect everything with RDMA instead of a generic network — is genuinely distinctive among relational database platforms, and it’s been refined since the first Exadata machine shipped in 2008. Autonomous Database wraps that hardware in automation that removes most of the day-to-day DBA work: patching, indexing, backups, and scaling happen without a maintenance window. The catch is the one every Oracle-engineered-system story has: Oracle’s own pages make broad performance claims (“dramatically better performance,” “extreme performance”) without publishing benchmark numbers or prices, so anything beyond the documented mechanics needs a sales conversation to confirm.
What Exadata Actually Is
Exadata is Oracle’s term for a system built from four pieces working together: database servers that run Oracle Database, storage servers that hold the data, a low-latency RDMA network fabric connecting them, and Exadata System Software that runs on both tiers. The point of the design is to target Oracle Real Application Clusters’ (RAC) shared-everything model — many database servers sharing the same storage — without making that sharing the bottleneck.
The detail that separates Exadata from “Oracle Database running on a SAN” is that the storage servers aren’t dumb disks. Each one runs a slice of Oracle Database’s own code and can process query logic locally — filtering rows, projecting columns, even applying some predicates — before anything crosses the network back to a database server. Oracle’s architecture page describes the storage servers’ CPUs as accelerating database-intensive work “similar to how GPUs accelerate graphics,” working alongside the database servers’ CPUs rather than replacing them.
Smart Scan: How the Offload Actually Works
The mechanism behind that offload is called Smart Scan (Oracle also calls it SQL Offload), and it’s the single most load-bearing idea in the Exadata design. Per Oracle’s documentation, Smart Scan kicks in automatically whenever the query optimizer picks a full table scan, a fast full index scan, or a full bitmap index scan — the scan types that would otherwise mean “read everything, then filter it after it arrives.”
Instead, the database server sends the storage servers the column projections and SQL predicates for the query. Each storage server applies those filters locally, in parallel, as it reads from flash or disk, and returns only the rows and columns that actually matched. Oracle’s own example: a query for North American sales orders of at least $500 is evaluated entirely on the storage tier, so only the matching customers’ names and addresses — not the full order table — travel back across the network. Oracle states this can reduce the data volume crossing the wire by orders of magnitude for large scans, and that the optimization still applies to compressed and encrypted tables.
Exadata System Software: What Runs Where
Component
Runs on
Job
CELLSRV
Storage servers
Core service handling Smart Scan offload, I/O Resource Manager, and flash/XRMEM tiering
IORM
Storage servers
I/O Resource Manager — stops one database from monopolizing shared storage bandwidth
MS / RS
Storage servers
Management and automatic service restart
CELLOFLSRV
Storage servers
Version-specific offload functions
libcell
Database servers
Lets Oracle Database talk to storage using Oracle’s iDB protocol over RDMA
The networking layer underneath all of this is RDMA (remote direct memory access) over a converged Ethernet fabric (RoCE), carrying a purpose-built Oracle protocol called iDB. RDMA lets one server read or write another server’s memory without routing through either machine’s operating system or network stack — no extra copying, no kernel involvement. The same fabric also carries RAC’s instance-to-instance traffic. Oracle also layers automatic, workload-aware caching on top: data moves between hard disk, flash, and XRMEM (Exadata RDMA Memory) based on access patterns, and because every storage server is reachable from every database server, that cache benefit is shared across the whole cluster rather than pinned to one machine.
Oracle’s newest storage architecture, Exadata Exascale (available from release 24.1), goes a step further by decoupling the database and Grid Infrastructure layers from the storage servers entirely, so customers can scale compute and storage independently — though it can also run alongside the older Automatic Storage Management (ASM) model, and Oracle says a full Exascale cluster needs at least five storage servers to run its own grid services rather than borrowing cycles from the database servers.
From Exadata to Autonomous Database
Exadata is infrastructure; Autonomous Database (Oracle now calls it Autonomous AI Database) is the managed service built on top of it that automates nearly everything a DBA would otherwise do by hand. Oracle’s own product page groups the automation into three themes, even though it doesn’t literally use the old “self-driving / self-securing / self-repairing” marketing labels anymore:
Automated operation: provisioning, backups, monitoring, alerting, and disaster recovery run without manual intervention; automatic indexing and partitioning tune the schema for the actual workload; compute and storage scale up to 3x base-provisioned resources with no downtime.
Automated security: patches apply without downtime, Transparent Data Encryption covers data at rest, in motion, and in backups, and Oracle Data Safe plus Database Vault add threat detection, role-based access, and always-on auditing.
Automated resilience: Oracle Autonomous Data Guard and Application Continuity recover in-flight transactions during outages, backed by the hardware redundancy and RDMA networking Exadata already provides.
Oracle’s default SLA for Autonomous Database is 99.95% uptime without a standby, rising to a claimed 99.995% with Autonomous Data Guard enabled. The service ships in several deployment shapes:
Deployment
Where it runs
Pricing model
Serverless
OCI public cloud, fully managed
Pay-per-use; free tier and 30-day trial available
Dedicated Infrastructure
OCI public cloud, single-tenant
Quote-based; more control over patch timing
Exadata Cloud@Customer
Your own data center
Quote-based; for data residency/latency requirements
Multicloud
AWS, Azure, Google Cloud (via Oracle Database@AWS/Azure/GCP)
Quote-based
Oracle also claims that consolidating multiple databases into shared, elastic Autonomous Database resource pools can cut compute costs by up to 87% — a figure from Oracle’s own marketing that, like the Exadata performance superlatives, comes with no stated benchmark methodology, so it’s worth treating as a best-case scenario rather than a typical result.
Exadata vs. Running Oracle on Generic Cloud Storage
Dimension
Exadata
Oracle DB on generic block storage
Where filtering happens
Partly in storage (Smart Scan), reducing data moved to compute
Entirely at the database server; storage just returns raw blocks
Network path
RDMA (iDB over RoCE), bypassing OS network stack
Standard storage network protocol (iSCSI, NFS, etc.)
I/O isolation across tenants
Enforced by IORM at the storage layer
Depends on the underlying storage platform’s own QoS features
Caching
Automatic, workload-aware, tiered across flash/XRMEM/disk, shared cluster-wide
Typically a single storage-side cache tier, not database-aware
Who manages patching/tuning
Largely automated by Autonomous Database
Manual, unless the customer builds equivalent automation
Trade-offs
Smart Scan only triggers on specific scan types (full table, fast full index, full bitmap index) — index range scans and other access paths don’t get the same offload benefit.
Oracle’s architecture and pricing pages make strong comparative claims (“dramatically better performance… than other platforms”) without publishing the benchmarks, hardware specs, or prices behind them — you need a direct quote to know what you’re actually paying.
Exadata’s value is specifically about offloading SQL processing to storage; it doesn’t replace good query design, and non-Exadata workloads (or queries that can’t use Smart Scan’s supported scan types) won’t see the same gains.
Autonomous Database’s automation is a trade of control for convenience — DBAs who want to hand-tune indexing or control exact patch windows have less to do, by design.
Who It’s a Good Fit For
Organizations already committed to Oracle Database, running large OLTP or analytics workloads where full scans are common, get the clearest benefit from Exadata’s storage-offload model — and Autonomous Database is the easiest way to consume that infrastructure without staffing a dedicated DBA team for patching and tuning. Regulated industries with data-residency requirements have a specific reason to look at Exadata Cloud@Customer, which puts the same hardware and automation inside their own data center.
Bottom Line
Exadata’s hardware-software co-design — storage servers that run database logic, RDMA networking, and workload-aware caching, all coordinated by Exadata System Software — is a genuinely different architecture from “database plus generic storage,” and it predates Oracle’s current AI push by well over a decade. Autonomous Database is the layer that turns that infrastructure into something you consume as a managed service instead of a rack you babysit. The mechanics are well documented; the performance superlatives and the actual bill are not, so budget a real conversation with Oracle before assuming either one.
FAQ
Is Exadata the same thing as Autonomous Database? No. Exadata is the underlying hardware-software system (database servers, storage servers, RDMA networking). Autonomous Database is a managed cloud service that runs on Exadata infrastructure and automates administration on top of it.
Does Smart Scan work with every query? No. Oracle’s documentation says it activates when the optimizer chooses a full table scan, fast full index scan, or full bitmap index scan — not every access path qualifies.
Can I run Autonomous Database outside Oracle Cloud? Yes. Exadata Cloud@Customer brings the same infrastructure into your own data center, and Oracle also offers Autonomous Database through its multicloud deals on AWS, Azure, and Google Cloud.
How much does Exadata cost? Oracle doesn’t publish a list price for Exadata hardware or for Dedicated/Cloud@Customer deployments on its architecture or product pages — those require a quote. Serverless Autonomous Database is pay-per-use with a published free tier and 30-day trial.
“Internal developer platform” (IDP) has become the label for a specific pattern: a self-service layer that lets application developers provision infrastructure, deploy services, and find ownership information without filing a ticket to the platform team — while that platform team still enforces guardrails behind the scenes. Three names come up constantly in 2026 conversations about building one: Backstage, the open-source framework Spotify built and donated to the CNCF; Port, a SaaS developer portal; and Humanitec, a platform orchestrator built around a code-based abstraction called Score. They solve overlapping but genuinely different problems, and conflating them is the most common mistake teams make when evaluating this space.
At a Glance
Platform
What it fundamentally is
Deployment model
Starting price
Best for
Backstage
Open-source framework for a software catalog, docs, and scaffolding templates, under CNCF governance
Self-hosted (Apache 2.0 license); managed options exist via Spotify Portal and third parties like Roadie
Free (open source); managed hosting is a separate paid product
Teams that want full control and are willing to run and maintain their own portal
Port
SaaS developer portal: software catalog, scorecards, and self-service actions, now positioned around an “Agentic SDLC” with AI/agent governance
Fully managed SaaS
Free tier (up to 15 seats); Basic from $30/seat/month (50-seat minimum)
Teams that want a catalog and self-service UI running in days without hosting Backstage themselves
Humanitec
Platform Orchestrator: a graph-based backend that turns a Score workload spec into provisioned infrastructure, applying guardrails to both humans and AI agents
Managed SaaS or self-hosted (Enterprise/Self-hosted tiers)
Teams tier from ~€1,999–2,199/month; Pro from ~€4,999–5,499/month; Enterprise and Self-hosted are custom-quoted
Platform teams that need the orchestration/provisioning engine, often paired with a separate catalog UI
The short version: Backstage and Port both compete to be the catalog and self-service front end developers actually click around in; Humanitec competes to be the orchestration engine underneath one. In practice, a lot of real deployments pair a catalog (Backstage or Port) with an orchestrator (Humanitec or an internal equivalent) rather than picking just one.
Why teams build an IDP in the first place
As organizations split a monolith into dozens or hundreds of services, two problems compound. First, nobody can find anything: which team owns this service, what’s its on-call rotation, what’s its current deploy status. Second, every developer who wants to spin up a new service or provision a database has to either learn the full depth of the cloud/Kubernetes/Terraform stack or file a ticket and wait. An internal developer platform is the standard answer: a thin, opinionated self-service layer in front of the messy infrastructure reality, so a developer can request “a new Postgres database for service X” without needing to know Terraform, and so anyone can find who owns what. Backstage’s own framing of this — “a centralized software catalog… for restoring order to your microservices and infrastructure while enabling your product teams to ship high-quality software quickly without compromising autonomy” — is close to the industry-standard pitch for the category as a whole.
Backstage: the open-source catalog framework
Backstage started at Spotify and was donated to the Cloud Native Computing Foundation, where it has graduated from CNCF Sandbox to CNCF Incubation status; it’s licensed under Apache 2.0. Its own documentation centers on four pieces:
Software Catalog — a centralized registry of microservices, libraries, data pipelines, websites, and ML models.
Software Templates — scaffolding that lets teams start new projects fast while standardizing on approved tooling.
TechDocs — documentation treated as code, authored alongside the services it describes.
Plugins — an open ecosystem that extends what the catalog can show and do.
Being open source and self-hosted is Backstage’s defining trade-off: you get full control over the data model and plugin ecosystem at zero license cost, but you take on the operational burden of running, upgrading, and plugin-maintaining a production web application. That operational cost is substantial enough that a managed-hosting market has grown up around it — Spotify’s own “Spotify Portal” product and third-party vendors like Roadie package Backstage as a hosted service specifically to remove that burden, which tells you something about how real the burden is.
Port: the SaaS developer portal
Port is a fully managed SaaS alternative to running Backstage yourself — historically positioned around a software catalog, scorecards for measuring service health, and self-service actions/workflows. Port’s current public positioning has shifted further toward what it calls the “Agentic SDLC”: governing AI coding agents alongside human developers, with components it names AI Builder, Context Lake, a Workflow Orchestrator, and an MCP hub, on top of the catalog fundamentals. Port’s pricing page lists four tiers: a Free tier (up to 15 seats, up to 10,000 entities, up to 500 automation runs), Basic at $30 per seat per month with a 50-seat minimum, Standard at $40 per seat per month for up to 200 seats, and a custom-quoted Enterprise tier with SSO/SAML and flexible deployment. Because it’s SaaS, Port trades the self-hosting burden Backstage carries for a recurring per-seat bill and less control over the underlying data model.
Humanitec: the platform orchestrator
Humanitec sits at a different layer of the stack. Its own site describes the Platform Orchestrator as a graph-based backend for an IDP, paired with a Portal front end (service catalog, scaffolding, self-service) and a code-based interface for developers called Score. Rather than being the catalog itself, Humanitec is the engine that turns a developer’s declared workload spec into actually-provisioned infrastructure, using pre-configured Resource Definitions that wrap existing Terraform or OpenTofu modules. Its current messaging leans heavily into governing AI agents’ infrastructure requests the same way it governs humans’: guardrail features include progressive rollouts, impact analysis, rollback, and drift detection, explicitly framed around avoiding agents that are “blocked,” “ungoverned,” or stuck in a human-approval bottleneck. Humanitec’s pricing is unusually transparent for this category: a Teams tier at roughly €1,999–2,199/month (5 users, 1 project), a Pro tier at roughly €4,999–5,499/month (50 users, RBAC, a sandbox org), and custom-quoted Enterprise and Self-hosted tiers for compliance-heavy deployments.
Side-by-side comparison
Dimension
Backstage
Port
Humanitec
Core abstraction
Software catalog + plugins
Software catalog + scorecards + workflows
Score workload spec + Resource Definitions
License/cost model
Open source (Apache 2.0), free to self-host
Per-seat SaaS subscription
Flat-rate monthly tiers, or custom Enterprise/Self-hosted
Who runs it
You (or a managed-hosting vendor like Roadie/Spotify Portal)
Port
Humanitec (SaaS) or you (Self-hosted tier)
Governance
CNCF Incubation project
Venture-backed private company
Venture-backed private company
Primary audience
Platform engineers comfortable building and maintaining their own portal
Platform teams that want a catalog UI without the hosting burden
Platform teams that need the provisioning/orchestration engine, often underneath a separate catalog
Trade-offs
Backstage pros: no license cost, full control, enormous plugin ecosystem, vendor-neutral under CNCF governance. Cons: you own the operational burden of running and upgrading it — real enough that a managed-hosting market exists specifically to sell you out of that burden.
Port pros: fast time-to-value as a managed SaaS, transparent published pricing, a usable free tier for small teams. Cons: per-seat cost scales with headcount, and the platform is now explicitly repositioning around AI-agent governance, which may or may not match what you actually need from a catalog tool.
Humanitec pros: solves the harder, less commoditized problem — actually provisioning infrastructure safely — with a documented guardrail model for both human and AI-driven requests. Cons: it’s explicitly not a catalog UI replacement (its own site says it integrates with, rather than replaces, existing developer portals), and its lowest published tier still starts in the thousands of euros per month.
Who should use which
Choose Backstage if you have (or can build) a platform team willing to run a production web application indefinitely, and you want zero license cost plus maximum control over the catalog’s data model and plugins — or choose a managed-Backstage vendor if you want Backstage’s plugin ecosystem without the hosting burden. Choose Port if you want a catalog and self-service UI live in days rather than months, your team is small enough to fit comfortably in its per-seat pricing, and you’re comfortable depending on a venture-backed vendor for a core piece of developer workflow. Choose Humanitec if your actual bottleneck isn’t “developers can’t find service docs” but “developers and now AI agents can’t safely provision infrastructure without a human in the loop for every request” — and treat it as a complement to, not a replacement for, whatever catalog UI you choose.
Bottom line
These three products aren’t really direct competitors once you look past the “internal developer platform” label they all wear: Backstage and Port compete for the catalog-and-self-service-UI layer (open source and self-hosted versus managed SaaS), while Humanitec competes for the orchestration-and-provisioning layer underneath either one. The practical architecture many platform teams land on is a catalog (Backstage or Port) in front of an orchestration engine (Humanitec or an internally built equivalent) — so the real decision isn’t “which one of these three,” it’s “which catalog, and do we need a dedicated orchestration layer at all, or can our existing CI/CD and infrastructure-as-code tooling handle provisioning directly.”
FAQ
Can I run Backstage and Humanitec together? Yes — this is a common pairing. Backstage (or Port) serves as the catalog and self-service UI developers interact with, while Humanitec’s Platform Orchestrator handles the actual provisioning behind the scenes; Humanitec’s own documentation describes connecting to existing developer portals rather than replacing them.
Is Backstage really free? The framework itself is free and open source under Apache 2.0. The cost you’re actually taking on is operational: hosting, upgrading, and maintaining plugins, which is substantial enough that managed-hosting products exist specifically to sell you out of it.
What’s Score, and is it specific to Humanitec? Score is a code-based workload specification format that Humanitec promotes as the developer-facing interface to its Platform Orchestrator — you declare what your workload needs, and Resource Definitions map that to actual infrastructure via existing Terraform/OpenTofu modules.
Do these platforms replace Terraform or Kubernetes? No. All three explicitly sit on top of existing infrastructure tooling rather than replacing it — Humanitec’s own site states it connects to, rather than replaces, CI/CD, infrastructure-as-code, and cloud accounts.
How does this relate to GitOps? They’re complementary layers, not competitors: GitOps tools like ArgoCD and Flux reconcile a cluster’s state to match what’s declared in Git, while an IDP is the layer developers interact with to request changes in the first place. Our GitOps explainer covers the reconciliation side of that pairing.
Most “best CRM” roundups default to the same three names and the same generic “small business” framing. But a two-person consultancy and a 40-person sales floor need very different things from a CRM, and HubSpot, Pipedrive, and Close actually split along that exact line. This guide is written specifically for freelancers, solo founders, and one-to-three-person sales teams deciding between them in 2026, with every price pulled directly from each vendor’s current pricing page.
At a Glance
Tool
Starting Price
Free Plan
Best For
Key Specs
HubSpot (Sales Hub)
$0, or $20/seat/month for Starter
Yes — up to 2 users, 1,000 contacts
Solo founders who want room to grow into marketing and service tools later
500+ integrations, AI reporting, meeting scheduler, limited automation on Free/Starter
Pipedrive
$14/seat/month (Lite, billed annually)
No — 14-day free trial only
Solo founders who think in visual pipelines and want fast setup
No — 14-day free trial with $5 in calling/enrichment credits
Freelancers and tiny teams who sell primarily by phone and email
Built-in calling and SMS, AI credits for email writing, workflows from Growth tier up
The Verdict
If you’re a true solo operator who never wants to touch a phone dialer, Pipedrive is the fastest path to a usable pipeline: it’s built around one visual view of deals, it’s cheap at the entry tier, and it doesn’t try to sell you marketing software you don’t need. If outbound calling and texting are core to how you sell — think independent recruiters, insurance agents, or solo sales reps — Close is worth the slightly higher entry price because calling, SMS, and a shared inbox are native instead of bolted on. If you expect to eventually hire a marketing person or need a CRM that can grow into a full HubSpot-powered funnel, the HubSpot free plan is the only one of the three that costs nothing indefinitely, though its paid tiers get expensive fast once you need real automation.
What These Tools Actually Do
All three are relationship-tracking databases with a sales pipeline layered on top, but they come from different starting points. HubSpot grew out of inbound marketing software and still thinks like a marketing platform — Sales Hub is one of five connected “Hubs” (Marketing, Service, Content, Operations), and its CRM is free specifically to get you into that ecosystem. Pipedrive was built by salespeople frustrated with spreadsheet pipelines, so the entire product is organized around one Kanban-style deal board with almost nothing else competing for attention. Close was built for inside-sales teams that live on the phone, so calling, SMS, and email sending are treated as first-class CRM activities rather than integrations you bolt on afterward.
For a one-person operation, this distinction matters more than feature-count comparisons suggest. A freelance consultant closing deals over email and the occasional call doesn’t need HubSpot’s marketing automation or Close’s power dialer — they need somewhere to track who they talked to and when to follow up. A solo recruiter or insurance agent making 40 calls a day, on the other hand, will feel Close’s built-in dialer and call recording almost immediately, while Pipedrive and HubSpot would require a separate calling tool.
Capped at 1 user and 10,000 leads; no workflow automation
Essentials
$35
$49
Unlimited contacts/leads, team inbox, built-in calling/SMS, still no workflows
Growth
$99
$109
Automated workflows, power dialer, bulk email
Scale
$139
$149
Role-based access, predictive dialer, live call coaching
Close charges calling and SMS usage on top of the plan price (roughly $0.02/minute for most outbound calls) and offers a 30-day money-back guarantee plus a 14-day trial with $5 of calling credit.
Pros and Cons
HubSpot — Pros: genuinely useful free tier, huge integration ecosystem, scales into full marketing/service software. Cons: paid tiers jump in price quickly, onboarding fees on Professional and Enterprise, more complexity than a solo user needs.
Pipedrive — Pros: fastest to set up, cleanest pipeline-first UI, predictable per-seat pricing. Cons: no free plan, lighter built-in calling than Close, fewer “all-in-one” features than HubSpot.
Close — Pros: calling, SMS, and email are native rather than add-ons, strong for high-call-volume solo sellers. Cons: no free plan, Solo tier caps you at one user with no automation, usage-based calling costs add up.
Who It’s a Good Fit For — and Who Should Look Elsewhere
Pick Pipedrive if you want the simplest possible visual pipeline and don’t need marketing tools or heavy calling. Pick Close if you spend most of your day on the phone or texting leads and want that built into the CRM instead of stitched together with a third-party dialer. Pick HubSpot’s free plan if budget is your main constraint right now but you expect to need marketing automation, landing pages, or a help desk down the line — just budget for a real price jump once you outgrow Starter. None of the three is a great fit for teams larger than about 10 reps that need territory management, complex approval chains, or deep customization; at that size it’s worth evaluating Salesforce or HubSpot’s higher Enterprise tiers directly. Freelancers who also need invoicing and billing, not just lead tracking, may want to pair whichever CRM they choose with a dedicated tool — see our guide to invoicing software for freelancers for that half of the stack.
Bottom Line
For a solo founder or tiny team, the honest default is Pipedrive for pure pipeline simplicity, Close if calling is central to your sales process, and HubSpot’s free tier if you need to spend nothing today but expect to grow into a full marketing stack. All three are credible choices — the mistake is picking based on brand recognition rather than how you actually sell.
FAQ
Does HubSpot’s free CRM expire or get worse over time? No — the Free tier has no time limit, but it’s capped at 2 users and 1,000 contacts, and carries HubSpot branding on outgoing emails and meeting links until you upgrade.
Can I use Pipedrive or Close with just one user? Yes. Pipedrive’s Lite tier has no seat minimum, and Close’s Solo tier is explicitly capped at one user, making both viable for true solo operators.
Which one has the best built-in calling? Close, by a clear margin — calling, SMS, and call recording are core features starting on Essentials, while Pipedrive and HubSpot rely more on integrations or add-on minutes for serious calling volume.
Is Zoho CRM worth comparing too? Zoho CRM is a reasonable fourth option, especially for its free tier covering up to 3 users, but we focused this comparison on the three tools that differ most sharply in approach — all-in-one (HubSpot), pipeline-first (Pipedrive), and calling-first (Close).
Do any of these charge extra for AI features? Close bundles a monthly AI-credit allowance into every paid tier. HubSpot includes “HubSpot Credits” for AI usage starting on Starter. Pipedrive’s AI reporting is included in all tiers, including Lite.
Every system that sits between an application and a slower backing store — a database, a disk, another service — eventually has to answer the same question: when does the cache get filled, and when does it get updated? The answer isn’t one universal “best” pattern. It’s a small set of named strategies, each with a documented trade-off between latency, staleness, and durability risk. This explainer walks through cache-aside, write-through, and write-behind (write-back) using the patterns as AWS and Redis actually document them, so you can match the pattern to the workload instead of guessing.
At a Glance
Pattern
Who writes to the cache
Write latency
Staleness risk
Best for
Cache-aside (lazy loading)
The application, only on a cache miss
Unaffected — writes go straight to the database
Cache can go stale until TTL expiry or explicit invalidation
Read-heavy data that’s read far more often than it’s written (user profiles, product catalogs)
Write-through
The application, synchronously on every write, alongside the database
Higher — every write is two round trips instead of one
None, as long as both writes succeed
Data you know will be read right after it’s written, where staleness is unacceptable
Write-behind (write-back)
The application writes only to the cache; a background process syncs to the database later
Lowest — a write finishes once the cache acknowledges it
The database briefly lags the cache (eventual consistency)
The short version: AWS’s own ElastiCache documentation frames this as a combination problem, not a single choice — “start with cache-aside, add write-through for specific hot keys, and layer a TTL on everything as a safety net.” Write-behind is the odd one out: it trades durability for write throughput, and neither AWS’s nor Redis’s own documentation recommends it for data you can’t afford to lose.
Cache-aside (lazy loading)
Cache-aside — AWS calls it “lazy loading” in the ElastiCache documentation — loads data into the cache only when an application actually asks for it. The application, not the cache, owns the logic:
function get_customer(customer_id):
record = cache.get(customer_id)
if record is null: // cache miss
record = db.query("SELECT * FROM customers WHERE id = ?", customer_id)
cache.set(customer_id, record)
return record // cache hit or freshly loaded
On a hit, the application returns the cached value directly. On a miss, it takes three trips — cache read, database query, cache write — and returns the result. AWS documents the upside plainly: only requested data ever enters the cache, so memory isn’t wasted on records nobody reads, and if a cache node fails and comes back empty, the application degrades to more cache misses rather than breaking outright. The documented downside is the mirror image: that three-trip miss penalty adds latency on cold keys, and because nothing updates the cache when the underlying database changes, cached values can silently go stale. AWS’s own fix for the staleness problem is to pair cache-aside with a TTL or with write-through for the specific keys that need to stay current.
Write-through
Write-through flips the order: the cache is updated every time the database is updated, as part of the same write operation.
function save_customer(customer_id, values):
db.execute("UPDATE customers SET ... WHERE id = ?", customer_id, values)
cache.set(customer_id, values) // write to cache only after the DB write succeeds
return success
Redis’s own engineering documentation recommends writing to the database first and the cache second, specifically so the system of record is never behind the cache. Because the cache is updated on every write, data is never stale — there’s no window where a stale value sits in cache waiting to be read. The trade-off is latency: a write now takes at least as long as both operations combined, though AWS notes that end users are typically more tolerant of a slower write than a slower read. Redis’s documentation also flags a consistency hazard worth planning for explicitly: if the database write succeeds but the cache write fails, log the error and don’t fail the whole operation — a later read will simply fall through to the database and get a fresh value. There’s a second documented cost too: write-through fills the cache with every write, including data that’s rarely or never read afterward, which wastes memory unless it’s combined with a TTL.
Write-behind (write-back)
Write-behind looks similar to write-through at the API level but makes a fundamentally different durability trade. The application writes only to the cache, which acknowledges immediately; a background process later drains changed keys to the database, often batching or coalescing repeated updates into one write.
function increment_view_count(post_id):
cache.incrby("views:" + post_id, 1) // returns immediately, ~1ms
mark_dirty("views:" + post_id) // background worker syncs this later
// background worker, running continuously:
function sync_dirty_keys():
for key in dirty_keys():
db.upsert(key, cache.get(key))
clear_dirty(key)
The documented upside is real: writes finish in roughly a millisecond because only the cache is on the critical path, the database is shielded from write bursts, and repeated updates to the same key — think view counters — can collapse into a single database write instead of one per increment. The documented downside is just as real: until the sync runs, the cache is the system of record, and if it fails before syncing, those writes are gone. Redis’s own write-behind documentation is explicit about mitigations (enabling AOF persistence with `everysec` bounds the loss window to about a second) but equally explicit that none of them match the durability of a synchronous database write. That’s why this pattern is documented as a fit for counters, metrics, session touches, and analytics ingestion — and explicitly not recommended for financial transactions, orders, credentials, or anything with a compliance requirement around data loss.
Side-by-side comparison
Concern
Cache-aside
Write-through
Write-behind
Stale data
Possible between writes and the next read-triggered refresh
Avoided, by construction
Expected — database briefly lags cache
Cache miss cost
Full penalty on every miss (cache + DB + cache write)
Rare, since reads of recently-written data hit cache
Rare for written data; same miss behavior as cache-aside for never-written keys
Write latency
Unaffected — writes bypass the cache entirely
Higher: two synchronous writes per operation
Lowest: one asynchronous write (cache only)
Durability on failure
Database is always authoritative
Database is always authoritative
Unsynced writes can be lost if the cache fails
Memory efficiency
High — only requested data is cached
Lower — every write fills the cache, including rarely-read data
Depends on sync frequency and coalescing
Trade-offs: pros and cons
Cache-aside pros: simplest to reason about, memory-efficient, resilient to empty/failed cache nodes. Cons: every cold key pays a three-trip miss penalty, and nothing keeps the cache fresh on its own.
Write-through pros: cache is always current for recently written keys, which removes a whole class of stale-read bugs. Cons: slower writes, and a failed or replaced cache node still starts out missing data for keys nobody has re-written yet.
Write-behind pros: by far the fastest writes, and it absorbs write bursts the database couldn’t handle directly. Cons: a real, documented durability gap — the cache is the system of record until the sync runs, and that window is where data gets lost if something crashes.
Who should use which
Both AWS and Redis’s own documentation converge on the same recommendation: use cache-aside as your default for read-heavy data (user profiles, product listings, configuration), add a TTL to every key as a safety net against forgotten invalidations, and layer write-through on top only for the specific keys you know will be read again almost immediately after being written — leaderboards, session data, recently viewed items. Reach for write-behind only for data where losing a few recent updates during an outage is genuinely acceptable: view counters, rate-limit counters, telemetry, and other aggregate or non-critical state. If you’re caching anything with a compliance or correctness requirement — money, orders, credentials — write-through or a transactional write pattern is the documented choice, not write-behind.
Bottom line
There’s no single “best” caching strategy because the three patterns optimize for different things: cache-aside optimizes for simplicity and memory, write-through optimizes for consistency, and write-behind optimizes for write throughput at the cost of a durability window. Most production systems — and this is explicit in AWS’s own caching best-practices documentation — end up combining all three: cache-aside as the default, write-through for predictable hot data, TTLs everywhere, and write-behind reserved for the narrow set of high-volume, loss-tolerant writes where it actually pays off. The mistake to avoid is picking one pattern and applying it uniformly to every key in your cache.
FAQ
Can I combine cache-aside and write-through? Yes — this is the documented AWS recommendation. Use cache-aside as the base strategy for most data, and apply write-through selectively to keys you know will be read immediately after being written.
What’s the difference between write-behind and write-back? They’re the same pattern under two different names used across the industry — Redis’s own documentation uses “write-behind” and “write-back” interchangeably for the pattern where the application writes only to the cache and a background process syncs to the database later.
Does a TTL replace the need for write-through? No. AWS’s documentation is explicit that a TTL only bounds how long stale data can persist — it doesn’t guarantee freshness between the time data changes and the time the TTL expires. Write-through removes staleness immediately; a TTL just limits its blast radius.
What happens if a write-through cache write fails but the database write succeeded? Redis’s documentation recommends logging the error and letting the operation succeed anyway, since the database (the source of truth) already has the correct value — the next read will fall through to the database and refresh the cache.
Is Memcached or Redis documentation the better reference for these patterns? Both document the same core patterns, but Redis’s own “fundamental” pattern pages and AWS’s ElastiCache documentation (which covers both Redis and Memcached engines) are the clearest primary sources, and that’s what this piece draws from directly.
Every distributed database, coordination service, and container orchestrator eventually runs into the same problem: several machines need to agree on one value — who the leader is, what the next log entry says, whether a transaction committed — even though machines crash, networks partition, and messages get lost or delayed. The algorithms that solve this are called consensus algorithms, and two names dominate the field: Paxos, the 1998 algorithm that proved it was possible, and Raft, the 2014 algorithm built specifically to be easier to understand and implement. This explainer walks through how each one actually works, where they differ, and which real systems — etcd, Kubernetes, Consul, CockroachDB — rely on which.
At a Glance
Algorithm
Core mechanism
Leader model
Understandability
Used by
Paxos (1998/2001)
Two-phase prepare/accept voting among proposers, acceptors, and learners
No built-in leader; any proposer can compete, which Lamport’s own paper flags as a liveness risk
Formally proven safe, but notoriously hard to turn into working code
Google Chubby/Spanner, Apache ZooKeeper (ZAB, a Paxos variant), Microsoft Azure Storage
Raft (2014)
Strong leader election plus replicated, ordered log entries
Exactly one leader at a time per term, elected by majority vote
Explicitly designed and user-tested for understandability
etcd (and therefore Kubernetes), HashiCorp Consul and Nomad, CockroachDB, InfluxDB, TiKV
The short version: both algorithms give you the same guarantee — a cluster of replicas agrees on a sequence of values and keeps working as long as a majority of nodes are up — but Raft gets there with one clearly defined leader and an explicit log, which is why almost every consensus library built since 2014 is a Raft implementation rather than a raw Paxos one.
The problem both algorithms solve
Consensus lets a group of servers agree on values even when some of them fail, and once a decision is made, it is final. The standard way this gets used in real systems is a replicated state machine: each server keeps an identical, ordered log of commands, and consensus guarantees every server applies the same command at the same log position. That one property — “if one replica applies command X as its Nth entry, no other replica will ever apply a different command as its Nth entry” — is what every database replica, every etcd key, and every Kubernetes cluster’s control-plane state is built on top of.
The hard constraint underneath both algorithms is the FLP impossibility result (Fischer, Lynch, and Paterson, 1985): no algorithm can guarantee both safety and termination in a fully asynchronous network where messages can be delayed arbitrarily. Paxos and Raft both resolve this the same way — they guarantee safety unconditionally and guarantee progress only when a majority of nodes can communicate, using timeouts and randomization to make progress likely in practice.
How Paxos works
Leslie Lamport’s “Paxos Made Simple” (2001) defines three roles — a process can hold more than one at once:
Proposers propose values.
Acceptors vote on proposals; a value is chosen once a majority of acceptors accept it.
Learners find out which value was chosen.
Agreement happens in two phases. In Phase 1 (prepare), a proposer picks a unique proposal number n and asks a majority of acceptors to promise not to accept anything numbered lower than n; each acceptor also reports the highest-numbered proposal it has already accepted, if any. In Phase 2 (accept), if a majority responds, the proposer sends an accept request for n — using whatever value the acceptors already reported, or its own value if none was reported. An acceptor accepts unless it already promised a higher number in the meantime.
The safety argument is elegant: once a value is chosen, every higher-numbered proposal is forced to carry that same value, because any two majorities of acceptors must overlap by at least one node. That overlap is what prevents two different values from ever being chosen. This holds no matter how messages are delayed, duplicated, or lost.
What Paxos does not give you is a clean path to liveness or to a replicated log. Lamport’s paper is explicit that two competing proposers can keep preempting each other’s proposals indefinitely — so real systems need a distinguished proposer (a leader), and electing one safely requires the same kind of timeout logic Raft makes central. Running basic (single-decree) Paxos once per log slot also leaves gaps that need no-op filling, and reconfiguring the acceptor set mid-flight is notoriously fiddly — which is exactly the gap that “Multi-Paxos” variants, and eventually Raft, were built to close.
How Raft works
Diego Ongaro and John Ousterhout designed Raft explicitly to be easier to understand than Paxos while matching it in fault tolerance and performance; their paper, “In Search of an Understandable Consensus Algorithm,” won the Best Paper Award at USENIX ATC 2014. Raft achieves understandability by splitting consensus into three largely independent subproblems: leader election, log replication, and safety.
Leader election. Every node is a follower, candidate, or leader. A follower that hears nothing from a leader before its randomized election timeout expires becomes a candidate, increments a term number, and requests votes from its peers:
on election timeout (follower):
state ← candidate
currentTerm ← currentTerm + 1
votedFor ← self
send RequestVote(term=currentTerm, lastLogIndex, lastLogTerm) to all peers
on receiving RequestVote(term, lastLogIndex, lastLogTerm):
if term < currentTerm: reject
if votedFor is null (or already = candidate) AND
candidate's log is at least as up-to-date as mine:
votedFor ← candidate
grant vote
else:
reject
on candidate receiving majority of votes:
state ← leader
send empty AppendEntries (heartbeat) to all peers
Randomizing each node’s election timeout is what keeps elections from splitting forever: it makes it unlikely two nodes become candidates at exactly the same moment, so one usually gathers a majority before a competitor even starts.
Log replication. Once elected, a leader is the only node that accepts client commands. It appends each command to its own log and replicates it to followers via AppendEntries RPCs; once a majority of nodes have stored an entry, the leader marks it committed and applies it to its state machine, then followers commit it on their next heartbeat.
Safety. Raft’s election rule — a candidate only wins a vote if its log is at least as up-to-date as the voter’s — guarantees that a new leader always already holds every entry that has ever been committed. That single invariant (the “Leader Completeness” property in the paper) is what lets Raft avoid the gap-filling and reconfiguration headaches that complicate Multi-Paxos; membership changes go through the replicated log itself, using an overlapping joint-consensus step so the cluster is never split across two incompatible configurations at once.
Raft vs Paxos, side by side
Dimension
Paxos
Raft
Leadership
Not required by the base algorithm; added informally in practice
Built into the algorithm as “strong leader”
Log handling
Not addressed directly; Multi-Paxos variants bolt it on
First-class: the log is the mechanism
Membership changes
Handled outside the core algorithm, inconsistently across implementations
Specified via joint consensus in the paper itself
Formal verification
Proven safe by Lamport’s original invariant argument
Proven safe in Ongaro’s PhD dissertation, including a TLA+ specification
Implementation ecosystem
Fewer general-purpose open libraries; often reimplemented per system (ZAB, Spanner’s internal Paxos)
Many mature libraries: hashicorp/raft, etcd’s raft, openraft (Rust)
Where each one actually runs
etcd — and by extension every Kubernetes control plane — uses Raft (via the go.etcd.io/raft library) to replicate its key-value store across cluster members, which is why a Kubernetes control plane needs an odd number of etcd nodes and tolerates the loss of a minority. HashiCorp Consul documents the same majority-quorum model directly: with 3 server nodes quorum is 2 and the cluster tolerates 1 failure, and with 5 servers quorum is 3 and it tolerates 2 — losing quorum blocks new writes until it’s manually recovered. CockroachDB runs a separate Raft group per data range, with one replica acting as both Raft leader and “leaseholder” to avoid an extra network hop on writes; a range with 3 replicas survives 1 node failure, and 5 replicas survive 2. On the Paxos side, Google’s internal systems (Chubby, and Spanner’s data-replication layer) and Apache ZooKeeper’s ZAB protocol are the best-known production uses — ZooKeeper in particular predates Raft and is often the thing a new project replaces with a Raft-based store.
Trade-offs
Pros
Cons
Paxos
Minimal, formally proven core; flexible enough that systems like Spanner and ZooKeeper have built very different production protocols on top of it
The base algorithm doesn’t specify leader election, log replication, or reconfiguration, so every real deployment ends up inventing its own variant — which is part of why implementations have historically diverged and been hard to get right
Raft
Leader election, log replication, and membership changes are all specified in one paper with a reference implementation and formal proof; genuinely easier to reason about and debug
A single strong leader means all writes funnel through one node per term, which is a throughput ceiling some Paxos-derived systems (notably Google Spanner, which spans data centers) are built to avoid
Who should use which
Reach for an existing Raft library (hashicorp/raft, etcd’s raft, openraft) if you’re building a new coordination service, a metadata store, or anything that needs a replicated log with a clear leader — this is the default choice for virtually every new distributed systems project in 2026, precisely because the ecosystem and tooling around Raft is so much more mature. Study Paxos if you’re working inside or extending a system that already uses a Paxos-family protocol (ZooKeeper’s ZAB, Spanner-style globally distributed databases), or if your workload genuinely needs multiple concurrent proposers rather than a single serializing leader. For nearly everyone building something new, Raft’s explicit design for understandability is also a maintainability advantage: the next engineer who has to debug a split-brain incident at 3 a.m. will have an easier time with Raft’s log-and-leader model than with a from-scratch Paxos variant.
Bottom line
Paxos proved that distributed consensus was possible and remains the formal foundation the field builds on; Raft took the same guarantees and organized them into a leader-election-plus-replicated-log design that’s dramatically easier to implement correctly, which is exactly why it now underpins etcd, Kubernetes, Consul, Nomad, and CockroachDB. If you’re picking a consensus approach for a new system today, Raft’s library ecosystem and its explicit specification for leader election, log replication, and cluster membership changes make it the practical default — reserve Paxos-family protocols for the specific cases where you’re extending a system (or a globally distributed, multi-leader architecture) that already depends on one.
FAQ
Is Raft faster than Paxos? Neither algorithm’s authors claim one is categorically faster — the Raft paper’s goal was understandability “while matching Paxos in fault-tolerance and performance.” Real-world throughput depends far more on implementation, batching, and network topology than on the base algorithm, so don’t treat either name as a stand-in for a specific benchmark number.
Can a Raft or Paxos cluster survive any number of failures? No — both require a majority (quorum) of nodes to be reachable to make progress. A 5-node cluster tolerates 2 simultaneous failures; a 3-node cluster tolerates 1. Lose quorum and the cluster stops accepting new writes, by design, rather than risk an inconsistent result.
What is ZAB, and is it Paxos? ZooKeeper’s Atomic Broadcast (ZAB) protocol is a Paxos-family protocol purpose-built for ZooKeeper’s primary-backup replication model; it’s not identical to Lamport’s Paxos but shares its majority-quorum voting foundation.
Does Raft handle network partitions safely? Yes. If a partition splits a cluster, only the side with a majority of nodes can elect a leader and commit new entries; the minority side can’t form a quorum, so it simply stops accepting writes until the partition heals — there’s no scenario where both sides commit conflicting entries.
How does this relate to CRDTs? Consensus algorithms and CRDTs solve the same underlying problem — keeping replicas in agreement — with opposite philosophies: Raft/Paxos force agreement through a coordinated vote before data is considered committed, while CRDTs let replicas accept writes independently and merge afterward. Our CRDTs explainer covers the merge-without-coordination side of that trade-off.
Kubernetes made declarative infrastructure the default. GitOps extends that idea to deployment itself: instead of a CI system pushing changes into a cluster, an in-cluster agent continuously pulls the desired state from Git and reconciles it. Three open-source tools dominate this space heading into 2026 — ArgoCD, Flux CD, and Spinnaker. All three are governed by neutral foundations rather than sold as commercial products, but they take noticeably different approaches to the problem. This guide compares their governance, architecture, and ideal use cases.
At a Glance
Tool
Governance / Maintainer
Architecture Style
Best For
ArgoCD
CNCF graduated project (originally Argoproj/Intuit); commercial support from vendors like Akuity
Pull-based GitOps reconciliation; Kubernetes-native controller with a dedicated UI
Teams wanting a visual, Kubernetes-only GitOps tool with strong multi-cluster support
Flux CD (v2)
CNCF graduated project; GitOps Toolkit originated at Weaveworks (which shut down in 2024)
Pull-based GitOps reconciliation via modular Kubernetes controllers (source, kustomize, helm)
Teams wanting a lightweight, composable GitOps engine with progressive delivery via Flagger
Spinnaker
Continuous Delivery Foundation (CDF, under the Linux Foundation); originated at Netflix with early Google collaboration
Pipeline-driven continuous delivery platform; not GitOps-native, though it can be Git-triggered
Organizations deploying across multiple clouds and compute targets (VMs, serverless, Kubernetes) needing a full CD pipeline UI
Short Verdict
For Kubernetes-only teams that want pull-based GitOps with a strong dashboard, ArgoCD is the easiest starting point. For teams that prefer a lighter, composable set of controllers and care about progressive delivery, Flux CD paired with Flagger is the better fit. For estates spanning multiple clouds and compute platforms that need a general-purpose CD pipeline tool rather than a strict GitOps reconciler, Spinnaker is worth a look, though it has a heavier footprint and a less GitOps-centric model.
What GitOps Actually Means
GitOps treats a Git repository as the single source of truth for a system’s desired state, with an automated process continuously working to make the live system match it. Two properties separate it from traditional CI/CD:
Declarative state in Git. Manifests, Helm charts, and Kustomize overlays live in version control, not in a pipeline script.
Pull-based reconciliation. An agent inside the cluster watches Git and pulls changes in, continuously comparing live state to declared state and correcting drift — the opposite of traditional CI/CD, where a pipeline runner (e.g., Jenkins or a GitHub Actions job) authenticates outward and pushes changes into the target environment.
Argo CD’s documentation describes the tool as “a declarative, GitOps continuous delivery tool for Kubernetes” that treats Git as the source of truth and flags drifted applications as OutOfSync. Flux’s documentation describes a similar loop: controllers run checks on an interval, and “if you make any changes to the cluster using kubectl edit/patch/delete, they will be promptly reverted” — a direct illustration of pull-based self-correction. Spinnaker, by contrast, calls itself an “open-source, multi-cloud continuous delivery platform” built around pipelines and approvals rather than continuous drift correction from a Git source of truth.
ArgoCD: Kubernetes-Native GitOps With a Dashboard
ArgoCD runs as controllers inside the cluster it manages, watching Git repositories containing YAML, Kustomize, Helm, or Jsonnet, and continuously diffing live state against what’s declared in Git. When drift appears, it can flag it for review or auto-sync the correction. Its standout feature is the web UI: a real-time view of every Application’s sync and health status, resource trees, and diffs, which makes GitOps visible to the whole organization rather than invisible background automation. ArgoCD also ships ApplicationSets, a controller that generates many Application resources from templates — driven by generators such as Git directories or cluster lists — the standard way teams manage GitOps at fleet scale. ArgoCD graduated from CNCF incubation in December 2022, the status the CNCF reserves for projects it considers “stable, widely adopted, and production ready.” Vendors including Akuity (founded by original Argo maintainers) now offer managed or enterprise versions, but the core project remains free and open source.
Flux CD: A Modular GitOps Toolkit
Flux CD v2 is assembled from a set of composable controllers collectively called the GitOps Toolkit — “a collection of specialized tools, Flux Controllers, composable APIs, and reusable Go packages,” in Flux’s own words — rather than one monolithic controller plus a UI. Separate controllers handle sources (GitRepository, OCIRepository, HelmRepository, Bucket objects), Kustomize-based reconciliation, and Helm release reconciliation, each its own Kubernetes custom resource. That modularity makes Flux easy to compose into existing automation, though it generally lacks ArgoCD’s built-in dashboard out of the box.
Flux’s other defining feature is its pairing with Flagger, “a specialised controller that implements various progressive delivery techniques” such as canary releases, blue/green deployments, and A/B testing, automating traffic shifting and rollback based on metrics. That makes Flux/Flagger a strong option for teams wanting progressive rollout logic built into the reconciliation loop itself. Flux graduated from CNCF incubation in late 2022, about a week before ArgoCD did the same. The GitOps Toolkit originated at Weaveworks, which shut down its commercial operations in 2024, though the Flux project and its CNCF governance continue independently of that.
Spinnaker: Multi-Cloud Delivery Pipelines, Not Strict GitOps
Spinnaker predates the GitOps pattern as commonly defined today. It was created at Netflix, with early collaboration from Google, as a general continuous delivery platform spanning many compute targets — not just Kubernetes, but also AWS EC2 and ECS, Azure, Google Compute Engine and Cloud Run, Oracle Cloud, and Cloud Foundry. Its documentation calls it an “open-source, multi-cloud continuous delivery platform,” with pipelines built around triggers (Jenkins, GitHub, Pub/Sub, Artifactory, webhooks), deployment strategies, and manual judgment/approval stages running through a dedicated pipeline UI.
That breadth is Spinnaker’s main differentiator: it isn’t Kubernetes-only, and it doesn’t work primarily as a pull-based reconciler watching one source of truth. A pipeline typically runs in response to a trigger and pushes the deployment through defined stages — closer to traditional CI/CD orchestration than continuous drift correction. Teams can trigger Spinnaker pipelines from Git events, but reconciling live state against a Git-declared desired state isn’t the core mechanism the way it is in ArgoCD or Flux. Spinnaker is governed today by the Continuous Delivery Foundation (CDF), a Linux Foundation project that lists it among current hosted projects, describing it as providing “multi-cloud continuous delivery for the enterprise.”
ArgoCD cons: Kubernetes-only; UI and controller add operational overhead versus Flux; multi-cluster setups need deliberate architecture choices.
Flux CD pros: lightweight, modular controllers that compose into existing tooling; strong progressive-delivery story via Flagger; CNCF-graduated; API/CLI-first.
Flux CD cons: no built-in dashboard as rich as ArgoCD’s; multi-controller design has a steeper learning curve; Kubernetes-only.
Spinnaker pros: genuinely multi-cloud and multi-platform; mature pipeline UI with approval stages and canary analysis; broad provider integrations.
Spinnaker cons: not GitOps in the pull-based reconciliation sense; heavier installation and operational footprint; smaller CDF contributor ecosystem relative to CNCF’s Argo/Flux community.
Who It’s a Good Fit For / Who Should Look Elsewhere
ArgoCD fits platform teams running one or many Kubernetes clusters who want a visible, dashboard-driven workflow and are comfortable staying Kubernetes-only.
Flux CD fits teams wanting a minimal, composable GitOps engine that integrates into existing automation, especially with progressive delivery via Flagger.
Spinnaker fits organizations deploying across multiple clouds and compute types that need a general-purpose CD pipeline tool with approval gates, not a pure GitOps reconciler.
Teams deploying only outside Kubernetes should look elsewhere for ArgoCD or Flux, since both are Kubernetes-native.
Teams wanting strict, continuous Git-to-cluster drift correction as the core model will likely find Spinnaker’s pipeline-and-trigger approach a mismatch, even though it can be adapted to Git-triggered workflows.
Bottom Line
All three tools are free and open source, governed by neutral foundations rather than sold as commercial products, though support and managed offerings exist around each (notably Akuity for ArgoCD). Start with ArgoCD for classic Kubernetes GitOps with a strong UI. Choose Flux CD paired with Flagger for a modular toolkit with built-in progressive delivery. Reach for Spinnaker when deployment targets go beyond Kubernetes and you need a full pipeline orchestration platform — keeping in mind it isn’t a GitOps tool in the strict pull-based sense that ArgoCD and Flux are.
FAQ
What is GitOps, and how does it differ from traditional CI/CD?
GitOps uses a Git repository as the single source of truth, with an agent inside the target environment continuously pulling and reconciling state. Traditional CI/CD typically works the opposite way: a pipeline runner outside the environment pushes changes in, usually as a one-time action per deployment rather than a continuous loop.
Is Spinnaker a GitOps tool?
Not in the strict sense that ArgoCD and Flux are. Spinnaker is a general continuous delivery pipeline platform; it can be triggered by Git events, but its core mechanism is pipeline execution rather than continuous pull-based reconciliation against a Git source of truth.
Are ArgoCD, Flux CD, and Spinnaker free to use?
Yes. All three are open-source projects governed by neutral foundations — ArgoCD and Flux by the CNCF, Spinnaker by the CD Foundation — rather than sold as paid products. Some vendors offer managed hosting or enterprise support on top, Akuity being a notable example for ArgoCD, but the underlying projects are free.
Can I use these tools together?
Technically yes, though most teams pick one GitOps engine per cluster to avoid conflicting reconciliation loops. Some organizations pair Spinnaker’s pipeline orchestration (for build/test/promotion or non-Kubernetes targets) with ArgoCD or Flux handling Kubernetes-specific GitOps reconciliation.
Which tool has the largest community?
ArgoCD and Flux are both CNCF graduated projects — a status reserved for projects considered stable, widely adopted, and production-ready — reflecting substantial community scale for both. There is no verified, apples-to-apples contributor or adoption count for Spinnaker available to compare directly, so no specific numeric comparison is made here.
Writing and maintaining Selenium scripts by hand is one of the most-cited drains on QA team velocity: a single CSS selector change can break dozens of tests overnight. A newer generation of AI-powered test automation platforms promises to fix that by generating test cases from plain-language descriptions and “self-healing” locators when the underlying app changes. This roundup compares three of the best-known names in that category for 2026: Testim (now Tricentis Testim), mabl, and ACCELQ. It focuses specifically on AI-driven functional test generation and self-healing automation — not visual regression testing, which this site covers separately in its comparison of Applitools, Percy, and Chromatic.
At a Glance
Tool
Pricing model
Free trial
Best for
Tricentis Testim
Custom quote (Essentials/Pro/Mobile/Salesforce plans); no public list pricing; free “Community” tier after trial ends
Yes (self-serve “Try Testim for Free” signup; converts to limited Community plan)
Teams replacing hand-written Selenium/web scripts, including Salesforce-heavy orgs
Low-code teams and “citizen testers” who want one tool across web, mobile, and API
ACCELQ
Custom quote by tier (Professional/Enterprise per module); free-for-life “Automate Manual” plan for individuals; Gen AI “Autopilot” features are a separate add-on subscription
Yes for Teams/Professional tiers (length not published)
Enterprises wanting unified test management plus automation across web, API, mobile, and packaged apps like Salesforce/SAP/Oracle
Short Verdict
All three tools generate or heal tests with AI rather than relying on brittle hand-coded locators, but they target different buyers. Tricentis Testim is the closest match for a team migrating off raw Selenium scripts and wants AI-assisted authoring plus strong self-healing. mabl is the most approachable for low-code/citizen-tester organizations that want a single platform spanning web, mobile, and API without a steep learning curve. ACCELQ is built for enterprises that want test case generation and self-healing bundled with full test management, requirements traceability, and packaged-app support (Salesforce, SAP, Oracle) in one platform — though its newest Gen AI “Autopilot” capabilities are sold as an add-on, not included by default.
What AI-Powered Test Generation and Self-Healing Actually Mean
“AI-powered test case generation” in this category generally covers two related but distinct capabilities. The first is natural-language or AI-assisted test authoring: instead of a tester writing code or manually recording every click, they describe a workflow in plain English (or point the tool at existing requirements), and the platform generates the test steps, data combinations, and assertions. The second is self-healing test maintenance: when a UI changes — an element’s ID, class, or position shifts — the platform uses a combination of machine learning and metadata (not just a single brittle selector) to recognize the element and keep the test running, rather than failing and requiring a manual fix. Vendors differ in how much of the test case itself the AI originates versus how much it merely keeps already-authored tests alive, which is a meaningful distinction for teams evaluating “AI test generation” claims.
Tricentis Testim: Status, AI Features, and Platform Coverage
Testim was acquired by Tricentis in February 2022, and the product is now marketed as Tricentis Testim, sitting alongside Tricentis’s other continuous-testing products rather than operating as a standalone brand. It is sold in three flavors — Testim Web, Testim Mobile, and Testim Salesforce — each with its own AI tooling.
On the AI side, Testim’s core differentiator is still self-healing locators: the product combines AI, machine learning, and page metadata so a test can recognize an element even after the underlying code changes, reducing the constant locator-maintenance burden that plagues raw Selenium suites. Tricentis has layered newer Gen AI features on top, including Agentic Test Automation (describe what needs testing and an agent builds the test — currently emphasized for Salesforce), Testim Copilot (generates custom JavaScript test steps from a text description for more advanced scripting needs), and AI-assisted root cause analysis that correlates screenshots, console logs, and network logs when a test fails.
Platform coverage includes web (run locally, on Testim’s own grid, or any compatible Selenium grid), mobile (native, hybrid, React Native, and Flutter apps via a cloud-based Virtual Mobile Grid), Salesforce-specific testing with locators tuned for dynamic Lightning components, and API testing (documented under Tricentis’s advanced-editing API testing features).
mabl: AI Features and Platform Coverage
mabl positions itself around an “agentic” testing workflow. Its GenAI test creation lets users generate tests from natural-language prompts or by pointing the tool at JIRA requirements, which mabl says can make initial test creation roughly 10x faster than manual authoring. Its self-healing capability — branded “adaptive auto-healing” — uses a mix of traditional ML models and generative AI to keep tests running as an app changes, and mabl publishes a maintenance-reduction claim of 85% on its own site. Notably, auto-healed test changes are routed to an approval screen rather than silently applied, which gives QA teams a review checkpoint.
Platform coverage spans web (including cross-browser testing), mobile (iOS and Android), and API testing via Postman collection imports, plus specific support for validating dynamic AI-application outputs (e.g., chatbot responses). mabl also emphasizes automatic failure triage and “unlimited execution agents” for parallel runs.
ACCELQ: AI Features and Platform Coverage
ACCELQ is positioned less as a point testing tool and more as a unified test management-plus-automation platform, which is its core differentiator versus Testim and mabl. Its Gen AI layer, branded Autopilot (introduced in Release 7.0), bundles several pieces: natural-language automation authoring (write automation logic in plain English, with the AI referencing the application and auto-reconciling some errors); an AI Test Case Generator that analyzes business logic, detects parameters, and explores data combinations to produce populated test cases automatically; an AI Designer that organizes test logic into reusable, modular components; and Autonomous Element Healing, ACCELQ’s self-healing mechanism for web applications, which detects UI changes and adjusts element interactions automatically. According to ACCELQ’s own support documentation, these Autopilot Gen AI features require a separate subscription beyond the base automation platform — an important detail for budget planning, since marketing pages don’t always flag this.
ACCELQ’s platform coverage is broad by design: web, desktop, and cloud ERP apps; mobile (iOS/Android, cloud-native, zero-setup); API protocols including REST, SOAP, Kafka, message queues, microservices, and SSH; and packaged enterprise applications such as Salesforce, Oracle, SAP, and ServiceNow. It also includes manual test case management and planning tools that Testim and mabl don’t offer natively.
Pricing Breakdown
None of the three vendors publish list prices for their core plans — a meaningful buying consideration on its own, since it means every deal starts with a sales call.
Tricentis Testim: Sold as Essentials, Pro, Mobile, and Salesforce plans with 24×5 chat support, all priced by quote. A free, self-service “Community” plan (features subject to change, one per organization) is what accounts revert to after a trial ends. Accepted payment is check or wire transfer, with more options at enterprise tiers.
mabl: Single published plan structure built around cloud test-run credits — 500 credits per month shared across browser/mobile UI, API, performance, and accessibility testing, with free, unlimited local and CI test runs. It includes unlimited apps, environments, workspaces, and “Participant” licenses, live 24/5 support, and a Customer Success Manager; actual dollar pricing requires contacting sales. Mobile App Testing and a dedicated Technical Account Manager are available as paid add-ons.
ACCELQ: Tiered by product (Automate Web, API, Mobile) and plan (Professional vs. Enterprise), each by quote. “Automate Manual” for individuals is free for life with core test design and manual test running; Teams and Enterprise tiers add collaboration, SSO, unlimited execution agents, and longer result retention, all requiring a sales conversation. On-premise deployment requires a minimum of 10 licenses, and the newer Autopilot Gen AI features are billed as a separate add-on subscription.
Pros
Tricentis Testim: Mature self-healing locator technology with years of refinement post-acquisition; strong fit for teams already standardized on Salesforce; flexible execution (local, Testim grid, or existing Selenium grid) eases migration from legacy scripts.
mabl: Approachable natural-language test creation suitable for non-engineers; auto-healing changes go through a human approval step rather than applying silently; broad coverage (web, mobile, API, AI-output validation) in one UI.
ACCELQ: Combines test management, requirements traceability, and automation in a single platform, reducing tool sprawl for larger QA orgs; widest out-of-the-box protocol and packaged-app coverage of the three; a genuinely free tier exists for individual manual testers.
Cons
Tricentis Testim: No public pricing makes cost comparison difficult up front; the free Community plan is explicitly noted as subject to change; API testing is present but less prominently documented than web/mobile.
mabl: Credit-based cloud test-run model (500/month baseline) could force an upgrade conversation for teams running large suites frequently; API testing is scoped to Postman collection imports rather than broader protocol support; no public price list.
ACCELQ: The flagship Gen AI “Autopilot” features (AI test case generation, autonomous element healing, natural-language authoring) require a separate paid subscription on top of the base platform, which can make the true cost of “AI-powered” testing higher than it first appears; pricing opacity extends across every tier above the free individual plan.
Who It’s a Good Fit For — and Who Should Look Elsewhere
A QA team actively replacing a legacy Selenium suite, especially one with heavy Salesforce testing needs, is the clearest match for Tricentis Testim: its self-healing locators directly target the maintenance pain of hand-coded scripts. Organizations trying to spread test authorship beyond dedicated automation engineers — onboarding product managers, designers, or manual QA staff as “citizen testers” — are better served by mabl’s natural-language, low-code workflow and its built-in review step for AI-made changes. Enterprises that need test automation bundled with formal test-case management, requirements traceability, and coverage of packaged business applications (Salesforce, SAP, Oracle, ServiceNow) alongside web/mobile/API should look at ACCELQ, understanding that its most advanced Gen AI features carry an additional cost. Teams with a tight budget and no appetite for a sales-led procurement process may find all three frustrating, since none publish self-serve pricing beyond trial/free tiers — in that case, it’s worth directly comparing open-source frameworks or simpler codeless tools before committing to an enterprise sales cycle.
Bottom Line
Testim, mabl, and ACCELQ all genuinely use AI to reduce the test-maintenance burden that makes hand-written automation expensive to keep up, but they aren’t interchangeable. Pick Tricentis Testim for Selenium-replacement projects and Salesforce testing, mabl for a low-code team that wants one easy-to-learn tool across web/mobile/API, and ACCELQ for an enterprise that wants test management and automation unified in a single platform — while budgeting separately for its Autopilot Gen AI add-on. Because none of the three publish list pricing, plan to request a quote and a trial from at least two before committing.
FAQ
Is Testim still a separate company? No. Tricentis acquired Testim in February 2022, and the product is now sold as “Tricentis Testim” as part of Tricentis’s broader continuous-testing lineup, rather than operating independently.
Do these tools fully replace manual QA engineers? No vendor claims that on its official pages. All three describe their AI as reducing authoring and maintenance effort — generating test steps, healing broken locators, triaging failures — rather than eliminating the need for QA oversight. mabl, for instance, routes auto-healed changes through a human approval screen rather than applying them automatically.
Which tool is cheapest? It isn’t possible to say from public information. Tricentis Testim, mabl, and ACCELQ all require a sales conversation for core plan pricing; only ACCELQ publishes a free-for-life tier (manual testing only, for individuals) and mabl publishes details of what a cloud credit allotment includes rather than its price.
Do any of these tools cover API testing? Yes, with different depth. Tricentis Testim documents API testing as part of its advanced editing features. mabl supports API testing via Postman collection imports. ACCELQ offers the broadest protocol coverage, including REST, SOAP, Kafka, message queues, microservices, and SSH.
Is ACCELQ’s AI test generation included in the base price? Not entirely. ACCELQ’s base automation plans include self-healing and codeless record/playback, but its newer Gen AI “Autopilot” suite — including the AI Test Case Generator and autonomous element healing refinements introduced in Release 7.0 — requires a separate add-on subscription, per ACCELQ’s own support documentation.
Every large distributed system eventually has to answer the same question: given a piece of data and a set of machines that can store it, which machine should hold it? The naive answer — hash the key and take it modulo the number of machines — works fine until a machine is added or removed, at which point almost every key lands on a different machine. Consistent hashing is the technique that fixed this, and it quietly underpins the caches, CDNs, and databases that most of the internet runs on.
At a Glance
Attribute
Details
Problem it solves
Minimizing data/key remapping when nodes (servers, caches, shards) are added or removed from a distributed system
Map both nodes and keys onto a circular hash space (“ring”); each key belongs to the next node clockwise
Typical lookup complexity
O(log n) with a sorted ring structure (binary search over node positions)
Remapping on node change
On average only K/n keys move, versus nearly all keys with plain modulo hashing
Key refinement
Virtual nodes (multiple ring positions per physical node) to smooth out load imbalance
Originates from
Karger et al., “Consistent Hashing and Random Trees” (STOC, 1997)
The Problem With Naive Modulo Hashing
Suppose you have a pool of cache servers and you want to decide which server stores which key. The simplest approach is server = serverlist[hash(key) % N], where N is the number of servers. This distributes keys evenly as long as N never changes. The trouble starts the moment it does.
If you go from N to N+1 servers, the modulus changes, and for almost every key, hash(key) % N and hash(key) % (N+1) point to different servers. In practice this means nearly the entire cache is invalidated at once: every client suddenly looks for its data on the “wrong” server, gets a miss, and re-fetches from the origin. This is exactly the scenario Richard Jones at Last.fm described when building ketama, a consistent-hashing library for memcached: with naive modulo hashing, adding or removing even one server from the pool “effectively wiped the entire cache,” because nearly every key remapped to a different node at once.
For a cache, that’s a painful but survivable thundering herd against the origin servers. For a sharded database, it’s worse: it means moving nearly all of your data between machines just because one machine joined or left the cluster.
How Consistent Hashing Works: The Hash Ring
Consistent hashing was introduced by David Karger and colleagues at MIT in their 1997 paper “Consistent Hashing and Random Trees,” written to address hot spots on the early web, where a surge of requests for one popular page could overwhelm a single cache server, and where different clients might have inconsistent views of which caches were even available. Their insight was to stop treating the server list as a flat array indexed by a modulus, and instead map both servers and keys onto points on a shared, circular space — commonly visualized as a clock face or ring running from 0 up to some maximum hash value and then wrapping back to 0.
The mechanics are simple:
Hash each server (by its address or ID) to get a position on the ring.
Hash each key the same way to get its own position on the ring.
To find which server owns a key, walk clockwise from the key’s position until you hit the first server position. That server owns the key.
If you reach the end of the ring without finding a server, wrap around to the first one.
The payoff shows up when the server set changes. If you remove a server, only the keys that were mapped to it need to move — and they move to the next server clockwise, not to some arbitrary new location. If you add a server, it slots in between two existing positions and takes over only the keys in that narrow arc; every other server’s holdings are untouched. The original paper formalizes this as the “monotonicity” property: when a new bucket is added, items can move only to the new bucket, never between two buckets that already existed. On average, adding or removing a node remaps only about K/n of the keys, where K is the total number of keys and n is the number of nodes — a dramatic improvement over the “remap almost everything” behavior of modulo hashing. Amazon’s Dynamo paper independently arrives at the same mechanism for the same reason, describing the mechanism as treating the hash space as “a fixed circular space or ring,” with each key assigned by walking clockwise to the first node encountered, so that “the departure or arrival of a node only affects its immediate neighbors.”
Virtual Nodes and Why They Matter
A plain hash ring with one position per server has a real weakness: because server positions are essentially random, the arcs between them are wildly uneven. Some servers end up owning a tiny sliver of the keyspace and others a huge chunk, simply by the luck of where their hash landed. With only a handful of servers, this imbalance can be severe.
The fix, present in both Karger’s original analysis and every production system that followed, is to give each physical node many positions on the ring instead of one — commonly called virtual nodes, replicas, or (in Dynamo’s terminology) tokens. Karger et al. show that assigning each bucket a number of points proportional to log(number of buckets) is what makes their balance, spread, and load guarantees hold with high probability; a single point per bucket does not give those guarantees. The ketama library, widely used for memcached client-side sharding, applies the same idea concretely: each server is hashed to somewhere between 100 and 200 points on a 32-bit ring, which smooths out the lumpy distribution a single point per server would produce.
Amazon’s Dynamo paper gives three concrete reasons for using virtual nodes rather than one token per physical node:
Heterogeneity: a more powerful machine can be given more tokens than a weaker one, so it naturally takes on a proportionally larger share of the keyspace.
Failure handling: when a node goes down, its load disperses across many remaining nodes rather than piling entirely onto whichever single node happens to be its ring neighbor.
Rebalancing on recovery or growth: when a node returns or a new node joins, it absorbs a roughly equal slice of load from each of several other nodes instead of taking one large block from a single neighbor.
Virtual nodes don’t change the fundamental ring-walking algorithm; they just make the resulting distribution far more even in practice, at the cost of a larger table of ring positions to search.
A Minimal Hash Ring in Python
The following is a deliberately small illustration of the ring-lookup mechanism — enough to show the idea, not a production-grade implementation (a real one needs a consistent, well-distributed hash function and careful handling of collisions):
import bisect
import hashlib
class HashRing:
def __init__(self, nodes=None, virtual_nodes=100):
self.virtual_nodes = virtual_nodes
self.ring = {} # hash position -> node name
self.sorted_keys = [] # sorted list of hash positions
for node in nodes or []:
self.add_node(node)
def _hash(self, key):
digest = hashlib.md5(key.encode("utf-8")).hexdigest()
return int(digest, 16)
def add_node(self, node):
for i in range(self.virtual_nodes):
pos = self._hash(f"{node}#{i}")
self.ring[pos] = node
bisect.insort(self.sorted_keys, pos)
def remove_node(self, node):
for i in range(self.virtual_nodes):
pos = self._hash(f"{node}#{i}")
del self.ring[pos]
self.sorted_keys.remove(pos)
def get_node(self, key):
if not self.ring:
return None
pos = self._hash(key)
idx = bisect.bisect(self.sorted_keys, pos) % len(self.sorted_keys)
return self.ring[self.sorted_keys[idx]]
ring = HashRing(nodes=["cache-a", "cache-b", "cache-c"])
print(ring.get_node("user:42"))
The bisect module gives the O(log n) lookup: instead of scanning every ring position, it binary-searches the sorted list of positions for the first one at or after the key’s hash. Adding or removing a node only touches that node’s own virtual_nodes entries, leaving everyone else’s ring positions, and therefore their keys, alone.
Real-World Uses
Consistent hashing shows up anywhere a fixed key needs to reliably route to the same backend, cache, or partition, even as the pool of backends changes:
Distributed caches: ketama is the canonical example, used by memcached client libraries so that adding or removing a cache server only displaces a small fraction of keys instead of collapsing the whole cache.
Databases and storage systems: Amazon’s Dynamo uses a ring-based partitioning scheme with virtual nodes (“tokens”) to spread both data and replica placement across a cluster that can grow or shrink. According to Wikipedia’s overview of the technique, Apache Cassandra, Riak, Voldemort, and ScyllaDB apply the same idea for data partitioning, and Couchbase and OpenStack Swift use it for automated partitioning across storage nodes.
Request routing in chat/messaging infrastructure: Discord’s engineering team has described routing requests in its Rust-based data services using a consistent-hash-based scheme keyed on channel ID, so that requests for the same channel land on the same service instance, which improves local request coalescing and reduces redundant load on the databases behind it.
CDNs and load balancing: Wikipedia’s article on the technique notes that Akamai’s CDN — co-founded by one of the original paper’s authors — uses consistent hashing to balance load within a cluster of servers, and that Discord also applies it for load balancing in its chat application.
Consistent Hashing vs. Alternatives
Approach
How it picks a node
Remapping on node change
Extra state required
Where it tends to fit
Modulo hashing
hash(key) % N
Nearly all keys, on almost any change to N
None — just the node count
Fixed-size pools that rarely or never resize
Consistent hashing (ring)
Walk clockwise on a shared ring from the key’s hash position
~K/n keys on average; only neighbors of the changed node are affected
Sorted table of (virtual) node positions
Caches, databases, and routers where nodes join/leave regularly
Rendezvous hashing (highest random weight)
Compute a weighted score for every node for the given key; pick the highest
Similar minimal-disruption property to consistent hashing, without needing a ring data structure
None beyond the node list — no ring to maintain
Systems that prefer a stateless, ring-free computation per lookup
Rendezvous hashing, sometimes called highest random weight (HRW) hashing, is the most common alternative discussed alongside consistent hashing: rather than placing nodes on a ring, it computes a hash-based score for every (key, node) pair and picks the node with the highest score. It achieves a similar minimal-disruption property to ring-based consistent hashing without requiring a maintained ring structure, at the cost of an O(n) scan over all nodes per lookup unless additional indexing is layered on top.
Trade-offs and Limitations
Consistent hashing is not free of complexity:
Load imbalance without virtual nodes: a plain one-position-per-node ring can leave some nodes with a disproportionate share of keys purely due to hash placement; this is why virtual nodes are near-universal in real deployments, as both the original paper’s analysis and systems like ketama and Dynamo demonstrate.
More moving parts than a modulus: maintaining a sorted ring (or token table) and doing a binary search is more machinery than a single modulo operation, even though the asymptotic lookup cost, O(log n), stays cheap.
Hot keys aren’t solved by hashing alone: consistent hashing distributes keys evenly across nodes, but it does nothing to prevent one specific, very popular key from overwhelming the single node it lands on. Discord’s own account of hot partitions in its message-storage systems is a reminder that key distribution and load distribution are related but distinct problems — consistent hashing addresses the former, not automatically the latter.
Still requires replication and consensus elsewhere: consistent hashing answers “which node owns this key,” not “how many copies exist” or “what happens during a network partition.” Systems like Dynamo pair it with separate replication and quorum mechanisms.
Bottom Line
Consistent hashing exists to solve one specific, well-defined pain point: keeping key-to-node assignment stable as the set of nodes changes. By placing keys and nodes on a shared ring instead of indexing a flat array with a modulus, it turns a full-cache-wipe event into a localized, proportional reshuffle — and by giving each physical node many positions on that ring (virtual nodes), it keeps the resulting distribution close to even in practice. That combination is why it has been reinvented, cited, and reimplemented across three decades of infrastructure, from Akamai’s original CDN caches to memcached pools to Amazon’s Dynamo and the databases it inspired.
FAQ
Is consistent hashing the same as a hash ring? The hash ring is the standard way to implement consistent hashing, but the two aren’t strictly synonymous — the original Karger et al. paper describes the mapping onto a circular space, and “hash ring” is simply the common name for that structure. Rendezvous hashing achieves comparable properties without a ring at all.
Why not just use a bigger, better modulus? No modulus avoids the core issue: changing N, the number of slots, changes essentially every key’s hash(key) % N result regardless of which hash function you use. The problem is structural, not a hash-quality issue.
How many virtual nodes should a real system use? There’s no single universal number. Ketama, used for memcached, assigns roughly 100-200 points per physical server. Amazon’s Dynamo paper leaves the exact token count as a tunable parameter (denoted T) rather than specifying one fixed value, since the right count depends on cluster size and how evenly capacity needs to be represented.
Does consistent hashing guarantee perfectly even load? No. Even with virtual nodes, the original paper only proves balance, spread, and load bounds that hold with high probability, not exact equality. Popular individual keys (“hot keys”) can still overload a single node regardless of how evenly the keyspace itself is divided.
Where did the idea originate? From David Karger, Eric Lehman, Tom Leighton, Rina Panigrahy, Matthew Levine, and Daniel Lewin’s 1997 paper “Consistent Hashing and Random Trees: Distributed Caching Protocols for Relieving Hot Spots on the World Wide Web,” presented at STOC 1997. Several of the authors went on to co-found Akamai.
Sources
This article draws on the following primary and engineering sources:
Teams building autonomous developer agents in 2026 keep landing on the same three names: LangGraph, CrewAI, and AutoGen. All three are open-source orchestration frameworks, not SaaS products, and each takes a genuinely different approach to the same problem: how do you get one or more large language models to plan, call tools, and hand off work reliably instead of just answering a single prompt? This guide compares their architectures, licensing, and paid add-ons using only what each project’s own GitHub repository and documentation say, so you can pick the right foundation instead of guessing from a blog post.
At a Glance
Framework
License
Primary Language
Best For
LangGraph (LangChain)
MIT (code)
Python, with a separate LangGraph.js library
Fine-grained control over stateful, long-running agent workflows
CrewAI
MIT (code)
Python (>=3.10, <3.14)
Role-based teams of agents collaborating on a shared goal
AutoGen (Microsoft)
MIT (code) / CC BY 4.0 (docs)
Python, plus a .NET implementation
Conversational multi-agent prototypes — now in maintenance mode
Short Verdict
LangGraph is the strongest default for a developer agent that needs explicit, debuggable control over state and execution order, and it pairs with LangSmith if you want hosted tracing and deployment. CrewAI is the fastest way to stand up a team of role-playing agents with minimal boilerplate, backed by an optional commercial control plane for production governance. AutoGen’s core GitHub project is now officially in maintenance mode, with Microsoft steering new work toward Microsoft Agent Framework, so teams starting fresh in 2026 should strongly consider AG2 — the actively developed community fork — instead of the original repo.
What Is an AI Agent Framework?
An “AI agent framework” is a code library that sits between a raw LLM API call and a working autonomous system. It typically handles three things an LLM can’t do on its own: orchestration (deciding what step runs next, and in what order), tool-calling (letting the model invoke functions, APIs, or code execution and feed results back in), and multi-agent coordination (letting several specialized agents communicate, delegate, and share state). For developer-agent use cases — writing code, running tests, opening pull requests — the framework is the part that keeps a long chain of model calls from drifting, looping forever, or losing track of what it already tried.
LangGraph: Graph-Based State Machines
LangGraph describes itself in its own documentation as “a low-level orchestration framework and runtime for long-running, stateful agents.” Instead of a fixed agent loop, you model your workflow as a graph: a shared, typed state object, a set of nodes (plain functions, each of which reads and updates that state), and edges that define which node runs next. This graph model is what gives LangGraph its defining strengths — durable execution, streaming, persistence, and human-in-the-loop checkpoints — because the runtime can pause, inspect, or resume at any node boundary rather than treating the whole run as one opaque call.
LangGraph works standalone and doesn’t require LangChain, though many examples use LangChain’s model and tool integrations alongside it. The project’s own docs are explicit that it is deliberately low-level: it doesn’t prescribe a prompt format or agent architecture, and the maintainers point developers toward higher-level options (like LangChain’s own prebuilt agents) if they don’t need this much control. The paid layer in this ecosystem is LangSmith, described in LangGraph’s docs as “the platform for tracing, evaluation, prompts, and deployment across frameworks” — it’s a separate, commercial product for observability and hosted deployment, not part of the open-source graph runtime itself.
Here’s a minimal LangGraph graph with two nodes, matching the pattern shown in LangGraph’s official Python documentation:
CrewAI bills itself as “the leading open-source framework for orchestrating autonomous AI agents and building complex workflows,” released under the MIT license and requiring Python 3.10 through 3.13. Its model is built on two complementary pieces. A Crew is a team of agents, each given a role, a goal, and a backstory, that collaborate on tasks through role-based delegation — this is the part most people mean when they say “CrewAI agents.” A Flow is the event-driven backbone around that: it defines steps, conditional branching, loops, and shared state, and it’s the layer that decides when and how a Crew gets invoked. In practice, a Flow is the controller and a Crew is the team it dispatches work to.
CrewAI’s documentation supports defining agents and tasks directly in Python (instantiating an Agent object with role, goal, and backstory parameters) as well as a project-based structure that loads agent and crew definitions from config files. On the commercial side, CrewAI offers what its README calls the “AMP Suite,” a control plane adding managed deployment, observability, governance, and enterprise support on top of the open-source framework, with both cloud and on-premise options and a free trial; the public materials don’t list specific subscription pricing.
AutoGen and AG2: Conversable Multi-Agent Chat
Microsoft’s AutoGen pioneered a different mental model: agents as participants in a conversation. Its current architecture, documented at microsoft.github.io/autogen, is layered — a Core API described as “an event-driven programming framework for building scalable multi-agent AI systems,” an AgentChat API built on top of it for conversational single- and multi-agent patterns including two-agent chats and group chats, an Extensions layer for connectors like MCP servers and Docker code execution, and AutoGen Studio, a no-code prototyping UI that the docs explicitly say is “not meant to be a production-ready app.”
The material fact developers need going into 2026: Microsoft’s own GitHub repository states that AutoGen is now community-managed and in maintenance mode, and recommends Microsoft Agent Framework for new projects. This was confirmed by Microsoft’s own announcement, reported by VentureBeat, that AutoGen and Semantic Kernel both moved to maintenance mode — receiving bug fixes and security patches but no new features — while Microsoft Agent Framework, released in public preview, absorbs both projects’ capabilities as the company’s forward-looking SDK. No breaking changes were planned for existing AutoGen workloads, but new feature work isn’t happening there.
Separately, AG2 (hosted at ag2ai/ag2, Apache-2.0 licensed, requiring Python 3.11+) is a community-driven continuation that describes itself as “AG2 (formerly AutoGen).” Its README is direct that AG2 v1.0 is not a drop-in upgrade from “AG2 Classic” (the original AutoGen-derived lineage, now kept in a separate ag2ai/ag2-classic repository): the classic ConversableAgent, GroupChat, and swarm patterns are gone, replaced by an Agent primitive and a “Hub”/”Network” model for multi-agent coordination. For anyone evaluating “AutoGen” today, it’s worth knowing you’re really choosing between three things: the original Microsoft repo (maintenance mode), AG2 (actively developed fork with a changed API), or Microsoft Agent Framework (the new, non-AutoGen successor).
Pros
LangGraph — explicit, inspectable state at every step; built-in support for persistence, streaming, and pausing a run for human approval; works with or without LangChain; a JavaScript/TypeScript version (LangGraph.js) exists for non-Python teams.
CrewAI — fast to get a multi-agent “team” running with role/goal/backstory framing that’s intuitive to reason about; Flows give deterministic control flow on top of the agent layer; permissive MIT license with no required paid tier.
AutoGen — the AgentChat API’s conversational pattern (two-agent chat, group chat) is still a clean mental model for prototyping; Core API is event-driven and can scale to larger multi-agent systems; both Python and .NET implementations exist.
Cons
LangGraph — deliberately low-level, so simple use cases mean writing more graph-wiring code than a higher-level framework would require; full observability and managed deployment live behind the separate, commercial LangSmith product.
CrewAI — the Crew/Flow split adds a second mental model (event-driven Flows versus role-based Crews) that takes time to learn; production governance features are gated behind the commercial AMP Suite, whose pricing isn’t published.
AutoGen — the GitHub project itself says it’s community-managed and in maintenance mode, so it won’t gain new features; AutoGen Studio is explicitly not production-ready; teams who want ongoing development must evaluate AG2 or Microsoft Agent Framework instead, and AG2’s own README warns its newest version is not a drop-in replacement for the classic API.
Who It’s a Good Fit For
Choose LangGraph if your developer agent needs durable, auditable execution — for example, a coding agent that runs for minutes or hours, needs to resume after a failure, or needs a human to approve a risky step (like merging a PR) before continuing. Choose CrewAI if you’re modeling the problem as a team with distinct responsibilities — a researcher agent, a coder agent, a reviewer agent — and want that structure to be the primary abstraction rather than a graph you wire by hand. Choose AG2 (not the original AutoGen repo) if you specifically want the conversational, chat-style multi-agent pattern and are comfortable adopting an actively developed fork with its own evolving API.
Who Should Look Elsewhere
Teams that want a single, prescriptive “just works” agent loop with minimal setup may find LangGraph’s low-level graph API more plumbing than they want — LangChain’s own higher-level agent abstractions, built on top of LangGraph, are the documented alternative. Teams that need heavy deterministic control-flow logic as the primary structure (not agent roles) may prefer LangGraph’s explicit graphs over CrewAI’s Crew abstraction. And anyone starting a new project in the Microsoft ecosystem should not default to the original AutoGen repository, given Microsoft’s own guidance to evaluate Microsoft Agent Framework first.
Bottom Line
All three frameworks are free, open-source, and genuinely production-capable, but they solve the orchestration problem from different angles: LangGraph with explicit graphs and state, CrewAI with role-based teams and event-driven Flows, and AutoGen with conversational multi-agent chat. The licensing and cost model is simple across the board — MIT-licensed open source with an optional, separately priced commercial layer (LangSmith for LangGraph, the AMP Suite for CrewAI) — except AutoGen, where the more important 2026 fact isn’t pricing but status: the original project is in maintenance mode, and the real choice is between AG2’s fork and Microsoft’s newer Agent Framework.
FAQ
Are LangGraph, CrewAI, and AutoGen free to use? Yes. All three are open-source under permissive licenses (LangGraph and CrewAI under MIT, AutoGen’s code under MIT) and free to self-host. Each has an optional commercial layer on top — LangSmith for LangGraph, the AMP Suite for CrewAI — for managed deployment and observability, but none require it to run.
Is Microsoft’s AutoGen still being actively developed in 2026? The original microsoft/autogen repository is in maintenance mode: it gets bug fixes and security patches but no new features, per Microsoft’s own GitHub page and its public announcement covered by VentureBeat. Active development of the AutoGen lineage continues in the community-run AG2 fork, while Microsoft’s own forward investment is in Microsoft Agent Framework.
Do I need LangChain to use LangGraph? No. LangGraph’s documentation describes it as working on its own; LangChain provides optional higher-level agent abstractions and integrations that many examples use alongside it, but the graph runtime itself is independent.
What’s the difference between a CrewAI Crew and a Flow? A Crew is a team of role-playing agents that collaborate on tasks through delegation. A Flow is the event-driven layer around it that defines steps, state, and control flow (conditionals, loops, branching) and decides when to hand work to a Crew.
Can I combine these frameworks, or use AG2 instead of AutoGen? They’re independent Python libraries, so technically you can call one from inside another’s tool node (for example, a LangGraph node that invokes a CrewAI Crew). AG2 is a separate package (pip install ag2) with its own API — its README is explicit that v1.0 is not a drop-in replacement for classic AutoGen code, so migrating requires reading AG2’s own migration notes rather than assuming compatibility.
Every database that stores data on disk has to answer the same question: how should the data be laid out so that reads and writes are both reasonably fast? There is no structure that is optimal at both, so database engineers have converged on two dominant answers. B-trees, refined for decades, keep data sorted on disk so that reads are cheap and predictable. Log-structured merge-trees (LSM-trees), introduced in a 1996 paper by Patrick O’Neil and co-authors, instead buffer writes in memory and write them out in large sequential batches, trading some read performance for dramatically cheaper writes. Almost every database you’ve heard of picked one of these two, and the choice shapes everything else about how it behaves under load.
A B-tree is a balanced, multi-way tree. PostgreSQL’s own documentation describes its B-tree index as organized into levels that can each be traversed as a doubly linked list of pages, with a fixed metapage at the start of the index and leaf pages — which make up over 99% of all pages in practice — holding the tuples that point back to table rows. Internal pages hold “downlinks” to the level below. When a leaf page fills up, it splits in two and a new downlink is inserted into its parent; if the root itself has to split, the tree gains a new level. This is the mechanism that keeps the tree balanced: height only grows when the root splits, so every leaf stays the same distance from the root.
SQLite’s file format documentation describes the same balance property from a different angle: an interior b-tree page’s children are all required to be at the same depth, which is what keeps lookups to a predictable number of page reads. MySQL’s InnoDB storage engine likewise clusters table rows directly in the leaf pages of a B-tree keyed on the primary key (its “clustered index”), with secondary indexes stored as separate B-trees that point back to that primary key.
Because the tree stays sorted and balanced at all times, a lookup, a range scan, or an ORDER BY can walk directly from the root to the relevant leaf in a small, predictable number of I/Os. PostgreSQL’s documentation on index types notes that B-tree indexes handle not just equality but also range comparisons, BETWEEN, IN, and sorted output, which is why B-tree is the default index type for CREATE INDEX. The cost of that convenience shows up on the write side: inserting or updating a row means finding the correct leaf page and modifying it in place, which the original LSM-tree paper describes as costing “about two random disk I/Os” for an index on a table growing quickly — a cost that accrues continuously as more pages fill up and split.
How LSM-Trees Work — and Why They’re Write-Optimized
The log-structured merge-tree was introduced by Patrick O’Neil, Edward Cheng, Dieter Gawlick, and Elizabeth O’Neil in a 1996 paper in Acta Informatica, motivated by exactly the write-cost problem above: on a file experiencing a high rate of inserts, maintaining a B-tree index in real time could push total system I/O cost up by as much as 50%. Their fix was to stop updating the on-disk structure immediately and instead defer and batch those updates.
The paper’s design uses multiple components of increasing size. The smallest, C0, is “entirely memory resident,” so new entries can be inserted with no disk I/O at all. In modern systems such as RocksDB this component is called the memtable — RocksDB’s own wiki describes it as an in-memory, skiplist-based structure that absorbs every write, and which becomes read-only (immutable) once it reaches a size threshold (64MB by default), at which point a new memtable takes over and a background thread flushes the full one to disk as an SST file, RocksDB’s on-disk sorted-string table format — the modern descendant of the paper’s larger, disk-resident C1 component.
Once data lands on disk as immutable sorted files, it has to be kept under control, because a lookup may otherwise have to check every file ever flushed. This is done by compaction: a background process that merges sorted files together, drops overwritten or deleted entries, and writes the result out as new, larger sorted files. The original paper calls this a “rolling merge,” carried out by a cursor that circulates through the key range, moving entries from the smaller component into the larger one; because the merge writes to new disk locations, the old blocks remain valid until the merge’s trailing edge frees them, which keeps crash recovery simple. RocksDB’s compaction documentation describes the same idea in modern terms: in its default “leveled” compaction style, level 0 holds the newest flushed data, and each level below is progressively larger and older, with compaction merging data from one level into the next.
Here is a simplified sketch of the merge step at the heart of compaction — merging several sorted runs into one, keeping only the newest version of each key:
function compact(sorted_runs):
# sorted_runs: list of sorted (key, value, sequence_number) iterators,
# newest run first
output = []
heap = min-heap of (key, run_index) seeded with each run's first entry
while heap is not empty:
key, run_index = heap.pop_min()
entry = sorted_runs[run_index].current()
# keep only the newest version of this key across all runs
if entry.sequence_number is the highest seen for `key`:
if not entry.is_tombstone:
output.append(entry)
# else: deletion marker, drop the key entirely
advance sorted_runs[run_index]
skip any further entries in other runs that still match `key`
if sorted_runs[run_index] has more entries:
heap.push(sorted_runs[run_index].current().key, run_index)
write output as one new sorted file
Because every write — insert, update, or delete — is just an append to the current memtable and, eventually, a sequential write during flush or compaction, LSM-trees turn expensive random-page writes into cheap sequential ones. The cost shows up later and in the background, during compaction, rather than synchronously on every write.
Write Amplification vs. Read Amplification
The trade-off between these two designs is usually described with two terms: write amplification (how many times a byte of data gets physically rewritten before it settles) and read amplification (how many places a read might have to check before it finds the right version of a key).
B-trees have low write amplification per logical write in the sense that only the affected leaf (and occasionally its ancestors, on a split) is touched — but each of those touches is a random I/O, and the original LSM-tree paper’s whole argument is that on a fast-growing index this random-I/O cost dominates. Reads, by contrast, are cheap: one descent from root to leaf.
LSM-trees push that cost around. Writes are sequential and batched, so they’re fast, but the same piece of data can be rewritten multiple times as it’s compacted from one level to the next — RocksDB’s compaction documentation states this directly, noting that its default leveled compaction style has “higher write amplification” because data is rewritten at each level, while its alternative “universal” (tiered) style minimizes write amplification at the cost of higher read and space amplification, because more separate sorted runs have to be kept and checked. Apache Cassandra’s documentation makes the same point about its own LSM-based storage engine: compaction “causes write amplification, meaning data is rewritten multiple times,” which it frames as the explicit cost of a write-optimized design, offset by Bloom filters that let reads skip files that can’t contain a given key. A read against an LSM-tree, in the worst case, has to check the memtable and then every relevant on-disk level until it finds the key (or confirms it’s absent) — the 1996 paper notes plainly that “LSM-tree finds of three or more components suffer somewhat in performance, typically by one extra page I/O per disk component.”
B-Trees vs. LSM-Trees: Side by Side
Factor
B-Tree
LSM-Tree
Write cost
Random I/O per update; costly under high insert rate
Sequential, batched; cheap per write, cost deferred to compaction
Read cost
One predictable tree descent
May touch memtable plus several on-disk levels/files
Space overhead
Pages kept partially full to allow inserts (InnoDB reserves ~1/16 of each page)
Stale/overwritten versions linger until compaction reclaims them
Background work
Occasional page splits/merges
Continuous compaction merging sorted files
Update-in-place
Yes, row is modified where it lives
No, new version appended; old version removed later by compaction
Best fit
Mixed read/write OLTP workloads
Write-heavy / high-ingest workloads tolerant of eventual background cost
Which Real Databases Use Which
The split between the two designs is visible across the industry’s best-known systems.
PostgreSQL uses a B-tree as the default index type for CREATE INDEX, per its own documentation, handling equality, range comparisons, and sorted retrieval.
MySQL (InnoDB) stores table rows directly inside a B-tree clustered on the primary key, with secondary indexes as separate B-trees pointing back to it, as described in MySQL’s own InnoDB documentation.
SQLite stores every table and index as a B-tree on disk — a “table b-tree” keyed by rowid holding the actual row data, and “index b-trees” for secondary indexes — as laid out in SQLite’s file format documentation.
RocksDB, Meta’s embedded key-value store, is explicitly built as a log-structured merge-tree: writes land in an in-memory memtable and a write-ahead log, and are later flushed and compacted into on-disk SST files, per its own wiki documentation.
LevelDB, the Google-originated key-value library RocksDB was forked from, uses the same memtable/SSTable/compaction design.
Apache Cassandra documents its storage engine as explicitly “based on Log Structured Merge (LSM) trees,” using an append-only commit log, memtables, and SSTables merged by background compaction.
Several other widely used systems (such as HBase and ScyllaDB) also use LSM-tree-based storage engines, though this article focuses on the sources verified above.
Bottom Line
Neither design is objectively better — they optimize for opposite failure modes. A B-tree keeps data sorted on disk at all times, so reads stay fast and predictable, at the cost of expensive random writes as the tree grows; that’s the right trade-off for general-purpose relational tables and anything read-heavy. An LSM-tree defers that cost by buffering writes in memory and flushing them as large sequential batches, accepting slower and more variable reads (and ongoing compaction overhead) in exchange for write throughput that can be an order of magnitude higher; that’s the right trade-off for logging, time-series ingestion, and other high-write-rate workloads. Many modern systems don’t pick just one globally — some let you choose a storage engine per table or per workload — but understanding which cost each structure defers, and to where, is what makes that choice make sense.
FAQ
Is an LSM-tree always faster than a B-tree? No. It’s faster for writes because it turns random writes into sequential ones, but reads can be slower because a lookup may have to check the memtable plus multiple on-disk levels, and compaction adds background I/O. The 1996 paper that introduced the structure says this plainly: lookups “will lose I/O efficiency in some cases” compared to a B-tree.
What is compaction, in one sentence? It’s the background process that merges multiple sorted on-disk files into fewer, larger ones, discarding obsolete or deleted entries so reads don’t have to check an ever-growing number of files.
Why do B-trees reserve empty space in their pages? So that later inserts and updates can be absorbed without an immediate page split. MySQL’s InnoDB documentation notes it tries to keep about 1/16 of each clustered index page free by default for this reason.
Can a database use both structures? Yes, at the system level. Several databases support multiple storage/index engines, and an application can mix a B-tree-backed relational database with an LSM-based key-value store for different parts of the same system, choosing per workload.
Does “sorted string table” (SSTable) mean the same thing as the original paper’s “C1 component”? Conceptually yes — both are immutable, sorted, disk-resident structures that hold the bulk of the data and are produced and merged by batch processes. SSTable is the specific file format used in LevelDB, RocksDB, Cassandra, and similar systems; the term predates the original paper’s exact terminology but implements the same core idea.
Startups chasing their first SOC 2 report and larger companies juggling SOC 2, ISO 27001, HIPAA, and GDPR at once tend to land on the same short list: Vanta, Drata, and Secureframe. All three replace spreadsheets and screenshots with continuous monitoring, automated evidence collection, and a workspace auditors can log into directly. This guide compares what each platform actually automates, how transparent their pricing is, which frameworks they cover, and which one fits a first-time SOC 2 startup versus a company managing multiple frameworks.
At a Glance
Tool
Pricing Model
Published Starting Price
Free Trial
Best For
Vanta
Custom quote (no public price list)
Not published; “Get personalized pricing” only
Yes — 7 days (14 days for the enterprise trial)
Startups and mid-market teams wanting the broadest integration ecosystem and an AI-assisted workflow
Drata
Custom quote (no public price list)
Not published; contact sales for Startup/Growth tiers
Yes — 21 days, no credit card required
Companies that want a fixed annual price regardless of headcount growth and a dedicated CSM from day one
Secureframe
Partly public: entry tier has a listed starting price; higher tiers are quote-only
Fundamentals: “Starting at $7,500/year”
Not mentioned on the pricing or trial-demo page (length/terms unstated)
Budget-conscious first-time SOC 2 teams who want at least one real price anchor, and larger teams needing CMMC 2.0 support
Short Verdict
All three automate the same core job — continuous control monitoring, automated evidence collection, and auditor-facing access — so the real differences are commercial, not functional. Secureframe is the only one that publishes any price at all ($7,500/year for its entry Fundamentals tier). Vanta and Drata require a sales conversation before you see a number, but both offer free trials (7–14 days and 21 days respectively) to test integrations before negotiating. None is a bad choice for a first SOC 2; the decision usually comes down to the quote you get and which integration list matches your stack.
What These Platforms Actually Are
Vanta, Drata, and Secureframe are compliance automation (“audit readiness”) platforms. Instead of manually screenshotting AWS IAM settings or chasing laptop encryption status in a spreadsheet, each tool connects to your cloud provider, identity provider, HR system, and device management tool, then continuously checks whether your environment matches the controls a framework like SOC 2 or ISO 27001 requires, flagging drift — a public S3 bucket, an offboarded employee who still has access — before an auditor sees it. All three converge on a similar feature set: policy templates, automated evidence collection, continuous monitoring, a questionnaire-response tool, and a “Trust Center” page. They diverge on integration breadth, depth of automation beyond SOC 2, and how willing each vendor is to publish a price.
What Each One Automates
Vanta — “Agentic” evidence collection, continuous monitoring at every tier, an Auditor API, and a claimed 400+ integrations. Higher tiers add custom monitoring tests, access management, and tiered-cap AI questionnaire automation.
Drata — 80+ integrations and an open API, automation across “16+ frameworks,” and 20+ auditor-approved policy templates with built-in signing. Its “Alliance Audit Firm” network offers preferred pricing, though any auditor works; audit fees go to the firm, not Drata.
Secureframe — Infrastructure and continuous monitoring, evidence collection, 300+ integrations (custom from Complete up), automated onboarding/offboarding, AI policy drafting (“Comply AI”), asset scoping, and a device agent. Its Audit Partner Network starts at Complete.
The evidence-collection and continuous-monitoring claims are broadly comparable across all three; the variable that matters most is whether your specific cloud provider, HRIS, or device management tool is on each vendor’s integration list.
Pricing Breakdown: Mostly Quote-Only
This is where buyers get the least help from the vendors, so it’s worth being precise about what is and isn’t public.
Vanta publishes no prices. It names four tiers — Essentials, Plus, Professional, and Enterprise — and describes what each unlocks, but every tier routes to a “Get personalized pricing” form with no starting dollar figure.
Drata is the same story under different tier names: “Startup” and “Growth,” plus a custom hybrid plan. Drata’s page emphasizes a subscription price fixed for the year even as headcount grows, and every plan includes a dedicated Customer Success Manager — but no number appears without talking to sales.
Secureframe is the partial exception: its entry-level Fundamentals tier is listed as “Starting at $7,500/year” directly on the pricing page — a real anchor the other two don’t give you. That tier includes infrastructure monitoring, evidence collection, and a Trust Center, capped at 100 AI questionnaire responses and 15 Trust Center requests per year. Complete and Defense (built for CMMC 2.0) are both quote-only.
Treat any number beyond Secureframe’s $7,500/year figure — including cost estimates on third-party comparison sites — as unverified, not vendor-confirmed. Actual cost for all three scales with headcount, number of frameworks, and add-ons, and requires a live quote.
Framework Coverage
Framework
Vanta
Drata
Secureframe
SOC 2
Yes
Yes
Yes
ISO 27001
Yes
Yes
Yes
HIPAA
Yes
Yes
Yes
GDPR
Yes
Yes
Yes
PCI DSS
Mentioned only in page metadata, not the listed framework set
Yes
Yes
ISO 42001 / AI frameworks
Yes (ISO 42001, NIST AI RMF)
Not specified on the pages reviewed
Not specified on the pages reviewed
CMMC 2.0
Not specified on the pages reviewed
Not specified on the pages reviewed
Yes (dedicated “Defense” tier)
Custom frameworks
Yes
Not specified on the pages reviewed
Yes
All three clearly support the big four — SOC 2, ISO 27001, HIPAA, and GDPR — covering most first-time buyers. Beyond that: Vanta leans into AI-governance frameworks (ISO 42001, NIST AI RMF), Drata advertises the broadest raw framework count (“16+”), and Secureframe is the only one with a purpose-built CMMC 2.0 tier for defense-supply-chain companies.
Pros
Vanta
Largest advertised integration library (400+ tools)
Entry tier includes an Auditor API and continuous monitoring out of the box
Covers newer AI-governance frameworks (ISO 42001, NIST AI RMF)
Two free trial lengths: 7-day standard, 14-day enterprise
Drata
Fixed annual price regardless of headcount growth, per Drata’s own page
Every plan includes a dedicated Customer Success Manager and auditor-staffed live chat
Longest clearly stated free trial (21 days, no credit card)
Works with any audit firm, plus a discounted “Alliance” partner network
Secureframe
Only vendor of the three with a real published starting price ($7,500/year)
Dedicated Defense tier for CMMC 2.0, including SPRS tracking and POA&M support
AI-assisted policy drafting (“Comply AI”) from the entry tier
Cons
Vanta
Zero published pricing; every tier requires a sales call
Questionnaire automation is capped by tier (25/year at Plus, 144/year at Professional)
The pricing page’s comparison table referenced a “Pro” tier that didn’t match the named plans — worth double-checking with sales
Drata
Zero published pricing; tier names (“Startup,” “Growth”) give little sense of actual cost
Its public pages say less about specific evidence-collection mechanics than Vanta’s or Secureframe’s do
No stated usage caps on the trial page, so it’s unclear what’s restricted during the 21 days
Secureframe
The $7,500/year price is only a starting point — Fundamentals caps AI questionnaire responses at 100/year, and larger or multi-framework teams will likely need a Complete or Defense quote
No free trial length or terms are stated publicly
Advanced third-party risk management and SSO/SCIM are gated behind Complete, not included at the entry price
Who It’s a Good Fit For — and Who Should Look Elsewhere
Early-stage startup doing a first SOC 2: Secureframe’s published $7,500/year starting price makes it the easiest to evaluate before a sales call, and its feature list covers what a first SOC 2 typically needs. Vanta’s 7-day trial is also a low-commitment way to test integration fit before negotiating. Startups with heavy vendor-questionnaire volume should ask about each platform’s response caps, since all three gate that feature by tier.
Larger company managing multiple frameworks: All three claim multi-framework support with shared-control mapping, so the deciding factors become integration coverage for your stack, AI-governance framework needs (Vanta’s stated strength), CMMC 2.0 (Secureframe’s dedicated Defense tier), and how much you value a fixed annual price as headcount grows (Drata’s explicit pitch).
Who should look elsewhere: Teams that need a firm number before any internal budget conversation can start will be frustrated by Vanta and Drata’s quote-only model — get quotes from all three in parallel rather than negotiating with one in isolation. Teams with low tolerance for sales-cycle friction might start with Secureframe, the only one willing to put a number on a webpage.
Bottom Line
Functionally, Vanta, Drata, and Secureframe are close enough — continuous monitoring, automated evidence collection, policy templates, and auditor-facing access — that the decision tends to turn on contract terms, integration fit, and framework specialization rather than core capability. Get live quotes from at least two before committing, use the free trials to sanity-check integrations, and lean toward Secureframe if a public price anchor matters, Drata if a fixed annual price regardless of growth matters more, and Vanta if AI-governance framework coverage or integration breadth is the priority.
FAQ
Do any of these platforms publish real prices?
Only partly. Secureframe lists a starting price of $7,500/year for its entry Fundamentals tier; Complete and Defense are quote-only. Vanta and Drata publish no prices at all — every tier routes to a sales form.
Which tool offers the longest free trial?
Drata’s trial page confirms 21 days, no credit card required. Vanta offers 7 days (14 for its enterprise track). Secureframe has a trial sign-up page but doesn’t state the length or terms.
Do all three support both SOC 2 and ISO 27001?
Yes. All three explicitly list SOC 2 and ISO 27001 support on their official pricing or marketing pages, alongside HIPAA and GDPR.
Which platform is best for a company that needs CMMC 2.0?
Only Secureframe advertises a dedicated tier (Defense) built around CMMC 2.0, including an SPRS score tracker, System Security Plan support, and POA&M tooling. Vanta’s and Drata’s pages reviewed here don’t specify CMMC support.
Does the vendor or the customer pay the SOC 2 auditor?
Drata’s pricing page states audit fees go directly to the audit firm, not Drata, whether you use its “Alliance” partner network or your own auditor. Vanta and Secureframe reference auditor access tools (an Auditor API, an Audit Partner Network) but don’t spell out billing as explicitly.
Hardcoded API keys in a Git repo. A database password in a plaintext .env file on three laptops. A rotation policy that exists only as a Slack reminder nobody acts on. These are the everyday failures secrets management platforms exist to fix, and by 2026 picking one is a baseline requirement, not a nice-to-have. This guide compares three common choices: HashiCorp Vault (now under IBM’s banner), AWS Secrets Manager, and Doppler.
At a Glance
Tool
Pricing Model
Deployment
Best For
HashiCorp Vault (IBM)
Free open-source edition; consumption-based or custom-quoted paid tiers
Self-hosted (Community/Enterprise) or cloud-managed SaaS (HCP Vault Dedicated)
Large or regulated orgs needing dynamic secrets, PKI, and deep policy control
AWS Secrets Manager
Pay-as-you-go: per secret per month + per API call
Fully managed cloud service (AWS only)
Teams already running on AWS who want native IAM-integrated secrets
Doppler
Per-seat subscription, with a free tier for small teams
Managed SaaS; on-prem/cloud choice on Enterprise
Small-to-midsize dev teams wanting fast setup across any cloud or stack
Short Verdict
Doppler is the fastest path to decent secrets hygiene for small and mid-sized teams, with transparent per-seat pricing and almost no infrastructure to manage. AWS Secrets Manager makes sense by default if your workloads already live on AWS and you want secrets tied directly into IAM. HashiCorp Vault (now part of IBM) is the deepest and most flexible option — free to self-host at the Community tier — but it demands real operational investment, and its paid Enterprise and cloud tiers are priced through consumption billing or custom quotes rather than a simple public price list.
What It Is: Why Secrets Management Matters
“Secrets” is the industry term for anything an application needs to authenticate or encrypt but shouldn’t be visible in source code: API keys, database credentials, TLS certificates, OAuth tokens, SSH keys, and encryption keys. A secrets management platform centralizes how those values are stored, distributed, rotated, and audited, replacing credentials scattered across config files, forgotten CI/CD environment variables, or shared spreadsheets. Three capabilities separate a real secrets manager from “a vault we built ourselves with environment variables”:
Centralized storage with access control — secrets are encrypted at rest and released only to authenticated services or people, instead of being copy-pasted between files.
Rotation — credentials can be regenerated on a schedule or on demand without a manual scramble across every service that uses them.
Audit trails — every read, write, and rotation is logged, which matters for incident response and for compliance frameworks like SOC 2 or ISO 27001.
Hardcoded credentials remain one of the most common root causes behind credential-leak incidents, which is the practical reason this category exists at all.
Pricing Breakdown
HashiCorp Vault (an IBM company)
HashiCorp was acquired by IBM in a deal reported at $6.4 billion, and Vault is now marketed and priced under the “HashiCorp, an IBM Company” brand. Vault ships in several editions with very different cost structures:
Vault Community Edition — free and self-managed; you run and operate it yourself. It lacks namespaces, HSM auto-unseal, SAML, secrets import/sync, Sentinel policies, and replication, which are reserved for Enterprise.
Vault Enterprise — self-managed or operated for you via HCP; adds the features above plus disaster-recovery replication and secrets sync to other clouds. IBM does not publish a flat rate for Enterprise; it’s sold through “Flex” multi-year plans or “Enterprise Self Managed” contracts that require contacting sales.
HCP Vault Dedicated — a fully managed SaaS cluster on the HashiCorp Cloud Platform. IBM’s published pay-as-you-go rate card lists hourly cluster pricing starting around $0.62/hour for an extra-small dev cluster, scaling up through small (~$1.58–$1.84/hour), medium (~$3.16–$3.69/hour), and large (~$7.49–$9.41/hour) depending on the Essentials or Standard tier. New accounts get a $500 trial credit.
Vault Radar (secret-sprawl scanning add-on) — $7 per active user/month on the Essentials tier.
Because Enterprise and Flex pricing is quote-based, exact costs vary by negotiated contract — treat the cluster rates above as the clearest public reference point rather than a full enterprise price.
AWS Secrets Manager
AWS prices Secrets Manager purely on consumption, per its official pricing page:
$0.40 per secret, per month (prorated for secrets stored less than a full month).
$0.05 per 10,000 API calls (reads, writes, lists, etc.).
No charge for creating a new secret version through automatic rotation.
No Secrets-Manager-specific free trial; new AWS accounts can apply the general AWS Free Tier credit (up to $200, usable within a 6-month window as of this writing) toward it, but there’s no standing free allotment for the service itself.
There are no separate “plans” — cost scales directly with secret count and API call volume, which is predictable for small secret counts but worth modeling at high call volumes (e.g., many short-lived Lambda invocations each fetching a secret).
Doppler
Doppler uses straightforward per-seat subscription pricing, per its official pricing page:
Developer plan — free for up to 3 users, then $8/month per additional user, up to 25 users. Includes 10 projects, 4 environments, 10 configs per environment, and CLI/API/webhook access.
Team plan — $21/month per user (14-day free trial), up to 500 users. Adds SSO, RBAC, automatic secret rotation, service accounts, and 90 days of activity log retention. Add-ons like custom roles, user groups, and higher integration-sync limits run an additional $9/seat/month.
Enterprise plan — custom pricing, with on-prem or cloud deployment, SCIM, Enterprise Key Management, dynamic secrets, custom SLAs, and dedicated support.
Doppler’s own positioning line is notable for cost planning: “AI agents and non-human identities ride free” — seats are billed for human users, not every service account or bot that reads a secret.
Quick Look: Retrieving a Secret
The three platforms differ most in how a running application actually fetches a secret at runtime. Here’s the equivalent one-line CLI call for each:
# HashiCorp Vault - read a KV v2 secret
vault kv get -field=password secret/myapp/db
# AWS Secrets Manager - get a secret value via the AWS CLI
aws secretsmanager get-secret-value --secret-id prod/myapp/db --query SecretString --output text
# Doppler - fetch a single secret for the current project/config
doppler secrets get DB_PASSWORD --plain
Pros
HashiCorp Vault
Dynamic, short-lived secrets (databases, cloud credentials) that are generated on demand and expire automatically
Fine-grained policy engine and broad plugin ecosystem (PKI, transit encryption, SSH, Kubernetes auth, and more)
Free, open-source, self-hosted Community Edition with no vendor lock-in for the core product
Cloud-managed HCP Vault Dedicated option removes most operational overhead if you don’t want to self-host
AWS Secrets Manager
Native integration with IAM, Lambda, RDS, and the rest of the AWS ecosystem
Zero infrastructure to run or patch — fully managed by AWS
Built-in automatic rotation for RDS, Redshift, and DocumentDB credentials
Simple, predictable consumption-based pricing with no seat counting
Doppler
Fastest setup of the three — a developer can be syncing secrets into a project within minutes
Cloud-agnostic: works the same way whether you deploy to AWS, GCP, Vercel, Kubernetes, or a laptop
Clean CLI and dashboard UX built specifically for developer workflows, including config inheritance across environments
Free tier is genuinely usable for small teams, not just a trial
Cons
HashiCorp Vault
Self-hosted Community Edition requires real operational work: unsealing, storage backend choice, upgrades, and HA configuration
Enterprise and Flex pricing isn’t public — budgeting requires a sales conversation
Steeper learning curve than the other two options, especially around policies and auth methods
Post-acquisition branding and roadmap now run through IBM, which some teams will want to watch for pricing or support changes
AWS Secrets Manager
AWS-only — there’s no multi-cloud story if part of your stack lives outside AWS
Per-API-call billing can add up quickly for chatty services that fetch secrets frequently instead of caching them
No dedicated developer-facing UI for day-to-day secret editing beyond the AWS console/CLI
Lacks Vault-style dynamic, auto-expiring credentials outside of its specific database rotation integrations
Doppler
Per-seat pricing can scale faster than expected as a team grows past the free or Developer tier
Less depth than Vault for advanced use cases like PKI issuance or transit encryption-as-a-service
As a third-party SaaS, it adds an external dependency and vendor relationship that self-hosted Vault avoids
Who It’s a Good Fit For / Who Should Look Elsewhere
Choose HashiCorp Vault if you need dynamic secrets, PKI, or encryption-as-a-service, run multi-cloud or hybrid infrastructure, and have a platform team that can own the operational cost — but look elsewhere if you have no infra engineer to run it and don’t want to negotiate Enterprise pricing.
Choose AWS Secrets Manager if your workloads are AWS-native and you want access governed entirely through IAM — but look elsewhere if your stack spans multiple clouds, or if per-call billing is hard to forecast for your traffic pattern.
Choose Doppler if you’re a small-to-midsize team wanting secrets synced across local dev, CI, and multiple clouds with minimal setup — but look elsewhere if you’re strictly AWS-only with no multi-cloud ambitions, where Secrets Manager’s native fit is simpler.
Bottom Line
There isn’t a single “best” secrets manager in 2026 — there’s a best fit for your stack and team size. AWS Secrets Manager wins on simplicity if you’re all-in on AWS. Doppler wins on developer experience and transparent per-seat pricing for multi-cloud teams. HashiCorp Vault, now under IBM, remains the most capable option for complex, regulated environments — provided you can run it yourself for free or pay for the managed, consumption-priced version.
FAQ
Is HashiCorp Vault still independent, or is it an IBM product now?
IBM completed its acquisition of HashiCorp, and Vault is now marketed under the “HashiCorp, an IBM Company” brand, with its cloud pricing published on IBM’s own pricing pages alongside other IBM/HashiCorp products.
Is HashiCorp Vault free to use?
Vault Community Edition is free and self-hosted, but it lacks several features reserved for Vault Enterprise (namespaces, SAML, replication, and more). Enterprise and the managed HCP Vault Dedicated SaaS option are paid, with Enterprise priced through custom contracts rather than a public rate card.
How does AWS Secrets Manager pricing actually work?
You pay $0.40 per secret per month plus $0.05 per 10,000 API calls, with no separate subscription tiers. There’s no dedicated free allotment for the service, though new AWS accounts can apply general AWS Free Tier credits toward it.
Can small teams use Doppler for free?
Yes. Doppler’s Developer plan is free for up to 3 users, with paid seats at $8/month per additional user up to 25 users on that tier. Larger teams needing SSO and RBAC move to the Team plan at $21/user/month.
Which tool is best for a multi-cloud setup?
Doppler and HashiCorp Vault both work across clouds; AWS Secrets Manager is tied to AWS. Doppler is generally the faster setup for multi-cloud teams, while Vault offers deeper control if you need dynamic, short-lived credentials across multiple providers.
Affiliate and partnership software has split into two camps. On one side are platforms built for B2B SaaS companies running affiliate, reseller, and referral programs side by side, with partner payouts routed through finance workflows. On the other are platforms built for e-commerce brands that need to track clicks and coupon codes and pay creators and affiliates on a schedule. PartnerStack, Impact.com, and Tapfiliate sit across that split, and their pricing pages tell you almost as much about who they’re built for as their feature lists do. Here’s what each one actually publishes about price, payouts, and tracking, sourced from their own pricing and documentation pages.
At a Glance
Tool
Price / Quote Model
Starting Price
Free Trial
Best For
PartnerStack
Fully quote-based; no published pricing on any of its three tiers
Custom, confirmed during a demo
Gated — “exclusively available for qualified companies and programs”
B2B SaaS companies building affiliate, reseller, and referral partner ecosystems
Impact.com
Published starting prices for ecommerce tiers; Enterprise is quote-based
From $30/mo + 2.5% of revenue
None stated on the pricing page
E-commerce brands scaling multi-channel partnerships, with custom plans for larger or non-ecommerce programs
Tapfiliate
Published tiered self-serve pricing; Enterprise is quote-based
From $89/mo ($74/mo billed annually)
14 days on every tier
Small businesses wanting a simple, self-serve affiliate program
Short Verdict
PartnerStack and Impact.com’s upper tiers are both built around a sales conversation rather than a price list, and that’s by design — they’re selling partner-program infrastructure, not a self-serve tool. Tapfiliate is the exception: it publishes exact monthly prices and a 14-day trial you can start without talking to anyone, though its entry tier caps you at 50 affiliates and 5,000 monthly clicks. If you’re a SaaS company building out affiliate, reseller, and referral motions together, PartnerStack’s payout and commission automation is purpose-built for that; if you’re an e-commerce brand, Impact.com’s published starter tiers scale with your revenue; and if you just want a working affiliate program this week without an enterprise sales cycle, Tapfiliate is the practical pick.
What These Tools Are
All three fall into the same software category: partnership and affiliate tracking platforms. They give you a way to recruit partners or affiliates, generate trackable links or codes, record clicks and conversions, calculate commissions, and get partners paid — usually through a partner-facing portal where affiliates can see their own stats and balance.
PartnerStack is positioned specifically for B2B SaaS companies and sells three plans — Launch, Growth, and Enterprise — each adding more workflow depth (CRM integrations and partner payments on Launch; MDF management, partner incentives, and a learning management system on Growth; custom workflows and a dedicated CSM on Enterprise). None of the three list a price.
Impact.com runs a broader “partnership cloud” covering affiliate, creator, and referral partnerships. Its public pricing page is aimed at e-commerce brands, with tiers sized by annual revenue and a cap on monthly partner payouts per tier. Larger programs, and presumably most SaaS partnership deals, move to a custom Enterprise quote.
Tapfiliate is the simplest of the three to evaluate: two published self-serve tiers (Launch and Scale) plus a custom Enterprise tier, all billed monthly or annually, with hard limits on affiliates, clicks, and conversions that scale up as you pay more.
Pricing Breakdown
PartnerStack publishes no dollar figures at all. Its pricing page states plainly that cost “is based on your partner program size, feature needs and level of support,” and that you confirm final pricing during a demo — you don’t even need to pick a plan before booking one. A free trial exists, but it’s gated behind qualification rather than open self-serve signup.
Impact.com’s published ecommerce pricing runs: Starter at $30/month plus 2.5% of revenue (for brands spending under $300k/year on marketing, limited to specific platforms like Shopify, WooCommerce, BigCommerce, and Squarespace, no add-ons); Essentials at $500/month, including up to $2,500/month in partner payouts (with a $2,500/month minimum in processed payouts), aimed at brands up to $2M/year in ecommerce revenue; Pro at $2,500/month, including up to $14,300/month in payouts, for the $2M–$15M/year range; and Enterprise, custom-quoted, for brands above $15M/year or running multi-channel programs. Add-ons such as Creator Premium, Advocate Premium, and Optimize are available from Essentials up, with availability varying by tier. The page doesn’t mention a free trial.
Tapfiliate’s pricing is the most transparent of the three. Launch is $89/month ($74/month billed annually) for one program, 50 affiliates, one team seat, and 5,000 clicks/500 conversions monthly, with overage billed at $1.50 per 1,000 extra clicks and $15 per 1,000 extra conversions. Scale is $179/month ($149/month annually, and marked “Most popular”) for unlimited programs, 150 affiliates, five seats, 100,000 clicks/10,000 conversions monthly, automated payouts, and multi-level marketing support, with lower overage rates. Enterprise is custom-quoted, adding unlimited affiliates and seats, tailored volume limits, full white-labeling, and a dedicated account manager. Every tier gets a 14-day free trial, and Tapfiliate states that billing starts automatically once the trial ends unless you cancel first.
Partner and Affiliate Payout Automation
PartnerStack consolidates partner commissions into a single monthly invoice, paid in the partner’s preferred method and currency. Partners withdraw via direct deposit, PayPal, or Stripe; brands fund payouts in USD or EUR while partners can still receive local currency. It supports flat-rate, percentage, milestone, DRIP (installment), and multi-step revenue-share commission structures, with fraud screening that flags and blocks suspicious rewards until disputed.
Impact.com schedules partner payouts rather than processing them manually: partners choose either a balance threshold (minimum $10 USD or local equivalent) or a fixed day of the month, and funds go out to a bank account or PayPal. US-based partners (or those working with US brands) must file a tax document once yearly earnings pass $2,000, and bank-detail changes trigger a 48-hour withdrawal pause.
Tapfiliate offers “automated affiliate payouts” starting on its Scale plan and supports the widest range of named payout methods of the three: PayPal, Payoneer, Venmo, Skrill, Neteller, PayQuicker, MercadoPago, Webmoney, check, ACH, several regional bank-transfer formats, and even crypto (Bitcoin, Ether, Litecoin, Stellar), plus custom payout methods for anything not on that list.
Tracking Methods
PartnerStack defaults to first-party cookie tracking with a 90-day attribution window from the initial click (resettable on a repeat click), and the referral must convert on the same browser and device as the original click. It also offers server-to-server (S2S) tracking, which generates a Click ID on PartnerStack’s own server and has the advertiser’s server confirm conversions directly — avoiding the ad-blocker and cookie-clearing issues that front-end snippet trackers face.
Impact.com lists four core tracking methods: pixel/cookie tracking (its standard method, with a custom tracking domain to work around Safari’s Intelligent Tracking Prevention); API tracking, a cookieless server-to-server method it calls “the recommended solution for brands” and fully ITP-compliant; FTP tracking, where conversion data is matched via ClickID through batch file uploads; and CPC tracking for cost-per-click programs. A modified pixel method also powers its Shopify connector.
Tapfiliate supports cookie-based tracking with an adjustable window (one day up to lifetime), server-to-server/postback tracking for cookieless setups (recommended for mobile apps and subscriptions), coupon-code attribution for influencer and offline campaigns, and custom metadata capture — set up via a JavaScript snippet, native integrations, or its REST API.
Pros
PartnerStack: Purpose-built for B2B SaaS partner ecosystems; consolidated monthly payouts with flexible commission structures (flat, percentage, milestone, DRIP, revenue share); fraud screening built into the payout flow; both cookie and S2S tracking available.
Impact.com: Actually publishes starting prices and payout caps for its ecommerce tiers, unlike PartnerStack; four distinct tracking methods including a cookieless API option it recommends as the default; scheduled, self-service partner withdrawals.
Tapfiliate: Fully transparent, self-serve pricing with a real 14-day trial and no sales call required; by far the widest list of named affiliate payout methods, including crypto; flexible tracking setup via snippet, native integrations, or API.
Cons
PartnerStack: Zero published pricing on any tier; the free trial is gated to “qualified” companies rather than open to everyone; you can’t budget or compare cost without a sales conversation.
Impact.com: No free trial listed; the published tiers are explicitly sized for ecommerce revenue, so SaaS companies or larger programs land on a custom Enterprise quote anyway; Starter tier is locked to a short list of ecommerce platforms with no add-ons.
Tapfiliate: Entry tier caps out at 50 affiliates and one team member, with per-unit overage fees once you exceed click/conversion limits; its multi-program and MLM features only unlock on the pricier Scale plan; Enterprise pricing is still a custom quote.
Who It’s a Good Fit For
PartnerStack fits a SaaS company that wants to run affiliate, reseller, and referral partnerships together under one roof, with finance-friendly consolidated payouts and a partner marketplace for discovery — and that’s comfortable going through a demo and sales process to get pricing. Impact.com fits an e-commerce brand that wants published starting prices tied to its own revenue tier, plus a choice of tracking methods including a cookieless option built for a post-ITP world; it also scales up to large, multi-channel programs once you move to its custom Enterprise tier. Tapfiliate fits a small business or solo-run brand that wants to launch a basic affiliate program this week, know the monthly cost upfront, and test it for two weeks before paying a cent.
Who Should Look Elsewhere
A small business that wants an exact price before signing up should skip PartnerStack, since nothing is published and the trial itself requires qualifying first. A SaaS company evaluating Impact.com purely from its public pricing page should be aware that page is built for ecommerce revenue brackets, not partner-led SaaS growth — expect a custom conversation instead. And a fast-growing program that’s about to blow past 150 affiliates or 100,000 monthly clicks should budget for Tapfiliate’s overage fees or its custom Enterprise tier rather than assume the published Scale price is the ceiling.
Bottom Line
None of these three is strictly “better” — they’re built for different buyers. PartnerStack’s quote-only model buys you B2B SaaS-specific partner tooling and consolidated finance workflows, but you’ll need a sales call to know the cost. Impact.com splits the difference, publishing real starting prices for ecommerce brands while reserving custom quotes for Enterprise and larger programs. Tapfiliate is the only one of the three you can price and trial without talking to a salesperson, which makes it the right starting point for a small business, and the one to outgrow once your affiliate count or traffic volume climbs.
FAQ
Is PartnerStack pricing published anywhere? No. PartnerStack’s pricing page states that cost depends on your partner program size, feature needs, and support level, and is confirmed during a demo — none of its three plans (Launch, Growth, Enterprise) list a price.
Does Impact.com have a free trial? Impact.com’s published ecommerce pricing page doesn’t describe a free trial or free tier for any of its Starter, Essentials, Pro, or Enterprise plans.
What’s the cheapest way to start with Tapfiliate? The Launch plan is $89/month billed monthly, or $74/month if billed annually, and includes a 14-day free trial before billing starts.
Which of the three supports cookieless, server-to-server tracking? All three do. PartnerStack and Tapfiliate both offer S2S/postback tracking alongside cookie-based tracking, and Impact.com calls its API-based server-to-server method “the recommended solution for brands” because it’s fully compliant with Safari’s Intelligent Tracking Prevention.
Can affiliates get paid in cryptocurrency on any of these platforms? Of the three, only Tapfiliate lists crypto payout methods by name — Bitcoin, Ether, Litecoin, and Stellar (XLM) — alongside more conventional methods like PayPal, Payoneer, and bank transfer.
Infrastructure-as-code (IaC) tooling had a genuinely disruptive few years. In August 2023, HashiCorp moved Terraform away from its open-source Mozilla Public License to the Business Source License (BUSL 1.1), a change aimed at commercial competitors reselling Terraform as a service. The community response was immediate: within weeks, a group of vendors and contributors forked the last MPL-licensed release into what became OpenTofu, now governed by the Linux Foundation. Meanwhile Pulumi, which predates the fork entirely, has spent the same years making the case that infrastructure code is better written in TypeScript, Python, Go, C#, or Java rather than a domain-specific language. This piece compares all three on license, syntax, pricing, and fit — using only what HashiCorp, the OpenTofu project, and Pulumi themselves publish.
At a Glance
Tool
License
Language / Syntax
Best For
Terraform
Business Source License (BUSL 1.1) since August 2023; maintained by HashiCorp, now owned by IBM
HCL (HashiCorp Configuration Language), with a JSON variant
Teams already standardized on HCL and HCP Terraform who aren’t building a competing commercial IaC product
Pulumi
Apache 2.0 for the core CLI/SDKs (open source); Pulumi Cloud is a separate commercial SaaS
General-purpose languages: TypeScript, JavaScript, Python, Go, C#, Java, or YAML
Developers who want real programming constructs (loops, functions, tests, IDE support) instead of a DSL
OpenTofu
Mozilla Public License 2.0 (MPL-2.0), fully open source, governed under the Linux Foundation
HCL — a largely drop-in fork of Terraform’s syntax
Teams that want Terraform-compatible configuration without BUSL licensing terms or vendor lock to one company
Short Verdict
Terraform remains the most widely documented and integrated option, but it now carries a license that restricts building competing commercial offerings on top of it and ties day-to-day pricing decisions to IBM. OpenTofu is the right default if your main objection is the license — it’s a community-governed, MPL-2.0 fork that reuses Terraform’s own HCL syntax and most existing configurations. Pulumi is the right pick if you’d rather write infrastructure in a language your application developers already use, and are willing to pay for its usage-based cloud backend once you outgrow the free tier.
What It Is: Infrastructure as Code, and Why Three Tools Exist
Infrastructure as code means describing servers, networks, databases, and other cloud resources in version-controlled configuration files instead of clicking through a console. A tool reads that configuration, compares it against the real state of your cloud accounts, and calculates a plan of changes — create, update, or destroy — to reconcile the two. Terraform popularized this declarative, provider-plugin model across hundreds of cloud and SaaS APIs and became the de facto standard for multi-cloud provisioning.
That dominance is exactly why the 2023 license change mattered so much: an enormous ecosystem of modules, CI/CD integrations, and internal tooling was built assuming Terraform would stay under a permissive open-source license. OpenTofu exists specifically to preserve that assumption. Pulumi, in contrast, was built from the start on a different premise — that the declarative “plan and apply” model is right, but the configuration language shouldn’t be a bespoke DSL when a general-purpose language already has loops, types, package managers, and testing frameworks.
Pricing and Licensing Breakdown
Terraform / HCP Terraform. The core Terraform CLI is source-available under BUSL 1.1: you can read, modify, and self-host it, but the license bars using it to build a product that competes with HashiCorp’s (now IBM’s) own commercial offerings. HashiCorp’s HCP Terraform (formerly Terraform Cloud) documentation lists a Free plan with no charge for up to 500 managed resources, unlimited team members, and one concurrent run, but without team-based RBAC, cost estimation, or audit logging. Paid tiers move to pay-as-you-go pricing per resource under management: IBM’s published Terraform pricing lists Essentials at $0.00013 per resource-hour, Standard at $0.00064 per resource-hour, and Premium at $0.00135 per resource-hour, with Standard and Premium priced further by quote for extra concurrency. IBM completed its $6.4 billion acquisition of HashiCorp in 2025, so Terraform’s commercial roadmap and pricing now sit inside IBM’s hybrid-cloud business.
OpenTofu. OpenTofu is released under MPL-2.0, the same permissive open-source license Terraform used before the BUSL change, with no usage restrictions on competing products. The project forked the last MPL-licensed Terraform codebase in September 2023 (first as “OpenTF,” then renamed OpenTofu), joined the Linux Foundation, and reached its first stable 1.0 release on January 10, 2024, after contributions from more than five dozen developers. There’s no separate commercial product to price: the CLI is free, and hosting your own state backend, runner, or CI pipeline is up to you or a third-party provider.
Pulumi. Pulumi’s CLI and language SDKs are Apache 2.0 and free to self-host against your own state backend. Its hosted Pulumi Cloud backend has a published tiered structure: Free ($0, one user, basic state management and ESC, up to 500 workflow minutes/month), Essentials ($40/month including 40 credits and up to 500 managed resources, unlimited users, SSO-adjacent collaboration features), Pro ($400/month including 400 credits and up to 2,000 managed resources, adding SAML/SSO, RBAC, and policy enforcement), and a custom-quoted Enterprise tier adding self-hosting and compliance packs (CIS, ISO 27001, PCI DSS, among others). Beyond the included credits, Pulumi bills usage per managed resource-hour (from $0.0005/hour on Pro) and per workflow-minute.
Pros
Terraform: the largest provider and module ecosystem, the most third-party tutorials and Stack Overflow answers, and broad CI/CD and SaaS integration support built up over a decade.
OpenTofu: MPL-2.0 licensing with no usage restrictions, strong compatibility with existing Terraform configurations and state files, and vendor-neutral governance under the Linux Foundation rather than a single company.
Pulumi: infrastructure defined in a real programming language, so you get IDE autocomplete, unit testing, loops/conditionals without a DSL’s limitations, and easy sharing of logic as ordinary packages.
Cons
Terraform: the BUSL license creates real legal uncertainty for vendors and consultancies building competing products, and commercial roadmap decisions now run through IBM.
OpenTofu: younger project history than Terraform itself, and some newer HashiCorp-side provider features or HCP integrations may lag or never arrive.
Pulumi: the free tier’s resource and workflow-minute limits are modest, and costs scale with both managed resources and workflow minutes as usage grows, so bills can be less predictable than a flat seat price.
Who It’s a Good Fit For / Who Should Look Elsewhere
Terraform fits teams already deep in the HashiCorp/IBM ecosystem (Vault, Consul, HCP) who have reviewed the BUSL terms with their own legal counsel and aren’t building a product that competes with HCP Terraform. It’s a poor fit for vendors building a commercial IaC platform, or teams that want governance decisions made outside a single vendor.
OpenTofu fits teams that like Terraform’s HCL model and existing module library but want a permissively licensed, community-governed path forward — including anyone who was uneasy about the 2023 license change specifically. It’s a weaker fit if you need a feature that’s only shipping in HashiCorp’s newest proprietary tooling first.
Pulumi fits engineering organizations where application developers also own infrastructure and would rather not learn a dedicated DSL, or teams that want unit tests around their infrastructure logic. It’s a weaker fit for teams that specifically want to avoid a usage-metered SaaS backend, or that have large existing Terraform/HCL investments they don’t want to rewrite.
A Minimal Example
To show how close OpenTofu’s syntax stays to Terraform’s, here is a minimal HCL resource block as documented by HashiCorp — valid, unmodified, in both Terraform and OpenTofu:
The two quoted labels are the resource type (defined by the provider) and a local name used elsewhere in the configuration, such as in aws_instance.web. Because OpenTofu forked Terraform’s codebase directly, blocks like this one typically run unchanged after switching the binary.
Bottom Line
There is no longer a single obvious default IaC tool. Terraform still has the deepest ecosystem, but its license and its new ownership under IBM are factors every team now has to weigh deliberately rather than assume away. OpenTofu removes the licensing question entirely while staying close enough to Terraform that migration is usually mechanical. Pulumi solves a different problem — DSL fatigue — by letting you write infrastructure in languages your team already knows, at the cost of a metered cloud backend once you scale past its free tier. Pick based on which trade-off (license risk, migration effort, or language preference) matters most for your organization.
FAQ
Why did OpenTofu get forked from Terraform? HashiCorp announced in August 2023 that Terraform and its other core products would move from the open-source Mozilla Public License to the Business Source License (BUSL 1.1), restricting use by companies that compete with HashiCorp’s commercial offerings. A group of contributors and vendors responded by forking the last MPL-licensed Terraform release, first as “OpenTF” and then renamed OpenTofu, and brought the project under the Linux Foundation to keep it vendor-neutral.
Is OpenTofu a drop-in replacement for Terraform? For most existing Terraform configurations and state files, yes — OpenTofu forked Terraform’s codebase directly and aims for compatibility. Always test provider versions and any newer HashiCorp-only features before migrating a production workspace.
Does Pulumi require using its hosted cloud service? No. Pulumi’s CLI and SDKs are Apache 2.0 and open source, and you can configure a self-managed state backend instead of Pulumi Cloud. The hosted Pulumi Cloud backend, with its Free, Essentials, Pro, and Enterprise tiers, is optional but is where most of Pulumi’s collaboration, policy, and CI/CD features live.
Who owns Terraform now? HashiCorp, Terraform’s original creator, completed a $6.4 billion acquisition by IBM in 2025. Terraform and HCP Terraform are now part of IBM’s hybrid-cloud product line.
Can I use Terraform for free? Yes, within limits. The Terraform CLI itself is free to download and run under BUSL 1.1 (subject to its usage restrictions), and HashiCorp’s HCP Terraform documentation lists a free plan covering up to 500 managed resources with unlimited team members, though without team-based RBAC, cost estimation, or audit logging.
Every programmatic media buy runs through a demand-side platform (DSP), but the three biggest general-purpose DSPs — The Trade Desk, Google Display & Video 360 (DV360), and Amazon DSP — are not interchangeable. They differ in who is allowed to log in and run campaigns, how (and whether) pricing is public, what inventory sits behind the buy button, and how they identify a browser or device without relying on a third-party cookie. This guide compares the three on those terms specifically for general-purpose demand-side buying, not retail media networks — Amazon Ads, Walmart Connect, and Instacart Ads as on-site retail media placements are covered in a separate article on this site.
At a Glance
Platform
Access Model
Minimum Spend / Fees
Best For
The Trade Desk
Self-serve platform; no public signup page, onboarding is via a sales contact
No published minimum; pricing is quoted per account
Agencies and brands with an in-house trading desk buying the open internet and CTV at scale
Google DV360
Enterprise platform; new accounts are opened by “talking to sales” or through a certified Google Marketing Platform partner/reseller
No published minimum or fee schedule
Advertisers already standardized on Google Marketing Platform / Google Analytics who want tight YouTube and Google-ecosystem integration
Amazon DSP
Both self-service (direct account control) and managed-service (Amazon account executive manages it for you)
Self-service: no management fee disclosed. Managed service: “typically requires a minimum spend of $50,000 USD,” varying by country
Advertisers who want Amazon shopping/streaming signals and are comfortable with Amazon-run audiences, with or without selling on Amazon
Short Verdict
The Trade Desk is the best fit for a brand or agency that wants to run its own independent trading desk across the open web and CTV without being tied to one walled garden’s data. DV360 is the natural choice if your stack is already Google-centric and YouTube is a priority channel. Amazon DSP is the right tool specifically when Amazon’s shopping and streaming signals matter to your targeting — but budget for either hands-on self-service work or Amazon’s disclosed $50,000 managed-service minimum.
What a DSP Is, and Why These Three
A demand-side platform lets an advertiser buy ad impressions programmatically — in real time, across many publishers and exchanges at once — instead of negotiating with each publisher directly. The three platforms here are “general-purpose” DSPs: they’re built to buy a wide range of inventory (display, video, audio, CTV) across many sellers, as opposed to retail media networks, which exist mainly to sell inventory inside one retailer’s own app, site, or streaming surface. The Trade Desk is an independent company with no media or exchange of its own; it says explicitly that it does not own or operate media. DV360 is part of Google Marketing Platform. Amazon DSP sits inside Amazon Advertising and, notably, can be used by advertisers whether or not they sell products on Amazon.
How Each Platform’s Access and Pricing Model Works
The Trade Desk. The Trade Desk markets itself as offering “a simple self-serve experience” for planning, executing, and measuring campaigns, and says it is trusted by “the world’s biggest brands and agencies.” There is no public self-signup form and no published price list or minimum spend on its own site; prospective advertisers are routed to a contact form, and pricing is evidently negotiated per account. In practice, most advertisers reach The Trade Desk either as an agency’s dedicated trading desk or as a brand-side team that has built (or hired) the programmatic expertise to run self-serve campaigns directly.
Google DV360. DV360 is positioned on Google’s own marketing site as an enterprise tool for “end-to-end campaign management,” and its help center tells new advertisers to “talk to our sales team to get started with a new Display & Video 360 account” — there is no visible self-serve signup flow comparable to, say, Google Ads. Google also operates a certified-partner/reseller program for Google Marketing Platform products, through which many mid-sized advertisers get managed access rather than a direct Google sales relationship; Google’s own terms restrict reselling DV360 access outside of an approved arrangement. No minimum spend figure is published by Google for DV360.
Amazon DSP. Amazon is the one platform of the three that publishes a concrete number. Amazon Ads documentation states that Amazon DSP comes in two forms: self-service, where the advertiser has “full control of your campaigns” with no stated management fee, and managed service, which “typically requires a minimum spend of $50,000 USD” (with the exact figure varying by country) and is run by an Amazon Ads account executive on the advertiser’s behalf. Either option is open to brand advertisers, ad agencies, and tool providers — Amazon is explicit that you do not need to sell on Amazon to use its DSP.
Inventory Access
The Trade Desk buys across the open internet: display, native, audio, video, digital out-of-home, and — increasingly central to its pitch — Connected TV/OTT, where it says it partners with major ad-supported streaming services globally rather than owning any of that inventory itself. It also runs OpenPath, a way for publishers to offer inventory directly into the platform. DV360 buys YouTube inventory (including Google Preferred and YouTube Reserve placements) directly, plus what Google’s own marketing page describes as “dozens of third-party exchanges” for display, video, and audio across the open web; Google’s help documentation groups that inventory into public auction/sub-exchange inventory, app-mediation inventory, and private deals, without naming every exchange involved. Amazon DSP’s inventory is split between Amazon’s own first-party properties — Prime Video, Twitch, Freevee, Fire TV, Kindle, Alexa, Amazon.com, and in some markets Thursday Night Football and Amazon Fresh kiosk screens — and third-party sites and apps reached through Amazon Publisher Direct and third-party exchanges, with availability varying by region.
Identity, Targeting, and the Cookie Question
Identity strategy is where these three diverge most. Context worth knowing up front: Google announced in 2025 that it would not, after all, deprecate third-party cookies in Chrome, choosing instead to keep its existing user-level choice setting rather than force a cookieless web; Privacy Sandbox APIs are being re-scoped as a result. That reversal reduces the urgency of the “cookiepocalypse,” but it hasn’t erased the industry’s multi-year move toward alternative identifiers, because cookies never worked well on Safari or Firefox, in-app environments, or CTV to begin with.
The Trade Desk has invested the most publicly in an alternative: it originated Unified ID 2.0 (UID2), an open-source, email/phone-based pseudonymous identifier, and the related EUID for Europe. The Trade Desk transferred UID2’s governance to Prebid.org as an independent operator in 2021 so it wouldn’t be seen as a proprietary Trade Desk ID, and the UID2 project site today describes it as “an open-source identity solution built for the open internet,” with cross-industry adoption beyond The Trade Desk itself. DV360 leans on Google’s own signed-in and modeled audience data and first-party integrations (notably Analytics 360); Google’s public DV360 materials don’t detail a specific cookieless-ID strategy comparable to UID2. Amazon DSP leans hardest on first-party data it already has from shopping and streaming — Amazon Ads documentation says it can reach qualified audiences “without relying on traditional ad identifiers,” using deterministic and modeled audiences built from purchase, browsing, and streaming behavior.
Pros
The Trade Desk: Independent of any single media owner, broad open-web and CTV reach, and the most visible industry push behind a cookie-alternative identity standard (UID2/EUID).
Google DV360: Deep, direct access to YouTube inventory and tight integration with Analytics 360 and the rest of Google Marketing Platform.
Amazon DSP: Access to high-intent shopping and streaming signals (Prime Video, Twitch) that no outside DSP can replicate, plus a disclosed, concrete self-service vs. managed-service choice.
Cons
The Trade Desk: No public pricing or minimum spend, so smaller advertisers can’t self-assess cost before talking to sales; running it well requires real in-house or agency programmatic expertise.
Google DV360: No visible self-serve signup; most advertisers reach it only via a Google sales relationship or a certified reseller, and Google discloses no pricing or minimum spend publicly.
Amazon DSP: Managed service carries a real, disclosed cost floor ($50,000 typical minimum), and Amazon’s audience signals and reporting are Amazon-controlled, which limits portability of insights to other channels.
Who It’s a Good Fit For
A brand running its own in-house trading desk, or an agency building one for clients, generally fits The Trade Desk best: it’s built for that self-serve, cross-publisher workflow and doesn’t tie you to one walled garden’s inventory or data. An agency or advertiser already deep in the Google stack — running Google Ads, Analytics 360, and Campaign Manager 360 together — fits DV360 well, especially where YouTube is a core channel. A retailer-focused advertiser, or any brand that wants to target people based on what they actually shop for and stream, fits Amazon DSP well, particularly at the self-service tier if the team has the bandwidth to run it directly.
Who Should Look Elsewhere
A small advertiser without a dedicated programmatic specialist, or without budget anywhere near Amazon’s disclosed $50,000 managed-service threshold, will likely find all three platforms a poor fit and should consider a smaller, explicitly self-serve DSP or a managed-service alternative built for smaller budgets instead. Advertisers whose goal is specifically to advertise inside Amazon’s, Walmart’s, or Instacart’s own retail surfaces — rather than buy general open-web or CTV inventory — should start with this site’s separate retail media networks comparison rather than treating these general-purpose DSPs as retail media tools.
Bottom Line
None of the three publishes a full, apples-to-apples price sheet, and that opacity is itself a real feature of this market: expect a sales conversation before you see a number, except at Amazon, which at least discloses a managed-service floor. Choose The Trade Desk for independent, cross-publisher reach and the strongest public identity strategy; choose DV360 if YouTube and the Google stack are central to your plan; choose Amazon DSP if shopping and streaming signals are what you’re actually trying to buy against.
FAQ
Is The Trade Desk self-serve or managed? The Trade Desk describes its platform as self-serve, but there’s no public signup page — advertisers and agencies onboard through a sales conversation, and pricing isn’t published.
What’s the minimum spend for Amazon DSP? Self-service Amazon DSP has no disclosed management fee or minimum. Amazon’s own documentation states managed service “typically requires a minimum spend of $50,000 USD,” and that figure can vary by country.
Do I need to sell on Amazon to use Amazon DSP? No. Amazon Ads states that brand advertisers, agencies, and tool providers can use Amazon DSP whether or not they sell products on Amazon.
Can I sign up for Google DV360 online myself? Google’s support documentation directs new advertisers to contact its sales team to open a DV360 account; many mid-sized advertisers instead get access through a certified Google Marketing Platform partner or reseller.
Did Google remove third-party cookies from Chrome? No. Google announced in 2025 that it would keep its existing approach of letting users choose on third-party cookies in Chrome rather than deprecating them outright, and said Privacy Sandbox APIs would take on a different role as a result.
What is UID2 and who runs it? Unified ID 2.0 is an open-source, cookieless identifier originally built by The Trade Desk. The Trade Desk transferred its operation to Prebid.org as an independent operator starting in 2021 so it wouldn’t be controlled by a single company.
Cloud sync folders like Google Drive or Dropbox are built for convenience, not disaster recovery — they often sync a ransomware infection to every connected device before you notice. Dedicated backup software works differently: it keeps versioned, point-in-time copies of your files so you can roll back to a clean state after an attack, a failed drive, or an accidental overwrite. This guide compares three of the best-known dedicated backup and recovery tools for individuals and small businesses — Backblaze, Acronis True Image (the product long known as Acronis Cyber Protect Home Office), and IDrive — on price, ransomware-relevant features, version retention, and restore options.
At a Glance
Tool
Starting Price
Free Plan
Best For
Backblaze
$9/month or $99/year for unlimited storage on one computer
No permanent free tier; 14–15-day free trial, no card required
Individuals who want simple, truly unlimited backup at a flat price
Acronis True Image
$49.99/year (Essentials)
No permanent free tier; 30-day free trial
Users who want backup bundled with anti-ransomware and anti-malware tools
IDrive
$83.88 first year for 5TB (renews at $119.88/year)
Yes — Basic plan, 10GB free, no card required
Multi-device households and small businesses wanting one quota shared across many machines
Short Verdict
Backblaze is the simplest and cheapest option for unlimited single-computer backup, but its ransomware defenses rely almost entirely on 30-day version history (longer retention costs extra). Acronis True Image is the most “security-forward” of the three, pairing backup with built-in anti-ransomware and anti-malware scanning even at its entry tier. IDrive sits in between: it’s the best value for covering several devices under one storage quota and offers physical-media backup and restore (IDrive Express) that the other two don’t match in the same way, but it lacks Acronis’s active malware-blocking layer on the consumer plan.
What These Tools Are
All three are dedicated backup and disaster-recovery applications rather than file-sync services. They run a client on your Windows or Mac computer, encrypt your files, and upload versioned copies to the vendor’s cloud (or, for Acronis, optionally to local/NAS storage as well). The pitch for ransomware recovery is the same across vendors: because backups are versioned and stored outside the folder a ransomware strain can reach and encrypt, you can wipe an infected machine and restore from a version taken before the attack, rather than paying a ransom.
Backblaze Personal/Business Backup backs up an entire computer automatically with no file-type or size exclusions, and storage is unlimited regardless of how much data you have. It is the most hands-off of the three — there’s very little to configure.
Acronis True Image (the current name for what Acronis previously branded Cyber Protect Home Office, before reverting to the True Image name in 2024) combines disk-image backup with a cybersecurity suite: anti-ransomware/anti-cryptojacking protection, and, on paid-up tiers, real-time anti-malware, antivirus scanning and web filtering. It’s the only one of the three built explicitly as “backup plus endpoint security” rather than backup alone.
IDrive backs up unlimited devices (desktops, laptops, phones, and servers) into a single shared storage quota under one account, which makes it unusually efficient for a household or small office with several machines. Its snapshot feature keeps multiple historical versions to protect against ransomware, and its IDrive Express service can ship or receive a physical drive for bulk backup or restore.
Pricing Breakdown
Tool
Plan
Price
Storage / Devices
Backblaze
Personal Backup
$9/month, $99/year, or a discounted two-year rate
Unlimited storage, one computer per license
Business Backup
$99/year per computer
Unlimited storage, adds multi-user admin controls
Acronis True Image
Essentials
$49.99/year
No cloud storage; local/disk backup only, up to 5 PCs/Macs
Advanced
From $57.99/year
50GB, 250GB, or 500GB cloud storage
Premium
$124.99/year
1TB up to 10TB cloud storage
IDrive Personal
5TB
$83.88 first year ($119.88 standard renewal)
One account, multiple computers/devices sharing the quota
10TB
$125.88 first year ($179.88 standard renewal)
Same as above
Basic (free)
$0
10GB, no credit card required
Note that IDrive’s advertised rate is a first-year promotional price that steps up to the standard renewal rate from year two onward — budget for the higher number when comparing long-term cost. Acronis’s published U.S. pricing (Essentials/Advanced/Premium) can also differ slightly by region and bundled storage selection, so always confirm the exact figure on the checkout page for your country before buying.
Ransomware Protection, Versioning, and Restore Options
Backblaze: Keeps 30 days of file version history free with every account. Extended “Forever Version History” can be turned on for files older than a year at $0.006/GB per month. Restores are free: download a zip of up to 500GB per request, or request an encrypted USB flash drive or hard drive by mail, which is free if you return it within 30 days. Backblaze doesn’t market a dedicated active-ransomware-blocking feature; its recovery model depends on version history rather than real-time detection.
Acronis True Image: Built-in anti-ransomware and anti-cryptojacking protection is listed as included on all three plans (Essentials, Advanced, Premium), based on Acronis’s official plan comparison. Full real-time anti-malware/antivirus scanning, however, is only a 30-day trial on Essentials and becomes a full feature on Advanced and Premium. This is the only one of the three vendors that actively tries to stop a ransomware process before it finishes encrypting files, rather than relying solely on recovering from a backup afterward.
IDrive: Snapshots retain up to 30 previous versions of backed-up files (accounts created before November 2018 are limited to 10), which the company positions as ransomware protection through point-in-time recovery. Deleted files sit in a 30-day trash before permanent removal. IDrive Express lets you ship a physical drive to IDrive for bulk backup (one free use per year on Personal plans, three on Team/Business, $59.95 for extra backup requests) or request a physical restore ($99.50 per request, typically returned within 48 hours for orders up to 1TB placed before 3pm Pacific). IDrive’s immutable, tamper-resistant snapshot technology is marketed for its 360 Endpoint enterprise product, not the consumer Personal plan.
Pros
Backblaze: Truly unlimited storage for one flat fee, dead-simple setup, free physical-drive restore option, no surprise overage charges.
Acronis True Image: Only option with built-in anti-ransomware and (on paid tiers) full anti-malware scanning bundled with backup; also supports full disk imaging and bare-metal/universal restore.
IDrive: One quota covers many devices (good for multi-PC households or small offices), a genuine free 10GB tier to try the service, and the fastest guaranteed physical-restore turnaround (48 hours) of the three.
Cons
Backblaze: One license per computer only (no multi-device quota sharing on Personal); extended version history beyond a year costs extra; no active malware-blocking component.
Acronis True Image: No cloud storage at all on the cheapest Essentials tier; pricing and feature tables are inconsistently presented across regional pages, so it’s worth double-checking the exact plan contents before buying; historically a heavier, more resource-intensive client than the other two.
IDrive: The attractive headline price is a first-year promotion that roughly rises 40–50% at renewal; extra physical-restore requests and Express Backup uses beyond the free allotment add real cost; consumer plan snapshots aren’t the “immutable” grade IDrive reserves for its business/360 product.
Who It’s a Good Fit For
Individuals with one computer and a lot of data (photographers, video editors, anyone with large local libraries) are well served by Backblaze’s flat-rate unlimited plan. Users who specifically want ransomware defense bundled with their backup — rather than relying on antivirus software separately — fit Acronis True Image best, especially the Advanced or Premium tiers. Households or very small businesses with several machines that want to pool storage under one bill, plus the option to ship a physical drive for the first big backup or an emergency restore, fit IDrive well.
Who Should Look Elsewhere
IT-managed environments that need centralized, policy-driven backup across many endpoints, immutable/air-gapped enterprise-grade retention, or integration with a broader endpoint-security stack will likely outgrow all three consumer-facing plans discussed here and should look at Acronis’s full Cyber Protect business tier or Backblaze’s/IDrive’s dedicated business and enterprise offerings instead of the personal plans compared in this article. Anyone who only needs occasional file sharing or sync (not full-system backup and point-in-time recovery) is better served by a sync tool, not any of these three.
Bottom Line
There’s no single “best” among these three — it depends on what you’re protecting against. For straightforward, affordable, unlimited single-machine backup, Backblaze is hard to beat. For a tool that actively fights ransomware rather than just letting you recover from it, Acronis True Image’s bundled anti-ransomware and anti-malware protection makes it the most security-centric pick, provided you’re willing to pay for cloud storage on the Advanced or Premium tier. For multi-device households or small offices that want one storage pool and the option of physical-media backup and restore, IDrive offers the most flexible value — as long as you budget for the renewal price jump after year one.
FAQ
Can any of these tools actually recover files after a ransomware attack? Yes, in principle. Because all three keep versioned backups stored separately from your live files, you can restore a version from before the infection as long as the ransomware didn’t also compromise your backup credentials or encrypt the local backup cache. Off-site, version-retained cloud backup is one of the standard ransomware-recovery strategies recommended by security practitioners.
Is Acronis Cyber Protect Home Office the same product as Acronis True Image? Yes. Acronis renamed its consumer backup/security product from Acronis True Image to Acronis Cyber Protect Home Office, then reverted it back to the Acronis True Image name in 2024. Feature sets have evolved with each rebrand, so if you’re comparing old reviews, confirm the current plan details on Acronis’s site.
Which of the three is cheapest for a single computer? On official list pricing, Acronis True Image Essentials ($49.99/year) is the lowest sticker price, but it includes no cloud storage at all — it’s local/disk backup only. For cloud-backed unlimited storage on one machine, Backblaze’s $99/year plan is generally the better value once you factor in off-site storage.
Do any of these offer a free plan? IDrive offers a genuinely free Basic plan with 10GB of storage and no credit card required. Backblaze and Acronis only offer time-limited free trials (roughly two weeks and 30 days, respectively) rather than a permanent free tier.
What’s the fastest way to restore a large amount of data after an incident? IDrive Express and Backblaze both offer physical-media restore options that avoid re-downloading everything over the internet. IDrive’s Express 48 service targets a 48-hour turnaround for restores up to 1TB (for orders placed before 3pm Pacific), while Backblaze ships an encrypted USB drive or hard drive and refunds the cost if you return it within 30 days. Both are generally faster than a multi-terabyte download on a typical home connection.
Todoist, TickTick, and Things 3 are three of the most recommended personal task managers on the market, but they solve the “what should I do today” problem in very different ways. Todoist leans on natural-language quick entry and broad platform reach, TickTick bundles a calendar, habit tracker, and Pomodoro timer into one subscription, and Things 3 is a one-time-purchase, Apple-only app built around clean design rather than feature sprawl. This guide compares current pricing, platform availability, and the day-to-day features that matter most — recurring tasks, natural-language input, and widgets — so you can match the app to how and where you actually work.
At a Glance
App
Starting Price
Free Plan?
Best For
Todoist
Free, or Pro at $7/mo (billed monthly) / $60/yr (billed annually)
Yes — 5 personal projects
Cross-platform users who want fast natural-language entry
TickTick
Free, or Premium at $49.99/yr ($4.99/mo billed monthly)
Yes — 9 lists
Power users who want calendar, habits, and Pomodoro bundled in
Apple-only users who want polished design and no subscription
Short Verdict
Todoist is the safest pick if you (or your household) mix Android, iPhone, Windows, Mac, and Linux devices and want a generous free tier plus the most mature natural-language input on the market. TickTick is the best value for people who want a free tier that already includes a calendar view and habit tracker, with a premium upgrade that undercuts Todoist Pro on price. Things 3 is not for everyone — there’s no Android or Windows version and no free plan — but for Apple-only users who want a beautifully designed app they pay for once instead of forever, it remains a strong choice, especially since its 2026 update overhauled how repeating to-dos work.
What These Apps Are
All three are personal task managers: apps for capturing to-dos, scheduling them, grouping them into projects or lists, and repeating them on a cadence. They sit a notch below full project-management software like Asana or ClickUp — the focus is individual productivity, though all three allow light collaboration on paid plans.
Todoist and TickTick are subscription SaaS products with a free tier, available on nearly every major platform. Things 3, from Cultured Code, is a traditional App Store app: no account required, no ads, and a flat purchase price per Apple platform, with device sync handled for free via Cultured Code’s own cloud service.
Pricing Breakdown
App
Free Tier Limits
Paid Tier & Price
What Paid Adds
Todoist
5 personal projects, 3 saved filter views, 1 week of activity history, 5MB file uploads
Pro: $7/mo or $60/yr (~$5/mo)
300 projects, 150 filters, full history, 100MB uploads, calendar & table layouts, AI Task/Email Assist, auto backups
None — 15-day free trial per platform, no ongoing free tier
One-time: $9.99 (iPhone & Apple Watch), $19.99 (iPad), $49.99 (Mac); also sold for Apple Vision Pro
Full app, no in-app purchases or subscription — each platform is a separate purchase
A practical note on the math: an Apple user who wants Things 3 on iPhone, iPad, and Mac pays roughly $80 once, with no further charges for syncing. A Todoist Pro or TickTick Premium subscriber pays less upfront but keeps paying every year.
Platform Availability
Todoist: Android, iPhone, iPad, Mac, Windows, Linux, Apple Watch, Wear OS, plus browser extensions and email add-ons.
TickTick: iOS/iPadOS, Android, Windows, macOS, Linux, a web app, and a browser extension.
Things 3: Apple only — Mac, iPhone, iPad, Apple Watch, and Apple Vision Pro. There is no Android, Windows, Linux, or web version, and none is planned.
Recurring Tasks, Natural-Language Input & Widgets
Recurring tasks: Todoist and TickTick both let you type a recurring pattern directly into the task field (e.g. “every 3 months”), and both support standard recurrence rules. Things 3 handles recurrence through a repeat-rule dialog rather than typed text, and its August 2026 update (version 3.23) improved it: repeating to-dos can be completed early, rescheduled with a choice between “Make Exception” (one occurrence) or “Update Rule” (all future occurrences), and tracked from a new Repeating list.
Natural-language input: Todoist has the most complete implementation — its Quick Add field recognizes dates, times, recurring patterns, labels, priorities, and project assignment in a single typed line (e.g. “Call dentist tomorrow 4pm #Health p1”). TickTick has a comparable Smart Date Parsing engine for dates and times. Things 3’s Quick Entry recognizes relative date phrases (such as “in 5 weeks”) and converts them to a calendar date in the device’s language, but it does not parse labels, projects, or recurrence from typed text the way the other two apps do.
Widgets: All three support home-screen widgets on mobile. Todoist offers iOS and Android widgets for viewing and quick-adding tasks. TickTick’s widgets let you view and add tasks from the home screen. Things 3 added interactive iOS/iPadOS home-screen widgets in 2023 and has supported iOS Lock Screen widgets since iOS 16. None offers a desktop-OS widget outside the apps themselves.
Pros
Todoist: Runs on nearly every platform and wearable; the most mature natural-language quick-add on the market; generous Pro tier (300 projects); strong third-party integrations.
TickTick: Free plan already includes a calendar view, habit tracker, and Pomodoro timer; Premium is cheaper per year than Todoist Pro; also cross-platform on desktop, mobile, and web.
Things 3: No subscription, ever; widely praised interface and interaction design; free Things Cloud sync between your own devices; 2026 update made recurring to-dos far more flexible.
Cons
Todoist: Free tier caps you at just 5 projects and 3 filters, which power users will hit quickly; AI features are Pro-only.
TickTick: Interface is busier than Todoist or Things 3 because it packs in more views and tools; some users find the many feature toggles overwhelming at first.
Things 3: No free tier beyond a trial; no Android, Windows, Linux, or web client at all; paying separately for Mac, iPhone/Watch, and iPad adds up versus a single cross-platform subscription; no native collaboration features for sharing lists with others.
Who It’s a Good Fit For
Choose Todoist if you switch between Android and Apple devices, or use Windows or Linux at work, and want the fastest typed task entry. Choose TickTick if you want one app to also handle your calendar and habit tracking without buying separate apps, and you want the richest free tier of the three. Choose Things 3 if every device you own is made by Apple, you value interface polish over feature count, and you’d rather pay once per device than indefinitely.
Who Should Look Elsewhere
Skip Things 3 if you have any Android or Windows devices in your daily routine, need to share lists with people who aren’t on Apple hardware, or want to try a full feature set before paying anything beyond a short trial. Skip Todoist’s free tier if you manage more than five ongoing projects and aren’t ready to pay for Pro. Skip TickTick if you specifically want the single cleanest, most minimal interface of the three — that’s Things 3’s strength, not TickTick’s.
Bottom Line
There isn’t a single “best” app here — it depends on your platforms and your tolerance for subscriptions. Todoist wins on cross-platform reach and input speed, TickTick wins on free-tier feature depth and price-per-year, and Things 3 wins on design and a one-time cost if you’re fully inside the Apple ecosystem. Most people can make a confident choice just by checking which devices they own and whether a $0 free tier or a one-time purchase matters more to their budget.
FAQ
Is Things 3 really a one-time purchase, not a subscription?
Yes. Each Apple platform is sold as a single flat-price App Store purchase ($9.99 for iPhone & Apple Watch, $19.99 for iPad, $49.99 for Mac) with no subscription or in-app purchases, and sync between your own devices is included for free via Things Cloud.
Does Things 3 work on Android or Windows?
No. Things 3 is Apple-only, covering Mac, iPhone, iPad, Apple Watch, and Apple Vision Pro. There is no Android, Windows, Linux, or web version.
Which app has the best free plan?
TickTick’s free plan is the most feature-rich of the three, including a calendar view and habit tracking at no cost, though it limits you to 9 lists. Todoist’s free plan is more restrictive on project count (5) but includes unlimited tasks within those projects. Things 3 has no ongoing free plan, only a 15-day trial.
Can I use natural language to add recurring tasks in all three apps?
Todoist and TickTick both let you type recurrence directly into the task field. Things 3 uses a separate repeat-rule dialog instead of typed recurrence, though its 2026 update made managing and rescheduling those repeating to-dos considerably more flexible.
Which is cheapest per year if I want the paid tier?
Billed annually, TickTick Premium costs $49.99/yr, a bit less than Todoist Pro’s $60/yr annual plan; billed monthly, TickTick is $4.99/mo versus Todoist Pro’s $7/mo. Things 3 has no recurring fee at all after the one-time purchase, which can be the cheapest option long-term if you stay on the same Apple devices for years.
Freelancers and small agencies don’t need accounting software built for enterprises — they need something that gets invoices out the door, gets paid faster, and doesn’t eat half a day a month in setup. FreshBooks, Bonsai, and Invoice Ninja all promise exactly that, but they take very different approaches: one is a polished all-in-one accounting suite, one bundles invoicing into a client-management and proposal platform, and one is a genuinely free, open invoicing tool you can self-host for nothing. Here’s how they actually compare on price and features, verified against each vendor’s current pricing pages.
At a Glance
Tool
Starting Price
Free Plan
Best For
FreshBooks
$23/mo (Lite), 30-day free trial
No permanent free plan
Solo freelancers who want full accounting plus invoicing
Bonsai
$9/mo per user (Basic, billed annually); $19/mo for invoicing (Essentials)
No free plan, 7-day trial
Freelancers who also need contracts, proposals, and a client CRM
Invoice Ninja
$0 (hosted Free plan) or free self-hosted
Yes — free forever (hosted, 5 clients) or unlimited self-hosted
Budget-conscious freelancers and small agencies comfortable with a leaner UI
Short Verdict
FreshBooks is the best fit if you want invoicing bundled with real double-entry accounting and don’t mind paying for it. Bonsai is the strongest choice for freelancers who need contracts and proposals alongside invoicing, not just invoices. Invoice Ninja is the clear pick for anyone who wants capable invoicing without a recurring bill, whether that’s the free hosted plan or a self-hosted install.
What It Is: Category Overview
All three tools sit in the invoicing-and-billing software category aimed at freelancers, consultants, and small agencies, but they’re built around different centers of gravity. FreshBooks started as invoicing software and grew into a full small-business accounting platform — it now handles expenses, time tracking, basic bookkeeping, and payroll add-ons alongside invoicing. Bonsai is positioned as an all-in-one freelancer operating system: invoicing sits next to contracts, proposals, a client CRM, task management, and time tracking, and the lowest-priced plan doesn’t include invoicing at all. Invoice Ninja is a dedicated invoicing and billing tool, available both as a hosted SaaS product and as source-code-available software you can run on your own server under the Elastic License v2 — free to self-host for your own business, with a separate commercial agreement required if you want to resell it or run it as a hosted service for others.
On payment processing, FreshBooks’ standard rate is 2.9% + $0.30 per card transaction and 1% for ACH bank transfers on the Lite, Plus, and Premium plans, with lower negotiated rates on Select. FreshBooks also charges separately for its Advanced Payments add-on ($20/mo), extra team-member seats ($11/mo each), and its payroll add-on ($40/mo plus $6/mo per employee). Bonsai’s invoicing pages state it accepts credit cards, bank transfers, and other methods depending on client preference, and it names Stripe Payments Company as its partner for money transmission and account services, though it doesn’t publish a specific per-transaction rate on its pricing or invoicing pages. Invoice Ninja’s hosted and self-hosted plans both let you connect your own payment gateway — including Stripe, PayPal, Square, GoCardless, Authorize.net, and Mollie — so processing fees are whatever your chosen gateway charges rather than a fee set by Invoice Ninja itself.
Invoicing Features: Recurring Billing, Late Fees, and Client Portals
All three support recurring/subscription invoices and give clients a portal to view and pay invoices online, but they differ on overdue-payment handling. FreshBooks is the only one of the three whose documentation confirms it can automatically add an actual late fee — a flat amount or percentage — as a line item on an overdue invoice, on top of sending reminder emails. Bonsai’s invoicing pages describe automatic payment reminders for overdue invoices but don’t document an automatic late-fee charge. Invoice Ninja likewise documents automatic late-payment reminder emails (and the ability to pass credit card processing fees on to the client) but doesn’t document an automatic late-fee charge either. If charging real late fees automatically matters to your collections process, that’s a point in FreshBooks’ favor specifically.
Contracts and proposals are where Bonsai pulls ahead: its Essentials plan and above include contract templates with e-signatures and a dedicated proposals tool with service packages and electronic approval — features FreshBooks and Invoice Ninja don’t build around in the same way. Invoice Ninja’s client portal supports viewing payment history and saved payment methods, with document uploads available on its Enterprise tier, and its Pro and Enterprise plans use different portal URL formats (a subdomain on Pro, a custom branded URL on Enterprise).
Pros
FreshBooks
True automatic late-fee charges, not just reminders
Full accounting features (expenses, basic bookkeeping) alongside invoicing
30-day free trial with no credit card required
Custom Select plan for agencies wanting negotiated processing rates
Bonsai
Contracts, e-signatures, and proposals built in alongside invoicing
Unlimited clients and projects even on lower tiers
Client CRM and scheduling tools beyond just billing
Useful for agencies that need a 3+ user plan with shared permissions (Elite)
Invoice Ninja
Genuinely free forever on the hosted plan (up to 5 clients) or unlimited self-hosted
No markup on payment processing — connect your own gateway at its rates
Self-hosting option means no recurring SaaS fee at all
Lowest-cost paid tier of the three ($14/mo for unlimited clients)
Cons
FreshBooks
No permanently free plan — the Lite plan caps you at 5 billable clients for $23/mo
Team members, advanced payments, and payroll are all separate add-on costs
Most expensive entry point among the three for a single freelancer
Bonsai
Cheapest plan (Basic) doesn’t include invoicing at all — you need Essentials or higher
No permanent free plan, only a 7-day trial
Elite plan requires a 3-user minimum, which doesn’t suit solo freelancers
Per-transaction payment processing rate isn’t published on its site
Invoice Ninja
Free hosted plan caps you at 5 clients
Self-hosting requires you to run and maintain your own server
No contracts/proposal tooling comparable to Bonsai
Interface and onboarding are generally less polished than FreshBooks or Bonsai
Who It’s a Good Fit For
Solo freelancers who want simple, reliable invoicing plus basic bookkeeping: FreshBooks Lite.
Freelancers who sell project-based work and need contracts and proposals, not just invoices: Bonsai Essentials.
Anyone on a tight budget, or a small agency comfortable with self-hosting: Invoice Ninja’s free hosted plan or self-hosted install.
Small agencies with multiple team members needing shared permissions: Bonsai Elite or Invoice Ninja Enterprise, depending on whether contracts or user-count scaling matters more.
Who Should Look Elsewhere
If you need contracts and e-signatures but want to stay under $20/mo, Bonsai’s Essentials tier ($19–25/mo) may push past what Invoice Ninja charges for unlimited invoicing alone.
If you need full double-entry accounting and payroll, Invoice Ninja isn’t built for that — FreshBooks is the closer fit.
If a polished, well-supported SaaS experience matters more than price, Invoice Ninja’s free self-hosted route asks more technical effort than either FreshBooks or Bonsai.
Bottom Line
There’s no single winner here because the three tools solve slightly different problems. FreshBooks is the safest choice if invoicing needs to sit inside broader small-business accounting and you want automatic late fees, not just reminders. Bonsai earns its higher price by bundling contracts, proposals, and a client CRM around the invoice, which suits freelancers selling scoped projects. Invoice Ninja is the value play: a free hosted plan, an even cheaper Pro tier, and a genuinely free self-hosted option make it hard to beat on cost for anyone willing to live with a less polished interface.
FAQ
Does any of these three have a truly free plan? Only Invoice Ninja does. Its hosted Free plan supports up to 5 clients at no cost, and its self-hosted software is free to run on your own server under the Elastic License v2. FreshBooks and Bonsai both offer free trials (30 days and 7 days respectively) but no permanent free tier.
Which one supports automatic late fees on overdue invoices? FreshBooks is the only one of the three whose support documentation confirms an automatic late-fee charge (a flat amount or percentage added as a line item). Bonsai and Invoice Ninja both document automatic reminder emails for overdue invoices, but not an automatic fee charge.
Can I get contracts and e-signatures with FreshBooks or Invoice Ninja? Not natively in the way Bonsai offers them. Bonsai’s Essentials plan and above include contract templates with e-signatures and a separate proposals tool; FreshBooks and Invoice Ninja are built primarily around invoicing and payments rather than contract workflows.
What does self-hosting Invoice Ninja actually cost? The software itself is free to self-host for your own business under the Elastic License v2 (“source-code available,” with commercial resale or offering it as a managed service to others requiring a separate agreement). You still pay for your own server hosting and any payment gateway fees, which Invoice Ninja doesn’t mark up.
Is Bonsai or FreshBooks better for a small agency with employees? It depends on what the agency needs most. Bonsai’s Elite plan (3-user minimum) adds custom permissions and timesheet locking for teams managing client projects and contracts. FreshBooks lets you add team members for $11/mo per user and adds a separate payroll add-on, which suits agencies that want invoicing and basic payroll in one place.
Real-time collaborative editing is now the baseline expectation for any team document tool, not a nice-to-have. But “collaborative document editor” means different things depending on which product you pick: Google Docs is a word processor with best-in-class co-editing, Notion is a connected workspace built around flexible pages and databases, and Coda — now rebranding as Superhuman Docs — tries to fuse a document with a lightweight app. This guide compares all three on price, real-time editing, commenting, templates, and database features, so you can match the tool to how your team actually works. (This is a separate comparison from our note-taking apps and video conferencing roundups — this one is specifically about collaborative document and workspace editing.)
At a Glance
App
Starting Price (paid)
Free Plan
Best For
Google Docs (Google Workspace)
From $7/user/month (Business Starter, list price)
Yes — full Docs/Sheets/Slides free with a personal Google account
Teams that want simple, fast, universally familiar document editing
Notion
$10/member/month (Plus)
Yes — limited for multi-member workspaces
Teams that want an all-in-one workspace, wiki, and light database on top of docs
Coda (now Superhuman Docs)
$15/Doc Maker/month (Pro), $12/mo billed annually
Yes — capped automations, 1GB attachments/doc, 7-day history
Teams that want a doc-plus-app hybrid with tables, automations, and integrations
Short Verdict
If your team just needs reliable, familiar real-time document editing with comments and suggestions, Google Docs inside Google Workspace is still the safest, cheapest default. If you want docs, a wiki, and simple databases living in one connected workspace, Notion is the better fit. If you want documents that behave like lightweight internal apps — with tables, automations, and pulled-in data — look at Coda, keeping in mind it is actively being folded into Superhuman’s “Docs” product and bundled with Grammarly, Mail, and an AI assistant.
What These Tools Are
Google Docs is Google’s cloud word processor, part of the Google Workspace suite alongside Sheets, Slides, Drive, and Gmail. It is the reference implementation of real-time co-editing: multiple people can type in the same paragraph simultaneously, see each other’s cursors, leave comments, and use Suggesting mode (Docs’ version of tracked changes) to propose edits without touching the live text.
Notion is a connected workspace built from nested pages and blocks. A “document” in Notion is just a page, but pages can embed databases (tables, boards, calendars, galleries) with custom properties, linked views, and relations to other pages. That makes Notion closer to a company wiki or knowledge base with documents as one of its building blocks, rather than a word processor first.
Coda blends a document canvas with spreadsheet-like tables and formulas, buttons, automations, and “Packs” that pull in data from tools like Jira, GitHub, Figma, and Slack — effectively a doc that can also act like a small internal app. Important context: in October 2025, Coda’s parent Grammarly rebranded the whole company as Superhuman, and on July 8, 2026 Coda itself was renamed Superhuman Docs. According to Superhuman’s own help center, existing Coda docs, formulas, automations, and API endpoints continue to work, coda.io links redirect automatically, and current Coda plans and pricing carry over unless a workspace chooses to upgrade into the newer bundled plans. New signups, however, are now priced and sold as part of the Superhuman suite rather than as standalone “Coda.”
Pricing Breakdown
Plan Tier
Google Workspace
Notion
Coda / Superhuman Docs
Free
Personal Google account: Docs, Sheets, Slides free; 15GB shared storage
$0 — unlimited pages for individuals, limited blocks for multi-member workspaces, 5MB file uploads, 7-day page history
$0 — capped automations, 1GB attachments per doc, 7-day version history, limited AI trial
Entry paid
Business Starter: $7/user/month (list price), 30GB storage/user
Notes on the numbers above: Google’s prices are the standard published rates on its pricing page; Google is currently running a limited-time promotion (roughly 30–50% off for a set period on new signups) that is separate from these list prices, so always check the live checkout price before buying. Notion’s page states annual billing saves “up to 20%” off the monthly rates shown, without listing the exact per-seat annual figure. Coda/Superhuman Docs bills only “Doc Makers” — members who create docs and pages — while Editors and Viewers are free seats on every plan; new workspaces are generally sold the bundled Superhuman plan (which also includes Grammarly, Mail, and the Go AI assistant), though Superhuman’s help center says some existing Coda workspaces can keep an a-la-carte, Docs-only subscription at their legacy pricing.
Pros
Google Docs: Rock-solid real-time co-editing with near-zero learning curve; comments and Suggesting mode are familiar to almost any professional; integrates with the rest of Google Workspace (Drive, Sheets, Meet); works well offline with sync.
Notion: One workspace for docs, wikis, and lightweight databases with relations and linked views; flexible page nesting suits teams that want a single source of truth; strong template ecosystem and free plan for individuals.
Coda / Superhuman Docs: Tables and formulas feel like a real database inside a document; buttons and automations let a doc trigger actions instead of just recording information; Packs connect to third-party tools so data stays current without copy-pasting.
Cons
Google Docs: Weak as a structured database or wiki; no native relational tables, automations, or app-like building blocks; organization depends heavily on Drive folder discipline.
Notion: Can get slow in very large, heavily nested workspaces; its databases are not a substitute for a real relational database or spreadsheet formula engine; free plan limits multi-member workspaces more than solo use.
Coda / Superhuman Docs: The ongoing Superhuman rebrand adds real uncertainty about pricing, branding, and roadmap continuity for teams evaluating it today; new signups are pushed toward a bundled suite (Mail, Grammarly, Go) rather than a simple Docs-only purchase; per-Doc-Maker pricing is the most expensive of the three at the entry paid tier.
Who It’s a Good Fit For — and Who Should Look Elsewhere
Choose Google Docs if your team mainly writes and edits prose documents — proposals, reports, memos — and already lives in Gmail/Drive/Calendar. It’s the lowest-friction, cheapest option for pure document collaboration and the easiest for external collaborators and clients to use without training.
Choose Notion if you want a company wiki, internal knowledge base, and project tracking in the same place as your written docs, and you’re willing to invest time structuring pages and databases. It’s a better fit than Google Docs for teams that outgrow folders-and-files organization but don’t need a full no-code app builder.
Choose Coda / Superhuman Docs if you specifically want documents that double as small internal tools — status trackers with buttons, docs that pull live data from Jira or GitHub, or forms that trigger automations. Teams that are purely writing-focused, cost-sensitive, or wary of adopting a product mid-rebrand should look elsewhere for now, or confirm current plan terms directly with Superhuman before committing.
Bottom Line
There’s no single winner here — the right pick depends on whether you need a word processor, a workspace, or a doc-app hybrid. Google Docs wins on simplicity and price for straightforward document collaboration. Notion wins for teams that want docs and a lightweight database/wiki in one place. Coda (now being rebranded as Superhuman Docs) wins on power and automation for teams willing to accept a higher price and some transitional uncertainty while the Superhuman rebrand plays out.
FAQ
Is Google Docs really free for real-time collaboration? Yes. Any personal Google account gets free access to Docs, Sheets, and Slides with full real-time co-editing and commenting; paid Google Workspace plans add business email, more storage, admin controls, and Gemini AI features on top of the same core editing experience.
Does Notion support suggested edits like Google Docs? Notion supports inline comments and page/block history, but its editing model isn’t built around a formal “suggest mode” the way Google Docs’ Suggesting mode is — most Notion teams use comments and version history instead of tracked changes.
What happened to Coda — is it shutting down? No. Coda was acquired by Grammarly, which rebranded itself as Superhuman in October 2025. On July 8, 2026, the Coda product itself was renamed Superhuman Docs. Per Superhuman’s help center, existing docs, formulas, automations, and the API continue to work, and coda.io links redirect automatically — Superhuman describes it as “an evolution, not a replacement.”
Which tool has the best database/table features? For relational, formula-driven tables that can also trigger actions, Coda/Superhuman Docs is the most capable. Notion’s databases are strong for organizing and filtering structured content (tasks, wikis, CRMs) but have a simpler formula engine. Google Docs has no native database features — you’d pair it with Google Sheets instead.
Can I mix tools — for example, Google Docs for writing and Notion for the wiki? Yes, and many teams do. Google Docs and Notion both support embedding or linking to each other’s content, so it’s common to draft long-form documents in Google Docs while using Notion as the central index or wiki that links out to them.
Remote and distributed teams can’t rely on someone walking past a desk to know what’s being worked on, which is why time tracking software has become one of the first tools a distributed team adopts. Toggl Track, Harvest, and Clockify are three of the most widely used options, and each takes a different approach to pricing, reporting, and billing. This guide compares their current plans and features directly from each vendor’s own pricing and integration pages, verified in November 2026, so you can pick the right one without digging through marketing pages yourself.
At a Glance
Tool
Starting Paid Price
Free Plan
Best For
Toggl Track
$9/user/month (billed annually)
Yes, up to 3 users
Freelancers and small teams who want simple, privacy-first tracking
Harvest
$9/seat/month (billed annually)
Yes, 1 seat / 2 projects
Agencies and consultancies that invoice clients by the hour
Clockify
$3.99/seat/month (billed annually)
Yes, up to 5 users
Larger or budget-conscious teams needing the cheapest per-seat cost
Short Verdict
All three tools cover the basics of starting a timer and generating a report, but they diverge once you need to bill clients or manage a distributed team at scale. Harvest is the strongest choice if invoicing is central to your workflow, since billing and expense tracking are built in from the free tier. Clockify wins on raw price-per-seat as headcount grows, and its free plan covers more users than the other two. Toggl Track sits in the middle, with the cleanest interface and strong calendar and project-management integrations, but its free tier is capped at just three users.
What These Tools Are
Toggl Track, Harvest, and Clockify are all cloud-based time tracking platforms built around a simple core: a start/stop timer (or manual entry) that logs hours against a client, project, or task, which then rolls up into reports. For remote teams, the categories split mainly on how much project-management and billing functionality is layered on top of that core timer.
Toggl Track is positioned as a lightweight, privacy-conscious tracker. Its own marketing is explicit that the desktop app “never monitors screens, keystrokes, or webcams,” which sets it apart from employee-monitoring-style tools. Harvest leans toward agency and consulting workflows, bundling time tracking with invoicing, expense tracking, and accounting integrations (QuickBooks Online, Xero, Stripe) from day one. Clockify, built by the CAKE.com group that also makes the Pumble chat app and Plaky project tool, is positioned as the budget and scale option, with a free plan that supports more users than either competitor and a tiered structure that adds administration, billing, and security features as you move up.
Pricing Breakdown
All prices below are per user (or per seat) per month, in USD, as published on each vendor’s own pricing page. Clockify and Harvest list a billed-monthly price alongside a lower billed-annually price; Toggl Track’s page follows the same pattern.
Plan
Billed Annually
Billed Monthly
Notes
Toggl Track
Free
$0
$0
Up to 3 users; personal reports; Google/Outlook calendar sync
Timesheeting, billing, invoicing and recurring invoices
Pro
$7.99
$9.99
Profitability and productivity reporting
Enterprise
$11.99
$14.99
Advanced control and security (SSO, custom roles)
On reporting and invoicing, the three tools land in different places. Toggl Track lets any user create and download an invoice PDF from a report, but calculating a billable amount requires a paid plan, the free-tier PDF carries a Toggl watermark, and sending invoices to QuickBooks is a Starter-plan-and-up feature. Harvest builds full invoicing, recurring invoices, and payment integrations (Stripe, PayPal, Deel) into every plan, including Free, which is why it remains the default choice for agencies that bill clients directly out of their time tracker. Clockify holds invoicing back until the Standard plan, so its cheapest paid tier (Basic) is administration-only.
Idle-time and activity handling also differs. Clockify includes idle detection on every plan, including Free. Harvest’s Mac and Windows desktop apps flag inactivity after a default 10 minutes idle, then let you discard the idle time, keep it, or log it as a separate entry. Toggl Track lists “idle time notifications” as part of its automated desktop tracking, which detects when you’ve stepped away from the keyboard and lets you discard or keep that time; none of the three vendors publish camera, screenshot, or keystroke monitoring, since all three position themselves against invasive employee-monitoring software.
For integrations, Harvest and Toggl Track both list native Slack and Asana connections on their own integrations pages: Harvest’s Slack app lets you start timers and check project budgets from inside Slack, while Toggl’s Asana integration (a paid-plan feature) and Slack integration let you start timers from either tool. Clockify’s own integrations page lists a native Asana connection but does not list a native Slack app; Clockify promotes its own CAKE.com chat tool, Pumble, instead, and Slack connectivity is left to third-party automation tools like Zapier rather than a first-party app.
Pros
Toggl Track: Clean, fast interface; strong calendar integrations on the free plan; explicit no-surveillance stance; native Slack and Asana integrations on paid tiers.
Harvest: Invoicing, expense tracking, and payment integrations built into every plan, including Free; native Slack and Asana apps; idle detection with granular options on desktop.
Clockify: Lowest per-seat price of the three on every paid tier; free plan supports up to 5 users; idle detection included even on Free.
Cons
Toggl Track: Free plan is capped at just 3 users; invoicing needs a paid plan to calculate billable totals or remove branding; Jira/Asana integration is Premium-only.
Harvest: No published free-trial middle ground between Free (1 seat) and the paid Teams plan; priciest entry point into paid reporting among the three.
Clockify: Free-plan reports are capped to a one-month date range; invoicing is withheld until the Standard tier; no native Slack app.
Who It’s a Good Fit For
Freelancers working solo are well served by any of the three free plans, but Harvest’s free tier is the only one that ships with real invoicing out of the box, which matters if you’re billing clients directly rather than exporting hours to another tool. Small teams (roughly 3–10 people) who need to collaborate without hitting a user cap will likely outgrow Toggl Track’s free plan fastest and should budget for Starter or Clockify’s Basic/Standard tier instead. Larger or budget-conscious organizations that need SSO, custom roles, and dozens or hundreds of seats will find Clockify’s per-seat economics hard to beat, while agencies with complex client billing, retainers, and approval chains will likely still prefer Harvest’s Enterprise tier or Toggl Track’s Premium plan for the deeper reporting.
Who Should Look Elsewhere
Teams that need built-in invoicing on a tight budget should be cautious with Clockify’s Basic tier, since invoicing only unlocks at Standard ($5.49/seat/month annually). Teams larger than 3 people who want to stay on a truly free plan should skip Toggl Track in favor of Clockify’s 5-user free tier or Harvest’s single-seat free plan paired with a paid upgrade sooner. And teams that specifically need a native Slack integration without third-party automation tools should lean toward Harvest or Toggl Track rather than Clockify.
Bottom Line
There’s no single winner here because the three tools are optimized for different jobs. If client invoicing is the priority, Harvest’s all-plan billing features make it the safest default. If the priority is the lowest possible per-seat cost at scale, Clockify’s tiered pricing and generous 5-user free plan win out. If the priority is a clean, fast interface with solid calendar and project-tool integrations and you’re not worried about outgrowing a 3-user free tier, Toggl Track remains a strong, well-regarded choice. Whichever you pick, confirm current pricing directly on the vendor’s page before committing, since all three have changed their pricing within the past year.
FAQ
Does Toggl Track have a free plan for teams? Yes, but it’s capped at up to 3 users according to Toggl’s own pricing FAQ. Beyond that, you need the Starter plan at $9/user/month billed annually ($12 billed monthly).
Can I send invoices directly from Harvest’s free plan? Yes. Harvest’s free plan (1 seat, 2 projects) includes invoicing and expense tracking, which is not the case for Toggl Track’s or Clockify’s free plans.
Which tool is cheapest for a 20-person remote team? Based on published per-seat pricing, Clockify’s paid tiers (from $3.99/seat/month billed annually) are the lowest cost of the three once you exceed the free-plan user caps, though the right plan depends on which features — invoicing, SSO, custom roles — your team actually needs.
Do any of these tools track screenshots or keystrokes? No. Based on each vendor’s own product pages, none of the three markets screenshot, webcam, or keystroke monitoring; all three focus on timers and idle-time detection rather than activity surveillance.
Does Clockify integrate with Slack? Not natively. Clockify’s own integrations page lists a native Asana connection but does not list a first-party Slack app; connecting the two currently relies on third-party automation platforms like Zapier.
“9,216 chips in a pod” and “42.5 ExaFLOPS” are the two numbers that show up in every headline about Google’s Ironwood TPU, and both are real, confirmed figures from Google Cloud’s own materials. But neither number means much without understanding how those 9,216 chips are actually wired together — because the interesting engineering in Ironwood isn’t the chip itself, it’s the optical switching fabric that lets Google treat a room full of racks as one reconfigurable machine. This is specifically about that pod-and-superpod architecture, not a general tour of the TPU chip (which this site has already covered elsewhere).
At a Glance
Generation
7th-generation TPU (“Ironwood”)
Chips per superpod
9,216 (also offered at 256-chip pod scale)
Compute per full pod
42.5 ExaFLOPS (FP8)
Peak compute per chip
4,614 TFLOPS
HBM per chip
192 GB across 8 HBM3E stacks
HBM bandwidth per chip
7.37–7.4 TB/s
Total shared HBM (superpod)
1.77 PB
Chip-to-chip interconnect (ICI)
1.2 TB/s bidirectional per chip (9.6 Tb/s)
Rack-level topology
64 chips per rack (“cube”), direct 3D torus
Inter-cube fabric
Optical Circuit Switching (OCS)
Superpod footprint
Approximately 10 MW
What a 9,216-Chip Pod Actually Means
Google’s basic building block is a “cube”: 64 Ironwood chips, four chips per physical host, 16 hosts per rack, all connected directly via Inter-Chip Interconnect (ICI) in a 3D torus — meaning every chip has direct links to six neighbors across three axes, rather than a flat switch. A 256-chip pod, Google’s smaller offering, is simply four of these cubes connected together. The full 9,216-chip superpod is 144 cubes (144 × 64 = 9,216), and that’s the detail that explains why Ironwood needed a fundamentally different interconnect than earlier TPU generations: a 3D torus alone doesn’t scale cleanly to 144 racks without either enormous fixed cabling complexity or some way to dynamically rewire connections between cubes. That’s exactly what Google added.
Google states a full superpod provides 1.77 petabytes of directly accessible shared HBM — a figure arrived at simply by multiplying 9,216 chips by 192 GB of HBM3E per chip (8 stacks per chip), with each chip delivering roughly 7.37–7.4 TB/s of HBM bandwidth. The physical footprint of a 9,216-chip superpod runs to nearly 10 MW, which is a useful number for anyone trying to understand why “renting a TPU pod” is a data-center-level commitment, not a server order.
Optical Circuit Switching: The Part That Actually Matters
Within a single 64-chip cube, chips connect directly via ICI. Connecting 144 cubes into one 9,216-chip domain is handled by Optical Circuit Switching (OCS) — a dynamic, reconfigurable optical fabric that sits between cubes rather than inside them. Google describes OCS as giving the superpod fault tolerance that a fixed electrical fabric can’t easily match: if a cube or a link fails, the OCS fabric manager optically routes around the unhealthy unit and establishes new circuits among the remaining healthy cubes, swapping in a designated spare cube to keep the workload running rather than restarting a failed training job from scratch. The same reconfigurability lets Google carve out “slices” of any size from a superpod for different customers or jobs, rather than being locked into fixed-size partitions.
Beyond a single superpod, Google says Ironwood scales further — “into clusters of hundreds of thousands of TPUs” — by connecting multiple superpods over Google’s standard data-center network (the Jupiter network), rather than extending the OCS fabric itself across that distance. In other words, there are effectively three tiers: ICI within a cube, OCS between cubes inside a superpod, and conventional data-center networking between superpods.
Cooling at This Density, and the ExaFLOPS Caveat
Packing 9,216 chips into roughly 10 MW of continuous AI compute load isn’t viable with air cooling, and Google says as much directly: its advanced liquid cooling, paired with the Ironwood board design, is stated to sustain up to 2x the performance of standard air cooling under continuous, heavy AI workloads, using what Google calls third-generation Cooling Distribution Units at the superpod level. Google separately notes that its liquid cooling deployments across its fleet have run at “GigaWatt scale” with roughly 99.999% uptime since 2020 — worth noting that this is a fleet-wide historical claim about Google’s liquid cooling program generally, not an Ironwood-specific reliability figure, and the article treats it accordingly rather than implying it’s a guarantee for any single Ironwood deployment.
One figure worth reading carefully: Google compares a full Ironwood pod’s 42.5 ExaFLOPS to the El Capitan supercomputer’s 1.7 ExaFLOPS rating, framing Ironwood as “more than 24x” larger. That comparison mixes precisions — Ironwood’s 42.5 ExaFLOPS is an FP8 AI-compute figure, while El Capitan’s rating is a traditional FP64 high-precision-computing benchmark (the standard used for supercomputer rankings like the TOP500). FP8 and FP64 measure fundamentally different kinds of arithmetic, so the comparison illustrates scale in a general sense but isn’t an apples-to-apples performance claim, and readers evaluating TPU pods against traditional HPC systems should keep that distinction in mind rather than treating the 24x figure as a literal speed multiple.
How This Compares to Nvidia and AWS’s Scale-Out Approach
All three major infrastructure providers solve the same underlying problem — getting more chips to behave as one coherent domain — with different topology philosophies. Nvidia’s approach centers on the NVLink Switch fabric inside a single GB200/GB300 NVL72 rack, creating a fixed 72-GPU domain that then scales out to multiple racks over InfiniBand or Spectrum-X Ethernet networking; the “one giant GPU” abstraction stops at 72 GPUs, with everything beyond that handled by conventional networking. AWS’s Trainium side uses NeuronLink to join four Trn2 servers into a 64-chip UltraServer, then scales further using its Elastic Fabric Adapter (EFA) networking across instances — also a fixed small-scale domain plus conventional scale-out. Google’s superpod design is the most aggressive of the three in pushing the “one coherent domain” boundary outward: by using OCS to dynamically rewire 144 racks’ worth of chips before resorting to standard data-center networking, Google extends the tightly-coupled fabric to 9,216 chips rather than stopping at a single rack. This is a difference in architectural philosophy, not a simple better-or-worse ranking — each approach reflects what each company’s own networking stack (NVLink/InfiniBand, EFA, or OCS/Jupiter) was built to do well.
Who Should Care
Pod-scale architecture matters most to teams training foundation models large enough to need thousands of accelerators working as one job — at that scale, the resilience of OCS (routing around failed cubes without restarting a training run) can be the difference between a training job completing on schedule and one that stalls repeatedly. For teams doing inference serving, fine-tuning, or smaller-scale training, the smaller 256-chip pod configuration (or a fraction of a superpod via Google’s slicing) is the more realistic unit of consumption, and most of what makes a superpod interesting — OCS fault tolerance, 10 MW-scale liquid cooling — is infrastructure Google manages on your behalf rather than something you configure directly.
Bottom Line
The 9,216-chip number is real, and so is the 42.5 ExaFLOPS figure, but the actual engineering achievement is the Optical Circuit Switching fabric that lets Google treat 144 racks as one reconfigurable, fault-tolerant domain rather than a loose cluster of separately-networked machines. That’s a meaningfully different approach from how Nvidia and AWS scale their own flagship systems, and it’s the detail worth understanding if you’re evaluating TPU pods against GPU or Trainium clusters for large-scale training — not the headline multiples by themselves.
FAQ
What does “9,216 chips in a pod” actually mean physically? It’s 144 racks (“cubes”) of 64 chips each, connected into one domain — 64 chips connect directly via a 3D torus interconnect within a cube, and Optical Circuit Switching links the 144 cubes together.
Is the 42.5 ExaFLOPS figure comparable to supercomputer rankings like the TOP500? Not directly — Google’s 42.5 ExaFLOPS figure is an FP8 AI-compute number, while supercomputer rankings use FP64 precision. Comparing the two (as Google itself does, against the El Capitan supercomputer) illustrates scale but isn’t a true apples-to-apples performance comparison.
What is Optical Circuit Switching (OCS) and why does it matter? It’s a dynamic, reconfigurable optical fabric connecting cubes within a superpod. If a cube or link fails, OCS reroutes around it and swaps in a spare, which avoids restarting a large training job from scratch — a major practical advantage at this scale.
How much memory does an Ironwood superpod have in total? Google states 1.77 petabytes of shared, directly accessible HBM across a full 9,216-chip superpod, based on 192 GB of HBM3E per chip.
Can Ironwood scale beyond a single 9,216-chip superpod? Yes — Google says multiple superpods connect over its standard data-center network (the Jupiter network) to reach clusters of hundreds of thousands of TPUs, though that tier uses conventional networking rather than the OCS fabric used within a superpod.
How does Ironwood’s scale-out compare to Nvidia’s or AWS’s? Nvidia and AWS both use a fixed small-scale, tightly-coupled domain (72 GPUs via NVLink for Nvidia’s NVL72 racks, 64 chips via NeuronLink for AWS’s Trainium2 UltraServers) and then rely on conventional networking (InfiniBand/Spectrum-X, or EFA) to scale further. Google’s OCS-based superpod pushes the tightly-coupled domain out to 9,216 chips before switching to conventional data-center networking — a different point on the same basic trade-off.
AWS runs two separate custom-silicon product lines for machine learning — Trainium and Inferentia — and it’s easy to assume Inferentia is just “last year’s Trainium” repurposed for a cheaper job. It isn’t. Inferentia chips were purpose-built for inference from their first generation in 2018, years before Trainium existed, and the two families have stayed architecturally distinct ever since: different core counts per chip, different memory configurations, and different instance-scaling models. Here’s what AWS has actually published about Inferentia and Inferentia2, how that compares with what AWS says about Trainium, and — importantly — what AWS has not yet announced.
At a Glance
First Inferentia chip
Announced November 2018
Inferentia (gen 1) cores
4 NeuronCores per chip
Inferentia (gen 1) memory
8 GB DDR4 per chip
Inferentia2 cores
2 (second-generation) NeuronCores per chip
Inferentia2 compute
Up to 190 TFLOPS FP16 per chip
Inferentia2 memory
32 GB HBM per chip (4x capacity, 10x bandwidth vs. gen 1)
Instance families
Inf1 (up to 16 chips), Inf2 (up to 12 chips)
Sibling chip for training
Trainium / Trainium2 / Trainium3
Inferentia3
Not officially announced as of this writing
What It Is
Inferentia is AWS’s custom ASIC family dedicated to running trained models cheaply at scale — not training them. The first-generation chip, announced in 2018, packs four first-generation NeuronCores and 8 GB of DDR4 memory per chip (plus additional on-chip memory), supports FP16, BF16, and INT8, and powers Inf1 instances that scale up to 16 chips. AWS’s own figures put Inf1 at up to 2.3x higher throughput and up to 70% lower cost per inference than comparable general-purpose EC2 instances.
Inferentia2 is the current generation, and AWS describes it on its own product page as built for “large-scale generative AI applications.” Each Inferentia2 chip has two second-generation NeuronCores delivering up to 190 TFLOPS of FP16 performance, paired with 32 GB of HBM per chip — AWS states this is 4x the total memory and 10x the memory bandwidth of the first-generation chip. Inferentia2 also adds FP32, TF32, and a configurable FP8 format (cFP8) to the supported data types, along with hardware support for dynamic input sizes, custom C++ operators, and stochastic rounding — all features aimed specifically at serving large transformer-based models efficiently rather than training them from scratch. Inf2 instances scale up to 12 chips and, per AWS, deliver up to 4x higher throughput and up to 10x lower latency than Inf1, plus up to 50% better performance per watt than comparable EC2 instances. AWS calls Inf2 “the first inference-optimized instances in Amazon EC2 to support scale-out distributed inference.”
Inferentia vs. Trainium: Two Different Chips, One SDK
AWS positions these as genuinely separate silicon lines sharing a software stack (the Neuron SDK), not one chip wearing two hats. Trainium — now on its third generation — is built around large-scale distributed training: AWS’s Trainium2 press materials describe a Trn2 instance packing 16 chips for 20.8 peak petaflops of compute, and a Trn2 UltraServer connecting four Trn2 servers (64 chips total, via NeuronLink) for 83.2 peak petaflops, explicitly aimed at training and deploying very large models — AWS cites Project Rainier, an UltraCluster built with Anthropic using hundreds of thousands of Trainium2 chips, as the extreme end of that scale. Notably, AWS’s own Trainium3 messaging describes the chip as delivering “the best economics for high performance AI training and inference at scale,” meaning the newest Trainium generations are increasingly capable inference platforms too — the line between “training chip” and “inference chip” has blurred somewhat as Trainium has matured, even though Inferentia remains the dedicated, inference-only product.
Inferentia2
Trainium2
Primary design target
Inference serving at low cost/latency
Large-scale distributed training (increasingly also inference)
Scale unit
Up to 12 chips per Inf2 instance
16 chips per Trn2 instance; 64 chips per UltraServer
Published compute figure
Up to 190 TFLOPS FP16 per chip
20.8 peak petaflops per Trn2 instance (16 chips)
Published memory figure
32 GB HBM per chip
Not published by AWS at the per-chip level
AWS price-performance claim
Up to 70% lower cost per inference (Inf1) vs. comparable EC2
30–40% better price-performance vs. EC2 P5e/P5en GPU instances
One gap worth flagging plainly: AWS’s own Trainium2 materials do not publish a per-chip HBM memory capacity figure, so this article leaves that cell blank rather than repeating a third-party estimate that isn’t AWS’s own number.
The Cost Claims — And Whose Numbers They Are
AWS’s own benchmarked claims (70% lower cost per inference for Inf1, 50% better performance per watt for Inf2) are AWS’s figures, run against AWS’s own comparable EC2 instances. Beyond those, AWS’s Inferentia page cites a long list of customer-reported results that are not AWS benchmarks and should be read as such: Leonardo.ai and Finch AI each report roughly 80% cost reduction moving to Inferentia-based inference; NTT PC reports 90% lower cost versus current-generation GPU instances; Dataminr reports up to 9x better throughput per dollar; Tomofun reports an 83% lower deployment cost for a specific model (BLIP); Screening Eagle reports a 50% cost reduction; and Metagenomi reports up to 56% lower cost for protein design workloads. These are real customer statements AWS chose to publish, but they reflect specific workloads and migration paths, not a guaranteed savings rate for any given deployment.
Who Should Care
If your workload is primarily serving already-trained models — especially large transformer or generative AI models at high request volume — Inferentia2 and Inf2 instances are built specifically for that cost/latency profile, and AWS’s own throughput-per-dollar claims are a reasonable starting point for a proof-of-concept comparison against GPU instances. If you’re training models from scratch or doing heavy fine-tuning at scale, Trainium is AWS’s intended chip, not Inferentia — Inferentia’s smaller per-chip memory and core count reflect that it was never meant to hold the full state needed for large-scale backpropagation across huge models. Teams already committed to the Neuron SDK get to move between Inferentia and Trainium instance types with a shared tooling stack, which lowers the switching cost of trying both for a given workload.
Bottom Line
Inferentia and Trainium are genuinely different chips solving different problems, not a training/inference relabeling of the same silicon — Inferentia2’s smaller, cheaper-per-chip design with 32 GB of HBM and a focus on scale-out distributed inference is purpose-built for serving cost, while Trainium’s larger per-instance compute pools target training throughput (and, increasingly, inference at extreme scale). As of this writing, AWS has not announced an “Inferentia3,” so Inferentia2 remains the company’s current dedicated inference chip even as newer Trainium generations pick up more of the inference workload.
FAQ
Is there an Inferentia3? Not as of this writing. AWS’s most recent custom-silicon announcements (Trainium3) are for the training line; AWS has not officially announced a third-generation Inferentia chip.
What’s the core difference between Inferentia2 and Trainium2? Inferentia2 is built for low-cost, low-latency inference serving with 32 GB of HBM and up to 190 TFLOPS of FP16 per chip; Trainium2 is built for large-scale distributed training, with AWS citing 20.8 peak petaflops across 16 chips in a single Trn2 instance.
Can Trainium chips be used for inference? Yes — AWS’s own messaging for Trainium3 describes it as delivering “the best economics for high performance AI training and inference at scale,” so the newer Trainium generations aren’t training-only in practice, even though Inferentia remains AWS’s dedicated inference product.
How many Inferentia2 chips fit in one instance? Inf2 instances scale up to 12 Inferentia2 chips per instance, according to AWS.
Are AWS’s cost-savings claims independently verified? The headline throughput and performance-per-watt figures are AWS’s own benchmarks against comparable EC2 instances. The larger percentage savings figures (80-90%) come from individual customer case studies that AWS publishes, not from AWS’s internal benchmarking methodology, and reflect specific workloads rather than a universal guarantee.
Do Inferentia and Trainium share the same software? Yes — both use AWS’s Neuron SDK, which is part of why AWS can position them as a coherent custom-silicon family even though the chips themselves are architecturally distinct.
IBM doesn’t compete with Power processors on raw core count or clock-speed bragging rights — Power has always been sold on reliability, and Power11 continues that pitch almost unchanged in form while adding a genuinely new piece: on-chip AI inferencing acceleration, paired with a separate AI accelerator card aimed squarely at enterprises that can’t tolerate downtime but still want generative AI running next to their core banking or ERP systems. Here’s what IBM actually announced, what’s new relative to Power10, and where the real uncertainty in the public specs sits.
At a Glance
General availability
July 25, 2025
Server tiers
High-end, mid-range, entry — plus IBM Power Virtual Server on IBM Cloud
Named models
E1180, E1150, S1124, S1122
Predecessor
Power10
Capacity gain vs. Power10
Up to 45% more capacity in entry/mid-range systems
2x performance per watt vs. comparable x86 servers (IDC QPI-based)
Resilience target
Designed for 99.9999% uptime (E1180)
Target workloads
Mission-critical, data-intensive: banking, healthcare, retail, government
What It Is
Power11 is IBM’s current-generation Power Architecture processor family, announced on July 8, 2025, and generally available July 25, 2025 across high-end, mid-range, and entry server tiers, as well as through IBM Power Virtual Server on IBM Cloud. It’s the direct successor to Power10, and IBM frames it less as a single chip and more as a platform refresh spanning “its processor, hardware architecture, and virtualization software stack.”
IBM’s named Power11 server models are the E1180 and E1150 (high-end and mid-range) and the S1124 and S1122 (entry). IBM’s own press materials give core configurations in footnotes rather than a single headline number, and those footnotes aren’t fully consistent with each other across different documents — one lists a 4×30-core configuration for the E1150 at 3.0–4.1 GHz, another lists 4×16 cores for the same model. Rather than pick one as the definitive flagship spec, the honest read is that Power11 ships in multiple core-density configurations depending on model and workload tier, and IT buyers evaluating a specific deployment should pull exact core counts and clock speeds from IBM’s configurator or a sales engineer rather than from any single secondary source — including, candidly, from generic specs you’ll find aggregated elsewhere online.
What’s New vs. Power10
IBM’s stated gains over Power10 are capacity and efficiency, not a reinvented microarchitecture. The company claims up to 45% more capacity in entry and mid-range systems, driven by higher core counts in those tiers, and up to 55% better core performance compared with earlier-generation Power processors. On power draw, IBM claims up to 28% better server efficiency when a Power11 system runs in Energy Efficient Mode versus Maximum Performance Mode — a built-in power/performance toggle rather than a fixed design point.
The more interesting architectural addition is on-chip AI inferencing acceleration built directly into the Power11 processor — IBM’s announcement describes this only at a high level, without naming specific matrix-math units or instruction extensions, so treat “on-chip AI acceleration” as a confirmed capability without over-specifying its internals based on announcement language alone. Layered on top of that is the IBM Spyre Accelerator, a separate system-on-a-chip PCIe card that IBM describes as the first accelerator supported on the Power platform, expected in Q4 2025. Spyre’s own architecture is a large enough topic that this site covers it separately — the relevant point here is that Power11’s on-chip acceleration and the add-in Spyre card are two distinct, complementary pieces of IBM’s AI story for Power, not the same thing.
Resilience: The Actual Selling Point
Power has always been sold to customers who measure downtime in dollars per minute, and Power11’s headline numbers reflect that. IBM says the platform is designed for 99.9999% uptime (six nines) based on unplanned-downtime calculations for the E1180, and targets zero planned downtime for routine maintenance through autonomous patching and automated workload movement — though some maintenance scenarios still require Live Partition Mobility rather than being fully automatic. On the security side, IBM cites ransomware threat detection in under one minute via Power Cyber Vault (the guarantee covers the alert itself, with remediation handled separately, up to the cost of a drive replacement), plus built-in NIST-approved quantum-safe cryptography and firmware integrity protection.
Capability
IBM’s stated figure
Unplanned downtime target
99.9999% uptime (E1180)
Planned maintenance
Zero downtime goal via autonomous patching / workload mobility (some cases need Live Partition Mobility)
Power11 is not a general-purpose cloud CPU play the way AWS Graviton or Google Axion are — it’s aimed at enterprises already running core banking, ERP, or similarly non-negotiable systems on Power or AIX/IBM i, who now want to layer AI inferencing onto that same infrastructure without migrating off it. IBM specifically calls out core banking (with Temenos as a named partner), healthcare, retail, and government, and highlights that IBM Power Virtual Server is now certified as a hyperscaler platform for RISE with SAP — relevant if your SAP strategy already runs partly in IBM Cloud. If you’re choosing a CPU platform from a blank slate for a new cloud-native or AI-training workload, Power11’s pitch (uptime, resilience, on-chip inferencing) is a narrower fit than general x86 or Arm options; it’s much more compelling if you’re already a Power/AIX shop evaluating whether to modernize in place.
Bottom Line
Power11 is an incremental, resilience-and-efficiency-focused update to IBM’s enterprise CPU line, not a from-scratch redesign — and IBM’s own public materials are more precise about uptime guarantees and efficiency percentages than about raw core counts, which vary meaningfully by model tier and aren’t fully consistent across IBM’s own footnoted documentation. The real new idea is on-chip inferencing acceleration paired with the separate Spyre card, aimed at letting mission-critical Power shops add AI capability without leaving the platform they already trust for uptime.
FAQ
When did Power11 become generally available? IBM announced Power11 on July 8, 2025, with general availability across high-end, mid-range, and entry servers, plus IBM Power Virtual Server, on July 25, 2025.
What’s the difference between Power11’s on-chip AI acceleration and the Spyre Accelerator? Power11’s on-chip acceleration is built into the processor itself for inferencing tasks; the IBM Spyre Accelerator is a separate PCIe accelerator card, described by IBM as the first accelerator supported on Power, that arrived later (Q4 2025).
How many cores does a Power11 chip have? It varies by model and tier — IBM’s own announcement materials give different core configurations in different footnotes for different server models, so there’s no single universal “Power11 core count”; check IBM’s configurator for a specific model.
What uptime does IBM claim for Power11? IBM says the platform is designed for 99.9999% uptime, based on unplanned-downtime calculations for the E1180 model specifically.
Is Power11 meant to compete with Graviton or Axion for general cloud workloads? Not really — it’s positioned for mission-critical, data-intensive enterprise workloads (banking, healthcare, government) already running on Power/AIX/IBM i, rather than as a general-purpose cloud-native CPU for net-new workloads.
Does Power11 support SAP workloads? Yes — IBM states that IBM Power Virtual Server is certified as a hyperscaler platform for RISE with SAP.
Every few years Nvidia renames its GPU architecture, and every few years the tech press treats it as a bigger GPU with a bigger number on the box. Blackwell is not that. It’s the first Nvidia data-center architecture built from two physically separate dies that behave as one GPU, the first to lean on 4-bit floating point as a first-class training and inference format, and the first sold almost entirely as a rack-scale system rather than a standalone card. Understanding what changed means looking past the marketing multiples and at the actual engineering: the die, the memory, the interconnect, and how those three things combine in the GB200 and GB300 NVL72 systems that are now the default unit of AI infrastructure purchasing.
At a Glance
Architecture name
Blackwell (B200/B100), Blackwell Ultra (B300)
Transistors per GPU
208 billion
Process
Custom TSMC 4NP
Die design
Two reticle-limited dies joined by a 10 TB/s chip-to-chip link, presented as one GPU
Memory type
HBM3E
GB200 NVL72 total GPU memory
13.4 TB across 72 GPUs
GB300 NVL72 total GPU memory
20 TB across 72 GPUs
NVLink generation
Fifth-generation NVLink (scales to 576 GPUs)
NVLink domain bandwidth (NVL72)
130 TB/s
Low-precision format
FP4 via second-generation Transformer Engine (micro-tensor scaling)
Prior generation
Hopper (H100/H200)
What It Is
Blackwell is Nvidia’s successor to the Hopper architecture that powered the H100 and H200. According to Nvidia’s own architecture page, a Blackwell GPU packs 208 billion transistors, built on a custom TSMC 4NP process. The headline engineering change is the die itself: instead of one large monolithic die (Hopper’s approach), Blackwell uses two reticle-limited dies connected by what Nvidia calls a 10 TB/s chip-to-chip interconnect, wired together closely enough that software and the rest of the system see it as a single unified GPU. This is Nvidia’s version of the chiplet transition other chipmakers went through years earlier — necessary because a single die at this transistor count would exceed what TSMC’s lithography can physically print in one piece (the “reticle limit”).
Blackwell Ultra, sold as the B300 and used in GB300 systems, is a refinement rather than a new architecture generation. Nvidia states it delivers 1.5x more dense FP4 Tensor Core FLOPS, 2x the attention-layer acceleration, and 1.5x more HBM3E memory than the original Blackwell GPU — gains that come mostly from a memory and clock refresh rather than a new die design.
Precision, Transformer Engine, and NVLink 5
The second major change is precision support. Blackwell’s second-generation Transformer Engine adds hardware support for FP4 through what Nvidia calls micro-tensor scaling, which the company says “doubles the performance and size of next-generation models that memory can support” compared to running the same workloads in FP8. FP8 itself gets a boost too, handled in part by the NVLink Switch chip’s SHARP (Scalable Hierarchical Aggregation and Reduction Protocol) implementation, which offloads some reduction math from the GPUs to the network fabric. In practice, FP4 is now viable for inference on very large models in a way it wasn’t on Hopper, which topped out at FP8 as its lowest-precision Tensor Core format.
The third change is the interconnect generation. Blackwell ships with fifth-generation NVLink, which Nvidia says scales up to 576 GPUs in a single NVLink domain, versus Hopper’s fourth-generation NVLink topping out at a smaller GPU count. Inside one GB200 or GB300 NVL72 rack, 72 GPUs talk to each other across an NVLink Switch fabric delivering 130 TB/s of aggregate GPU bandwidth, with Nvidia describing that 72-GPU domain as acting like “one giant GPU.” The Grace CPU-to-GPU link inside each superchip runs at 900 GB/s bidirectional, and multi-server scale-out beyond a single rack uses 1.8 TB/s of interconnect per the company’s materials.
GB200 vs. GB300 NVL72: The Rack Is the Product
Nvidia no longer really sells “a GPU” at the top of its lineup — it sells a rack. The GB200 NVL72 and GB300 NVL72 are liquid-cooled, rack-scale systems that each combine 36 Grace CPUs (2,592 Arm Neoverse V2 cores total) with 72 Blackwell-class GPUs, wired together with NVLink 5 into one coherent domain.
Spec (per rack)
GB200 NVL72
GB300 NVL72 (Blackwell Ultra)
GPUs / CPUs
72 / 36
72 / 36
Total GPU memory (HBM3E)
13.4 TB
20 TB
GPU memory bandwidth
576 TB/s
Up to 576 TB/s
FP4 Tensor Core (sparse/dense)
1,440 / 720 PFLOPS
Higher than GB200; exact split not published as clean sparse/dense figures on Nvidia’s page
FP8/FP6 Tensor Core
720 PFLOPS
720 PFLOPS
NVLink bandwidth
130 TB/s
130 TB/s
Networking
Not specified at this level
ConnectX-8 SuperNIC, 800 Gb/s per GPU
CPU memory
17 TB LPDDR5X at 14 TB/s
17 TB LPDDR5X at 14 TB/s
Nvidia’s own vendor benchmarks (stated as projected and subject to change) claim the GB200 NVL72 delivers 30x faster real-time LLM inference than an H100-based cluster under specific test conditions — 50ms token latency, a 1.8-trillion-parameter mixture-of-experts model, 32,768 input tokens — and roughly 4x the training throughput of 4,096 H100 GPUs using 456 GB200 NVL72 systems instead, plus a claimed 25x improvement in energy efficiency from comparing liquid-cooled Blackwell racks against air-cooled Hopper infrastructure at equal power draw. For GB300 NVL72, Nvidia’s figures versus Hopper run even higher — up to 50x AI factory output (explicitly labeled a projection), 10x better responsiveness per user, and 5x throughput per megawatt. These are vendor-stated, system-level comparisons, not independent per-GPU benchmarks, and readers should treat the biggest multiples as illustrative rather than literal guarantees for any specific workload.
Who Should Care
If you’re training or serving models in the hundreds-of-billions-to-trillion-parameter range, the dual-die design and FP4 support are the parts that actually matter to your bill: FP4 lets more of a huge model’s weights and activations fit in the same HBM footprint, which is what makes trillion-parameter inference economically viable at all. If you’re running smaller models, fine-tuning, or classic ML workloads, Blackwell’s gains are real but less transformative — you were likely memory-bandwidth-bound in ways Hopper already handled reasonably well, and the jump from NVLink 4 to NVLink 5 matters most to people building multi-rack training clusters, not single-node inference deployments. Cloud customers renting GB200/GB300 capacity through a hyperscaler inherit these numbers without needing to manage the liquid cooling or rack engineering themselves, which is arguably the more important shift for most IT buyers than any individual spec.
Bottom Line
Blackwell’s real story isn’t a bigger chip — it’s a chip that had to stop being one piece of silicon to keep scaling, paired with a precision format (FP4) that only makes sense once your models are big enough to need it, wrapped in a rack-scale NVLink domain that Nvidia now sells and prices as the actual product. GB300 NVL72 pushes those same ideas further with more memory and faster networking rather than a fundamentally new design. For most buyers, the practical question isn’t “Blackwell or Hopper” anymore — it’s whether your workload is large enough to need a 72-GPU NVLink domain at all, or whether a smaller Hopper-generation deployment still gets the job done at lower cost.
FAQ
Is Blackwell one GPU or two? Physically it’s two reticle-limited dies, but Nvidia’s 10 TB/s chip-to-chip interconnect links them closely enough that software, drivers, and the rest of the system address them as a single GPU.
What’s the difference between Blackwell and Blackwell Ultra (B300)? Blackwell Ultra is a refresh of the same architecture with more HBM3E memory (1.5x), higher dense FP4 throughput (1.5x), and better attention-layer acceleration (2x), rather than a new die design.
Can you buy a single Blackwell GPU, or only full racks? Individual Blackwell GPUs and smaller configurations exist, but Nvidia’s flagship data-center offerings — GB200 NVL72 and GB300 NVL72 — are sold and marketed as complete 72-GPU liquid-cooled rack systems.
What is FP4 and why does it matter? FP4 is a 4-bit floating-point format supported by Blackwell’s second-generation Transformer Engine. It lets large models run with roughly half the memory footprint of FP8 at acceptable accuracy for many inference workloads, which is a major factor in fitting trillion-parameter models into a given HBM budget.
How does NVLink 5 compare to NVLink 4 on Hopper? Nvidia states fifth-generation NVLink scales up to 576 GPUs in one domain, versus a smaller ceiling on Hopper’s fourth-generation NVLink, and within a GB200/GB300 NVL72 rack it delivers 130 TB/s of aggregate bandwidth across 72 GPUs.
Are Nvidia’s performance multiples (like “30x” or “50x”) independently verified? No — these are Nvidia’s own vendor benchmarks, run under specific stated test conditions and in some cases explicitly labeled as projections. They’re useful for directional comparison but shouldn’t be read as guaranteed real-world gains for every workload.
Break a monolith into a few dozen (or a few hundred) microservices, and the network stops being plumbing and becomes the integration layer — every call between services now needs encryption, retries, timeouts, load balancing, and observability that used to be handled inside one process. A service mesh moves that logic out of application code and into shared infrastructure, so individual services don’t each have to reimplement mutual TLS and retry logic. This explainer covers how a mesh works — sidecar proxies versus the newer eBPF-based sidecar-less model — why microservices architectures tend to need one at all, and how three of the leading open-source options, Istio, Linkerd, and Cilium’s service mesh, compare on architecture, maturity, and what their own documentation claims.
At a Glance
What it is
Infrastructure layer that handles service-to-service networking, security, and observability
Classic model
A proxy “sidecar” container injected into every application pod
Newer model
Sidecar-less, using eBPF to move networking logic into the Linux kernel
Envoy-proxy based; supports both sidecar and sidecar-less “ambient” modes; CNCF graduated (2023)
Linkerd
Purpose-built Rust micro-proxy sidecar (linkerd2-proxy); CNCF graduated (2021, first mesh to do so)
Cilium Service Mesh
eBPF datapath for L3/L4, Envoy for L7 parsing; sidecar-free option; Cilium project CNCF graduated (2023)
What Problem This Solves
In a microservices system, every request between services is now a network call, and network calls fail, get intercepted, and need observability in ways in-process function calls never did. Without a mesh, each service team has to implement its own TLS handling, retry and timeout logic, and metrics/tracing instrumentation — inconsistently, and often incorrectly under pressure to ship. A service mesh centralizes that logic: it provides automatic mutual TLS between services so traffic is encrypted and both ends are cryptographically authenticated, traffic management features like retries, timeouts, circuit breaking, and fine-grained routing (for canary releases or A/B testing) without touching application code, and uniform observability — metrics, logs, and distributed traces — generated by the mesh’s infrastructure rather than hand-rolled in every service.
Sidecar vs Sidecar-less (eBPF) Architecture
The traditional mesh architecture injects a proxy container — a “sidecar” — into every application pod, and reroutes all of that pod’s inbound and outbound traffic through it (typically via iptables rules), so the proxy can enforce mTLS, apply routing rules, and emit metrics transparently to the application. This is how Istio’s sidecar mode and Linkerd both work by default. The newer alternative uses eBPF (extended Berkeley Packet Filter), a Linux kernel technology that lets programs run safely inside the kernel’s networking path, to handle L3/L4 traffic (IP, TCP, UDP) without a per-pod proxy process at all — Cilium’s service mesh and Istio’s newer “ambient mode” both use variations of this approach. Per Cilium’s own documentation, “protocols at the application layer such as HTTP, gRPC, and DNS are parsed using a proxy such as Envoy,” meaning even sidecar-less designs still fall back to a proxy for Layer-7-aware features — the eBPF path handles the lower-level, higher-volume traffic, while a shared (not per-pod) Envoy instance handles the parts that genuinely require application-layer parsing.
Why Microservices Need This: mTLS, Traffic Management, Observability
The three capabilities a mesh centralizes map directly onto problems that get worse as a system grows. mTLS gives every service cryptographic proof of who it’s talking to and encrypts the traffic, which matters once services are communicating across namespaces, clusters, or clouds and can no longer assume the internal network itself is trustworthy — this connects directly to the identity-centric thinking behind zero trust architectures. Traffic management — Istio’s own documentation highlights request routing, fault injection, traffic shifting, circuit breaking, traffic mirroring, and load balancing as core tasks — lets operators change how traffic flows (for a canary rollout, a failover, or a chaos test) without redeploying the services themselves. Observability gives every team the same metrics, logs, and distributed traces for free, rather than each service instrumenting itself differently (or not at all).
Istio vs Linkerd vs Cilium Service Mesh
Dimension
Istio
Linkerd
Cilium Service Mesh
Data plane proxy
Envoy (general-purpose proxy), sidecar or ambient “ztunnel”
linkerd2-proxy, a purpose-built micro-proxy written in Rust
eBPF kernel datapath for L3/L4; Envoy for L7 (HTTP/gRPC/DNS) parsing
Sidecar requirement
Optional — supports classic sidecar mode and sidecar-less “ambient mesh”
Required — proxy injected into every meshed pod
Optional — can run without per-pod sidecars; falls back to Envoy for L7
mTLS
Built-in, via Istio’s identity/certificate system
Built-in by default via the Identity service (a TLS certificate authority) signing proxy certs
Supported; Cilium’s own documentation currently lists mutual authentication as a “Beta” feature
CNCF status
Graduated, July 2023
Graduated, July 2021 — the first service mesh project to graduate
Cilium (the overall project) graduated, October 2023
Documented emphasis
Breadth of traffic-management features and multi-mode flexibility (sidecar + ambient)
Simplicity and a minimal, purpose-built proxy footprint
Kernel-level efficiency; avoiding a second proxy process per pod for most traffic
A few caveats worth flagging directly from the documentation: Linkerd’s own architecture docs make no quantitative performance claims and don’t publish head-to-head benchmarks against Istio or Cilium. Cilium’s launch material (from Isovalent, the company founded by Cilium’s creators) does include comparative latency charts for its sidecar-free design versus a two-sidecar Istio setup, but presents them as illustrative figures in a vendor blog post rather than as a reproducible, numbered benchmark — so readers should treat them as a vendor claim, not an independently verified result. Istio’s ambient mode and Cilium’s service mesh are both newer than their respective projects’ sidecar-based roots, and both are evolving faster than their sidecar counterparts.
Trade-Offs
Istio: The broadest feature set and strongest ecosystem/tooling support, but historically the heaviest resource footprint and steepest operational learning curve in sidecar mode (mitigated, but not eliminated, by ambient mode).
Linkerd: Praised in its own documentation and by the CNCF for simplicity and a lightweight, purpose-built proxy; narrower feature surface than Istio, and still requires a sidecar in every meshed pod.
Cilium Service Mesh: Lowest per-pod overhead when the sidecar-free path is used, and it comes bundled with Cilium’s broader eBPF-based networking/CNI capabilities; L7 features still depend on Envoy, and its mTLS/mutual-authentication feature is documented as Beta at the time of writing.
General trade-off: All three add real operational complexity (certificate rotation, proxy upgrades, policy CRDs) — a mesh is a net win once the number of services and the cross-service traffic justify it, and a net cost for a handful of services that don’t need mTLS or fine-grained traffic shaping yet.
Bottom Line
All three meshes solve the same core problem — mTLS, traffic management, and observability for service-to-service traffic — but make different architectural bets. Istio trades operational weight for the broadest feature set and now offers a sidecar-less path of its own via ambient mode. Linkerd bets on a minimal, purpose-built Rust proxy and operational simplicity, and was the first service mesh to reach CNCF graduation. Cilium bets on pushing as much as possible into the kernel via eBPF, falling back to Envoy only where Layer-7 parsing genuinely requires it. For teams already running Cilium as their CNI, its service mesh is a natural extension; for teams wanting the most mature, broadly supported option, Istio and Linkerd — both CNCF-graduated — remain the safer defaults, with the sidecar-vs-sidecar-less choice increasingly available within Istio itself.
FAQ
Do I need a service mesh for a small number of microservices? Usually not. The operational overhead (certificate management, proxy upgrades, added latency hops) tends to outweigh the benefit until the number of services and the volume of east-west traffic make hand-rolled mTLS and retry logic unmanageable.
What does “sidecar-less” actually mean? Instead of injecting a dedicated proxy container into every application pod, networking logic runs via eBPF programs in the Linux kernel (for L3/L4) and, where needed, through a shared rather than per-pod proxy for L7 protocols.
Is Istio’s ambient mode the same as Cilium’s approach? They’re conceptually similar — both avoid a per-pod sidecar — but Istio’s ambient mode uses a shared per-node “ztunnel” component over a secure tunneling protocol, while Cilium relies on eBPF as the in-kernel datapath directly; the two are independent implementations, not the same technology.
Which project is the most mature? By CNCF graduation date, Linkerd was first (2021), followed by Istio (2023) and Cilium as an overall project (2023); graduation reflects governance and adoption maturity as judged by the CNCF, not a ranking of technical capability.
Can I run more than one of these at once? Not typically on the same workloads — they compete for the same traffic-interception point (iptables rules or eBPF hooks). Some setups do combine Cilium as the CNI/networking layer with Istio’s control plane for policy, since Cilium can act purely as the dataplane underneath.
For most of enterprise IT history, security was architected like a castle: build a strong wall (the firewall and VPN), and trust almost everything once inside it. That model assumed the network perimeter was a meaningful security boundary — an assumption remote work, BYOD, and cloud-hosted services have steadily eroded. Zero Trust Architecture (ZTA) is the industry’s formal answer, codified by the U.S. National Institute of Standards and Technology in Special Publication 800-207. Its central claim is blunt: no user, device, or network location should be trusted by default, no matter where it sits relative to a firewall. Access should instead be evaluated, continuously, per request, based on verified identity and device posture. This explainer covers NIST’s own tenets, the architecture’s core components, the case study that inspired much of the industry’s thinking — Google’s BeyondCorp — and how modern ZTNA products relate to the concept without turning this into a product comparison.
At a Glance
Defining standard
NIST Special Publication 800-207, “Zero Trust Architecture” (August 2020)
Core assumption
No implicit trust based on network location or asset ownership
Policy Engine, Policy Administrator, Policy Enforcement Point
Originating case study
Google BeyondCorp, built after the 2009 “Operation Aurora” attacks
Replaces (in part)
Perimeter firewalls and traditional full-network-access VPNs
Modern implementations
ZTNA products such as Cloudflare Access and Zscaler Private Access
What Problem This Solves
A traditional VPN authenticates a user once, at connection time, and then typically places their device on the internal network as if it were physically in the building — often with broad reachability to internal systems. If that device is compromised, or the credentials are stolen, an attacker inherits a large amount of implicit trust in one step; this is the “soft, chewy center” problem of perimeter security, where authentication is a one-time gate rather than a continuous check. NIST SP 800-207 defines zero trust as “a collection of concepts and ideas designed to minimize uncertainty in enforcing accurate, least-privilege, per-request access decisions,” explicitly moving the trust boundary away from the network and onto individually verified users, devices, and sessions.
The Seven Tenets of Zero Trust, Per NIST
NIST SP 800-207 lays out seven basic tenets that define the model, independent of any specific product:
All data sources and computing services — including IoT devices, SaaS, and personally owned devices — are treated as resources.
All communication is secured regardless of network location; location alone never implies trust.
Access to individual resources is granted per-session, using the fewest privileges needed to complete that specific task.
Access decisions are dynamic, drawing on client identity, requesting-asset state, and behavioral or environmental attributes.
The enterprise continuously monitors and measures the integrity and security posture of all owned and associated assets.
Authentication and authorization are strictly enforced and dynamically re-evaluated before access is granted, not just once at login.
The enterprise collects data on asset state, network traffic, and access requests to continuously improve its policy and enforcement.
Core Components: How a Zero Trust Architecture Actually Decides
NIST’s reference architecture splits the decision-making logic into distinct, named components rather than leaving “access control” as a black box:
Component
Role
Policy Engine (PE)
Makes the final decision to grant, deny, or revoke access to a resource, using enterprise policy plus external inputs like threat intelligence, and logs every decision.
Policy Administrator (PA)
Executes the Policy Engine’s decision by establishing or tearing down the actual communication path, and issues session-specific credentials.
Policy Enforcement Point (PEP)
Enables, monitors, and terminates the connection between a subject and a resource — may be a single gateway or split into a client-side agent and a resource-side gateway.
The Policy Engine and Policy Administrator together are sometimes referred to as the Policy Decision Point (PDP). In practice, every access attempt flows: subject requests access → PEP intercepts it → PDP (PE + PA) evaluates identity, device posture, and context → PA instructs the PEP to allow or block the connection, typically with a short-lived, session-scoped credential rather than standing network access.
Identity Verification, Least Privilege, and Micro-Segmentation
Three concepts do most of the practical work in a zero trust deployment. Identity verification authenticates both the human subject and the requesting device as separate, discrete steps — a valid user on a compromised or unmanaged device is still a denial case. Least privilege, per NIST’s tenet four, restricts both the visibility and the accessibility of resources to only what a specific session needs, rather than granting standing access to an entire network segment or application suite. Micro-segmentation is the network-layer implementation of that principle: individual resources, or small groups of them, sit behind their own gateway enforcement point (a next-generation firewall, an intelligent switch, or a host-based agent) rather than one flat internal network — so that even a successfully authenticated session only ever reaches the one resource it was authorized for, not everything else reachable from the same subnet.
Case Study: Google BeyondCorp
Google’s BeyondCorp is widely cited as the originating real-world case study for zero trust thinking, predating NIST SP 800-207 by roughly a decade. Google began building it after the 2009 “Operation Aurora” attacks, which demonstrated the risk of relying on network-perimeter trust. BeyondCorp shifted access decisions for Google’s own internal applications away from VPNs and onto a combination of a Trust Inferrer (assessing device security posture and ownership), an Access Control Engine (evaluating policy, device state, and the specific resource requested), and a Device Inventory Database (tracking devices by certificate-based identity). Google described the architecture in a multi-part series published in the journal ;login: between 2014 and 2018, and the model has since become the reference point the broader ZTNA product category is measured against.
Modern ZTNA Products in Practice
Commercial Zero Trust Network Access (ZTNA) products implement the same core idea — identity- and context-based access to individual applications instead of network-wide VPN access — as a managed service. Cloudflare Access, part of Cloudflare’s broader Zero Trust platform, enforces per-application access policies evaluated against identity provider sign-in, device posture signals, and location, acting as a reverse-proxy-style Policy Enforcement Point in front of each application rather than granting access to a network. Zscaler Private Access (ZPA) takes a similar approach, brokering connections between an authenticated user’s device and a specific private application through its cloud, without ever placing the device on the corporate network or exposing a listening port to the internet. Both are concrete implementations of the same NIST tenets described above — they differ in deployment model and ecosystem integration, but the underlying principle (verify identity and device state continuously, grant the narrowest possible access, per session) is the same one Google formalized internally and NIST later standardized.
Trade-Offs
Pro: Eliminates the “flat internal network” blast radius — a compromised credential or device no longer implies broad lateral access.
Pro: Access decisions use richer, continuously re-evaluated signals (device posture, behavior, context) instead of a one-time login check.
Pro: Works naturally for remote and BYOD scenarios, since network location is no longer a factor in the trust decision.
Con: Requires a mature identity and device-inventory foundation (per NIST’s own tenets) before it can be implemented effectively — it’s not a single product you install.
Con: Migration from a perimeter/VPN model is typically incremental and can take years for large, legacy-heavy organizations.
Con: Continuous verification and fine-grained policy add operational complexity and new failure modes (e.g., a misconfigured policy engine can lock out legitimate access) compared to a single VPN gateway.
Bottom Line
Zero trust is not a product category — it’s an architectural principle, formally defined by NIST SP 800-207, that replaces “trusted because it’s inside the network” with “verified, for this session, based on identity and context.” Google’s BeyondCorp proved the model at scale years before it had a name, and today’s ZTNA products (Cloudflare Access, Zscaler Private Access, and others) are commercial implementations of the same underlying tenets. Organizations evaluating a move beyond VPN-based access should treat the NIST tenets as the specification to measure any vendor or internal build against, not the other way around.
FAQ
Is Zero Trust a specific product you can buy? No. It’s an architectural model defined by NIST SP 800-207. Products like Cloudflare Access or Zscaler Private Access are implementations of the model, not the model itself.
Does Zero Trust mean no VPN at all? Not necessarily by definition, but in practice ZTNA is usually adopted specifically to replace the broad network-level access a traditional VPN grants with narrower, per-application, per-session access.
What’s the difference between a Policy Decision Point and a Policy Enforcement Point? The Policy Decision Point (the Policy Engine plus the Policy Administrator) makes the access decision. The Policy Enforcement Point is the component that actually opens, monitors, or closes the connection based on that decision.
Is BeyondCorp the same thing as NIST Zero Trust Architecture? They’re closely related but not identical — BeyondCorp is Google’s own internal implementation, built before NIST SP 800-207 was published, and is widely cited as a key real-world influence on the standard’s thinking.
What is micro-segmentation, in plain terms? Instead of one flat internal network where reaching one server often means you can reach many others, each resource (or small group of resources) sits behind its own access gateway, so authorization is evaluated resource-by-resource.
Can a small company realistically adopt Zero Trust, or is this only for large enterprises? The tenets scale down conceptually — identity-based, least-privilege, per-session access — but NIST’s own guidance notes it requires an identity and asset-management foundation first, which is often the bigger lift for smaller organizations than the access-control layer itself.
Every compiler, interpreter, configuration-file reader, or query-language engine starts with the same job: turning a flat stream of tokens into a structured tree the rest of the program can walk. That job is parsing, and for hand-written parsers, two techniques dominate: recursive descent, which maps each grammar rule directly onto a function, and Pratt parsing, a specialized technique for expressions that handles operator precedence without a function explosion. Recursive descent is simple and works beautifully for most of a language’s grammar — statements, declarations, blocks — but it gets awkward exactly where arithmetic-style expressions live, because precedence and associativity don’t map cleanly onto “one function per rule.” Pratt parsing exists specifically to fix that. This explainer covers how each technique works, where recursive descent breaks down, and how Pratt parsing’s precedence-driven loop solves the same problem with far less code.
At a Glance
Recursive descent
One parsing function per grammar rule, calling each other top-down
Pratt parsing
One generic expression-parsing loop driven by per-token precedence (binding power)
Best suited for
Recursive descent: statements/structure. Pratt: expressions with operators
Precedence handling
Recursive descent: a separate function per precedence level. Pratt: a precedence number per operator
Adding a new operator
Recursive descent: insert/renumber grammar functions. Pratt: register one new table entry
Origin
Pratt parsing comes from Vaughan Pratt’s 1973 paper “Top Down Operator Precedence”
What Problem This Solves
Parsing takes the token stream produced by a lexer (e.g. NUM(1), OP(+), NUM(2), OP(*), NUM(3) for the text 1 + 2 * 3) and builds an abstract syntax tree that reflects the language’s grammar rules — in particular, which operations bind more tightly than others. A parser that got this wrong would parse 1 + 2 * 3 as (1 + 2) * 3 instead of the mathematically correct 1 + (2 * 3). Both recursive descent and Pratt parsing are top-down parsing strategies — they start from the whole expression and work down into its parts — but they differ sharply in how they encode precedence, which is the crux of the problem this explainer is about.
How Recursive Descent Works
Recursive descent translates a grammar almost mechanically: each production rule becomes a function, and each function calls the functions for the rules it references. A grammar rule like statement -> if_statement | while_statement | expr_statement becomes a parse_statement() function that peeks at the next token and dispatches to parse_if(), parse_while(), or parse_expr_statement(). This is simple to write, simple to debug (a stack trace literally shows you the grammar path taken), and it maps cleanly onto most of a real language’s syntax — declarations, blocks, control flow. It struggles specifically with left-recursive rules (a rule that refers to itself as its own first symbol, which causes infinite recursion in a naive top-down implementation) and, most relevantly here, with operator precedence in expressions.
The standard recursive-descent fix for precedence is to write one function per precedence level, each calling the next tighter-binding level before trying to consume an operator at its own level. For a language with just +, -, *, and /, that’s already parse_additive() calling parse_multiplicative() calling parse_unary() calling parse_primary(). Real languages have far more precedence levels than that — in his widely cited article on the subject, developer Bob Nystrom points out that JavaScript’s expression grammar has roughly seventeen distinct precedence levels. Written the naive recursive-descent way, that means roughly seventeen near-identical functions, each differing only in which operator tokens it checks for and which function it calls next. Associativity (does a - b - c group as (a - b) - c or a - (b - c)?) has to be hand-coded into each of those functions separately, and adding a new operator at a new precedence level means inserting a new function into the chain and renumbering everything below it.
What Pratt Parsing Does Differently
Pratt parsing — sometimes called “top-down operator precedence parsing,” after Vaughan Pratt’s original 1973 title — replaces that chain of functions with a single loop and a table. Every token type that can start an expression (a number, a variable, a unary -, an opening parenthesis) gets a prefix handler. Every token type that can appear after an expression as an operator (+, *, etc.) gets an infix handler and a precedence number, sometimes called its “binding power.” The core function, often called parse_expression(min_precedence), works like this: parse one prefix expression to get a starting value, then repeatedly look at the next operator — as long as its precedence is at least as high as the minimum precedence the caller asked for, consume it, recursively parse its right-hand side (passing in that operator’s own precedence, which is what produces correct left-associativity), and fold the result into the running expression. Precedence is no longer encoded as “which function am I in” — it’s a plain number compared at one single point in the code, so adding a new operator means adding one entry to a table, not a new function in a chain.
Recursive Descent vs Pratt Parsing
Aspect
Recursive Descent (naive)
Pratt Parsing
Functions needed for N precedence levels
N separate functions
1 function + N table entries
Adding a new operator
Insert a function, renumber the chain
Register one prefix/infix handler with a precedence number
Associativity
Hand-coded per level (loop vs recursion choice)
Controlled by passing precedence vs precedence+1 to the recursive call
Readability of the grammar structure
Very explicit — one rule, one function
Less explicit — precedence lives in a table, not the control flow
Best fit
Statements, declarations, overall language structure
Expressions with many operators and precedence levels
Code Example: A Minimal Pratt Parser in Python
The example below parses simple arithmetic with +, -, *, /, and parentheses into a nested tuple AST, using the precedence-climbing form of Pratt parsing (a restricted version that handles binary operators without a full prefix/infix table). Calling parse("1 + 2 * 3") correctly returns ('+', 1, ('*', 2, 3)), and parse("(1 + 2) * 3") returns ('*', ('+', 1, 2), 3) — multiplication binds tighter than addition in the first case, while the parentheses override that in the second.
import re
TOKEN_RE = re.compile(r"\s*(?:(\d+)|(.))")
PRECEDENCE = {"+": 1, "-": 1, "*": 2, "/": 2}
def tokenize(text):
tokens = []
for num, op in TOKEN_RE.findall(text):
if num:
tokens.append(("NUM", int(num)))
elif op:
tokens.append(("OP", op))
return tokens
class Parser:
def __init__(self, tokens):
self.tokens = tokens
self.pos = 0
def peek(self):
return self.tokens[self.pos] if self.pos < len(self.tokens) else (None, None)
def advance(self):
tok = self.peek()
self.pos += 1
return tok
def parse_expression(self, min_precedence=0):
kind, value = self.advance()
if kind == "NUM":
left = value
elif kind == "OP" and value == "(":
left = self.parse_expression(0)
self.advance() # consume the matching ")"
else:
raise SyntaxError(f"Unexpected token: {value}")
while True:
kind, op = self.peek()
if kind != "OP" or op not in PRECEDENCE:
break
precedence = PRECEDENCE[op]
if precedence < min_precedence:
break
self.advance() # consume the operator
# precedence + 1 on the right side gives left-associativity
right = self.parse_expression(precedence + 1)
left = (op, left, right)
return left
def parse(text):
return Parser(tokenize(text)).parse_expression()
print(parse("1 + 2 * 3")) # ('+', 1, ('*', 2, 3))
print(parse("(1 + 2) * 3")) # ('*', ('+', 1, 2), 3)
Trade-Offs
Pro (Pratt): Adding an operator or changing precedence is a one-line table edit, not a restructuring of the function chain.
Pro (Pratt): Naturally handles prefix, infix, postfix, and mixfix operators (like a ? b : c) within the same uniform mechanism.
Pro (Recursive descent): The control flow directly mirrors the grammar, which makes it easier for newcomers to read and debug, especially outside of pure expression parsing.
Con (Pratt): Precedence lives in a table rather than in the code’s structure, which can make the grammar less self-documenting to someone unfamiliar with the technique.
Con (Recursive descent): Scales poorly as the number of precedence levels grows — real language grammars (e.g. JavaScript’s ~17 levels) turn into long chains of near-duplicate functions.
Shared limitation: Both are typically hand-rolled for expressions; for very large or ambiguous grammars, parser-generator tools (LALR, PEG) may be a better fit than either.
Bottom Line
Recursive descent and Pratt parsing aren’t competitors so much as a division of labor: use recursive descent for the overall shape of a language — statements, declarations, blocks — and drop into a Pratt-style parse_expression(precedence) loop the moment you hit arithmetic-like expressions with multiple operators and precedence levels. Nearly every production hand-written parser for a language with infix operators — including real-world interpreters and compilers — uses exactly this hybrid, because it avoids both recursive descent’s function explosion and the complexity of a full parser-generator toolchain.
FAQ
Is Pratt parsing a replacement for recursive descent? No — it’s typically combined with it. Recursive descent handles the overall grammar; a Pratt-style loop is dropped in specifically for expression parsing.
What does “binding power” mean? It’s another name for an operator’s precedence value inside the Pratt algorithm — how strongly it “pulls” neighboring operands into its own sub-expression versus letting an outer operator claim them.
What are “nud” and “led”? Terms from Vaughan Pratt’s original 1973 paper for a token’s “null denotation” (how it parses with nothing to its left — i.e. a prefix handler) and “left denotation” (how it parses with an already-parsed expression to its left — i.e. an infix handler). Modern explanations, including Bob Nystrom’s, often use the friendlier terms “prefix” and “infix” parselets instead.
Does Pratt parsing handle right-associative operators like exponentiation? Yes — passing the operator’s own precedence (rather than precedence + 1) to the recursive call on the right-hand side produces right-associativity instead of left.
Why doesn’t the code example handle left recursion directly? It doesn’t need to — the while loop inside parse_expression handles left-leaning chains of operators (like a - b - c) iteratively, which is precisely how Pratt parsing avoids the infinite-recursion problem that a naive left-recursive grammar rule would cause in straight recursive descent.
For four decades, the dominant systems programming languages — C and C++ — have made a trade that most developers only notice when it fails: they hand full control of memory to the programmer and trust the programmer to get it right every single time. That trust is expensive. Microsoft has reported that roughly 70 percent of the security vulnerabilities it fixes each year, across more than a decade of patches, are memory-safety issues, and Google has independently reported the same figure for serious Chrome security bugs. Rust was designed specifically to make these bug classes — use-after-free, double-free, buffer overflows, and data races — unrepresentable in a program that compiles, without adding a garbage collector or a runtime safety net. It does this through a compile-time analysis called the borrow checker, built on three interlocking ideas: ownership, borrowing, and lifetimes. This explainer walks through that model and shows, with a real compiler error and its fix, exactly how it catches a bug before the program ever runs.
At a Glance
Core guarantee
No use-after-free, double-free, or data races in “safe” Rust code
Enforcement mechanism
Static analysis at compile time (the borrow checker) — no garbage collector
Ownership rule
Every value has exactly one owner at any given time
Borrowing rule
Either one mutable reference, or any number of immutable references — never both at once
Lifetime rule
A reference can never outlive the data it points to
Runtime cost of the checks
None — all analysis happens before the binary is produced
Escape hatch
unsafe blocks, which opt back into manual, unchecked memory operations
What Problem This Solves
“Memory safety” refers to a cluster of related bug classes that all come from the same root cause: a program accessing memory it should not be allowed to access. The usual suspects are use-after-free (reading or writing through a pointer after the memory it points to has been freed), double-free (releasing the same block of memory twice, corrupting the allocator’s internal state), buffer overflows and out-of-bounds reads/writes (accessing an array or buffer past its allocated bounds), and data races (two threads reading and writing the same memory without synchronization, producing undefined results). MITRE’s 2024 CWE Top 25 Most Dangerous Software Weaknesses list ranks Out-of-bounds Write (CWE-787) at #2, Out-of-bounds Read (CWE-125) at #6, and Use After Free (CWE-416) at #8 — these are not rare, exotic bugs, they are consistently among the most frequently exploited weaknesses in software shipped today.
The scale is what makes this a systemic problem rather than a handful of unlucky bugs. In a 2019 MSRC blog post, Microsoft stated that “~70% of the vulnerabilities Microsoft assigns a CVE each year continue to be memory safety issues,” based on an analysis of roughly a decade of its own patch data. Google reached a nearly identical conclusion independently: in a September 2021 post on its Security Blog, the Chrome team wrote that “more than 70% of our severe security bugs are memory safety problems.” In November 2022, the U.S. National Security Agency published a Cybersecurity Information Sheet explicitly citing both figures and recommending that organizations move toward memory-safe languages where feasible. When two unrelated engineering organizations, analyzing two unrelated codebases, arrive at the same number, it stops looking like coincidence and starts looking like a property of the tools.
How C and C++ Leave This to the Runtime
C and C++ give the programmer raw pointers and manual allocation (malloc/free, new/delete) with no compiler-enforced tracking of who is responsible for freeing what, or whether a pointer is still valid. Freeing memory does not erase it or invalidate every pointer to it — it just marks the block available for reuse. A pointer that still refers to that address (“dangling”) will often still “work” until the memory is reused for something else, at which point reads and writes through it silently corrupt unrelated data. The compiler does not reject this code; the behavior is classified as “undefined,” meaning anything from a crash to a silent miscalculation to, in the worst case, attacker-controlled code execution. CVE-2014-0160 (“Heartbleed”), an out-of-bounds read in OpenSSL’s C codebase, is one of the most widely documented real-world examples of exactly this class of bug reaching production for years before detection. None of this requires programmer carelessness in the usual sense — it requires only that a large, evolving codebase have a single lapse anywhere in its call graph.
Ownership: Rust’s Core Model
Rust’s starting rule is simple: every value has exactly one owner at a time. When you assign a heap-allocated value like a String to a new variable, ownership moves to that variable, and the original variable becomes invalid — the compiler will refuse to compile any later use of it. When the owner goes out of scope, Rust automatically calls the value’s destructor and frees its memory, deterministically, with no garbage collector deciding when to run. Because exactly one piece of code is ever responsible for freeing a given value, double-free becomes structurally impossible in safe Rust: there is never a second owner left around to free the same memory again.
Borrowing and the Aliasing Rule
Moving ownership every time you want to use a value would make most programs unworkable, so Rust also lets you borrow a value through a reference without taking ownership of it. The rule governing borrows is where the real payoff shows up: at any given point in the program, you may have either one mutable reference (&mut T) or any number of immutable references (&T) to a value — never both kinds alive at the same time. This is sometimes called the “aliasing XOR mutability” rule. It directly prevents data races: if only one piece of code can ever hold a mutable reference while all other references are read-only, there is no way for two pieces of code to simultaneously read and write — or write and write — the same memory without going through an explicit, checked synchronization type such as Mutex or RwLock. The same rule also prevents the classic “reading through a reference after the underlying collection resized and moved” bug, as the code example below demonstrates.
Lifetimes: Making “How Long” Part of the Type System
Every reference in Rust has a lifetime: the span of the program during which it is guaranteed to point at valid data. Most of the time the compiler infers lifetimes automatically. When a function’s signature is ambiguous about how long an input and output reference should be related — for example, a function that takes two string references and returns whichever is longer — the programmer writes an explicit lifetime annotation such as 'a to tell the compiler “the reference I return lives no longer than the shorter of these two inputs.” Lifetime annotations don’t change how long anything actually lives in memory; they only describe relationships the compiler then checks. The practical effect is that a function can never hand back a reference to data that is about to be destroyed — the kind of mistake that, in C or C++, produces a dangling pointer discovered only when something crashes much later.
How the Borrow Checker Catches This at Compile Time
Modern Rust (since the 2018 edition) uses an analysis called non-lexical lifetimes (NLL), which ends a borrow at its last actual use in the code, rather than at the end of its enclosing block. This makes the checker precise enough to accept common, correct patterns while still rejecting the unsafe ones. The example below is a well-known case: borrowing the first element of a growable vector, then trying to push a new element onto that same vector while the borrow is still “alive.” Pushing can force the vector to reallocate and move its entire contents to a new memory address, which would leave first pointing at freed memory — a use-after-free. The borrow checker rejects this at compile time, before any such reallocation could ever happen at runtime.
// This does NOT compile. The immutable borrow `first` is still
// considered "alive" at the point where `v.push(4)` tries to
// take a mutable borrow of `v` to grow it.
fn broken() {
let mut v = vec![1, 2, 3];
let first = &v[0];
v.push(4);
println!("{}", first);
}
// rustc's error (abridged):
// cannot borrow `v` as mutable because it is also
// borrowed as immutable
// This compiles. Thanks to non-lexical lifetimes, the compiler
// sees that `first` is never used again after the println!, so
// its borrow has already ended before `v.push(4)` runs.
fn fixed() {
let mut v = vec![1, 2, 3];
let first = &v[0];
println!("{}", first); // last use of `first` — borrow ends here
v.push(4); // OK: no active borrow when we mutate `v`
}
Trade-Offs
Pro: Use-after-free, double-free, and unsynchronized data races are caught at compile time, not discovered in production or by an attacker.
Pro: All of this is static analysis — there is no garbage collector, no runtime borrow-tracking, and no performance penalty in the compiled binary.
Pro: The same rules that prevent memory bugs also tend to surface certain logic bugs (like aliased mutation) earlier in development.
Con: The learning curve is real — “fighting the borrow checker” is a common experience for programmers used to C, C++, Java, or Python, especially around self-referential data structures and graphs.
Con: Some valid, safe patterns (e.g., certain graph or GUI widget structures) require extra machinery like Rc<RefCell<T>> or arena allocators to satisfy the checker.
Con: Memory safety is not the same as correctness — Rust does not prevent logic errors, memory leaks (which are safe but still wasteful), or vulnerabilities unrelated to memory, such as injection or authentication flaws.
Con:unsafe blocks are sometimes necessary (for FFI, certain low-level optimizations, or OS interfaces) and reintroduce the possibility of memory-safety bugs within that scope.
Bottom Line
Rust’s borrow checker is not a style preference or a lint — it is a formal set of rules about ownership and aliasing that, enforced at compile time, make an entire class of bugs responsible for a documented majority of serious security vulnerabilities in memory-unsafe languages structurally impossible to write in safe Rust. That is precisely why the NSA, alongside Microsoft’s and Google’s own internal data, now points to memory-safe languages as a strategic mitigation rather than a nice-to-have. For teams building new systems-level software — network services, parsers, embedded firmware, browser engines — the upfront cost of learning ownership and borrowing is traded for the removal of one of the largest sources of critical vulnerabilities in the industry’s own data.
FAQ
Does Rust eliminate all security vulnerabilities? No. It eliminates memory-safety bugs in safe Rust code specifically. Logic errors, injection flaws, authentication bypasses, and vulnerabilities inside unsafe blocks or in C libraries linked via FFI are all still possible.
What is unsafe Rust, and doesn’t it defeat the whole point? unsafe is a keyword that lets a specific, explicitly marked block of code perform operations the borrow checker can’t verify, such as raw pointer dereferencing or calling into C. It’s intentionally rare, explicit, and auditable — the rest of the codebase stays checked.
Is Rust slower than C or C++ because of all these checks? No. Ownership, borrowing, and lifetime checks happen entirely at compile time and leave no trace in the compiled binary — there is no runtime borrow-tracking overhead, unlike a garbage-collected language’s runtime.
Can the borrow checker reject programs that are actually safe? Yes — it is deliberately conservative. Some patterns that a human can reason are safe (certain data structures with internal aliasing) aren’t provable by the checker’s current rules, and need wrapper types like RefCell or restructuring to compile.
What’s the difference between ownership and borrowing? Ownership determines who is responsible for freeing a value and lasts until that owner goes out of scope. Borrowing lets other code read (or, exclusively, write) a value temporarily without taking that responsibility.
Why are Microsoft and Google talking about this if they mostly ship C and C++? Because their own vulnerability data — patches issued over many years across Windows and Chrome respectively — showed memory safety bugs as the dominant category of serious security fixes, which is why both now invest in memory-safe language adoption (including Rust) for new and rewritten components.
Visual regression testing has moved well past pixel-diffing screenshots. Today’s tools use AI to tell the difference between a meaningless rendering artifact and a genuine visual bug, and to adapt as a UI evolves instead of breaking on every minor change. Applitools, Percy (from BrowserStack), and Chromatic are the three most widely used platforms for this, each with a different approach to how it counts usage and bills for it. This is specifically about visual/UI regression testing — not functional or API testing tools — and every price below comes from each vendor’s own current pricing page.
At a Glance
Applitools
AI-powered “Visual AI” validation, plus AI-driven functional/API testing on higher tiers; priced by checkpoints
Percy
BrowserStack’s visual testing product; priced by screenshots, with real mobile device coverage on higher tiers
Chromatic
Visual testing built around Storybook/component snapshots; priced by monthly snapshots
Chromatic is the easiest and cheapest entry point, especially for teams already using Storybook, with a genuinely free tier (5,000 snapshots/month) and a clear path up to paid tiers. Percy is the strongest choice if you’re already in the BrowserStack ecosystem or need real mobile device coverage alongside visual testing, also with a usable free tier. Applitools is the most feature-rich and enterprise-oriented of the three — its Visual AI engine and optional AI-driven functional testing are well-regarded — but its only publicly priced tier starts at $667/month billed annually, with everything above that requiring a sales conversation.
What They Are
Applitools built its name on “Visual AI” — using perceptual/AI-based comparison instead of strict pixel diffing, so it can ignore rendering noise (like anti-aliasing or font-hinting differences) while still catching real layout, color, or content regressions. Its higher tiers extend well beyond visual testing into AI-driven functional testing, natural-language test authoring, and codeless API testing, positioning it as a broader AI testing platform rather than a pure visual-diff tool.
Percy is BrowserStack’s visual testing product, integrated with BrowserStack’s existing cross-browser and real-device infrastructure. It bills by “screenshots” — one rendering of a page or component in one browser at one responsive width — and groups related screenshots into “snapshots” for reporting, so a single page tested across multiple browsers and widths consumes several screenshots from your monthly allotment.
Chromatic, built by the Storybook maintainers, is most tightly associated with component-level visual testing: it snapshots your Storybook stories (or “TurboSnaps,” an optimization that only re-tests components affected by a given change) and flags visual diffs in pull requests. It bills by monthly snapshot volume and is often the first visual-testing tool teams adopt once they already have a Storybook set up.
One ambiguity worth flagging directly: BrowserStack’s own pricing page lists Percy’s Desktop plan as covering “10,000 or 25,000” screenshots per month without fully clarifying whether that’s a single tier or two sub-tiers at the same $199 price — worth confirming with BrowserStack sales before budgeting.
Pros and Cons
Applitools — Pros: the most mature AI-based visual comparison engine in the category, plus an optional path into broader AI-driven functional and API testing on higher tiers. Cons: no self-serve free tier on its public pricing page, and only the entry Starter plan has a published price — everything else requires a sales call.
Percy — Pros: a workable free tier (5,000 screenshots/month), tight integration with BrowserStack’s real-device cloud for teams that need true mobile coverage, and transparent overage pricing. Cons: billing by individual screenshots (not unified snapshots) means multi-browser, multi-viewport test suites can burn through the monthly allotment faster than expected.
Chromatic — Pros: the most generous free tier of the three, clear published pricing all the way up to the Pro plan, and purpose-built TurboSnap optimization that reduces billed usage for incremental changes. Cons: its core strength is Storybook/component-level testing, so teams without an established Storybook setup may get less immediate value than with full-page visual testing tools.
Who It’s a Good Fit For / Who Should Look Elsewhere
Applitools fits larger organizations that want an AI testing platform that goes beyond visual diffing — into functional and API testing — and that are comfortable negotiating pricing directly with sales past the entry Starter tier. Percy fits teams already using or considering BrowserStack for cross-browser and real-device testing who want visual regression folded into the same bill and dashboard. Chromatic fits teams building component libraries with Storybook, especially smaller teams and open-source projects that can operate comfortably within its free tier before needing to pay. Teams with simple, low-volume visual testing needs and no Storybook usage may find Chromatic’s component-centric model less of a fit than Percy’s page-level screenshot approach; teams with tight budgets and no immediate need for AI-driven functional testing may find Applitools’s entry price harder to justify than the other two.
Bottom Line
Start with Chromatic if you’re Storybook-based and cost-sensitive, start with Percy if you’re already in or considering the BrowserStack ecosystem or need real mobile device coverage, and consider Applitools if you want the most advanced AI-driven testing capabilities and have the budget (or the willingness to negotiate) to go beyond its $667/month Starter tier.
FAQ
Does Applitools have a free plan? Not on its public pricing page as of this writing — the lowest published tier is Starter at $667/month billed annually; a free trial is offered instead of a permanent free tier.
What’s the difference between a Percy “screenshot” and a “snapshot”? A screenshot is one rendering of a page or component in one browser at one width; a snapshot groups the screenshots for the same page/component across browsers and widths for reporting — so testing one page in 2 browsers at 3 widths uses 6 screenshots, shown as 1 snapshot.
What is a Chromatic “TurboSnap”? TurboSnap is Chromatic’s optimization that only re-snapshots the Storybook stories affected by a given code change, which is why its plans list a much higher “TurboSnap-equivalent” number than raw billed snapshots.
Which of these three has real mobile device testing? Percy’s Desktop & Mobile plan ($599/month) adds real mobile devices and browsers; Applitools’s higher tiers also offer real iOS/Android device access as an add-on; Chromatic’s plans are focused on browser rendering rather than physical devices.
Can any of these integrate with Figma or Storybook directly? Applitools lists Figma design integration and Storybook component testing on its Starter plan; Chromatic is built around Storybook natively; Percy’s integrations are primarily CI/CD and browser-based rather than design-tool-specific.
Before anyone talks about AI agents reviewing pull requests, most engineering teams still run a more traditional layer underneath: static analysis that checks for bugs, code smells, security hotspots, duplication, and test coverage on every commit. SonarQube, Code Climate Quality, and DeepSource are the three names that come up most often for this job. One important note before the comparison: Code Climate Quality isn’t quite “Code Climate” anymore — in 2026 it was spun out into a separate company called Qlty Software, while the original Code Climate kept its separate engineering-intelligence product, Velocity. This guide covers the current, officially published plans and prices for all three.
At a Glance
SonarQube (Sonar)
Static analysis and security scanning in the cloud (SonarQube Cloud/Team) or self-hosted (SonarQube Server); free Community Build available
Code Climate Quality
Now operated as Qlty Software; Rust-based CLI analysis, maintainability/duplication scoring, AI autofixes
DeepSource
Static analysis, SAST, IaC scanning, and credit-based AI Review/Autofix add-on
SonarQube: 35+ (Team) / 45+ (Enterprise) · Qlty and DeepSource: broad multi-language support (exact counts not separately published)
Short Verdict
SonarQube remains the default choice for teams that need breadth — the most languages, the deepest security-rule coverage, and both cloud and self-hosted deployment options — but its page is also the most layered, with separate paid add-ons (Advanced Security, AI code-review and remediation agents) stacked on top of the base plan. Qlty (formerly Code Climate Quality) is the leanest and most transparently priced of the three, with a genuinely useful free tier and simple per-contributor pricing. DeepSource sits in between: strong static analysis plus an AI Review/Autofix credit system that’s useful if you want automated fixes but adds a second pricing dimension (lines processed) on top of the per-seat fee.
What It Is
SonarQube, from Sonar (formerly SonarSource), is the long-running standard for static analysis: it scans for bugs, vulnerabilities, code smells, and test coverage gaps, enforces quality gates in CI, and reports against standards like OWASP and MISRA. It ships in two deployment families: SonarQube Cloud (the hosted SaaS, sold as “Team” and “Enterprise” plans) and SonarQube Server (self-hosted, sold as Developer, Enterprise, and Data Center editions, priced per instance per year by lines of code). A free Community Build also exists for self-hosted, open-source-style use, and SonarQube is free forever for public OSI-licensed repositories.
Code Climate Quality / Qlty Software is the product long known for its maintainability letter grades (A–F) and duplication/complexity scoring, built around a fast, open, Rust-based CLI. In 2026 it was spun out of Code Climate into a standalone company, Qlty Software, which relaunched it as “Qlty Cloud” with an expanded feature set — including AI-powered autofixes counted as a distinct monthly allowance alongside analysis minutes.
DeepSource combines traditional static analysis (SAST, infrastructure-as-code scanning, secrets detection, code coverage) with an AI Review and Autofix layer that’s billed on a credit system — each Team seat comes with an annual AI credit, and heavier usage is metered by lines of code processed rather than by seat.
A typical SonarQube CI integration just points the scanner at your project key and quality-gate token:
Up to 50k lines of code (LOC) of private projects; community-forum support only
SonarQube
Team (Cloud)
From $34/month, billed monthly
For under 50 developers; covers up to 100k LOC; 35+ languages; 14-day free trial
SonarQube
Enterprise (Cloud)
Custom (contact sales)
45+ languages, SSO/SCIM, portfolios, OWASP/MISRA reporting, zero data retention option
SonarQube
Server editions (self-hosted: Developer/Enterprise/Data Center)
Not publicly listed — priced per instance, per year, by LOC
Details require a separate quote; exact LOC-tier pricing isn’t published
Qlty (Code Climate Quality)
Free
$0/month
1,000 analysis minutes/month, 100 AI autofixes/month, unlimited contributors
Qlty (Code Climate Quality)
Pro
$20/contributor/month
20,000 analysis minutes/month, 5,000 AI autofixes/month, 1-year trend history
Qlty (Code Climate Quality)
Enterprise
$30/contributor/month
75,000 analysis minutes/month, advanced analytics, org policies, SLA support; extra minutes $0.01 each
DeepSource
Open Source
Free
Public repos only; 1,000 PR reviews and 1,000 auto-format runs/month per the comparison table
DeepSource
Team
$24/user/month, billed yearly
Unlimited repos, PRs, and members; $100 annual AI Review credit per user; overage $8–$15 per 10K LOC processed; 3 free OSS-dependency-scan targets, then $8/month each
DeepSource
Enterprise
Custom (contact sales)
Self-hosted option, BYOK for AI Review (Claude, GPT, or Gemini), SSO, SLA support
Pros and Cons
SonarQube — Pros: broadest language support, strongest security/compliance reporting (OWASP, MISRA), flexible cloud-or-self-hosted deployment, and a genuine free tier for small private codebases and OSS. Cons: self-hosted Server-edition pricing isn’t public, and the Cloud plan structure now layers several separately priced AI add-ons (Advanced Security, Gitar AI Code Review, remediation/hunter agents) on top of the base Team price.
Qlty (Code Climate Quality) — Pros: simplest, most transparent per-contributor pricing of the three; a usable free tier; a fast, extensible Rust CLI. Cons: still a very new brand as of 2026 following the Code Climate spin-out, so documentation, integrations, and long-term support history are less proven than SonarQube’s.
DeepSource — Pros: unlimited repos and members even on the Team plan, with a useful bundled AI-review credit and clear OWASP/CWE-mapped reporting. Cons: AI Review overage is billed by lines of code processed, a second metered dimension on top of the per-seat price that can be harder to forecast for large monorepos.
Who It’s a Good Fit For / Who Should Look Elsewhere
SonarQube fits organizations that need compliance-grade reporting (OWASP Top 10, MISRA for embedded/automotive code) across many languages, or that specifically want the option to self-host for data-residency reasons — though they should budget time to get an exact self-hosted quote, since per-instance LOC pricing isn’t posted publicly. Qlty is a strong fit for small-to-mid-size teams that want clear, predictable per-contributor pricing and don’t need SonarQube’s compliance depth; its newness as a standalone company is worth weighing for teams that prioritize vendor longevity. DeepSource fits teams already bought into AI-assisted remediation who want that billed transparently as a credit rather than bundled invisibly into a flat fee, but teams with very large codebases should model the LOC-based overage costs before committing.
Bottom Line
For most engineering organizations evaluating traditional static analysis in 2026, SonarQube is still the safe, comprehensive default, especially where compliance reporting or self-hosting matters — just get a direct quote for the self-hosted tiers rather than assuming a number. Qlty is the best value pick for smaller teams that want simple, predictable pricing without SonarQube’s add-on sprawl. DeepSource is worth a close look specifically if AI-assisted autofixing is a priority and you’d rather see that cost itemized as credits than hidden in a flat per-seat fee.
FAQ
Is Code Climate Quality the same product as Qlty Software? Yes, functionally — Code Climate Quality was spun out in 2026 into a new, separate company called Qlty Software, which now operates and sells the product (relaunched as Qlty Cloud); the original Code Climate company kept its separate Velocity product.
Does SonarQube have a free self-hosted option? Yes — the SonarQube Community Build is free and open for self-hosted use, separate from the paid cloud Team/Enterprise plans and the paid self-hosted Developer/Enterprise/Data Center server editions.
How does DeepSource’s AI Review pricing work? Team-plan users get a $100 annual AI Review credit per user included in the $24/user/month price; usage beyond that is billed at $8 per 10,000 lines processed (Standard) or $15 per 10,000 (Advanced).
What counts toward SonarQube’s lines-of-code billing? Only private-project LOC counts, and for branched projects only the largest branch’s LOC is counted — analysis frequency doesn’t affect the bill.
Is there a free tier for open-source projects on all three? SonarQube is free forever for public OSI-licensed repos, and DeepSource has a free Open Source plan for public repos; Qlty’s free plan isn’t restricted to public repos but caps analysis minutes and AI autofixes per month.
“Server-side tagging” gets thrown around as shorthand for “future-proofing your tracking,” but it’s worth being precise about why it matters in 2026 — and correcting a popular misconception along the way. Google originally planned to deprecate third-party cookies in Chrome, but it reversed that plan in 2024 and, in an April 2025 follow-up, abandoned even the scaled-back opt-out prompt it had proposed instead, choosing to keep Chrome’s existing third-party cookie settings as-is. So the drivers for server-side tagging in 2026 aren’t “Chrome just killed cookies” — they’re the drivers that were already real before that: Safari’s Intelligent Tracking Prevention and Firefox’s Enhanced Tracking Protection have blocked third-party cookies by default for years, iOS App Tracking Transparency has cut mobile ad attribution significantly, ad blockers strip client-side tracking scripts, and privacy regulation (GDPR, CCPA, and similar laws) keeps raising the bar for what you can collect client-side without consent friction. Server-side tagging addresses all of that by moving tag execution off the visitor’s browser and onto a server you control.
At a Glance
Option
What It Is
Starting Price
Best For
Google Tag Manager Server-Side
Free server container software you self-host (typically on Cloud Run)
Free software; hosting itself can run free at low volume, ~$30–$50/month per server once scaled
Teams comfortable managing their own Google Cloud infrastructure
Stape
Managed hosting layer built specifically for GTM server containers
Free tier (10K requests/mo); paid plans from $17/month
Marketers who want GTM server-side without managing Google Cloud themselves
Segment
A full customer data platform (CDP) with native server-side event collection, not a GTM container
Not published — custom quote only
Data teams wanting a unified CDP rather than a GTM-based pipeline
Short Verdict
These three aren’t quite peers, so match the tool to the job. If you already run GTM and just want first-party control over your tag server without a middleman, Google’s own server-side container is free software — you just pay Google Cloud for hosting. If you want the benefits of GTM server-side without learning Cloud Run, logging, and scaling yourself, Stape is a managed hosting layer purpose-built for exactly that, with predictable monthly pricing starting free. If your actual goal is a unified customer data layer across your whole stack (web, app, warehouse, dozens of downstream tools) rather than specifically a GTM server container, Segment is a different category of product entirely, and it’s priced accordingly — through a custom enterprise quote, not a self-serve rate card.
What It Is
Server-side tagging replaces (or supplements) the client-side GTM container running in a visitor’s browser with a server container that sits between your website and the ad/analytics platforms you send data to. Instead of the browser firing a pixel directly to Google Ads, Meta, or your analytics tool, it sends one request to your own server, which then validates, enriches, filters, or anonymizes that data before forwarding it on. Per Google’s own developer documentation, this reduces the amount of code that has to run in the browser (helping page performance) and lets you collect and distribute visitor data in an environment you control rather than one dictated entirely by what each ad platform’s client-side script can see. It also typically uses a first-party cookie set on your own subdomain rather than a third-party one, which holds up better against the tracking-prevention features already built into Safari and Firefox, regardless of what Chrome ultimately does with third-party cookies.
Google Tag Manager Server-Side is Google’s own implementation: the server container itself is free, but it needs to run somewhere. Google’s documentation recommends Cloud Run, either auto-provisioned (Tag Manager creates the Google Cloud project and Cloud Run service for you) or manually configured on existing infrastructure.
Stape is a third-party managed hosting service built specifically to run GTM server containers without requiring you to touch Google Cloud Console directly. It layers on features Google’s raw container doesn’t include out of the box, like cookie handling tools, bot detection, and request analytics.
Segment (by Twilio) is not a GTM server container at all — it’s a customer data platform that collects events server-side and client-side natively and routes them to hundreds of downstream destinations (ad platforms, analytics tools, data warehouses) without requiring you to build or maintain a GTM server setup. It’s included here because it solves an overlapping problem — getting clean, durable, server-controlled event data to your ad platforms — through an entirely different architecture.
Pricing and Plans Compared
Plan
Price
Limits / Notes
GTM Server-Side (software)
Free
No license cost from Google; you only pay for cloud hosting
GTM Server-Side (Cloud Run hosting, default)
Often free
Default single-server deployment is within the Google Cloud free tier for low/test traffic, per Google’s own documentation
GTM Server-Side (Cloud Run hosting, production)
~$30–$50/month per server (Google’s own estimate)
Google recommends a minimum of 3 instances for redundancy on live traffic, so cost scales with instance count and network traffic
Stape Free
$0
Up to 10,000 requests/month; includes custom loader, request analytics, global CDN
Stape Pro
$17/month, billed annually
Up to 500,000 requests/month; adds 3 days of logs, Cookie Keeper, bot detection
Stape Business
$83/month, billed annually
Up to 5,000,000 requests/month; adds custom-cookie Cookie Keeper, up to 20 multi-domains, monitoring
Stape Enterprise
$167/month, billed annually
Up to 20,000,000 requests/month; adds a dedicated account manager, up to 50 multi-domains, log export
Custom MTU and throughput limits, unlimited seats, invoice billing
Segment (full Customer Data Platform)
Contact sales — no published price
Adds Unify and Engage on top of Connections; AI features bundled in or sold as add-ons depending on plan
Worth noting: Google’s documentation itself flags that costs can appear unexpectedly if the Google Cloud billing account tied to your server container is shared with other projects that push you past the free tier — a common surprise for teams who assumed “free” meant “always free.” Stape’s tiered pricing largely exists to abstract that variability away into a flat monthly number.
Pros and Cons
Google Tag Manager Server-Side — Pros: free software with no vendor lock-in, full control since it’s Google’s native tool integrated with the rest of the GTM ecosystem. Cons: you own the DevOps burden — provisioning, scaling instances, monitoring uptime, and managing a real (if often modest) Google Cloud bill that can spike with traffic.
Stape — Pros: removes almost all the Google Cloud management overhead, free tier is genuinely usable for small sites, predictable flat monthly pricing at every paid tier. Cons: it’s still fundamentally bound to the request-volume limits of each tier, so high-traffic sites need to budget for Business/Enterprise tiers or negotiate Custom pricing.
Segment — Pros: unifies server-side and client-side data collection into one platform with hundreds of pre-built destinations, removing the need to build/maintain a GTM server setup at all. Cons: zero public pricing — every evaluation requires a sales conversation, and it’s solving a broader data-infrastructure problem than teams who just want a GTM server container may actually need.
Who It’s a Good Fit For / Who Should Look Elsewhere
Teams with an engineer comfortable in Google Cloud, and traffic low enough to stay mostly within free-tier limits or predictable enough to budget the ~$30–$50/month-per-server estimate, should go straight to Google’s native GTM server-side setup — there’s no reason to pay a markup for something you can self-host. Marketing teams and agencies without dedicated cloud infrastructure staff, who want server-side tagging’s benefits (first-party cookie durability, data filtering before it reaches ad platforms, reduced client-side script weight) without the DevOps work, are the clear audience for Stape. Organizations whose actual pain point is fragmented customer data across many tools — not specifically “our GTM container needs a server” — should evaluate Segment instead, since it replaces the GTM-server-plus-destinations architecture with one platform, but should expect an enterprise sales cycle and custom pricing rather than a quick self-serve signup.
Bottom Line
Server-side tagging is still worth adopting in 2026 — not because Chrome killed third-party cookies (it didn’t; Google reversed that plan), but because Safari, Firefox, mobile privacy controls, ad blockers, and tightening privacy law have already eroded client-side tracking fidelity regardless of what Chrome does. For most marketing teams without in-house cloud engineering, Stape is the pragmatic middle path between “free but you manage the infrastructure” (native GTM server-side) and “powerful but enterprise-only and unpriced” (Segment). Choose native GTM server-side if you have the engineering capacity to run it yourself for free; choose Stape if you want the same benefit without the DevOps; choose Segment only if your real problem is broader customer data unification, not just getting a tag server online.
FAQ
Did Google actually kill third-party cookies in Chrome? No. Google abandoned its plan to deprecate third-party cookies in Chrome in July 2024, and in April 2025 it went further, dropping even the scaled-back opt-out prompt it had proposed, choosing instead to keep Chrome’s existing third-party cookie settings as they are.
If third-party cookies aren’t going away in Chrome, why does server-side tagging still matter? Because Safari’s Intelligent Tracking Prevention and Firefox’s Enhanced Tracking Protection already block third-party cookies by default, iOS App Tracking Transparency has already reduced mobile attribution signal, and privacy regulation keeps increasing consent friction for client-side collection — all independent of whatever Chrome ultimately decides.
Is Google Tag Manager’s server-side container really free? The software itself has no license fee, and Google’s own documentation says the default single-server deployment is often free within Google Cloud’s free tier for low/test traffic — but a production-ready deployment (Google recommends a minimum of three instances) typically costs roughly $30–$50 per server per month, by Google’s own estimate, and more under heavy traffic.
What does Stape add that raw GTM server-side on Cloud Run doesn’t give you? Per Stape’s pricing page, its paid tiers add features like multi-day request/cookie logging, a Cookie Keeper tool for first-party cookie durability, bot detection, multi-domain support, and monitoring — none of which come with a bare Cloud Run deployment of Google’s container.
Can Segment replace a Google Tag Manager server-side setup entirely? Functionally, yes for many use cases — Segment natively collects and routes events server-side to downstream ad and analytics tools without requiring a GTM container at all — but it’s a different architecture and a different buying process (custom enterprise quote, no public pricing) rather than a drop-in substitute.
Does Segment have a free plan? Segment’s official pricing page, as currently published, shows only custom-quote plans (Customer Data Pipeline and the full Customer Data Platform) with no listed free tier, Team tier, or published dollar price.
Click fraud and invalid traffic quietly eat into paid advertising budgets in ways standard analytics tools don’t catch — a competitor repeatedly clicking your Google Ads, a bot farm inflating impressions, or a click farm gaming your affiliate program. ClickCease, CHEQ, and Lunio all promise to detect and block this kind of traffic before it drains your ad spend, but they’re aimed at meaningfully different buyers and ownership structures that aren’t always obvious at first glance — most notably, ClickCease was acquired by CHEQ in 2022 and today operates as a related brand under the same parent company, while still running its own independent self-serve pricing. This guide untangles what each product actually does, who it’s for, and what it costs based on their current official pricing and product pages.
At a Glance
Tool
Starting Price
Pricing Model
Best For
ClickCease
$69/month (promo) / $99/month (regular)
Flat monthly tiers by website/traffic volume, billed annually
Small businesses and single-site PPC advertisers wanting self-serve setup
CHEQ
Not published — demo/quote only
Custom enterprise quote
Larger brands wanting go-to-market security across ads, forms, and bots, not just PPC clicks
Lunio
Not published — based on a percentage of ad spend
Custom quote tied to ad spend and channel coverage
Mid-size to large advertisers running paid search and paid social at scale
Short Verdict
ClickCease is the clear pick if you want transparent, self-serve pricing and run one to twenty websites with modest traffic — you can see exactly what you’ll pay before you sign up, which neither competitor offers. CHEQ is built for larger organizations that want fraud and bot protection woven across their entire acquisition funnel (paid ads, lead forms, analytics integrity), not just PPC click blocking, but you’ll need to book a demo to get a number. Lunio sits closest to ClickCease in actual function — blocking invalid clicks on paid search and social — but prices itself as a percentage of your ad spend rather than a flat seat/traffic tier, which tends to make more sense once your monthly ad budget is substantial.
What They Are
ClickCease is a self-serve click fraud protection tool that monitors your Google Ads and Facebook Ads traffic, automatically flags and blocks suspicious IPs, and reports on invalid clicks. It is now owned by CHEQ (listed as a related brand on cheq.ai) but continues to operate its own branded site and independent, publicly posted pricing, with tiers defined by number of websites protected and monthly traffic volume.
CHEQ is the broader enterprise security platform that owns ClickCease, but CHEQ itself is positioned as a much wider “go-to-market security” suite. Its own homepage lists product lines spanning Marketing Security (ad acquisition fraud protection, form-fill fraud/Form Guard, and analytics integrity), plus Control & Compliance and Trust & Intent tools — i.e., protecting the whole top-of-funnel stack, not just PPC clicks. There is no self-serve signup or published pricing on CHEQ’s own site; the only call to action is “Book a demo.”
Lunio is a traffic protection platform focused on identifying and blocking invalid clicks and bot traffic across paid search and paid social campaigns in real time, paired with analytics showing how much ad spend it’s saving you. Per its own FAQ, Lunio’s pricing is based on a small fraction of your ad spend rather than a flat subscription fee, and it’s adjusted for how many ad channels you want covered.
1 website, up to 5,000 monthly visits, up to 250 leads/mo
ClickCease Pro
$104/mo promo, $149/mo regular, billed annually
Up to 10 websites, up to 40,000 monthly visits, up to 2,000 leads/mo
ClickCease Advanced
$244/mo promo, $349/mo regular, billed annually
Up to 20 websites, up to 80,000 monthly visits, up to 7,000 leads/mo
ClickCease Enterprise
Contact sales
For brands with 1M+ annual web visits
CHEQ (Marketing Security suite)
Contact sales / book a demo — no published pricing
Not disclosed
Lunio
Custom quote — priced as a percentage of ad spend
14-day free traffic audit offered before purchase
Because none of these three disclose an apples-to-apples “price per click blocked” figure, the most useful comparison for budgeting purposes is ClickCease’s transparent flat tiers against Lunio’s audit-first, spend-percentage model: if your monthly ad spend is modest, ClickCease’s capped monthly fee is easier to forecast; if your ad spend is large, Lunio’s percentage-of-spend model and free audit make it easier to prove ROI before committing.
Pros and Cons
ClickCease — Pros: transparent published pricing, fast self-serve setup, works directly with Google and Facebook Ads accounts. Cons: traffic/website caps mean busier sites need to move up tiers (and pay overage on visits above the prepaid allowance); its highest self-serve tier still caps out well below enterprise-scale traffic.
CHEQ — Pros: covers a much wider surface than click fraud alone — form-fill fraud, bot traffic across the funnel, and analytics integrity — useful for larger marketing orgs. Cons: zero published pricing anywhere on its site; every evaluation starts with a sales demo, which is slower and harder to budget for than a self-serve tool.
Lunio — Pros: percentage-of-spend pricing scales naturally with your budget rather than penalizing high traffic with tier overages, and the 14-day free audit lets you see projected savings before paying. Cons: no published rate card at all, so you can’t estimate cost without going through sales; pricing model may feel less predictable to finance teams used to flat SaaS fees.
Who It’s a Good Fit For / Who Should Look Elsewhere
ClickCease is the right call for small and mid-sized businesses running Google or Facebook Ads on one to twenty sites who want to see the exact price before signing up and don’t need protection beyond paid search/social clicks. CHEQ is a better fit for larger organizations — think established mid-market and enterprise marketing teams — that want fraud and bot protection unified across ads, lead forms, and analytics rather than buying several point solutions. Lunio suits advertisers with meaningful monthly ad budgets across paid search and social who are comfortable with a spend-based pricing model and want to validate ROI with a free audit first. Businesses with very low ad spend or a single small campaign should probably start with ClickCease’s Starter tier rather than entering a sales process with CHEQ or Lunio for enterprise-oriented tools.
Bottom Line
For most small and mid-sized advertisers, ClickCease remains the most straightforward buy: known pricing, fast setup, and direct integration with the ad platforms you’re already using — and the fact that it’s backed by CHEQ’s parent infrastructure doesn’t change that self-serve experience. Larger organizations with bigger ad budgets and a broader fraud-surface problem (forms, bots, analytics integrity, not just clicks) should request a CHEQ demo, while advertisers who specifically want click/invalid-traffic protection tied proportionally to spend should get a Lunio audit and compare the projected savings against ClickCease’s flat fee for their traffic volume.
FAQ
Is ClickCease the same company as CHEQ? CHEQ acquired ClickCease in 2022, and cheq.ai’s own site lists ClickCease as a related brand today, but ClickCease continues to run its own branded website and independent, publicly posted pricing separate from CHEQ’s enterprise, quote-only suite.
Does ClickCease have a free trial? ClickCease’s pricing page offers promotional pricing (discounted for the first three billing cycles) on annual plans rather than a separate free trial tier; check its current pricing page for the latest offer terms.
How is Lunio’s pricing calculated if there’s no published rate card? Per Lunio’s own FAQ, pricing is based on a small percentage of your ad spend, adjusted for how many ad channels you want covered, and quoted individually rather than published as a fixed table.
What happens if I exceed my ClickCease plan’s monthly visit limit? ClickCease’s pricing page states that usage above a plan’s prepaid visits is billed at actual usage and the plan’s rates, rather than an automatic hard block or forced upgrade.
Does CHEQ only protect against click fraud? No. CHEQ’s homepage lists a wider Marketing Security product line that also includes form-fill fraud protection (Form Guard) and analytics integrity tooling, alongside acquisition/ad fraud protection — it’s a broader go-to-market security suite rather than a single-purpose click fraud blocker.
Can I try Lunio before paying for a plan? Yes. Lunio offers a 14-day free traffic audit with full analytics access, according to its own pricing page, before you commit to a paid, quote-based plan.
“Passkey platform” has become a confusing phrase because it gets applied to two very different kinds of products. On one side you have password managers like 1Password that now let you generate, store, sync, and autofill passkeys alongside your regular logins. On the other side you have enterprise identity providers like Okta and Microsoft Entra ID, which issue and enforce passwordless and passkey-based sign-in as one control inside a much larger workforce identity and access management (IAM) system — single sign-on, conditional access, lifecycle management, and compliance reporting included. This article compares all three honestly, which means it does not pretend they compete head-to-head for the same buyer. If you’re choosing a consumer-grade or small-team password/passkey vault, 1Password is your comparison point. If you’re standing up enterprise workforce identity with passwordless as one requirement among many, it’s Okta vs. Entra ID.
At a Glance
Platform
Category
Starting Price
Passkey Role
1Password
Password manager with passkey storage
$3.99/user/month (Individual)
Create, store, sync, and autofill passkeys across devices/browsers
Okta Workforce Identity
Enterprise IAM / SSO
$6/user/month (Starter)
Passwordless sign-in via Okta Verify and the Device Access add-on
Microsoft Entra ID
Enterprise IAM / SSO
Free tier available; $7/user/month for Premium P1
Passwordless and phishing-resistant authentication built into P1 and P2
Short Verdict
These three aren’t interchangeable, so the “best” one depends entirely on what you’re actually solving for. If you want a team or small business to start storing and using passkeys today without standing up a full IAM program, 1Password Business ($8.99/user/month) is the fastest path, and it even integrates with Okta and Entra ID for SSO-based unlock. If you’re an enterprise that needs passwordless authentication enforced across every SaaS app, device, and conditional-access policy, the real decision is Okta vs. Entra ID — and that decision usually comes down to whether you’re already deep in the Microsoft 365/Azure ecosystem (favoring Entra ID’s bundled pricing) or need best-of-breed, platform-agnostic identity management with the broadest third-party app catalog (favoring Okta).
What They Are
1Password is a password manager that has extended its vault to also create, store, and sync passkeys. Per 1Password’s own product page, passkeys sync across Mac, iOS, Windows, and Android, can be organized with vaults and tags, shared through shared vaults, and flagged by its Watchtower feature whenever an existing account offers an upgrade to a passkey. On the business side, 1Password Business lists integrations for unlocking via SSO with identity providers including Okta, Entra ID, OneLogin, and Duo — meaning it’s often deployed alongside an enterprise IAM platform, not instead of one.
Okta Workforce Identity Cloud is an enterprise identity provider: single sign-on, multi-factor and adaptive authentication, lifecycle management, and a large app-integration catalog. Passwordless and passkey-style authentication show up here as components, not as the product itself — “Device Access” is sold as an add-on that Okta describes as extending “highly secure, passwordless Okta authentication to desktops and devices,” while Adaptive MFA (phishing-resistant authentication) is bundled starting at the Essentials tier.
Microsoft Entra ID (formerly Azure AD) is Microsoft’s cloud identity and access management platform, covering SSO, conditional access, and identity governance for an organization’s Microsoft 365 and third-party apps. Microsoft’s own pricing page lists “passwordless and phishing-resistant authentication” explicitly as a feature of the Premium P1 tier, with P2 inheriting everything in P1 and adding identity protection and privileged access management on top.
Pricing and Plans Compared
Plan
Price
Notes
1Password Individual
$3.99/month (billed yearly)
Personal vault, passkey saving/autofill
1Password Families
$5.99/month for up to 5 members
Shared family vaults, passkey support
1Password Teams Starter Pack
$24.95/month flat, up to 10 members
Additional seats roughly $4.99/seat/month
1Password Business
$8.99/user/month, billed yearly, 1-user minimum
SSO integrations with Okta/Entra ID/OneLogin/Duo, passkey/biometric unlock
Okta Starter
$6/user/month
SSO, MFA, Universal Directory; Device Access and Adaptive MFA are add-ons
Okta Core Essentials
$14/user/month (listed; purchase via sales)
Adaptive MFA appears included; Device Access still an add-on
Okta Essentials
$17/user/month (listed; purchase via sales)
Adaptive MFA included; Device Access add-on still required for full passwordless desktop auth
Okta Professional / Enterprise
Contact sales
Adds Device Access as standard, API Access Management, Access Gateway at Enterprise
Entra ID Free
$0 (requires an Azure subscription)
Basic MFA, SSO, password self-service — no passwordless/passkey feature listed
Entra ID Premium P1
$7.00/user/month
Adds passwordless/phishing-resistant auth, conditional access; bundled in M365 E3/Business Premium
Entra ID Premium P2
$10.00/user/month
Everything in P1 plus identity protection, privileged identity management; bundled in M365 E5
Entra Suite
$12.00/user/month
Requires an existing P1 subscription
Note the asymmetry: Okta publishes a minimum annual contract value of $1,500 for Workforce Identity and bills annually, and its passwordless desktop feature (Device Access) is an unpriced add-on at every self-serve tier — so a true “passwordless everywhere” Okta deployment will cost more than the headline $6–$17/user figures suggest. Microsoft, by contrast, bakes passwordless authentication directly into the P1 price with no separate add-on.
Pros and Cons
1Password — Pros: cheapest entry point by far, passkeys sync natively across all major platforms, integrates with Okta/Entra ID rather than competing with them. Cons: it’s a vault, not an IAM system — no conditional access, no directory services, no SSO enforcement across an org’s app stack on its own.
Okta Workforce Identity — Pros: broadest third-party app integration catalog among enterprise IAM vendors, Adaptive MFA included from the Essentials tier up. Cons: true passwordless-to-desktop (Device Access) is an unpriced add-on at every published tier, and a $1,500/year minimum plus annual-only billing raises the entry barrier for smaller teams.
Microsoft Entra ID — Pros: passwordless/phishing-resistant auth is built into P1 at $7/user/month with no separate add-on, and pricing is often absorbed into existing Microsoft 365 E3/E5/Business Premium licensing. Cons: Entra Suite requires an existing P1 subscription as a prerequisite, and the free tier offers no passwordless capability at all.
Who It’s a Good Fit For / Who Should Look Elsewhere
1Password fits individuals, families, and small-to-mid-size businesses that want to start replacing passwords with passkeys today without a six-month IAM rollout — and it’s a sensible companion purchase even for enterprises that already run Okta or Entra ID, since it explicitly supports SSO unlock through both. Okta fits organizations that need enterprise-grade identity across a highly heterogeneous app stack and value its integration breadth enough to accept the add-on costs for full passwordless coverage. Microsoft Entra ID fits organizations already committed to Microsoft 365/Azure, where passwordless authentication arrives bundled into a P1 or P2 license you may already be paying for. Businesses that only need password/passkey storage should skip Okta and Entra ID entirely — buying enterprise IAM for that job is significant overkill. Conversely, enterprises needing centralized directory services, conditional access, and lifecycle governance should not expect 1Password to replace that function.
Bottom Line
This comparison only works if you accept it isn’t really a three-way tie for the same job. 1Password is the right tool for storing and using passkeys cheaply and quickly. Okta and Entra ID are the right tools for enforcing passwordless authentication as policy across an entire workforce — and between those two, Entra ID generally wins on bundled economics for Microsoft-centric organizations, while Okta wins on platform-agnostic breadth for everyone else. Many organizations will reasonably end up running 1Password for secrets/passkey storage alongside one of the two IAM platforms for enforcement, rather than picking just one.
FAQ
Is 1Password a replacement for Okta or Entra ID? No. 1Password is a password and passkey vault; Okta and Entra ID are enterprise identity and access management platforms with SSO, conditional access, and directory services. 1Password’s own Business plan lists Okta and Entra ID as SSO integrations rather than competitors.
Does Microsoft Entra ID’s free tier support passwordless sign-in? Microsoft’s pricing page lists passwordless and phishing-resistant authentication as a Premium P1 feature ($7/user/month); the free tier’s listed features are limited to basic MFA, SSO, and password self-service.
Do I have to pay extra for passwordless authentication on Okta? Full passwordless authentication to desktops and devices (Device Access) is sold as an add-on at Okta’s Starter, Core Essentials, and Essentials tiers, with pricing available only by contacting sales; it’s included as standard only from Professional and up.
What’s the cheapest way to start using passkeys for a small team? Among these three, 1Password’s Teams Starter Pack ($24.95/month flat for up to 10 members) is the lowest-cost entry point for team-wide passkey storage and sharing.
Is Microsoft Entra Suite the same as Entra ID P2? No. Entra Suite is a separate $12/user/month add-on that requires an existing Entra ID P1 subscription (or a plan that includes P1); Microsoft also offers special pricing for P2 and Microsoft 365 E5 customers upgrading to the Suite.
Can 1Password itself be unlocked with a passkey instead of a master password? 1Password’s product page describes this as available in public beta for new Individual accounts, with support for unlocking existing accounts across Mac, iOS, Windows, and Android listed as “coming soon” at the time of our research.
Small businesses are now squarely in ransomware crews’ crosshairs, but most don’t have a security operations center or a six-figure budget for one. That’s created real demand for endpoint detection and response (EDR) tools that are affordable per seat, quick to deploy without a dedicated security team, and don’t require a forklift upgrade of existing infrastructure. CrowdStrike, SentinelOne, and Microsoft have all built (or repackaged) products specifically to meet that demand: Falcon Go, SentinelOne’s Singularity line, and Microsoft Defender for Business. This guide compares what each actually costs and includes, based on their current published pricing pages, so you can shortlist the right one for a 10- to 300-seat environment.
At a Glance
Tool
Starting Price
Pricing Model
Best For
CrowdStrike Falcon Go
$7.99/device/month or $59.99/device/year
Per-device, capped at 100 devices
Very small businesses wanting CrowdStrike’s core EDR engine on a budget
SentinelOne Singularity Complete
$179.99/endpoint/year (public list price)
Per-endpoint, annual, sized for 5–100 workstations
Businesses wanting AI-driven autonomous response without a SOC
Microsoft Defender for Business
$3.00/user/month, billed annually
Per-user (covers up to 5 devices per user)
Microsoft 365 shops up to 300 users wanting EDR bundled cheaply
Short Verdict
If you’re already a Microsoft 365 shop with under 300 users, Microsoft Defender for Business is the easiest financial decision: at $3 per user per month it undercuts both competitors by a wide margin and already understands your Windows/macOS/iOS/Android fleet. If you want a dedicated, best-of-breed EDR engine and don’t mind paying more, CrowdStrike Falcon Go gives you the real Falcon sensor (not a cut-down version) at a small-business price, capped at 100 devices. SentinelOne sits in between on philosophy — it leans harder on autonomous, AI-driven remediation that doesn’t require an analyst to act — but its cheapest publicly listed tier, Singularity Complete, costs more per endpoint per year than either alternative once you annualize it.
What They Are
CrowdStrike Falcon Go is CrowdStrike’s small-business edition of its Falcon platform, built around the same cloud-native sensor and threat-intelligence graph used in its enterprise tiers, just packaged into simpler bundles. According to CrowdStrike’s own pricing page, Falcon Go, Pro, and Enterprise all include next-gen antivirus, device control, mobile device protection, firewall management, EDR, threat intelligence and hunting, identity protection, IT hygiene, next-gen SIEM, and “Express Support,” with each higher tier adding more depth (centralized firewall policy management at Pro, deeper threat hunting at Enterprise). Falcon Go purchases are capped at 100 devices, positioning it explicitly for small businesses rather than mid-market IT departments.
SentinelOne Singularity is built around autonomous, AI-driven detection and response that can act on a threat (killing a process, rolling back encryption) without waiting for a human analyst — a pitch aimed directly at organizations without 24/7 security staff. SentinelOne’s pricing page names Core, Control, Complete, Commercial, and Enterprise tiers, but only publishes list prices for Complete and Commercial; Core and Control appear in its comparison table without public pricing, and Enterprise is sold through a quote only.
Microsoft Defender for Business is Microsoft’s EDR product purpose-built for organizations with up to 300 employees, sold standalone or bundled inside Microsoft 365 Business Premium. Per Microsoft’s own product page, it includes next-generation antivirus, AI-powered EDR with “automatic attack disruption,” vulnerability management, and wizard-based onboarding meant for IT generalists rather than security specialists, covering Windows, macOS, iOS, and Android with up to five devices per licensed user.
Pricing and Plans Compared
Plan
Monthly
Annual
Notes
Falcon Go
$7.99/device
$59.99/device
Max 100 devices; 15-day free trial, no card required
Falcon Pro
$14.99/device
$99.99/device
Adds deeper firewall management
Falcon Enterprise
$19.99/device
$184.99/device
Adds deeper threat hunting/intel
Falcon Complete
Contact sales
Fully managed 24/7 MDR with a breach-prevention warranty
Singularity Complete
$179.99/endpoint/year
14-day data retention; sized for 5–100 workstations
Adds agentic SOC-analyst triage and full network forensics
Defender for Business (standalone)
$3.00/user/month, billed yearly
Up to 300 users, 5 devices/user
Microsoft 365 Business Premium
$22.00/user/month, billed yearly
Bundles Defender for Business with productivity apps
Two things worth flagging for budgeting purposes. First, CrowdStrike’s and SentinelOne’s publicly listed prices exclude taxes and partner-specific adjustments — SentinelOne explicitly sells through authorized third-party partners and says partner pricing can override the list price shown. Second, nobody in this comparison publishes pricing for their top-end managed-detection-and-response tier (Falcon Complete, Singularity Enterprise); both require a sales conversation, so budget extra time if 24/7 managed response is a requirement rather than a nice-to-have.
Pros and Cons
CrowdStrike Falcon Go — Pros: real Falcon sensor technology at a small-business price, strong threat-intel pedigree, simple per-device pricing with a no-card 15-day trial. Cons: capped at 100 devices so you’ll need to migrate off it as you grow; managed MDR (Falcon Complete) pricing isn’t public.
SentinelOne Singularity — Pros: strongest autonomous/AI remediation story for teams without a SOC, Commercial tier adds managed threat hunting and 90-day retention. Cons: its cheapest public tier (Complete) costs more per endpoint annually than either competitor; Core/Control tier pricing isn’t public, and pricing routes through third-party partners who can vary the list price.
Microsoft Defender for Business — Pros: by far the cheapest list price here, native fit for Microsoft 365 environments, easy generalist-friendly onboarding. Cons: hard cap at 300 users means it’s not a long-term fit for growing mid-market companies; EDR depth and threat-hunting sophistication are generally considered lighter than dedicated EDR vendors.
Who It’s a Good Fit For / Who Should Look Elsewhere
Microsoft Defender for Business is the obvious fit for any small business already paying for Microsoft 365, especially ones under roughly 50 seats where $3/user/month barely registers as a line item. CrowdStrike Falcon Go fits businesses that have outgrown “good enough” antivirus and want a dedicated EDR vendor’s actual engine, not a watered-down one, while staying under the 100-device ceiling. SentinelOne Singularity Complete/Commercial fits businesses that specifically want automated rollback and remediation because they have no security staff to respond to alerts manually, and are willing to pay more per endpoint for that autonomy. Companies expecting to blow past 100–300 endpoints within a year or two should treat all three small-business tiers as a bridge, not a destination, and start evaluating the next tier up (Falcon Pro/Enterprise, Singularity Enterprise, or Defender for Endpoint P1/P2) now.
Bottom Line
There’s no universally “best” EDR for small business in 2026 — there’s a best fit for your budget, your existing stack, and your appetite for hands-on security management. Microsoft Defender for Business wins on price and ecosystem fit for Microsoft 365 users; CrowdStrike Falcon Go wins if you want proven enterprise-grade EDR technology scaled down rather than watered down; SentinelOne wins if autonomous, no-human-required remediation is your top priority and you’re comfortable paying a premium for it. Get a quote for the managed/enterprise tiers before committing either way — list prices only tell part of the story once support SLAs and managed response enter the conversation.
FAQ
Is Microsoft Defender for Business the same as Microsoft Defender Antivirus built into Windows? No. The built-in Defender Antivirus is free consumer-grade protection; Defender for Business is a separately licensed product ($3/user/month) that adds EDR, centralized management, vulnerability management, and attack disruption on top of it.
Can I buy CrowdStrike Falcon Go month-to-month? Yes. CrowdStrike’s pricing page lists monthly billing at $7.99/device for Falcon Go, alongside a discounted annual rate of $59.99/device if you commit for a year.
Does SentinelOne publish pricing for every plan? No. Singularity Complete and Commercial have public per-endpoint annual list prices on SentinelOne’s pricing page, but Core, Control, and Enterprise require contacting sales, and purchases generally route through an authorized partner whose pricing can differ from the listed figure.
What happens if I exceed Falcon Go’s 100-device cap? You’ll need to upgrade to Falcon Pro or Falcon Enterprise, since Falcon Go purchases are explicitly limited to a maximum of 100 devices according to CrowdStrike’s pricing page.
Is a 24/7 managed SOC included in any of these small-business tiers? No. Fully managed detection and response (CrowdStrike Falcon Complete, SentinelOne Singularity Enterprise’s managed options) sits above these small-business tiers and is sold only through a custom quote.
Which of these three is cheapest for a 20-person company? On published list pricing, Microsoft Defender for Business is cheapest at $3/user/month (about $720/year for 20 users), versus roughly $1,200/year for CrowdStrike Falcon Go billed annually, and roughly $3,600/year for SentinelOne Singularity Complete at its public per-endpoint rate.
AI meeting notetakers have gone from novelty to default in the space of a couple of years, and the category has consolidated around a few clear leaders. Otter.ai, Fireflies.ai, and Fathom all record, transcribe, and summarize meetings, but they differ meaningfully on pricing structure, storage limits, and which audience (individual, team, or sales org) they’re really built for. Here’s a current, sourced comparison.
At a Glance
App
Starting Paid Price
Free Plan?
Best For
Otter.ai
$8.33/user/mo (Pro, annual)
Yes (300 min/mo)
Individuals and students needing reliable everyday transcription
Fireflies.ai
$10/seat/mo (Pro, annual)
Yes (unlimited transcription, limited AI)
Teams wanting unlimited transcription cheaply, with room to add AI features
Fathom
$15/mo (Team, annual, 2-user minimum)
Yes (unlimited recording)
Sales teams wanting CRM-synced call summaries and coaching
Short Verdict
Otter.ai is the most mature, broadly-used option and offers the most generous free tier for individuals (300 minutes per month). Fireflies.ai stands out for pairing unlimited transcription on its free plan with genuinely cheap paid tiers that unlock AI summaries, voice agents, and large storage allowances. Fathom leans hardest into sales use cases — its Business and Enterprise tiers sync directly into CRM deal records and surface coaching metrics, making it the strongest pick specifically for revenue teams rather than general meeting notes.
What They Are
Otter.ai is a transcription and meeting-notes app that joins video calls (or records in-person conversations via mobile) to produce live transcripts, speaker identification, and AI-generated summaries, with its own AI Chat feature for querying past meetings.
Fireflies.ai takes a similar core approach — joining calls, transcribing, and summarizing — but builds out further into “conversation intelligence,” team analytics, and an expanding set of AI “Skills” and voice agents, all gated behind a monthly AI-credit allowance that scales with plan tier.
Fathom focuses specifically on sales and customer-facing calls, pairing meeting recording and summarization with CRM field sync, deal-level call rollups, and AI scorecards intended to help managers coach reps based on call content.
Pricing Breakdown
Plan
Price
Limits
Key Features
Otter.ai Basic
Free
300 min/mo, 30-min max per conversation, 3 lifetime imports
Live transcription, speaker ID, AI Chat
Otter.ai Pro
$16.99/mo or $8.33/mo billed annually
1,200 min/mo, 90-min max per conversation, 10 imports/mo
Advanced AI workflows, unlimited storage, CRM integrations
Otter.ai Business
$30/mo or $19.99/mo billed annually
Unlimited meeting minutes, 6,000 imported-file minutes, 4-hr max
Admin analytics, 3 concurrent meetings, 200 AI Chat queries/user/mo
Otter.ai Enterprise
Custom
Unlimited
SSO, SCIM, HIPAA add-on, API/webhooks
Fireflies.ai Free
$0
Unlimited transcription, 400 storage mins/team, 20 AI credits
Meeting search, AskFred AI assistant, API access
Fireflies.ai Pro
$10/seat/mo, billed annually
8,000 storage mins/seat, 20 AI credits
Video recording, Personal Assistant, unlimited integrations
Fireflies.ai Business
$19/seat/mo, billed annually
Unlimited storage, 30 AI credits
Multi-language mode, team analytics, conversation intelligence
Fireflies.ai Enterprise
$39/seat/mo, billed annually only
Unlimited storage, 50 AI credits
SSO/SCIM, HIPAA compliance, custom data retention
Fathom Free
$0
Unlimited recordings/transcription
AI call summaries, clips and playlists
Fathom Premium
$20/mo or $16/mo billed annually
Individual plan
Advanced summaries, AI action items, custom meeting bot
Fathom Team
$19/mo or $15/mo billed annually (2-user minimum)
Team plan
Shared workspace, team-wide search, HIPAA compliance with BAA
Fathom Business
$34/mo or $25/mo billed annually (2-user minimum)
Team plan
CRM field sync, Deal View, coaching metrics and AI scorecards
Fathom Enterprise
Custom, annual billing only
Organization-wide
SSO/SCIM, custom data retention, dedicated Success Manager
Both Otter.ai and Fireflies.ai advertise discounted annual pricing (Otter markets roughly 50% off list monthly pricing when billed annually; Fireflies advertises savings of up to 44%). Fathom’s Team and Business plans both carry a 2-user minimum, so solo users on those tiers would pay for at least two seats.
Pros and Cons
Otter.ai — Pros: the most generous free minutes of the three (300/month), mature mobile apps, solid everyday reliability. Cons: file import limits are tighter than competitors’ on lower tiers, and per-conversation time caps (30-90 minutes) can cut off long meetings on cheaper plans.
Fireflies.ai — Pros: unlimited transcription even on the free plan, cheapest entry-level paid tier of the three, broad integration support. Cons: AI features (summaries beyond the basics, Skills, voice agents) are gated by a monthly AI-credit system that adds a layer of complexity to understand what’s actually included.
Fathom — Pros: deepest CRM and sales-coaching integration, unlimited recording even on the free plan, strong HIPAA/compliance posture on team tiers. Cons: Team and Business plans require a minimum of 2 seats, and its feature set is noticeably sales-skewed rather than general-purpose.
Who It’s a Good Fit For / Who Should Look Elsewhere
Otter.ai fits individuals, students, and small teams who want dependable transcription with minimal setup and a genuinely useful free tier; it’s a weaker fit for sales teams wanting deal-level analytics. Fireflies.ai fits teams that want transcription without volume anxiety and plan to grow into AI features gradually, thanks to its credit-based scaling; it’s a less obvious fit if you want all AI features unlocked without tracking a credit balance. Fathom fits sales and customer-success teams that want call insights synced into their CRM and coaching data for managers; it’s overbuilt and less cost-effective for someone who just wants plain meeting transcripts.
Bottom Line
For general-purpose meeting notes, Otter.ai and Fireflies.ai are both strong, with Fireflies edging ahead on unlimited free transcription and a cheaper entry paid tier. For sales teams specifically, Fathom’s CRM sync and coaching features justify its sales-oriented pricing in a way the other two don’t match.
FAQ
Which of these has the best free plan? Fireflies.ai offers unlimited transcription for free (with storage and AI-credit limits), while Otter.ai caps free use at 300 minutes per month; Fathom’s free plan allows unlimited recording and transcription but with fewer AI summary features than its paid tiers.
Do any of these integrate directly with a CRM? Yes — Otter.ai Pro and above integrate with Salesforce and HubSpot, and Fathom’s Business plan adds direct CRM field sync and deal-level call rollups, which is the deepest of the three on this front.
What are Fireflies.ai’s “AI credits” and why do they matter? AI credits gate access to Fireflies’ AI features (like AskFred, Skills, and voice agents) beyond basic transcription; each plan includes a monthly credit allowance (20 on Free and Pro, 30 on Business, 50 on Enterprise) that can run out with heavy use.
Can I use Fathom’s Team or Business plan as a single user? No — both plans carry a 2-user minimum, so a solo user would need to pay for at least two seats to access Team or Business features; Fathom’s Premium plan is the individual-user paid option instead.
Are any of these HIPAA compliant? Fathom’s Team plan includes HIPAA compliance with a standard BAA, and Fireflies.ai offers HIPAA compliance on its Enterprise plan; Otter.ai offers HIPAA compliance as an add-on specifically on its Enterprise plan.
For most people, the built-in Mail app is fine. Power users — the ones processing hundreds of emails a day, running a team’s inbox, or treating email as a core part of their workflow — need something faster and smarter. Superhuman, Spark, and Outlook (via Microsoft 365) represent three very different bets on what “power user email” means: speed and keyboard-driven minimalism, AI-assisted team collaboration, or deep enterprise integration. Here’s how their 2026 pricing and features stack up.
At a Glance
App
Starting Price
Free Plan?
Best For
Superhuman
$30/mo (Starter)
No
Individuals who live in their inbox and want maximum speed
Spark
$0 (Free)
Yes (full-featured)
Individuals and small teams wanting AI features without a steep price
Outlook (Microsoft 365)
$7.00/user/mo (Business Basic, web/mobile only)
No (basic Outlook.com is separate)
Businesses already standardized on Microsoft 365
Short Verdict
Superhuman is the fastest, most keyboard-driven experience of the three, but it’s also the most expensive relative to what it does — it’s an email client layered on top of Gmail or Outlook accounts you already have, not a full email provider. Spark gives you a genuinely capable free tier with AI meeting notes and a smart inbox, and its paid tiers are considerably cheaper than Superhuman’s for similar AI-assisted features. Outlook, bundled into Microsoft 365, isn’t trying to be the flashiest client — it wins by being the default, deeply integrated choice for any organization already paying for Teams, SharePoint, and the rest of the Microsoft stack.
What They Are
Superhuman is a premium email client that connects to your existing Gmail or Microsoft account and layers on a keyboard-shortcut-driven interface, AI writing and triage features, and social/CRM-style context on senders. It’s explicitly positioned as a productivity tool for people who process very high email volumes.
Spark is an email client from Readdle built around a “Smart Inbox” that categorizes messages automatically, plus an increasingly prominent AI layer (Spark +AI) that handles meeting notes, draft replies, and team collaboration features like shared threads and comments on emails.
Outlook is Microsoft’s email client, bundled into Microsoft 365 subscriptions for both consumers and businesses. For power users, the relevant distinction is between the web/mobile-only “Business Basic” tier and the tiers that include the full desktop Outlook app, plus Copilot AI features now bundled into the higher business tiers after Microsoft’s 2026 pricing changes.
Pricing Breakdown
Plan
Price
Key Features
Superhuman Starter
$30/mo or $300/yr
Superhuman Mail, shared conversations and team comments, most AI features
Superhuman Business
$40/mo or $396/yr
Everything in Starter, plus Auto Drafts, Ask AI, HubSpot/Salesforce integration
Superhuman Enterprise
Custom (contact sales)
Advanced security, SSO, dedicated support
Spark Free
$0
Smart Inbox, unlimited accounts, calendar, smart notifications
Spark Plus
$10/user/mo or $99/user/yr
AI assistant, 40 AI meeting notes/month, custom templates
Spark Pro
$20/user/mo or $199/user/yr
Unlimited AI meeting notes, Autopilot rules, auto-drafts, HubSpot integration
Microsoft 365 Business Basic
$7.00/user/mo, billed yearly
Web and mobile Outlook only (no desktop app), Teams included
Microsoft 365 Business Standard (with Copilot)
$23.50/user/mo, billed yearly
Desktop Outlook, bundled Copilot AI, full Office apps
Microsoft 365 Business Premium (with Copilot)
$32.00/user/mo, billed yearly
Everything in Standard, plus advanced security and device management
Microsoft also lists lower-priced “no Teams” versions of its Business plans ($5.40, $20.30, and $28.80/user/month for Basic, Standard, and Premium respectively) for organizations that don’t need Teams bundled in. Microsoft’s Business Standard and Premium prices now include Copilot by default following a 2026 price restructuring that bundled AI features into the core plans rather than selling Copilot as a separate add-on.
Pros and Cons
Superhuman — Pros: the fastest, most keyboard-centric interface of the three, strong AI triage and writing tools. Cons: most expensive per user by a wide margin, and it’s an add-on layer that still requires a separate Gmail or Microsoft account underneath.
Spark — Pros: the most generous free tier, cheapest paid AI features, built-in team collaboration on emails. Cons: AI features run on a monthly quota that heavy users can exhaust, and its brand/ecosystem is smaller than Microsoft’s or Superhuman’s.
Outlook (Microsoft 365) — Pros: deepest enterprise integration (Teams, SharePoint, Exchange), desktop app included from Business Standard up, Copilot AI now bundled rather than a pricey add-on. Cons: the cheapest Business Basic tier lacks the desktop app entirely, and overall per-user cost climbs quickly once you want Copilot and advanced security together.
Who It’s a Good Fit For / Who Should Look Elsewhere
Superhuman fits individuals and small teams who process enormous email volume and will genuinely use its speed-focused shortcuts daily — it’s hard to justify for casual email users at $30-40/month per seat. Spark fits individuals, freelancers, and small teams who want AI-assisted email and meeting notes without committing to an expensive tool, and its free tier alone beats what either competitor offers at $0. Outlook fits any organization already running on Microsoft 365 for Teams, SharePoint, or Exchange — the integration value outweighs any client-level feature gaps. It’s a poor fit if you’re not otherwise in the Microsoft ecosystem and don’t need its enterprise features, since Business Basic doesn’t even include the desktop app.
Bottom Line
There’s a clear price-to-value gradient here: Spark delivers the most AI-assisted email power per dollar, Outlook delivers the most integration per dollar for Microsoft-based organizations, and Superhuman delivers the most raw speed per dollar — if speed is genuinely your bottleneck and you can justify the cost.
FAQ
Does Superhuman replace Gmail or Outlook, or sit on top of it? Superhuman connects to and sits on top of an existing Gmail or Microsoft email account — it’s a client, not an email provider, so you still need an underlying email account.
Is Spark’s AI meeting notes feature really unlimited on any plan? Only on Pro ($20/user/month or $199/user/year). The free plan doesn’t include it, and Plus caps it at 40 AI meeting notes per month.
Which Microsoft 365 business plan is the cheapest one that includes desktop Outlook? Business Standard with Copilot, at $23.50/user/month billed yearly (or $20.30 without Teams bundled in); Business Basic is cheaper but web/mobile-only.
Why did Microsoft 365 Business plans get more expensive in 2026? Microsoft restructured pricing in 2026 to bundle its Copilot AI features into the core Business Standard and Premium plans rather than selling Copilot separately, raising the base price of those tiers.
Can I get a discount on Superhuman? Superhuman’s publicly listed prices are $30/month (Starter) and $40/month (Business), with annual billing at $300 and $396/year respectively; it doesn’t list public promotional discounts, though it does offer separate student and non-profit pricing by contacting its team directly.
Choosing accounting software is one of those decisions that quietly shapes how much time you spend on busywork for years afterward. Freelancers want something that won’t eat an evening every month; small businesses with a few employees need multi-user access, inventory, and real reporting. QuickBooks Online, Xero, and Wave sit at three different points on that spectrum, and 2026 pricing changes at both QuickBooks and Xero have shifted the math. This guide breaks down what each one actually charges, what you get at each tier, and who should pick which.
At a Glance
Software
Starting Price
Free Plan?
Best For
QuickBooks Online
$38/mo (Simple Start, list price)
Yes (limited)
Growing small businesses needing deep reporting and inventory
Xero
$27/mo (Early, regular price)
No
Service businesses that want unlimited invoicing without per-invoice caps
Wave
$0 (Starter)
Yes (robust)
Freelancers and solopreneurs who want core bookkeeping for free
Short Verdict
If you’re a true solo freelancer watching every dollar, Wave’s free Starter plan covers invoicing and bookkeeping better than anything else at that price. If you need multi-user access, inventory tracking, or project profitability reporting as you scale, QuickBooks Online’s Plus and Advanced tiers are the most feature-complete, though 2026’s price increases make them the priciest option in this trio. Xero sits in between: its Early plan caps invoices at 20 per month, but Growing and Established remove that cap and add stronger cash-flow forecasting and multi-currency support at a lower list price than QuickBooks’ equivalent tiers.
What They Are
QuickBooks Online is Intuit’s cloud accounting platform and the most widely used small-business accounting tool in the US, largely because so many bookkeepers and accountants are already trained on it. It handles invoicing, expense tracking, payroll (as an add-on), inventory, and increasingly detailed reporting as you move up its tiers.
Xero is a New Zealand-founded cloud accounting platform popular with accountants and bookkeepers internationally. It’s built around unlimited users on every paid plan (a notable difference from QuickBooks, which caps users per tier) and strong multi-currency and cash-flow forecasting tools, with payroll available via an add-on powered by Gusto in the US.
Wave is a free-first accounting and invoicing tool originally built for freelancers and very small businesses. Its core bookkeeping, invoicing, and estimating features are free indefinitely; it generates revenue mainly through payment processing fees and its Pro plan, payroll add-on, and bookkeeping service.
Pricing Breakdown
Plan
List Price
Users
Key Limits/Features
QuickBooks Simple Start
$38/mo (promo: $19/mo for 3 months)
1 user, 2 accountant seats
Invoicing, expense tracking, 1 connected bank, basic reports
QuickBooks Essentials
$85/mo (promo: $42.50/mo for 3 months)
3 users, 2 accountant seats
Bill management, time tracking on invoices, enhanced reports
QuickBooks Plus
$140/mo (promo: $70/mo for 3 months)
5 users, 2 accountant seats
Inventory tracking, project profitability, budgeting, up to 40 classes/locations
Unlimited invoices/estimates/bills, mobile invoicing; card payments at 2.9%+$0.60
Wave Pro
$19/mo or $190/yr
Multiple, with access roles
Bank transaction auto-import, auto-categorization, branding removal, 10 free card transactions/month
Both QuickBooks and Xero offer time-limited introductory discounts on new sign-ups (shown above), after which billing reverts to the list price. Payroll is a separate paid add-on for all three platforms; Xero’s US payroll (via Gusto) runs $36/month plus $6 per employee or contractor, on top of your Xero subscription.
Pros and Cons
QuickBooks Online — Pros: the deepest reporting and inventory features of the three, huge accountant/bookkeeper familiarity, extensive app integrations. Cons: the most expensive tier-for-tier after 2026’s price increases, and the Free plan caps you at 2 invoices per month.
Xero — Pros: unlimited users on every plan, strong multi-currency and cash-flow forecasting, lower list prices than QuickBooks’ equivalent tiers. Cons: no permanent free plan, and the entry-level Early plan’s 20-invoice-per-month cap is restrictive for invoice-heavy freelancers.
Wave — Pros: genuinely full-featured free tier for invoicing and bookkeeping, simple flat per-business (not per-seat) pricing on Pro. Cons: fewer deep features (no built-in inventory management, more limited reporting) and a narrower support window (weekday business hours only).
Who It’s a Good Fit For / Who Should Look Elsewhere
QuickBooks Online fits small businesses that expect to grow into needing inventory, multiple employees, and project-level profitability tracking, and that value working with an accountant already fluent in the platform. It’s a poor fit for a solo freelancer who just needs to invoice clients and track expenses — you’ll pay far more than you need to. Xero is a strong fit for businesses with several people who all need login access without per-seat fees, and for anyone doing business in multiple currencies. It’s less appealing if you want a genuinely free starting point. Wave is the clear choice for freelancers, consultants, and very small businesses whose accounting needs are mainly invoicing and basic bookkeeping; it becomes a weaker fit once you need inventory tracking, detailed job costing, or larger team workflows.
Bottom Line
There’s no single winner here because the three tools are aimed at different budgets and different stages of business. Wave wins on price for anyone who can live with its simpler feature set. Xero wins on value for small teams that want unlimited users and strong forecasting without QuickBooks’ price tag. QuickBooks Online wins on depth and ecosystem support for businesses that are ready to pay for inventory, multi-user access, and the reporting an accountant will recognize instantly.
FAQ
Is Wave really free, or are there hidden costs? Wave’s Starter plan is free for unlimited invoicing, estimates, bills, and bookkeeping records. The costs come from payment processing fees (2.9% + $0.60 per card transaction, more for Amex) and optional add-ons like payroll or unlimited receipt capture.
Does Xero limit the number of users on any plan? No. All three Xero plans (Early, Growing, Established) include unlimited users; the differences between tiers are about invoice/bill volume and feature depth, not seat count.
Why did QuickBooks Online get so much more expensive? QuickBooks raised its list prices in 2026 across all plans; Simple Start, Essentials, Plus, and Advanced now list at $38, $85, $140, and $340/month respectively, though new subscribers can get 50% off for the first three months.
Can I switch between these platforms later without losing my data? All three support data export (and QuickBooks/Xero support accountant-assisted migrations), but moving historical transaction data cleanly between platforms typically requires either a migration tool or manual re-entry, so it’s worth choosing carefully upfront.
Do any of these include payroll by default? No. Payroll is a paid add-on for all three: QuickBooks and Wave offer their own payroll add-ons, and Xero’s US payroll is powered by Gusto at $36/month plus $6 per employee or contractor.
AWS says its custom Trainium chips are cheaper to train on than renting Nvidia GPU instances. That’s a real, specific, AWS-published claim for Trainium2 — but when AWS announced the newer Trainium3 a year later, the cost claims got noticeably vaguer. This piece digs into exactly what AWS has and hasn’t published about Trainium’s economics, and the architectural reasoning for why custom silicon can be cheaper in the first place, without inventing numbers AWS hasn’t actually stated.
AT A GLANCE
Fact
Detail
What it is
AWS’s custom AI training silicon (Trainium2, generally available Dec. 2024; Trainium3, available Dec. 2025) versus renting Nvidia GPU-based EC2 instances (P5/P5e/P5en)
Who makes it
AWS, designed by its Annapurna Labs silicon team
Primary economic claim
Trn2 (Trainium2) instances: “30-40% better price performance than GPU-based EC2 P5e and P5en instances” — AWS’s own stated, specific comparison
Where it fits in the stack
Compute layer for large-scale model training and inference — an alternative purchasing option to Nvidia GPU EC2 instances on the same cloud
Trainium3 cost claims
Vague by comparison: AWS cites performance/efficiency gains over Trainium2 (not Nvidia) and a handful of customer anecdotes, with no AWS-stated percentage or dollar figure comparing Trainium3 directly to any named Nvidia instance
Short Verdict
AWS’s economic case for Trainium is genuinely specific in one place and genuinely vague in another. For Trainium2, AWS puts a number on it: 30-40% better price-performance than its own Nvidia-based P5e/P5en instances, a comparison AWS controls (it’s AWS’s pricing on both sides) but is at least a concrete, named, apples-to-apples figure. For Trainium3, launched a year later, AWS’s public materials pivot to comparing the new chip against its own previous generation (Trainium2) rather than against Nvidia, and the GPU-cost claims that do appear come from individual customers using unspecified comparison baselines. The architectural case for why custom silicon should be cheaper is sound and well-documented; the specific savings figure you’ll actually get depends heavily on workload, and AWS’s own disclosures get less precise as the product line gets newer.
The One Specific, Sourced Number: Trainium2 vs. P5e/P5en
AWS’s own Trn2 instance page states plainly that “Trn2 instances offer 30-40% better price performance than GPU-based EC2 P5e and P5en instances.” This is the clearest, most specific economic claim AWS makes anywhere in its Trainium materials: a named percentage range, against named competing instance types, both sold by AWS itself. It does not disclose the workloads used to generate that range, and because both sides of the comparison are AWS’s own instance pricing, it isn’t an independent, third-party benchmark against Nvidia hardware broadly — it’s AWS’s own GPU-instance line versus AWS’s own custom-silicon line.
AWS backs this up with customer-reported figures on the same page, each with its own stated (or unstated) baseline: poolside expects “savings of 40% compared to EC2 P5 instances” when training future models on Trn2 UltraServers; Databricks plans to deliver “lower TCO by up to 30%” for its customers (baseline not stated); Ricoh reports a 50% training-cost reduction “compared with the latest GPU machines in AWS” (without specifying which generation); and Stockmark reports a 20% training-cost reduction using the earlier Trn1 chip (baseline not stated). Separately, on the inference side, Refact.ai reports 1.5x higher tokens-per-dollar using Inferentia2-based Inf2 instances compared with Nvidia-based G5 instances — one of the few customer figures that names a specific Nvidia-based comparison instance.
Where the Claims Get Vaguer: Trainium3
Trainium3 reached general availability in Trn3 UltraServers in December 2025. Reviewing AWS’s and Amazon’s own press materials for this launch, the headline figures are about performance and efficiency versus Trainium2, not versus Nvidia: “up to 4.4x higher performance, 3.9x higher memory bandwidth, and 4x better performance/watt” than Trn2 UltraServers, with Amazon Bedrock inference described as “up to 3x faster” than Trainium2 and delivering “over 5x higher output tokens per megawatt at similar latency per user.” None of these figures compares Trainium3 to a named Nvidia GPU or instance type, and none is expressed as a dollar or percentage cost figure.
The closest things to a GPU cost comparison in Amazon’s own Trainium3 press release are customer anecdotes: Amazon states that customers including Anthropic, Karakuri, Metagenomi, NetoAI, Ricoh, and Splash Music are “reducing training and inference costs by up to 50% with Trainium,” without specifying whether this refers to Trainium3 specifically, an earlier generation, or what it’s measured against. One customer, Decart, reports “4x faster inference for real-time generative video at half the cost of GPUs” — the only explicit GPU-cost comparison in the release, and it names no specific GPU vendor or instance type. We are not treating “half the cost of GPUs” or “up to 50%” as generalizable, verified figures for Trainium3 specifically, because AWS itself doesn’t attach a clear baseline to either claim.
AWS’s Own Claims, Side by Side
Claim
Source
Baseline named?
Specific figure?
Trn2: “30-40% better price performance”
AWS Trn2 instance page
Yes — P5e and P5en instances
Yes — percentage range
poolside: 40% savings
AWS Trn2 instance page (customer quote)
Yes — EC2 P5 instances
Yes
Ricoh: 50% training cost reduction
AWS Trn2 instance page (customer quote)
Vague — “latest GPU machines in AWS”
Yes, but baseline unclear
Refact.ai: 1.5x tokens per dollar
AWS materials (customer quote)
Yes — EC2 G5 (Nvidia-based)
Yes
Trainium3: 4.4x performance, 4x perf/watt
AWS Trn3 announcement
Trainium2 (not Nvidia)
Yes, but not a cost figure
Decart: “half the cost of GPUs”
Amazon Trainium3 press release (customer quote)
No — “GPUs” unspecified
Qualitative only
AWS P5 (Nvidia) page: “reduce training cost by up to 40%”
The Architectural Case for Why Custom Silicon Can Be Cheaper
Separate from any specific percentage, AWS’s own “why purpose-built AI chips matter” materials lay out a qualitative argument that holds up independent of the exact numbers in any given generation:
Workload-specific design. Trainium’s NeuronCores are described by AWS as “purpose built for deep learning algorithms” rather than general-purpose graphics/compute silicon adapted for AI. A chip designed only to do matrix multiplication and the handful of operations deep learning actually needs can spend its entire transistor budget on that, instead of also carrying graphics-pipeline logic a training workload never touches.
No separate hardware-vendor margin. A GPU instance’s price has to cover Nvidia’s margin on the chip itself, on top of AWS’s own infrastructure and margin. A chip AWS designs itself (through its Annapurna Labs silicon team) removes that intermediate markup layer from the cost structure, at least in principle — AWS’s materials don’t quantify this specific effect in dollars, but the structural logic is real and is the same logic AWS has applied to its Graviton Arm CPUs.
Power efficiency compounds at scale. AWS ties Inferentia’s lower energy use per unit of work directly to cost and sustainability; at data-center scale, power and cooling are a direct, ongoing operating cost, so even a modest efficiency edge compounds over a long-running training job or high-volume inference workload.
Supply control. AWS’s own materials reference the “scarcity of the powerful A100 GPU” (via a quoted customer, OctoML) as a motivation for exploring alternatives — owning your own chip supply chain is itself an economic hedge against GPU shortages and the pricing power that scarcity gives Nvidia.
Independent analyst Patrick Moorhead, quoted in AWS’s own blog, frames this plainly: custom silicon “can provide public cloud customers with lower costs, higher performance” when designed well — a conditional statement (“when designed well”) that’s worth taking seriously rather than treating custom silicon as automatically cheaper.
Trade-offs
Pros
Cons
AWS does publish at least one specific, named-baseline price-performance figure for Trainium2 (30-40% vs. P5e/P5en)
That figure compares AWS’s own two product lines, not an independent Nvidia benchmark
The architectural reasoning for lower-cost custom silicon (no GPU-vendor margin, workload-specific design) is sound and documented
AWS doesn’t quantify the margin-removal effect in dollars anywhere reviewed for this article
Multiple customers report real-world savings, several with named Nvidia-based baselines (P5, G5)
Trainium3’s own launch materials give no comparable Nvidia cost figure at all, only Trainium2-to-Trainium3 performance gains
Nvidia-based P5 instances also claim generational cost improvements (up to 40% vs. previous-gen GPU instances), showing cost gains aren’t exclusive to custom silicon
Actual savings depend heavily on specific workload, model architecture, and software porting effort via AWS’s Neuron SDK
Who This Economics Case Is Relevant For
Teams already on AWS evaluating Trn2 UltraServers against P5e/P5en for large training runs have the clearest, most directly comparable AWS-published figure to work from (30-40%). Teams evaluating Trainium3 should budget time to run their own workload-specific benchmark rather than relying on a published Nvidia-comparison percentage, because AWS hasn’t published one for that generation as of this writing.
Who Should Look Elsewhere
Teams that need a vendor-neutral, third-party-verified cost comparison between Trainium and Nvidia hardware won’t find one in AWS’s own materials — every cost figure reviewed here comes from AWS or an AWS customer, comparing AWS’s own instance catalog. Organizations running workloads with heavy CUDA-specific dependencies, where porting cost to AWS’s Neuron SDK would likely exceed any compute savings, are also better served sticking with Nvidia GPU instances regardless of the published percentages.
Bottom Line
AWS’s economic pitch for custom silicon is real but uneven across generations. Trainium2 has one specific, named-baseline number behind it (30-40% better price-performance than P5e/P5en) plus several customer testimonials with named comparisons. Trainium3, a newer and faster chip, so far comes with efficiency and throughput claims measured against its own predecessor, not against Nvidia, and its one GPU-cost anecdote (“half the cost of GPUs”) names no specific hardware. The architectural reasoning for why custom, workload-specific silicon without a separate GPU-vendor margin should be cheaper is credible and consistent with AWS’s broader custom-silicon strategy (it mirrors the logic behind Graviton), but anyone weighing Trainium3 specifically against Nvidia should run their own numbers rather than lean on a percentage AWS hasn’t actually published.
FAQ
What’s the single most specific cost claim AWS makes about Trainium? That Trn2 (Trainium2) instances offer 30-40% better price performance than GPU-based EC2 P5e and P5en instances, stated directly on AWS’s Trn2 instance page.
Does AWS make the same specific claim for Trainium3? No. AWS’s Trainium3/Trn3 UltraServer launch materials compare the new chip’s performance and efficiency to Trainium2, not to any named Nvidia GPU or instance, and give no percentage or dollar cost figure for a Trainium3-vs-Nvidia comparison.
Why would custom silicon be cheaper than renting GPUs in principle? AWS’s own materials point to workload-specific chip design (no wasted silicon on graphics-pipeline logic a training job never uses), the removal of a separate GPU-vendor margin layer since AWS designs the chip itself, better power efficiency per unit of work, and controlling its own supply chain instead of competing for scarce GPU allocation.
Are the savings figures AWS publishes independently verified? No. Every cost comparison reviewed for this article comes from AWS itself or from AWS customers quoted in AWS’s own press and product materials, comparing AWS’s own instance catalog. None is a neutral, third-party benchmark against Nvidia hardware broadly.
Most writing on Google Consent Mode v2 treats it as a compliance checklist: get a banner, link to Google’s policy page, done. That’s the right level for a marketer auditing their account — we’ve covered that checklist separately. This piece is for whoever actually has to write or review the code: what the gtag('consent', ...) API does at the wire level, how Google Tag Manager’s consent handling differs from raw gtag.js, and the specific implementation mistakes that silently break measurement even when the banner itself looks correct. Everything below is sourced directly from Google’s own developer and support documentation.
At a Glance: What Consent Mode v2 Actually Requires
Requirement
Detail
Who it applies to
Advertisers and sites using Google tags/SDKs for measurement, ad personalization, or remarketing with end users in the EEA (Google’s enforcement also extends to the UK and Switzerland in related consent-audit guidance)
The two v2-specific signals
ad_user_data (consent to send user data to Google for advertising) and ad_personalization (consent for personalized advertising/remarketing), added alongside the original ad_storage and analytics_storage
Enforcement timeline
Google told advertisers the changes could require action “before March 2024” as it began enhancing enforcement of its EU User Consent Policy
Consequence of non-compliance
Per Google’s EU User Consent Policy, Google “may limit or suspend your use of the product, or terminate our agreement with you”; Google’s consent-mode guidance separately warns of “loss in data” if consent signals aren’t sent
Two implementation levels
Basic (tags blocked until interaction) or Advanced (tags load immediately, send cookieless pings while consent is denied)
Persistence
Consent Mode itself does not store the user’s choice — your site must persist it (e.g., a first-party cookie) and resend it on every page
Short Verdict
If you’re implementing this yourself rather than through a certified consent management platform (CMP), the two things most teams get wrong are ordering (consent defaults must run before any Google tag fires, and your consent tool has to run before or alongside it, not after) and persistence (Consent Mode doesn’t remember anything between page loads — your code has to). Get those two things right and the rest is mostly filling in which of the four signals your banner’s categories map to. Advanced mode is the better default for most sites that want usable conversion data; basic mode is the better default if your legal team’s position is that nothing — not even a cookieless ping — should reach Google before a choice is made.
The Four Signals, Precisely
Signal
Introduced in
What denying it does
ad_storage
Consent Mode v1
Blocks Google Ads cookies and device identifiers from the Google Analytics tag and Firebase SDK
analytics_storage
Consent Mode v1
Blocks first-party analytics cookies/app identifiers from being read or written
ad_user_data
Consent Mode v2
Stops sending user data to Google for advertising purposes — this disables features like enhanced conversions and user_id collection
ad_personalization
Consent Mode v2
Disables personalized advertising features such as remarketing. If you also set the older allow_ad_personalization_signals flag with a conflicting value, personalization is disabled outright — so implement ad_personalization explicitly rather than relying on the legacy flag
The Default/Update Pattern
Consent Mode runs on exactly two commands. Default sets the starting state before any user choice and must execute before any config or event command on the page:
The region parameter takes ISO 3166-2 codes, so you can set a stricter default for the EEA and UK while leaving other regions untouched — a default call with no region specified becomes the fallback for everyone not matched by a more specific regional default. The more specific regional match always wins. wait_for_update (in milliseconds) tells Google tags to pause briefly for an asynchronous consent banner to call update before any tag fires, which matters because banners that render client-side after the page has already started loading can otherwise lose the race.
Update sends the user’s actual choice after they interact with your banner or privacy settings, and is also how you handle revocation (changing a previously granted signal back to denied):
Google’s own documentation flags a specific failure mode here: if an update call fires late — for example, right as the page is unloading — the consent transition can be lost entirely. Send the update as soon as the choice is made, not on a delay or deferred to an unload handler.
Basic vs Advanced: What’s Actually Different on the Wire
The distinction isn’t just “stricter vs looser” — the two modes have genuinely different data flows:
Basic consent mode: Google tags stay blocked until the visitor interacts with the banner at all. If they decline, nothing is sent to Google — not even the fact that they declined. If they accept, tags load and send default consent states followed by the updated states. Conversion measurement falls back on Google’s general conversion model, which Google describes as less detailed than the advertiser-specific alternative.
Advanced consent mode: Google tags load as soon as the page opens, with defaults set to denied (unless you’ve configured otherwise). While consent remains denied, tags still send consent-state and measurement pings — but cookielessly, storing no cookies and sending no full measurement data. Only once the visitor grants consent do tags send full measurement. This cookieless-ping behavior is what feeds Google’s conversion modeling, which it says becomes advertiser-specific (and more detailed) only when this data is available.
Consent-state pings carry a timestamp, referrer, user agent (on web), a boolean consent flag, a random per-page-load number, and an identifier for the consent platform in use (such as a CMP’s Developer ID). Google says it needs roughly seven full days of implementation, and a minimum data threshold per slice, before any conversion-modeling impact shows up in reporting — so don’t judge an implementation by what you see in the first 48 hours.
Two Advanced-Mode Controls Worth Knowing
Two optional gtag.js settings specifically support advanced consent mode and are easy to miss in a basic implementation guide:
URL passthrough — gtag('set', 'url_passthrough', true);, placed before any config command — keeps ad-click and session identifiers in the page URL instead of a cookie, when ad_storage is denied. Without it, a denied-consent visitor who clicks through from an ad can still be effectively “lost” for attribution purposes even in advanced mode.
Ads data redaction — gtag('set', 'ads_data_redaction', true); — strips ads-click identifiers from requests sent to Google when ad_storage is denied. This only takes effect while ad_storage is actually denied; it’s a no-op otherwise.
Google Tag Manager Is Not a Drop-In Replacement for Raw gtag Calls
This is the single most common implementation mistake Google’s own documentation calls out directly: in Google Tag Manager, don’t call gtag('consent', 'update', ...) the same way you would in a bare gtag.js setup. GTM queues gtag commands, and a queued command may not be processed before the very next event fires — which can mean a tag fires with stale consent state. Instead, GTM has its own consent APIs for this purpose: setDefaultConsentState, updateConsentState, and optionally gtagSet, used inside a consent template. Most Google-certified CMPs ship a community template that wires this up correctly, which is the main practical reason Google recommends a CMP for GTM-based sites rather than a fully custom build.
The required load order, per Google’s documentation, is: the default consent snippet first, then the Google tag itself, then your consent banner/CMP code. Google is explicit that getting this order wrong means “consent defaults won’t work” — the default has to already be in place before the tag that’s supposed to respect it even loads.
Pros and Trade-Offs of Each Implementation Path
Certified CMP + advanced mode: least engineering effort, best conversion modeling data. Trade-off: Google tags load and ping (cookielessly) before any explicit user choice, which some legal teams are uncomfortable with regardless of the technical cookieless guarantee.
Certified CMP + basic mode: cleanest privacy story — literally nothing reaches Google pre-consent. Trade-off: weaker, generalized conversion modeling until consent is granted.
Fully custom gtag/GTM implementation: complete control over every signal and timing detail. Trade-off: you own getting default/update ordering, region scoping, and persistence exactly right — and re-verifying it every time Google changes the API, since none of this is abstracted away for you the way a CMP template handles it.
Who Needs to Act
Any site or app using Google tags or SDKs for ad personalization, remarketing, or conversion measurement with visitors in the EEA needs verifiable consent signals flowing to Google — this also covers Google Analytics data used inside Google Ads, Search Ads 360, or Display & Video 360, per Google’s own guidance. If you’re already on a Google-certified CMP with ads personalization enabled, confirm with your provider that they’re running the current Consent Mode v2 template rather than assuming an existing integration was auto-upgraded. If you built your own banner and consent logic, audit it specifically against the ordering and persistence issues above — they’re the failure modes that pass a quick visual check of the banner while still sending incorrect or incomplete signals underneath.
Bottom Line
Consent Mode v2 is a small API surface — two commands, four signals, two optional flags — but the implementation details that break it are almost all about timing and persistence rather than the signals themselves: load order, the GTM-specific consent API instead of raw gtag calls inside Tag Manager, and remembering that Consent Mode doesn’t store anything for you between page loads. Get a Google-certified CMP if you want that complexity handled for you; if you’re building it yourself, treat the ordering requirement as non-negotiable and test consent state changes across a full page reload, not just in the same session.
FAQ
Does Consent Mode v2 replace my consent banner? No. Google’s documentation is explicit that Consent Mode doesn’t provide a banner or collect consent itself — it’s the API that tells Google tags what your banner’s consent choices were, so it has to work alongside a banner or CMP, not instead of one.
Is advanced consent mode required? No, Google documents both basic and advanced as valid implementations. Advanced enables advertiser-specific conversion modeling; basic is the stricter, fully-blocked-until-consent option.
Why would my consent signals silently fail in Google Tag Manager even though the banner displays correctly? The most common cause, per Google’s own guidance, is calling the raw gtag('consent', 'update', ...) command inside GTM instead of using GTM’s dedicated consent APIs (setDefaultConsentState/updateConsentState) — GTM queues gtag commands, so timing isn’t guaranteed the way it is in a bare gtag.js page.
What happens if I never implement Consent Mode for EEA traffic? Google’s EU User Consent Policy states it may limit or suspend use of the relevant Google product, or terminate its agreement with you, for non-compliance; separately, Google’s technical documentation warns that skipping verifiable consent signals “may lead to loss in data” for measurement and personalization features.
How does this relate to a consent management platform (CMP)? A CMP handles displaying the banner and collecting the user’s actual choice; many Google-certified CMPs then automatically translate that choice into the correct Consent Mode signals for you, including the GTM-specific wiring described above. For how to evaluate and choose a CMP itself, see our comparison of consent management platforms for ad compliance.
Open source keyless signing infrastructure for software artifacts, under OpenSSF/Linux Foundation
“Who signed this, and can I verify it without managing long-lived keys?”
SLSA (Supply-chain Levels for Software Artifacts)
A framework of build-track levels (0–3) defining how trustworthy a build’s provenance is
“How tamper-resistant was the process that produced this artifact?”
Provenance attestation
A signed, structured statement (in-toto format) describing how/where/from-what an artifact was built
“What’s the verifiable, machine-readable evidence behind the SLSA claim?”
Short Verdict
Sigstore and SLSA solve two different, complementary problems, and most teams need both, not one or the other. Sigstore answers “who signed this artifact,” using short-lived, identity-bound certificates instead of long-lived private keys you have to protect and rotate forever. SLSA answers a bigger question — “how trustworthy was the build process itself” — by defining escalating levels of build-platform hardening, with signed provenance as the evidence that ties a specific artifact to a specific, auditable build. Neither is a product you buy; both are specs and open tooling you adopt incrementally, and GitHub Actions now ships native support for generating the attestations that back both.
What Sigstore Actually Does
Sigstore’s own documentation frames the problem plainly: unsigned software is exposed to typosquatting, compromised distribution sites, and post-publication tampering, while traditional key-based signing has its own failure modes — proving identity, protecting and distributing keys, and recovering trust after a key leaks. Sigstore’s answer is to replace long-lived private keys with short-lived, identity-bound ones, via three components:
Cosign — the client that signs and verifies artifacts (binaries, container images, SBOMs).
Fulcio — a code-signing certificate authority that checks an OpenID Connect (OIDC) identity token (a CI workflow’s identity, a service account, or a user’s email) and, if valid, issues a short-lived certificate binding that identity to an ephemeral public key.
Rekor — a tamper-resistant, append-only transparency log that records every signing event’s digest, signature, and certificate, so signatures are publicly auditable after the fact.
The “keyless” part works like this: the client generates a throwaway key pair, sends a certificate signing request to Fulcio along with its OIDC token, Fulcio verifies the token and issues a short-lived cert, the private key is discarded immediately after signing, and the event lands in Rekor’s log. Verification checks the signature, confirms the certificate’s identity matches what’s expected (e.g. “this was signed by this exact GitHub Actions workflow”), validates the cert chain against Sigstore’s root of trust, and confirms the matching Rekor log entry exists. Nobody — not even the signer — has a long-lived private key to lose or leak.
What SLSA Actually Defines
SLSA’s Build track defines four levels of build-process trustworthiness, each one a strict superset of the last:
Level
Requirement
What it guards against
Build L0
No requirements — the absence of SLSA
Nothing; baseline for dev/test builds
Build L1
Consistent build process; generates provenance describing the build platform, process, and top-level inputs
Accidental mistakes — provenance may be unsigned and is easy to forge or bypass
Build L2
Everything in L1, plus builds run on dedicated hosted infrastructure, with signed provenance tied to that platform
Tampering after the build — consumers can validate provenance authenticity
Build L3
Everything in L2, plus the platform isolates runs from each other and keeps signing secrets away from user-defined build steps
Tampering during the build, including by other jobs on the same platform
Provenance itself — the artifact that ties each level together — is formally defined in the SLSA/in-toto attestation model as a signed, machine-readable statement with three parts: an envelope (the signature and signer identity, typically in DSSE format), a statement (which binds the attestation to a specific subject — the artifact’s hash — plus a predicate type), and a predicate (the actual metadata, such as the build command and dependencies used). The point of structuring it this way, rather than just signing the artifact directly, is that the metadata is explicit and machine-readable — a policy engine can check not just “is this signed” but “was this built from the expected source repo, by the expected CI system, using the expected command.”
Putting It Together in a Real Pipeline
GitHub Actions has native support for generating these attestations without standing up Fulcio or Rekor yourself — GitHub operates its own Sigstore-backed signing path behind the action. Per GitHub’s own documentation, available on all current plans (public repos on Free/Pro/Team; private repos need GitHub Enterprise Cloud), the workflow is:
1. Grant the workflow id-token: write, contents: read, and attestations: write permissions (packages: write too, for container images). 2. After the build step, add a step using GitHub’s attestation action, pointing it at the built artifact. 3. For binaries, set the artifact’s path; for container images, set the fully-qualified image name and its sha256: digest and push to the registry; for SBOMs, add the SBOM path as a separate predicate.
Verification happens with the GitHub CLI: gh attestation verify <artifact-path> -R <org>/<repo> for binaries, or the same command prefixed with oci:// against a logged-in registry for container images. That single command checks the signature, the signer identity, and the Rekor-equivalent log entry in one step — the same verification chain Sigstore defines generally, wired into GitHub’s CI identity.
Trade-offs
Pros of adopting Sigstore/SLSA: no long-lived signing keys to protect, rotate, or leak; publicly auditable transparency log means a compromised identity leaves a trace; incremental adoption — SLSA L1 (just generate provenance) is low-effort and still gives you an audit trail; GitHub’s native integration means no separate signing infrastructure to run for the common case.
Cons / real costs: SLSA L3 requires genuine build-platform isolation, which is a real engineering investment, not a config flag; verifying attestations downstream requires policy tooling (admission controllers, deployment gates) that many teams haven’t built yet, so signed provenance sitting unused provides no protection; OIDC-based keyless signing shifts trust to your CI identity provider’s security, which becomes a new high-value target; private-repo attestation support requires GitHub Enterprise Cloud, which is a real constraint for teams on lower tiers.
Who Should Adopt This Now vs. Who Can Wait
Adopt now if you publish artifacts that other teams or the public consume — open source libraries, container base images, CLI binaries — where an unsigned or unverifiable artifact is a direct supply-chain risk to everyone downstream; if you’re already using GitHub Actions, generating SLSA L1/L2 provenance is a small, low-risk addition. It’s also worth prioritizing if you’re subject to regulatory pressure around software supply-chain integrity (e.g. government or critical-infrastructure vendors), where provenance attestation is increasingly an explicit requirement rather than a nice-to-have. It can reasonably wait if your build output never leaves a single trusted, access-controlled internal environment and you don’t yet have any downstream policy engine that would consume the attestations — in that case, invest first in the verification/enforcement side (so signed provenance actually gates deployment) before spending more effort generating attestations nobody checks.
Bottom Line
Sigstore removes the key-management excuse for not signing artifacts; SLSA gives you a shared vocabulary and a staged path for how much you trust the process that produced them; provenance attestation is the concrete, verifiable artifact that connects the two. None of this is exotic anymore — it’s a few workflow permissions and one action step in GitHub Actions to get real, auditable evidence of what built your software and from what. The harder, still-unsolved part for most teams is the back half: actually verifying and enforcing those attestations at deploy time, not just generating them.
FAQ
Do I need to run my own Fulcio/Rekor instance? No — the public Sigstore infrastructure is free to use for open source projects, and GitHub Actions’ native attestation feature uses GitHub’s own Sigstore-backed signing path, so most teams never operate Fulcio or Rekor themselves.
Is SLSA a certification I can get audited for? No — SLSA is a specification describing levels of build-process guarantees, not a certifying body. You self-assess or build tooling (like the Generic SLSA Verifier) to check a given artifact’s provenance against a level’s requirements.
What’s the difference between signing an artifact and attesting to it? A plain signature only proves who signed something; an attestation is a structured, signed statement that makes the claim explicit (e.g. “built from commit X using command Y”), which is what lets automated policy engines make decisions rather than just confirming authenticity.
Does this replace secrets management or policy-as-code tooling? No — supply-chain signing/provenance, secrets management, and policy-as-code/CSPM are three distinct, complementary layers of a secure pipeline. See the related posts below for the other two.
Before comparing these three tools, one naming note worth clearing up: VistaCreate has not been discontinued or absorbed into anything, and it isn’t the same product as Creatopy. VistaCreate is the current name for what started life as Crello, a browser-based design editor launched by Depositphotos in 2016; Vistaprint (now operating as Vista) acquired Crello and Depositphotos in October 2021 for $85 million and rebranded the editor as VistaCreate, which is still the active, maintained product today. Creatopy is a different, unrelated tool — the rebrand of Bannersnack, an ad-banner-focused design app — so don’t confuse the two when researching alternatives.
With that settled: Canva, Adobe Express, and VistaCreate are the three most relevant template-driven design tools for building ad creative in 2026 — banner ads, social ad variants, and multi-format resizing — without a dedicated design team. They overlap heavily on paper (templates, brand kits, AI image tools, one-click resizing) but differ meaningfully on price, team collaboration model, and how deep the AI tooling goes.
At a Glance
Tool
Free plan
Entry paid price
Team plan entry
Best for
Canva
Yes — Free
Pro, ~$18/month (1 person)
Business, ~$25/user/month, 3-seat minimum
Largest template and asset library, most mature ecosystem
Adobe Express
Yes — Free
Premium, $9.99/month
Teams, $4.99/license/month in year one (then $7.99), 2-seat minimum
Solo marketers and small teams wanting the cheapest all-in seat price
Canva’s exact current pricing is in active flux: multiple outlets reported in 2026 that Canva significantly raised prices on its Teams/Business plan — in some cases over 300% for existing customers migrating off the old flat-rate Teams plan — with a Canva spokesperson confirming the original pricing had been unchanged for roughly four years before the increase. Figures above reflect pricing-tracker data current as of this writing; confirm the exact number for your seat count directly on Canva’s pricing page before budgeting, since Canva’s own page could not be independently re-verified for this article.
Short Verdict
Canva has the deepest template library and the most name recognition, but it’s now also the most expensive of the three at the team tier, and 2026’s price changes make it worth double-checking your actual renewal cost before assuming the old rate still applies. Adobe Express is the best value if you want real generative-AI depth (Firefly) and any tie-in to Photoshop, with the cheapest team-plan entry price of the three. VistaCreate is the value pick for a solo marketer or small team: one Pro subscription covers up to 10 seats, which undercuts per-seat pricing at Canva or Adobe Express if you actually have several people touching the account — the trade-off is a smaller template library and collaboration that’s sequential rather than real-time.
Pricing and Feature Breakdown
Feature
Canva
Adobe Express
VistaCreate
Free tier limits
Free plan, core templates and tools
Free: 100,000+ templates, 5GB storage, limited generative AI
No separate enterprise tier; an API suite is offered for businesses
Pros and Cons
Canva — Pros: by far the largest template and stock-asset library; Magic Resize makes multi-format ad campaigns fast; near-universal brand recognition means freelancers and agencies rarely need to train clients on it. Cons: 2026 price increases on the team tier, in some cases reported as steep as 300% for existing customers migrating plans; confirm your actual renewal price rather than assuming last year’s rate.
Adobe Express — Pros: cheapest team-plan entry price of the three; real generative-AI depth through Firefly, plus a path up to Photoshop on web/mobile; One-Click Resize covers ad-format variants cleanly. Cons: free tier’s generative AI allowance is limited; the jump to Firefly Pro ($19.99/month) is needed for meaningful monthly AI credit volume.
VistaCreate — Pros: cheapest effective per-seat cost if you have a small team, since up to 10 seats share one Pro plan; unlimited brand kits and storage on Pro. Cons: smaller template and asset library than Canva; team “collaboration” is sequential access, not simultaneous real-time co-editing, which matters if multiple people need to work the same ad set at once.
Who’s a Good Fit For Each
Choose Canva if template variety and brand recognition matter more than being the cheapest option, and you’re prepared to verify current team pricing before committing. Choose Adobe Express if your team already pays for Adobe Creative Cloud or wants deeper generative-AI tooling without jumping straight to full Photoshop. Choose VistaCreate if you’re a solo marketer or a small team (up to 10 people) who wants the lowest all-in monthly cost and doesn’t need simultaneous real-time co-editing.
Who Should Look Elsewhere
Agencies running large, distributed creative teams that need true simultaneous multi-user editing at scale will find VistaCreate’s sequential access model limiting — Canva or Adobe Express fit that workflow better. And if budget is the only factor and your team is larger than 10 people, run the actual per-seat math for all three rather than assuming VistaCreate’s single-Pro-plan model still wins, since it scales differently than Canva’s or Adobe Express’s per-seat pricing.
Bottom Line
All three tools can produce solid, multi-format ad creative without a dedicated designer. The decision mostly comes down to team size and how much you value a deep template library versus the lowest monthly bill: Canva for breadth and brand recognition (at a 2026 price point worth double-checking), Adobe Express for the best generative-AI value and Creative Cloud tie-in, and VistaCreate for the cheapest small-team math.
FAQ
Is VistaCreate the same thing as Creatopy? No. VistaCreate is the rebrand of Crello (acquired by Vistaprint/Vista in 2021). Creatopy is an unrelated product — the rebrand of Bannersnack, a separate ad-banner design tool.
Why did Canva’s pricing change so much in 2026? Multiple outlets reported significant increases to Canva’s Teams/Business plan in 2026, with a Canva spokesperson attributing it to pricing that had been unchanged since the plan launched roughly four years earlier. Exact figures vary by region and existing-customer transition terms, so confirm your own renewal price directly with Canva.
Can I use any of these for free indefinitely? Yes — all three offer a genuinely free tier (Canva Free, Adobe Express Free, VistaCreate Starter) with no forced trial expiration, though premium templates, full AI credit allowances, and resizing tools generally require a paid plan.
Which tool is best for resizing one ad into multiple platform formats? All three offer a dedicated resizing feature on their paid tiers — Canva’s Magic Resize, Adobe Express’s One-Click Resize, and VistaCreate’s built-in resizing on Pro — so this isn’t a strong differentiator; team size and budget matter more for this decision.
Pro: on-demand Active CPU + Provisioned Memory, billed per region (e.g. $0.128/CPU-hour and $0.0106/GB-hr in US regions)
Short Verdict
“Edge compute” no longer means one thing. Cloudflare Workers is the most mature V8-isolate platform and the cheapest entry point for high-request, low-per-request-CPU workloads (API proxies, auth checks, A/B routing). Fastly Compute is the WebAssembly-native option, letting you ship Rust, Go, or C++ to the edge, not just JavaScript, with a generous free tier and usage-based pricing that rewards low CPU time per request. Vercel is the odd one out in 2026: its own documentation now recommends migrating away from the Edge runtime toward Node.js on “Fluid Compute,” which is not a classic isolate-at-every-PoP model but a CPU/memory-metered compute layer — meaning Vercel is less a pure edge-isolate competitor to Cloudflare/Fastly today and more a full-stack hosting platform with edge routing on top.
What Each Platform Actually Runs
Cloudflare Workers executes code in V8 isolates — the same lightweight JavaScript sandboxing engine Chrome uses for browser tabs — rather than spinning up a container or VM per request. Because an isolate doesn’t need to boot an OS or runtime process, Workers avoids the classic serverless cold-start penalty; Cloudflare’s pricing page confirms requests are billed on CPU time actually used, not wall-clock duration, and the free tier caps CPU time per invocation at 10ms, with paid plans defaulting to a 30-second CPU cap (configurable up to 5 minutes per invocation, 15 minutes for Cron Triggers/Queue consumers).
Fastly Compute takes a different technical route: everything compiles to WebAssembly and runs in Fastly’s Wasmtime-based sandbox, regardless of source language. Fastly markets this explicitly as a memory-safety advantage (“pioneering WebAssembly” to guard against classes of memory-safety bugs) and supports JavaScript, Rust, Go, and C++ as first-class source languages, compiled ahead of time to Wasm rather than interpreted per request. Fastly’s own FAQ claims the model “eliminates cold starts, allowing code to execute in microseconds” — a vendor claim with no published methodology, so treat the magnitude skeptically even though the direction (fast, AOT-compiled Wasm startup) is architecturally plausible.
Vercel’s position has shifted meaningfully. Its Edge Runtime (V8-isolate based, similar in spirit to Workers) still exists, but Vercel’s own documentation as of 2026 explicitly says: “We recommend migrating from edge to Node.js for improved performance and reliability,” and as of Next.js 16.3, setting runtime = 'edge' in a Next.js app is no longer even honored — routes run on Node.js regardless. The replacement is Fluid Compute, a pricing and execution model that bills “Active CPU” (only while your code is actually executing, pausing during I/O wait) plus “Provisioned Memory” (billed for the full instance lifetime). This is architecturally closer to a smart, auto-scaled container/function model than to a stateless isolate running at every edge PoP simultaneously.
Comparison: Limits, Languages, and Pricing Mechanics
Dimension
Cloudflare Workers
Fastly Compute
Vercel Functions
Primary languages
JavaScript/TypeScript, plus Wasm-compiled languages
JavaScript, Rust, Go, C++ (all → Wasm)
Node.js (recommended), legacy Edge runtime (V8 subset), Bun supported
Max execution window
Up to 5 min CPU/invocation (paid), 15 min for scheduled/queue triggers
Not published in the pages reviewed here
Edge runtime: must start responding within 25s, can stream up to 300s
Filesystem / Node API access
No filesystem; Node.js compatibility layer (nodejs_compat) covers a growing subset
No native filesystem; language-specific Wasm SDKs
Full Node.js APIs on the Node.js runtime; Edge runtime explicitly blocks filesystem access and most Node APIs
Billing unit
Requests + CPU-ms
Requests + vCPU-ms
Invocations + Active CPU (per-hour) + Provisioned Memory (GB-hr), varies by region
Cloudflare Workers pros: largest, most mature edge network; cheapest at high request volume with low per-request CPU; simple mental model (one isolate, one request).
Cloudflare Workers cons: JavaScript/Wasm-first — not a natural fit if your team wants to ship Go or Rust services without a JS entry point; Node.js compatibility is a shim, not full parity.
Fastly Compute pros: genuine multi-language support (Rust/Go/C++ compiled directly, not transpiled); strong free tier (10M requests + 100M vCPU-ms/month); Wasm sandboxing is a real security property, not just marketing.
Fastly Compute cons: smaller ecosystem and community than Cloudflare’s; the $500/month Starter package is a bigger jump than Cloudflare’s $5/month entry if you outgrow the free tier but aren’t ready for enterprise contact-sales pricing.
Vercel pros: best-in-class developer experience for Next.js and frontend-framework deployments; Fluid Compute’s “pause CPU billing during I/O wait” model is genuinely good for API-call-heavy, I/O-bound functions; full Node.js API access removes the edge-runtime limitation entirely.
Vercel cons: no longer positioned as a pure edge-isolate platform — if the reason you wanted “edge compute” was running the exact same stateless isolate at every PoP with no regional pinning, Vercel’s own guidance is steering you toward regional Node.js functions instead.
Who Should Use Which
Choose Cloudflare Workers for latency-sensitive, high-volume, low-compute-per-request logic: auth/JWT validation at the edge, API gateways, bot mitigation, header rewriting, and anything where you want the same JS/TS logic running identically at hundreds of PoPs with minimal per-request cost. Choose Fastly Compute when you specifically need a non-JavaScript language at the edge (Rust or Go teams in particular), or when Wasm’s sandboxing model matters for your security posture, and your traffic profile fits comfortably inside or just above the free tier. Choose Vercel when your priority is shipping a full Next.js/React application with server-side rendering, API routes, and a polished CI/preview workflow — and treat its edge capabilities as a routing/CDN layer on top of a primarily Node.js compute model, not as a drop-in Workers/Compute replacement. Teams that need true multi-region active-active isolate execution with no single compute “home region” should look at Cloudflare or Fastly first.
Bottom Line
The three platforms have diverged more than they’ve converged since the “edge functions” category first took shape. Cloudflare and Fastly are still competing head-to-head as isolate/Wasm-based edge runtimes with genuinely comparable pricing mechanics (both bill requests + compute-time, both offer meaningful free tiers). Vercel has moved toward a different architecture entirely — Node.js-first, CPU/memory-metered, I/O-aware billing — and now explicitly discourages its own Edge runtime in favor of that model. Match the decision to what you’re actually building, not to which vendor says “edge” the loudest.
FAQ
Is Vercel still an “edge computing platform” in 2026? It still offers an Edge runtime and edge routing/CDN, but Vercel’s own docs now recommend Node.js on Fluid Compute over the Edge runtime for most workloads, and Next.js 16.3+ no longer honors runtime: 'edge' at all — so its center of gravity has moved toward regional compute rather than universal edge isolates.
Can I run a database connection from an edge function? All three platforms restrict or complicate persistent TCP connections from isolate/Wasm runtimes; the common pattern is an HTTP-based or connection-pooling-aware database driver rather than a raw long-lived socket, regardless of platform.
Which is cheapest at low volume? Both Cloudflare Workers and Fastly Compute have usable free tiers (100K requests/day and 10M requests/month respectively) before any payment is required; Vercel’s Hobby plan is also free but intended for personal/non-commercial use per its terms.
Do these platforms support WebAssembly the same way? No — Fastly’s Compute is Wasm-native for every supported language, while Cloudflare Workers runs JS/TS natively in V8 and supports Wasm as a module you call into, not as the universal compilation target. For a deeper look at server-side Wasm runtimes themselves (Wasmtime, Fermyon Spin) rather than the hosted edge platforms built on them, see our related piece linked below.
“Email security gateway” used to mean one thing: inbound mail routes through a vendor’s servers (an MX record change), which match it against spam signatures, malware hashes, and known-bad sender lists before letting it through. That architecture still exists and still works for commodity spam and malware — but business email compromise (BEC) and highly targeted phishing rarely trip a signature at all, because there’s no malicious attachment or known-bad link to catch. That gap is why the three vendors most worth comparing in 2026 — Proofpoint, Mimecast, and Abnormal AI (formerly Abnormal Security) — now split along a real architectural line: traditional gateway/signature filtering layered with AI, versus a platform built from the ground up on behavioral AI with no gateway mode at all. None of the three publish self-serve pricing, which is itself a buying consideration.
This piece is about the enterprise-tier products from each vendor, not entry-level SMB bundles — see our guide to email security and anti-phishing tools for small businesses for how Microsoft 365’s built-in protection and Proofpoint’s SMB-focused Essentials tier compare for smaller teams.
At a Glance
Vendor
Deployment model
Core defense approach
Pricing
Best for
Proofpoint (Core Email Protection)
API-based or secure email gateway (SEG) — your choice
Multi-model behavioral AI layered on top of M365/Workspace, plus traditional SEG filtering
Quote-based; not published
SOC teams wanting one investigation workflow across inbound, BEC, and account-takeover threats
Mimecast (Advanced Email Security)
MX-based gateway or API-based — your choice
AI/ML detection (anomaly detection, social graphing, computer vision) plus sandboxing
Quote-based; not published
Orgs wanting security bundled with archiving, continuity, and awareness training
Abnormal AI
API-only — no MX change, no gateway mode
Pure behavioral AI, explicitly positioned to displace or sit behind an existing SEG
Quote-based; not published
Microsoft 365/Google Workspace shops that already have a SEG and want to catch what it misses
Short Verdict
If you want one vendor covering inbound threats, account takeover, and a SOC-friendly investigation console in a single pane, Proofpoint‘s Core Email Protection is the most complete single product of the three. If you need archiving, continuity, and security-awareness training bundled with your gateway — common in regulated mid-market and enterprise accounts — Mimecast fits that bundle better than either competitor. If you already run a traditional SEG (including Proofpoint’s or Mimecast’s own gateway mode, or Microsoft’s built-in Defender for Office 365) and want a second, API-only layer specifically to catch business email compromise and account-takeover attempts that signature-based filtering misses, Abnormal AI is built exactly for that job — and increasingly for governing AI agents and non-human identities too. None of the three list prices publicly, so budget for a sales cycle regardless of which you choose.
How Each One Actually Works
Proofpoint Core Email Protection adds an AI detection layer on top of Microsoft 365 or Google Workspace, deployable either through an API connection to the mail platform or as a traditional secure email gateway — so it can run as a drop-in SEG replacement or as a second layer alongside your existing mail flow. Proofpoint describes continuous protection across inline, in-mailbox, post-delivery, and click-time stages, with a unified “Threat Protection Workbench” covering inbound threats, account takeover, supplier risk, and credential compromise in one console. It also automates abuse-mailbox triage (the “Satori” agent) for repeated user-reported phishing emails, and surfaces detections directly inside the Microsoft 365 admin console. Proofpoint’s own marketing claims it catches 27% more novel threats than competing products with the industry’s lowest false-positive rate — a vendor claim, not an independently audited figure, so weigh it as a starting point for your own proof-of-concept rather than a settled fact.
Mimecast Advanced Email Security can be deployed MX-based (mail routes through Mimecast first, intercepting threats inline) or API-based (no MX change required), and works across Microsoft 365, Google Workspace, and on-premise or hybrid mail. Its detection stack combines anomaly detection with social-graph analysis, sandboxing, on-click protection, and computer vision specifically built to spot impersonated login pages and brand logos. Mimecast bundles this with contextual warning banners, SIEM/XDR integrations (it names CrowdStrike, Netskope, and Palo Alto Networks XSOAR), and — notably — the option to add continuity, DMARC management, security-awareness training, and email archiving within the same platform. Mimecast reports more than 42,000 customers, another vendor-sourced figure.
Abnormal AI (Abnormal Security rebranded to Abnormal AI in April 2025, per the company’s own announcement) takes the most architecturally distinct position of the three: it has no gateway mode at all. It connects via API to Microsoft 365, Google Workspace, and identity providers (Microsoft Entra, Okta, Ping Identity), builds an “Identity Trust Graph” of human, non-human, and cloud identities, and learns each organization’s normal behavior patterns to flag meaningful deviations automatically. Its positioning is explicitly adversarial toward traditional gateways — a “Displace Your SEG” use case built on the argument that modern attacks are engineered to slip past signature- and reputation-based filtering precisely because they contain no malware or known-bad link. Abnormal has also expanded into identity threat detection and, more recently, governance for AI agents and non-human identities, with integrations into platforms like Anthropic, OpenAI, and Microsoft Copilot. Its benchmark claims (46× fewer missed attacks, 60× fewer false positives, 21× faster processing versus tested general-purpose LLMs) are self-reported and should be validated in your own environment.
The Real Architectural Split
It’s a mistake to read this as simply “two old gateway vendors vs. one AI upstart” — Proofpoint and Mimecast have both layered real AI/ML detection on top of their gateway heritage, and both now offer API-based deployment as an alternative to MX rerouting. The cleaner distinction is that Proofpoint and Mimecast still offer a gateway mode as a first-class option, while Abnormal AI doesn’t have one at all — it’s designed to sit on top of whatever mail security you already have (including a competitor’s gateway) rather than replace your mail routing. That makes Abnormal a natural second layer for organizations that are reasonably happy with their existing SEG but keep losing BEC and account-takeover cases to it, and makes Proofpoint or Mimecast the more natural single-vendor choice for an organization starting from scratch.
Pricing
None of the three vendors publish per-seat or tiered pricing on their official sites — all three route buyers to a demo request or “contact sales” form, consistent with how enterprise email security is typically sold (scaled to mailbox count, feature tier, and contract length through a direct or channel sales process). Treat any specific dollar figure you see quoted by a third-party aggregator as an estimate, not a list price, and get a quote for your own mailbox count before budgeting.
Pros and Cons
Proofpoint — Pros: broadest single-console coverage (inbound, BEC, account takeover, supplier risk); flexible API or SEG deployment; deep Microsoft 365 console integration. Cons: detection-quality claims are vendor-reported; no public pricing to anchor a budget conversation early.
Mimecast — Pros: the only one of the three with security, archiving, continuity, and awareness training natively bundled; flexible MX or API deployment; strong existing SIEM/XDR integration list. Cons: no public pricing; reseller/channel-driven buying process can make apples-to-apples comparison harder.
Abnormal AI — Pros: purpose-built for the BEC and account-takeover gap that gateways miss; fast, non-disruptive API deployment with no MX change; expanding into AI-agent and non-human identity governance. Cons: no gateway mode, so it can’t fully replace a SEG for organizations that specifically need MX-level control; benchmark claims are self-reported; no public pricing.
Who’s a Good Fit For Each
Choose Proofpoint if you want one vendor and one console covering the broadest set of inbound and identity-related email threats, especially if your SOC already leans on Proofpoint elsewhere in its stack. Choose Mimecast if archiving, business continuity, and security-awareness training are procurement requirements alongside the gateway itself, not separate line items you want to source elsewhere. Choose Abnormal AI if you already have a SEG you’re not ready to rip out (or one bundled into Microsoft 365) and want a fast, API-only layer specifically aimed at the BEC and account-takeover attacks that keep getting through.
Who Should Look Elsewhere
Very small organizations that haven’t outgrown Microsoft 365’s built-in Exchange Online Protection and basic staff training probably don’t need any of these three yet — see our SMB-focused guide linked above. And if your primary need is MX-level control with zero reliance on API permissions into your mail platform, Abnormal’s API-only model is a mismatch; Proofpoint or Mimecast’s traditional gateway deployment is the better starting point.
Bottom Line
Gateway filtering and behavioral AI aren’t really competing philosophies anymore so much as complementary layers — the practical question in 2026 is whether you want one vendor to do both (Proofpoint or Mimecast, each now AI-augmented) or two vendors doing one job each (a traditional SEG plus Abnormal AI as a dedicated behavioral layer on top). Either structure is defensible; what matters is testing detection quality against your own phishing and BEC patterns during a proof-of-concept, since the headline performance claims from all three vendors are self-reported.
FAQ
Is Abnormal Security the same company as Abnormal AI? Yes. Abnormal Security rebranded to Abnormal AI in April 2025, per the company’s own press release, while continuing the same email and identity security product line.
Can I run Abnormal AI alongside Proofpoint or Mimecast? Yes — that’s the typical deployment pattern. Abnormal connects via API without touching MX records, so it’s designed to run as an additional layer on top of an existing gateway rather than replace it outright, though some organizations do use it to fully displace a SEG.
Why don’t any of these vendors publish pricing? Enterprise email security is typically sold through direct or channel sales, scaled to mailbox count and feature tier, which makes a simple published rate card uncommon compared with self-serve SaaS products.
What is business email compromise (BEC), and why does it matter for this comparison? BEC attacks impersonate an executive, vendor, or partner to trick an employee into wiring money or sharing credentials — typically without any malware or malicious link, which is exactly why signature- and reputation-based gateway filtering alone tends to miss them, and why behavioral/identity-based detection exists as a category.
Durable, replicated, retained by time/size policy — not deleted on read
High-throughput event streaming, long retention, replay
RabbitMQ
Traditional broker: exchanges route messages into queues
Messages typically removed once acknowledged; quorum queues replicate for safety
Flexible routing, task queues, request/reply, lower-latency work distribution
NATS (Core + JetStream)
Lightweight subject-based pub/sub; JetStream adds a persistence layer on the same server
Core NATS is fire-and-forget (no persistence); JetStream adds storage and replay
Simplicity, very low latency, small footprint, microservices and edge/IoT
Short Verdict
These three solve overlapping but genuinely different problems, and the “which is fastest” framing misses the point. Kafka is a replicated, append-only log built for high-volume event streams that need to be replayed, re-processed, or fed to multiple independent consumers over long retention windows. RabbitMQ is a traditional message broker built around flexible routing (exchanges, bindings, topic patterns) and is still the most ergonomic choice for classic task-queue and request/reply workloads. NATS is the simplicity-and-speed option: a single small binary, sub-millisecond latency for core pub/sub, with JetStream bolted on when you need persistence without adopting Kafka’s operational weight. Pick based on your delivery and retention model first, raw throughput second.
How Each One Actually Works
Kafka organizes data into topics, which are split into partitions spread across brokers in a cluster. Each event is appended to one partition; events sharing a key always land in the same partition, and a consumer reading a given partition sees its events in the exact order they were written. Producers and consumers are decoupled — producers never wait on consumers — and topics can be replicated across brokers (a common production replication factor is 3) so a broker failure doesn’t lose data. Critically, Kafka does not delete messages when they’re read: retention is a time or size policy per topic, and Kafka’s own documentation notes that read/write performance is “effectively constant with respect to data size,” which is what makes long retention and replay practical rather than just theoretically possible.
RabbitMQ is architecturally a classic broker: publishers send messages to an exchange, which routes them into one or more queues according to bindings (direct, topic-pattern, or fanout routing). Consumers then pull from queues and acknowledge messages — manual acknowledgment is the recommended default, since automatic acks offer the weakest delivery guarantees. For durability, RabbitMQ 4.x uses quorum queues, which are replicated and built for data safety (classic queues lost their replication option in 4.x). A per-queue delivery limit can also protect against poison messages that repeatedly fail processing. This exchange/binding model is what gives RabbitMQ its routing flexibility: the same message can fan out to multiple queues, or be routed selectively by topic, without the consumer needing to know about partitioning.
NATS takes the opposite design bet: minimize moving parts. The core server routes messages between publishers and subscribers by subject — a named channel — with no broker-side persistence by default. NATS’s own documentation describes the project as optimized for “a small single binary” with “low latency at high message rates,” and states vendor-claimed figures of millions of messages per second, sub-millisecond latency, and a typical in-memory footprint of around 15MB for the server itself. JetStream is NATS’s persistence layer, running inside the same nats-server process alongside clustering and leaf-node support; it adds storage and replay on top of core NATS’s fire-and-forget pub/sub, closing much of the durability gap with Kafka and RabbitMQ without requiring a separate system.
Comparison: Delivery, Ordering, and Operations
Dimension
Kafka
RabbitMQ
NATS (Core / JetStream)
Ordering guarantee
Strict order within a partition
Per-queue order under normal delivery; redelivery can disturb order
Per-subject order within JetStream streams
Replay / reprocessing
Native — consumers track their own offset into the retained log
Not a design goal — messages are generally removed once consumed
JetStream supports replay from stored streams; Core NATS does not
Routing flexibility
Topic/partition keying; routing logic lives in producers/consumers
Rich server-side routing via exchanges and bindings
Subject hierarchies with wildcard subscriptions
Operational footprint
Heavier — ZooKeeper-free (KRaft) still means a multi-broker cluster to run and tune
Moderate — well-documented clustering, long operational history
Light — single binary, documented as easy to run at small and large scale alike
Multiple independent consumer groups
Strong fit — many consumer groups can replay the same retained log independently
Possible via fanout exchanges, but each queue still competes for the same messages unless explicitly fanned out
JetStream supports multiple durable consumers per stream
Trade-offs
Kafka pros: best-in-class for event streaming, audit logs, and feeding multiple downstream systems (analytics, search indexing, caches) from one durable source of truth; near-linear scaling by adding partitions and brokers.
Kafka cons: heaviest operationally of the three; overkill for simple task queues or low-volume request/reply; schema and topic design mistakes are expensive to undo once data and consumers depend on them.
RabbitMQ pros: mature, flexible routing without custom logic; strong fit for background job queues, RPC-style request/reply, and workloads where you want the broker to make per-message delivery decisions.
RabbitMQ cons: not built for long-term retention or replay; classic queues lost replication in 4.x, pushing anyone needing HA toward quorum queues, which have their own throughput characteristics to test for your workload.
NATS pros: lowest operational overhead, lowest latency for core pub/sub, genuinely simple mental model; JetStream narrows the durability gap when needed.
NATS cons: Core NATS alone has no persistence — a message with no active subscriber is simply gone; JetStream is newer and less battle-tested at extreme scale than Kafka’s log model; the broader tooling and connector ecosystem is smaller than Kafka’s.
When to Use Which
Reach for Kafka when you need an auditable, replayable stream of events consumed by multiple independent systems over days, weeks, or longer — change-data-capture pipelines, clickstream/analytics ingestion, or any architecture where “what happened, in order, and can we replay it” matters more than shaving off milliseconds of latency. Reach for RabbitMQ when the problem is really a task queue or RPC pattern: background jobs, work distribution among competing workers, or routing messages to different consumers based on content — especially if your team already knows AMQP and wants the broker to own routing logic. Reach for NATS when operational simplicity and raw latency matter most — microservice-to-microservice messaging, IoT/edge fan-in, or any system where running and tuning a JVM-based cluster is disproportionate to the actual message volume; add JetStream only once you’ve confirmed you need durability, not by default.
Bottom Line
Don’t start this decision by benchmarking throughput. Start by asking whether you need replay of historical events (Kafka), flexible server-side routing for task distribution (RabbitMQ), or the smallest possible operational footprint with optional persistence (NATS/JetStream). All three remain actively developed, all three can be made durable and fast enough for the vast majority of real workloads, and all three are frequently combined in the same organization for different services rather than chosen as a single company-wide standard.
FAQ
Can Kafka be used as a simple task queue? Yes, but it’s generally not the most efficient fit — Kafka’s consumer-group model assumes you want partitioned, ordered, replayable delivery, which adds complexity a simple work queue doesn’t need. RabbitMQ or NATS typically fit that shape more directly.
Is NATS JetStream a Kafka replacement? It covers much of the same ground — persistence, replay, multiple durable consumers — inside a lighter-weight server, and is a reasonable alternative for many workloads. Teams with very large retained-log and consumer-group requirements still tend to default to Kafka, partly for its maturity and ecosystem.
Does RabbitMQ guarantee message order? Within a single queue under normal conditions, yes. Redelivery after a failed acknowledgment can change that order (RabbitMQ flags redelivered messages), so strict ordering under failure scenarios needs explicit design, not an assumption.
Do I need ZooKeeper to run Kafka? Not anymore for new clusters — KRaft mode removed the ZooKeeper dependency, but running and tuning a multi-broker Kafka cluster is still a heavier operational commitment than RabbitMQ or NATS.
Most “AI code security” content either repeats vague warnings about hallucinated code or pitches a scanning tool. This piece does neither: it’s a walkthrough of what OWASP itself has actually published on securing AI-generated and AI-assisted code — specifically the OWASP Top 10 for LLM Applications and, more directly, the OWASP AI Security Verification Standard’s (AISVS) dedicated appendix on AI-assisted secure coding. If you want the broader technical-debt angle or a tool-by-tool comparison, see our pieces on AI-generated code’s hidden technical debt, static analysis tools (SonarQube, Semgrep, CodeQL), and our agentic-security checklist — this one stays specifically inside OWASP’s own published framework.
At a Glance
OWASP Source
What It Covers
Relevant to AI-Generated Code?
OWASP Top 10 for LLM Applications (2025)
Ten risk categories for applications built on or with LLMs (prompt injection, output handling, supply chain, etc.)
Indirectly — these are the risk mechanisms that also show up when an LLM writes code
OWASP AISVS (AI Security Verification Standard) v1.0, Appendix C
A dedicated appendix titled “AI-Assisted Secure Coding,” with 14 control families and three verification levels
Directly — this is OWASP’s explicit guidance for teams using AI to generate, refactor, or review code
Short Verdict
OWASP’s most direct, named guidance on AI-generated code lives in AISVS Appendix C, “AI-Assisted Secure Coding” — not in the better-known Top 10 for LLM Applications, which is about risks in LLM-powered applications generally. Appendix C’s core message is procedural, not technical: AI coding tools must be forced into your existing secure development lifecycle (SSDLC) rather than allowed to bypass it, humans (never the AI itself) must remain the accountable reviewer, and every AI-generated artifact — code, infrastructure files, pipeline configs — needs the same or stricter scanning and sign-off as human-written equivalents.
What OWASP’s Guidance Actually Says
The Top 10 for LLM Applications (2025) catalogs ten risk categories relevant to any system built around a large language model: LLM01 Prompt Injection, LLM02 Sensitive Information Disclosure, LLM03 Supply Chain, LLM04 Data and Model Poisoning, LLM05 Improper Output Handling, LLM06 Excessive Agency, LLM07 System Prompt Leakage, LLM08 Vector and Embedding Weaknesses, LLM09 Misinformation, and LLM10 Unbounded Consumption. Several of these map directly onto AI coding tools: a prompt-injected code comment or PR description (LLM01), an agent given more repository permissions than it needs (LLM06), or a coding assistant quietly leaking a secret it was shown in context (LLM02).
AISVS Appendix C takes those general risks and translates them into specific, testable requirements for code-generation workflows. Its core premise: AI coding tools must fit into the existing SSDLC without weakening its security gates, and organizations should document which adversarial-AI threats each guardrail addresses before adopting a tool. OWASP names concrete risk scenarios the appendix is designed to address, including prompt injection delivered through PR descriptions, issues, commit messages, or MCP tool outputs; sensitive data leaking into prompts; AI-generated dependencies that are typosquatted or unresolvable; autonomous agents approving their own work; and bulk, AI-driven fork-and-PR campaigns from low-reputation accounts.
The 14 Control Families in AISVS Appendix C
Control Family
Key Requirement
AC.1 Workflow
Document when AI may generate/refactor/review code; keep mandatory security gates regardless of AI involvement
AC.2 Tool Qualification
Threat-model every AI tool and run adversarial robustness (prompt-injection/jailbreak) tests before onboarding
AC.3 Prompt and Context Management
Prohibit secrets in prompts; treat external context as untrusted; enforce an instruction hierarchy
AC.4 Validating AI Code
Require review by a human who is not the requester; never count the AI as the reviewer; run SAST/DAST/SCA on AI PRs
AC.5 Traceability
Log prompt-response pairs with correlation IDs; store AI event logs in tamper-evident storage
AC.6 Feedback and Red-Teaming
Let developers flag insecure suggestions; run scheduled red-team exercises against the AI tooling itself
AC.7 Infrastructure and Pipeline Artifacts
Label AI-generated IaC/CI/CD files; require human approval before they run outside a sandbox
AC.8 Agent Change Control
Agents must not approve, merge, sign, or deploy their own output — enforced in tooling, not just policy
AC.9–AC.10 Origin Validation
Attach signed provenance (SLSA/in-toto attestations, AI BOM entries) to AI-generated artifacts
AC.11 AI Review Bot Hardening
Treat PR content as untrusted; sign/hash-pin bot system prompts; run bots in isolated, least-privilege sandboxes
AC.12 Pipeline Hardening for AI
Never run untrusted fork code in privileged workflow contexts; use ephemeral runners and two-stage workflows
AC.13 Inbound Adversarial Detection
Flag bulk PR creation from new accounts and coordinated fork waves; map detections to MITRE ATT&CK/ATLAS
AC.14 Containment and Remediation
Maintain an incident playbook for AI-in-pipeline compromise; test time-to-revoke AI agent credentials
OWASP assigns each requirement a verification level — Level 1 (baseline), Level 2, or Level 3 (advanced) — modeled on the existing OWASP ASVS (Application Security Verification Standard). Level 1 covers essentials like an AI usage policy, prompt redaction, untrusted-input screening, and separation of duties between the AI and its human reviewer. Level 3 covers more mature practices like measuring AI-produced code against a human-only baseline, tamper-evident logging, and continuous regression testing of the AI tooling itself.
Practical Mitigations: Adapting Code Review and Security Practice
Keep humans as the accountable reviewer. AISVS AC.4 is explicit that the reviewer must not be the AI agent itself, and should not be the person who requested the generation — this closes the “autonomous agent approves its own work” gap named under AC.8.
Run the same scanners on AI output as on human code — or stricter ones. AC.4 calls for SAST, DAST, IAST, secret scanning, IaC scanning, and SCA on AI-generated PRs, with merges blocked on critical findings absent a written human exception, and stricter review reserved for security-critical files (auth, crypto, IAM, CI/CD).
Treat anything an AI tool reads from a repository as untrusted input. AC.3 and AC.11 both call for screening external context — PR descriptions, issues, comments, web content, MCP tool outputs — for injection attempts before it reaches a model or an AI review bot.
Harden the pipeline itself, not just the code. AC.12 specifically warns against running untrusted fork code in privileged GitHub Actions contexts like pull_request_target or workflow_run, and calls for ephemeral runners and two-stage workflows that pass only validated artifacts forward.
Attach provenance to AI-generated artifacts. AC.9–AC.10 call for signed attestations (SLSA, in-toto) and AI bill-of-materials entries recording model identity, tool identity, and prompt hash — so a compromised or hallucinated artifact can be traced back to its origin.
Where OWASP’s Guidance Is Still Maturing
OWASP is explicit that some of this ground is still shifting. AC.13 notes that “where automated detection of LLM-generated code is immature, use compensating controls such as mandatory human review and sandboxed execution” — in other words, OWASP itself does not claim there’s a reliable automated way to detect whether code came from an AI versus a human, and recommends process controls instead of a detection tool. AISVS is versioned at 1.0, positioned as the latest stable release and modeled on the long-established OWASP ASVS, but it is a newer, community-driven standard rather than a decades-proven one — teams should expect it to evolve and should check for newer versions before treating any specific control as final.
Who This Guidance Is For
This is directly useful for security and platform engineering teams standing up policy around AI coding assistants, AI PR-review bots, and autonomous coding agents — especially teams that need a structured, levelled checklist (Level 1/2/3) to decide how far to go rather than starting from a blank page.
This is less directly useful for teams looking for a specific tool recommendation (OWASP’s guidance is tool-agnostic and procedural) or for a ranked list of today’s most severe AI-code vulnerabilities (that’s closer to what the Top 10 for LLM Applications covers at the application level, not the coding-workflow level Appendix C addresses).
Bottom Line
OWASP’s position, stated plainly across AISVS Appendix C, is that AI-generated code is not inherently more or less dangerous than human-written code — it’s dangerous when it’s allowed to skip the controls human-written code already goes through. The fix isn’t a new scanning product; it’s making sure your existing SSDLC gates (review, SAST/DAST/SCA, least-privilege CI, signed provenance) apply with equal or greater force to anything an AI tool touches, and that no AI agent is ever its own approver. Teams adopting AI coding agents in 2026 should treat AISVS Appendix C as a checklist to audit against, not a one-time read.
FAQ
Does OWASP have guidance specifically about AI-generated code, or only about LLM applications in general? Both exist, but they’re different documents. The OWASP Top 10 for LLM Applications (2025) covers risks in applications built on LLMs generally. OWASP’s AI Security Verification Standard (AISVS) v1.0 includes a dedicated appendix, “Appendix C: AI-Assisted Secure Coding,” that speaks directly to AI-generated/AI-assisted code in software development workflows.
Can an AI code review bot count as the required human reviewer under OWASP’s guidance? No. AISVS AC.4 explicitly requires review by a qualified human who is not the original requester, and states the AI agent must never be counted as that reviewer.
What does OWASP say about letting AI agents merge or deploy their own code? AISVS AC.8 (“Agent Change Control”) states that agents must not approve, merge, sign, or deploy their own output, and that this must be enforced in source control, CI, and the artifact registry — not just written as policy.
Is AISVS a finished, stable standard? Version 1.0 is described by OWASP as the latest stable release, modeled on the established OWASP ASVS. It is newer and less battle-tested than ASVS itself, and OWASP structures it with three verification levels so organizations can adopt baseline controls first and add more advanced ones over time.
Screenshot tools split cleanly along platform and price lines: ShareX is free, open-source, and Windows-only; CleanShot X is a polished, paid, Mac-only tool; and Snagit is the cross-platform subscription option built for teams and documentation work. We checked each vendor’s current site and pricing page to confirm cost, platform support, and feature sets before comparing them.
At a Glance
Tool
Price
Platform
Best For
ShareX
Free and open source, no cost ever
Windows only
Windows power users who want maximum capture/upload features for $0
Mac users who want a polished, native capture and annotation tool
Snagit
Individual: $39/user/year, billed yearly
Windows and macOS
Teams and documentation writers needing cross-platform step-by-step guides
Short Verdict
If you’re on Windows and don’t want to spend a dollar, ShareX is genuinely hard to beat — it’s free, open source, and covers screenshot capture, GIF/video recording, annotation, OCR, and uploads to more destinations than either paid competitor lists. If you’re on a Mac and want something that feels native and polished without a subscription commitment, CleanShot X’s $35 one-time Basic plan is the better fit, with Pro’s $10/user/month unlocking unlimited cloud storage and team features. If your team spans both Windows and Mac and needs consistent step-by-step documentation tools (and is fine paying an annual subscription), Snagit at $39/user/year is the only one of the three that runs natively on both platforms.
What Each Tool Is
ShareX is a free, open-source Windows application. Per its own site, it supports full-screen, region, active-window, monitor, and scrolling-page capture, plus auto capture, along with video and GIF screen recording. Its image editor includes shapes, arrows, text, numbered steps, highlighting, blur, pixelation, magnification, and cropping. It also bundles a color picker, OCR text recognition, image/video converters, and a large list of upload destinations (including self-hosted options like Amazon S3, Google Cloud Storage, and Cloudflare R2), plus URL shortening and QR code generation — all at no cost.
CleanShot X is a Mac-only app (requiring macOS 13.0 or newer, per its own FAQ, which also confirms there are no plans to release a Windows version). It’s sold two ways: a one-time Basic purchase ($35, license never expires, includes one year of updates with an optional $19/year renewal after that) or a Pro subscription ($10/user/month billed annually) that keeps the app always up to date and adds unlimited cloud storage, custom domain/branding, team access management, SSO, and SCIM. Both tiers include 4K capture quality.
Snagit, from TechSmith, runs on both macOS 14+ and Windows 10/11, per its own system requirements. Per TechSmith’s product and store pages, it’s sold as an annual subscription at $39/user/year (or bundled into pricier Camtasia plans), and includes screen recording (with microphone, system audio, and webcam capture, clip trimming, and noise reduction), Scrolling Capture for long pages/windows, Step Capture for auto-generated click-by-click guides, annotation (arrows, callouts, text, and team-brand “themes”), Smart Redact for hiding sensitive information, and Screencast hosting for up to 25 videos.
Pricing Breakdown
Plan
ShareX
CleanShot X
Snagit
Entry
Free — full feature set, no paid tier exists
Basic — $35 one-time; perpetual license, 1 year of updates, 1 GB Cloud storage
Teams/Business and Camtasia bundles — pricing not published on the general product page; requires checking the dedicated Teams & Business store page
Renewal/add-ons
N/A — always free
Basic license: optional $19/year renewal for continued updates after year one
Volume licensing discounts starting at 5+ seats, per TechSmith’s product page
ShareX: Pros and Cons
Pros: Completely free and open source with no feature gating; very large feature set including OCR, GIF/video recording, and dozens of upload destinations; actively maintained with portable and Microsoft Store/Steam distribution options.
Cons: Windows only — no Mac version exists; interface is more utilitarian/configuration-heavy than CleanShot X’s or Snagit’s polished UI; no official vendor support channel the way paid tools offer.
CleanShot X: Pros and Cons
Pros: One-time Basic purchase option avoids a forced subscription; clean, native-feeling Mac UI; Pro tier’s unlimited cloud storage and team/SSO/SCIM features are strong for small design or support teams.
Cons: Mac only, with no Windows version planned per its own FAQ; Basic plan’s Cloud storage is capped at just 1 GB; advanced team/security features require the subscription Pro tier, not the one-time purchase.
Snagit: Pros and Cons
Pros: Only one of the three that runs natively on both Windows and macOS; Step Capture and Smart Redact are purpose-built for documentation and training content; screen recording with webcam/audio mixing is more built-out than CleanShot X’s.
Cons: Subscription-only at $39/user/year with no one-time purchase option found on TechSmith’s current pricing pages; Teams/Business pricing isn’t published and requires visiting a separate store page; costs more per year than ShareX’s $0 or CleanShot X’s one-time Basic option.
Who Each Tool Is a Good Fit For
Choose ShareX if you’re on Windows, comfortable with a more configuration-driven interface, and want the deepest feature set for zero cost.
Choose CleanShot X if you’re on a Mac and want a native, polished tool — the one-time Basic purchase suits individuals, while Pro’s team features suit small Mac-based design or support teams.
Choose Snagit if your team is mixed Windows/Mac, or you specifically need step-by-step documentation generation (Step Capture) or sensitive-data redaction (Smart Redact) as part of your workflow.
Who Should Look Elsewhere
Mac users should skip ShareX entirely — it has no Mac build. Windows-only teams that don’t need cross-platform parity may find Snagit’s $39/year subscription an unnecessary cost compared to ShareX’s free feature set, unless Step Capture or Smart Redact specifically matter to them. And anyone needing enterprise-grade team deployment pricing for Snagit will need to visit TechSmith’s separate Teams & Business store page, since general pricing for that tier isn’t published alongside the Individual price.
Bottom Line
Platform support is the real deciding factor here before price even enters the conversation: ShareX only runs on Windows, CleanShot X only runs on Mac, and Snagit is the sole cross-platform option of the three. Within that constraint, ShareX is the easy choice for cost-conscious Windows users, CleanShot X is the cleanest experience for Mac users willing to pay a modest one-time fee, and Snagit earns its subscription price for teams that specifically need documentation-focused features like Step Capture across both operating systems.
FAQ
Is ShareX really completely free? Yes — per its own site, ShareX is free and open source with no advertisements and no paid tier of any kind.
Does CleanShot X have a Windows version? No. CleanShot X’s own FAQ states there is no Windows version and no plans to release one; it requires macOS 13.0 or newer.
Can I buy Snagit outright instead of subscribing? Based on TechSmith’s current store and product pages, Snagit Individual is sold only as a $39/user/year subscription — no one-time perpetual license option is listed on those pages.
Which tool supports screen recording, not just screenshots? All three do. ShareX includes video and GIF recording for free; CleanShot X includes 4K capture on both its Basic and Pro tiers; Snagit includes screen recording with microphone, system audio, and webcam capture plus clip trimming and noise reduction.
Authy, Google Authenticator, and Microsoft Authenticator all do the same basic job: generate a six-digit, time-based one-time code (TOTP, per the open RFC 6238 standard) that proves you hold a second factor beyond your password. None of them charge consumers a cent. The real differences are in how each one backs up and syncs your codes across devices, what that convenience costs you in attack surface, and what happens the day you lose your phone. In 2026 the more interesting question for most people isn’t “which app” — it’s whether an authenticator app is still the right tool at all, versus a passkey or a hardware security key.
At a Glance
App
Maker
Cloud backup/sync
Platforms
Price
Best for
Authy
Twilio
Yes — multi-device cloud sync (mobile only)
Android, iOS (desktop app discontinued)
Free
People who want codes on more than one phone at once
Google Authenticator
Google
Optional — syncs via Google Account sign-in
Android, iOS
Free
Simplicity, and anyone already living in a Google Account
Microsoft Authenticator
Microsoft
Optional — backup via Microsoft personal account (Android/iOS, not cross-compatible)
Android, iOS
Free
Microsoft/Entra-heavy households and workplaces
Short Verdict
For most people, Google Authenticator is the least fussy choice if you’re already signed into a Google Account everywhere: turn on sync once and you’re protected against losing your phone. Microsoft Authenticator makes sense if your digital life already centers on a Microsoft personal account or your employer uses Microsoft Entra — but know that work/school accounts and passwordless credentials are explicitly excluded from its backup. Authy still has the most mature multi-device story (several phones showing the same codes at once), but it lost its desktop apps in 2024 and carries the reputational baggage of a 2024 incident involving an unsecured API. None of the three is phishing-resistant: for your highest-value accounts, pair any of them with a passkey or a hardware security key rather than relying on a six-digit code alone.
What They Are and How They Differ Technically
All three apps implement the same TOTP algorithm, so a QR code from, say, your bank will work identically in any of them — the apps aren’t tied to specific services. The differences that actually matter sit in backup and recovery architecture:
Authy markets itself around “secure cloud backup, multi-device support” and is free with no paid tier, according to Twilio’s own Authy site. Multi-device sync lets the same account show live codes on more than one phone simultaneously — historically Authy’s signature feature. The desktop apps for Windows, macOS, and Linux were end-of-lifed starting in 2024 and fully discontinued; Twilio has confirmed mobile is now Authy’s only supported platform.
Google Authenticator lets you save codes to your Google Account; once you sign in, codes sync automatically to any new device, and Google states the data is encrypted both in transit and at rest. Skip the Google Account sign-in and your codes never leave that one device — you’d need to manually scan an export QR code on the old phone to move them, which only works if the old device is reachable and running a current app version.
Microsoft Authenticator backs up codes for personal Microsoft accounts and compatible third-party accounts (its own documentation names LinkedIn and Facebook as examples) via a Cloud Backup toggle on Android. Critically, Microsoft’s own support documentation states that work or school account credentials are not backed up — only the account name is saved, and you must re-register that account on a new device — and that passwordless sign-in credentials for personal accounts aren’t backed up either. Backups are also device-type locked: an iOS backup can’t be restored on Android, or vice versa.
A Platform Shift Worth Knowing About
Microsoft’s own support page states that, starting in January 2027, Android users will no longer use a Microsoft personal account to enable Authenticator backup — they’ll be moved to Google One backup instead. It’s a small but telling sign of how much of the mobile backup plumbing underneath these “competing” apps already runs through the same infrastructure, even when the brand on the app icon says otherwise.
Security Model: Convenience vs. Attack Surface
Factor
Authy
Google Authenticator
Microsoft Authenticator
Codes recoverable if phone is lost
Yes, via multi-device/cloud backup
Yes, if signed into Google Account
Yes for personal accounts with Cloud Backup on; no for work/school accounts
Account takeover risk if parent account is compromised
Twilio/Authy account becomes a target
Google Account becomes a target (also protected by the account’s own 2FA)
Microsoft personal account becomes a target
Known incident
2024: an unsecured Authy API let attackers enumerate phone numbers tied to accounts, exposing ~33 million phone numbers (not TOTP seeds themselves); Twilio patched the API and shipped an updated app
None publicly reported of this kind
None publicly reported of this kind
Phishing resistance
No — codes can be relayed by a real-time phishing page
No
No
That Authy incident is worth understanding precisely rather than as a vague rumor: the exposed data was phone numbers associated with accounts, pulled through an API endpoint that wasn’t properly locked down — it was not a reported compromise of users’ actual TOTP seeds or generated codes. Twilio fixed the API and pushed a security update. The lesson generalizes beyond Authy, though: any time a 2FA app adds account-linked cloud infrastructure for convenience, that infrastructure itself becomes something worth securing and something that can fail. A code generator with zero network connectivity has a smaller attack surface, full stop — it just also has a worse “I lost my phone” story.
Pros and Cons
Authy — Pros: true multi-device live sync (multiple phones can show the same codes at once); free; simple setup. Cons: desktop app discontinued, mobile-only now; 2024 phone-number exposure incident dents trust even though TOTP seeds weren’t the data exposed.
Google Authenticator — Pros: dead simple; backup is opt-in but seamless once enabled; works offline with zero setup if you skip sync entirely. Cons: no simultaneous multi-device display like Authy; cross-device moves without an account require a manual QR export from the old phone.
Microsoft Authenticator — Pros: tight integration if you’re already in the Microsoft/Entra ecosystem; supports passwordless sign-in for personal accounts. Cons: work/school accounts explicitly excluded from backup — a real trap for anyone who assumes “cloud backup” means everything is covered; backups don’t move between iOS and Android.
Who Should Pick Which
Pick Google Authenticator if you want the least to think about and you’re already a heavy Google Account user. Pick Authy if you specifically want the same live codes available on, say, both a phone and a tablet at once. Pick Microsoft Authenticator if your employer already mandates it for Entra sign-in, or your personal accounts are Microsoft-centric — but set a calendar reminder to manually re-register any work/school account whenever you change phones, since cloud backup won’t do it for you.
When a Hardware Key or Passkey Is the Better Call
A TOTP code from any of these three apps can still be captured and relayed in real time by a convincing phishing page — the code itself doesn’t know or care which site it was typed into. A FIDO2/WebAuthn hardware security key or a passkey is cryptographically bound to the website’s actual domain, so a lookalike phishing site simply can’t complete the handshake, no matter how good the forgery looks. That makes hardware keys and passkeys phishing-resistant in a way no app-generated code can be. For your email account, your primary cloud identity (Google/Microsoft Account), financial accounts, and anything tied to administrator or domain-level access, treat an authenticator app as the minimum bar, not the ceiling — add a passkey or hardware key wherever the service supports one, especially if you’re a specific target (an executive, journalist, activist, or IT administrator).
Bottom Line
There’s no wrong free choice among these three for everyday accounts — the real risk with authenticator apps isn’t picking the wrong brand, it’s losing your phone with no backup method enabled, or assuming a “cloud backup” toggle covers account types it explicitly doesn’t (Microsoft’s work/school exclusion being the sharpest example). Enable sync or backup on day one, understand exactly what it does and doesn’t cover, and reserve hardware keys or passkeys for the handful of accounts where a phished code would actually hurt.
FAQ
Is Authy still safe to use after the 2024 incident? The exposed data was phone numbers linked to accounts, not the TOTP codes or secret seeds themselves, and Twilio patched the underlying API. Authy remains a functioning, free, actively maintained app — but the incident is a legitimate reason some users moved to Google or Microsoft’s apps instead.
Can I use Google Authenticator without a Google Account? Yes. Codes simply stay local to that one device, with no cloud backup — if you lose the phone without having exported your codes first, you’ll need each service’s account-recovery process to regain access.
Will Microsoft Authenticator back up my work accounts? No. Microsoft’s own documentation is explicit that only personal Microsoft accounts and select third-party consumer accounts are backed up; for a work or school account, only the account name is saved, and you must sign back in and re-register it on a new device.
Do any of these apps cost money? No — Authy, Google Authenticator, and Microsoft Authenticator are all free for personal use, with no paid consumer tier.
Should I switch from an authenticator app to a passkey? Where a service offers passkeys, they’re generally the better choice because they resist phishing in a way a six-digit code cannot. Many people end up running both for a while: passkeys on services that support them, an authenticator app everywhere else.
Canonical decomposition, then canonical composition — combines base letters with marks into single codepoints where possible
Default for storage, URLs, and most text on the web
NFD (Normalization Form D)
Canonical decomposition only — splits precomposed characters into base + combining marks
Text analysis, diacritic-insensitive search, some macOS filesystem APIs
NFKC (Normalization Form KC)
Compatibility decomposition, then canonical composition — also folds stylistic/compatibility variants (e.g. ligatures, roman numerals) into plain equivalents
Search, security checks on identifiers, loose matching
NFKD (Normalization Form KD)
Compatibility decomposition only, no recomposition
Aggressive text normalization before further processing
Short Verdict
Unicode allows more than one sequence of codepoints to render as the same visible string. “café” typed on one system can be a single precomposed character (U+00E9, LATIN SMALL LETTER E WITH ACUTE) and on another a base letter plus a separate combining accent (U+0065 U+0301). Both look identical. Neither is “more correct.” But a naive == comparison, a database unique index, or a cache key built from the raw string will treat them as different values. The fix, per the Unicode Standard itself, is to normalize both sides to the same form — usually NFC — before comparing, storing, hashing, or indexing. This is not an edge case for CJK or emoji only; it hits any text with accents, umlauts, or combining marks, which means most non-English (and plenty of English) text that passes through more than one system.
What Unicode Normalization Actually Is
Unicode Standard Annex #15 (UAX #15), the Unicode Normalization Forms specification, defines the problem as canonical equivalence: “a fundamental equivalency between characters or sequences of characters” that represent the same abstract character and are supposed to look and behave identically when rendered correctly. A weaker relationship, compatibility equivalence, covers characters that are related in meaning but may look or behave differently — the roman numeral “Ⅰ” (U+2160) and the letter “I” (U+0049), for instance, which share meaning but not necessarily rendering.
Normalization resolves this by giving every equivalent sequence a single, well-defined representative form. UAX #15 defines four:
NFD — Canonical Decomposition: break every precomposed character into its base character plus combining marks.
NFC — Canonical Decomposition followed by Canonical Composition: decompose, then recombine every base-plus-mark sequence back into a single precomposed character wherever one exists.
NFKD — Compatibility Decomposition: like NFD, but also expands compatibility characters (ligatures, fullwidth forms, superscripts, roman numerals) into their plain equivalents.
NFKC — Compatibility Decomposition followed by Canonical Composition: NFKC and NFC differ only in that decomposition step.
The mechanics behind composition and decomposition matter for correctness, not just trivia. Every character carries a Canonical_Combining_Class; characters with class zero (“starters”) anchor a run, and non-zero-class combining marks following a starter get sorted by that class under the Canonical Ordering Algorithm — so the same accent marks typed in a different order still normalize identically. The Canonical Composition Algorithm then scans left to right and merges any eligible starter+mark pair into its precomposed codepoint, except for a documented set of characters that UAX #15 excludes from composition entirely (so they never get recombined, by design).
Two properties from the spec matter in practice. First, normalization is stable across Unicode versions: a string normalized under one version of Unicode stays normalized under every later version, which is why it’s safe to normalize once and store the result long-term. Second, and easy to miss, none of the four forms is closed under string concatenation — joining two independently-normalized strings (e.g. gluing a normalized prefix to a normalized suffix at a boundary) can produce a string that is no longer normalized, so systems that build text by concatenation need to re-normalize after assembly, not just at the edges.
Where This Breaks Real Systems
The classic failure mode: a user registers an account with a name typed on a Mac, which may produce decomposed sequences from certain input methods; a second system (a database, a search index, an API from a different vendor) receives the same visual string but precomposed, because its OS or browser normalized on input. "café" == "café" returns false even though a human reading both sees the same word. This shows up as: duplicate user accounts that look identical, failed login/username lookups, broken full-text search, HMAC or hash mismatches on supposedly-identical payloads, and inconsistent sort order. It is especially common at the boundary between macOS (whose HFS+/APFS filesystem APIs have historically normalized filenames toward a decomposed form) and systems on Linux or Windows that leave filenames exactly as given, byte for byte.
NFKC/NFKD introduce a second, security-relevant failure mode in the opposite direction: because they fold visually or semantically similar characters together, they can be used to defeat naive blocklists (a filter that blocks the ASCII word “admin” might not catch a fullwidth or ligature variant until it’s been NFKC-normalized) — but the same folding is exactly why UAX #15 warns compatibility forms “must not be blindly applied to arbitrary text”: they are lossy with respect to formatting and can change meaning (e.g. collapsing a trademark symbol into plain letters) in contexts where that distinction matters, such as user-facing display or legal text.
A Minimal, Correct Example
Python’s standard library implements all four forms via unicodedata.normalize(form, text), with form one of "NFC", "NFD", "NFKC", "NFKD":
import unicodedata
composed = "caf\u00e9" # NFC: single codepoint U+00E9 (é)
decomposed = "cafe\u0301" # NFD: "e" + combining acute U+0301
print(composed == decomposed)
# False -- same visible text, different codepoint sequence
print(unicodedata.normalize("NFC", decomposed) == composed)
# True -- normalize both sides before comparing
print(unicodedata.is_normalized("NFC", composed))
# True -- cheap check before doing the full normalization pass
The Python docs flag the same root issue directly: “Even if two unicode strings are normalized and look the same to a human reader, if one has combining characters and the other doesn’t, they may not compare equal.” The fix is always the same shape — normalize to one form at the boundary (on input, before storage, before comparison) rather than trying to special-case every possible equivalent sequence.
Trade-offs: NFC vs. NFD vs. NFKC/NFKD
NFC pros: most compact representation; what most web content, URLs, and the W3C’s own guidance for HTML/XML use by default; round-trips cleanly through most legacy systems that expect precomposed accented letters.
NFC cons: not every combining sequence has a precomposed codepoint, so some marks never recompose — NFC does not guarantee a mark-free string.
NFD pros: useful when you need to isolate or strip diacritics (e.g. building an accent-insensitive search index by decomposing, then dropping combining-mark codepoints).
NFD cons: larger byte size; many older libraries and protocols assume precomposed input and mishandle bare combining marks.
NFKC/NFKD pros: good for loose matching, search, and some identifier-spoofing defenses, since it collapses compatibility variants that would otherwise bypass exact-match filters.
NFKC/NFKD cons: lossy and one-directional — you cannot recover the original formatting distinctions, so it is unsafe for anything that must preserve exact user input (legal names, file content, cryptographic payloads).
Who Should Use Which Form
Use NFC as the default for anything you store, compare, hash, index, or put in a URL — it’s the form most interoperable systems already expect. Use NFD only when you specifically need to manipulate base characters and marks separately, such as building a diacritic-folding search feature, or when working directly with macOS filesystem APIs that normalize toward it. Use NFKC/NFKD only for non-reversible operations like fuzzy search, spam/abuse filtering, or identifier collision checks — never for data you need to preserve exactly, and never as a silent step before storage, since you’d be discarding information users typed on purpose.
Bottom Line
Most “duplicate account” and “search can’t find text that’s clearly there” bugs involving accented or non-Latin text trace back to one root cause: two systems chose different, equally valid, codepoint sequences for the same visible string, and nobody normalized before comparing. Pick NFC as your storage and comparison default, normalize at every system boundary (not just once at the start), and reach for NFKC/NFKD deliberately and only for lossy, non-reversible matching — never as an invisible default.
FAQ
Is NFC “more correct” than NFD? No. Both represent the exact same abstract text under Unicode’s canonical equivalence; NFC is simply the more common interoperability default because it’s more compact and matches what most legacy encodings and the web already expect.
Does normalizing fix emoji or CJK comparison bugs too? It fixes any text built from combining sequences or compatibility variants that have multiple valid representations — this includes many CJK compatibility ideographs and some emoji ZWJ sequences, though the exact equivalence rules differ by category and UAX #15 should be checked for edge cases.
Can I normalize once and never worry about it again? Normalization is stable across Unicode versions, so a string normalized today stays normalized later — but concatenating two normalized strings is not guaranteed to produce a normalized result, so re-normalize after any operation that joins or edits text, not just at ingestion.
Is NFKC safe for security filtering (e.g. blocking reserved usernames)? It helps catch some lookalike-character bypasses, but it is lossy by design and should be paired with other checks (such as Unicode confusables detection), not treated as a complete defense on its own.
Most coverage of Google’s AI infrastructure focuses on the TPU chip itself — Trillium, Ironwood, their FLOPS and memory bandwidth. But a chip is only as fast as the network connecting it to thousands of others. Google’s answer at the data-center scale is Jupiter, a network fabric built around optical circuit switching (OCS) that Google has been evolving in production since 2015, and which Google’s own TPU documentation says is what lets individual TPU superpods be wired together into clusters of hundreds of thousands of chips. This piece is about that fabric, not the chips themselves.
AT A GLANCE
Fact
Detail
What it is
Google’s data-center network fabric, built on optical circuit switches (OCS) and centralized software-defined networking (SDN)
Who makes it
Google (first deployed 2015; evolution published at SIGCOMM 2022 as “Jupiter Evolving”)
Primary use case
Uniform, high-bandwidth, low-latency connectivity across tens of thousands of servers and accelerators in a Google data center; at the TPU level, Google states it is what links multiple TPU “superpods” into much larger training/inference clusters
Where it fits in the stack
Sits above the TPU-specific interconnect (ICI and in-pod OCS) — Jupiter/the Data-Center Network (DCN) is the layer that connects whole superpods to each other and to the rest of Google’s infrastructure
Scale (per Google’s own published figures)
2015 deployment: 30,000+ servers, 1+ Pb/s aggregate bandwidth. By 2022: 6+ Pb/s of data-center bandwidth, with Google reporting 5x higher speed/capacity, 30% lower capex, and 41% lower power versus the prior architecture
Short Verdict
Jupiter is one of the least-discussed but most load-bearing pieces of Google’s AI infrastructure. Instead of fixed electrical switches wired into a rigid spine-and-leaf topology, Google uses mirror-based optical switches that can redirect light between any two points in the building without touching a cable. That lets Google reconfigure the network’s shape in software, route around failures in milliseconds, and upgrade link speeds one section at a time instead of ripping out an entire data center’s spine. For TPU training, Google’s own technical blog states plainly that this network — which it calls Jupiter in its 2022 research publication and simply the “Data-Center Network” in its 2025 Ironwood materials — is the layer that stitches individual superpods together into the massive clusters needed for frontier-scale AI training.
What Jupiter Actually Is
According to Google’s own Cloud blog and its peer-reviewed SIGCOMM 2022 paper (“Jupiter Evolving: Transforming Google’s Datacenter Network via Optical Circuit Switches and Software-Defined Networking”), Jupiter is the data-center network fabric connecting the servers, storage, and accelerators inside Google’s warehouse-scale computers. It was first deployed in 2015, built on three ideas: a logically centralized software-defined networking (SDN) control plane managing thousands of switching chips, a Clos (non-blocking, multistage) network topology, and commodity “merchant silicon” switching hardware. At that scale, Google reports more than 30,000 servers in a single deployment, uniform 40 Gb/s per-server links, and more than 1 petabit per second of aggregate bandwidth, guaranteeing sub-100-microsecond latency for arbitrary server-to-server communication.
Why Optical Circuit Switching
The original Clos design had a structural limitation Google’s paper describes directly: the network’s “spine” layer has to be fast enough to match whatever the newest, fastest attached devices need, and every part of the building needs full fanout to that spine. Upgrading link speeds across a live data center meant replacing the entire spine at once — expensive and operationally disruptive. Google’s fix was to insert a layer of MEMS-based optical circuit switches between aggregation blocks. An OCS doesn’t parse or route packets at all; it uses two sets of mirrors that physically rotate to redirect light from an input fiber to an output fiber, which makes it agnostic to data rate and wavelength. That means the optical layer can sit in the building’s infrastructure indefinitely while the electrical switches behind it are upgraded independently, and Google’s centralized Orion SDN control plane can reconfigure which blocks are connected to which — in effect rewiring the building’s logical topology in software, coordinating link drains, routing changes, and OCS reconfiguration together.
Google’s SIGCOMM paper reports that this direct-connect, OCS-based approach achieved roughly 5x higher speed and capacity over a decade of production use, alongside a 30% reduction in capital expenditure and a 41% reduction in power, while being deployed incrementally against live production traffic. About 60% of production traffic takes a direct path between source and destination blocks in this topology, with the rest transiting one additional block, and OCS-based reconfiguration is reported as roughly 3x faster than the patch-panel-based fiber changes it replaced.
How This Differs From the TPU’s Own Interconnect
It’s important to separate two distinct optical-switching layers in Google’s AI stack, both documented in Google’s own materials but at different scopes:
Inter-Chip Interconnect (ICI) and in-pod OCS: This is the TPU-specific fabric that wires individual chips into a pod and a pod into a superpod. Google’s published TPU v4 research paper describes using 48 MEMS-based “Palomar” optical circuit switches to link 64-chip blocks into a 4,096-chip, 3D-torus supercomputer, letting Google reconfigure the torus topology in software and route around failed hosts rather than requiring near-perfect hardware availability. For the current Ironwood TPU generation, Google’s Cloud blog describes the same OCS pattern operating at the “cube” (64 chips) and “superpod” (9,216 chips, 144 cubes) level, with the OCS fabric manager able to optically bypass a failed cube or link and swap in a spare.
Jupiter / the Data-Center Network (DCN): This is the general-purpose fabric, described in Google’s 2022 Jupiter paper, that connects whole superpods, and everything else in the data center, to each other. Google’s 2025 Ironwood announcement states explicitly that for the largest-scale systems — into the hundreds of thousands of chips — multiple superpods are connected via this standard data-center network, with other Google materials naming that network Jupiter.
In short: OCS does double duty in Google’s stack, but at two different scales, built by overlapping but distinct engineering efforts — one wires chips into a pod, the other wires pods into a building-spanning, and ultimately campus-spanning, cluster.
Jupiter vs. In-Pod TPU Optical Switching
Dimension
In-pod/superpod OCS (ICI layer)
Jupiter / Data-Center Network
Scope
Chips within a cube/pod/superpod (up to 9,216 TPU chips on Ironwood)
Connecting whole superpods and other data-center infrastructure to each other
Documented scale
TPU v4: 4,096 chips via 48 Palomar OCSes; Ironwood: 9,216-chip superpods built from 144 cubes
Software-configurable torus topology; tolerates 0.1%–1.0% host unavailability without rewiring
5x higher speed/capacity, 30% lower capex, 41% lower power over a decade of production use (SIGCOMM 2022)
Stated role for largest AI clusters
Builds the superpod itself
Connects multiple superpods into clusters of “hundreds of thousands” of chips, per Google’s Ironwood blog
Trade-offs
Pros
Cons / Open Questions
Software-reconfigurable topology avoids physical rewiring for upgrades or failure recovery
Google’s own published figures for Jupiter mostly predate the current TPU generation (2015/2022); up-to-date bandwidth/latency figures for connecting Ironwood-era superpods specifically are not published in the sources reviewed here
OCS is data-rate agnostic, letting link speeds be upgraded incrementally rather than building-wide
All performance figures (5x speed/capacity, 30% lower capex, etc.) are Google’s own claims from its SIGCOMM paper, not independently audited
Fault tolerance: can bypass failed hardware optically, in milliseconds, rather than failing the whole topology
Exact bandwidth/latency specifically for the Jupiter layer connecting multiple TPU superpods (as opposed to the in-pod ICI figures) is not broken out in Google’s public TPU materials
Who This Matters To
Infrastructure engineers and researchers evaluating why Google can plausibly offer TPU training clusters at the scale of hundreds of thousands of chips — the answer isn’t just more chips, it’s a network layer purpose-built to reconfigure itself around those chips in software. It’s also relevant to anyone comparing Google’s approach to Nvidia’s NVLink/InfiniBand/Spectrum-X stack or AWS’s EFA: all three hyperscalers have converged on optical and software-defined techniques for scale-out AI networking, but Google’s OCS-centric approach, deployed for general-purpose data-center traffic since 2015 and later adapted to TPU pods, is the most publicly documented example of reusing a decade-old general networking investment for AI-specific scale-out.
Who Should Look Elsewhere
Readers looking for exact current bandwidth and latency numbers for Jupiter connecting today’s Ironwood-generation superpods specifically won’t find them in Google’s public materials as of this writing — Google’s most detailed published Jupiter figures are from its 2015 and 2022 (SIGCOMM) disclosures, which predate Ironwood and describe general data-center traffic rather than TPU-cluster-to-TPU-cluster traffic specifically. Readers wanting to compare raw chip-level FLOPS or pricing across Trillium, Ironwood, and Nvidia GPUs should look at TPU-chip-focused coverage instead; this piece deliberately stays at the network layer.
Bottom Line
Jupiter is Google’s general-purpose, OCS-based data-center network, in production since 2015 and significantly reworked by 2022 to use direct-connect topologies managed by centralized SDN. It is distinct from, but complementary to, the optical circuit switching Google also uses inside TPU pods and superpods to wire individual chips together. Per Google’s own 2025 Ironwood materials, it’s this outer network layer — not the in-pod interconnect — that lets Google link multiple 9,216-chip superpods into AI clusters reaching into the hundreds of thousands of chips. The chips get the headlines; the fabric is what makes clustering them at that scale possible at all.
FAQ
Is Jupiter the same thing as the optical switching inside a TPU pod? No. Google documents two separate uses of optical circuit switching: one inside TPU pods/superpods (wiring chips and cubes together, as described in the TPU v4 paper and Ironwood blog), and Jupiter, the broader data-center network that connects whole superpods and other infrastructure to each other.
How big is a Jupiter deployment? Google’s 2015 disclosure describes a single deployment of more than 30,000 servers with over 1 Pb/s of aggregate bandwidth; by 2022, Google reported more than 6 Pb/s of data-center bandwidth using the evolved, OCS-based architecture.
What is an optical circuit switch, technically? Per Google’s published description, it’s a switch that uses two sets of MEMS mirrors, rotating in two dimensions, to redirect light from an input fiber to an output fiber without parsing or routing packets — making it transparent to the data rate and wavelength of the signal passing through it.
How many TPU chips can a single Jupiter-connected cluster reach? Google’s Ironwood materials state that individual superpods reach 9,216 chips, and that connecting multiple superpods via the data-center network (Jupiter) scales to “hundreds of thousands” of chips. Google does not publish an exact maximum chip count for a single cluster in the sources reviewed for this article.
Google Drive, Dropbox, and Box all solve the same basic problem — store files in the cloud and let a team access and share them — but they sell very different team sizes and security postures. Drive comes bundled inside Google Workspace, Dropbox sells storage with a simpler admin layer, and Box leans hardest into enterprise compliance and admin controls. We pulled current pricing directly from each vendor’s pricing page to compare what a team actually gets per dollar.
At a Glance
Tool
Entry Team Price
Storage
Best For
Google Drive (via Workspace)
Business Starter — $7/user/mo (annual commitment)
30 GB pooled per user
Teams that want Docs/Sheets/Meet collaboration built in, not just file storage
Dropbox
Standard — $15/user/mo
Starts at 3 TB for the team
Teams that just want fast, reliable file sync/sharing without a full office suite
Box
Business — $15/user/mo (min. 3 users)
Unlimited
Larger or compliance-heavy teams needing deep admin controls and unlimited storage
Short Verdict
If your team is already using Gmail, Docs, Sheets, and Meet, Google Drive via Business Starter at $7/user/month is the cheapest entry point and the storage is simply a byproduct of the suite you’re already paying for. If you want pure file storage and sharing without buying into an entire office suite, Dropbox Standard at $15/user/month gives a generous 3 TB team pool and a simpler admin experience than Box. If unlimited storage and heavier compliance/admin tooling (DLP, SOC certifications, advanced classifications) matter more than simplicity, Box’s $15/user/month Business plan — with no fixed storage cap — is the strongest fit, especially as the team or file volume grows.
What Each Tool Is
Google Drive isn’t sold as a standalone team product — it’s the storage layer underneath every Google Workspace plan, pooled per user and shared across the organization. Per Google’s own pricing page, Business Starter includes 30 GB pooled storage per person along with 2-step verification and endpoint management; Business Standard raises that to 2 TB and adds group-based policy controls; Business Plus reaches 5 TB and adds Vault for retention/eDiscovery and Secure LDAP; Enterprise goes to 5 TB or more with full DLP, context-aware access, and enterprise data regions.
Dropbox is a dedicated file-sync and sharing product first. Per Dropbox’s pricing page, the Standard team plan starts at 3 TB of pooled team storage with an admin console, device approvals, granular permissions, and centralized billing; the Advanced plan starts at 15 TB and layers in tiered admin roles, end-to-end encryption, advanced key management, compliance tracking, and single sign-on.
Box positions itself as the enterprise-content-management-grade option. Per Box’s pricing page, even the entry Business Starter plan (100 GB, minimum 3 users) includes 2-factor authentication and file versioning, but storage becomes unlimited starting at the Business plan, which adds data loss protection, an Admin Console, custom branding, watermarking, and SOC 1/2/3 support. Higher tiers (Business Plus, Enterprise, Enterprise Plus, Enterprise Advanced) add FedRAMP Moderate and HIPAA support, advanced threat detection and classifications, and — at the top tier — AI agent guardrails and long-term archival.
Pricing Breakdown
Plan Tier
Google Drive / Workspace
Dropbox
Box
Entry
Business Starter — $7/user/mo (annual commitment; $3.50 intro rate for first 20 users for 12 months); 30 GB pooled/user
Standard — $15/user/mo; 3 TB team pool; admin console, device approvals, granular permissions
Business Plus — $22/user/mo; 5 TB pooled/user; Vault retention/eDiscovery, Secure LDAP
Enterprise — custom pricing; storage not publicly stated
Business Plus — $25/user/mo (min. 3 users); unlimited storage; advanced admin controls
Top
Enterprise — custom pricing; 5 TB+ pooled/user; full DLP, context-aware access, enterprise data regions
—
Enterprise — $35/user/mo (min. 3 users); unlimited storage; FedRAMP Moderate, HIPAA, SOC 1/2/3; Enterprise Plus from $50/user/mo; Enterprise Advanced from $70/user/mo
Individual (non-team) plans exist on both Dropbox and Box for comparison: Dropbox Plus is $9.99/month for 2 TB with no team admin features, and Box’s Personal Pro is $10/month for 100 GB. Box also offers a free Individual plan (10 GB, 250 MB max file size) and a free Developer tier (10 GB, 2 GB max file size), while Dropbox’s free Basic plan gives just 2 GB.
Google Drive: Pros and Cons
Pros: Cheapest entry point of the three at $7/user/month; storage comes bundled with Gmail, Docs, Sheets, Slides, and Meet rather than being a separate purchase; strong real-time collaborative editing built in.
Cons: Entry-tier storage (30 GB pooled per user) is the smallest of the three at the lowest tier; advanced security (DLP, context-aware access) is reserved for Enterprise; you’re buying an entire productivity suite, not just storage, whether you need the rest of it or not.
Dropbox: Pros and Cons
Pros: Generous 3 TB team pool at the entry Standard tier; admin console and device approvals included from Standard; widely regarded for fast, reliable file sync across platforms.
Cons: SSO and end-to-end encryption are reserved for the pricier Advanced tier ($24/user/mo); no unlimited-storage tier short of custom Enterprise pricing; doesn’t include a bundled office suite the way Drive does.
Box: Pros and Cons
Pros: Unlimited storage starting at the $15/user/month Business tier; the deepest compliance credential list of the three (FedRAMP Moderate, HIPAA, SOC 1/2/3) at Enterprise; granular admin controls, watermarking, and classifications aimed at regulated industries.
Cons: Every team plan requires a minimum of 3 users, so it’s not practical for solo users or very small teams; Business Starter’s 100 GB and 2 GB max file size are tight if you’re not ready to jump to the unlimited Business tier; pricing climbs quickly at the top end (up to $70/user/month for Enterprise Advanced).
Who Each Tool Is a Good Fit For
Choose Google Drive/Workspace if your team is going to use Gmail, Docs, Sheets, and Meet regardless, and file storage is just one piece of a broader productivity-suite decision.
Choose Dropbox if you want dedicated, best-in-class file sync and sharing without committing to a full office suite, and a 3 TB team pool comfortably covers your needs.
Choose Box if your team has heavy compliance requirements (HIPAA, FedRAMP, SOC audits), handles large or unpredictable storage volumes, or needs the deepest admin/classification controls of the three — and you have at least 3 users to meet its minimum-seat requirement.
Who Should Look Elsewhere
Solo users or two-person teams will find Box’s 3-user minimum on every paid team plan a poor fit — Dropbox’s individual Plus plan or Google’s personal Drive storage both serve smaller setups without that constraint. Teams that specifically need SSO or end-to-end encryption on a budget should note that Dropbox reserves both for its pricier Advanced tier, and Google reserves comparable controls for Business Plus and Enterprise — budget accordingly rather than assuming the entry tier covers it.
Bottom Line
This isn’t really a storage-only comparison — it’s a decision about which bundle of adjacent tools you want storage attached to. Google Drive is the cheapest way in if you want an office suite included, Dropbox is the most focused pure file-sharing tool with a generous entry storage pool, and Box is the strongest choice once compliance and unlimited storage matter more than simplicity or price.
FAQ
Does any of these three offer unlimited storage? Yes — per Box’s official pricing page, every tier from Business upward ($15/user/month, minimum 3 users) includes unlimited storage. Neither Google Workspace nor Dropbox publish an unlimited tier; both scale storage by pooled amount per tier.
Which is cheapest for a small team? Google Workspace Business Starter at $7/user/month (with an introductory $3.50/user/month rate for the first 20 users for 12 months) is the lowest listed entry price of the three, per Google’s official pricing page.
Does Dropbox or Box include an office suite like Google Docs? No — neither Dropbox nor Box bundles a word processor, spreadsheet, or video-conferencing suite the way Google Workspace does. Both focus on file storage, sync, and sharing, with collaboration layered on top rather than a full productivity suite included.
Is there a minimum number of users for team plans? Box requires a minimum of 3 users on every team-tier plan, per its pricing page. Dropbox’s Standard and Advanced team plans and Google Workspace’s Business tiers do not state a minimum seat count on their pricing pages.
AI code review agents are a distinct category from AI pair-programming tools or static analysis scanners: instead of writing code or scanning a whole repo on a schedule, they sit inside the pull request workflow itself, posting comments, flagging risky changes, and sometimes pushing fixes directly to the branch. CodeRabbit, Greptile, and Qodo are three of the most widely adopted agents in this space. Here’s how their current pricing, PR-workflow integration, and review coverage compare — a companion piece to our look at static analysis tools like SonarQube, Semgrep, and CodeQL and the broader risks covered in our piece on AI-generated code’s hidden technical debt.
At a Glance
Tool
Entry Price
Billing Model
Git Platforms
Best For
CodeRabbit
$24/user/mo (Essentials)
Per-seat, tiered
GitHub, GitLab
Teams wanting a full PR-review suite: chat, autofix, security scans, pre-merge checks
Teams that want deep whole-codebase context and don’t want per-seat pricing
Qodo
From ~$30/mo (2,500 credits, Pro Team)
Credit-based, pooled across team
GitHub, GitLab, Bitbucket, Azure DevOps, Gerrit
Teams wanting broad git-platform coverage and ticket/requirement-aware review
Short Verdict
CodeRabbit is the most feature-complete out of the box, with review, chat, autofix, and security scanning bundled into a predictable per-seat price — but it’s GitHub/GitLab-only and the cost scales linearly with headcount. Greptile differentiates on review depth: it builds a graph index of the entire codebase before reviewing a PR, which helps it catch cross-file logic bugs that diff-only tools miss, and its usage-based Pro plan avoids per-seat fees entirely. Qodo offers the broadest git-platform support (including Azure DevOps and Gerrit) and adds requirement-aware review against linked tickets, with Enterprise-only access to on-prem and air-gapped deployment.
How Each Tool Integrates Into the PR Workflow
CodeRabbit installs as a GitHub or GitLab app and reviews PRs automatically, posting inline comments, a summary, and (on paid tiers) autofix suggestions it can commit directly. It also offers a CLI and IDE extension for pre-commit feedback, plus “CodeRabbit Engineer,” an on-demand deeper review available across all tiers. Review tone is configurable via profiles (Quiet, Chill, Assertive), and teams can set pre-merge checks that block a PR until specific conditions pass.
Greptile first indexes a repository into a dependency/function graph, then dispatches a “swarm” of parallel review agents against each new PR so reviews account for how a change ripples through the rest of the codebase, not just the diff. It reads prior PR comments to infer team conventions and supports plain-English custom rules. Its TREX feature runs the PR branch in a sandbox to catch runtime-only bugs that static review can’t see. Greptile supports GitHub, GitLab, and Bitbucket natively, with GitHub Enterprise Server/Cloud, GitLab Self-Managed, Bitbucket Data Center, Gitea, and Perforce (via P4 Code Review) on Enterprise.
Qodo (formerly CodiumAI) describes itself as “Git agnostic,” supporting GitHub, GitLab, Bitbucket, Azure DevOps, and Gerrit. Its agentic PR review checks changes against linked ticket requirements and cross-repo breaking changes, ranking findings by severity with blockers surfaced first. Qodo also offers “shift-left” pre-PR skills and an unlimited, no-cap rules system for enforcing team-specific standards.
Pricing Comparison
Plan
CodeRabbit
Greptile
Qodo
Free / Starter
Not published as a standalone paid-free tier (FAQ references a free open-source plan)
Starter: Free — 1 active developer, 50 credits/mo, unlimited repos
No permanent free tier; 14-day trial, free program for qualifying open-source projects
All three offer 20% off for annual billing where seat-based (CodeRabbit), and Greptile’s and Qodo’s usage-based models mean actual monthly cost depends on PR volume rather than headcount. A 10-developer team reviewing a moderate volume of PRs could land anywhere from roughly $240/month (CodeRabbit Essentials at list price) to a usage-driven total on Greptile or Qodo that’s cheaper for low-volume teams and potentially more expensive for very high-volume ones.
What Each Tool Actually Flags
CodeRabbit: logic bugs (e.g., stale cache after a DB update, missing token-expiry checks), dependency vulnerabilities via scheduled and per-PR deep scans (CodeRabbit Secure), and style/convention adherence via configurable review profiles and learned team conventions.
Greptile: “style violations to security risks and multi-file logical bugs,” per its own description — concrete examples include unbalanced resource handling, undefined methods breaking downstream calls, and mid-loop overflow bugs. A separate Security Review product exists, and TREX catches runtime-only issues via sandboxed execution.
Qodo: bugs and “issues that matter,” ranked by severity with blockers first; requirement gaps against linked tickets; cross-repo breaking changes. Qodo’s own marketing does not explicitly categorize its findings into style/security/test buckets the way CodeRabbit and Greptile do, so teams evaluating it for dedicated security review should verify current capability directly with Qodo rather than assume parity with the other two.
CodeRabbit cons: GitHub/GitLab only (no confirmed Bitbucket or Azure DevOps support); cost scales directly with headcount regardless of PR volume.
Greptile pros: whole-codebase graph indexing for deeper cross-file review; no per-seat fees on Pro; widest Enterprise git-platform coverage including Perforce and Gitea.
Greptile cons: usage-based pricing is harder to forecast than flat per-seat plans; Starter free tier limited to a single developer.
Qodo pros: broadest standalone git-platform list (including Azure DevOps and Gerrit); requirement/ticket-aware review; flexible credit packs pooled across the team.
Qodo cons: no permanent free tier; published marketing is less explicit than competitors about dedicated security-finding categories; Enterprise gated behind a 30+ user minimum.
Who Each Tool Is a Good Fit For
Choose CodeRabbit if your team is on GitHub or GitLab and wants one predictable, feature-rich subscription covering review, chat, autofix, and basic security scanning without assembling several point tools.
Choose Greptile if your codebase is large or has deep cross-module dependencies where diff-only review misses real risk, and you’d rather pay for actual usage than a fixed per-seat fee.
Choose Qodo if your org runs on Azure DevOps, Bitbucket, or Gerrit (platforms CodeRabbit doesn’t confirm support for) or if ticket/requirement-aware review is a priority alongside standard bug-catching.
Bottom Line
None of these tools replace a human reviewer or a dedicated static-analysis/SAST pipeline — they’re a first-pass layer that catches obvious logic errors, flags risky patterns, and reduces the volume of trivial comments a human reviewer has to write. Which one fits best depends more on your git platform and PR volume than on raw review quality: CodeRabbit for GitHub/GitLab teams wanting an all-in-one subscription, Greptile for codebase-wide context without per-seat costs, and Qodo for platform breadth and requirement-aware checks. Run a real sprint of PRs through each tool’s trial before committing, since review quality and false-positive rates vary meaningfully by codebase and language.
FAQ
Can these tools automatically fix issues, not just flag them? CodeRabbit explicitly offers “autofix” that can commit suggested fixes directly to a PR branch on paid tiers. Greptile and Qodo both surface “suggested fixes” in review comments; check each vendor’s current documentation for whether auto-committing fixes is supported on your plan.
Do any of these tools support self-hosting or on-prem deployment? Yes — all three offer this only on Enterprise plans: CodeRabbit lists “custom deployment (including self-hosting),” Greptile lists self-hosting, and Qodo lists single-tenant SaaS or on-prem/air-gapped deployment.
Are these tools a replacement for SAST/static analysis tools like Semgrep or CodeQL? No. They operate at the PR-review layer, using LLM-based reasoning over the diff and surrounding code context, which is a different mechanism than the pattern-based and dataflow analysis SAST tools use. Many teams run both — see our comparison of SonarQube, Semgrep, and CodeQL for the static-analysis side of that stack.
Is pricing per developer seat, or based on usage? CodeRabbit is per-seat across all its named tiers. Greptile’s Pro plan has no seat fees and bills per credit instead. Qodo’s Pro Team plan is credit-based and pooled across the whole team rather than priced per seat.
IBM’s Telum II processor already puts an AI accelerator directly on the mainframe chip, scoring transactions for fraud in under a millisecond. But on-chip silicon has a ceiling: it is built for speed on small, simple models, not for the larger neural networks and large language models that generative and agentic AI demand. IBM’s answer is the Spyre Accelerator, a PCIe card that plugs into IBM Z, LinuxONE, and now Power systems to add a much bigger pool of dedicated AI compute alongside Telum II. This piece explains what Spyre is, how it divides labor with Telum II, what IBM says it’s for, and where it stands today.
AT A GLANCE
Fact
Detail
What it is
A PCIe add-in AI accelerator card for IBM Z, LinuxONE, and Power servers, built from IBM Research’s AI Hardware Center work
Who makes it
IBM (IBM Research AI Hardware Center, previewed publicly at Hot Chips 2024)
Primary use case
Low-latency inferencing for generative and agentic AI, and larger/more complex predictive models (fraud detection, retail automation, code modernization) that exceed what the on-chip Telum II accelerator alone can handle
Where it fits in the stack
Add-on AI acceleration layer alongside Telum II’s on-chip accelerator — not a replacement for it, additional PCIe-attached capacity
Availability (per IBM)
Generally available for IBM z17 and LinuxONE 5 since October 28, 2025; Power11 support followed in December 2025
Short Verdict
Spyre is IBM’s acknowledgment that one on-chip accelerator, however fast, can’t carry the full weight of generative and agentic AI on a mainframe. By putting a scalable, 32-core AI chip onto a PCIe card that can be clustered up to 48-deep, IBM gives IBM Z and LinuxONE shops a path to run bigger models in the same data center as the transaction data, without shipping that data out to a separate AI cluster or the public cloud. It’s a genuinely new category of mainframe hardware, commercially available as of late 2025, not a prototype or a roadmap promise.
What the Spyre Accelerator Is
According to IBM’s official commercial-availability announcement and IBM Research’s own technical blog, the Spyre Accelerator is a system-on-a-chip with 32 AI accelerator cores and 25.6 billion transistors, built on a 5-nanometer process. It ships as a 75-watt PCIe card. Multiple cards can be installed in a single system: IBM states up to 48 Spyre cards can be clustered into one IBM Z or LinuxONE system, and up to 16 into a Power11 server, with card memory capacity reported at up to 1 TB per the card’s technical coverage. The chip is optimized for matrix and vector math — the operations most AI inference relies on — and supports lower-precision numeric formats such as int8 and int4, which reduce memory footprint and power draw versus running the same models on general-purpose CPU cores.
Spyre traces its lineage to IBM’s AIU (Artificial Intelligence Unit) research prototype, itself an extension of the on-chip AI accelerator design first shipped in the Telum processor (used in the IBM z16, announced 2022). IBM first previewed Spyre publicly at the Hot Chips 2024 conference, then announced it for commercial availability alongside the z17-generation Telum II processor on October 7, 2025, with shipping beginning October 28, 2025, for z17 and LinuxONE 5, and Power11 support arriving in December 2025.
How Spyre Complements Telum II
Telum II’s on-chip AI accelerator and Spyre are built on similar underlying architecture, but they occupy different places in the inferencing pipeline. Per IBM’s own technical announcement for Telum II and the z17, the on-chip accelerator is rated at 24 TOPS (trillion operations per second) per chip, scaling to roughly 192 TOPS across a fully configured eight-chip drawer, and it is designed to sit directly in the path of live transactions — any processor core in the system can dispatch inference work to any on-chip accelerator, balancing load across the drawer in real time. IBM’s benchmark for an LSTM-based fraud-detection model on this on-chip accelerator claims up to 5 million inference operations per second with sub-millisecond response time.
Spyre exists because that on-chip capacity, while extremely fast, is still finite and shared with every other transaction running on the processor. IBM’s announcement describes connecting multiple Spyre Accelerators into the I/O subsystem of IBM Z and LinuxONE via PCIe to “substantially increase” available AI acceleration beyond what’s built into the chip. In practice, this means Telum II handles the always-on, inline scoring that must keep pace with transaction throughput, while Spyre provides a much larger, dedicated compute pool for workloads that need more model capacity than the on-chip accelerator was designed to carry — larger neural networks, ensemble approaches that combine a traditional model with a large language model, and generative or agentic AI tasks. IBM’s Telum II announcement specifically describes an “ensemble AI” pattern for insurance-claims and financial-crime detection, where a traditional neural network produces an initial risk score and an LLM-based pass refines it — the kind of workload that benefits from Spyre’s added capacity.
Workloads IBM Targets
Advanced fraud and financial-crime detection: models too complex for the on-chip accelerator alone, run in-line with transaction processing rather than as a separate batch job.
Retail automation and other predictive use cases IBM groups alongside fraud detection in its commercial-availability announcement.
Generative and agentic AI directly on the mainframe or LinuxONE system, which IBM frames around the need for real-time responsiveness without moving sensitive transaction data off-platform.
Code modernization, including COBOL-to-modern-language translation and watsonx Code Assistant-style tooling, cited in IBM’s and IBM Research’s coverage of Spyre.
Document ingestion on Power11: IBM reports internal testing (on a 1-million-unit dataset, using a single-card container, at a prompt size of 128) showing more than 8 million documents ingested per hour for knowledge-base integration — a figure IBM itself notes may vary by workload.
Spyre vs. Telum II At a Glance
Dimension
Telum II (on-chip accelerator)
Spyre Accelerator (PCIe card)
Location
Built into the processor chip itself
Separate PCIe add-in card, connected via the I/O subsystem
Cores / throughput cited
24 TOPS per chip; up to ~192 TOPS per 8-chip drawer
32 AI accelerator cores per card; up to 48 cards per Z/LinuxONE system
Best suited for
Always-on, inline inferencing at transaction speed (e.g., per-swipe fraud scoring)
Larger models, ensemble AI, generative/agentic AI needing more dedicated capacity
Availability
Shipped with z17 (announced April 2025)
GA October 28, 2025 (z17, LinuxONE 5); Power11 December 2025
Trade-offs
Pros
Cons
Keeps AI inferencing co-located with transaction data on the mainframe, avoiding data movement to a separate AI cluster
Only benefits organizations already running IBM Z, LinuxONE, or Power11 — not a general-purpose accelerator available on other platforms
Scales well beyond on-chip capacity (up to 48 cards per system) for genuinely large models
Public performance figures so far are limited to IBM’s own internal benchmarks (e.g., the Power11 document-ingestion figure), which IBM itself flags as workload-dependent
Designed to pair naturally with Telum II’s existing inline accelerator rather than replace it
Newly GA as of late 2025 for Z/LinuxONE and Power11 — limited independent, third-party benchmarking exists yet
Who It’s Relevant For
Banks, insurers, payment processors, and other IBM Z or LinuxONE customers running real-time fraud and compliance workloads that need more AI model capacity than Telum II’s on-chip accelerator alone provides — particularly where regulatory or latency requirements make moving transaction data to an external GPU cluster impractical. Power11 shops building retrieval-augmented generation or document-ingestion pipelines that need to stay close to enterprise data are the other clear fit, per IBM’s own cited use cases.
Who Should Look Elsewhere
Organizations without an existing IBM Z, LinuxONE, or Power11 footprint gain nothing from Spyre specifically — it is not a standalone accelerator card for x86 servers or other clouds. Teams training large foundation models from scratch, rather than running inference on them, are also outside Spyre’s current stated scope; IBM frames mainframe-side model training as a longer-term research direction, not a shipped capability today.
Bottom Line
Spyre is the second half of IBM’s two-tier AI inferencing strategy for the mainframe: Telum II’s on-chip accelerator handles the always-on, millisecond-scale scoring baked into every transaction, and Spyre adds a much larger, clusterable pool of dedicated AI compute for the generative, agentic, and ensemble workloads that transaction-speed silicon alone can’t carry. It reached general availability for z17 and LinuxONE 5 on October 28, 2025, with Power11 support following in December 2025 — making it a shipped, commercially available product rather than a research preview, built on technology IBM first showed publicly at Hot Chips 2024.
FAQ
Is the Spyre Accelerator the same thing as Telum II’s AI accelerator? No. Telum II’s AI accelerator is built into the mainframe processor chip itself. Spyre is a separate 75-watt PCIe card that adds additional, larger-scale AI compute alongside it.
What systems support Spyre? Per IBM’s commercial-availability announcement, Spyre is generally available for IBM z17 and LinuxONE 5 (since October 28, 2025) and for IBM Power11 servers (since December 2025).
How many Spyre cards can one system hold? IBM states up to 48 cards in a single IBM Z or LinuxONE system, and up to 16 in a Power11 server.
What workloads is Spyre built for? IBM’s own materials cite advanced fraud detection, retail automation, generative and agentic AI, code modernization (including COBOL-to-modern-language translation), and, on Power11, high-throughput document ingestion for knowledge-base and retrieval-augmented-generation use cases.
Can Spyre train AI models, not just run inference? Not currently, per IBM’s public statements. IBM Research describes fine-tuning and eventual training on the mainframe as a future direction, but Spyre’s shipped capability today is inferencing.
Issue tracking is one of the few tools every engineering team touches daily, which makes the choice of platform a long-term commitment rather than a quick trial. Jira, Linear, and Shortcut represent three different philosophies: Jira’s near-infinite configurability for large, process-heavy organizations; Linear’s fast, opinionated workflow built for product teams that want speed over flexibility; and Shortcut’s lean, developer-friendly middle ground for smaller teams that have outgrown spreadsheets but don’t want Jira’s complexity. Here’s how their current pricing, workflow philosophy, and integrations compare.
Large orgs with complex, cross-team processes and compliance needs
Linear
$10/user/mo (Basic)
Unlimited members, 2 teams, 250 issues
Fast and opinionated: minimal setup, built-in best-practice workflow
Product and engineering teams that want speed and consistency over configurability
Shortcut
$8.50/user/mo (Team)
Up to 10 users, 1 team, 1 workflow
Lean and developer-centric: simple workflow states, story/epic hierarchy
Small-to-mid-size engineering teams wanting Jira-like structure without the overhead
Short Verdict
If your organization needs custom approval chains, multiple departments on one instance, or compliance features like audit logs and data residency, Jira’s Premium or Enterprise tiers are built for exactly that — at the cost of a steeper learning curve and per-seat prices that climb fast at small scale. Linear is the better choice for product-engineering teams who want a consistent, fast-moving workflow without configuring one from scratch — its opinionated defaults mean less setup but also less flexibility to bend the tool to an unusual process. Shortcut sits between the two: more structured than Linear, far simpler than Jira, and priced to match lean engineering teams.
What Each Tool Actually Is
Jira (Atlassian) is the industry-standard, enterprise-configurable issue tracker. Every plan includes unlimited projects and work items, Scrum and Kanban boards, and (starting with Standard) automation rules, custom permission schemes, issue-level security, and audit logs. Premium adds Advanced Roadmaps, a developer sandbox, and a 99.9% uptime SLA; Enterprise scales to multi-site deployments across up to 150 sites with a single per-user license. Atlassian’s Rovo AI features are bundled into paid tiers with a credit allowance that grows at each level (25 credits/user on Standard, 70 on Premium, 150 on Enterprise).
Linear takes the opposite approach: a deliberately narrow, fast interface with keyboard-first navigation and a workflow that’s largely pre-decided for you (triage, backlog, in progress, done). Business-tier features include Issue SLAs, “Triage Intelligence” and “Code Intelligence” AI features, Linear Insights for reporting, and native Zendesk/Intercom integrations. Linear restricts SSO to Google on its Business tier — SAML/SCIM and advanced admin controls are Enterprise-only.
Shortcut (formerly Clubhouse) targets small-to-mid-size software teams with a structure closer to Jira’s (stories, epics, objectives) but far less configuration overhead. The free plan caps out at 10 users and a single team/workflow; Team tier unlocks automations, WIP limits, and up to 5 teams/workflows; Business tier adds OKR-style Objectives and Key Results, advanced custom fields, and multiple workspaces. SSO and SCIM are available as paid add-ons rather than bundled into a specific tier.
Pricing Comparison
Plan
Jira
Linear
Shortcut
Free
$0 — up to 10 users, 100 automation rule runs/mo, 2GB storage, no roles/permissions
$0 — unlimited members, 2 teams, 250 issues, 10MB uploads, Google SSO only
$0 — up to 10 users, 1 team, 1 workflow, 5GB storage, Admin/Owner roles only
Custom — volume discounts, SSO/SCIM included, premier support SLA
Jira’s per-user price actually drops as team size grows — list pricing for Standard falls from $9.70/user/month at 1–100 users down into the low single digits at tens of thousands of users, while Premium follows the same declining curve. Linear and Shortcut, by contrast, publish flat per-user pricing regardless of team size at the Basic/Team and Business levels, with custom discounts reserved for Enterprise deals.
Trade-offs
Jira pros: unmatched configurability (custom workflows, fields, permission schemes), scales from startup to multi-thousand-person enterprise on one platform, the deepest third-party marketplace of any issue tracker.
Jira cons: that same configurability means setup and admin overhead; small teams often find it slower and heavier than they need; free tier caps at just 10 users with no roles or permissions.
Linear pros: genuinely fast UI, strong keyboard-driven workflow, generous free tier for small teams (unlimited members, 250 issues), clean built-in reporting (Insights) on Business tier.
Linear cons: less workflow customization than Jira — teams with unusual processes may find Linear’s defaults restrictive; SSO limited to Google below Enterprise; no on-prem/self-hosted option.
Shortcut pros: structured enough for real engineering process (epics, objectives) without Jira’s weight; competitive per-seat pricing; startups under 50 employees can get a free year.
Shortcut cons: smaller ecosystem and integration marketplace than Jira or Linear; SSO/SCIM cost extra even on paid tiers; free tier limited to a single team and workflow.
Who Each Tool Is a Good Fit For
Choose Jira if you’re a larger organization with multiple departments, compliance requirements (audit logs, data residency, IP allowlisting), or workflows that genuinely differ team-to-team and need their own custom fields, statuses, and approval chains.
Choose Linear if you’re a product-led engineering org that wants everyone moving fast inside a consistent, opinionated workflow, and you’re willing to adapt your process to the tool rather than the other way around.
Choose Shortcut if you’re a small-to-mid-size engineering team that wants more structure than Linear’s minimalism but doesn’t want to pay for or administer Jira’s enterprise machinery — especially if you qualify for Shortcut’s startup or nonprofit discounts.
Bottom Line
Team size and process complexity — not raw price — should drive this decision. A 10-person startup will likely outgrow Jira’s free tier friction before it outgrows Linear’s or Shortcut’s; a 500-person engineering organization with compliance obligations will likely outgrow Linear’s and Shortcut’s lighter administration tooling before it outgrows Jira’s. Run a real sprint or two in each tool’s free/trial tier with your actual backlog before signing an annual contract, since switching issue trackers later is expensive in migrated history and retrained habits.
FAQ
Does Jira get cheaper per user as my team grows? Yes — Atlassian’s published Jira Cloud pricing tables show per-user list prices declining in tiers as total user count rises, from $9.70/user/month at 1–100 users down to a few dollars per user at the highest volume tiers (list pricing, before any negotiated discount).
Can I self-host any of these tools? Jira offers Server and Data Center deployment options in addition to Cloud, per Atlassian’s own pricing page. Linear and Shortcut are cloud-hosted SaaS only, with no published self-hosted option.
Which tool has the most generous free tier? Linear’s free tier allows unlimited members (capped at 2 teams and 250 issues total), which is more generous on user count than Jira’s or Shortcut’s 10-user caps — though all three free tiers restrict teams, automation, or advanced permissions in some way.
Do any of these include AI features without extra cost? Jira bundles Rovo AI credits into every paid tier (25/user on Standard, rising to 150/user on Enterprise). Linear includes “Triage Intelligence” and “Code Intelligence” AI features starting on its Business tier, though its pricing page notes that coding sessions and some AI features draw on separate AI credits across all tiers. Shortcut’s published pricing page does not list a dedicated AI feature tier.
Picking a form builder in 2026 usually comes down to three very different philosophies: Typeform’s conversational, one-question-at-a-time design; Jotform’s sprawling, feature-dense toolkit with hundreds of integrations; and Google Forms’ bare-bones, completely free simplicity for anyone already living in Google Workspace. We dug into each vendor’s current pricing pages and help documentation to see what you actually get at each tier, and who each tool really fits.
Basic: $39/mo ($28/mo billed annually), 100 base responses/mo
Conversational, design-forward forms and surveys for marketing/lead gen
Jotform
5 active forms, 100 submissions/mo, 10 signed documents/mo
Paid plans (Bronze) start from $19/mo
Teams that need a huge library of templates, integrations, and payment/e-sign forms
Google Forms
Unlimited forms and responses, full feature set, no cost
Not sold standalone — bundled in Google Workspace (Business Starter from roughly $7–12/user/mo depending on region and billing term)
Anyone already on Google Workspace who needs a fast, free, no-frills form
Short Verdict
If budget is the deciding factor and you already have a Google account, Google Forms wins outright — it is free, has no response cap, and covers logic branching and quiz scoring without a credit card. If you want forms that feel like a conversation and convert well for marketing campaigns, Typeform is worth its premium, but its free plan is genuinely restrictive at just 10 responses a month. If you need the most features per dollar — payment collection, e-signatures, approval workflows, hundreds of integrations — Jotform’s free tier is more usable day-to-day than Typeform’s, and its paid plans start lower, at $19/month.
What Each Tool Is
Typeform built its reputation on a full-screen, one-question-at-a-time interface that feels more like a conversation than a static form. It’s popular for lead-gen quizzes, customer feedback, and job applications where completion rate and brand feel matter more than raw cost. According to Typeform’s own pricing page, every paid tier (Basic and above) includes conditional logic, webhooks, and integrations such as Google Sheets, HubSpot, Mailchimp, Slack, and Zapier, with partial-response capture, custom subdomains, and branding removal unlocked at higher tiers.
Jotform takes the opposite approach: a traditional drag-and-drop form builder with an enormous feature surface. Jotform’s own help center lists 150+ to 200+ integrations plus Zapier access to 3,000+ further apps, built-in payment gateways, e-signature collection, and approval workflows. It’s the kind of tool that can replace several specialist apps (forms, basic e-sign, simple payment collection) for a small operations or HR team.
Google Forms is the free, no-signup-required form tool bundled into every Google account and every Google Workspace plan. Per Google’s own product page, it supports multiple question types, built-in logic/branching (“skip to section based on answer”), quiz scoring, real-time response charts, and direct export to Google Sheets. It isn’t sold as a separate product — it’s simply included wherever Google Workspace or a personal Google account is used.
5 active forms, 100 submissions/mo, 10 signed documents/mo
Unlimited forms and responses, no branding, no cost, ever
Entry paid tier
Basic — $39/mo monthly, $28/mo billed annually; 100 base responses/mo (up to 750), 1 GB file uploads, 1 user
Bronze — from $19/mo; 25 active forms, 1,000 submissions/mo, 100 signed documents/mo
N/A (not sold as a standalone paid product)
Mid tier
Plus — $79/mo monthly, $56/mo annually; 1,000 base responses/mo, custom subdomain, branding removal, 3 users
Silver — 50 active forms, 2,500 submissions/mo, 250 signed documents/mo
N/A
Upper tier
Business — $129/mo monthly, $91/mo annually; 10,000 base responses/mo, drop-off/conversion tracking, 4 GB uploads, 5 users
Gold — 100 active forms, 10,000 submissions/mo, 1,000 signed documents/mo
N/A
Enterprise
Custom pricing, custom response volume
Custom pricing, multiuser management
Included free with any Google Workspace edition (which itself is priced per user/month, separately from Forms)
Two caveats worth flagging. Jotform’s public pricing page does not publish exact dollar figures for its Silver and Gold tiers — only that paid plans “start at $19 per month” and that limits increase at each level, per Jotform’s own help documentation. If an exact Silver/Gold price matters to your budgeting, confirm it directly on Jotform’s checkout flow before committing, since it can vary by promotion and region. Second, Google Workspace’s per-user pricing is region- and currency-dependent and uses an interactive calculator rather than a fixed USD table, so treat the Workspace cost above as directional rather than exact — Forms itself remains free with any personal Google account regardless of Workspace pricing.
Typeform: Pros and Cons
Pros: Best-in-class conversational UI that tends to boost completion rates for marketing and feedback forms; logic and integrations (Zapier, HubSpot, Salesforce) included from the entry Basic tier; clean analytics on drop-off and conversion at higher tiers.
Cons: Free plan is capped at just 10 responses/month, which is unusable for anything beyond testing; response-based pricing means costs scale quickly once you move past testing; advanced logic/scoring with partial responses is reserved for pricier tiers.
Jotform: Pros and Cons
Pros: Free Starter plan is more workable day-to-day (100 submissions/mo plus signed documents); huge integration and template library; built-in payments and e-signatures reduce the need for separate tools; paid plans start lower than Typeform’s.
Cons: Interface is denser and less “designed” than Typeform’s; exact pricing for Silver/Gold tiers isn’t published as a fixed number on the public pricing page; oldest submissions can be auto-deleted once total storage limits are exceeded.
Google Forms: Pros and Cons
Pros: Completely free with no response or form caps; tight integration with Sheets, Drive, and the rest of Google Workspace; simple branching logic and quiz scoring built in; nothing to configure or pay for to get started.
Cons: Minimal design customization compared to Typeform or Jotform; no built-in payment collection or e-signature workflow; file-upload questions require respondents to sign in with a Google account and use the form owner’s Drive storage; fewer native third-party integrations than Jotform.
Who Each Tool Is a Good Fit For
Choose Typeform if you’re running marketing lead-gen, NPS/feedback surveys, or job applications where the respondent’s experience and your brand’s polish matter, and you have budget for a per-response pricing model.
Choose Jotform if you need one tool to cover forms, simple payments, approval workflows, and e-signatures without buying three separate SaaS subscriptions, and you want the most functional free tier of the three.
Choose Google Forms if cost is the primary constraint, your team already lives in Google Workspace, and your form needs are straightforward — surveys, RSVPs, quizzes, internal data collection — without payment processing or heavy branding requirements.
Who Should Look Elsewhere
High-volume survey teams on a tight budget may find Typeform’s response-based pricing punishing — Jotform’s submission caps scale more gradually per dollar. Teams that need serious e-signature compliance workflows (audit trails, legally binding multi-party signing) should also compare against a dedicated e-signature tool rather than relying on Jotform’s or any form builder’s signing feature alone. And organizations without any Google Workspace footprint may find Google Forms’ lack of payment and advanced branding support a dealbreaker for customer-facing forms.
Bottom Line
There’s no single “best” form builder — the right pick depends on whether you’re optimizing for conversion design (Typeform), feature breadth per dollar (Jotform), or zero cost with Google Workspace integration (Google Forms). For most small teams just getting started, Google Forms is the rational default until a specific limitation — payment collection, branding, or advanced logic — forces an upgrade to Typeform or Jotform.
FAQ
Is Google Forms really free forever? Yes. Google Forms is included with any personal Google account at no cost, with no response limit, and is also bundled into every paid Google Workspace edition.
How many responses does Typeform’s free plan allow? 10 responses per month across all of your typeforms, per Typeform’s help center — forms themselves are unlimited, but response collection is capped.
Can Jotform collect payments and signatures? Yes — Jotform’s free Starter plan includes payment integrations and up to 10 signed documents per month, scaling to 100, 250, and 1,000 signed documents on the Bronze, Silver, and Gold plans respectively, per Jotform’s own plan documentation.
Does Google Forms support conditional logic? Yes, in a basic form — you can set a form to jump to a specific section based on an earlier answer, which Google’s own product page describes as a way to improve completion rates, though it is less granular than Typeform’s or Jotform’s full conditional-logic engines.
Oracle spent decades building its business on the idea that customers run Oracle Database on Oracle’s own infrastructure. In 2023, that changed. Oracle began physically installing its own database hardware inside the data centers of its three biggest cloud rivals — Microsoft Azure, Amazon Web Services, and Google Cloud — under a family of offerings it brands “Database@AWS,” “Database@Azure,” and “Database@Google Cloud.” This piece explains what each partnership actually delivers, how it differs from simply running Oracle software on rented cloud compute, and why Oracle believes giving up single-cloud exclusivity is the right trade.
AT A GLANCE
Fact
Detail
What it is
Oracle Exadata database hardware and Oracle Database software, physically deployed inside a partner cloud’s own data centers
Who makes it
Joint engineering/commercial offering between Oracle and Microsoft, Oracle and AWS, and Oracle and Google Cloud (three separate deals, not one)
Primary use case
Moving mission-critical Oracle databases (often on-premises Exadata) into a public cloud without re-architecting applications, while keeping low-latency access to that cloud’s compute and AI services
Where it fits in the stack
Data layer — sits alongside, not instead of, the partner cloud’s native compute, analytics, and AI services; billed and supported jointly
Status (per official sources)
Database@Azure: generally available in many regions worldwide. Database@AWS: GA since July 8, 2025, initially in US East (N. Virginia) and US West (Oregon), with expansion planned. Database@Google Cloud: live with Exadata and Autonomous AI Database services
Short Verdict
Oracle’s multicloud database strategy is a genuinely unusual move for an infrastructure vendor: instead of forcing customers to choose Oracle Cloud Infrastructure (OCI) over AWS, Azure, or Google Cloud, Oracle brought its own hardware to its competitors’ data centers. For enterprises with large, latency-sensitive Oracle estates who are already committed to a specific hyperscaler for compute and AI, this removes a real architectural headache — cross-cloud network hops between application and database. It is not a replacement for OCI, and it does not make Oracle Database cheaper or easier to run than it was before; it mainly removes the “which cloud do I put the database in” decision as a blocker to modernization.
What It Is: Three Separate Deals, One Pattern
Each “Database@” offering follows the same basic pattern, confirmed on Oracle’s own documentation and product pages: Oracle Exadata infrastructure is installed and run inside the partner cloud’s physical data centers, managed through OCI control systems, but purchased, provisioned, and in most cases monitored through the partner cloud’s own console. The partner cloud supplies the data-center facility, power, physical security, and networking; Oracle supplies and operates the database hardware and software stack on top of it. The three deals are not identical, however — they launched at different times, with different service catalogs and regional footprints.
Oracle Database@Azure
According to Oracle’s official Database@Azure page, this offering provides Oracle Exadata Database Service (including a version built on Exadata Exascale Infrastructure for smaller workloads that scale incrementally), Oracle Autonomous AI Database, high-availability features such as Real Application Clusters (RAC), Data Guard, Maximum Availability Architecture, and GoldenGate replication, plus Oracle Zero Downtime Migration tooling. The Exadata hardware is colocated directly in Azure data centers across North America, South America, Europe, the Middle East, Africa, and Asia Pacific. Customers buy it through Azure Marketplace, can apply spend against an existing Azure consumption commitment, and can bring their own Oracle licenses. Oracle’s pitch centers on pairing Oracle AI Vector Search and Oracle data with Microsoft Copilot and Power BI without moving data across clouds, plus unified monitoring, billing, identity, and support.
Oracle Database@AWS
Database@AWS reached general availability on July 8, 2025, per Oracle’s press release and AWS’s own “What’s New” announcement, initially in the US East (N. Virginia) and US West (Oregon) Regions, with Oracle and AWS stating plans to expand to roughly 20 more regions. The service includes Oracle Exadata Database Service and Oracle Autonomous Database on Dedicated Exadata Infrastructure, provisioned through the AWS Management Console and purchasable via AWS Marketplace, including private offers from Oracle. AWS’s announcement highlights integration with AWS Identity and Access Management, CloudWatch, CloudFormation, CloudTrail, EventBridge, and VPC Lattice, plus zero-ETL integration into Amazon Redshift for near-real-time analytics on Oracle transactional data, and the option to store backups in Amazon S3. Oracle SVP Karan Batta framed the rationale directly in Oracle’s release: “Customers have been putting their most valuable data in Oracle databases for decades… Oracle Database@AWS lets them run Oracle Database workloads on OCI in AWS,” combined with “AWS’s advanced generative AI and analytics services.”
Oracle Database@Google Cloud
Per Google Cloud’s and Oracle’s joint documentation, Database@Google Cloud deploys Oracle Exadata systems inside Google Cloud data centers, running Exadata Database Service, Autonomous AI Database Service, Base Database Service, Exadata Database Service on Exascale Infrastructure, and GoldenGate. Google Cloud supplies the core data-center infrastructure, physical and network security, and hardware monitoring for the underlying OCI resources, while customers manage the service through the Google Cloud console, the gcloud CLI, or a dedicated Oracle Database@Google Cloud API, with connectivity handled through what Google calls ODB Networks. Oracle announced expanded AI database services for this offering at Oracle AI World in October 2025. The publicly available documentation does not spell out as many specific integration workloads (equivalents of AWS’s Redshift zero-ETL or Azure’s Copilot tie-in) as the other two partnerships describe; where that specificity is missing, we have left it out rather than guess.
How the Three Partnerships Compare
Dimension
Database@Azure
Database@AWS
Database@Google Cloud
Core database services
Exadata Database Service (incl. Exascale), Autonomous AI Database, RAC, Data Guard, MAA, GoldenGate
Exadata Database Service, Autonomous Database on Dedicated Exadata Infrastructure
Exadata Database Service (incl. Exascale), Autonomous AI Database Service, Base Database Service, GoldenGate
Management console
Azure portal, OCI console
AWS Management Console
Google Cloud console, gcloud CLI, dedicated API
Headline AI integration
Oracle AI Vector Search with Microsoft Copilot and Power BI
Zero-ETL to Amazon Redshift for near real-time analytics
Expanded Oracle AI Database services announced at Oracle AI World 2025
Purchasing
Azure Marketplace, Azure consumption commitment, Bring Your Own License
AWS Marketplace, including private offers; counts toward AWS commitments; Oracle Support Rewards
Not detailed in public documentation at time of writing
Regional footprint (per official sources)
Many regions across multiple continents
US East (N. Virginia), US West (Oregon) at GA, ~20 more regions planned
Live in supported Google Cloud regions; exact count not specified in reviewed docs
Why Oracle Is Doing This
The strategic logic, as Oracle itself describes it, is not about winning a head-to-head cloud infrastructure contest against AWS, Azure, and Google Cloud on compute, storage, or AI model training — Oracle Cloud Infrastructure still exists as its own standalone offering for customers who want that. Instead, Database@ is built around a narrower and, for Oracle, more defensible asset: an enormous installed base of mission-critical Oracle databases that enterprises are reluctant to migrate off Exadata hardware or rewrite against a different database engine. Rather than requiring those customers to pick OCI as their cloud of record, Oracle lets them keep whichever hyperscaler already runs their applications, analytics, and AI workloads, and simply brings the Oracle database to that cloud. This also answers a very practical infrastructure problem: a database in one cloud region and an application in another cloud’s region means every query crosses the public internet or a dedicated interconnect, adding latency and often data-transfer charges. Colocating Exadata inside the same data center as the application removes that hop entirely.
How This Differs From a Traditional Single-Cloud Strategy
No forced migration off Exadata. Customers keep Real Application Clusters, GoldenGate replication, and Oracle’s high-availability architecture exactly as they ran on-premises, rather than being pushed onto a different database engine native to the hyperscaler.
Hardware, not just software, moves. This is not Oracle Database running as a VM image on rented AWS/Azure/Google compute — it is actual Oracle-managed Exadata infrastructure physically sited in the partner’s data center.
Unified operations across two vendors. Billing, identity, support, and (in most cases) provisioning happen through the partner cloud’s own console and marketplace rather than requiring a separate OCI relationship.
The customer’s “primary cloud” doesn’t change. A company that has standardized on AWS for everything else doesn’t need an OCI account, VPN, or interconnect to a separate Oracle region — the database shows up inside AWS itself.
Trade-offs
Pros
Cons / Open Questions
Eliminates cross-cloud latency between application and Oracle database
Still requires Oracle Exadata licensing and support costs; doesn’t eliminate Oracle’s pricing model
No application rewrite needed to migrate off on-premises Exadata
Three separate partnerships with different regional footprints and (for Google Cloud) less publicly documented integration detail — feature parity across all three is not guaranteed
Keeps customers on their chosen hyperscaler for compute/AI while retaining Oracle for data
Creates a three-way support relationship (customer, Oracle, hyperscaler) that can complicate troubleshooting versus a single-vendor stack
Enables AI/analytics tie-ins specific to each cloud (Redshift zero-ETL on AWS, Copilot/Power BI on Azure)
Database@AWS launched in only two regions at GA (July 2025), so geographic coverage still trails Database@Azure
Who It’s Relevant For
Enterprises with large, latency-sensitive Oracle Exadata estates (financial services, telecom, large-scale ERP, government) that have already standardized their applications and AI tooling on a specific hyperscaler, and that want to retire on-premises Exadata hardware without a database migration project, are the clearest fit. It also suits organizations running hybrid Oracle-plus-cloud-native architectures that need the database and the application compute to sit in the same data center for compliance or performance reasons.
Who Should Look Elsewhere
Organizations building new, cloud-native applications with no existing Oracle investment have little reason to introduce Oracle Exadata licensing costs and operational complexity through this route; a hyperscaler’s own managed database service (Amazon RDS, Azure SQL, Google Cloud SQL/AlloyDB) is the simpler starting point. Companies that want the full Oracle Cloud Infrastructure platform — not just the database — are also better served going directly to OCI rather than a Database@ offering, which only brings the database layer into the partner cloud.
Bottom Line
Database@AWS, Database@Azure, and Database@Google Cloud are Oracle’s answer to a problem that has nothing to do with chips or GPUs: enterprises have decades of mission-critical data locked into Oracle Exadata, and they don’t want to choose between keeping that database and standardizing on a single hyperscaler for everything else. By physically placing Exadata hardware inside each partner’s data centers, Oracle sidesteps that choice entirely. It’s a multicloud strategy built on dependency, not on OCI winning a head-to-head infrastructure fight — and so far, based on Oracle’s own GA dates and regional rollouts, Azure has the broadest footprint, AWS is the newest and most narrowly scoped, and Google Cloud sits in between with Oracle actively expanding its AI database services there as of late 2025.
FAQ
Is Database@AWS/Azure/Google Cloud the same as running Oracle Database on a virtual machine in that cloud? No. These are dedicated Oracle Exadata systems physically installed in the partner’s data centers and managed through OCI, not Oracle software installed on generic rented compute instances.
Do all three partnerships offer the same features? No. Based on official documentation, Database@Azure and Database@Google Cloud both offer Exadata Database Service (including Exascale Infrastructure) plus GoldenGate, while Database@AWS’s publicly documented catalog centers on Exadata Database Service and Autonomous Database on Dedicated Exadata Infrastructure. Each also has distinct cloud-specific integrations (Redshift zero-ETL on AWS; Copilot/Power BI on Azure).
Does this replace Oracle Cloud Infrastructure (OCI)? No. OCI continues to exist as Oracle’s own full cloud platform. Database@ offerings only bring the database layer into a partner cloud; compute, AI training infrastructure, and other services in that scenario still come from the partner (AWS, Azure, or Google Cloud), not from OCI directly.
Which of the three launched first, and which has the widest availability? Public sources reviewed here confirm Database@Azure’s regional footprint spans many regions across several continents, and that Database@AWS reached general availability on July 8, 2025, starting in just two AWS regions with further expansion planned. Exact first-announcement dates for all three were not consistently available across the official pages reviewed for this article.
Choosing an API client in 2026 is no longer just about which tool has the nicest request builder. Postman’s March 2026 pricing overhaul, Insomnia’s shift toward unlimited Git Sync for paid users, and Bruno’s offline-first, git-native approach have turned “which API tool” into a real architecture decision: do you want a cloud-hosted workspace, or do you want your API collections to live as plain text in the same repo as your code? This guide compares current pricing, collaboration models, and local-first vs. cloud-based design across Postman, Insomnia, and Bruno so you can pick the right fit for your team.
At a Glance
Tool
Starting Paid Price
Free Tier
Local-First?
Git-Native Storage
Best For
Postman
$9/mo (Solo), $19/user/mo (Team)
Yes, 1 user, 100 AI credits/mo
No — cloud workspace by default
Supports Git-based sync as a feature, not the default model
Teams that want a full API platform: mocks, monitors, docs, catalog
Insomnia
$12/user/mo (Pro)
Yes, unlimited for 1–3 users on Git Sync
Partial — local/cloud/Git storage options per project
Git Sync built in; choice of storage per project
Teams that want flexibility between local, Git, and cloud storage
Bruno
$6/user/mo (Pro add-on)
Yes, core app fully free and open source
Yes — offline by design, no cloud sync in the app itself
Collections are plain-text .bru files, versioned like code
Teams that want API collections to live and diff in Git like source code
Short Verdict
Postman is the platform choice: it bundles API design, mock servers, monitoring, and a private API network, but its per-seat pricing adds up fast for larger teams. Insomnia sits in the middle, giving you a genuine choice between cloud convenience and Git-based storage on a per-project basis. Bruno is the purist’s pick: the desktop app is free, open source, and stores every request as a plain-text file that reviews and diffs exactly like code — with an optional paid layer for teams that want shared workspaces, OpenAPI sync, and enterprise identity controls on top of that free core.
What Each Tool Actually Is
Postman has grown from a request-building Chrome extension into a full “API platform”: a client, a spec editor, mock servers, automated monitors, a Private API Network for internal discovery, and (as of its 2026 pricing update) an AI credit system baked into every tier. Collections can sync through Postman’s cloud or through Native Git integration, but the cloud workspace is the default collaboration surface.
Insomnia, owned by Kong, is built around the same request/collection model but gives teams an explicit choice of where data lives: Cloud projects, Local projects, or Git Sync projects, selectable per project rather than forced account-wide. Its Essentials (free) tier already includes unlimited Git Sync for up to three users, which is unusually generous for a free plan. Insomnia also ships an Inso CLI for running collections in CI/CD.
Bruno takes the opposite starting position: the open-source desktop app (MIT licensed) is local-first and offline by design — its maintainers have stated there are no plans to add cloud sync inside the app itself. Every request, folder, and environment is written to disk as a human-readable .bru file, so a collection is just another set of files in your repository: it diffs cleanly in pull requests and needs no account to use. On top of that free core, Bruno sells an optional licensed layer (workspaces, Git-provider integration, OpenAPI sync, SSO/SCIM) for teams that want managed collaboration without giving up the plain-text format.
All three vendors bill their paid per-seat tiers annually by default, so monthly-billing buyers should expect a premium over the figures above. Postman’s and Insomnia’s Enterprise tiers are the least transparent: both ultimately route larger teams to a sales conversation rather than a fixed self-serve price.
Pros and Cons
Postman pros: the broadest feature set (mocks, monitors, API catalog, docs hosting), huge ecosystem and integrations, built-in AI assistant credits.
Postman cons: cloud-centric by default, per-user Team pricing climbs quickly, free tier now capped at a single user.
Insomnia pros: genuine per-project choice of storage (local, cloud, or Git), a free tier generous enough for very small teams, straightforward CLI for CI/CD.
Insomnia cons: Enterprise jumps sharply to $45/user/month before larger-team discounts kick in; some advanced governance features are Enterprise-only.
Bruno pros: the core app is completely free, open source, and offline — no account, no vendor lock-in, and collections version-control naturally since they’re just text files.
Bruno cons: smaller ecosystem and plugin marketplace than Postman or Insomnia; managed collaboration features (shared workspaces, OpenAPI sync at scale) require the paid Pro or Ultimate layer; no native cloud sync inside the free app for teams that want that convenience.
Who Each Tool Is a Good Fit For
Choose Postman if your organization needs more than a request client — API design governance, hosted documentation, scheduled monitors, and a searchable internal API catalog — and per-seat cost is a secondary concern next to having one platform for the whole API lifecycle.
Choose Insomnia if different teams or projects within your org have different needs — some want a quick cloud workspace, others want Git-based review — and you’d rather pick per project than commit the whole org to one storage model.
Choose Bruno if your team already treats API contracts as code: you want requests reviewed in pull requests, run in CI via the Bruno CLI or Docker image, and stored with zero dependency on a third-party cloud account. It’s also the clear pick for privacy-sensitive teams that don’t want API payloads touching an external server at all.
Bottom Line
There’s no universal winner — the right tool depends on whether you want a managed platform (Postman), flexible per-project storage (Insomnia), or a git-native, local-first workflow (Bruno). Smaller engineering teams increasingly default to Bruno or Insomnia’s free tiers to avoid Postman’s per-seat costs, while platform teams running large API catalogs still lean on Postman’s broader feature set. If you’re unsure, start with each tool’s free tier against a real collection before committing a whole team to annual billing.
FAQ
Is Bruno really free for teams, not just individuals? Yes — the core desktop app is MIT-licensed open source with no user cap for local, offline use. Paid tiers only add managed extras like shared workspaces, private Git provider integration, OpenAPI sync at scale, and enterprise identity features (SSO/SCIM).
Can I use Git with Postman and Insomnia too, or is that Bruno-only? No — both Postman (Native Git integration) and Insomnia (Git Sync projects) support storing and syncing collections through Git. The difference is that Bruno’s file format is git-native by default for every user, while Postman and Insomnia treat Git as one storage option alongside their own cloud.
Which tool is cheapest for a 10-person engineering team? Based on published list pricing, Bruno’s Pro tier ($6/user/month) and Insomnia’s free Essentials tier (unlimited Git Sync for up to 3 users, though a 10-person team would need Pro at $12/user/month) are the least expensive starting points; Postman’s Team tier ($19/user/month) is the most expensive of the three at list price.
Do these tools support GraphQL and gRPC, not just REST? Bruno explicitly supports REST, GraphQL, gRPC, and WebSocket in its client. Postman and Insomnia both support REST and GraphQL as well; check each vendor’s current documentation for the latest protocol coverage before standardizing on one tool for non-REST APIs.
REST (Content Delivery/Management API) and GraphQL
Sanity
Managed (Content Lake) with open-source Studio you can self-host as a UI
Yes (Free, forever)
$15/seat/month (Growth)
GROQ (native query language) plus a GraphQL API
Strapi
Self-hosted (MIT-licensed, free) or Strapi Cloud (managed)
Yes — Community Edition is free and open-source; Cloud has no permanent free tier
$35/month (Cloud Starter) or $45/month (self-hosted Growth)
REST by default, with an official GraphQL plugin
These three aren’t really competing on the same axis. Contentful and Sanity are managed, API-first content platforms you rent; Strapi is open-source software you can run yourself for free, with a managed Cloud option if you don’t want to. If “self-hosted” or “no vendor lock-in” matters to your team, that alone should narrow the field before price does.
What These Platforms Are
A headless CMS separates content storage and editing from presentation, serving content to any frontend — a Next.js site, a mobile app, a kiosk — through an API rather than server-rendered templates. Contentful and Sanity are both commercial SaaS platforms: you don’t run any servers, you just model content and query it. Strapi is different in kind, not just in price: it’s an open-source Node.js application distributed under the MIT license, which you can self-host on your own infrastructure at zero license cost, or run on Strapi’s own managed Cloud if you’d rather not operate it yourself.
Pricing Breakdown
Platform
Tier
Price
Key Limits
Contentful
Free
$0 forever
10 users, 2 locales, 100K API calls/month, 50GB CDN bandwidth/month, 1 Starter Space (25 content types, 2 environments, 10,000 records)
Lite
$300/month
20 users, 3 locales, 1M API calls/month, 100GB bandwidth/month; a second “Lite Space” costs an additional $850/month
Enterprise
Custom quote
Unlimited API calls, custom users/spaces, 24/7 support, up to 99.99% uptime SLA
Sanity
Free
$0 forever
Up to 20 seats, 2 public datasets, 10k documents, 1M CDN API requests/month, 100GB bandwidth
Growth
$15/seat/month
Up to 50 seats, private datasets, 25k documents; add-ons include Dedicated Support ($799/month) and extra datasets ($999/dataset/month)
Unlimited users; RBAC included; no audit logs, review workflows, or SSO
Cloud Starter
$35/month
100k API requests/month, 50GB storage, 50GB bandwidth, project sleeps when idle, no backups
Cloud Business
$450/month
10M API requests/month, 1,000GB storage/bandwidth, daily backups, 99.9% uptime SLA, priority support
Strapi also sells a self-hosted Growth plan at $45/month (including 3 users) for teams that want enterprise features like Live Preview and content-release tooling without moving to Strapi Cloud, with add-ons for SSO ($150/month plus $50/user/month) and AI credits. All three vendors charge overage fees once you exceed a tier’s included usage: Contentful at $5 per extra 1M API calls, Sanity at $1 per extra 250k CDN requests, and Strapi at $1.50 per extra 25k API requests.
Pros and Cons
Contentful
Pros: Mature structured-content model with 2 free environments and a generous 100K-call free tier; both REST and GraphQL content APIs are first-class, well-documented options.
Pros: Enterprise tier adds Personalization, Studio, and AI Actions add-ons for teams that want a broader content platform, not just an API.
Cons: The jump from Free to Lite is steep — $300/month — with a second content “Space” costing a further $850/month, which is a real cliff for growing teams.
Cons: No self-hosting option at any price; you’re locked into Contentful’s infrastructure and SLAs.
Sanity
Pros: GROQ, Sanity’s native query language, gives developers a genuinely different (and widely praised) way to shape complex, relational content queries that REST-only CMSs struggle with; a GraphQL API is also available.
Pros: Per-seat pricing ($15/seat on Growth) is more predictable for small teams than Contentful’s flat per-plan jump, and the free tier’s 20 seats is generous.
Cons: The Sanity Studio editing UI is open-source and can be self-hosted, but the underlying Content Lake (where data actually lives) is managed-only — there’s no fully self-hosted path.
Cons: Private datasets, review tooling, and SSO are gated behind Growth and Enterprise respectively, and extra datasets are expensive at $999/month each on Growth.
Strapi
Pros: The only one of the three that’s genuinely free to self-host at any scale under an MIT license — no seat caps, no usage meters, full control of your data and infrastructure.
Pros: Ships REST by default with an official GraphQL plugin, so teams aren’t locked into one query paradigm.
Cons: Community Edition has no audit logs, review workflows, or SSO out of the box — those require either the paid Growth/Enterprise self-hosted tiers or Strapi Cloud.
Cons: Self-hosting means you own uptime, scaling, and security patching yourself; Strapi Cloud’s entry Starter tier has no backups and the project “sleeps when idle,” which isn’t production-ready for most sites.
Who Each Platform Is a Good Fit For — and Who Should Look Elsewhere
Contentful suits teams that want a battle-tested, fully managed platform and can either stay comfortably within the Free tier’s limits or justify enterprise-level spend — the Lite tier’s $300/month floor makes it an awkward middle option for small teams scaling past free-tier usage. Sanity is a strong fit for developers who want a more expressive query layer than REST alone and whose team size maps cleanly onto per-seat pricing. Strapi is the right call for teams that want to self-host, avoid recurring API-call fees entirely, or need full control over their data residency and infrastructure — and the wrong call for teams that don’t want to own server operations and aren’t ready to pay for Strapi Cloud’s production-grade (Business-tier) reliability.
Bottom Line
Pick Strapi if self-hosting or open-source licensing is a requirement, not a preference. Pick Sanity if your content model is complex and relational and your team will benefit from GROQ’s query power. Pick Contentful if you want the most established managed platform and your usage (or budget) clears the Free-to-Lite jump comfortably. All three remain actively developed, officially documented, and genuinely API-first — the real decision is hosting model and pricing shape, not capability.
Frequently Asked Questions
Can I self-host Contentful or Sanity? No. Contentful is fully managed SaaS with no self-hosted option. Sanity’s Studio editing interface is open-source and can be self-hosted, but its Content Lake data store is managed-only.
Is Strapi really free? Yes — Strapi Community Edition is MIT-licensed and free to self-host with unlimited users, though you pay for your own hosting infrastructure and lose enterprise features like audit logs and SSO unless you upgrade to a paid self-hosted tier or Strapi Cloud.
Does Sanity support GraphQL, or only its own query language? Both. GROQ is Sanity’s native and most commonly used query language, but a GraphQL API is also officially available.
Which platform is cheapest for a small project? On a strict free-tier basis, all three offer a permanent free plan, but Strapi’s free Community Edition has no usage meter at all (only your own hosting costs), while Contentful and Sanity’s free tiers cap API calls, records, and bandwidth.
Do any of these charge for exceeding usage limits? Yes. Contentful charges $5 per additional 1M API calls; Sanity charges $1 per additional 250k CDN API requests on Growth; Strapi Cloud charges $1.50 per additional 25k API requests.
Statuses above are taken directly from Google’s own Privacy Sandbox feature status page, last updated August 14, 2026.
The Short Version
If you’ve been planning for a “cookieless 2026,” pause and recheck your assumptions. Google is not removing third-party cookies from Chrome. What it has done instead is retire most of the Privacy Sandbox APIs that were supposed to replace them — Topics, Protected Audience, Attribution Reporting, and Private Aggregation/Shared Storage — after years of delay, citing low ecosystem adoption. The practical result for 2026: third-party cookies keep working in regular Chrome browsing much as they always have, while the privacy-preserving ad-targeting and measurement tools Google spent six years building are being wound down.
How We Got Here: A Timeline of Reversals
Privacy Sandbox was announced in 2019 as Google’s plan to phase out third-party cookies in Chrome and replace cross-site tracking and ad measurement with a set of privacy-preserving browser APIs. That original cookie-deprecation timeline slipped repeatedly over 2021–2024. The real pivot points, confirmed by Google’s and the UK Competition and Markets Authority’s own records, were:
July 2024: Google announced it would not deprecate third-party cookies by default, proposing instead to give users an “informed choice” via a new prompt.
April 2025: Google dropped the plan for a standalone third-party-cookie choice prompt altogether, reaffirming it would keep Chrome’s existing approach to cookies rather than ship any new blocking mechanism.
June–July 2025: The UK CMA — which had been overseeing Google’s Privacy Sandbox commitments since accepting them in February 2022 — opened a consultation (June 13, 2025) on releasing Google from those commitments, stating it “believes the commitments are no longer necessary.”
October 17, 2025: Two things happened the same day. The CMA formally released Google from its Privacy Sandbox commitments, saying its “competition concerns no longer arise.” And Google’s VP of Privacy Sandbox, Anthony Chavez, published “Update on Plans for Privacy Sandbox Technologies,” announcing the retirement of the Topics API, Protected Audience API, Attribution Reporting API, and Private Aggregation (including Shared Storage), “after evaluating ecosystem feedback about their expected value and in light of their low levels of adoption.”
What’s Actually Being Retired
According to Google’s own feature status page, the relevance and measurement APIs that advertisers were told to prepare for — Topics (interest-based targeting without third-party cookies), Protected Audience (on-device remarketing/auction, formerly FLEDGE), and Attribution Reporting (conversion measurement) — are all marked “Deprecate and remove” in Chrome and “Scheduled for phaseout” on Android. Private Aggregation and Shared Storage, the lower-level primitives several of those APIs depended on for noisy, aggregated reporting, are being retired alongside them. Fenced Frames, the isolated-rendering mechanism Protected Audience used, is listed as “Scheduled for phaseout.” Google’s announcement gives no specific removal date, saying only that it “will follow Chrome and Android processes for phasing out these technologies and share updates on our developer site.”
Not everything is being scrapped. Google’s status page lists several Privacy Sandbox-adjacent mechanisms it intends to keep supporting in Chrome, including CHIPS (partitioned cookies), FedCM (federated identity), the Storage Access API, User-Agent reduction and Client Hints, Private State Tokens, and bounce-tracking mitigations. These are lower-profile, less ad-targeting-specific technologies than the headline APIs, and they survive the cuts.
So What Happens to Third-Party Cookies in Chrome?
Nothing changes by default. Google’s own cookies documentation does not announce any new blocking or removal of third-party cookies; it instead describes them as something that “may or may not be available” depending on browser design, enterprise policy, or user choice — the same framing Chrome has used for years (Incognito mode, for instance, has blocked third-party cookies by default since 2020, independent of Privacy Sandbox). Google explicitly says it will “maintain our current approach to offering users third-party cookie choice in Chrome,” which — after the April 2025 reversal — means no new standalone prompt and no default blocking beyond what already existed before Privacy Sandbox began.
Trade-Offs and What Remains Unresolved
The practical trade-off for advertisers is this: the status quo (third-party cookies continuing to work) is more stable than it has been in years, but it isn’t guaranteed to be permanent, and the tools Google built as an alternative are now being dismantled rather than matured. Google cited “low levels of adoption” as its reasoning — ad tech companies largely didn’t build their targeting and measurement stacks around Topics, Protected Audience, or Attribution Reporting at scale, preferring to keep relying on cookies and other identifiers while Google’s timeline kept slipping. That leaves the industry without a widely adopted privacy-preserving replacement, and without near-term regulatory pressure forcing one, since the CMA closed its oversight of the commitments in October 2025. Separately, Google’s own status page shows some Android-side mechanisms (On-Device Personalization, Protected App Signals, SDK Runtime) also being deprecated or phased out, so mobile measurement strategies tied to those APIs need the same re-evaluation as web strategies.
Bottom Line
Don’t build a 2026 media plan around the assumption that third-party cookies are going away in Chrome — Google’s own developer site confirms they aren’t being deprecated, and the APIs meant to replace them (Topics, Protected Audience, Attribution Reporting, Private Aggregation) are the ones actually being retired. The safer long-term bet is still first-party data and consent-based targeting, not because Chrome is about to block cookies, but because Google itself has shown it will abandon ad-targeting infrastructure that doesn’t reach adoption — and there’s no guarantee today’s “current approach” to cookies survives the next policy or regulatory shift either.
Frequently Asked Questions
Are third-party cookies dead in Chrome in 2026? No. Google’s own Privacy Sandbox site states Chrome is maintaining its current approach to third-party cookies and is not deprecating them by default.
What exactly did Google retire on October 17, 2025? The Topics API, Protected Audience API, Attribution Reporting API, and Private Aggregation (including Shared Storage), per Google VP Anthony Chavez’s official announcement, citing low ecosystem adoption.
Does this mean Privacy Sandbox is completely gone? Not entirely. Several components — CHIPS, FedCM, the Storage Access API, User-Agent reduction, Private State Tokens, and bounce-tracking mitigations — remain supported in Chrome per Google’s status page.
What role did the UK’s competition regulator play? The CMA had overseen Google’s Privacy Sandbox commitments since February 2022. On October 17, 2025 — the same day Google announced the API retirements — the CMA formally released Google from those commitments, saying its competition concerns “no longer arise.”
Is there an exact date when Topics, Protected Audience, and Attribution Reporting will be removed from Chrome? Google has not published a specific removal date; its announcement says only that it will follow Chrome’s standard deprecation process and post updates on its developer site.
Documented TCF v2.2/v2.3 support; published a TCF v2.4 readiness guide in August 2026
Large enterprises wanting one platform for cookies, privacy rights, and risk
Cookiebot (Usercentrics)
Public self-serve tiers, plus a custom enterprise tier
From $10/month (Premium Lite)
Lists “IAB TCF 2.4 framework” support on Premium plans
SMBs and mid-market sites that want transparent, self-serve pricing
Didomi
Custom quote, tiered by Monthly Unique Visitors (MUV)
Quote-based (no public price)
Confirms it rolled out TCF v2.3 compliance automatically ahead of the Feb 28, 2026 deadline; has published TCF v2.4 guidance
Publishers and broadcasters needing multi-regulation plus CTV/mobile consent in one suite
If you need transparent, self-serve pricing you can budget against today, Cookiebot (sold under the Usercentrics brand) is the only one of the three that publishes real numbers. OneTrust and Didomi are both enterprise, quote-based platforms aimed at organizations that need the CMP bundled with broader privacy or risk tooling — OneTrust leans toward large enterprises consolidating privacy programs, Didomi toward publishers and broadcasters juggling web, app, and CTV consent under multiple regulations at once.
What a Consent Management Platform Actually Does for Ad Compliance
A consent management platform (CMP) shows the cookie/tracking banner, records what a visitor agreed to, and — for programmatic advertising — encodes that decision into a Transparency & Consent (TC) string that ad exchanges and demand-side platforms read before they bid. That encoding follows IAB Europe’s Transparency & Consent Framework (TCF), the industry-wide standard most European programmatic buyers rely on to know which vendors have a legal basis to process a given user’s data.
It’s worth being precise about which TCF version actually applies right now, because the framework has moved twice since the “v2.2” baseline most marketing materials still reference. IAB Europe’s own site confirms TCF v2.2 launched May 16, 2023; v2.3 followed in April 2025 with an adoption deadline of February 28, 2026; and TCF v2.4 (under Policies v5.0.b) was published July 23, 2026, with a web implementation deadline of October 23, 2026 — a date that has already passed as of this writing. In practice, a CMP that only mentions “TCF v2.2” today is describing a superseded baseline, not what ad exchanges currently require.
Pricing Breakdown
Platform
Tier
Price
Limits
OneTrust
CMP Base / Suite
Custom quote
Priced by average daily visitors aggregated across channels and properties, per OneTrust’s own pricing page
Cookiebot
Free
$0
Up to 50 subpages, 1 domain; initial + monthly scans, no banner customization listed
Premium Lite
$10/month
Up to 50 subpages, 1 domain, full Premium feature set
Premium Small
$20/month
Up to 350 subpages/domain; FAQ notes a minimum of four domains on this tier
Premium Medium
$43/month
Up to 3,500 subpages/domain
Premium Large
$70/month
Up to 7,000 subpages/domain
Premium XLarge
$120/month
More than 7,000 subpages/domain
Didomi
Essential / Advanced / Premium (All-in-One)
Custom quote
Unlimited domains scaled by Monthly Unique Visitors; SSO seat caps of 10 (Advanced) or 100 (Premium); weekly vs. monthly compliance scans
All Cookiebot Premium tiers include banner customization, 47+ languages, regional/country-targeted banners, CSV reporting exports, and the “IAB TCF 2.4 framework,” per Cookiebot’s own pricing page. Daily (rather than monthly) cookie scans cost an extra €99/month on any tier. An enterprise option, Usercentrics Advanced, is priced by session volume rather than subpages and adds unlimited domains, geotargeting, SSO, MFA, and A/B testing — but like OneTrust and Didomi, it has no public price.
Pros and Cons
OneTrust
Pros: Scans against a database of more than 45 million pre-categorized cookies/trackers, offers region-specific banners in 250+ languages, and extends consent management to mobile apps and OTT/CTV from the same console.
Pros: Bundles naturally with OneTrust’s other privacy-rights and risk modules if you’re already on the platform for broader compliance work.
Cons: No public pricing — every quote requires a sales call, which slows down evaluation for smaller teams.
Cons: Its own documentation shows TCF v2.4 rollout guidance still being finalized as of an August 2026 blog post, with exact enforcement dates flagged as “to be confirmed” even after IAB Europe had already set them.
Cookiebot (Usercentrics)
Pros: Only one of the three with transparent, published self-serve pricing, making it easy to budget for a single-site or small multi-site deployment.
Pros: Entry tiers are inexpensive ($10–$120/month) and still include full banner customization and TCF support.
Cons: Tier limits are based on “subpages” and domain counts rather than traffic, which can make capacity planning for larger, high-page-count sites less intuitive.
Cons: Enterprise-grade features (SSO, MFA, geotargeting, unlimited domains) only arrive on the custom-quote Usercentrics Advanced tier, so very large organizations lose the pricing transparency that makes the lower tiers attractive.
Didomi
Pros: Confirmed on its own blog that its CMP became fully TCF v2.3 compliant automatically ahead of the IAB’s February 28, 2026 deadline, with no console changes required from customers on web.
Pros: Modular suite (standalone CMP, CTV consent, compliance scanning, preference management, and server-side tagging via Addingwell) suits publishers that need consent handled consistently across web, app, and connected TV.
Cons: No public pricing; the “All-in-One” tiers gate meaningful features (white labelling, vendor-banner sync, preference management) behind the higher Advanced/Premium tiers, which are also quote-based.
Cons: Mobile app and CTV environments require a separate SDK update to reach full TCF v2.3 compliance — it isn’t automatic the way the web rollout was.
Who It’s a Good Fit For — and Who Should Look Elsewhere
OneTrust fits large organizations that want cookie consent to live alongside data-subject-rights and risk-management tooling under one enterprise contract, and that have the budget and procurement patience for a custom quote. Cookiebot is the better starting point for small-to-mid-size publishers or e-commerce sites that want to see a price before they talk to anyone, and don’t need mobile app or CTV consent. Didomi is built for publishers, broadcasters, and media companies juggling consent across web, native apps, and connected TV under several regulations simultaneously.
Teams that should look elsewhere: a solo site owner on a tight budget may find even Cookiebot’s Premium Small tier more than they need and should start with its Free plan or a lighter-weight CMP; and any ad-tech buyer that treats TCF v2.2 as the finish line should know that v2.3 and v2.4 compliance — not v2.2 — determine whether exchanges will actually honor the consent signal today.
Bottom Line
There’s no single “best” CMP here — the right pick depends on whether you value pricing transparency (Cookiebot), enterprise-wide privacy consolidation (OneTrust), or multi-channel publisher consent (Didomi). What all three now share is the need to keep pace with a TCF specification that has moved twice since v2.2, most recently to v2.4 with an October 23, 2026 web deadline that has already passed — so whichever platform you choose, confirm its current TCF version support directly with the vendor rather than relying on older marketing copy.
Frequently Asked Questions
Is TCF v2.2 still the current standard? No. IAB Europe’s own framework page confirms v2.3 superseded it in April 2025 (adoption deadline February 28, 2026), and v2.4 followed with specifications published July 23, 2026 and a web deadline of October 23, 2026, which has already passed.
Does Cookiebot have a free plan? Yes — its Free tier covers one domain and up to 50 subpages, with initial and monthly cookie scans, per Cookiebot’s own pricing page, though it doesn’t include banner customization or the Premium feature set.
Can I get a public price quote from OneTrust or Didomi without talking to sales? No. Both publish their pricing structure (visitor-based for OneTrust, Monthly-Unique-Visitor tiers for Didomi) but not actual figures; a sales conversation is required for a number.
Do any of these three support CTV and mobile app consent, not just web? Yes. OneTrust extends to Mobile App Consent and OTT/CTV Consent from the same platform; Didomi offers a dedicated CTV module; Cookiebot/Usercentrics’ core product is web-focused, with mobile handled via the broader Usercentrics suite.
“AI agent” has become the default label for almost any automation feature in incident management tooling, which makes it worth being precise about what each named product actually does, versus what it claims. This roundup covers five platforms — PagerDuty, incident.io, Resolve.ai, Xurrent IMR (the product formerly known as Zenduty), and BigPanda — based on what their own sites, documentation, and press releases say as of November 2026. Every performance figure below is a vendor claim or customer testimonial unless otherwise noted; none are independently benchmarked.
PagerDuty’s October 2025 “Fall ’25” release introduced what it called an end-to-end AI Agent Suite. The SRE Agent learns from related past incidents, automatically surfaces context, recommends and executes diagnostics and remediations, and generates self-updating runbooks — it was in early access at launch, with general availability projected for Q4 2025. Three other named agents round out the suite: Scribe Agent transcribes Zoom calls and chats and generates status updates in Slack or Microsoft Teams (generally available); Shift Agent automatically detects and resolves on-call scheduling conflicts (generally available); and Insights Agent gives context-aware answers from PagerDuty analytics (early access at launch). PagerDuty’s own release states that early adopters reported “up to a double-digit percentage” faster resolution times, and separately claims customers who tried the broader suite resolved incidents “up to 50% faster” — both are vendor-stated figures without published methodology, and the 50% figure applies to the suite overall rather than the SRE Agent specifically.
incident.io: From Human-Assist to Agentic Investigation
incident.io’s approach has visibly evolved. Its original 2024 AI features — an Assistant for natural-language queries over incident history, suggested incident summaries, related-incident matching, and suggested follow-ups — were explicitly framed as “exoskeletons, not robots,” assisting human responders rather than acting autonomously. Its newer Investigations feature, powered by what incident.io calls “Nexus,” goes further: when an incident is declared, it runs an automatic first-pass analysis, producing root-cause hypotheses with confidence levels, a map of affected services, and suggested next steps, then keeps re-assessing as new signals arrive. An adversarial agent reportedly challenges each hypothesis before it reaches the responder, and every hypothesis links back to its underlying sources. Notably, incident.io states Investigations makes no changes on its own in production — the only action it can take is opening a pull request for a human to review and merge. The vendor’s headline claim is getting teams “an order of magnitude faster” from alert to resolution, with no published baseline; a customer (turbopuffer’s CTO) is quoted saying it did in minutes what would otherwise take a human 30–60 minutes — a single testimonial, not a controlled benchmark.
Resolve.ai: An Agent That Investigates Before You’re Paged
Resolve.ai positions its product as an “always-on AI SRE” that joins the on-call rotation itself. Its On-Call Agent autonomously investigates alerts pulled from PagerDuty and other alerting tools, assesses severity and blast radius with supporting evidence, silences noisy alerts, can run GitHub Actions, and routes findings to the right team — ideally before a human is paged at all. Findings are delivered via Slack, Microsoft Teams, a CLI, or the Resolve.ai interface itself. The vendor describes guardrails distinguishing actions agents can take autonomously from those requiring human approval, and says engineer corrections to agent findings are retained as reusable knowledge. Resolve.ai integrates with Datadog, Grafana, Prometheus, and OpenTelemetry-based observability stacks. Customer-stated outcomes include DoorDash’s Shahrooz Ansari saying investigations moved “from hours to minutes” in many incidents, and Coinbase’s Angelo Marletta citing root causes surfaced “72% faster” than their own teams achieved — both single-customer testimonials rather than independently audited metrics, and Resolve.ai does not publish a standardized time-to-resolution benchmark of its own.
Xurrent IMR (Formerly Zenduty): A Notable Industry Consolidation
Worth flagging on its own: Xurrent acquired Zenduty in February 2025, and Zenduty has since been rebranded as Xurrent IMR (Incident Management and Response). The combined product’s named AI features include Sera, described as an “AI SRE teammate” that reads alert payloads, finds similar past incidents, and pulls related postmortems and Slack threads when triggered from an incident channel; an AI Querier for natural-language questions about impacted services; an AI Postmortem Generator that drafts postmortems from logs, metrics, and chat history against a chosen template; an AI Scheduling Assistant; and AI-powered alert correlation. On outcomes, Xurrent cites specific customer figures rather than only generic claims: Pima Community College reports a 49% reduction in MTTR and alerted 34,000 users during outages; PopClub reports critical alerts reaching the service owner in under a minute with P0 acknowledgment in 10–15 minutes; and Bajaj Finserv Health reports monthly reporting time cut from three hours to zero, with incidents acknowledged in under five minutes. These are customer-attributed case-study figures published by the vendor, not independently verified.
BigPanda: Correlation-First AIOps
BigPanda’s framing is closer to classic AIOps than to an autonomous agent acting on infrastructure. Its platform applies AI-driven correlation across observability data, service desk activity, and external dependency data to group related alerts and cut noise, supported by what it calls an “IT Knowledge Graph” unifying observability, ITSM, and organizational data for root-cause analysis. Named AI components include an L1 Agent that analyzes and assigns incidents using AI reasoning for Level-1 triage workflows, an AI Incident Assistant covering natural-language investigation and automated incident-channel collaboration, and AI Detection and Response, which gathers triage insights from service desk activity, change data, and observability sources. Unlike Resolve.ai or PagerDuty’s SRE Agent, BigPanda’s own product page doesn’t describe its agents directly executing remediations — response is framed as surfacing runbooks and historical resolutions and escalating when necessary. BigPanda’s page gives no quantified MTTR or alert-noise-reduction figures; customer quotes are qualitative (IHG cites “much faster” detection time; NYSE describes no longer manually combing through thousands of alerts), with the $250 billion figure on the page describing industry-wide manual IT operations spend, not a BigPanda-specific result.
Trade-offs at a Glance
Platform
Autonomy Level
Human-in-the-Loop Control
Primary Integration Focus
PagerDuty
Executes diagnostics/remediations; GA status still rolling out per agent
Guardrails per agent; human review of runbooks
Native PagerDuty ecosystem, Slack/Teams, MCP server
incident.io
Investigates and hypothesizes; cannot change production directly
Correlates and triages; surfaces (doesn’t execute) remediation
Human executes fixes; agent escalates when needed
CMDB, ITSM, observability, topology data
Bottom Line
Every platform here uses the word “agent,” but they sit at different points on the autonomy spectrum. PagerDuty and Xurrent IMR lean toward broad agent suites covering investigation, communication, and scheduling. incident.io and Resolve.ai both emphasize investigation-first agents that stop short of touching production directly — incident.io by limiting itself to pull requests, Resolve.ai through configurable guardrails. BigPanda remains closer to traditional correlation-and-triage AIOps than to an agent that acts independently. None of the quantified outcome claims in this space — PagerDuty’s “50% faster,” Resolve.ai’s “72% faster,” Xurrent’s “49% MTTR reduction” — come from independent, cross-vendor benchmarks; they’re vendor-reported or single-customer figures, and prospective buyers should ask each vendor for methodology and a trial against their own incident history before trusting the headline number.
FAQ
Can any of these AI agents actually fix a production incident on their own, with no human involved? Based on each vendor’s own description, no — not fully autonomously in production. incident.io’s Investigations is explicit that its only direct action is opening a pull request for human review. Resolve.ai and PagerDuty’s SRE Agent can execute some diagnostics/remediations, but both describe configurable guardrails requiring human approval for higher-risk actions.
Is Zenduty still a separate product? No. Xurrent acquired Zenduty in February 2025, and the product has been rebranded as Xurrent IMR (Incident Management and Response); some of Xurrent’s own case studies still refer to the product as “Zenduty (now Xurrent IMR).”
Which platform has the most mature AI feature set as of late 2026? PagerDuty has the broadest named agent suite (four distinct agents covering diagnostics, transcription, scheduling, and analytics), though several components were still in early access as of its October 2025 announcement. incident.io’s Investigations and Resolve.ai’s On-Call Agent are both narrower but more deeply agentic in their investigation workflow specifically.
Are the vendor-reported speed improvements (e.g., “50% faster,” “72% faster”) independently verified? No. Every such figure found across these five vendors’ own sites is either a vendor-reported aggregate without published methodology or a single customer testimonial — none point to a third-party or cross-vendor benchmark.
Do these tools replace PagerDuty-style alerting, or sit on top of it? They mostly sit on top of or alongside existing alerting. Resolve.ai explicitly ingests alerts “from PagerDuty and other alerting tools” rather than replacing them, and BigPanda’s correlation layer is designed to reduce noise from existing monitoring and ITSM tools rather than replace them outright.
AI coding assistants write code fast — that part isn’t in dispute. What’s less settled is what that code looks like six months later, after it’s been merged, extended, and handed off to someone who didn’t write it. A handful of named studies have tried to measure this directly, and their findings don’t fully agree with each other. This piece sticks to what those studies actually say, including where they conflict.
At a Glance
Source
Scope
Headline Finding
GitClear, “Coding on Copilot” (2024)
~153 million changed lines, Jan 2020–Dec 2023
Code churn projected to double in 2024 vs. the 2021 pre-AI baseline
GitClear, “AI Copilot Code Quality” (2025)
211 million changed lines, Jan 2020–Dec 2024, enterprise repos
Copy-pasted (“cloned”) code rose from 8.3% to 12.3% of changed lines (2021→2024); moved (reused) code fell from 25% to under 10%
Xiao et al., “Self-Admitted GenAI Usage in Open-Source Software” (arXiv, 2025)
151 repositories with explicit AI-usage mentions
Found no general increase in churn; disputes GitClear’s churn-quality link directly
41% higher bug rate for developers with Copilot access; no measurable throughput gain
Yetiştiren et al., arXiv 2304.10778
HumanEval benchmark, 3 AI tools compared
Copilot: 46.3% correct-code rate; ~9.1 minutes of estimated technical debt per generated snippet
The Productivity Story Everyone Already Knows
Most of the public conversation about AI coding assistants centers on speed: how much faster developers ship code with GitHub Copilot, Cursor, or similar tools. Stack Overflow’s 2024 Developer Survey — cited in GitClear’s own 2025 report — found that 63% of professional developers already used AI tools in their development process, with another 14% planning to. That adoption curve is real. What’s less discussed is whether the code those tools produce is as easy to live with later as the code it replaces.
What GitClear’s Data Actually Shows
GitClear, a code analytics vendor, has published two widely cited reports built from large commit datasets. The 2024 report (“Coding on Copilot: 2023 Data Suggests Downward Pressure on Code Quality”) analyzed roughly 153 million changed lines of code from January 2020 through December 2023 and defined churn as the percentage of lines reverted or updated within two weeks of being authored. Its headline projection: churn was expected to double in 2024 relative to the 2021 pre-AI baseline. The report did not publish exact churn percentages, only this doubling projection.
The 2025 follow-up (“AI Copilot Code Quality: 2025 Data Suggests 4x Growth in Code Clones”) expanded the dataset to 211 million changed lines from repositories owned by large enterprises, covering 2020–2024. Its most specific finding: copy-pasted (“cloned”) code rose from 8.3% of changed lines in 2021 to 12.3% in 2024, while “moved” code — lines relocated and reused rather than duplicated — fell from 25% to under 10% of changed lines over the same period. For the first time in GitClear’s dataset, copy/paste code volume exceeded moved code volume. The report frames this as evidence that AI-assisted development leans toward duplicating logic rather than refactoring it into something reusable.
The Academic Pushback
Not every study agrees with GitClear’s churn framing, and it’s worth being upfront about that disagreement rather than treating GitClear’s conclusion as settled fact. A 2025 arXiv paper, “Self-Admitted GenAI Usage in Open-Source Software” by Tao Xiao, Youmei Fan, Fabio Calefato, Christoph Treude, Raula Gaikovina Kula, Hideaki Hata, and Sebastian Baltes, specifically tested GitClear’s 2024 claim that rising churn signals downward pressure on code quality — and its data didn’t support it. Looking at 151 repositories with explicit, self-admitted mentions of GenAI tool usage (in commit messages, comments, or docs), the authors found average file-based churn actually fell from 0.17 to 0.06 after AI adoption (a medium effect size), and line-based churn fell from 0.68 to 0.50 (a negligible effect). Of the repositories showing statistically significant churn trend changes, only a minority trended upward faster; some trended downward. The one nuance that did hold up: “generation” tasks — producing new code, test data, or regular expressions — showed more rework-proneness than optimization or maintenance tasks using AI.
The two studies used different populations (GitClear: broad enterprise commit history; Xiao et al.: a curated set of repos where developers explicitly admitted to using AI) and somewhat different churn definitions, which may partly explain the divergence. The honest takeaway is that the “AI increases churn” claim is contested in the literature, even though it’s often repeated as settled.
Where the Duplication Concern Holds Up Better
Unlike churn, GitClear’s duplication findings haven’t been directly contradicted by the academic paper above — the Xiao et al. study didn’t attempt to measure code cloning itself, and cites GitClear’s duplication figures only for context rather than disputing them. That leaves the copy-paste trend as the better-supported half of GitClear’s thesis so far: more code is being duplicated rather than abstracted into shared functions, which is a classic driver of long-term maintenance cost even when it doesn’t show up as “churn” in the short term.
Bug Rates: The Uplevel Finding
A separate line of evidence comes from Uplevel Data Labs, which compared 785 enterprise developers (351 with GitHub Copilot access, 434 without) across matched time windows before and after Copilot rollout. The result most often cited: developers with Copilot access had a 41% higher bug rate than the control group. Critically, the same study found no measurable improvement in PR cycle time, throughput, code complexity, or test coverage for the Copilot group — the productivity gain some teams expect didn’t show up in this dataset, even as the bug-rate increase did. Uplevel itself describes the results as observational and not causal, and the sample is limited to a specific set of enterprise customers, so it shouldn’t be read as a universal verdict on Copilot.
Code Smells and Estimated Technical Debt
A 2023 academic paper by Burak Yetiştiren, Işık Özsoy, Miray Ayerdem, and Eray Tüzün — “Evaluating the Code Quality of AI-Assisted Code Generation Tools” — benchmarked GitHub Copilot, Amazon CodeWhisperer, and ChatGPT against the HumanEval problem set. On raw correctness, ChatGPT scored highest (65.2% correct solutions), followed by Copilot (46.3%) and CodeWhisperer (31.1%). More relevant to the technical-debt question: the authors estimated technical debt in minutes required to fix code smells in the generated output, finding roughly 9.1 minutes of estimated debt per snippet for Copilot’s output, 8.9 minutes for ChatGPT, and 5.6 minutes for CodeWhisperer. These are small, synthetic benchmark tasks rather than production codebases, so the absolute numbers don’t generalize directly — but they corroborate the broader pattern: AI-generated code frequently compiles and often passes tests, while still carrying maintainability costs that static analysis can detect.
Trade-offs at a Glance
Dimension
What the evidence suggests
Confidence
Code duplication / cloning
Rising — GitClear’s 2024→2025 reports; not directly disputed in the literature reviewed
Moderate
Code churn
Contested — GitClear projects an increase; Xiao et al.’s academic re-analysis found no general increase
Low / disputed
Bug rates
Higher in one controlled enterprise study (Uplevel, +41%), but observational and not causal
Moderate, single study
Code-smell debt per snippet
Measurable in benchmark tasks (Yetiştiren et al.), magnitude varies by tool
Moderate, synthetic benchmark
What This Means for Engineering Teams
None of this research supports banning AI coding assistants, and none of it supports treating their output as consequence-free either. The pattern that recurs across sources — duplication trending up, code-smell debt showing up in generated snippets, and at least one controlled study linking Copilot access to higher bug rates — points toward the same practical response regardless of which specific churn number you believe: keep human code review mandatory for AI-assisted PRs, track duplication metrics (not just lint and test pass rates) in CI, and budget refactoring time explicitly rather than assuming velocity gains are free. Teams that treat AI-generated code as a first draft requiring the same scrutiny as a junior engineer’s PR are acting on the strongest part of the evidence; teams that treat it as reviewed-grade output are relying on the weakest part.
Bottom Line
The claim that AI coding assistants universally degrade code quality is not as settled as it’s often presented — GitClear’s churn-doubling projection has been directly challenged by a peer-reviewed-adjacent academic re-analysis using a different (if smaller) dataset. What’s better supported across sources is a duplication problem: more copy-pasted code, less refactored reuse, and measurable code-smell debt in AI-generated snippets, plus at least one controlled study tying Copilot access to a meaningfully higher bug rate without a matching productivity gain. Read any single statistic in this space with its sample size and methodology attached, not as a universal law.
FAQ
Does AI-generated code definitely increase technical debt? Not definitively. GitClear’s reports argue that duplication is rising and churn is increasing; a 2025 academic re-analysis specifically disputes the churn claim using a different dataset. The duplication trend is less contested than the churn trend.
What is “code churn” and why does it matter? GitClear defines churn as the percentage of lines reverted or updated within two weeks of being written — a proxy for how often code needs immediate rework, which can indicate rushed or low-confidence changes.
Is the 41% higher bug rate from the Uplevel study reliable? It comes from a specific, named study (785 developers across several enterprise customers, comparing before/after Copilot access) and the authors themselves describe it as observational, not causal, and limited to their sample. It’s a real data point, not a universal benchmark.
Which AI coding tool produces the fewest code smells? In the Yetiştiren et al. HumanEval benchmark, Amazon CodeWhisperer had the lowest estimated technical debt per snippet (5.6 minutes) versus Copilot (9.1 minutes) and ChatGPT (8.9 minutes) — but CodeWhisperer also had the lowest correctness rate (31.1%), so lower estimated debt didn’t mean better overall output.
Should teams stop using AI coding assistants based on this research? The research reviewed here doesn’t support that conclusion — it supports treating AI-generated code with the same review rigor as any other untrusted first draft, and tracking duplication and churn metrics rather than assuming velocity gains come free.
GitHub still dominates developer mindshare, but it isn’t the only serious option for hosting Git repositories in 2026. GitLab, Bitbucket, and Gitea each take a different approach to pricing, self-hosting, and built-in CI/CD — and the right choice depends heavily on whether you want an all-in-one DevOps platform, tight Jira integration, or a lightweight server you fully control. This comparison sticks to verified, vendor-published figures as of November 2026.
Community Edition (CE) — free, MIT-licensed, unlimited users
$29/user/month (Premium, billed annually)
400 min/month on GitLab.com
Bitbucket Cloud
Deep Jira/Confluence integration
Bitbucket Data Center (separate product, custom/annual licensing)
$3.65/user/month (Standard)
50 min/month
Gitea
Lightweight, low-footprint self-hosting
Open Source edition — free, MIT-licensed, unlimited users
$9.50 or $19/user/month (Enterprise, self-managed; exact current rate unclear on vendor page)
No vendor cap — you supply your own Actions runners
Short Verdict
If you want one platform that bundles source control, CI/CD, and security scanning with a credible free self-managed tier, GitLab is the strongest all-rounder. If your team already lives in Jira and Confluence, Bitbucket Cloud‘s native Atlassian integration and low per-seat price make it hard to beat for that specific use case. If you want the smallest possible self-hosted footprint — a single Go binary, minimal resource usage, and no mandatory subscription — Gitea is purpose-built for that job, with Gitea Actions now offering GitHub Actions-compatible CI/CD.
GitLab: The All-in-One DevOps Platform
GitLab is positioned less as “a place to put your Git repos” and more as a full DevOps platform: source control, CI/CD pipelines, container registry, and security scanning live under one roof. Its biggest differentiator versus GitHub and Bitbucket is GitLab Community Edition (CE), which is free and open source under the MIT License and can be self-hosted with unlimited users — there’s no per-seat fee for the core, self-managed product. Paid tiers (Premium and Ultimate) are available both on GitLab.com (the SaaS offering) and as self-managed deployments, layering in advanced CI/CD controls, compliance and governance features, and — at the Ultimate tier — application security testing and vulnerability management.
Bitbucket Cloud: Built for Atlassian Shops
Bitbucket Cloud is Atlassian’s hosted Git service, and its core appeal is how tightly it threads into Jira, Confluence, and the rest of the Atlassian suite — branch-to-issue linking, smart commits, and deployment tracking tied directly to Jira tickets. Atlassian has been steadily consolidating around the cloud product: it ended support for Bitbucket Server on February 15, 2024 (Data Center licenses ran until March 19, 2024 for that specific version). Bitbucket Data Center still exists today as a self-managed option for enterprises with on-premises requirements, but it’s sold and licensed separately from Bitbucket Cloud’s self-serve plans, with pricing arranged through Atlassian directly rather than published on the standard pricing page.
Gitea: The Lightweight Self-Hosted Option
Gitea describes itself as “Git with a cup of tea” — a self-hosted DevOps platform that bundles Git hosting, code review, a package registry, and CI/CD into a small, resource-efficient package. The Open Source edition is free under the MIT license, supports unlimited users and repositories, and runs on Linux, Windows, macOS, FreeBSD, and Kubernetes, backed by SQLite, MySQL, PostgreSQL, TiDB, or MS SQL. For teams that want managed support, Gitea also sells an Enterprise self-managed tier — the pricing page lists two figures, $9.50 and $19 per user/month, without clearly stating which currently applies, so it’s worth confirming directly with Gitea before budgeting. There’s also a Gitea Cloud managed offering in preview-style rollout, but Gitea hasn’t published its pricing. CI/CD comes via Gitea Actions, which uses YAML workflow syntax designed for compatibility with GitHub Actions, including the ability to reuse many existing GitHub Actions workflows — though you still need to run your own Gitea Runner infrastructure.
Pricing Breakdown
Platform
Tier
Price
Key Limits / Inclusions
GitLab
Free
$0
5 users per top-level private group on GitLab.com; 400 CI/CD minutes/month; 10 GiB storage. Self-managed CE: unlimited users, no license fee.
GitLab
Premium
$29/user/month, billed annually (GitLab.com and self-managed)
Unlimited licensed users; 10,000 CI/CD minutes/month on GitLab.com; 500 GiB storage; advanced CI/CD and project management; $12/user/month of GitLab Credits currently included as a promotional offer.
GitLab
Ultimate
Custom pricing — not published
50,000 CI/CD minutes/month on GitLab.com; adds application security testing, supply chain security, and compliance/governance.
Bitbucket Cloud
Free
$0
Up to 5 users; unlimited public/private repos; 1 GB Git LFS storage; 50 Pipelines build minutes/month.
Bitbucket Cloud
Standard
$3.65/user/month
2,500 Pipelines build minutes/month; option to buy extra LFS and Pipelines allowances.
Note: build-minute multipliers matter. On Bitbucket, minutes are shared across the whole workspace and scale with runner size — a 5-minute step on a 2x runner counts as 10 minutes against your allowance, and extra capacity costs $10/month per 1,000 minutes or 100 GB. GitLab’s and Gitea’s self-managed CI/CD runs on infrastructure you control, so there’s no vendor-imposed minute cap at all — your only ceiling is your own compute budget.
Pros and Cons
GitLab
Pro: genuinely free, open-source self-managed CE with no seat limit
Pro: CI/CD, container registry, and security scanning built in, not bolted on
Con: Ultimate pricing is opaque — you have to talk to sales
Con: the full feature set can feel heavy for small teams that just want Git hosting
Bitbucket Cloud
Pro: lowest paid entry price of the three ($3.65/user/month)
Pro: unmatched integration depth with Jira and Confluence
Con: free-tier Pipelines minutes (50/month) are thin compared to GitLab’s 400
Con: self-managed Bitbucket Server is dead; Data Center remains but isn’t self-serve priced
Gitea
Pro: smallest resource footprint — runs comfortably on a Raspberry Pi-class server
Pro: Actions workflows designed to be compatible with existing GitHub Actions YAML
Con: no vendor-hosted SaaS tier with published pricing (Gitea Cloud pricing isn’t public)
Con: Enterprise pricing is listed inconsistently on the vendor’s own page
Who It’s a Good Fit For
GitLab fits teams that want to consolidate SCM, CI/CD, and AppSec tooling under one platform and value having a no-cost, no-seat-limit self-managed fallback.
Bitbucket Cloud fits organizations already standardized on Jira and Confluence, where workflow continuity matters more than CI/CD minute allowances.
Gitea fits small teams, homelabs, and infrastructure-conscious engineers who want full control over a minimal self-hosted Git server without a mandatory subscription.
Who Should Look Elsewhere
Teams needing a fully-supported, self-serve priced on-prem option today may find Bitbucket’s Data Center-only path to self-hosting frustrating compared to GitLab CE’s plug-and-play free tier.
Teams that need a managed cloud SLA with transparent published pricing may find Gitea Cloud’s unpublished pricing a blocker.
Budget-constrained teams that need very high CI/CD minute allowances without managing their own runners may find GitLab’s paid tiers (10,000+ minutes) a better fit than Bitbucket’s.
Bottom Line
There’s no single “best” GitHub alternative — the right pick tracks your existing toolchain and hosting appetite. GitLab offers the most complete platform with the most generous truly-free self-managed option. Bitbucket wins on price and Atlassian-ecosystem fit but has thinned out its self-hosting story since retiring Bitbucket Server. Gitea remains the go-to for anyone who wants a Git server, not a DevOps suite, and is willing to run their own CI runners. Verify current pricing directly with each vendor before committing, since GitLab’s promotional credits and Gitea’s Enterprise pricing both carry caveats that could change.
FAQ
Is GitLab’s free self-managed edition really free forever? Yes. GitLab Community Edition is open source under the MIT License and can be self-hosted with unlimited users at no license cost. Paid tiers (Premium, Ultimate) are optional add-ons for enterprise features and support.
Does Bitbucket still offer a self-hosted option? Not in the self-serve way it used to. Atlassian ended support for Bitbucket Server on February 15, 2024. Bitbucket Data Center remains available as a separately licensed, self-managed product for enterprises with on-premises requirements, but pricing isn’t published on Atlassian’s standard pricing page.
How much does Gitea cost to run? The core Open Source edition is free and self-hosted under the MIT license with no user limit. Gitea also sells an Enterprise self-managed tier (listed at $9.50 or $19 per user/month, with the page unclear on which currently applies) and a Gitea Cloud managed offering whose pricing hasn’t been published.
Which platform gives the most free CI/CD minutes? Among hosted free tiers, GitLab.com’s Free plan includes 400 CI/CD minutes/month versus Bitbucket Cloud Free’s 50 build minutes/month. Gitea Actions has no vendor-imposed minute cap since you run your own runners.
Can I reuse my existing GitHub Actions workflows elsewhere? Gitea Actions is specifically designed for syntax compatibility with GitHub Actions, so many existing workflows can be reused with minimal changes. GitLab and Bitbucket use their own CI/CD YAML formats (.gitlab-ci.yml and bitbucket-pipelines.yml respectively), so GitHub Actions workflows generally need manual translation.
Training a frontier AI model isn’t really a chip problem anymore — it’s an interconnect problem. Once a job spans more than a few hundred GPUs, how fast those GPUs can read and write each other’s memory matters as much as how fast any single GPU can compute. Oracle’s answer is what it markets as the OCI Supercluster, and underneath the marketing language is a genuinely detailed RDMA networking design. This piece breaks down what Oracle has actually published about how that fabric works, how big it scales, and what happens when a cable flickers in the middle of a six-week training run.
At a Glance
Aspect
What Oracle Publishes
Largest single supercluster (Clos fabric)
Up to 131,072 NVIDIA Blackwell (B200) GPUs
Peak performance of that cluster
2.4 zettaFLOPS
Larger multi-datacenter system
“Zettascale10”: up to 800,000 GPUs, 16 zettaFLOPS, multigigawatt campus, first deployment in Abilene, TX
Network protocol
Custom RDMA over Converged Ethernet v2 (RoCE v2), via Oracle’s “Acceleron” NIC
Topology
Three-tier Clos fabric, 400 Gbps nonblocking per GPU
Aggregate bandwidth (131,072-GPU cluster)
52 Pbps nonblocking, at 400 Gbps per port
Cluster-network bandwidth (per OCI product page)
Up to 3,200 Gb/sec, plus a separate front-end network up to 400 Gb/sec
Latency
As low as ~2 microseconds (innermost tier) up to ~8–9.1 microseconds across the full cluster
H100, H200, B200 / GB200 NVL72, A100, L40S, plus AMD MI300X as an alternative
What a “Cluster Network” Actually Is on OCI
Oracle’s documentation describes a cluster network as a group of bare-metal HPC, GPU, or optimized instances placed in close physical proximity and connected by a Remote Direct Memory Access (RDMA) network, with latency Oracle says is comparable to an on-premises HPC cluster. There are two ways to build one. “Cluster networks with instance pools” manage a group of identical instances together, which suits predictable, fixed-size capacity. “Compute clusters” instead start as an empty RDMA network group that you populate and depopulate instance by instance — useful when you want to mix instance types or manage nodes independently.
Layered on top of (not instead of) a compute cluster is what Oracle calls a GPU memory cluster: a group of instances that share a single GPU memory fabric domain, running in a hardware-isolated environment, which Oracle describes as turning a set of GPUs into “a single AI supercomputer.” Getting this working on a given bare-metal shape — Oracle lists shapes including BM.GPU.H100.8, BM.GPU.A100, BM.GPU4.8, BM.HPC2.36, and BM.Optimized3.36 — depends on the Oracle Cloud Agent’s HPC plugin, which handles three jobs automatically: configuring the Mellanox ConnectX network adapters correctly, authenticating and tuning RDMA interfaces (including QoS and MTU settings), and emitting the additional RDMA and GPU performance metrics engineers need to see what the fabric is actually doing.
Inside the Fabric: RoCE v2 and the Acceleron NIC
RDMA’s core trick is letting one server read or write another server’s memory directly, bypassing the operating system kernel and most of the CPU overhead that ordinary TCP/IP networking requires — which is exactly why HPC and AI training clusters use it instead of standard data-center networking. The traditional way to deliver RDMA at scale is InfiniBand, and Oracle’s literature on its largest, multi-datacenter Zettascale10 system does reference InfiniBand-based networking as part of the design. But the documented fabric behind Oracle’s mainstream Supercluster product — the one that scales to 131,072 GPUs — is Oracle’s own custom implementation of RDMA over Converged Ethernet v2 (RoCE v2), running over NVIDIA ConnectX network interface cards and data processing units (DPUs) for hardware-accelerated packet handling.
Oracle markets this specific implementation as the Acceleron RoCE Network Fabric. Its distinguishing design choice is that each GPU’s network interface card carries its own onboard four-port Ethernet switch, letting a single GPU fan out to several upstream switches simultaneously rather than relying on one uplink. The result, per Oracle, is a flatter network built from multiple isolated “planes” — any one of which can be taken offline for maintenance without disrupting the others — and fewer switch hops between any two GPUs, which directly lowers latency. Oracle also says Acceleron carries line-rate encryption and enforces what it calls Zero Trust Packet Routing (ZPR): a security policy enforced at every NIC that can, for example, block a running workload from reaching object storage over the public internet, as a guard against data exfiltration from a compromised training job. Oracle’s own comparison claims up to 2x more networking capacity and up to 2x more storage IOPS versus its prior-generation fabric — a vendor-stated figure that Oracle does not benchmark against a named competitor.
The Three-Tier Clos Network and Its Latency Budget
The fabric behind Oracle’s largest documented single supercluster is a three-tier Clos topology — a multi-stage, leaf-and-spine-style design common in hyperscale networks specifically because it can be built nonblocking, meaning no two GPUs have to compete for the same internal link just because of where they happen to sit. Oracle scales this design to up to 131,072 NVIDIA Blackwell GPUs, each with its own dedicated, nonblocking 400 Gbps port. The three tiers have distinct latency and reach:
Tier 1: up to 256 GPUs, roughly 2 microseconds of unidirectional latency
Tier 2: up to 2,048 GPUs, roughly 5 microseconds
Tier 3 (the full cluster): up to 131,072 GPUs, roughly 8 microseconds
Two engineering details explain how Oracle holds those numbers. First, the physical cable run from a GPU to its first-hop switch is capped at 40 meters, which keeps fiber-propagation delay — about 5 nanoseconds per meter — small relative to switching time. Second, the switch ASICs themselves are tuned to a latency budget under 1 microsecond, typically around 900 nanoseconds, by keeping routing and switching state in fast SRAM and TCAM memory rather than falling back to slower DRAM or HBM lookups. Aggregated across the full 131,072-GPU cluster, Oracle states the fabric delivers 52 petabits per second of nonblocking bandwidth at 400 Gbps per port. Separately, Oracle’s general Supercluster product page cites up to 3,200 Gb/sec of cluster-network bandwidth per node, plus an independent front-end network of up to 400 Gb/sec reserved for storage and management traffic, so ordinary I/O doesn’t compete with GPU-to-GPU chatter. Oracle also claims this adds up to 5x the network bandwidth and up to 5x lower latency than unnamed competing clouds — a marketing claim worth flagging as unverified rather than an independently benchmarked figure.
Keeping the Fabric Alive at 131,000-GPU Scale
Raw bandwidth and topology are only half the story; the other half is keeping six-figure-GPU jobs from stalling on congestion or a single bad cable. Classic RoCE deployments lean on Priority Flow Control (PFC) to avoid dropped packets, but PFC can cascade into head-of-line blocking across an entire fabric when one slow receiver backs up traffic for everyone behind it. Oracle’s network instead treats congestion control as the primary mechanism at every layer of the fabric, and separates traffic into distinct classes — so GenAI collective-communication traffic and HPC-MPI traffic each get their own quality of service rather than starving one another.
On top of that, Oracle runs what it calls intelligent GPU placement, which keeps a given customer’s leased GPUs physically close together in the topology to reduce latency and the odds of competing flows colliding, backed by a “network locality service” that exposes topology information to job schedulers so bandwidth-heavy work stays within a faster, lower tier instead of spilling across the entire Tier-3 fabric. Standard equal-cost multi-path (ECMP) routing — the default way most networks spread traffic across redundant links — has no awareness of how AI collective operations like all-reduce actually move data, so it can route several heavy flows onto the same path and collide. Oracle says it built, together with an unnamed switch vendor, “collectives-aware load balancing” that understands these ML traffic patterns and spreads them deliberately to avoid that.
Failure handling is its own discipline at this scale. On a 400G link, as few as three uncorrectable forward-error-correction block errors within about 20 nanoseconds can force the link down, and recovering from a flap typically costs 10 to 15 seconds while every layer — PMD, PMA, FEC, PCS, MAC, and IP — retrains and routing protocols like BGP or OSPF reconverge. At cluster scale, that’s meaningful lost training time, repeated across thousands of links. Oracle’s mitigations include “link debounce,” which keeps upper network layers up through brief optical interruptions without forcing a reroute; predictive monitoring that flags “repeat offender” cables and optics for automatic traffic rerouting and physical repair; and a GPU-hosted Oracle Cloud Agent that watches for host-side link and environmental anomalies.
Beyond One Cluster: Zettascale10
A single 131,072-GPU, 2.4-zettaFLOPS supercluster is itself only one building block of what Oracle, at Oracle AI World, branded Zettascale10: a system spanning multiple data centers, tied together by Oracle’s RoCE- and InfiniBand-based networks plus high-capacity fiber links between sites, rated at 16 zettaFLOPS and scaling to as many as 800,000 Nvidia GPUs inside a “multigigawatt” campus. The first such deployment is sited in Abilene, Texas. Oracle EVP Mahesh Thiagarajan framed the goal around efficiency rather than raw GPU count, stating that customers can “build, train, and deploy their largest AI models into production using less power per unit of performance.” Oracle has not published how the 131,072-GPU Clos fabric nests inside that larger multi-datacenter figure, nor site-level power specifics beyond the “multigigawatt” description — a real gap in an otherwise detailed set of disclosures.
Supercluster Size by GPU Generation
GPU / Accelerator
Max GPUs per Single OCI Supercluster (Oracle-published)
NVIDIA L40S
3,840
NVIDIA H100
16,384
AMD MI300X
16,384
NVIDIA A100
32,768
NVIDIA H200
65,536
NVIDIA GB200 NVL72 Superchips
More than 100,000
NVIDIA B200 (Blackwell)
Up to 131,072
Bottom Line
Oracle’s Supercluster pitch is ultimately a networking story dressed up as a GPU-count story. The headline numbers — 131,072 Blackwell GPUs, 800,000 GPUs under Zettascale10 — are the visible tip of a fabric built from custom Ethernet NICs with onboard switches, a carefully latency-budgeted three-tier Clos topology, and a fairly unusual amount of published detail on how Oracle keeps that fabric from falling over under real-world link failures. Whether it actually beats InfiniBand-based alternatives from other clouds in practice is something Oracle’s own marketing claims rather than something this piece can independently verify — but the underlying engineering choices are real, documented, and more specific than most cloud providers publish about their own AI networking.
FAQ
Is OCI’s Supercluster fabric InfiniBand or Ethernet? Oracle’s documented, Acceleron-based Clos fabric that scales to 131,072 GPUs runs RoCE v2 over Ethernet. Oracle’s larger, multi-datacenter Zettascale10 system references both RoCE- and InfiniBand-based networking, but Oracle hasn’t published a diagram reconciling exactly which links use which protocol.
What does RDMA actually buy you over ordinary networking? It lets one server read or write another’s memory directly, skipping most OS kernel and CPU overhead — which is why single-digit-microsecond, kernel-bypass communication is achievable at all between tens of thousands of GPUs.
Does every OCI customer get a full 131,072-GPU cluster? No — these are Oracle’s published maximum platform-scale figures, not a guaranteed allocation size for any individual customer.
Does Oracle charge extra for RDMA bandwidth? Oracle states that RDMA capability, block storage, and the published cluster-network bandwidth carry no additional charge beyond the compute shape’s price, and that the first 10 TB of monthly egress is free.
How does this compare to Nvidia’s own networking stack? Oracle builds its superclusters on Nvidia GPU and Superchip hardware (including GB200 NVL72), but layers its own custom RoCE v2 fabric — Acceleron — on top, rather than adopting Nvidia’s InfiniBand/Spectrum-X networking stack end-to-end.
Internal tools — admin panels, support dashboards, ops consoles — are the kind of software every engineering team needs and almost none wants to build from scratch. Retool, Appsmith, and Budibase have all grown up around that gap, but they come from genuinely different starting philosophies: one is a commercial, cloud-first product with an enterprise self-hosting tier; the other two are open-source platforms first, with hosted cloud plans layered on top.
At a Glance
Platform
Entry Price
Self-Hosting
License
Retool
Free for up to 5 users; Team from $10/builder + $5/user per month (billed annually)
Enterprise plan only (self-hosted or air-gapped, in your own VPC)
Proprietary, commercial product
Appsmith
Free (Community edition, self-hosted or cloud, up to 5 users); Business from $15/user/month
Available on every tier, including free Community
Apache 2.0 (open-source core)
Budibase
Free, unlimited, self-hosted open-source edition; Cloud Pro from $19/month
Available for free on the open-source edition
GPL v3 (core); client/components under MPL; paid features under BSL
Short Verdict
If budget allows and you want a polished, managed product with strong AI-assisted app generation, Retool’s cloud plans remain the most capable out of the box, but self-hosting is locked behind its Enterprise tier. If self-hosting from day one matters — for compliance, cost, or control — Appsmith and Budibase are both genuinely free and open-source at the core, with Budibase leaning more toward workflow/automation-heavy internal apps and Appsmith leaning toward a broader library of UI widgets and integrations.
Overview
Retool is a commercial, proprietary low-code platform for building internal software by dragging in pre-built UI components and wiring them to databases, REST APIs, and internal services. It is not open-source. Its free and mid-tier plans run only on Retool’s own cloud; self-hosting — in your own VPC via Docker, or fully air-gapped — is reserved for the Enterprise plan. Retool has also leaned heavily into AI: its pricing page describes an AI-native app builder that generates a working starting app from a description, plus a pool of monthly “AI credits” for app-building and AI Actions, and separately billed AI “Agents.”
Appsmith is an open-source low-code platform (Apache 2.0 licensed, confirmed on its GitHub repository) that you can self-host for free from day one, or run on Appsmith’s managed cloud. The free Community tier includes up to 5 users, Git-based version control with a limited number of repositories, and basic role-based access. Paid Business and Enterprise tiers add things like unlimited users, custom roles, audit logs, SAML/OIDC SSO, and managed/air-gapped hosting add-ons.
Budibase is also open-source (GPL v3 for the core, confirmed on its GitHub README, with client/component libraries under MPL and paid-only features under a Business Source License). Its self-hosted open-source edition is free and, notably, imposes no user limits — unlimited creators and end users are listed even on the free self-hosted tier. Budibase’s cloud plans are metered by monthly “actions” (automation runs, AI agent calls, and database writes) rather than purely by seat, which is a different pricing axis than either Retool or Appsmith use.
Pricing Breakdown
Tier
Retool
Appsmith
Budibase
Free / Community
$0 for up to 5 users; 250 pooled AI credits/month; cloud only, production environment only
$0 (Community), self-hosted or cloud; up to 5 users, 5 workspaces, Git with 3 repos, Google SSO
$0, self-hosted, open-source; unlimited apps/automations/users; 1-day automation log retention; community support
Mid-tier
Team: $10/builder + $5/internal user per month (billed annually); external users free up to 50, then tiered down to $4/month at scale
Business: $15/user/month; up to 99 users; unlimited environments/Git repos/workspaces; audit logs; premium integrations
A structural difference worth flagging: Retool and Appsmith both charge primarily per named user/builder, while Budibase’s cloud plans charge a flat platform fee plus a metered “actions” allowance that scales by tier, with end users and extra creators billed as separate add-ons on top.
Pros and Cons
Retool
Pro: Deep library of pre-built components and the most mature AI app-generation feature of the three, per its own pricing page.
Pro: Free tier is genuinely usable for small teams (5 users, unlimited apps).
Con: Not open-source; self-hosting requires an Enterprise contract, which is a significant jump from the Team/Business tiers.
Con: Internal-user pricing compounds quickly for larger teams since both builders and non-builder internal users are billed per seat.
Appsmith
Pro: Self-hosting is available for free from the Community tier — no paid plan required to run it on your own infrastructure.
Pro: Apache 2.0 license gives maximum flexibility to fork, modify, or embed.
Con: Free tier caps out at 5 users; scaling past that means jumping to the $15/user Business tier.
Con: Enterprise pricing ($2,500/month for 100 users) is a steep step up from Business.
Budibase
Pro: The free self-hosted edition has no listed user cap — unlimited creators and end users, which is unusual among the three.
Pro: Action-based metering can be cheaper than per-seat pricing for small teams with many viewers and few builders.
Con: GPL v3 licensing is more restrictive for companies that want to embed or redistribute modified code than Appsmith’s Apache 2.0.
Con: Cloud action limits (e.g. on the Pro and Premium tiers) can be reached quickly by automation-heavy apps, forcing an upgrade.
Who It’s a Good Fit For
Retool: Teams with budget for a managed product, who want polished components and AI-assisted app generation, and who either stay small (under 5 users) or are prepared to eventually negotiate an Enterprise contract for self-hosting.
Appsmith: Teams that want to self-host from day one without paying anything, and value a permissive open-source license (Apache 2.0) for internal or embedded use.
Budibase: Teams building automation- and workflow-heavy internal apps with many viewers relative to builders, or anyone who wants an uncapped free self-hosted tier.
Who Should Look Elsewhere
Retool: Teams that need self-hosting but can’t justify an Enterprise contract — there’s no self-hosted option on Team or Business.
Appsmith: Teams that need more than 99 users but aren’t ready for a custom Enterprise negotiation, since Business tops out there.
Budibase: Teams with GPL-incompatible legal requirements around the self-hosted core, or heavy automation usage that will blow through cloud action limits on lower tiers.
Bottom Line
There’s no universally “best” choice here — the decision mostly comes down to whether self-hosting on day one matters more than a managed, AI-forward product experience. Appsmith and Budibase both remove the cost barrier to self-hosting entirely via open-source licenses (Apache 2.0 and GPL v3, respectively), while Retool keeps self-hosting as an Enterprise-only perk behind its otherwise more polished cloud product. Teams should weigh per-seat pricing (Retool, Appsmith) against metered-action pricing (Budibase) against their actual usage pattern — many viewers and few builders favors Budibase’s model; many builders favors per-seat pricing.
FAQ
Is Retool really free? Yes, for up to 5 users on Retool Cloud, with unlimited apps and a monthly pool of 250 AI credits — but the free tier doesn’t include self-hosting, SSO, audit logs, or granular roles.
Can I self-host Retool? Only on the Enterprise plan, which supports self-hosting in your own VPC or a fully air-gapped deployment; Free, Team, and Business all run exclusively on Retool’s cloud.
What license is Appsmith released under? Apache 2.0 for the open-source core, as confirmed on Appsmith’s GitHub repository — a permissive license with few restrictions on modification or embedding.
Is Budibase’s open-source edition missing key features compared to paid? It’s missing some operational features like extended log retention, enforced SSO, backups/restore, and custom branding, but the core app-building, automation, and unlimited-user capability is present in the free self-hosted edition per Budibase’s own comparison table.
Which one is best for a small startup building internal tools on a budget? Appsmith or Budibase’s self-hosted open-source editions are the only genuinely free options with no user cap pressure (Budibase) or a usable 5-user cap (Appsmith); Retool’s free tier works too but caps at 5 users with no path to free self-hosting.
Replicate the same piece of data across several machines, let each one accept writes independently — including while offline — and you have a conflict waiting to happen. Conflict-free replicated data types, or CRDTs, are a family of data structures specifically designed so that no matter what order concurrent updates arrive in, every replica ends up in the same final state, with no central coordinator and no manual conflict resolution. They were formally defined by Marc Shapiro, Nuno Preguiça, Carlos Baquero, and Marek Zawirski in a 2011 INRIA research report, and have since become the mechanism underneath a growing list of offline-first and real-time collaborative software.
At a Glance
Concept
Used By
Complexity
G-Counter / PN-Counter
Riak’s built-in Counter data type; distributed increment/decrement counters generally
State size grows linearly with the number of replicas (one slot per replica)
G-Set / OR-Set
Riak’s Set data type; Redis Enterprise’s CRDT-backed Sets in Active-Active databases
Merge is a set union/per-element tag comparison, roughly O(set size)
Sequence CRDTs (list/text)
Yjs (list-based sequence CRDT) and Automerge (JSON-like document CRDT with text/list support), used in collaborative editors
Metadata overhead scales with edit history; production libraries compact/garbage-collect it
The Problem: Why Replicas Disagree
In a system with a single server, there’s one obvious order of operations. The moment you let multiple replicas accept writes — because one device is offline, or because you’ve spread writes across regions for latency — you lose that single order. Two users might add and remove the same set element, or increment the same counter, at the “same time” from the system’s point of view. Traditional answers to this are locking (serialize writes through one node, sacrificing availability during partitions) or operational transformation, which requires a server to establish a canonical ordering of operations before broadcasting them back out. CRDTs take a third path: design the data type itself so that merging any two valid states — in any order, any number of times — always produces a deterministic, correct result.
Strong Eventual Consistency: The Guarantee CRDTs Make
CRDTs provide a property called strong eventual consistency: any two replicas that have received the same set of updates — regardless of the order they arrived in — are guaranteed to be in an identical state. This is stronger than ordinary eventual consistency, which only promises that replicas will converge eventually, not that they’ll be byte-identical the moment they’ve seen the same updates. The guarantee comes directly from the mathematical properties required of the merge function, not from any coordination between nodes.
State-Based vs. Operation-Based CRDTs
The 2011 paper describes two equivalent formulations. State-based CRDTs (CvRDTs) ship their entire current state to other replicas, which merge it into their own using a merge function that must be commutative, associative, and idempotent — meaning the order you apply merges in, and how many times you apply the same one, can’t change the result. This only requires an unreliable gossip-style transport, but shipping full state repeatedly can be expensive for large documents. Operation-based CRDTs (CmRDTs) instead broadcast the individual update operations (e.g. “add element X,” “increment by 1”), which must themselves be commutative and are usually required to arrive without duplication and in causal order. This uses much less bandwidth for small, frequent updates, but asks more of the delivery layer. Because each style can emulate the other, the choice is mostly an engineering trade-off, not a correctness one.
The Building Blocks: G-Counter, PN-Counter, G-Set, OR-Set
Most practical CRDTs are built from a small set of well-understood primitives:
G-Counter (grow-only counter): each replica tracks its own increment total in a separate slot; the counter’s value is the sum of all slots, and merging two replicas takes the element-wise maximum of each slot.
PN-Counter: pairs a G-Counter for increments with a second G-Counter for decrements; the value is increments minus decrements, which allows counters to go down as well as up.
G-Set (grow-only set): elements can be added but never removed; merging two sets is a plain union.
OR-Set (observed-remove set): each add is tagged with a unique identifier, and a remove only marks the specific tags that replica has actually observed as removed — which is what lets an element be removed and later re-added without the removal “winning” forever.
Riak’s built-in Data Types map directly onto this model: its Counter is a PN-Counter-style type, its Set and Map types use observed-remove semantics, and removing a Set or Map element requires a “context” token from a prior read — summed up in Riak’s own documentation as “you cannot remove something you haven’t seen,” which is the OR-Set rule in a sentence.
Sequence CRDTs: How Editors Merge Text
Text and lists are harder than sets or counters, because position matters: inserting a character doesn’t just add an element, it has to land in the right place relative to everyone else’s concurrent edits. Yjs is described in its own documentation as a high-performance CRDT built around a list-based sequence structure, exposing shared types like maps, arrays, and rich text that any number of clients can edit concurrently and merge without a central server resolving conflicts. Automerge takes a similar approach for JSON-like documents — a root map of keys to values, where values can be nested maps, lists, or collaborative text — and additionally keeps the full change history of a document, similar to a Git repository, so changes can be viewed, diffed, branched, and merged.
A Minimal Implementation
A G-Counter and an OR-Set are small enough to implement correctly in a few lines, and they illustrate the pattern every CRDT follows: track enough metadata that merging is just “combine and take the right side when there’s a conflict.”
class GCounter:
"""Grow-only counter CRDT: one slot per replica, merge = max per slot."""
def __init__(self, replica_id):
self.replica_id = replica_id
self.counts = {}
def increment(self, amount=1):
self.counts[self.replica_id] = self.counts.get(self.replica_id, 0) + amount
def value(self):
return sum(self.counts.values())
def merge(self, other):
for replica, count in other.counts.items():
self.counts[replica] = max(self.counts.get(replica, 0), count)
class ORSet:
"""Observed-remove set: add is tag-based, remove only affects tags seen."""
def __init__(self):
self.added = set() # (element, unique_tag) pairs
self.removed = set() # tags marked as removed
def add(self, element, tag):
self.added.add((element, tag))
def remove(self, element):
for el, tag in list(self.added):
if el == element:
self.removed.add(tag)
def contains(self, element):
return any(
el == element and tag not in self.removed
for el, tag in self.added
)
def merge(self, other):
self.added |= other.added
self.removed |= other.removed
Notice that merge in both cases is commutative and idempotent: calling it twice with the same other replica, or calling it on two replicas in either order, produces the same result either way — which is exactly the property a state-based CRDT’s merge function is required to have.
Real Systems Built on CRDTs
Redis implements CRDTs in its Active-Active geo-distribution feature (available in Redis Enterprise), where standard Redis commands are backed by CRDT-equivalent implementations so that replicas in different regions can all accept writes and converge automatically; Redis’s own engineering blog walks through its Set implementation specifically as an add-wins, observed-remove design, and notes that CRDT-backed counters can go negative during merges, making them unsuitable for values like account balances that must stay bounded. Riak, the distributed NoSQL database originally built by Basho, bakes CRDTs in as first-class “Data Types” — Counters, Sets, Maps, Registers, and Flags — specifically so application code never sees Riak’s older “sibling values” conflict model. Yjs and Automerge are the two most widely used CRDT libraries for building collaborative, local-first applications in JavaScript (and, for Automerge, Rust); Yjs ships official bindings for editors including ProseMirror, Tiptap, Monaco, Quill, and CodeMirror, and is also offered as a hosted sync service by providers like Liveblocks and Y-Sweet.
Trade-offs: CRDTs vs. the Alternatives
Approach
Coordination Needed
Conflict Handling
Best Fit
Single-writer / locking
Yes — writes block or queue on one authority
Conflicts are prevented, not resolved
Strongly consistent systems with low write concurrency
Operational Transformation
Typically needs a server to establish a canonical operation order
Concurrent operations are transformed against each other before applying
Real-time editors with a reliable, always-connected server
CRDTs
None required — any two replicas can merge directly, peer-to-peer
Deterministic, type-specific merge function (sum, union, observed-remove, etc.)
CRDTs trade a small amount of extra metadata and some constraints on what operations are allowed for a very large payoff: no central server is required for two replicas to merge correctly, even after an arbitrary amount of offline editing. That makes them the right tool whenever availability and offline support matter more than enforcing a single global order of operations — collaborative text editing, multi-region databases, and peer-to-peer sync are exactly that case. They’re the wrong tool when an operation genuinely needs cross-replica coordination to be meaningful, such as enforcing that an account balance never goes negative, which is precisely the limitation Redis calls out for its own CRDT counters.
FAQ
What does “conflict-free” actually mean here? It means the merge function is mathematically guaranteed to produce a deterministic result for any set of concurrent updates — not that concurrent edits can’t happen, but that merging them never requires a human or a server to pick a winner.
Are CRDTs the same as Operational Transformation? No. Both solve concurrent editing, but OT typically relies on a server to sequence operations before broadcasting them, while CRDTs are designed so any two replicas can merge directly, including peer-to-peer and fully offline.
Is state-based or operation-based better? Neither, categorically — they’re theoretically equivalent. State-based (CvRDT) is simpler to reason about and tolerates unreliable delivery better; operation-based (CmRDT) uses less bandwidth but needs more from the messaging layer (commutative ops, causal delivery).
Can a CRDT counter go negative unexpectedly? Yes, for PN-Counter-style implementations — Redis explicitly documents this behavior for its CRDT counters, which is why they’re unsuitable for values that must stay non-negative, like inventory or balances.
What’s the main downside of CRDTs? Metadata overhead. Tracking per-element tags (for OR-Sets) or full edit history (for sequence CRDTs like Automerge) costs memory and bandwidth that a simpler last-write-wins model wouldn’t, which is why production libraries invest heavily in compaction and compact binary encodings.
Every time a phone reroutes you around traffic, or a game character walks around a wall instead of into it, some version of the same two algorithms is running underneath. Dijkstra’s algorithm and A* (pronounced “A-star”) search are the two foundational techniques for finding the shortest path through a graph, and understanding one is mostly a matter of understanding the other with one extra idea added on top.
At a Glance
Concept
Used By
Complexity
Dijkstra’s Algorithm
Link-state network routing protocols (OSPF, IS-IS), uniform-cost search in AI, and as the base layer under many road-routing engines’ preprocessing pipelines
O((V + E) log V) with a binary heap; O(E + V log V) with a Fibonacci heap
A* Search
Game engine navigation (e.g. Unity’s NavMesh pathfinder), robotics path planning (built originally for the Shakey robot), turn-based and real-time strategy AI
O(b^d) worst case (b = branching factor, d = solution depth); reduces to Dijkstra’s bound when the heuristic is zero
Greedy Best-First Search
Fast approximate routing where a guaranteed-shortest path isn’t required
Typically faster in practice, but offers no optimality guarantee
The Problem Both Algorithms Solve
Represent a road network, a game level, or a computer network as a graph: nodes are intersections, grid cells, or routers, and edges are roads, walkable connections, or network links, each carrying a weight (distance, time, or cost). The shortest-path problem asks for the lowest-total-weight route between two nodes. That abstraction is general enough to cover GPS navigation, in-game AI movement, and internet routing with the same underlying math.
Dijkstra’s Algorithm: Growing the Known Region
Edsger Dijkstra conceived the algorithm in 1956 as a demonstration for the ARMAC computer, using a map of 64 Dutch cities, and published it in 1959. It works by maintaining a set of “settled” nodes whose shortest distance from the start is already known, and repeatedly pulling the closest not-yet-settled node out of a priority queue. For each neighbor of that node, it checks whether reaching the neighbor through the current node is cheaper than any route found so far, and updates the neighbor’s distance if so. The node is then marked settled, and the process repeats until the target is reached or the queue is empty.
The algorithm’s complexity depends entirely on how that priority queue is implemented. A simple array scan gives O(V²). A binary heap brings it to O((V + E) log V), which is efficient on sparse graphs like road networks. A Fibonacci heap, introduced by Fredman and Tarjan in 1984, gives the best known theoretical bound of O(E + V log V) — though in practice binary heaps often win anyway, because Fibonacci heaps carry larger constant-factor overhead.
A* Search: Dijkstra Plus a Heuristic
Peter Hart, Nils Nilsson, and Bertram Raphael published A* in 1968 at the Stanford Research Institute, built for the Shakey robot path-planning project. A* runs the same frontier-expansion loop as Dijkstra, but instead of ordering the queue purely by the known cost-so-far, g(n), it adds an estimate of the remaining cost to the goal, h(n), and expands nodes in order of f(n) = g(n) + h(n). That estimate — the heuristic — is what lets A* pull the search toward the goal instead of spreading evenly in every direction.
The relationship between the two algorithms is direct: Dijkstra’s algorithm is the special case of A* where h(n) is zero everywhere. Set the heuristic to zero and A* degenerates exactly into Dijkstra. Make the heuristic dominate the cost-so-far term and A* starts behaving like Greedy Best-First Search, which chases the goal fast but can commit to routes that aren’t actually shortest.
Why the Heuristic Has to Behave: Admissibility and Consistency
A heuristic is admissible if it never overestimates the true remaining cost to the goal. On a square grid where movement costs 1 per step, Manhattan distance (the sum of the absolute coordinate differences) is a standard admissible heuristic, because it can never exceed the real number of moves required. As long as the heuristic stays admissible, A* is guaranteed to find an optimal path, inheriting the same optimality guarantee Dijkstra’s algorithm already has on its own.
A stronger property, consistency (sometimes called monotonicity), requires that for every edge from x to y, h(x) ≤ cost(x, y) + h(y) — essentially a triangle inequality on the heuristic. A consistent heuristic guarantees that once a node is expanded, A* never needs to re-expand it with a better cost later, which is what makes the standard “closed set” implementation correct and efficient.
A Minimal Implementation
The two algorithms differ by exactly one term in the priority queue ordering. Here they are side by side in Python, using a binary heap via the standard library:
import heapq
def dijkstra(graph, start, goal):
g_score = {start: 0}
came_from = {start: None}
frontier = [(0, start)]
while frontier:
dist, current = heapq.heappop(frontier)
if current == goal:
break
for neighbor, weight in graph[current]:
new_dist = dist + weight
if neighbor not in g_score or new_dist < g_score[neighbor]:
g_score[neighbor] = new_dist
came_from[neighbor] = current
heapq.heappush(frontier, (new_dist, neighbor))
return g_score, came_from
def a_star(graph, start, goal, heuristic):
g_score = {start: 0}
came_from = {start: None}
frontier = [(heuristic(start, goal), start)]
while frontier:
_, current = heapq.heappop(frontier)
if current == goal:
break
for neighbor, weight in graph[current]:
new_g = g_score[current] + weight
if neighbor not in g_score or new_g < g_score[neighbor]:
g_score[neighbor] = new_g
priority = new_g + heuristic(neighbor, goal)
heapq.heappush(frontier, (priority, neighbor))
came_from[neighbor] = current
return g_score, came_from
def manhattan_heuristic(a, b):
return abs(a[0] - b[0]) + abs(a[1] - b[1])
The only structural change in a_star is that the priority pushed onto the heap is new_g + heuristic(neighbor, goal) instead of just new_dist. Everything else — the loop, the relaxation step, the path reconstruction via came_from — is identical.
Where These Algorithms Actually Run
Unity’s NavMesh system is a documented, concrete example of A* in production: Unity builds a navigation mesh of walkable convex polygons from scene geometry, then uses the A* algorithm to search outward across neighboring polygons from the start polygon to the destination polygon, producing a “corridor” the agent then steers through. Off-mesh links handle actions the mesh can’t represent, like jumping a gap, and the pathfinder treats them as valid route segments.
On the networking side, link-state routing protocols such as OSPF and IS-IS run a form of Dijkstra’s algorithm directly: every router computes shortest paths to every other router from its own local view of the network graph. Road-routing software generally keeps Dijkstra (or a close relative, uniform-cost search) as the correctness backbone, but layers heavy preprocessing on top — bidirectional search, or techniques like contraction hierarchies — because running plain Dijkstra over a continent-scale road graph on every query would be far too slow. A* itself remains the default choice in robotics and games specifically because a good spatial heuristic (straight-line or Manhattan distance to the goal) is cheap to compute and dramatically cuts down the explored search space versus Dijkstra’s undirected expansion.
Trade-offs at a Glance
Factor
Dijkstra’s Algorithm
A* Search
Optimality guarantee
Yes, always
Yes, provided the heuristic is admissible
Search direction
Expands uniformly outward from the start in all directions
Expands preferentially toward the goal
Heuristic required
No
Yes — quality of the heuristic drives performance
Best suited to
Finding shortest paths from one source to many/all destinations (e.g. routing-table computation)
Finding a path to one specific, known destination (e.g. navigation, game AI)
Worst-case complexity
O((V + E) log V) with a binary heap
Same bound as Dijkstra when h(n) = 0; can be far lower with a strong heuristic
Bottom Line
Dijkstra’s algorithm and A* aren’t competing techniques so much as the same technique with and without a goal-directed hint. If you need shortest paths to many destinations at once, or have no useful way to estimate remaining distance, Dijkstra is the correct and simpler tool. If you have a single known destination and a cheap, admissible way to estimate how far you still have to go — true of almost every grid-based game level and most point-to-point navigation problems — A* will typically explore a fraction of the nodes Dijkstra would, while still guaranteeing the shortest route.
FAQ
Is A* always faster than Dijkstra’s algorithm? In practice, yes, when the heuristic is informative — it explores fewer nodes by focusing toward the goal. With a heuristic of zero, A* and Dijkstra do identical work, since A* degenerates into Dijkstra exactly in that case.
What makes a heuristic “admissible”? It must never overestimate the true remaining cost to the goal. Manhattan distance on a uniform-cost grid and straight-line (Euclidean) distance on a Euclidean map are standard admissible heuristics, because the real path cost can never be shorter than the straight-line distance.
Can A* find the wrong (non-shortest) path? Only if the heuristic overestimates the true cost somewhere — i.e., it isn’t admissible. An inadmissible heuristic can make A* behave like Greedy Best-First Search, trading guaranteed optimality for speed.
Why does Dijkstra’s algorithm matter if A* generalizes it? Many problems don’t have a single destination or a useful heuristic — computing shortest paths to every node from one source, as link-state routing protocols do, is exactly the case A* offers no advantage over.
What’s the practical downside of A*? Memory. Like Dijkstra, it stores information for every node it has generated, which is why memory-bounded variants such as IDA* and SMA* exist for very large search spaces.
IBM’s enterprise AI story usually gets told through chips (Power11, Telum II) or models (watsonx.ai, the Granite family). Underneath both sits a less headline-grabbing but arguably more consequential bet: that enterprises don’t want to choose one cloud for AI, they want to run the same AI platform everywhere their data already lives. That bet is Red Hat OpenShift AI, delivered and increasingly managed through IBM Cloud — and it dates back to a decision IBM made years before generative AI existed.
At a Glance
Item
Detail
Core strategy
Run AI workloads on a consistent Kubernetes/OpenShift foundation across on-prem, edge, and multiple public clouds
Key platform
Red Hat OpenShift AI (part of the Red Hat AI portfolio, launched March 26, 2025)
Cloud layer
IBM Cloud — managed OpenShift, GPU infrastructure, IAM, and compliance controls for regulated industries
Hybrid/edge extension
IBM Cloud Satellite — brings IBM Cloud services to on-prem, edge, and other public clouds
Latest expansion
Red Hat AI Inference on IBM Cloud (GA May 22, 2026) and Red Hat OpenShift Virtualization Service on IBM Cloud (GA expected June 2026)
Origin of the bet
IBM’s ~$34 billion acquisition of Red Hat, completed July 9, 2019
Why Red Hat, Why a Decade Before It Looked Obvious
IBM completed its acquisition of Red Hat on July 9, 2019, paying $190 per share in cash for a deal valued at approximately $34 billion — at the time, the largest software acquisition in history. IBM’s own announcement framed the rationale explicitly: the deal was “positioning IBM as the leading hybrid cloud provider,” built around what IBM called a “next-generation hybrid multicloud platform.” Six years before generative AI became an enterprise mandate, IBM had already bet its hybrid-cloud future on Red Hat’s open-source Kubernetes distribution, OpenShift, as the common layer that would let workloads move between on-prem data centers and any public cloud. That bet is now the chassis IBM’s AI strategy runs on.
What Red Hat OpenShift AI Actually Does
Red Hat OpenShift AI is Red Hat’s hybrid cloud platform for deploying open-weight models and autonomous agents at production scale, built on open-source components including PyTorch, Kubeflow, MLflow, and the vLLM inference engine. It combines what Red Hat describes as MLOps, GenAIOps, and AgentOps capabilities: vLLM-based inference serving to cut GPU costs, an AI hub for centrally governing approved foundation models, a Models-as-a-Service layer for hosting models internal teams can call, NeMo Guardrails for real-time input/output filtering, and a Gen AI Studio playground for prototyping. Critically, it runs on “Kubernetes distributions of your choice” across on-premises, edge, and even disconnected (air-gapped) environments — and Red Hat lists IBM Cloud alongside AWS, Microsoft Azure, and Google Cloud as integrated cloud partners, with Nvidia, AMD, Intel, Dell, Lenovo, and Cisco as hardware partners.
OpenShift AI sits inside a broader umbrella Red Hat calls Red Hat AI, launched on March 26, 2025, which pairs OpenShift AI with Red Hat Enterprise Linux AI (RHEL AI) — a bootable server image that packages IBM’s Granite models with InstructLab alignment tooling. Red Hat’s AI Business Unit general manager Joe Fernandes described the goal as enabling “flexible inference across on-premises, cloud and edge environments” without re-architecting the model or the pipeline for each location.
IBM Cloud’s Job: Making the Platform Someone Else’s Problem to Operate
Open-source portability only helps if someone still runs the clusters. That’s the role Red Hat OpenShift on IBM Cloud plays: a fully managed OpenShift service where IBM handles provisioning, configuration, and lifecycle management through IBM Cloud Schematics, backed by a 99.99% availability SLA on regional high-availability clusters. Worker nodes support Nvidia V100, L40s, and H100 GPUs for AI workloads, clusters ship locked down by default, and existing Red Hat OpenShift software entitlements can be applied when a cluster is created — relevant for enterprises that already license Red Hat on-prem and don’t want to pay for OpenShift twice. IBM Cloud layers its own IAM, Observability, and Security services on top, and positions the whole stack toward regulated industries — financial services, government, and healthcare — through preconfigured compliance controls rather than leaving customers to assemble them.
The Latest Move: Managed AI Inference and Virtualization Services
IBM extended this stack on May 12, 2026 with two new managed services. Red Hat AI Inference on IBM Cloud, generally available May 22, 2026, lets enterprises run production models — a launch catalog including Granite 4.0 H Small, Mistral-Small-3.2-24B-Instruct, Llama 3.3 70B Instruct, GPT-OSS-120B, and Nemotron-3-Nano-30B-FP8 — without managing GPUs or inference infrastructure themselves. It’s built on vLLM, exposes OpenAI-compatible APIs for easy integration, and inherits IBM Cloud IAM, audit logging, and SLA-backed reliability. Red Hat OpenShift Virtualization Service on IBM Cloud, in limited availability with general availability expected in June 2026, runs on IBM Cloud VPC Bare Metal and gives enterprises a path to migrate legacy VM workloads onto OpenShift (via the included Migration Toolkit for Virtualization) alongside containerized and AI workloads, rather than running separate virtualization and container platforms.
IBM Cloud CTO Jason McGee framed the gap these services target directly: “Enterprises are eager to operationalize AI, but the gap between pilot and production may hold them back.” Red Hat’s Chief Product Officer Ashesh Badani called the launches “the next step” in the two companies’ work toward an open, consistent hybrid cloud platform for AI.
IBM Cloud Satellite: Extending the Same Platform to the Edge and On-Prem
IBM Cloud Satellite is the piece that lets this strategy reach beyond IBM’s own data centers. It’s a managed distributed cloud offering that brings IBM Cloud services, APIs, and security policies to on-premises data centers, edge locations, and even other public clouds (AWS, Azure, Google Cloud), without requiring data to move into IBM Cloud itself — a direct answer to data residency, latency, and compliance requirements that many enterprises can’t route around. A Satellite Connector extends services such as watsonx to on-premises resources over an auditable connection, and Red Hat OpenShift on IBM Cloud provides the common container runtime across every one of those locations, managed from a single dashboard.
IBM’s Hybrid Approach vs. the Hyperscalers’ Native Approach
AWS Bedrock, Azure AI Foundry, and Google Vertex AI each give enterprises fast, deeply integrated access to foundation models — but each is built first and foremost to run inside its own cloud. IBM’s pitch is structurally different: because the platform underneath (OpenShift, vLLM, Kubeflow, MLflow) is open source and Kubernetes-based, the same AI stack is designed to run on IBM Cloud, on a competitor’s cloud, on-premises, or disconnected — with IBM Cloud as the best-supported, most tightly integrated place to run it, not the only place it works.
Dimension
AWS Bedrock / Azure AI Foundry / Google Vertex AI
IBM Cloud + Red Hat OpenShift AI
Primary deployment surface
Native to their own respective public cloud
Any Kubernetes distribution: IBM Cloud, other public clouds, on-prem, edge, disconnected
Underlying stack
Proprietary managed services layered on each provider’s own infrastructure
Open-source stack (OpenShift, vLLM, Kubeflow, MLflow, PyTorch) managed as a service on IBM Cloud
Regulated-industry packaging
Compliance features available per-provider, per-service
Preconfigured compliance controls on IBM Cloud, plus IBM Cloud Satellite for keeping data on-prem entirely
Legacy VM + AI consolidation
Not a stated focus area
Explicit goal via Red Hat OpenShift Virtualization Service on IBM Cloud (2026)
Bottom Line
IBM’s hybrid-cloud AI strategy isn’t a new idea layered onto its 2019 Red Hat acquisition — it’s the direct, matured output of it. Red Hat OpenShift AI gives enterprises a model-agnostic, Kubernetes-based platform that runs wherever regulation, latency, or existing infrastructure require; IBM Cloud gives that platform a managed, SLA-backed, compliance-ready home; and IBM Cloud Satellite extends the same services to environments IBM doesn’t operate at all. The May 2026 launch of managed AI inference and OpenShift virtualization services shows IBM closing the remaining gaps — moving customers from “can deploy anywhere in theory” to fully managed services that remove GPU and VM-platform management as a blocker. Whether that beats the simplicity of a single hyperscaler’s native AI stack depends entirely on how much an enterprise’s data is already locked to specific locations — which, for IBM’s target regulated-industry customers, is usually the whole point.
Frequently Asked Questions
Is Red Hat OpenShift AI the same thing as IBM watsonx.ai?
No. Watsonx.ai is IBM’s platform for building and governing AI models and applications (including the Granite model family); Red Hat OpenShift AI is the underlying Kubernetes-based infrastructure and MLOps/AgentOps platform that can run those models — and other open-weight models — across hybrid environments. They’re complementary layers, not competing products.
Do I have to run on IBM Cloud to use Red Hat OpenShift AI?
No. Red Hat OpenShift AI runs on Kubernetes distributions of an organization’s choice, including on AWS, Microsoft Azure, and Google Cloud, which Red Hat lists as integrated cloud partners alongside IBM Cloud. IBM Cloud is where IBM offers the deepest managed-service integration, not the only place the platform runs.
What exactly did IBM announce in May 2026?
Two managed services: Red Hat AI Inference on IBM Cloud (general availability May 22, 2026), a vLLM-based managed inference service with an OpenAI-compatible API and a launch catalog including Granite 4.0 H Small and Llama 3.3 70B Instruct; and Red Hat OpenShift Virtualization Service on IBM Cloud (limited availability, general availability expected June 2026), which lets enterprises migrate VM workloads onto OpenShift alongside containerized and AI workloads.
How does IBM Cloud Satellite fit into this?
IBM Cloud Satellite extends IBM Cloud services, including AI services, to on-premises data centers, edge locations, and even other public clouds, without requiring the underlying data to move into IBM Cloud. It’s the mechanism that lets IBM’s hybrid strategy reach infrastructure IBM doesn’t directly operate.
Is any part of this open source?
Yes. Red Hat OpenShift AI is built on open-source projects including PyTorch, Kubeflow, MLflow, and vLLM, and runs on OpenShift, Red Hat’s Kubernetes distribution. IBM Cloud’s managed services (OpenShift, AI Inference, OpenShift Virtualization) are commercial offerings that run and support that open-source stack, rather than replacing it with proprietary infrastructure.
Most access-control systems ask a simple question the wrong way: “what role does this user have?” Relationship-based access control (ReBAC) asks a different, more flexible question: “what is this user’s relationship to this specific object?” That shift — from roles and static attributes to a graph of relationships — is what let Google secure products like Drive, Photos, and Calendar at a scale no role-based system could handle. The system that proved it out, Zanzibar, has since inspired a wave of open-source authorization systems that any engineering team can run today.
At a Glance
Item
Detail
What it is
Relationship-Based Access Control (ReBAC) — authorization decided by graphs of relationships, not just roles
Originated at
Google, described in the 2019 USENIX ATC paper “Zanzibar: Google’s Consistent, Global Authorization System”
Scale claimed by Google
Trillions of access control lists, millions of authorization checks per second, 95th-percentile latency under 10ms, >99.999% availability over 3 years
Google services using it
Calendar, Cloud, Drive, Maps, Photos, YouTube
Open-source implementations
OpenFGA, SpiceDB, Ory Keto, Permify
Core data model
Relation tuples: object#relation@user
What ReBAC Actually Changes
Role-based access control (RBAC) assigns users to roles like “editor” or “admin” and grants permissions to the role. That works until permissions depend on context: an editor of this document, a member of that team, a viewer because their manager shared a folder with them. Modeling that in RBAC means an explosion of roles — “editor-of-doc-123,” “viewer-via-folder-456” — that quickly becomes unmanageable. ReBAC instead stores the relationships themselves as data (user A is an editor of document B; folder B is a parent of document C) and lets the system traverse that graph at query time to answer “can user A view document C?” It is a generalization that cleanly subsumes simple RBAC and ACL-style permissions as special cases, which is part of why Google could use a single system across such different products.
Inside Zanzibar: Google’s Global Authorization System
Zanzibar was described publicly for the first time in a paper presented at the 2019 USENIX Annual Technical Conference by a team of Google engineers. According to Google Research’s own abstract, the system stores trillions of access control lists and processes millions of authorization requests per second on behalf of services used by billions of people — hundreds of Google client services, including Calendar, Cloud, Drive, Maps, Photos, and YouTube. Google reports 95th-percentile latency under 10 milliseconds and availability above 99.999% across three years of production operation. The central design problem the paper addresses is not raw throughput, but consistency: authorization decisions have to respect the real-world order in which a user’s permissions and the content they protect were changed, even though the underlying data is replicated across Google’s global infrastructure.
Relation Tuples: The Data Model Behind ReBAC
Zanzibar represents every permission as a relation tuple — a triple connecting an object, a relation, and a user (or another object). AuthZed’s own mapping of Zanzibar terminology confirms this is the foundational unit the paper calls a “Tuple,” which later ReBAC systems rename (SpiceDB calls it a “Relationship”). Object types and the relations they support are defined in a schema Zanzibar calls a namespace config. Modern implementations such as OpenFGA express the same idea in JSON. Here is an actual tuple example from OpenFGA’s own documentation, granting a user editor access to a document:
At query time, the system doesn’t just check for an exact tuple — it traverses the relationship graph. A user might not hold an “editor” tuple directly on a document, but might be a member of a team that has editor access to the folder containing it. The engine walks that chain and answers a single yes/no “Check” call, which is the API application code actually calls on every request.
Solving the “New Enemy Problem”
A distributed, globally replicated authorization graph creates a subtle danger the Zanzibar paper calls the New Enemy Problem: if a permission change and a content change aren’t applied in a consistent order, a user who was removed from a folder’s ACL could still end up seeing a document added to that folder afterward, because the permission check ran against stale replica data. Zanzibar’s answer is a consistency token the paper calls a zookie — later implementations use their own names, such as SpiceDB’s ZedToken — that lets a client ask the system to evaluate a check against data “at least as fresh as” a specific point in time, as AuthZed’s documentation explains. This is the detail that separates a genuine Zanzibar-style system from a simple permissions table: it’s built to be provably consistent under heavy replication, not just fast.
From Google-Only to Open Source: Four ReBAC Systems You Can Run Today
Zanzibar itself was never open-sourced, but its paper gave rise to several independent open-source systems that implement the same ideas. They differ in licensing, governance, and how literally they follow the original architecture.
System
Origin / Governance
License
Notable Detail
OpenFGA
Built at Auth0, open-sourced June 2022, continued at Okta, donated to the CNCF
Apache 2.0
CNCF Sandbox project since 2022; promoted to CNCF Incubating status on October 28, 2025
SpiceDB
Built and maintained by AuthZed
Apache 2.0
Describes itself as architecturally faithful to the Zanzibar paper; offers pluggable storage (Postgres, CockroachDB, MySQL, Spanner) and ZedToken-based consistency
Ory Keto
Built and maintained by Ory
Apache 2.0 (core); Ory Enterprise License for extra production features
Configured via the Ory Permission Language, a TypeScript-like, intentionally non-Turing-complete DSL; Ory calls it the most widely adopted open-source Zanzibar implementation
Permify
Standalone authorization service; Community Edition now part of FusionAuth per its own GitHub repo
AGPL-3.0 (Community Edition)
DSL supports ReBAC alongside RBAC and ABAC in one model; exposes both REST (port 3476) and gRPC (port 3478) APIs plus a browser Playground
Licensing is a real differentiator, not a footnote. OpenFGA and SpiceDB ship under the permissive Apache 2.0 license with no separate “open core” split for the engine itself (AuthZed sells managed hosting and support around SpiceDB, not a different license). Ory Keto’s core engine is Apache 2.0, with production add-ons gated behind a commercial Ory Enterprise License or Ory’s managed Ory Network. Permify’s Community Edition uses the AGPL-3.0 copyleft license, which has real implications if you plan to modify and redistribute it as part of a hosted product — teams in that position typically either accept AGPL’s obligations or move to Permify Cloud.
When ReBAC Is (and Isn’t) the Right Tool
ReBAC earns its complexity when authorization genuinely depends on relationships between resources — nested folders, team memberships, shared documents, multi-tenant hierarchies. If an application’s permission model is just “admin sees everything, member sees their own data,” plain RBAC is simpler to reason about and doesn’t need a relationship-graph engine at all. Attribute-based access control (ABAC) remains the better fit when decisions hinge on dynamic attributes — time of day, IP range, device posture — rather than who-is-related-to-what. In practice, the systems above (OpenFGA, SpiceDB, Ory Keto, Permify) all now support RBAC- and ABAC-style rules inside the same engine, which is one reason ReBAC frameworks have become a common default choice for new authorization layers rather than a niche tool.
Bottom Line
Zanzibar proved that relationship graphs, not role tables, are what let authorization scale to billions of users and trillions of permission records while staying consistent under constant change. Teams don’t need Google’s infrastructure to get those benefits: OpenFGA, SpiceDB, Ory Keto, and Permify each implement the same core ideas — relation tuples, graph traversal, and consistency tokens — as production-ready, self-hostable (or managed) open-source systems. The choice between them comes down to license terms, how closely you want to track the original Zanzibar architecture, and whether you want a CNCF-governed project (OpenFGA) or a vendor-backed one with a managed cloud option (SpiceDB, Ory Keto, Permify).
Frequently Asked Questions
Is Google Zanzibar itself open source?
No. Zanzibar is Google’s internal system, documented publicly in a 2019 research paper but never released as open-source software. OpenFGA, SpiceDB, Ory Keto, and Permify are independently built, open-source systems inspired by that paper, not forks or ports of Google’s code.
What is a “relation tuple” in plain terms?
It’s a single stored fact describing a relationship, such as “user Anne is an editor of document new-roadmap.” Authorization checks work by traversing chains of these tuples — through group memberships, folder hierarchies, and shared permissions — rather than looking up a user’s static role.
What is the “New Enemy Problem” and why does it matter?
It’s a consistency failure where a permission revocation and a content change aren’t applied in the correct order across replicas, letting a user who lost access still see new content. Zanzibar addresses it with consistency tokens (zookies, or ZedTokens in SpiceDB) that let a check be evaluated against data no staler than a specified point in time.
Which open-source ReBAC system should I choose?
There’s no universal answer — it depends on license fit (Apache 2.0 vs. AGPL-3.0), whether you want a CNCF-governed project (OpenFGA), how important a managed SaaS option is (Ory Network, AuthZed Cloud, Permify Cloud all exist), and which modeling language your team finds easiest to adopt. All four implement the same relation-tuple foundation.
Does adopting ReBAC mean replacing RBAC entirely?
Not necessarily. Every major open-source ReBAC engine covered here also supports RBAC- and ABAC-style rules within the same system, so teams typically migrate incrementally — modeling the relationships that actually need a graph while keeping simple role checks simple.
Sites that want deep, free analytics tied into Google Ads and Search Console
Free
Yes — the standard product is free
Plausible Analytics
Teams wanting the cheapest cookie-less option with multi-site/team plans
$9/month (Starter, lowest traffic tier)
No — 30-day free trial only
Fathom Analytics
Site owners wanting flat, predictable pricing and no cookie banner
$15/month (up to 100,000 monthly pageviews)
No — 7-day free trial only
Short Verdict
GA4 is the only genuinely free option here and remains the default for sites already using Google Ads, but it collects data via cookies, which generally brings EU/UK cookie-consent obligations with it. Plausible and Fathom are both paid, cookie-less alternatives that the vendors say remove the need for a consent banner around their own tracking — Plausible is the cheaper entry point, while Fathom’s flat per-tier pricing bundles more sites at every level.
What Privacy-First Analytics Actually Means
“Privacy-friendly” or “privacy-first” analytics tools are built around a specific technical trade-off: instead of tracking individual visitors across sessions with cookies or persistent device identifiers, they count aggregate pageviews and events without personally identifying anyone. Plausible and Fathom both market themselves this way, and both claim this design means their own tracking script doesn’t require a cookie-consent banner. GA4, by contrast, is Google’s standard, full-featured analytics platform; it’s free and extremely capable, but it uses cookies (such as _ga) and other identifiers to build its reporting, which is why GDPR/ePrivacy guidance in the EU and UK generally treats it as something that needs user consent before those cookies are set.
Pricing Breakdown
Tool
Plan
Price
What’s Included
GA4
Standard GA4
Free
Google Marketing Platform describes Google Analytics as free “to understand the customer journey and improve marketing ROI”
GA4
Google Analytics 360
Custom, quote-based
Enterprise tier; no public price listed on Google’s own marketing pages
Plausible
Starter
From $9/month (lowest traffic tier; 2 months free if billed annually)
1 site, unlimited data retention, 30-day free trial
Plausible
Growth
From $14/month
Up to 3 sites and 3 team members
Plausible
Business
From $19/month
Up to 10 sites and 10 team members, plus funnels and ecommerce revenue attribution
Plausible
Enterprise
Custom
10+ sites, SSO, priority support
Fathom
Entry tier
$15/month
Up to 100,000 monthly pageviews, 50+ sites included, 7-day free trial
Fathom
Mid tier
$25/month
Up to 200,000 monthly pageviews
Fathom
Higher tier
$45/month
Up to 500,000 monthly pageviews (Fathom’s pricing page notes additional higher tiers exist beyond these)
Both Plausible and Fathom price by traffic volume, so cost scales up as your site grows — unlike GA4’s flat $0 price regardless of pageviews. Neither Plausible nor Fathom currently offers a permanent free plan; both substitute a time-limited trial instead (30 days and 7 days, respectively).
The Cookie-Consent Angle
This is the detail that matters most if you’re also managing a cookie-consent banner. Google’s own support documentation on Consent Mode states plainly that “Consent Mode does not provide a consent banner or widget” — it’s a signal-passing framework your consent-management tool feeds into, not a replacement for one. When a visitor declines analytics cookies under Consent Mode, GA4 skips storing cookies and relies on modeled, cookieless pings to estimate the gap instead. Plausible’s and Fathom’s own marketing pages, by contrast, state that their trackers use no cookies and no persistent identifiers, and both claim this removes the need for an “intrusive” consent banner specifically for their own analytics. Fathom’s FAQ goes further, stating it is “fully compliant with GDPR, CCPA, and other privacy regulations” — a vendor claim, not independent legal certification. Importantly, switching analytics tools only addresses analytics cookies: if your site also runs ad pixels, embeds, or other cookie-setting scripts, you’ll likely still need a cookie-consent banner covering those regardless of which analytics tool you choose.
Pros and Cons
Google Analytics 4
Genuinely free for virtually any site size, with no pageview cap
Deep, direct integration with Google Ads, Search Console, and BigQuery export
Google’s modeling attempts to estimate data lost from users who decline cookie consent
Uses cookies and device identifiers, which generally triggers cookie-consent requirements in the EU/UK and under laws like the CCPA
Event-based reporting model has a steeper learning curve than a classic sessions dashboard
Consent Mode is a signal framework only — Google explicitly says it doesn’t supply the consent banner itself
Plausible Analytics
Vendor states its tracker uses no cookies and collects no personal data, which it says removes the need for a cookie banner for its own analytics
Lowest entry price among the two paid options, with a 30-day free trial
Open-source project, with a self-hostable Community Edition for teams that want to run it themselves (confirm feature/cost differences from the hosted product directly with Plausible)
No permanent free plan — only a time-limited trial
Reporting is intentionally shallower than GA4’s, by design, since it avoids extensive tracking
Pricing scales with traffic, so a high-traffic site can cost meaningfully more than GA4’s $0
Fathom Analytics
Vendor states no cookies are used and claims full GDPR/CCPA compliance, with an EU data-isolation option
Flat per-tier pricing bundles 50+ sites at every level, useful for agencies managing several small sites
Includes automatic bot filtering, saved views, an analytics API, and unlimited exports at the entry tier
No permanent free plan — only a 7-day trial, and a card is required upfront
Entry price ($15/month) is higher than Plausible’s ($9/month) at the lowest tier
Like Plausible, lacks GA4’s granular user-journey and ad-platform integrations
Who It’s a Good Fit For
GA4 — sites that want free analytics and already run Google Ads or lean on Search Console/BigQuery
Plausible — teams wanting the lowest entry price among privacy-first tools, with Growth/Business tiers for small agencies managing several sites
Fathom — businesses wanting flat, predictable billing tied purely to traffic volume, with many sites included at every tier
Who Should Look Elsewhere
Sites with strict compliance deadlines should treat vendor “GDPR compliant” claims as a starting point, not a legal guarantee, and consult a privacy professional for their specific jurisdiction
Businesses needing granular ecommerce funnels, cross-device IDs, and a free tier may find both Plausible and Fathom light on free options compared to GA4’s $0 price
Very high-traffic sites should model Plausible’s and Fathom’s tier costs against actual pageview volume before switching, since both pricing models scale with traffic
Bottom Line
If budget is the only constraint, GA4 wins by default — it’s free regardless of traffic. If your priority is avoiding analytics cookies and simplifying part of your cookie-consent story, Plausible is the cheaper of the two paid alternatives at the entry tier, while Fathom’s flat, site-bundled pricing suits agencies running several smaller properties. Either way, don’t assume switching analytics tools lets you remove your cookie banner entirely — check what else on your site sets cookies first.
FAQ
Does switching to Plausible or Fathom let me remove my cookie banner entirely?
Not necessarily for your whole site. Both vendors state their own tracking uses no cookies, so their analytics scripts specifically don’t require consent, according to their own marketing pages. But if your site also runs ad pixels, embeds, or other cookie-setting tools, you likely still need a consent banner covering those — switching analytics providers mainly removes one category of tracking from what the banner has to disclose.
Is Google Analytics 4 really free?
Yes — standard GA4 is free, per Google Marketing Platform’s own description of Analytics as “free of charge.” Google Analytics 360, the enterprise tier with higher data limits and an SLA, is quote-based and not publicly priced.
Do Plausible and Fathom offer a free plan?
No. As of this review, both offer only time-limited free trials — 30 days for Plausible and 7 days for Fathom — rather than a permanent free tier.
Which is cheapest for a small blog or marketing site?
Between the two paid options, Plausible’s Starter tier (from $9/month at its lowest traffic tier) is less expensive than Fathom’s entry tier ($15/month for up to 100,000 monthly pageviews). GA4 remains free regardless of traffic volume on the standard tier.
Does Google’s Consent Mode replace a cookie-consent banner?
No. Google’s own support documentation states that “Consent Mode does not provide a consent banner or widget” — it’s a signal-passing framework that a separate consent-management platform or cookie banner feeds into.
For most small teams, ClickUp offers the lowest verified entry price for a feature-complete paid tier, while Asana is the easiest to learn and monday.com is the most visually flexible — but its 3-seat minimum on every paid plan makes it a worse deal for teams of one or two people. None of the three free plans is really built to be a permanent solution once you pass a handful of users.
What Small-Team Project Management Software Actually Needs
“Project management software” covers everything from simple to-do lists to enterprise portfolio-tracking suites. For a small team — roughly 2 to 15 people — the priorities are usually narrower than what a big-company buyer needs: a clear task board or list, light automation so busywork doesn’t eat into billable hours, enough free or cheap seats to onboard everyone without a big upfront commitment, and a short learning curve so the tool gets adopted instead of ignored. Asana, ClickUp, and monday.com all target this segment directly with tiered, self-serve pricing (no sales call required for the plans covered here), which is why they’re consistently the three names that come up in small-business shortlists.
Pricing Breakdown
Tool
Plan
Price (billed annually)
Price (billed monthly)
Notes
Asana
Personal
Free
Free
Up to 2 users; unlimited tasks/projects, 100+ integrations
Asana
Starter
$10.99/user/mo
$13.49/user/mo
No seat cap; timeline/Gantt views, dashboards, unlimited automations, forms
Asana
Advanced
$24.99/user/mo
$30.49/user/mo
Adds goals, portfolios, time tracking, approvals/proofing
3-seat minimum; private boards/docs, time tracking
Both ClickUp and monday.com display only the annual-billed per-seat price on their current pricing pages; neither shows a separate monthly-billing figure for these tiers, so confirm the actual monthly rate directly with the vendor before budgeting against it. Asana is the only one of the three that publishes both numbers side by side.
Pros and Cons
Asana
Clean, easy-to-learn interface with strong task dependencies and workflow rules
Starter tier includes forms, custom fields, and unlimited free guests — useful for agencies working with outside clients
Both annual and monthly pricing are published up front, with no hidden quote requirement
Free plan tops out at just 2 users, so most small teams need to pay immediately
Deeper reporting and goal-tracking require the pricier Advanced tier
No built-in time tracking until Advanced
ClickUp
Lowest verified entry price among the three for a fully featured paid tier
Bundles docs, whiteboards, sprints, and time tracking into Core/Business rather than gating them behind an enterprise tier
Free plan allows unlimited tasks and members, not just a seat cap
Free plan’s 1-day activity history and 60MB storage are tight for teams that want an audit trail
Feature density means a steeper learning curve than Asana or monday.com
The displayed Core/Business prices are shown as discounted “sale” rates next to higher “regular” prices, so confirm what you’ll actually be billed long-term
monday.com
Visual, color-coded boards are easy for non-technical small-team members to adopt
Automation and integration action allowances are generous even on Standard
Companion products (monday CRM, monday dev, monday service) let a growing small business add adjacent tools on the same platform later
3-seat minimum on every paid plan means a 1-2 person team pays for a seat it doesn’t use
Free plan is capped at just 3 boards and 3 docs, tighter than the other two free tiers
Gantt/Timeline views don’t appear until Standard, one tier above the entry paid plan
Who It’s a Good Fit For
Asana — small teams juggling multiple cross-functional projects who want clean automation without a steep learning curve
ClickUp — budget-conscious teams that want to consolidate docs, sprints, and tasks into one low-cost subscription
monday.com — teams that think visually and may want to expand into CRM, dev, or service tools on the same platform later
Who Should Look Elsewhere
Solo founders or 2-person teams on a tight budget may find monday.com’s 3-seat minimum poor value compared to Asana’s or ClickUp’s per-seat free/paid structure
Teams chasing the lowest possible sticker price should double-check whether ClickUp’s displayed “sale” pricing is permanent before committing a budget to it
Teams that need deep goal-tracking and portfolio reporting out of the box may outgrow Asana’s Starter tier quickly and need to jump straight to Advanced
Bottom Line
There’s no universally “best” pick here — it depends on team size and shape. A team of exactly 3-10 people that wants the cheapest fully featured paid plan should start with ClickUp’s Core tier. A team that wants the smoothest onboarding and clear per-user pricing (both monthly and annual) should default to Asana’s Starter plan. A team that’s already decided it wants highly visual boards — and has at least 3 people to put on a paid seat — should look at monday.com’s Basic or Standard tier. Whichever you pick, start on the free plan first to confirm the workflow fits before paying for seats.
FAQ
Which tool has the best free plan for a small team?
ClickUp’s free plan allows unlimited tasks and members (with storage and activity-history limits), while Asana’s free Personal plan supports only 2 users and monday.com’s free plan supports only 2 seats and 3 boards. For a team larger than two people, ClickUp’s free tier is the most generous starting point of the three, though none is really meant as a permanent solution once a team grows past a handful of people.
Do I have to pay for team members who are just viewing tasks?
monday.com’s Basic plan explicitly includes unlimited free viewers, and ClickUp’s plans (including the free tier) include unlimited free members. Asana’s plans also allow unlimited free guests on paid tiers. Definitions of “viewer,” “guest,” and “member” vary by vendor, so check the current page before assuming parity.
Is monthly billing available at the advertised price?
Asana publishes both rates clearly ($10.99 annual vs. $13.49 monthly for Starter). ClickUp and monday.com currently display only the annual-billed rate for their core small-team tiers and don’t show a separate monthly number on their pricing pages, so confirm the monthly rate at checkout before assuming it matches the annual figure.
Which is easiest to learn for a non-technical small team?
Asana and monday.com are generally the more approachable starting points for first-time project-management users. ClickUp’s much larger feature set (docs, whiteboards, sprints, AI tools) usually means a longer onboarding curve, even though it’s the least expensive entry point of the three.
Do any of these include AI features for free?
Yes, to varying degrees: Asana’s Starter plan includes AI Teammates and AI Studio, ClickUp’s Free plan includes 500 AI credits per workspace, and monday.com’s Basic plan includes 1,000 AI credits per month. What counts as a “credit” and how far it goes differs by vendor, so treat these as a starting allowance rather than unlimited AI use.
When people talk about Google’s custom silicon, they usually mean TPUs — the AI accelerator chips behind Gemini training and inference. Axion is a different chip for a different job: it’s Google’s custom Arm-based general-purpose CPU, built to run the ordinary workloads that make up most of a cloud bill — web servers, microservices, databases, caches, analytics — not to train AI models. Google announced Axion in April 2024, and in late 2024 it became available to Google Cloud customers as the Compute Engine C4A instance family. It’s Google’s answer to a question AWS and Nvidia have also been asking: if Arm chips can match x86 performance at meaningfully better power efficiency, why keep buying x86 for everything?
At a Glance
Attribute
Detail
What it is
Google’s custom Arm-based general-purpose CPU for Google Cloud
Announced
April 9, 2024, at Google Cloud Next ’24
CPU core
Arm Neoverse V2 (Armv9 architecture)
Primary Compute Engine instance family
C4A (generally available); N4A (newer, in preview)
Max configuration (C4A)
Up to 72 vCPUs, 576 GB memory, 6 TB local storage
Google’s claimed price-performance vs. x86
Up to 65% better (Google’s own published benchmark, Sept. 2024 list prices)
Google’s claimed energy efficiency vs. x86
Up to 60% better (Google’s internal data)
Not to be confused with
TPUs (Google’s AI accelerator chips) — Axion is for general compute, not AI training
What Axion Actually Is
Axion is Google’s first custom Arm processor built specifically for its data centers. According to Google Cloud’s own announcement, it’s constructed around the Arm Neoverse V2 CPU core on the Armv9 instruction set — the same core family Arm licenses to other hyperscalers for their own chips — and it’s paired with Titanium, Google’s suite of custom silicon microcontrollers and offload hardware that handles networking, security, and storage I/O so those jobs don’t eat into the CPU capacity customers are paying for. Google positions Axion for general-purpose workloads: web and application servers, containerized microservices, open-source databases, in-memory caches, data analytics, media processing, and even CPU-based AI training and inference (as opposed to the GPU/TPU-based training Google’s TPU chips handle). The chip itself isn’t sold or exposed directly — you consume it through Compute Engine instance types, the same way AWS customers consume Graviton through EC2 instance types rather than buying the silicon.
The instance family built on Axion is C4A, which reached general availability in late 2024 alongside Titanium SSD-backed local storage. Per Google’s GA announcement, C4A scales up to 72 vCPUs, 576 GB of memory, and 6 TB of local storage, offered in both a standard shape (4 GB of memory per vCPU) and a high-memory shape (8 GB per vCPU), with networking up to 50 Gbps standard or 100 Gbps with Tier 1 networking. Google has since previewed a second Axion-based family, N4A, which its own documentation describes as using a different, newer Neoverse core generation (N3) — suggesting Google is iterating the Axion lineup rather than treating it as a single fixed chip. Both C4A and N4A are supported on Compute Engine, Google Kubernetes Engine, Batch, and Dataproc, with Dataflow support in preview and Cloud SQL and AlloyDB also running on Axion-based VMs.
The Price-Performance Claims, and What They’re Based On
Google’s headline numbers for Axion have shifted slightly between its initial announcement and the C4A GA post, and it’s worth separating the two. At the April 2024 announcement, Google claimed Axion offers up to 30% better performance than the fastest general-purpose Arm-based instances available in the cloud at that time, and up to 50% better performance and up to 60% better energy efficiency than comparable current-generation x86-based instances — both figures sourced to “Google Cloud Internal Data” dated March 31, 2024, without naming the specific comparison instances. At C4A’s general-availability announcement later that year, Google published a more specific and more aggressive claim: up to 65% better price-performance than comparable current-generation x86-based instances, alongside the same up-to-60%-better energy efficiency figure. That price-performance number carries an explicit methodology footnote — it’s based on published list prices as of September 2024 and estimated SPECrate2017_int_base scores for comparable, latest-generation, generally available VMs using general-purpose storage. In plain terms: it’s a list-price-to-benchmark-score ratio, not a guarantee of savings on your specific workload, discount tier, or committed-use pricing.
Google also backs the storage side of C4A with its own benchmarks: the Titanium SSD layer claims up to 2.4 million random read IOPS, up to 10.4 GiB/s of read throughput, and up to 35% lower access latency than the previous-generation SSD offering, based on Google’s internal benchmarking; attached Hyperdisk storage separately claims up to 350,000 IOPS and 5 GB/s of throughput per VM. On real-world adoption, Google’s GA post names early customers rather than just synthetic benchmarks: Couchbase uses C4A for Capella Columnar analytical and operational workloads, Databricks announced plans to bring data warehousing and AI workloads to Axion, and Elastic reported — in its own testing, not an x86 comparison — up to 40% better throughput on Axion-based VMs versus Elastic’s previous-generation instances for search and observability workloads.
How Axion Compares to AWS Graviton and Nvidia Grace
Axion isn’t the first custom Arm server chip from a major cloud player — AWS has been shipping its own, Graviton, since 2018, and Graviton4 (also built on Arm Neoverse V2 cores) now powers a wide range of EC2 instance families. The core strategic logic is the same for both companies: move general-purpose compute off licensed x86 chips and onto custom Arm silicon tuned for power efficiency, then pass some of that efficiency back as lower-priced instances. A deeper comparison of Graviton’s own generations and pricing is its own topic; the short version is that Google entered this race later than AWS but is using the same underlying Arm Neoverse V2 core family, so the two aren’t architecturally as different as the “Google vs. Amazon” framing might suggest.
Nvidia Grace is a different animal entirely. It’s also an Arm Neoverse V2-based CPU, but Nvidia designed it primarily to sit next to Nvidia GPUs over a high-bandwidth NVLink-C2C interconnect — in the Grace Hopper and Grace Blackwell “superchips” — rather than to serve as a standalone general-purpose cloud instance type you’d rent the way you rent a C4A or Graviton VM. Grace is sold as part of Nvidia’s own AI/HPC systems and through cloud providers that host those systems, not as an independent general-purpose compute tier competing directly with Axion or Graviton for everyday web and database workloads.
Comparison Table: Three Approaches to Custom Arm Silicon
Chip
Owner
Core
Primary Role
Axion (C4A/N4A)
Google Cloud
Arm Neoverse V2 (C4A); Neoverse N3 (N4A, preview)
General-purpose cloud compute instances
Graviton (latest: Graviton4)
AWS
Arm Neoverse V2
General-purpose cloud compute instances (EC2)
Grace
Nvidia
Arm Neoverse V2
CPU paired with Nvidia GPUs for AI/HPC systems, via NVLink-C2C
Trade-Offs to Weigh
Software compatibility: Arm-based instances require Arm-compatible builds of your software. Most mainstream Linux distributions, containers, and popular open-source databases now support Arm natively, but custom or legacy binaries compiled only for x86 won’t run without recompilation or emulation.
Benchmark specificity: Google’s 65% price-performance claim is based on a specific benchmark (SPECrate2017_int_base) and list prices at a specific point in time (September 2024) — real savings on your workload will depend on your actual usage pattern, committed-use discounts, and whether your workload resembles the integer-throughput profile that benchmark measures.
Ecosystem maturity: Graviton has several more years of production use and a wider base of AWS-native tooling built around it than Axion does on Google Cloud; Axion’s N4A family is still in preview, meaning its specs and availability could still change.
Not an AI training chip: Despite Google’s mention of “CPU-based AI training and inference” as a supported workload, Axion is not a substitute for TPUs or GPUs on large-scale model training — it’s aimed at the CPU-bound parts of a modern stack, not the accelerator-bound parts.
Bottom Line
Axion is Google Cloud’s bet that a meaningful slice of everyday cloud compute — the web servers, microservices, and databases that aren’t doing AI training at all — can run cheaper and more efficiently on custom Arm silicon than on licensed x86 chips. Google’s own published numbers (up to 65% better price-performance and up to 60% better energy efficiency versus comparable x86 instances, by its benchmark methodology) put it in the same conversation as AWS’s longer-running Graviton program, and both now lean on the same Arm Neoverse V2 core family under the hood. If your workloads are already Arm-compatible, C4A is worth testing against your current x86 instances using your own benchmarks — Google’s figures are a reasonable starting signal, not a guarantee for your specific bill.
FAQ
Is Axion the same as a TPU? No. TPUs are Google’s AI accelerator chips (the Trillium and Ironwood generations) built for training and running large AI models. Axion is a general-purpose CPU for ordinary compute workloads like web servers and databases.
Can I buy Axion chips directly? No. Axion is only available as the underlying silicon behind Google Compute Engine instance types like C4A and N4A — you rent VM instances, not chips.
Do I need to recompile my software to use C4A? If your software is already available for Arm (most modern Linux distributions, containers, and popular open-source databases are), migration is often straightforward. Software compiled only for x86 will need an Arm-compatible build.
How does Axion’s 65% price-performance claim compare to AWS Graviton’s own claims? Both companies publish favorable price-performance comparisons against x86 using their own benchmark methodologies, and both are now built on Arm Neoverse V2 cores; a rigorous apples-to-apples comparison between Axion and Graviton specifically would need independent, workload-matched benchmarking rather than relying on either vendor’s self-reported figures against x86.
Is N4A ready for production use? As of Google’s own documentation, N4A is in preview, which typically means it’s available to test but may not carry the same SLA or stability guarantees as the generally available C4A family — check Google Cloud’s current status before committing production workloads to it.
Nvidia’s hardware moat gets most of the attention, but the software layer that sits between a trained model and a running production endpoint is just as deliberate a lock-in strategy. NIM (Nvidia Inference Microservices) and Triton Inference Server — now rebranding as Nvidia Dynamo-Triton — are the two pieces developers actually touch when deploying a model, distinct from the Blackwell GPUs and CUDA layer we covered in Nvidia’s Data Center AI Empire and the NVLink/InfiniBand networking stack we covered separately. Here’s what each one actually does, based on Nvidia’s own documentation.
At a Glance
NVIDIA NIM
Triton Inference Server (→ Dynamo)
What it is
Pre-packaged, production-ready microservices for deploying specific foundation models
A general-purpose, open-source server for deploying models from any supported framework
Model scope
Nvidia’s curated catalog: LLMs, vision-language, speech, biology (AlphaFold2, Evo 2), climate (Earth-2), medical imaging, embedding/reranking, OCR, guardrails
Any model in TensorRT, PyTorch, ONNX, OpenVINO, Python, or RAPIDS FIL format
Deployment
Containers; NIM Operator for Kubernetes; GKE integration; WSL2 support
Linux containers via NGC; Windows/Jetson binaries on GitHub; Kubernetes with Prometheus monitoring
Licensing
Part of NVIDIA AI Enterprise
Open source (Apache-licensed on GitHub); also bundled in NVIDIA AI Enterprise for production support
Successor project
N/A
NVIDIA Dynamo — an open-source framework Nvidia calls “the successor to Triton Inference Server,” adding disaggregated prefill/decode serving
Short Verdict
NIM is the fastest path to a production endpoint if the model you need is already in Nvidia’s catalog — you get a hardened container with security updates, not a model you have to optimize and package yourself. Triton (and its emerging successor, Dynamo) is the right tool when you need to serve your own custom or fine-tuned model, or a model outside NIM’s catalog, with fine control over batching and multi-framework support. Both route through the same business reality: Nvidia bundles production support for either one inside NVIDIA AI Enterprise, a subscription Nvidia’s own CEO has publicly pegged at roughly $2,000 per GPU per year — the software half of Nvidia’s moat, sitting directly on top of the hardware half.
What NIM Actually Is
Nvidia describes NIM as “easy-to-use microservices for accelerating the deployment of foundation models on any cloud or data center.” In practice, a NIM is a pre-built, pre-optimized container for one specific model: Nvidia has already handled the inference engine selection, quantization, and performance tuning, and ships the result as a container with “production-grade runtimes” and ongoing security patching. The catalog is broad — large language models and vision-language models are the obvious entries, but it also covers speech (recognition, text-to-speech, translation), biology models like AlphaFold2, Evo 2, and RFdiffusion, Nvidia’s Earth-2 climate models, medical imaging, embedding and reranking models for retrieval-augmented generation, OCR, object detection, and safety guardrail models. Deployment tooling includes a NIM Operator for Kubernetes clusters, direct integration with Google Kubernetes Engine, and even a path to run NIMs inside WSL2 for local development. The trade-off for that convenience is scope: if the model you need isn’t in Nvidia’s catalog, NIM isn’t the tool — you fall back to Triton or another serving layer.
What Triton Does, and Why It’s Becoming Dynamo-Triton
Triton Inference Server is the general-purpose counterpart: an open-source server that deploys models from essentially any framework — TensorRT, PyTorch, ONNX, OpenVINO, Python, and RAPIDS FIL — on NVIDIA GPUs, non-NVIDIA accelerators, or plain x86/ARM CPUs, in the cloud or on-premises. Its core production features are dynamic batching (grouping incoming requests to use GPU capacity more efficiently), concurrent model execution, and support for real-time, batched, ensemble (multi-model pipeline), and streaming audio/video workloads. It integrates with Kubernetes for orchestration and Prometheus for monitoring, and Nvidia distributes Linux containers through NGC alongside Windows and Jetson binaries on GitHub.
Here’s the detail that’s easy to miss if you only know Triton by its old name: Nvidia’s own developer site now describes NVIDIA Dynamo as “the successor to NVIDIA Triton Inference Server.” Dynamo is an open-source, modular inference framework purpose-built for serving generative AI models across distributed, multi-GPU fleets, and it supports SGLang, TensorRT-LLM, and vLLM as backend engines. Its headline features go well beyond what Triton originally offered: disaggregated serving splits a request’s prefill and decode phases across different nodes so each can be scaled and optimized independently; a KV-aware router and KV Block Manager reduce redundant cache recomputation and offload cached attention state to cheaper memory tiers; and an SLO Planner adjusts allocated GPU resources to keep a deployment within a target latency budget. Nvidia cites independent benchmarks showing up to 50x higher throughput for mixture-of-experts models on its newest GB300 NVL72 systems running Dynamo compared with Hopper-generation hardware running older serving stacks — though as with any vendor-cited benchmark, treat the specific multiplier as directional rather than something every workload will replicate. Dynamo is available now as open source on GitHub, and Nvidia says NVIDIA AI Enterprise will add Dynamo for production inference support in a future release.
Licensing: What NVIDIA AI Enterprise Actually Costs
Triton itself is free and open source under an Apache license on GitHub — you can run it today with no Nvidia subscription. NIM and production support for Triton/Dynamo, however, are gated behind NVIDIA AI Enterprise, Nvidia’s commercial software subscription. Nvidia’s own licensing guide describes per-GPU licensing (every GPU in a server needs its own license), available as a subscription, a perpetual license with five years of support, or metered cloud consumption billed per GPU per hour on AWS, Google Cloud, Azure, or Oracle Cloud. The guide doesn’t publish a flat headline price and instead points to a separate pricing page — but Nvidia CEO Jensen Huang has publicly stated the company prices its AI Enterprise software at roughly $2,000 per GPU per year, a figure widely reported in coverage of Nvidia’s software strategy. Some data center GPUs (H100 PCIe/NVL, H200 NVL) ship with a bundled five-year AI Enterprise subscription already included, which is one reason the per-GPU economics of Nvidia’s platform are harder to compare directly against a GPU-only competitor’s sticker price.
Trade-offs vs. Alternatives
vLLM is the most common open-source alternative for LLM-specific serving: it’s free, widely adopted, and focused specifically on high-throughput language model inference with its own paged-attention memory management — notably, it’s also one of the backend engines Dynamo itself can orchestrate, so the two aren’t strictly competitors anymore. TensorFlow Serving is Google’s older, narrower serving system, built specifically around TensorFlow’s SavedModel format; it lacks Triton’s multi-framework flexibility and Dynamo’s distributed-serving features, but remains a simple, battle-tested choice for teams fully committed to the TensorFlow ecosystem. The general pattern: Nvidia’s stack (NIM/Triton/Dynamo) buys you tighter hardware-software co-optimization and enterprise support at the cost of a subscription and some platform lock-in; the open-source alternatives are free and portable but ask your team to own more of the integration and tuning work yourselves.
Pros and Cons
NVIDIA NIM
Pros: Fastest route to a production endpoint for catalog models; Nvidia handles optimization and security patching; broad catalog spanning far beyond LLMs.
Cons: Limited to Nvidia’s curated catalog; tied to NVIDIA AI Enterprise licensing; less control than rolling your own serving stack.
Triton / Dynamo-Triton
Pros: Open source and free to run; true multi-framework support; Dynamo’s disaggregated serving and KV-cache management are genuinely novel at large scale; works across NVIDIA and non-NVIDIA hardware.
Cons: You own the optimization and packaging work NIM would otherwise handle; production support still requires an AI Enterprise subscription; Dynamo’s most advanced features are newest and least battle-tested.
Who It’s a Good Fit For
Teams deploying a well-known foundation model with minimal customization — and who want Nvidia to own the optimization and patching burden — are the clearest fit for NIM. Teams serving their own fine-tuned or custom models, or running a genuinely multi-framework inference fleet, should look at Triton/Dynamo instead. Organizations operating at the scale of many GPUs across distributed nodes, where prefill/decode disaggregation and KV-cache offloading meaningfully change unit economics, are exactly who Dynamo was built for.
Who Should Look Elsewhere
If your workload is a single open-source LLM and you don’t need Nvidia’s broader catalog or enterprise support, vLLM alone is simpler and free. If you’re fully committed to TensorFlow and don’t need multi-framework flexibility, TensorFlow Serving avoids adopting a new toolchain entirely. And if avoiding per-GPU software licensing costs is a hard budget constraint, run Triton’s open-source build without an AI Enterprise subscription and accept community-support terms instead of Nvidia’s production SLA.
Bottom Line
NIM and Triton/Dynamo are the developer-facing half of Nvidia’s AI moat — the layer that converts raw GPU performance into something a team can actually deploy and operate. NIM trades flexibility for speed and support; Triton (and its new Dynamo successor) trades some convenience for openness and multi-framework reach. Both ultimately route spending back through NVIDIA AI Enterprise licensing, which is the real business model underneath “free and open source” software running on Nvidia hardware.
FAQ
Is Triton Inference Server being discontinued? Not immediately, but Nvidia’s own developer site names NVIDIA Dynamo as its successor, with Dynamo-Triton as a transitional branding. Triton remains available and supported, but new investment is clearly going into Dynamo’s distributed-serving features.
Do I need NVIDIA AI Enterprise to use Triton? No — Triton is open source and free to run on its own. AI Enterprise is only required if you want Nvidia’s production support, stable APIs, and long-term branch maintenance for it.
How much does NVIDIA AI Enterprise actually cost? Nvidia’s official licensing guide doesn’t publish a flat per-GPU price and refers buyers to a separate pricing page, but CEO Jensen Huang has publicly cited roughly $2,000 per GPU per year as the company’s software pricing target — a figure widely reported, not an official list price guaranteed for every deal.
Can I use NIM with models that aren’t in Nvidia’s catalog? Not directly — NIM is pre-built around specific catalog models. For custom or fine-tuned models outside that catalog, Triton or Dynamo is the appropriate serving layer instead.
How does Dynamo relate to vLLM? They’re not strictly competitors — Dynamo is a distributed orchestration framework that can run vLLM (along with SGLang and TensorRT-LLM) as one of its backend inference engines, adding disaggregated serving and KV-cache management on top.
Autonomous AI pentesting agents promise something static scanners never could: an attacker’s-eye view that doesn’t just flag a theoretical weakness but actually exploits it, chains it with other flaws, and proves impact. XBOW and Horizon3.ai’s NodeZero are the two most visible products in this space, and both have real, verifiable traction — but the loudest headline claim in the category, XBOW’s “#1 on HackerOne” milestone, is also a useful case study in how to read AI-security marketing critically. Here’s what’s actually been shown, what’s still just vendor claims, and where this fits relative to the static/SCA scanning we covered in our static analysis tools comparison and our prompt-injection and agentic security checklist.
At a Glance
XBOW
Horizon3.ai NodeZero
Core function
Autonomous web app/API penetration testing with exploit chaining
Autonomous internal/external network, cloud, and AD penetration testing
Deployment
Cloud-based, scoped by customer-set targets and rate limits
Free Docker host or OVA appliance for internal; Horizon3 cloud for external
Headline evidence
Ranked #1 on HackerOne’s US “reputation” leaderboard in mid-2025 (independently reported, with major caveats — see below)
No independently verified benchmark found; vendor describes capability, not third-party-audited results
Compliance claims
SOC 2, ISO 27001, ISO 42001, PCI DSS, NIS 2 (vendor-stated)
Not specified on the page reviewed
Short Verdict
Both tools are real products doing real automated exploitation, not vaporware — but “autonomous AI pentester” is being marketed more aggressively than the public evidence currently supports for either one. XBOW’s HackerOne result is genuine and independently reported, but a closer third-party analysis found it was driven heavily by one easy bug class (cross-site scripting) and a metric that measures reputation, not bounty earnings — and XBOW itself disclosed that a human was in the loop reviewing every submission. NodeZero has a mature, well-documented attack-path-mapping and exploit-verification workflow, but we found no independently audited benchmark of its real-world detection accuracy. Treat both as a meaningful addition to a security program’s testing cadence, not a replacement for human-led penetration testing or your existing vulnerability management stack.
What These Agents Actually Do
The pitch behind both products is the same: instead of a scanner that flags a pattern match and leaves a human to figure out if it’s real, an agentic pentester runs the actual attack. XBOW describes a three-stage loop — attack (many agents probe applications and APIs in parallel, chaining individual flaws into multi-step exploit paths), fix (each validated finding goes to the customer’s ticketing system with a specific code-level fix and the full exploit path), and verify (after a fix ships, XBOW re-runs the exploit and marks the finding resolved only if it no longer works). NodeZero frames its process similarly: it moves through a network the way a human attacker would, chains individually minor weaknesses — misconfigurations, weak or reused credentials, exposed data — into real attack paths, safely exploits what it finds, and then offers a “Quick Verify” step to confirm a remediation actually closed the hole.
That exploit-and-verify loop is the real differentiator from traditional vulnerability scanners, which typically stop at “this looks vulnerable based on a version number or signature” and leave validation, chaining, and remediation confirmation entirely to a human. Both XBOW and NodeZero also build in governance controls: XBOW lets customers set scope, rate limits, testing windows, and protected URLs, with a command checker that blocks destructive actions and full logging of agent activity. NodeZero isolates each test run in dedicated, ephemeral resources inside its own virtual private cloud, and its internal-network tests can run from a vendor-free Docker host or OVA appliance rather than requiring code deployed inside your perimeter.
The XBOW HackerOne Claim, Examined
This is the single most-cited piece of evidence in autonomous pentesting marketing, so it’s worth examining carefully rather than repeating uncritically. In mid-2025, XBOW’s AI agent topped a US leaderboard on the bug-bounty platform HackerOne, reportedly a first for a fully autonomous system — a milestone covered by multiple outlets and used to help XBOW raise a $75 million Series B. XBOW reported submitting roughly 1,060 vulnerabilities over the relevant period, including 54 critical and 242 high severity, and separately found a previously unknown flaw in Palo Alto’s GlobalProtect VPN affecting more than 2,000 hosts.
But an independent follow-up analysis, published on LessWrong and corroborated by a named security researcher’s own review, found important caveats that the headline coverage mostly skipped:
The leaderboard XBOW topped ranks reputation, a metric that blends submission volume and acceptance rate — not actual bounty earnings. XBOW’s total bounty payouts since early 2024 were reported at under $40,000, well below what top professional bug hunters typically earn.
Roughly 90% of XBOW’s score reportedly came from cross-site scripting (XSS), a comparatively easy-to-automate bug class, which inflates the apparent breadth of the result.
XBOW itself disclosed that a human was in the loop for every vulnerability submitted — researchers verified the agent’s findings and, at minimum, filtered them for relevance before submission. This is meaningfully different from a fully unsupervised system finding and reporting bugs on its own.
At the time of the TechCrunch-adjacent coverage, nearly 45% of XBOW’s submitted reports were still awaiting triage, which inflates the apparent submission count relative to confirmed, resolved findings.
None of this means XBOW’s technology isn’t real or useful — it clearly found a legitimate zero-day in widely deployed VPN software, and three Chrome sandbox-escape bugs chained by an XBOW researcher earned a $250,000 reward from Google, which is hard evidence of serious capability. But “AI becomes the #1 bug bounty hunter in the world” is a meaningfully overstated reading of “an AI-assisted team topped a reputation leaderboard heavily weighted toward one easy bug class, with humans checking every submission.” Readers evaluating this category should apply the same scrutiny to any vendor’s benchmark claim: check which specific metric was measured, look for concentration in one easy bug type, ask whether a human filtered the results, and treat press coverage as marketing until you’ve seen the underlying data yourself.
Pros and Cons
XBOW
Pros: Demonstrated real zero-day discovery (Palo Alto GlobalProtect, Chrome sandbox escape); strong governance controls (scope, rate limits, command checker); broad vendor-claimed compliance certifications; 200+ security teams reportedly using the platform.
Cons: Its signature benchmark claim is weaker than the headlines suggest once you check the underlying metric; heavy reliance on XSS in its published numbers; human-in-the-loop review undercuts “fully autonomous” framing; most performance data comes from the vendor itself.
Horizon3.ai NodeZero
Pros: Mature product with a clear attack-path-mapping and verified-exploitation workflow; “Quick Verify” closes the loop on remediation confirmation; broad scope (internal/external network, Kubernetes, cloud, AD password audits, phishing impact testing); no-agent internal deployment option.
Cons: No independently audited benchmark or published accuracy figures found in our research; less public third-party scrutiny than XBOW has received; evaluating real-world effectiveness requires a direct trial rather than published evidence.
Where This Fits in a Security Program
Autonomous pentesting agents sit between continuous vulnerability scanning and periodic human-led penetration testing or red-teaming — not as a replacement for either. Static and SCA scanners (the kind we covered comparing SonarQube, Semgrep, and CodeQL) catch patterns in source code before it ships; autonomous pentesting agents attack a running system the way an adversary would, which catches configuration and chaining issues that static analysis structurally can’t see. Human-led penetration tests and red teams still bring something these agents don’t yet claim to replace: judgment about business context, social engineering, and genuinely novel attack creativity outside an agent’s training distribution. The realistic near-term role for XBOW- or NodeZero-style agents is continuous, scheduled testing between the periodic human engagements most compliance frameworks still require — catching regressions and low-hanging exploitable paths faster and more often than an annual pentest ever could.
Who It’s a Good Fit For
Security teams with a mature vulnerability management program who want continuous, between-pentest validation that exploitable paths haven’t crept back in are the best fit for either tool. Organizations already running bug bounty programs may find XBOW’s web/API focus complements their existing coverage. Teams responsible for internal network, Active Directory, or cloud configuration hygiene are a more natural fit for NodeZero’s broader infrastructure scope.
Who Should Look Elsewhere
Teams that need a specific compliance checkbox requiring a human-certified penetration test (many frameworks still do) can’t substitute either tool for that requirement. Organizations without mature scope-control and incident-response processes should be cautious — running exploitation agents against production systems without tight guardrails carries real operational risk, regardless of vendor safety claims. And anyone evaluating this category based solely on press coverage of benchmark wins should read the underlying methodology first — as the XBOW case shows, the metric that was actually measured is often narrower than the headline suggests.
Bottom Line
Agentic offensive security is a genuinely new capability, not just rebranded scanning — the exploit-and-verify loop both XBOW and NodeZero run is a real step beyond pattern-matching vulnerability scanners. But the category is young enough that vendor benchmark claims need independent scrutiny before they inform a purchasing or risk decision, and “autonomous” currently means “heavily automated with humans still checking the output,” not “unsupervised.” Use these tools to extend and accelerate your testing cadence, not to replace human-led assessments your compliance program still requires.
FAQ
Is XBOW really the “#1 bug bounty hunter in the world”? It topped a specific HackerOne US leaderboard ranked by reputation (volume and acceptance rate), not by bounty earnings — its total payouts were reported under $40,000, well below top human hunters. A large share of its score reportedly came from one easy bug class (XSS), and XBOW disclosed humans reviewed every submission before it went out.
Do these tools replace traditional vulnerability scanners? No. They operate at a different layer — attacking and chaining exploits against a running system rather than pattern-matching code or configuration for known-bad signatures. Most security programs would run both, not one instead of the other.
Can autonomous pentesting agents cause damage to production systems? Both vendors describe safety controls (scope limits, rate limits, command checkers, isolated test environments), but any tool that actively exploits live systems carries real operational risk. Strict scoping and a clear incident-response plan before running either tool are essential, not optional.
What did XBOW’s researchers actually find in Chrome and Palo Alto’s GlobalProtect? XBOW reported finding a previously unknown GlobalProtect VPN flaw affecting more than 2,000 hosts, and a researcher using XBOW’s agents chained three Chrome bugs into a sandbox escape, for which Google paid a $250,000 bounty. Both are credible, specific, verifiable results distinct from the more disputed leaderboard claim.
Is NodeZero’s accuracy independently verified? We found no independently audited benchmark of NodeZero’s detection or exploitation accuracy in our research. Horizon3.ai’s own site describes the product’s workflow and capabilities but doesn’t publish third-party-reviewed performance figures, so teams should validate through a direct trial.
A landing page builder’s real job in a PPC campaign isn’t just “make a page” — it’s letting you launch variants fast, test them against each other, and keep load times low enough that you don’t burn ad spend on a slow page. Unbounce, Instapage, and Leadpages have all converged on roughly the same idea: a visual builder plus AI content generation plus A/B/multivariate testing, gated behind increasingly expensive tiers. The differences that actually matter for a PPC team are where testing unlocks, how traffic or visitor volume is capped, and whether the entry price gets you something usable or just a taste.
At a Glance
Tool
Entry Price
A/B Testing Unlocks At
Best For
Unbounce
$29/mo ($22/mo billed yearly)
Experiment tier, $149/mo
Agencies and PPC teams wanting AI traffic optimization at the top end
Instapage
$99/mo ($79/mo billed yearly)
Optimize tier, $199/mo
Teams that want server-side testing and ad-to-page personalization
Leadpages
$29/mo
Grow tier, $99/mo
Budget-conscious teams and solo marketers wanting AI page creation cheap
The Short Verdict
All three vendors now bundle AI page/copy generation even at their cheapest tier, so “can it build a page with AI” isn’t a differentiator anymore — “when does real A/B testing unlock, and what does it cost to get there” is. Leadpages gets you into manual A/B testing cheapest, at $99/month (Grow). Unbounce’s equivalent, Experiment, costs $149/month but throws in unlimited variants and confidence-interval reporting. Instapage asks the most to get any testing at all — $199/month for its Optimize tier — but that tier also includes server-side testing and dynamic text replacement, which the other two gate differently. If you just need a fast page with solid AI copy and don’t care about formal split testing yet, all three entry tiers (roughly $29–$99/month) will get a page live; the real decision is which vendor’s testing tier you’ll actually grow into.
What Each Tool Actually Offers
Unbounce‘s own pricing page lists six tiers. Starter ($29/month, or $22/month billed yearly) covers up to 500 monthly visits, 1 user, 1 domain, a hybrid page builder, AI copywriting, and 4,000 AI credits — but no A/B testing. Build ($99/$74) raises the visit cap to 20,000 and adds unlimited pages, custom code and scripts, and over 1,000 integrations, still with no A/B testing. Experiment ($149/$112, Unbounce’s “most popular” tier) is where testing unlocks: unlimited A/B testing and variants, manual traffic allocation, confidence intervals, dynamic text replacement, and conversion reporting, for up to 30,000 visits and 3 users. Optimize ($249/$187) adds AI-driven traffic routing to automatically favor better-performing variants, plus page scheduling and industry benchmarking, up to 50,000 visits. Concierge and Agency tiers above that are custom-quoted, aimed at high-volume accounts and agencies reselling the platform. Every tier includes unlimited conversions, unlimited subdomains, and free hosting.
Instapage prices higher at every step but leans on fewer, broader tiers. Create costs $99/month ($79/month billed annually) and covers 15,000 unique monthly visitors with the visual builder, reusable content blocks, real-time collaboration, triggered popups, AI content generation, and “Collections” for programmatic page generation — but, notably, no A/B testing. Optimize ($199/month, $159 annually) is Instapage’s recommended tier and the point where server-side A/B testing arrives, along with hypothesis tracking, experimentation history, customizable traffic splitting, scheduling, multi-step forms, and dynamic text replacement, on a 30,000-visitor base (expandable to 50,000). Convert is custom-quoted and adds ad-to-page personalization, global elements, root-domain publishing, heatmaps, a dedicated customer success manager, and enterprise security features. Create and Optimize both include a 14-day free trial capped at 2,500 unique monthly visitors.
Leadpages, per its current pricing page, has shifted toward a five-tier structure split between “publishing” and “testing” plans. Pro ($29/month) covers 25 pages, 1 custom domain, 1 blog, 5 GB storage, 12,000 AI credits per month, and API access, with no A/B testing. Business ($49/month) raises that to 50 pages, 2 domains, 2 blogs, 10 GB storage, and 12-month analytics retention. Grow ($99/month, marked “Most Popular”) is the first testing tier: unlimited pages, manual A/B testing with up to 6 variants per page, dynamic text replacement, and basic visitor personalization. Optimize ($199/month) adds multivariate (A/B/C/D) testing, click and scroll heatmaps, Smart Traffic auto-personalization, and performance alerts. A Scale tier at roughly $399/month is referenced in Leadpages’ FAQ with a higher AI-credit allowance, and Enterprise is custom. Leadpages states there are no traffic caps on any plan — the only volume limits are on anonymous-visitor detection and lead-enrichment credits on the higher tiers, not raw traffic.
Pricing and Feature Comparison
Feature
Unbounce
Instapage
Leadpages
Entry price
$29/mo ($22 annual)
$99/mo ($79 annual)
$29/mo
Traffic/visitor cap, entry tier
500 visits/mo
15,000 visitors/mo
No traffic cap
A/B testing unlocks at
$149/mo (Experiment)
$199/mo (Optimize)
$99/mo (Grow)
AI copy/page generation
Included from Starter
Included from Create
Included from Pro
Multivariate testing
Not explicitly named
Not explicitly named
Yes, Optimize tier (A/B/C/D)
Heatmaps
Not on standard tiers
Convert tier (custom)
Optimize tier ($199/mo)
Top self-serve price
$249/mo (Optimize)
$199/mo (Optimize)
~$399/mo (Scale, per FAQ)
Pros
Unbounce: Cheapest entry point, unlimited A/B test variants once you reach Experiment, and dedicated Agency/Concierge tiers for resellers.
Instapage: Highest visitor allowance at the entry tier (15,000 vs. Unbounce’s 500), plus real-time team collaboration and ad-to-page personalization at the top end.
Leadpages: No traffic caps on any plan, and the cheapest path to real A/B testing ($99/month vs. $149–$199 for the other two).
Cons
Unbounce: The $29 Starter tier’s 500-visit cap is tight for an active PPC campaign — many teams will need Build or Experiment almost immediately.
Instapage: The most expensive entry point of the three by a wide margin, and no A/B testing at all until the second tier.
Leadpages: Its newer tier structure (Pro/Business/Grow/Optimize/Scale) is a meaningful change from its historical simpler plans, so published feature-to-plan mapping can be harder to verify precisely — confirm current inclusions on the live pricing page before buying.
Who It’s a Good Fit For
Choose Unbounce if you’re an agency or high-volume PPC team that wants unlimited A/B test variants and dedicated reseller pricing once you’re ready to scale past the entry tiers. Choose Instapage if your team is collaborative (multiple editors working on pages simultaneously) and you can justify the higher entry price for a generous visitor allowance and later-stage ad personalization. Choose Leadpages if you want the cheapest route to real split testing and don’t want to worry about visitor caps regardless of plan.
Who Should Look Elsewhere
If your PPC campaigns are genuinely low-volume (under a few hundred monthly visits) and you don’t need testing yet, any of the entry tiers will feel like overkill compared to a simpler, cheaper page tool; conversely, enterprise advertisers running heavy multivariate testing across many landing pages should expect to land in custom-quoted territory on all three (Unbounce Concierge/Agency, Instapage Convert, or Leadpages Enterprise) rather than staying on published self-serve pricing.
Bottom Line
For a PPC team deciding where to put ad budget versus tooling budget, Leadpages offers the cheapest road to real A/B testing with no traffic caps anywhere in its lineup, Unbounce offers the most generous testing once you commit to its $149/month Experiment tier, and Instapage trades a higher entry price for the most headroom on raw visitor volume and the richest collaboration features. None of the three make their multivariate or enterprise-grade personalization features free or cheap — expect to pay $150–$250/month minimum for serious split testing on any of them.
FAQ
Which tool is cheapest overall for a small PPC campaign? Unbounce and Leadpages both start at $29/month, but Unbounce’s Starter tier caps you at 500 monthly visits while Leadpages has no traffic cap on any plan — making Leadpages the better value if you expect meaningful ad traffic from day one.
Do any of these integrate directly with Google Ads or Meta Ads? All three support standard tracking pixels, UTM parameters, and dynamic text replacement for matching ad copy to landing page headlines; deeper native ad-platform integration (like Instapage’s AdMap or ad-to-page personalization) tends to be reserved for higher tiers.
What’s the difference between A/B testing and multivariate testing here? A/B testing compares whole page variants against each other; multivariate testing (offered by Leadpages’ Optimize tier, labeled A/B/C/D) tests combinations of individual page elements simultaneously, which needs more traffic to reach statistical significance.
Can I use these tools without a developer? Yes — all three are built as visual, no-code page builders aimed at marketers; custom code and scripting are optional add-ons on higher tiers, not requirements.
Is annual billing significantly cheaper? Yes on Unbounce and Instapage, which both publish annual discounts (roughly 20–25%) directly on their pricing pages; Leadpages’ current page did not clearly display a separate annual price in our research, so confirm directly with Leadpages before assuming a discount applies.
Choosing a website builder in 2026 isn’t the same decision it was five years ago. Wix, Squarespace, and WordPress.com have all restructured their pricing and plan names at least once in the past year, and the gap between “easiest to use” and “most flexible” has narrowed. We pulled current plan tiers, prices, and feature lists straight from each vendor’s own pricing page to see where the real differences sit today.
At a Glance
Spec
Wix
Squarespace
WordPress.com
Entry paid plan
Light, ~$17.77/mo (annual)
Basic, $19/mo (annual)
Personal, $4/mo (annual)
Free plan?
Yes, Wix-branded subdomain
No (trial only)
Yes, wordpress.com subdomain
Best known for
Drag-and-drop design freedom
Designer-quality templates
Blogging heritage + WooCommerce option
E-commerce transaction fees
Varies by plan tier
0% on Core and up; 2% on Basic
0% with Business/Commerce plans
Best for
Visual control, small business sites
Portfolios, creative brands, online stores
Blogs, content sites, WooCommerce stores
Short Verdict
If you want the most hands-on visual editor and don’t mind a steeper learning curve for e-commerce, Wix’s Core and Business plans cover most small-business needs. If design polish matters more than flexibility — portfolios, photographers, boutique brands — Squarespace’s Core plan is the stronger template library and the better e-commerce fee structure for digital products. If you eventually want full control over plugins, themes, and your own WooCommerce store without paying transaction fees, WordPress.com’s Business plan is the better long-term home, especially if you already publish content regularly.
What Each One Is
Wix is a fully hosted, drag-and-drop site builder where you place elements freely on a canvas rather than working inside a fixed template grid. It markets itself on design freedom, a large app marketplace, and an AI site generator that can build a draft site from a text prompt.
Squarespace builds sites from a smaller set of professionally designed templates with a more opinionated editor — you get less pixel-level freedom than Wix, but a more consistent, higher-end look by default. It’s long been the go-to for photographers, restaurants, and creative portfolios, and it owns Acuity Scheduling and Unfold for additional booking and social tools.
WordPress.com is Automattic’s hosted version of the open-source WordPress software. The free and Personal plans are closer to a traditional website builder experience, but paying up to the Business or Commerce tier unlocks the ability to install any WordPress plugin and theme, including the full WooCommerce e-commerce stack — giving you an upgrade path to practically unlimited customization that Wix and Squarespace don’t offer.
Pricing Breakdown
Plan
Price (billed annually)
Key limits/features
Wix Free
$0
Wix subdomain, drag-and-drop editor, Wix branding
Wix Light
~$17.77/mo
2 GB storage, free domain for 1 year, 2 collaborators
Wix Core
~$29.77/mo
50 GB storage, basic e-commerce, 5 collaborators
Wix Business
~$39.77/mo
100 GB storage, standard e-commerce, 10 collaborators
Wix Business Elite
~$159.77/mo
Unlimited storage, advanced e-commerce, 100 collaborators, advanced dev platform
Squarespace Basic
$19/mo
30 min video storage, 2% store transaction fee, 7% digital content fee
Squarespace Core
$29/mo
5 hrs video, 0% store transaction fee, 5% digital content fee
Squarespace Plus
$49/mo
50 hrs video, 0% store fee, 1% digital content fee
Squarespace Advanced
$99/mo
Unlimited video, 0% fees on everything
WordPress.com Free
$0
1 GB storage, wordpress.com subdomain, no plugins
WordPress.com Personal
$4/mo
6 GB storage, free custom domain for 1 year
WordPress.com Premium
$8/mo
13 GB storage, payment buttons, video uploads
WordPress.com Business
$25/mo
50 GB+ storage, any plugin/theme, WooCommerce, SSH/WP-CLI access
WordPress.com Commerce
$45/mo
Full WooCommerce, premium store themes, 0% WooCommerce fees
A note on Wix pricing: Wix has adjusted its plan prices more than once in 2026, and its official pricing page states that quoted rates exclude tax and can vary by location. The figures above come directly from Wix’s current pricing page at the time of writing — confirm the live rate for your region and billing cycle before checking out. Squarespace and WordPress.com monthly figures reflect each vendor’s own published annual-billing rate; all three builders charge noticeably more if you pay month-to-month instead of annually.
Ease of Use
Wix’s canvas editor gives you the most granular control over exact placement of every element, which is powerful but also the easiest place to accidentally break a layout on mobile. Its AI site builder narrows that risk by generating a structured starting point. Squarespace trades some of that freedom for guardrails — sections snap into clean, pre-designed blocks, so it’s harder to make a page look unbalanced, but also harder to deviate from the template’s visual language. WordPress.com’s block editor (Gutenberg) sits in between: easier to learn than raw WordPress plugin management, but the full power of the platform — themes, plugins, custom code — only becomes available on paid plans, and that extra flexibility comes with a real learning curve compared to Wix or Squarespace.
E-Commerce and SEO Tools
All three offer built-in SEO basics — editable meta titles/descriptions, sitemaps, and mobile-responsive output — at every paid tier. Squarespace’s SEO panel and built-in keyword suggestions are generally considered the most beginner-friendly out of the box. For selling online, the economics differ sharply: Squarespace drops its store transaction fee to 0% starting on the Core plan, but still takes a cut of digital content and membership sales unless you’re on its top Advanced tier. WordPress.com only reaches 0% WooCommerce transaction fees on Business and Commerce plans, but WooCommerce itself is a far deeper, more extensible store engine once you’re there. Wix’s fee structure depends on which of its tiered “eCommerce” feature sets (Basic, Standard, Advanced) your plan includes, and scales with plan level rather than a flat percentage disclosed on the main pricing page.
Pros and Cons
Wix
Pros: most visual design freedom, large app marketplace, AI site generator, built-in booking/events tools
Cons: pricing has risen multiple times in 2026, free plan carries Wix branding, migrating off Wix later is harder than with standard WordPress
Squarespace
Pros: strongest default design quality, 0% store fees from Core up, unlimited bandwidth on every plan
Cons: less granular layout control than Wix, fewer third-party app integrations, digital content fee only disappears on the priciest Advanced plan
WordPress.com
Pros: cheapest entry point, real WordPress underneath (full plugin/theme access on Business+), no required transaction fee once you reach Business/Commerce
Cons: full customization locked behind pricier plans, steeper learning curve than Wix or Squarespace if you want to touch plugins and themes
Who It’s a Good Fit For
Choose Wix if: you want maximum visual control over layout and plan to use its app marketplace or built-in booking/events features.
Choose Squarespace if: you’re a creative professional, photographer, or boutique brand where visual polish matters more than layout flexibility, and you sell a modest volume of products or digital content.
Choose WordPress.com if: you blog or publish content regularly, want the option to grow into a full WooCommerce store without recurring platform fees, or want an exit path that doesn’t lock your content into a proprietary format.
Who Should Look Elsewhere
If you’re running a high-volume online store with complex inventory, all three of these general-purpose builders will eventually feel limiting compared to a dedicated e-commerce platform like Shopify. And if you need enterprise-grade workflow, multi-site management, or a custom dev team working against a headless CMS, none of these three hosted builders is the right long-term foundation.
Bottom Line
There’s no universal winner here — the right pick depends on whether you value design freedom (Wix), out-of-the-box visual polish (Squarespace), or long-term platform ownership and content flexibility (WordPress.com). Price annually with any of them; month-to-month billing on all three carries a meaningful premium.
FAQ
Can I switch builders later without losing my content? Moving a WordPress.com site’s content to another host is relatively straightforward since it’s built on open-source WordPress. Migrating a Wix or Squarespace site elsewhere is much harder, since both use proprietary, closed site architectures with no standard export-and-rebuild path.
Which is cheapest for a simple one-page site? WordPress.com’s Personal plan and free tier are the cheapest entry points. Wix and Squarespace’s paid plans both start higher, though Wix also offers a free, ad-branded tier.
Do any of these charge a transaction fee on sales? Squarespace drops its store transaction fee to 0% from the Core plan up (digital content/membership sales still carry a declining fee by tier). WordPress.com reaches 0% WooCommerce fees on Business and Commerce. Wix’s fee treatment depends on the eCommerce feature tier attached to your plan — check the live pricing page for your plan’s specifics.
Is WordPress.com the same as self-hosted WordPress.org? No. WordPress.com is a managed hosting service built on the same open-source software as WordPress.org, but lower-tier WordPress.com plans restrict plugin/theme installation. Only Business plan and above unlock the same openness that self-hosted WordPress.org offers by default.
Influencer marketing platforms promise to turn a chaotic spreadsheet-and-DM process into something closer to a real marketing channel: find creators, run outreach, manage contracts and content approvals, pay people, and tie it all back to sales. Aspire, Grin, and Upfluence are three of the category’s most established names, and all three target ecommerce and DTC brands first. Where they differ sharply is pricing transparency: Grin publishes real numbers on its website, while Aspire and Upfluence are both custom-quoted, with no public price list at all. That alone should shape how you shop.
At a Glance
Platform
Pricing Model
Published Starting Price
Best For
Aspire
Custom quote only
Not publicly listed
Established ecommerce brands running full-service creator programs
Grin
Published tiers, self-serve to Starter
Free, then $200/month (Starter)
Brands that want transparent pricing and to start small
Upfluence
Custom quote, modular plans
Not publicly listed
Agencies and brands needing a large creator database and e-commerce integrations
The Short Verdict
Grin is the only one of the three that lets you see a price before talking to a salesperson — its own pricing page lists Free, Starter at $200/month, Growth at $500/month, and Scale at $1,500/month, each raising creator-search volume, gifting caps, and the wallet-deposit fee structure. Aspire and Upfluence both require a demo call to get a number, which isn’t unusual in this category but does make them harder to budget for sight-unseen. Upfluence stands out for the size of its creator database (it advertises more than 14 million creators) and for charging a flat platform fee rather than a cut of tracked sales; Aspire leans hardest into full-service execution, pairing its software with agency-style services for brands that want help running campaigns, not just a tool to run them in.
What Each Platform Actually Offers
Aspire (formerly AspireIQ) centers on an AI-driven Creator Discovery tool that lets brands search its marketplace in plain language instead of building filter stacks, plus a Campaign Manager that handles content approval, briefs, affiliate links, promo codes, and Shopify-based product fulfillment for seeding. Its relationship tools include a Contact Hub for managing creator history, personalized commission structures (flat, percentage, or tiered), and automated performance-based payouts, alongside a Shopify app for recruiting existing customers as creators and tracking content-driven sales. Aspire also offers a full-service agency option with a dedicated customer success team. Its own site positions it toward ecommerce brands broadly — the company cites 800-plus brand customers — and does not publish any pricing, tiers, or plan names; every path on the site leads to a demo request.
Grin is the clearest on pricing of the three. Per its own site, Free ($0/month) is capped at 1,200 monthly creator searches, 2 live campaigns, and 10 total gifts, with a steep 20% fee on wallet deposits used for creator payouts. Starter ($200/month) raises that to 12,000 searches and 100 gifts/month with unlimited live campaigns, at a 10% wallet fee. Growth ($500/month) reaches 36,000 searches and 300 gifts/month at a 7% fee, and adds multi-brand support. Scale ($1,500/month) goes to 120,000 searches and 1,000 gifts/month at a 5% fee, aimed at programs funding $50,000 or more a month. Every tier, including Free, includes Gia (Grin’s AI agent for creator recommendations), an escrow wallet with creator payouts, unlimited CRM contacts, and Shopify integration — the differences are volume limits and the payout fee percentage, not which core features you get. Enterprise is custom, for brands sending thousands of gifts monthly.
Upfluence organizes itself around three modular, increasingly capable plans rather than a strict ladder of fixed tiers: Find Creators (discovery and outreach only), Scale Creator Programs (adds campaign management, ecommerce integrations for platforms like Shopify, WooCommerce, Magento, BigCommerce, and Amazon, a CRM, and sales analytics with zero platform fees on tracked sales), and Run Programs on Autopilot (adds AI-driven end-to-end campaign automation, budget management, and global creator payouts via Upfluence Pay, including automatic 1099/W-9 tax form handling). Upfluence’s database claim of 14 million-plus creators across Instagram, TikTok, YouTube, Twitch, and Pinterest is larger than what Aspire or Grin advertise. Pricing for all three Upfluence plans is custom-quoted based on team size and program volume, with a mandatory discovery call and a 12-month minimum on annual contracts — but the company is explicit that it charges a fixed platform fee rather than a percentage of sales, which is a meaningfully different economic model from Grin’s wallet-deposit fee.
Feature Comparison
Feature
Aspire
Grin
Upfluence
Public pricing
No
Yes — $0 to $1,500/mo published
No
Creator discovery method
AI plain-language search + marketplace
Marketplace + creator search, volume-capped by tier
14M+ creator database with advanced filters
Payment model
Custom commissions, flat/%/tiered
Escrow wallet; % fee on deposits (20% down to 5%)
Flat platform fee; no % of sales taken
Full-service agency option
Yes
No (software-only, self-serve or Enterprise support)
Aspire: Strong plain-language AI discovery and an optional full-service agency layer for brands that don’t want to run campaigns themselves.
Grin: The only platform here with a genuinely free tier and published, predictable pricing all the way to $1,500/month.
Upfluence: The largest advertised creator database and the broadest set of ecommerce platform integrations, plus a no-percentage-of-sales fee model.
Cons
Aspire: Zero public pricing makes it impossible to budget or comparison-shop without booking a sales call first.
Grin: Wallet-deposit fees (as high as 20% on the Free tier) add real cost on top of the monthly subscription for brands doing a lot of gifting or paid partnerships.
Upfluence: Also no public pricing, plus a 12-month minimum contract on annual plans, which is a longer commitment than month-to-month competitors.
Who It’s a Good Fit For
Choose Grin if you want to start small, see exact pricing up front, and scale a self-serve program without a sales process. Choose Aspire if you’re an established ecommerce brand that wants both software and agency-style execution support bundled together. Choose Upfluence if creator database size and multi-platform ecommerce integration (beyond just Shopify) matter most, and you’re comfortable with a quote-based sales process and annual commitment.
Who Should Look Elsewhere
Very small brands or solo marketers testing influencer marketing for the first time with a tight budget and no appetite for sales calls should start with Grin’s free tier rather than Aspire or Upfluence, since neither publishes pricing low enough (or at all) to evaluate without a demo. Brands running high-volume gifting programs should model Grin’s wallet fee carefully against Upfluence’s flat-fee model before committing, since the cost structures diverge significantly at scale.
Bottom Line
All three platforms can run a real creator program, but they ask you to buy very differently. Grin is the transparent, try-before-you-commit option. Aspire and Upfluence are both built for brands and agencies ready to invest in a longer sales process in exchange for a larger database (Upfluence) or more hands-on execution support (Aspire) — just budget extra time to get an actual number out of either one before you can compare total cost against Grin’s published tiers.
FAQ
Why don’t Aspire and Upfluence publish pricing? Neither company’s pricing or plans page lists dollar figures; both route every pricing inquiry through a demo or sales call, which is common in enterprise-leaning martech but means you can’t comparison-shop without engaging sales.
Is Grin’s free plan actually usable, or just a trial? It’s an ongoing free tier, not a time-limited trial, but it’s capped at 1,200 monthly creator searches, 2 live campaigns, and 10 total gifts with a 20% wallet-deposit fee — enough to test the platform, not to run a real program at volume.
Do these platforms take a cut of sales creators drive? It varies. Grin charges a percentage fee on wallet deposits used for creator payouts (not a cut of sales itself), while Upfluence explicitly says it takes no percentage of sales and instead charges a fixed platform fee.
Are these tools only for ecommerce brands? They’re built with DTC and ecommerce brands as the primary audience (hence the heavy Shopify/WooCommerce/Amazon integration focus), but agencies managing creator programs on behalf of multiple clients are also a named audience for all three, especially Upfluence and Aspire.
Can I switch platforms later without losing creator relationships? Creator contact data and campaign history generally don’t transfer automatically between platforms, so plan for some manual re-import of creator lists and payment history if you switch providers.
If you searched for “Codeium Windsurf enterprise pricing” expecting a straightforward comparison, you’ve run into the same surprise we did: as of late 2026, Windsurf no longer exists as a separate product. Codeium rebranded to Windsurf in 2024, Cognition (maker of the autonomous coding agent Devin) acquired Windsurf in late 2025 for a reported $250 million, and in June 2026 Cognition rebranded the Windsurf editor itself into “Devin Desktop.” This piece compares what that product has become — now simply part of Cognition’s Devin lineup — against Tabnine and Amazon Q Developer, the two other enterprise-oriented AI coding tools built specifically around on-prem/VPC deployment and compliance, rather than repeating our earlier Cursor vs. GitHub Copilot vs. JetBrains AI Assistant comparison.
At a Glance
Tool
Vendor
Entry enterprise pricing
Self-hosting/VPC
Key compliance certs
Devin / Devin Desktop (formerly Codeium/Windsurf)
Cognition
Teams: $80/mo + $40/seat/mo; Enterprise: custom
VPC deployment and a “dedicated deployment option” on Enterprise
SOC 2 Type II and ISO 27001 certified on all surfaces; FedRAMP High in progress
Tabnine
Tabnine
Not published; contact sales for Enterprise
Secured SaaS, on-premises, or fully isolated in your own VPC
SOC 2 compliant (per Tabnine’s own enterprise page)
Amazon Q Developer
AWS
Free; Pro at $19/user/month
VPC interface endpoints via AWS PrivateLink; inherits AWS’s compliance programs
Covered under AWS’s shared-responsibility compliance program (SOC, ISO, etc. at the AWS platform level)
Short Verdict
Devin (the product formerly known as Windsurf) is now the most compliance-forward of the three on paper, with SOC 2 Type II and ISO 27001 certification across cloud, desktop, and CLI, plus a FedRAMP High push underway — but it arrived there through two rebrands in under two years, which is worth weighing against stability. Tabnine remains the most deployment-flexible option, with genuine on-premises and air-gapped VPC installs, though its published compliance claims are thinner than its rivals’. Amazon Q Developer is the easiest sell for teams already standardized on AWS, inheriting AWS’s compliance programs and VPC networking rather than building its own from scratch, at the simplest published per-seat price of the three ($19/user/month for Pro).
What Happened to Codeium and Windsurf
This history matters for anyone evaluating the product today. Codeium launched as an AI code-completion tool, rebranded to Windsurf as it pushed into agentic editing, and became one of the most talked-about AI IDEs of 2025 — talked about partly because Google licensed Windsurf’s technology and hired several of its top researchers mid-year, leaving the standalone company in a weakened position. Cognition, the startup behind the autonomous coding agent Devin, acquired what remained of Windsurf in December 2025 for a reported $250 million. On June 2, 2026, Cognition shipped an over-the-air update that rebranded the Windsurf editor as “Devin Desktop”: existing accounts, plans, extensions, and keybindings carried over, but Windsurf’s built-in agent, Cascade, was retired in favor of “Devin Local,” a Rust-rewritten agent Cognition says uses roughly 30% fewer tokens and can spawn subagents. The practical upshot: there is no more “Codeium (Windsurf)” enterprise product to evaluate on its own terms — it’s now a surface inside Cognition’s broader Devin platform, alongside cloud Devin and a CLI.
What Each Platform Actually Offers
Devin / Devin Desktop now spans three surfaces — Cloud, Desktop, and CLI — and supports the Agent Client Protocol (ACP), which lets outside agents such as Codex or Gemini CLI run inside the editor rather than locking you into one vendor’s model. On the enterprise side, Devin’s security documentation states SOC 2 Type II and ISO 27001 certification across all surfaces, with FedRAMP High “in progress” for CLI/Desktop and Cloud. Enterprise deployment connects to internal systems via AWS PrivateLink or IPSec, with an outbound-only policy gateway (“Devin Connect”), and the vendor says single-tenant, region-pinned hosting is available on request. Devin Enterprise also supports self-hosted source control systems directly — GitHub Enterprise Server, GitLab self-managed, Azure DevOps Server, Bitbucket Data Center, Gerrit, and Perforce — which matters for codebase-aware features in locked-down environments. Pricing is published up to the Teams tier ($80/month plus $40/month per full seat, up to 200 users); Enterprise is quote-only.
Tabnine positions itself explicitly as “the AI code assistant that you control,” and deployment flexibility is its central pitch: Tabnine can run as a secured multi-tenant SaaS, fully on-premises, or isolated inside your own VPC with no outbound connectivity required. Its enterprise page states it doesn’t train on your code unless you explicitly connect your codebase, and that connected code stays inside your environment. Tabnine publishes SOC 2 compliance but its own enterprise materials don’t list ISO 27001, HIPAA, or FedRAMP, so compliance-sensitive buyers should confirm current certification status directly with Tabnine rather than assuming parity with Devin or AWS. IDE coverage includes VS Code, the JetBrains family (IntelliJ, PyCharm, WebStorm, and others), Eclipse, and Sublime. Tabnine does not publish per-seat enterprise pricing on its public site; it’s sold through a sales conversation.
Amazon Q Developer is the clearest fit for teams already deep in AWS. Its Free tier includes 50 agentic requests a month and 1,000 lines of code per user for Java upgrade transformations; Pro, at $19 per user per month, raises those limits, adds an admin dashboard with IAM Identity Center integration, automatic opt-out of data collection, and IP indemnity. Q Developer supports VPC interface endpoints through AWS PrivateLink, so traffic can stay off the public internet, and it inherits AWS’s existing compliance programs under the standard shared-responsibility model rather than publishing its own separate certification list — which is a meaningfully different compliance story than a vendor certifying its own product independently, and worth clarifying with your compliance team if you need a certification that names Q Developer specifically rather than “AWS” broadly.
Pros and Cons
Devin / Devin Desktop
Pros: Strongest published compliance posture (SOC 2 Type II + ISO 27001 on all surfaces, FedRAMP High in progress); supports self-hosted source control directly; ACP support avoids lock-in to one model vendor.
Cons: Two rebrands in under two years (Codeium → Windsurf → Devin Desktop) raise legitimate continuity questions; Enterprise pricing isn’t published; no on-premises option, only VPC/dedicated hosting.
Tabnine
Pros: True on-premises and air-gapped VPC deployment; broad, mature IDE support including Eclipse and Sublime; strong “your code stays yours” data-handling stance.
Cons: No public pricing; thinner published compliance-certification list than Devin or AWS; less agentic/autonomous capability positioning than Devin.
Amazon Q Developer
Pros: Simple, published per-seat pricing ($19/user/month Pro); VPC PrivateLink support; inherits AWS’s broad compliance program rather than building one from scratch; tight integration with other AWS services.
Cons: Compliance is inherited at the AWS-platform level, not independently certified for Q Developer specifically; most natural fit is inside the AWS ecosystem rather than as a standalone, cloud-agnostic tool.
Who It’s a Good Fit For
Choose Devin/Devin Desktop if you want the most agentic, autonomous workflow and can live with quote-only enterprise pricing and a security program that’s still completing FedRAMP High. Choose Tabnine if your compliance or infrastructure team requires a genuinely air-gapped, on-premises deployment with no outbound network dependency. Choose Amazon Q Developer if your organization already standardizes on AWS and wants predictable per-seat pricing with compliance handled under your existing AWS agreements.
Who Should Look Elsewhere
If brand stability matters to your procurement process, Devin’s rapid rebranding history (three names in roughly two years) is worth flagging to stakeholders before you commit. If you need a published, comparable enterprise price point without a sales call, Tabnine’s lack of public pricing may be a dealbreaker. And if you’re multi-cloud or cloud-agnostic by policy, Amazon Q Developer’s AWS-centric compliance and integration story may be a poorer fit than Devin or Tabnine.
Bottom Line
“Codeium (Windsurf)” as a distinct product is already history by late 2026 — it’s Devin Desktop now, inside Cognition’s broader agent platform, with a genuinely strong compliance story to show for the turbulence. Tabnine remains the deployment-flexibility specialist for teams that need true on-premises isolation. Amazon Q Developer is the low-friction default for AWS-committed organizations. None of the three is a universal “best” — match the choice to whether your constraint is agentic capability, deployment isolation, or cloud-platform alignment.
FAQ
Is Windsurf still a separate product from Devin? No. As of June 2026, Cognition rebranded the Windsurf editor as “Devin Desktop,” retiring the Windsurf name and its built-in Cascade agent in favor of Devin Local. Existing Windsurf accounts and plans carried over automatically.
Does Tabnine support fully offline, air-gapped deployment? Tabnine’s own enterprise materials describe running “fully isolated” in your VPC or on-premises, which is the strongest offline/air-gapped positioning of the three tools compared here.
What does Amazon Q Developer Pro cost per seat? $19 per user per month, billed with the first month prorated from activation. The Free tier has no per-seat charge but caps agentic requests at 50 per month.
Is Devin Enterprise FedRAMP certified? Not yet as of this writing. Devin’s security documentation lists FedRAMP High as “in progress” for its CLI, Desktop, and Cloud surfaces, alongside completed SOC 2 Type II and ISO 27001 certification.
Which of these three publishes clear enterprise pricing? Only Amazon Q Developer publishes a specific enterprise-relevant per-seat price ($19/month for Pro). Devin publishes pricing up to its Teams tier but not Enterprise; Tabnine doesn’t publish enterprise pricing at all.
While AWS’s Trainium and Inferentia chips get most of the attention as the hardware behind Amazon’s AI ambitions, a quieter custom-silicon program has been reshaping something more fundamental: the general-purpose CPU inside ordinary EC2 instances. That’s Graviton — AWS’s Arm-based processor family — and by 2026 it’s running a meaningful share of all new compute AWS customers deploy. Here’s what Graviton actually is, how its five generations compare, and what AWS’s own published numbers say about the price-performance case for switching from x86.
At a Glance
Spec
Detail
What it is
AWS’s custom Arm-based CPU family for general-purpose EC2 compute
Current generation
Graviton5 (192 cores, Arm Neoverse V3, 3nm process, GA June 2026)
Cost claim vs. comparable x86 EC2
Up to 20% lower cost (AWS’s own published figure)
Energy claim vs. comparable x86 EC2
Up to 60% less energy use (AWS’s own published figure)
Adoption
More than 120,000 AWS customers building on Graviton, per AWS
Key instance families
T4g, M6g/M7g/M8g/M9g, C6g/C7g/C8g, R6g/R7g/R8g, X2gd/X8g, I4g/I8g, and more
Conceptual competitors
Google Axion (Google Cloud), Nvidia Grace (hybrid CPU/GPU systems)
What AWS Graviton Is
Graviton is AWS’s own line of server CPUs built on the Arm instruction set rather than the x86 architecture that Intel and AMD chips use. Unlike Trainium (built for AI training) or Inferentia (built for AI inference), Graviton is a general-purpose processor — it runs ordinary EC2 virtual machines, the kind that host web servers, databases, microservices, and increasingly, agentic AI application logic that isn’t itself doing the heavy model math. AWS designs Graviton in-house and only offers it inside its own infrastructure; you can’t buy a Graviton chip for your own data center the way you can buy an Nvidia GPU or an AMD EPYC chip.
The pitch, repeated consistently across every Graviton generation, is “best price-performance” rather than “fastest at any cost.” AWS backs that with two headline figures on its official Graviton page: Graviton-based instances cost up to 20% less than comparable x86-based EC2 instances, and use up to 60% less energy for the same work.
Graviton Generations Compared
Generation
Announced
Cores
Core architecture
Representative EC2 families
Graviton (1st gen)
2018
16
Arm Cortex-A72
A1
Graviton2
2019
64
Arm Neoverse N1
M6g, C6g, R6g, T4g, X2gd, I4g
Graviton3 / 3E
2021 / 2022
64
Arm Neoverse V1
C7g, C7gd, M7g, M7gd, R7g, R7gd, C7gn, Hpc7g
Graviton4
2023
96 per socket
Arm Neoverse V2
C8g, M8g, R8g, X8g, I8g
Graviton5
2025 (GA June 2026)
192
Arm Neoverse V3
M9g, M9gd
Graviton5 is the newest and largest jump in the lineup: 192 cores on a 3nm process, a roughly 5x larger L3 cache than Graviton4 (2.6x more cache per core), up to 33% lower inter-core latency, DDR5-8800 memory, and PCIe Gen 6 I/O. It’s built on AWS’s sixth-generation Nitro System, which handles virtualization, storage, and networking offload outside the main CPU — a security and performance architecture AWS has carried through every Graviton generation. According to AWS, Graviton5-based M9g instances deliver up to 25% better compute performance than Graviton4, with web applications and ML inference workloads seeing roughly 35% improvements and databases around 30%.
Which EC2 Instance Families Use Graviton
AWS maps each Graviton generation onto a parallel set of EC2 instance families alongside their x86 equivalents — a “g” suffix marks the Arm/Graviton version (for example, M7g is the Graviton3 counterpart to the x86 M7i). The main families span three traditional categories:
General purpose (M-series): M6g through M9g — balanced compute and memory for web servers, app servers, and mid-size databases.
Compute optimized (C-series): C6g through C8g — higher compute-to-memory ratio for batch processing, media encoding, and scientific modeling.
Memory optimized (R-series/X-series): R6g through R8g, plus X2gd and X8g — for in-memory databases and caching layers.
Storage/local-NVMe optimized: I4g/I8g and the “d” variants like M9gd, which pair Graviton compute with fast local disk for storage-heavy workloads.
Burstable (T-series): T4g — the low-cost, burstable-performance option often used for dev/test environments and light web traffic.
AWS also extends Graviton into its managed services — Aurora, RDS, ElastiCache, OpenSearch, and EMR all offer Graviton-backed options, so adopting Graviton doesn’t require managing raw EC2 instances directly.
Real-World Adoption
AWS states that more than 120,000 customers are now building on Graviton. Specific examples AWS has cited include Pinterest, which runs Graviton-based infrastructure serving more than 500 million monthly active users; Meta, which has committed to deploying tens of millions of Graviton cores for agentic AI workloads; and Uber and Snowflake, both named as deploying Graviton for agentic AI use cases. Partner performance claims reported alongside the Graviton5 launch include Airbnb citing up to 25% better performance over comparable same-generation x86 architectures in production search workload testing, Atlassian reporting 30% higher performance and 20% lower latency running Jira on Graviton5-based M9g versus the prior generation, and SAP citing 35–60% improvement in OLTP query performance for SAP HANA Cloud on M9g.
How Graviton Compares to Google Axion and Nvidia Grace
Graviton isn’t the only custom Arm-based server chip in the cloud. Google Cloud’s Axion processor follows a similar playbook — a custom Arm Neoverse-based CPU built in-house and pitched on price-performance for general-purpose cloud workloads, analogous to Graviton’s role inside AWS. Nvidia’s Grace chip takes a different approach: it’s also an Arm-based CPU, but Nvidia designs it primarily to pair tightly with its own GPUs (as in the Grace Hopper and Grace Blackwell superchips) for AI and HPC workloads, rather than as a general-purpose EC2-style instance CPU competing on its own. In short, Graviton and Axion compete head-on as “cloud-provider house-brand Arm CPU for everyday compute,” while Grace plays a more specialized role bolted onto Nvidia’s GPU-centric AI stack — a distinction worth keeping in mind before assuming all three are interchangeable just because they’re all Arm-based.
Trade-Offs
Graviton’s biggest practical trade-off is software compatibility. Arm and x86 are different instruction set architectures, so any software with compiled x86-specific binaries, kernel modules, or dependencies needs an Arm-compatible build. Most mainstream Linux distributions, container base images, and managed-language runtimes (Java, Python, Node.js, Go) now ship native Arm builds, which is a big part of why Graviton adoption accelerated — but legacy applications, some proprietary third-party software, and x86-specific compiled extensions can still require rework or simply aren’t available on Arm. AWS’s own trial program (free t4g.small hours through the end of 2026, per its Graviton page) exists partly to lower the barrier to testing that compatibility before committing production workloads.
Bottom Line
Graviton has moved from a niche cost-saving option to a mainstream default across much of AWS’s EC2 lineup, backed by AWS’s own published claims of up to 20% lower cost and up to 60% less energy use versus comparable x86 instances, plus genuine adoption numbers in the hundreds of thousands of customers. Graviton5’s jump to 192 cores and a substantially larger cache puts clear distance between it and Graviton4, and the main real-world question for most teams isn’t whether Graviton is cheaper — AWS’s figures and partner testimonials are consistent on that point — but whether your specific software stack is Arm-ready. For anything running mainstream open-source software, the honest answer in 2026 is usually yes.
FAQ
Is Graviton the same as Trainium or Inferentia? No. Graviton is a general-purpose CPU for ordinary EC2 compute. Trainium and Inferentia are AWS’s separate custom chips built specifically for AI model training and inference, respectively.
How much cheaper is Graviton than x86 on AWS? AWS’s own Graviton page states Graviton-based instances cost up to 20% less than comparable x86-based EC2 instances, with up to 60% lower energy use for the same work. Actual savings vary by workload and instance family.
Do I need to rewrite my application to use Graviton? Usually not a full rewrite, but you do need an Arm-compatible build of your software stack. Most modern Linux distributions, container images, and language runtimes support Arm natively; older or x86-specific binaries may need to be recompiled or replaced.
Can I buy a Graviton chip for my own servers? No. Graviton is proprietary AWS silicon available only inside AWS’s own cloud infrastructure, unlike general-purpose chips from Intel, AMD, or Ampere.
Is Graviton5 generally available now? AWS previewed Graviton5 at re:Invent 2025 and announced general availability in June 2026, with M9g (general purpose) and M9gd (local NVMe storage) as the first instance families built on it.
Async video — recording your screen and face instead of scheduling a live call — has become a default part of how distributed teams communicate in 2026. Loom popularized the category, Vidyard pushed it toward sales and marketing use cases with AI avatars, and ScreenPal (formerly Screencast-O-Matic) kept pricing low for individuals and classrooms. All three now bundle some form of AI transcription or avatar generation, but at very different price points and with very different free-tier limits.
At a Glance
Spec
Loom
Vidyard
ScreenPal
Cheapest paid individual plan
Business: $18/user/mo
Starter: $59/seat/mo (annual)
Solo Deluxe: ~$3/mo
Free plan?
Yes — Starter, 25 videos/person
Yes — 5 recorded videos/mo, 30 min limit
Yes, limited features
AI transcripts/summaries
Business + AI tier ($24/user/mo)
AI script generator + custom avatars
Automated captions on paid tiers
Team video library
Yes, all tiers
Video hubs on Teams/Enterprise
Yes, on Team Business plan
Best known for
Fastest, simplest async video loop
AI avatars for sales/marketing outreach
Lowest cost per seat, classroom/education use
Short Verdict
Loom remains the simplest, fastest tool for everyday async updates between colleagues, and its Business + AI tier bundles auto-generated titles, summaries, and chapters for $24/user/month. Vidyard is built for a different job — generating and sending AI-avatar sales and outreach videos at scale — and prices accordingly, with its cheapest named-price tier starting at $59/seat/month. ScreenPal is the budget pick for individuals, educators, and small teams who need solid screen recording and editing without per-seat SaaS pricing; its flat per-plan rates (not per-user on the Solo tiers) make it dramatically cheaper for a single creator.
What Each One Is
Loom (owned by Atlassian) is built around one core loop: record your screen and webcam, get an instant shareable link, and let the viewer watch on their own time. Its AI tier adds automatic titles, summaries, chapters, filler-word removal, and meeting recaps on top of that core loop.
Vidyard started as a B2B video hosting and analytics platform and has leaned hard into AI avatars — letting a sales rep generate a personalized outreach video using a synthetic version of themselves, with detailed viewer analytics attached to every send. It’s priced and positioned more toward revenue teams than general internal communication.
ScreenPal is a screen recorder and video editor first, with sharing and hosting features layered on top. Its pricing is structured around individual “Solo” plans (flat monthly rate, not per seat) and separate education and team tiers, which makes it the cheapest option for a single freelancer, teacher, or support agent who mainly needs to record and edit, not run a company-wide video communication platform.
Pricing Breakdown
Plan
Price
Key features
Loom Starter
$0
25 videos/person, 5-min recordings, 720p, up to 50 members
Adds interactive video Q&A/polls, analytics, SSO/SAML, team management
A note on Vidyard’s add-on: its Video Agent feature (fully automated AI video generation at scale) is priced separately from the base Starter/Teams/Enterprise plans — budget an additional $29/seat/month ($24 billed annually) if you want that automation layer. ScreenPal’s published per-month rates reflect its flat-rate plan structure as listed by the vendor’s own rate card; ScreenPal’s live site did not load directly for us at the time of writing, so confirm current pricing and whether it’s billed monthly or annually directly on screenpal.com/pricing before purchasing.
Pros and Cons
Loom
Pros: fastest recording-to-share loop, strong AI summary/chapter features, familiar to most knowledge workers already
Cons: per-user pricing adds up fast for large teams, AI tier is a separate, pricier plan rather than an add-on
Vidyard
Pros: best-in-class AI avatar and personalized outreach video tools, deep CRM/marketing integrations on higher tiers, detailed viewer-level analytics
Cons: most expensive entry-level paid tier of the three, Video Agent AI automation is a separate paid add-on, Teams/Enterprise pricing requires a sales conversation
ScreenPal
Pros: by far the cheapest per-seat cost, flat individual pricing instead of per-user SaaS billing, strong fit for educators and solo creators
Cons: less sophisticated AI features than Loom or Vidyard, team tier requires a 3-seat minimum, lighter on CRM/marketing integrations
Who It’s a Good Fit For
Choose Loom if: your team needs a fast, familiar way to replace short meetings with async video updates and wants AI-generated summaries without extra setup.
Choose Vidyard if: you’re in sales or marketing and want AI-avatar outreach videos with detailed per-viewer analytics tied into your CRM.
Choose ScreenPal if: you’re an individual creator, educator, or small team on a tight budget who mainly needs reliable screen recording and basic editing.
Who Should Look Elsewhere
If your main need is actual video editing — multi-track timelines, color grading, motion graphics — rather than screen recording and sharing, look at a dedicated editor instead; see our Best Video Editing Software in 2026 comparison. And if you need live, synchronous video meetings rather than recorded async clips, none of these three tools replaces a proper video conferencing platform.
Bottom Line
These three tools now overlap less than their shared “screen recording” label suggests. Loom is the general-purpose async communication default, Vidyard is a sales/marketing AI-video platform wearing a screen recorder’s clothing, and ScreenPal is the budget-friendly recorder-and-editor for individuals and small teams. Pick based on the job, not just the price.
FAQ
Which of these has the best free plan? Loom’s free Starter plan (25 videos per person, 5-minute recordings) and Vidyard’s free plan (15 AI videos, 5 recordings/month) are both usable for light, individual use. ScreenPal also offers a free tier, though with more limited editing features than its paid plans.
Do any of these include AI avatars? Vidyard includes custom AI avatars starting on its free plan and expands avatar/automation features on paid tiers. Loom and ScreenPal focus on real-face/screen recording rather than synthetic avatars.
Is ScreenPal the same company as Screencast-O-Matic? Yes — Screencast-O-Matic rebranded to ScreenPal. Some third-party pricing pages and reviews still reference the old name.
Which is cheapest for a 10-person team? ScreenPal’s Team Business plan is the cheapest per-seat of the three at roughly $8/user/month. Loom Business runs $18/user/month, and Vidyard’s named Starter tier is priced per seat at $59–89/month, with its Teams tier (built for 5+ seats) requiring a custom quote.
Every monorepo build system solves the same core problem — don’t rebuild or retest what hasn’t changed — but Nx, Turborepo, and Bazel solve it with completely different levels of rigor, and that difference shows up the moment your repo grows past a handful of packages. Here’s what each one actually does, based on their own documentation and sites, and which one fits which scale of problem.
At a Glance
Tool
Maintained by
Caching model
Language support
Best fit
Nx
Nx (Narwhal Technologies)
Local + remote (Nx Cloud); tracks actual file reads/writes with “Ultracache”
Polyglot: first-class JS/TS, .NET, Java; community plugins for Python, Rust, Go, PHP
Small teams to large orgs wanting fast adoption without rewriting build config
Turborepo
Vercel
Local + Remote Cache; built on existing package.json scripts
JS/TS-oriented; works with npm, Yarn, pnpm
JS/TS monorepos wanting a lightweight, low-config speed layer
Bazel
Google (open-sourced 2015, from internal “Blaze”)
Hermetic local + distributed/remote caching and remote execution
Multi-language by design: Java, C++, Go, Android, iOS, and more via rules
Large, polyglot, or extremely large-scale monorepos where correctness and reproducibility matter most
Short Verdict
Turborepo is the fastest to adopt if you already have a JavaScript or TypeScript monorepo with working npm/Yarn/pnpm scripts — it layers caching on top of what you have in minutes. Nx goes further: it understands your project graph, orchestrates task ordering automatically, and now ships CI-specific features like splitting test suites across machines and auto-retrying flaky tasks. Bazel is the heaviest lift of the three but the only one built from the ground up for hermetic, reproducible builds across multiple languages at the scale Google itself operates at — which is exactly where it came from.
What Each Tool Actually Does
Nx positions itself as a monorepo platform for both developers and AI coding agents. Locally, it runs only the tasks a given change affects and serves everything else from cache; Nx Cloud adds remote caching across a team and CI. Its newer “Ultracache” feature tracks which files a task actually reads and writes at runtime rather than relying solely on inputs declared in config, which lets it safely cache tasks even inside one large application instead of requiring you to split everything into small packages. On the CI side, Nx Cloud can split large test suites into smaller units and pack them onto fewer machines (“Dynamic Task Packing”), split end-to-end suites by spec file, and retry flaky tasks automatically. Nx’s own case study with Hetzner Cloud cites 116+ projects, an 85% cache hit rate, and CI time cut from 45 minutes to 6.
Turborepo, maintained by Vercel, is deliberately narrower in scope. It calls itself “the build system for coding agents” and works by reading your existing package.json scripts and a single turbo.json config file — there’s very little new syntax to learn. It schedules tasks to run in parallel across available cores, handles ordering (build before test before lint), and its Remote Cache stores task outputs so CI doesn’t repeat work that’s already been done elsewhere. Turborepo doesn’t publicly document a multi-language story the way Nx or Bazel do; its own docs frame it around npm/Yarn/pnpm workspaces, which makes it squarely a JavaScript/TypeScript tool rather than a general-purpose polyglot build system.
Bazel started as Blaze, Google’s internal build tool, and was open-sourced in 2015. Its defining idea is hermetic builds: a build’s output should depend only on its declared inputs — source files and pinned tool/dependency versions — never on whatever happens to be installed on the machine running it. Tools are treated like source code and fetched into a sandbox rather than assumed to exist on the host. That property is what makes Bazel’s local and distributed caching trustworthy at scale: if two different machines build the exact same inputs, Bazel can prove the outputs will match and safely reuse a cached result instead of rebuilding. The same property enables remote execution, where build and test actions run on a cluster rather than a single laptop. Bazel supports Java, C++, Go, Android, and iOS out of the box, plus “many other languages and platforms” through its Starlark extension language and a large ecosystem of shared rule sets. Google, Stripe, and Dropbox are cited as users on Bazel’s own site.
A Minimal Example: The Same Idea, Three Config Styles
To see how differently these tools ask you to describe “build this package, then test it, and cache the result,” here’s a stripped-down comparison. This is illustrative shorthand, not a working end-to-end example for any specific repo:
Nx uses a comparable project.json or inferred-tasks model per project, plus a workspace-level nx.json for shared defaults and the task graph. Bazel instead requires an explicit BUILD file per package, declaring every target and its exact dependencies in Starlark:
# BUILD.bazel — explicit targets and dependencies
java_library(
name = "greeter",
srcs = ["Greeter.java"],
)
java_test(
name = "greeter_test",
srcs = ["GreeterTest.java"],
deps = [":greeter"],
)
That extra explicitness is exactly the trade-off: Bazel’s BUILD files give it the precise dependency graph it needs for hermetic, provably-correct caching, but someone has to write and maintain them. Turborepo and Nx infer most of that graph from your existing package manifests, which is faster to adopt but leans on the package manager’s own dependency resolution rather than a build system’s.
Pros and Cons
Nx
Pros: Genuinely polyglot with first-class support beyond JS; strong CI-scaling features (task splitting, flaky-task retries); large plugin ecosystem (140+ integrations claimed); works for small projects and scales to hundreds.
Cons: More configuration surface than Turborepo; full benefit requires Nx Cloud, a paid/hosted component for teams; less proven at Bazel’s extreme scale.
Turborepo
Pros: Minutes to adopt on an existing JS/TS repo; tiny config surface (turbo.json); backed and actively developed by Vercel; low learning curve.
Cons: JS/TS-centric, with no clearly documented multi-language story; lighter orchestration feature set than Nx for large CI fleets; less suited to genuinely huge, polyglot codebases.
Bazel
Pros: Hermetic, provably reproducible builds; true multi-language support in one dependency graph; proven at Google-internal scale and by large external adopters; remote execution, not just remote caching.
Cons: Steep learning curve; requires writing and maintaining explicit BUILD files; migrating an existing repo to Bazel is a real project, not a config tweak; overkill for small teams.
Who It’s a Good Fit For
Choose Turborepo if you have a JS/TS monorepo today and want fast wins with minimal setup. Choose Nx if you’re polyglot (say, a TypeScript frontend plus a .NET or Java backend) or you need CI-level features like automatic test splitting and flaky-task handling as your org grows past a few dozen projects. Choose Bazel if you’re operating at a scale where build correctness and reproducibility across many languages matters more than setup speed — think large platform teams, infrastructure-heavy codebases, or organizations explicitly modeling themselves on Google’s internal practices.
Who Should Look Elsewhere
If your team is small and your repo is pure JS/TS, Bazel’s setup cost almost certainly isn’t worth it — Turborepo or Nx will get you most of the speed with a fraction of the migration effort. If you need deep multi-language support today, Turborepo isn’t the right tool; look at Nx or Bazel instead. And if you don’t yet have CI pain (slow pipelines, redundant rebuilds) none of these tools will feel worth the config overhead — a plain npm/pnpm workspace may be enough for now.
Bottom Line
These three tools aren’t really competing for the same job. Turborepo optimizes an existing JS/TS workflow with minimal ceremony. Nx adds a real task-orchestration and project-graph layer that scales into large, polyglot organizations without demanding a full build-system rewrite. Bazel is the only one of the three built around hermeticity as a first principle, which is also why it asks the most of you upfront. Pick based on how much correctness guarantee you actually need versus how fast you need to move today — not based on which one trends on social media this month.
FAQ
Is Bazel only for Google-scale companies? No, but it’s built for that scale. Bazel’s own site cites Stripe and Dropbox as users alongside Google, and it works for smaller polyglot repos too — the trade-off is the upfront cost of writing explicit BUILD files.
Can I use Turborepo and Nx together? They solve overlapping problems (task caching and orchestration for JS/TS monorepos), so most teams pick one rather than running both. Choosing between them usually comes down to how polyglot your repo is and whether you need Nx’s CI-scaling features.
Does Turborepo support languages other than JavaScript/TypeScript? Its own documentation is built around npm/Yarn/pnpm workspaces and doesn’t lay out a multi-language story the way Nx or Bazel do, so treat it as JS/TS-oriented unless you verify otherwise for your specific case.
What does “hermetic” mean in Bazel’s build model? It means a build’s output depends only on its declared source and configuration inputs, never on whatever is installed on the machine running it — which is what lets Bazel trust a cached result from one machine on a completely different one.
Do I need a cloud/remote caching add-on to benefit from these tools? Local caching alone speeds up a single developer’s machine for all three. The bigger wins — avoiding redundant work across your whole team and CI fleet — require a remote cache: Nx Cloud, Turborepo’s Remote Cache, or Bazel’s remote caching/execution backends.
Every family ends up with the same problem eventually: thousands of photos and videos spread across multiple phones, with no single backup that everyone in the household can see and contribute to. Google Photos, Apple iCloud+, and Amazon Photos all solve this differently — in how they price storage, how many people can share a plan, and how much they lean on a wider ecosystem. Here’s what each one’s official pricing and policy pages say in 2026.
At a Glance
Spec
Google Photos (Google One)
Apple iCloud+
Amazon Photos
Free storage
15 GB (shared across Gmail/Drive/Photos)
5 GB
5 GB photos + videos; unlimited full-res photos for Prime members
Cheapest paid tier
100 GB for $1.99/mo
50 GB for $0.99/mo
100 GB for roughly $1.99/mo (Prime add-on pricing)
Unlimited full-resolution photo storage bundled into Prime
Short Verdict
If your family is already paying for Amazon Prime, Amazon Photos is close to a freebie: full-resolution photo storage is unlimited for Prime members, with only video eating into a small free video allowance. If your household is split between iPhones and Android phones, Google Photos remains the most cross-platform option and its 2 TB family-shareable plan is identically priced to Apple’s. If everyone in the house is on Apple devices already, iCloud+’s deep OS-level integration (automatic backup, Shared Photo Library, Family Sharing) makes it the path of least friction even though its entry tier offers less storage per dollar.
What Each One Is
Google Photos is Google’s photo and video library app, backed by Google One storage plans that also cover Gmail and Google Drive. Every Google account gets 15 GB free, shared across all three services, and paid Google One plans raise that shared quota.
Apple iCloud+ is Apple’s paid storage tier on top of the free 5 GB every Apple ID receives. It covers photo/video backup through the Photos app, plus device backups, Mail, and other iCloud-synced data, and includes privacy features like Private Relay and Hide My Email on top of storage.
Amazon Photos is bundled into every Amazon Prime membership, and its headline feature is unlimited full-resolution photo storage for Prime members — a benefit neither Google nor Apple offers at any price. Video storage, however, is capped unless you buy additional storage.
Pricing Breakdown
Plan
Monthly price
Storage
Family sharing
Google One Basic
$1.99
100 GB
Up to 5 members
Google One Standard
$2.99
200 GB
Up to 5 members
Google One Premium
$9.99
2 TB
Up to 5 members
Google One (higher tiers)
$99.99–$299.99
10 TB–30 TB
Up to 5 members
iCloud+ 50 GB
$0.99
50 GB
Up to 5 family members
iCloud+ 200 GB
$2.99
200 GB
Up to 5 family members
iCloud+ 2 TB
$9.99
2 TB
Up to 5 family members
iCloud+ 6 TB
$29.99
6 TB
Up to 5 family members
iCloud+ 12 TB
$59.99
12 TB
Up to 5 family members
Amazon Photos (Prime)
Included with Prime
Unlimited full-res photos, 5 GB video
Amazon Household sharing
A note on the numbers: Apple’s and Google’s tiers above are confirmed directly from Apple’s and Google’s own support/help documentation. Amazon’s exact paid add-on storage tiers for Amazon Photos beyond the Prime-included allowance were not consistently documented on a single current official page at the time of writing — if you need more than the Prime-included photo/video allowance, check your Amazon account’s storage settings directly for current add-on pricing rather than relying on third-party estimates.
Sharing and Privacy
Both Google One and iCloud+ let a paying member share their storage plan with up to five additional family members, with each person’s own files generally still counted against their own device’s local account first. Apple’s ecosystem adds a “Shared Photo Library” feature specifically for co-managing one combined family photo library across multiple Apple IDs, separate from basic storage sharing. Amazon’s model is different: Prime’s unlimited full-resolution photo benefit applies per Prime member, and Amazon Household lets eligible benefits be shared between two adults, but it isn’t the same five-person family split that Google and Apple offer.
On privacy, all three publish policies stating photos are stored encrypted in transit and at rest, and none of the three claims to use your personal photo library to train generative AI models without consent in their current consumer terms — but policy language and specific opt-in/opt-out AI-training toggles change often enough that it’s worth checking each provider’s current privacy settings directly inside your account rather than assuming last year’s policy still applies.
Pros and Cons
Google Photos / Google One
Pros: works identically on iPhone and Android, storage doubles as Gmail/Drive space, highest tiers scale up to 30 TB
Cons: 15 GB free tier is shared across three services so it fills up fast, no unlimited free tier anymore for any photo type
Apple iCloud+
Pros: cheapest entry tier (50 GB for under $1/mo), deep OS integration, Shared Photo Library for genuinely co-owned family albums
Cons: 5 GB free tier is the smallest of the three, best experience is Apple-device-only
Amazon Photos
Pros: unlimited full-resolution photo storage bundled free with Prime, no separate subscription needed if you already pay for Prime
Cons: video storage is capped unless you pay extra, less polished album/editing tools than Google Photos or Apple Photos, family sharing model is less generous than Google’s or Apple’s five-person split
Who It’s a Good Fit For
Choose Google Photos if: your family uses a mix of Android and iOS devices and you want one backup that works the same everywhere.
Choose iCloud+ if: your household is all-Apple and you want backups, device storage, and a genuinely shared family library handled automatically in the background.
Choose Amazon Photos if: you already pay for Prime and mainly need unlimited photo backup rather than video-heavy storage.
Who Should Look Elsewhere
Families who shoot a lot of 4K video and need generous video storage without hitting a cap quickly may find all three services’ video allowances tight at the entry tiers — budget for at least the 2 TB tier on Google or Apple if video is a big part of your library. If you want one unified backup for photos, documents, and general files rather than a photos-specific product, a general cloud storage comparison may be more useful — see our Dropbox vs Google Drive vs OneDrive comparison.
Bottom Line
Google Photos and iCloud+ are priced almost identically at every comparable storage tier in 2026 ($9.99/mo for 2 TB on both), so the real decision is ecosystem fit rather than price. Amazon Photos is the outlier: if you’re already a Prime member, its unlimited full-resolution photo storage is effectively free and hard to beat on pure photo-backup value, even if its video allowance and sharing model are more limited.
FAQ
Is Amazon Photos really unlimited for free? Full-resolution photo storage is unlimited for Prime members at no extra cost beyond the Prime subscription itself. Video storage is capped at a small free allowance (5 GB) and requires additional paid storage beyond that.
Can my whole family share one storage plan? Yes, on Google One and iCloud+ — both let the paying subscriber share their storage plan with up to five additional family members. Amazon’s sharing model works through Amazon Household rather than the same five-person storage split.
Which is cheapest for a typical family’s 2 TB of photos and videos? Google One and iCloud+ both charge $9.99/month for 2 TB, so they’re tied on headline price at that tier. The deciding factor is usually which ecosystem (Android/Google vs. Apple) your family’s devices already live in.
Do these services use my photos to train AI? Check each provider’s current privacy settings directly, since AI-training opt-in/opt-out policies for photo libraries have changed across the industry and specific terms can shift. None of the three currently states in its consumer terms that personal photo libraries are used for AI training without user control, but confirm current settings in your own account.
Zendesk, Freshdesk, and Help Scout all solve the same basic problem — turning scattered customer emails into a shared, trackable queue — but they price and position themselves very differently in 2026. Zendesk leans enterprise with AI add-ons billed separately; Freshdesk undercuts it on price while bundling its Freddy AI agent; Help Scout stays simpler and per-user, aimed at teams that want less admin overhead. Here’s what each one’s own pricing page actually says.
At a Glance
Spec
Zendesk
Freshdesk
Help Scout
Cheapest paid tier
Support Team: $19/agent/mo (annual)
Growth: $19/agent/mo (annual)
Standard: $25/user/mo
Free plan?
No
No (free trial only)
Yes — 5 users, 1 inbox
Built-in AI agent
Add-on (Copilot, custom pricing)
Freddy AI Agent, 500 free sessions/mo included
AI Inbox assistant included from Standard
Top self-serve tier
Suite Professional: $149/agent/mo (monthly)
Enterprise: $89/agent/mo (annual)
Pro: $75/user/mo
Best known for
Deep enterprise feature depth
Value-for-money with built-in AI
Simplicity, shared-inbox feel
Short Verdict
Freshdesk currently offers the best combination of price and AI functionality for small and mid-sized teams — its Growth and Pro tiers match Zendesk’s entry pricing while including a usable AI agent instead of charging extra for one. Zendesk remains the deepest platform once you need omnichannel routing, advanced reporting, and a large app ecosystem, but its AI add-on (Copilot) and highest tier require talking to sales. Help Scout is the best fit for small teams who find Zendesk and Freshdesk’s admin panels overwhelming and just want a clean shared inbox that still has real automation underneath.
What Each One Is
Zendesk is the most established enterprise helpdesk platform, built around tickets, triggers/automations, and — on its Suite plans — omnichannel messaging, live chat, and telephony in one system. Its pricing page separates “Support Team” (ticketing only) from the “Suite” tiers that add messaging and knowledge base tools.
Freshdesk, from Freshworks, targets the same market at a lower price point and bundles its Freddy AI Agent — which can resolve tickets automatically — into every paid plan, with a free monthly session allowance rather than a separate add-on fee.
Help Scout positions itself as the anti-enterprise-helpdesk: a shared inbox that still supports live chat, SMS, and multiple channels, but with a flatter learning curve and a free tier for very small teams.
Zendesk’s Copilot AI add-on price isn’t published on its main pricing page — it’s described as available on “Professional and higher” plans, with pricing handled through sales, so budget for a custom quote if you want Zendesk’s AI layer. Freshdesk’s page shows annual pricing clearly but doesn’t display monthly-billing rates in its main content, so confirm the monthly rate directly on the page’s toggle before buying if you need month-to-month billing. Help Scout also offers a 16% discount for annual billing on top of the monthly per-user prices shown above.
Pros and Cons
Zendesk
Pros: deepest feature set at the top end, mature app marketplace, strong reporting and SLA tooling
Cons: AI (Copilot) is a separately quoted add-on, Enterprise tier requires a sales call, most expensive of the three at equivalent feature depth
Freshdesk
Pros: AI agent bundled into every paid plan with a real free-session allowance, cheapest path to a usable multi-agent helpdesk, Enterprise tier is still self-serve priced
Cons: no free plan, fewer omnichannel options than Zendesk Suite out of the box, monthly (non-annual) pricing isn’t published up front
Help Scout
Pros: genuinely usable free plan for tiny teams, simplest learning curve of the three, HIPAA compliance available on Pro
Cons: highest per-user starting price of the three ($25 vs $19), fewer deep customization/automation options than Zendesk at the top tier
Who It’s a Good Fit For
Choose Zendesk if: you’re scaling a mid-size or enterprise support org and need omnichannel, telephony, and deep reporting under one roof, and you have budget for custom AI pricing.
Choose Freshdesk if: you want the best price-to-AI-feature ratio and don’t need Zendesk’s full omnichannel depth.
Choose Help Scout if: you’re a small team (or even a 5-person team on the free plan) that wants a shared inbox that feels like email, not an enterprise console.
Who Should Look Elsewhere
If your primary channel is live chat on a marketing site rather than a dedicated support queue, a chat-first tool may fit better than any of these three ticketing-first platforms — see our comparison of live chat software for websites. And if support is purely internal (employee IT helpdesk, not customer-facing), a lighter internal ticketing tool may be cheaper than any of these three customer-support platforms.
Bottom Line
For most small-to-mid-size teams in 2026, Freshdesk’s Growth or Pro plan delivers the best balance of price and built-in AI. Teams that will eventually need Zendesk’s full omnichannel and telephony depth should expect to pay more and negotiate AI pricing separately. Teams prioritizing simplicity over feature depth should start with Help Scout’s free plan and upgrade only when they outgrow it.
FAQ
Which of the three has a genuinely free plan? Only Help Scout, which includes 5 users, 1 inbox, and 1 knowledge base site at no cost. Zendesk and Freshdesk both require a paid plan after their free trial ends.
Does AI cost extra on all three? No — Freshdesk and Help Scout both bundle an AI assistant into their paid plans (Freshdesk’s Freddy AI Agent includes 500 free sessions/month; Help Scout’s AI Inbox assistant is included from Standard). Zendesk’s Copilot AI layer is a separate add-on with pricing handled through sales.
Can I switch between monthly and annual billing later? All three publish meaningfully lower per-agent prices for annual billing versus paying month-to-month; check each vendor’s pricing page for the exact monthly-billing premium, since Freshdesk in particular doesn’t show that number on its main pricing page.
Which is cheapest for a 10-agent team? At entry tiers, Zendesk Support Team and Freshdesk Growth are both $19/agent/month on annual billing — effectively tied. Freshdesk’s Growth plan includes a bundled AI agent at that price, which Zendesk’s equivalent tier does not.
“Encrypted email” means two very different things depending on which vendor you ask. Proton Mail and Tuta (formerly Tutanota) replace your email service outright, giving every user a new inbox where messages are end-to-end encrypted by default. Virtru takes the opposite approach: it layers encryption on top of the Gmail or Outlook inbox you already run, as a browser extension or add-in, so nobody has to migrate anything. Both approaches are legitimate for business use in 2026 — they just solve different problems, and picking the wrong one means either a painful migration you didn’t need or a false sense of security from a tool that isn’t actually protecting your existing mail flow.
Freelancers and EU-based teams wanting data sovereignty
Virtru
Encryption layered onto Gmail/Outlook
$119/month for 5 users (Starter, billed annually)
Organizations that must keep using Gmail/Microsoft 365 but need compliance-grade encryption
The Short Verdict
If you can move your whole team’s inbox, Proton Mail’s Workspace plans buy you end-to-end encrypted mail, calendar, drive, and VPN under one roof starting at $12.99 per user per month, with HIPAA and GDPR support built in. Tuta undercuts Proton on price (business plans start around €6/user/month) and stores everything in German, ISO 27001-certified data centers, but it’s a smaller company with a smaller ecosystem around it. If migrating off Gmail or Microsoft 365 is a non-starter — which it is for most mid-size and large organizations — Virtru is the more realistic choice: it bolts message- and file-level encryption onto the inbox people already use, starting at $119/month for five users, and it’s the only one of the three with published compliance tiers reaching CMMC, FedRAMP, and ITAR.
What It Is: Two Different Architectures
Proton Mail is a Swiss-based, standalone email provider built around end-to-end and zero-access encryption — Proton’s own servers can’t read stored mail content because the decryption keys live with the user. Messages between two Proton Mail users are encrypted automatically; sending encrypted mail to someone on Gmail or Outlook requires either a password-protected message link or the recipient getting their own Proton-compatible setup. Proton’s business pricing, per its own plans page, now centers on Workspace Standard at $12.99/user/month (billed yearly at $155.88, a 13% discount off the $14.99 monthly list price) and Workspace Premium at $19.99/user/month ($239.88/year, 20% off $24.99). Standard includes 1 TB of mail storage per user, up to 15 custom email domains, 20 addresses per user, GDPR and HIPAA compliance support, and compatibility with Outlook, Thunderbird, and Apple Mail via Proton’s bridge. Premium adds 3 TB of storage, 20 domains, and data-retention policy controls. An Enterprise tier is custom-quoted.
Tuta takes the same standalone-service approach but is based in Germany and markets itself hard on data sovereignty and post-quantum-ready encryption. According to Tuta’s own published business pricing, the three tiers are Essential at €6/user/month (50 GB storage, 3 custom domains, aimed at freelancers), Advanced at €8/user/month (500 GB, 10 domains, aimed at teams and SMEs), and Unlimited at €12/user/month (1,000 GB, unlimited custom domains, aimed at large businesses, and the only tier with email import). Tuta encrypts the subject line, body, attachments, calendar, and contacts end-to-end, says it’s moving toward quantum-safe encryption, stores data in ISO 27001-certified German data centers, and publishes a 99.95% uptime SLA along with a standard GDPR data processing agreement.
Virtru doesn’t replace your email provider at all. It’s an add-on for Gmail and Microsoft 365/Outlook that encrypts individual messages and attachments using the Trusted Data Format (TDF), an open standard Virtru co-created, and lets senders set expiration dates or revoke access after the fact — without forcing recipients to create a new account or use a separate inbox. Per Virtru’s own pricing page, Starter costs $119/month for 5 users (about $24/user/month) billed annually, and includes encrypted email and attachments, Microsoft 365/Google Workspace support, access revocation, and a Business Associate Agreement for HIPAA obligations. Business, at $219/month for 5 users, adds encrypted file sharing, custom branding, Google Vault integration, and support for CCPA, CJIS, EAR, GDPR, and FERPA on top of HIPAA. A Compliance tier at $499/month for 5 users adds CMMC, DFARS 7012, and ITAR support, a FedRAMP ATO at the Moderate level, FIPS 140-3 validated encryption, and PCI DSS-compliant infrastructure — clearly aimed at government contractors and regulated industries. Enterprise is custom-quoted for organizations over 50 employees.
Pricing and Feature Comparison
Feature
Proton Mail (Workspace)
Tuta Business
Virtru
Deployment model
Replaces your email provider
Replaces your email provider
Add-on inside Gmail/Outlook
Entry price
$12.99/user/month
€6/user/month
$119/mo for 5 users (~$24/user)
Top published tier
$19.99/user/month (Premium)
€12/user/month (Unlimited)
$499/mo for 5 users (Compliance)
Storage (entry tier)
1 TB/user
50 GB/user
Not storage-based
HIPAA support
Yes, all business tiers
Not explicitly marketed
Yes, with signed BAA from Starter up
Government-grade (CMMC/FedRAMP/ITAR)
No
No
Yes, Compliance tier
Keeps existing Gmail/Outlook address
No — new inbox
No — new inbox
Yes
Pros
Proton Mail: Mature product bundled with VPN, Drive, and Pass; strong brand trust; HIPAA and GDPR support on every business tier.
Tuta: Lowest published entry price of the three, EU-based data residency, and a security-first roadmap (quantum-safe encryption).
Virtru: No migration — works inside the inbox employees already use; the only option with published CMMC/FedRAMP/ITAR tiers for regulated industries.
Cons
Proton Mail: Encrypting mail to non-Proton recipients still requires a password-protected link workflow, which can confuse external contacts.
Tuta: Smaller ecosystem and support footprint than Proton; less third-party integration documentation available in English-language materials.
Virtru: Doesn’t encrypt an entire mailbox or provider by default — protection is per-message/per-file, so it depends on consistent user behavior (or admin-enforced policies) to be effective everywhere.
Who It’s a Good Fit For
Choose Proton Mail if you’re a small-to-mid-size business willing to migrate to a privacy-first email provider and want encrypted mail, calendar, and storage bundled together. Choose Tuta if budget and EU data residency matter more than ecosystem maturity. Choose Virtru if you’re already committed to Google Workspace or Microsoft 365 — which describes most mid-size and large organizations — and need to add verifiable, auditable encryption and compliance controls (HIPAA, CMMC, FedRAMP) without touching your existing email infrastructure.
Who Should Look Elsewhere
If your organization is legally or contractually locked into Microsoft 365 or Google Workspace, Proton Mail and Tuta aren’t realistic options no matter how good their encryption is — you’d be running a second, parallel inbox. Conversely, if you want every single message automatically end-to-end encrypted with zero reliance on user behavior, Virtru’s per-message model is a weaker fit than Proton’s or Tuta’s default-on encryption.
Bottom Line
There’s no single “best” encrypted email provider for business in 2026 — there’s a best architecture for your situation. Proton Mail and Tuta are the right call when you can move your whole organization’s email and want encryption on by default; Proton costs more but has the broader ecosystem, while Tuta is cheaper and more EU-centric. Virtru is the right call when migration is off the table and you need audited, compliance-grade encryption layered onto the Gmail or Outlook inbox your company already runs.
FAQ
Can I use Proton Mail or Tuta without giving up my Gmail or Outlook address? Not fully. Both are standalone mail services with their own addresses; you can forward or alias mail, but the end-to-end encryption benefit applies to mail sent and received through their systems, not your existing Gmail/Outlook account.
Does Virtru actually encrypt data, or is it just access control? It encrypts the message or file content itself using the Trusted Data Format, then layers access policies (expiration, revocation) on top — so it’s encryption plus policy control, not policy control alone.
Which of these is HIPAA-compliant out of the box? Proton’s business plans and Virtru’s plans (from Starter up, with a signed Business Associate Agreement) both publish HIPAA support. Tuta’s marketing doesn’t prominently cite HIPAA, so healthcare organizations should confirm directly with Tuta before relying on it for PHI.
Is Tuta’s business pricing in euros a problem for US buyers? No — it just means your invoice is denominated in euros and your USD cost will move with the exchange rate; Tuta bills in euros regardless of customer location.
Do any of these work for government contractors specifically? Virtru is the only one of the three with a published tier (Compliance, $499/month for 5 users) explicitly built around CMMC, DFARS 7012, ITAR, and a FedRAMP Moderate ATO.
Oracle’s cloud infrastructure business has gone from an afterthought to one of the most-discussed AI capacity stories in the industry, largely on the strength of a backlog metric most software companies would never let get this large: Remaining Performance Obligations (RPO), the dollar value of contracted revenue Oracle has not yet recognized. That number has become the de facto scoreboard for how much AI compute Oracle has committed to deliver — and how much financial risk comes with it. This piece sticks to what Oracle has actually disclosed in its own earnings materials, flags clearly where the widely reported headline numbers (like the reported $300 billion OpenAI deal) come from press reporting rather than an Oracle-confirmed figure, and explains what the backlog implies for OCI’s GPU buildout.
Press reporting (WSJ and others, Sept. 2025), unverified by Oracle filing
What Oracle Has Actually Disclosed
Oracle’s most recent earnings release (fiscal Q1 2027, covering the quarter ended August 31, 2026, reported September 10, 2026) is the most current primary source available as of this writing, and it is unusually specific for a company that doesn’t typically name AI customers in its press materials. Total revenue came in at $19.3 billion, up 30% year over year in both USD and constant currency. The headline figure, though, is Cloud Infrastructure (OCI/IaaS) revenue, which Oracle reported at $7.4 billion for the quarter — up 121% year over year.
The number that dominated coverage of the release was Remaining Performance Obligations: Oracle reported total RPO of $664 billion, up $209 billion year over year (implying prior-year RPO of roughly $455 billion, based on simple arithmetic from the two disclosed figures, not a percentage Oracle itself stated). Oracle attributed the jump specifically to booking “more than $30 billion of additional AI cloud contracts” during the quarter. Oracle also disclosed that it delivered more than 300,000 GPUs to AI Cloud customers since the end of the prior quarter — almost triple the capacity it delivered in the quarter before that — which is as close as the company gets to a physical-capacity proof point behind the RPO number. Oracle’s guidance for the following quarter (Q2 FY27) calls for total cloud revenue growth of 64% to 70% in constant currency, and full fiscal-year 2027 total revenue of at least $90 billion.
Notably, Oracle’s press release does not name individual AI customers behind these contracts, and it does not break out capital expenditure figures tied specifically to the AI buildout in the release itself; the company reported free cash flow of negative $5 billion for the quarter, which it attributed to investment supporting cloud infrastructure growth, alongside $23 billion of operating cash flow and $20 billion raised through an at-the-market common stock program.
What’s Reported, But Not Oracle-Confirmed
The number most people associate with this story — a roughly $300 billion, multi-year cloud computing deal between Oracle and OpenAI tied to Project Stargate — comes from reporting by outlets including the Wall Street Journal, citing people familiar with the agreement, in September 2025, and has been repeated widely since. It is a credible, widely corroborated report from reputable outlets, but it is not a figure Oracle itself has confirmed in a press release or SEC filing naming OpenAI as the counterparty and $300 billion as the contract value. Oracle’s own earnings materials describe AI cloud contract bookings only in aggregate and do not name which customers they’re with. Readers should treat the $300 billion OpenAI figure as credibly reported, not as an Oracle-disclosed fact, and the same caution applies to any other customer-specific dollar figures circulating in coverage of Oracle’s AI backlog that don’t trace back to an Oracle press release, 10-K, or 10-Q.
What RPO Actually Measures — and Its Limits
RPO is contracted, unrecognized revenue — a backlog, not cash in hand and not yet-earned revenue. It tells you Oracle has signed agreements obligating customers to pay for a certain amount of future cloud capacity, but it does not tell you the payment schedule, the credit quality of every counterparty, or how much of that capacity Oracle can physically build and deliver on the timeline the contracts assume. A large RPO number is genuinely a sign of real demand, but it’s also a number Oracle itself can influence through how aggressively it pursues long-duration, large-dollar-value contracts versus shorter, smaller ones — and analysts and financial press have flagged that funding a buildout this large requires Oracle to raise substantial capital (debt and equity, including the $20 billion at-the-market stock sale disclosed this quarter) ahead of actually recognizing the revenue those contracts represent. That’s a normal, disclosed part of Oracle’s financing strategy, not evidence of anything irregular, but it’s the context that should accompany any RPO headline number: backlog and delivered, recognized revenue are two different things, and the gap between them is where execution risk lives.
What This Means for OCI’s GPU Business
Taken together, Oracle’s own disclosures paint a consistent picture: OCI’s AI infrastructure business is growing extremely fast off a small base, is heavily reliant on a small number of very large contracts (Oracle’s SEC filings in prior quarters have separately disclosed meaningful customer concentration in RPO, a risk factor worth watching in Oracle’s subsequent 10-Q filings), and requires Oracle to keep raising capital well ahead of recognizing the revenue those contracts promise. The 300,000+ GPUs delivered since the prior quarter is the clearest evidence that contracted demand is translating into physically deployed capacity rather than remaining purely on paper, which matters because RPO growth without matching capacity delivery would be a much weaker signal. For a deeper look at OCI’s technical positioning against AWS, Azure, and Google Cloud for AI workloads, see our earlier piece linked below; this article is specifically about the financial and contractual side of that buildout.
Trade-offs and Open Questions
Strength: Oracle’s own numbers (RPO, OCI revenue growth, GPU delivery figures) are independently disclosed, audited-adjacent earnings figures, not marketing claims.
Uncertainty: individual mega-deal dollar figures (the reported $300B OpenAI agreement, and similar figures attributed to other AI labs in press coverage) are not independently confirmed by Oracle at the customer level.
Risk: a backlog this concentrated in a handful of counterparties carries real execution and credit risk if any major contract is delayed, renegotiated, or reduced — a dynamic Oracle’s own filings have flagged as a customer-concentration risk factor in the past.
Capital intensity: delivering on this backlog requires continuous, large-scale capital raising (debt and equity) well ahead of recognizing the matching revenue, which is a structural feature of this business model, not a one-time event.
The Bottom Line
Oracle’s own disclosed numbers — $664 billion in RPO, 121% OCI revenue growth, over 300,000 GPUs delivered in a single quarter — are real, verifiable, and describe a genuinely large and fast-growing AI infrastructure business. The specific mega-contract dollar figures that dominate headlines, including the widely reported $300 billion OpenAI deal, are credible press reporting but not figures Oracle has confirmed itself at the customer level, and that distinction matters when deciding how much weight to put on any single number. The more durable signal is the relationship between backlog growth and actual GPU delivery: as long as Oracle keeps converting RPO into deployed capacity at a pace resembling what it reported this quarter, the backlog is doing its job as a leading indicator rather than an accounting overhang.
FAQ
What exactly is Remaining Performance Obligations (RPO)? It’s the total dollar value of contracted revenue a company hasn’t yet recognized under its revenue recognition rules — essentially a backlog of signed, unfulfilled contracts. For Oracle, it ballooned specifically because of large, multi-year AI cloud infrastructure agreements.
Has Oracle confirmed the $300 billion OpenAI deal? Not at that specific dollar figure, tied to that specific customer, in an Oracle press release or SEC filing as far as this research could verify. The number traces to media reporting (the Wall Street Journal and subsequent outlets, September 2025) citing people familiar with the agreement. Oracle’s own earnings materials discuss AI contract bookings only in aggregate.
Is a growing RPO automatically good news? It’s a positive demand signal, but RPO is unrecognized, contracted revenue, not cash or completed work. Its value depends on counterparty credit quality, contract durability, and Oracle’s ability to actually deliver the capacity on the assumed timeline — none of which the headline number alone tells you.
How is Oracle funding this buildout? Through a mix of operating cash flow, debt, and equity issuance; this quarter’s release specifically disclosed $20 billion raised via an at-the-market common stock program alongside negative $5 billion in free cash flow, which Oracle attributed to infrastructure investment.
How does this relate to Oracle’s other AI announcements, like Database 23ai or its Nvidia partnership? Those cover different layers of the same broader strategy: Database 23ai is about AI features built into Oracle’s database product, and the Nvidia partnership concerns the GPU hardware supply behind OCI. This article is specifically about the financial scale of Oracle’s AI cloud capacity contracts and what the backlog numbers imply.
“Policy as code” covers a wider range of tools than it first appears. Some enforce rules on who can do what inside an application; others enforce rules on how infrastructure is allowed to be configured in the first place. This piece is about the second kind — a different, complementary layer to the relationship-based authorization systems covered in our Zanzibar/ReBAC explainer. Open Policy Agent (OPA), Kyverno, and AWS Config all let teams encode infrastructure and configuration rules as version-controlled policy rather than tribal knowledge or manual review, but they enforce those rules at different points, for different scopes, and with meaningfully different deployment models. Here’s how each actually works.
Decision engine queried by your software (sidecar, server, or library)
Kubernetes admission controller, CLI scanner, or runtime
Evaluates recorded resource configs; can auto-remediate
Learning curve
Higher — Rego is a new, Datalog-like language
Lower — “no new language to learn” per its own docs
Low for managed rules; higher for custom logic
Pricing model
Free, open source (CNCF graduated)
Free, open source (CNCF)
Metered: billed per configuration item and per rule evaluation
Governance body
CNCF (graduated)
CNCF
AWS proprietary service
Two Different Layers: Authorization vs Infrastructure Policy
It’s worth being precise about what these tools are not. Systems like Google Zanzibar, SpiceDB, and OpenFGA answer application-level authorization questions — “can this user view this document?” — by modeling relationships between users and resources. OPA, Kyverno, and AWS Config answer a different question entirely: “is this piece of infrastructure, Kubernetes manifest, or cloud resource configured the way our policy says it should be?” One layer governs who can do what inside your product; the other governs whether the systems your product runs on are compliant, secure, and consistent. A mature security posture typically uses both, and conflating them is a common mistake when teams first adopt policy-as-code.
Open Policy Agent (OPA): The General-Purpose Engine
OPA, a CNCF graduated project, describes itself in its own documentation as “a general-purpose policy engine that unifies policy enforcement across the stack.” Its design is deliberately decoupled from any one system: your application or infrastructure component sends OPA structured data (typically JSON) as input, and OPA evaluates that input against policies written in Rego, its purpose-built declarative language for reasoning over complex, hierarchical data, then returns a decision — which can be a simple allow/deny or arbitrary structured output.
That generality is OPA’s core trade-off. Its documentation lists an unusually wide integration surface: Kubernetes admission control, microservices and API gateways, Envoy and Istio service meshes, HTTP and GraphQL APIs, Kafka, Docker, SSH/sudo access control, Terraform plans, and AWS CloudFormation hooks. OPA typically runs as a standalone HTTP server (opa run --server, listening on localhost:8181 by default) that other systems query, or it can be embedded directly into Go programs via its rego package. The cost of that flexibility is Rego itself: it’s a genuinely new, Datalog-inspired language, and teams adopting OPA for the first time generally need to budget real ramp-up time for it, which is the single most common criticism leveled at OPA versus more narrowly scoped alternatives.
Kyverno: Kubernetes-Native, No New Language
Kyverno (also CNCF-hosted) was purpose-built for Kubernetes and has since expanded to work outside clusters as a more general policy tool, but its design center of gravity remains Kubernetes-native resource governance. Its own documentation leads with the contrast to Rego-based tools directly: policies are authored in YAML and CEL (Common Expression Language) as native Kubernetes resources managed the same way as any other manifest — with kubectl, Git, and kustomize — rather than in a separate policy language, which Kyverno’s docs frame as “no new language to learn.”
Functionally, Kyverno can validate, mutate, generate, or clean up Kubernetes resources, and it can verify container images and their metadata for supply-chain security — a feature set aimed squarely at platform engineering teams who need to enforce security and compliance baselines on application teams without those teams learning a new DSL. Deployment is correspondingly Kubernetes-centric: as an admission controller intercepting the API server, as a CLI-based scanner for CI pipelines, or evaluated at runtime, with results reported in the OpenReport format for integration with other tooling. Kyverno is the right fit when the governance problem is specifically “Kubernetes resources,” and the wrong fit when policy needs to span non-Kubernetes systems the way OPA can.
AWS Config: Cloud Resource Configuration, Metered
AWS Config is a different animal again: a managed AWS service, not an open source project, scoped specifically to AWS resource configuration rather than Kubernetes manifests or arbitrary application data. It continuously records the configuration of supported AWS resources and evaluates those recorded configurations against rules — either AWS-managed rules for common best practices or custom rules written against AWS’s own Guard policy DSL or backed by a Lambda function — flagging or, with remediation configured, automatically correcting non-compliant resources.
Unlike OPA and Kyverno, AWS Config is not free. According to AWS’s own pricing page (checked November 2026), the core charges are $0.003 per configuration item recorded with continuous recording (versus $0.012 per item under periodic recording), plus $0.001 per conformance pack evaluation and $0.001 per active Config rule evaluation for the first 100,000 evaluations in a region per month, with AWS’s documentation noting proactive evaluations from rules that support both proactive and detective modes are priced at $0 when run in combination. AWS states there is no free tier for this service and no minimum commitment — you pay purely for configuration items recorded and rule evaluations run, which means cost scales directly with both the size of your AWS footprint and the number of rules you turn on.
Choosing Between Them
Choose OPA when policy needs to span multiple, heterogeneous systems — Kubernetes admission control alongside API authorization, CI/CD gates, and Terraform plan checks — and your team can invest in learning Rego, or already has.
Choose Kyverno when the governance problem is specifically Kubernetes, your platform team wants policies that look like any other Kubernetes YAML manifest, and you want to avoid introducing a new policy language to application teams.
Choose AWS Config when you’re all-in on AWS and need continuous, automatic auditing of actual deployed resource configuration against compliance baselines (CIS benchmarks, internal standards), accepting its per-evaluation metered cost as the price of that continuous visibility.
Many mature AWS + Kubernetes shops run more than one: AWS Config for account- and resource-level compliance drift detection, plus Kyverno or OPA/Gatekeeper for admission-time enforcement inside the cluster — because Config audits after the fact, while Kyverno/OPA can block a non-compliant resource before it’s ever created.
Trade-offs Summary
OPA pros: broadest scope, CNCF-graduated maturity, works across Kubernetes and non-Kubernetes systems alike.
OPA cons: Rego’s learning curve is real and frequently cited as the main adoption barrier.
Kyverno pros: no new language, deeply Kubernetes-native, straightforward GitOps-style policy management.
Kyverno cons: scope is narrower than OPA’s outside the Kubernetes world.
AWS Config pros: deep, continuous AWS-native visibility and automatic remediation options, managed rule library for common compliance frameworks.
AWS Config cons: real metered cost that scales with resource count and rule evaluations, and it’s AWS-only — no multi-cloud coverage.
The Bottom Line
OPA, Kyverno, and AWS Config aren’t really competitors so much as three tools covering overlapping but distinct ground: general-purpose policy across many systems, Kubernetes-native governance without a new language, and AWS-specific continuous configuration auditing with a real metered bill attached. The practical pattern in 2026 is less “pick one” and more “pick the layer that matches the gap”: Kubernetes shops that want zero new languages lean Kyverno; teams with policy needs spanning multiple systems lean OPA; AWS-centric organizations layer Config on top of either for continuous drift detection, budgeting for its per-evaluation pricing as an operating cost rather than a one-time setup fee.
FAQ
Is this the same thing as Zanzibar/ReBAC authorization? No. ReBAC systems like Zanzibar, SpiceDB, and OpenFGA govern application-level access decisions (who can see or edit what). OPA, Kyverno, and AWS Config govern infrastructure and resource configuration — a separate, complementary layer, not a substitute.
Does Kyverno replace OPA/Gatekeeper? For Kubernetes-only use cases, many teams choose Kyverno specifically to avoid Rego. For policy needs spanning beyond Kubernetes, OPA’s broader integration surface still has no direct Kyverno equivalent.
How much does AWS Config actually cost for a mid-sized account? It depends entirely on resource count and rules enabled, since pricing is per configuration item recorded plus per rule evaluation, with no free tier. AWS’s own pricing page is the authoritative source and should be checked directly, since the component rates ($0.003 per config item, $0.001 per rule evaluation for the first 100,000) can change.
Can OPA and AWS Config be used together? Yes, and it’s a common pattern — OPA (often via Gatekeeper) enforcing policy at Kubernetes admission time inside a cluster, while AWS Config continuously audits the broader AWS account for drift and compliance across resources Kubernetes doesn’t touch.
Is Rego hard to learn? It has a real learning curve — it’s a declarative, Datalog-style language unlike most imperative languages developers already know — which is why Kyverno’s YAML/CEL approach markets itself explicitly against that friction for Kubernetes-only use cases.
Every one of the major serverless database platforms has rewritten its pricing and features at least once in the past two years, which makes “just use whichever one a tutorial mentions” a riskier strategy than it used to be. PlanetScale killed its free tier, Neon was acquired by Databricks for roughly $1 billion, and Supabase pushed its Team plan to $599 a month while keeping a genuinely usable free tier underneath it. Here is where the three stand as of late 2026, based on each vendor’s current pricing pages.
At a Glance
Platform
Database engine
Free tier
Entry paid price
Branching model
PlanetScale
MySQL (Vitess) or Postgres (single-node, HA, or sharded Neki)
None — discontinued March 2024
Postgres single-node from $5/month; Metal from $50/month
Full schema + data branching with non-blocking “deploy requests” across all three products
Neon
Postgres only
Yes — 100 projects, 100 CU-hours/project/month
Pay-as-you-go from $0.106/CU-hour (Launch)
Copy-on-write branches; child branches start at $0 storage
Supabase
Postgres only, plus bundled Auth/Storage/Edge Functions/Realtime
Yes — 2 active projects, 500 MB DB each
Pro from $25/month
Migration-based branch cloning (schema, not data, by default)
Short Verdict
If you need MySQL at serious scale, or you specifically want PlanetScale’s online, reversible schema-change workflow, PlanetScale is still the strongest option — but you’ll pay from day one. If you want a free-to-start, true serverless Postgres with instant, storage-efficient branching, Neon is the cleanest fit, and it now sits inside Databricks’ data platform. If you want a database plus auth, storage, and realtime in one SDK and don’t mind a steep jump from $25 to $599 a month once you need SOC 2 compliance, Supabase is the practical default for full-stack app teams.
What Each Platform Actually Is
PlanetScale was built by the team that created Vitess, the MySQL-sharding layer YouTube uses internally, and that heritage still shapes the product. Its core pitch is non-blocking schema migrations: you branch a database, make schema changes on the branch, and merge them back through a reviewable “deploy request” that applies without locking tables or causing downtime. PlanetScale has since added single-node and high-availability Postgres, plus Neki, a newer sharded Postgres engine, so branching and online schema changes now work across both MySQL and Postgres. There is no serverless or usage-based free option; PlanetScale’s own support documentation confirms the free Hobby plan was discontinued in March 2024, and every new database lands on a paid plan immediately.
Neon is a Postgres-only platform built around separating compute from storage, which is what makes scale-to-zero and copy-on-write branching possible. In 2025, Databricks acquired Neon in a deal reported at roughly $1 billion, and Neon’s technology now also powers “Lakebase,” Databricks’ own managed Postgres product for agentic and transactional workloads inside the Databricks platform. Neon continues to operate its own pricing and product independent of that integration. Its free plan is genuinely free forever (no credit card required) and supports up to 100 projects, each with 100 compute-hours a month and autoscaling up to 2 compute units (about 8 GB RAM) before suspending after five minutes of inactivity.
Supabase bundles a full Postgres database with authentication, file storage, auto-generated REST and realtime APIs, and Edge Functions, positioning itself as “the Postgres development platform” and an explicit alternative for teams leaving Firebase. Every project is a real, portable Postgres instance underneath — row-level security and SQL are available from day one rather than hidden behind a proprietary query layer.
Branching, Compared Properly
“Branching” means three different things on these platforms, and the difference matters for cost and workflow:
PlanetScale branches are full copies used specifically for schema review: you make a DDL change on a branch, PlanetScale validates it, and a deploy request applies the change to production without locking tables, with a revert path if something goes wrong.
Neon branches are copy-on-write at the storage layer: creating a branch is near-instant and costs nothing until the branch starts diverging from its parent through new writes, because only the deltas are stored. Free and Launch plans include 10 branches per project; Scale allows more, and paid plans can scale to thousands of branches per project at $1.50 per extra branch-month.
Supabase branches clone configuration and schema (rebuilt from your migration history) but not data by default — you opt in to copying data with a seed file or an “Include data” setting. Preview branches tied to a pull request are deleted automatically on merge or close; persistent branches stick around for staging or QA.
For teams doing frequent, data-heavy branch testing, Neon’s copy-on-write model is the cheapest and fastest. For teams whose main pain point is risky schema migrations on a live MySQL database, PlanetScale’s deploy-request workflow is still the more mature, purpose-built tool — it’s worth comparing against dedicated database migration tools like Flyway, Liquibase, and Atlas if schema change safety is your main requirement rather than hosting itself.
Pricing and Free-Tier Reality
PlanetScale
Neon
Supabase
Free tier
None
100 CU-hrs/project/month, 1 GB storage/project, 20 GB/account, scale-to-zero after 5 min
2 active projects, 500 MB DB each, pauses after 1 week inactive, 50k MAU auth
Cheapest paid tier
Postgres single-node from $5/month
Launch: pay-as-you-go, $0.106/compute-unit-hour, no monthly minimum
Pro: from $25/month, 8 GB included disk
Compliance-grade tier
Enterprise, custom pricing
Scale plan adds private networking and higher caps
Team at $599/month adds SOC 2, ISO 27001, SSO, 14-day backups
Supabase’s jump from $25 to $599 a month purely to get SOC 2 and SSO is the single biggest line-item surprise in this comparison, and it’s worth budgeting for early if you’re selling into enterprise customers. Neon’s model is the most forgiving for prototyping, since usage is metered down to the compute-hour and idle projects cost nothing. PlanetScale’s lack of any free tier means it’s really a tool for teams who already know they need its specific migration workflow or Vitess-scale sharding, not a place to experiment for free.
Pros and Cons
PlanetScale
Pros: Best-in-class non-blocking schema migration workflow; proven MySQL sharding (Vitess) at extreme scale; now also offers Postgres and sharded Neki; strong uptime SLAs.
Cons: No free tier at all; pricing for Vitess/Neki/HA is custom and opaque; less beginner-friendly than Supabase or Neon for a first side project.
Cons: Postgres only, so no MySQL path; autoscaling ceiling on lower tiers can surprise teams that outgrow it quickly; being folded into Databricks’ roadmap (via Lakebase) adds some long-term direction uncertainty for standalone users.
Supabase
Pros: Database, auth, storage, realtime, and edge functions in one platform; real, portable Postgres with no proprietary lock-in; usable free tier; open source and self-hostable.
Cons: Free projects pause after a week of inactivity; branching doesn’t copy data by default; the $599/month Team plan is a steep cliff just to get compliance certifications.
Who It’s a Good Fit For
Choose PlanetScale if you’re running a high-traffic MySQL application and schema changes are a recurring source of downtime risk, or if you need proven horizontal sharding at YouTube-scale traffic. Choose Neon if you want Postgres with the cheapest possible branching for CI/preview environments and don’t want to pay for idle compute. Choose Supabase if you’re building a full-stack app and want auth, storage, and realtime bundled with your database rather than assembled from separate vendors.
Who Should Look Elsewhere
If you need a true free tier to experiment with zero commitment, skip PlanetScale entirely. If you need MySQL compatibility specifically, Neon and Supabase are both out, since both are Postgres-only. If your budget caps out well under $599/month but you still need SOC 2 for a sales deal, check Neon’s and PlanetScale’s enterprise terms directly, since compliance gating varies and changes often on all three platforms.
Bottom Line
There’s no single winner here — the three platforms have diverged rather than converged. PlanetScale is the specialist for safe, large-scale schema changes, especially on MySQL. Neon is the most cost-efficient, developer-friendly serverless Postgres, now with Databricks’ backing. Supabase is the most complete “backend in a box” for teams that want more than just a database. Match the pick to what’s actually slowing your team down today, not to whichever platform shows up first in a Twitter thread.
FAQ
Does PlanetScale have a free tier in 2026? No. PlanetScale’s free Hobby plan was discontinued in March 2024, according to the company’s own support documentation. All databases now start on a paid plan immediately.
Is Neon still independent after the Databricks acquisition? Neon operates as its own product with its own pricing, but Databricks acquired the company in 2025 for a reported $1 billion and has built “Lakebase,” a managed Postgres offering, on Neon’s underlying technology.
Can I use MySQL on Neon or Supabase? No, both are Postgres-only. PlanetScale is the only one of the three with native MySQL (Vitess) support, alongside its newer Postgres offerings.
Does Supabase branching copy my production data? Not by default. Supabase branches rebuild the schema from your migration history and start without data; you have to explicitly add a seed file or enable the “Include data” option to populate a branch.
Which platform is cheapest for a side project? Neon, by a clear margin — its free tier has no card requirement and doesn’t pause projects for inactivity the way Supabase’s free tier does, and PlanetScale has no free tier at all.
WebAssembly (Wasm) spent its first several years as a browser performance trick: a compact bytecode format for running C, C++, and Rust code in a sandbox next to JavaScript. By 2026, its more consequential story is happening entirely outside the browser. A standardized system interface (WASI), a maturing component model, and runtimes purpose-built for servers and the edge have turned Wasm into a genuine alternative to containers for certain workloads — one that starts in microseconds rather than seconds and sandboxes by default rather than by configuration. This piece looks at the two names that matter most in that story, Wasmtime and Fermyon Spin, what the WASI standard they’re built on actually enables, and where the ecosystem still falls short.
At a Glance
Layer
What it is
Maintained by
WASI (0.2 / Preview 2)
Standard system interface (filesystem, sockets, clocks, HTTP) for Wasm outside the browser, built on the Component Model
Bytecode Alliance / WASI Subgroup
Wasmtime
Standalone, embeddable Wasm/WASI/Component Model runtime; the reference implementation most other tools build on
Bytecode Alliance
Fermyon Spin
Open source framework (now a CNCF project) for building and running event-driven microservices as Wasm components
Spin Framework / Fermyon
Why Wasm, Not Just Containers, for Server Workloads
Containers virtualize at the operating-system level: a container packages an application with its dependencies and runs it in an isolated process namespace, but it still boots something resembling a lightweight OS environment, which takes meaningful time and keeps a baseline memory footprint even when idle. Wasm modules are different in kind. A Wasm binary is sandboxed by construction — it can only do what its imported interfaces explicitly allow, with no ambient access to the filesystem, network, or memory outside its own linear memory space unless a host grants it. That sandboxing is enforced by the runtime’s bytecode verifier, not by namespaces or cgroups, so a Wasm module can be instantiated and torn down far faster than a container can be started and stopped. Spin’s own documentation markets this directly, citing “millisecond cold start times” as a headline benefit, specifically so that applications don’t need to be kept artificially warm the way serverless functions on heavier runtimes often do.
Portability is the other half of the pitch. A compiled Wasm module runs identically wherever a conformant Wasm runtime exists — a laptop, a Kubernetes cluster, a CDN’s edge network — without the architecture-specific binary concerns that follow native containers across x86 and ARM hosts.
WASI and the Component Model: What Actually Changed
Early WebAssembly had no standard way to talk to the outside world — no files, no sockets, nothing beyond pure computation. WASI (the WebAssembly System Interface) exists to fix that, defining POSIX-like interfaces for things like files, clocks, and random numbers so that a Wasm module can do real I/O in a portable, capability-based way: a module only gets access to the specific file handles or sockets its host explicitly hands it, not an open-ended syscall surface.
The pivotal recent milestone is WASI 0.2, also called WASI Preview 2, which the Bytecode Alliance’s WASI Subgroup launched on January 25, 2024, declaring its APIs stable even as surrounding tooling continued to mature. WASI 0.2 is built on the Component Model, a Wasm extension focused on composition: combining independently built, possibly cross-language Wasm modules (“components”) into larger systems through explicit interfaces, with no shared global namespace at runtime. WASI 0.2 defines this through “worlds” — wasi-cli for roughly POSIX-style command-line behavior, and, more relevant to server workloads, wasi-http, a proxy world built specifically around HTTP requests and responses. That’s the interface that makes a Wasm component usable as an HTTP-handling microservice in the first place. The Bytecode Alliance has also started early design work on WASI 0.3 (Preview 3), focused on async support, which it expects is “at least a year away” as of its most recent public roadmap article.
Wasmtime: The Reference Runtime
Wasmtime, also a Bytecode Alliance project, describes itself in its own documentation as “a standalone runtime for WebAssembly, WASI, and the Component Model.” It can be used directly as a command-line tool for running Wasm binaries, or embedded as a library inside a larger host application — which is exactly how most higher-level tools, Spin included, actually use it under the hood. Wasmtime compiles Wasm to native machine code through Cranelift, its optimizing code generator, and its documentation states that its development is “strongly focused on correctness and security,” including the ability to cap a guest module’s CPU and memory consumption from the host side. Wasmtime is, in effect, the engine; most developers interact with it indirectly, through a framework built on top.
Fermyon Spin: The Developer-Facing Framework
Spin, originally built by Fermyon and now a CNCF project under the Spin Framework umbrella, sits a level above Wasmtime. Its own documentation describes it as “a framework for building and running event-driven microservice applications with WebAssembly (Wasm) components,” designed to run the same application across local development machines, self-hosted servers, Kubernetes, and cloud-hosted services without modification. Spin applications are organized around triggers — HTTP, Redis, and Cron are the ones documented — that invoke a Wasm component in response to an event, so a Spin app is essentially a set of small, independently sandboxed components wired to the events that should run them. Because Wasm is a compilation target for many languages rather than a single new language to learn, Spin’s pitch is that teams can keep writing Rust, Go, JavaScript, or Python (its documented language guides) while gaining Wasm’s sandboxing and startup-speed properties for free.
Current Limitations
Server-side Wasm is real and shipping, but it is not a drop-in replacement for containers yet, for a few concrete reasons:
Ecosystem maturity: the Bytecode Alliance’s own WASI 0.2 announcement was explicit that documentation, test suites, toolchains, and implementations were all still catching up to the spec at launch — a sign of a young but moving standard, not a finished one.
Async is still emerging: WASI 0.2 does not yet have mature native async support; that’s the headline goal of WASI 0.3, which the Bytecode Alliance describes as roughly a year or more away as of its latest roadmap. Long-running or highly concurrent I/O-bound workloads are the hardest fit for today’s Wasm server stack as a result.
Language support varies in depth: most languages can compile to Wasm in some form, but the quality of WASI support, garbage-collected-language performance, and tooling polish differs significantly between, say, Rust (first-class across this ecosystem) and languages whose runtimes were not designed with Wasm compilation in mind.
Not every workload benefits: stateful, long-running processes, workloads needing deep OS-level access, or applications already well-served by a mature container pipeline may see little upside from switching, since Wasm’s main advantages — cold-start speed and sandboxing — matter most for short-lived, event-driven, multi-tenant workloads.
Who Should Actually Consider It
Server-side Wasm makes the most sense today for: edge and CDN-adjacent compute where cold-start latency directly affects user-perceived performance; multi-tenant platforms that need strong, cheap sandboxing between untrusted or semi-trusted customer code (plugin systems, serverless platforms); and teams building new, stateless, HTTP-triggered microservices who want portability across local dev, Kubernetes, and edge targets without separate build pipelines for each. It makes less sense, for now, as a wholesale replacement for an existing containerized fleet of long-running, stateful services, or for workloads that need mature async I/O and broad OS access that WASI doesn’t yet fully standardize.
Trade-offs Summary
Pros: sandboxing by default, millisecond-scale cold starts, strong portability across hosts and architectures, growing language support through standard compilation toolchains.
Cons: younger ecosystem with gaps in tooling and documentation, no mature native async yet (WASI 0.3 pending), uneven language support depth, and a smaller hiring pool of engineers already fluent in the stack compared to containers.
The Bottom Line
Server-side WebAssembly in 2026 is past the experimental-curiosity stage but still short of being a default choice. WASI 0.2’s stabilization and the Component Model it’s built on gave the ecosystem a real standard to build against, Wasmtime provides a solid, security-focused reference runtime, and Spin turns that into a genuinely usable developer experience for event-driven microservices. The honest read is that this is the right tool for specific jobs — edge compute, sandboxed multi-tenant workloads, fast-scaling stateless services — rather than a wholesale container replacement, and that async support arriving with WASI 0.3 will be the next real inflection point to watch.
FAQ
Is WebAssembly only for the browser? No. WASI and the Component Model specifically exist to let Wasm run outside browsers — on servers and at the edge — with standardized access to system resources like files, clocks, and HTTP.
How is this different from the Cloudflare Workers / Vercel / Deno Deploy edge platform comparison? Those are hosted edge-compute platforms that run application code (often JavaScript/V8 isolates, with varying Wasm support underneath). This article covers the underlying runtimes and standard — Wasmtime and WASI — and a framework, Spin, that you can self-host or deploy to multiple targets, rather than a single managed platform.
Do I need to learn a new language to use Spin or Wasmtime? No. Wasm is a compilation target, not a source language. Spin’s documented language guides cover Rust, Go, JavaScript, and Python, among others with Wasm toolchains.
What is the Component Model, in plain terms? It’s a standard way for separately built Wasm components, potentially written in different languages, to expose and consume interfaces and link together into larger applications — without a shared global namespace or the fragility of raw C ABI linking.
Is server-side Wasm production-ready? For specific workloads — HTTP-triggered microservices, plugin sandboxes, edge functions — yes, and Spin is a CNCF project with real production users. For workloads needing mature async I/O or deep OS integration, the ecosystem is still catching up to what WASI 0.3 is expected to standardize.
DNS filtering is one of the cheapest, lowest-effort ways to block malware, phishing, and unwanted content before a browser ever loads a page. Instead of inspecting traffic after the fact, it stops the lookup at the DNS layer — the step where a device asks “what’s the address for this domain?” If the answer is a known-bad or blocked domain, the request never goes anywhere. NextDNS, Cloudflare Gateway, and OpenDNS (now folded into Cisco’s security lineup) are the three names that come up most often, but they’re built for different people: a privacy-minded household, a small business wanting Zero Trust basics for free, and a large enterprise buying through a reseller, respectively.
At a Glance
Tool
Best For
Free Tier
Entry Paid Price
Setup Difficulty
NextDNS
Privacy-conscious individuals and families
300,000 queries/month, all features, unlimited devices
$1.99/mo or $19.90/yr (Pro)
Easy — apps, router, or DoH/DoT profile
Cloudflare Gateway
Small businesses wanting Zero Trust basics
Up to 50 users, full SWG/ZTNA, limited DLP
$7/user/month billed annually (self-serve tier)
Moderate — part of a broader Zero Trust setup
OpenDNS / Cisco Umbrella (Secure Access)
Enterprises already in the Cisco ecosystem
Free public resolvers with baseline filtering
Custom quote via Cisco partners — no public price list
Harder — sold and deployed through resellers
The Short Verdict
If you’re protecting your own home network or a handful of personal devices, NextDNS gives you serious control — security-threat blocking, ad/tracker filtering, and parental controls — for free or for about $2 a month, with logs you fully control. If you run a small or mid-size business and already like Cloudflare’s stack, Gateway’s free plan (up to 50 users) is a genuinely strong starting point for Zero Trust-style DNS filtering, and the paid tier is transparently priced at $7 per user, per month. If you’re a larger organization that needs Cisco’s enterprise support, integrations, and compliance posture, you’ll be filtering through Cisco Secure Access (the product line that is absorbing Umbrella) — but be aware that pricing is not published anywhere publicly; you’ll need to talk to a partner or account rep to get a number.
What Each Tool Actually Is
NextDNS is a consumer-and-prosumer DNS resolver and filtering service. According to NextDNS’s own pricing page, the free plan covers up to 300,000 DNS queries per month with access to every feature — security-threat blocking, ad and tracker blocking, and parental/content controls covering categories like adult content, violence, and piracy. Once you cross that query cap, NextDNS says it keeps resolving DNS “like a classic non-blocking DNS service” until the month resets or you upgrade, so a busy household can occasionally lose filtering, not internet access. The $1.99/month (or $19.90/year) Pro plan removes the query cap entirely but keeps every other feature identical — it’s explicitly aimed at personal and close-family use, not seat-based business deployments. NextDNS also lets you choose where logs are stored (United States, EU, UK, or Switzerland) and how long they’re kept, from one hour to two years, or off entirely — a level of control most consumer DNS tools don’t offer.
Cloudflare Gateway is the secure web gateway component of Cloudflare’s Zero Trust platform (part of the broader “Cloudflare One” SASE suite). Independent pricing trackers that monitor Cloudflare’s published Zero Trust plans consistently report a Free tier covering up to 50 users with no device limit, DNS-and-network-level policies across up to three locations, 24 hours of activity log retention, and full secure-web-gateway and Zero Trust network access capability (DLP is limited to predefined policies on this tier). The next tier — billed per user, self-serve, no sales call required — is commonly listed at $7/user/month when billed annually, raising the location count to 20, log retention to 30 days, and adding email/chat support. An Enterprise/contract tier above that adds up to 250 locations, six months of log retention with SIEM export, expanded CASB, and premium support, priced only through a sales conversation. Cloudflare’s own developer documentation confirms Gateway enforces DNS, network, and HTTP policies and maintains a categorized list of domains for content and risk-based filtering, though the exact category list isn’t published in a single static page we could verify word-for-word — expect broad coverage of both security-risk categories (malware, phishing, newly seen domains) and acceptable-use categories (adult content, gambling, social media, and similar).
OpenDNS was Cisco’s original consumer DNS security brand; it still publishes free resolver addresses (208.67.222.222 and 208.67.220.220) that apply baseline phishing and malware filtering with zero signup, and Cisco continues to document a FamilyShield variant that pre-configures adult-content blocking for home routers. For organizations, though, OpenDNS’s own site now funnels business visitors straight to Cisco Secure Access. That matters for buyers: Cisco’s official Umbrella packages page confirms that Umbrella — the business product OpenDNS evolved into — is in a planned end-of-sale and end-of-life transition as Cisco consolidates its DNS-layer security (plus SASE features like ZTNA and digital experience monitoring) under the Secure Access name. Existing Umbrella subscriptions continue under their current terms, but new buyers are being steered to Secure Access. Crucially, none of Cisco’s own pages list self-serve prices for either product — every package is “contact an expert” or quote-via-partner, which is standard for Cisco’s enterprise sales model but a real contrast with NextDNS and Cloudflare’s published numbers.
Pricing and Feature Comparison
Feature
NextDNS
Cloudflare Gateway
OpenDNS / Cisco Secure Access
Published self-serve pricing
Yes — $0 or $1.99/mo
Yes — $0 or ~$7/user/mo
No — quote-only via partners
Malware/phishing blocking
Included on free tier
Included on free tier
Included on free public resolvers
Content category filtering
Ads, adult, violence, piracy, more
Dozens of security and acceptable-use categories
Parental controls via FamilyShield; full category policy requires Secure Access
Log retention control
1 hour to 2 years, or off
24 hrs (Free) up to 6 months (Enterprise)
Not publicly documented
Device/user limits
Unlimited devices, all plans
Up to 50 users free; unlimited paid
Varies by contract
Target buyer
Individuals, families, small teams
Small-to-mid businesses, Zero Trust adopters
Mid-to-large enterprises, Cisco shops
Pros
NextDNS: Full feature access on the free tier, granular logging and data-residency controls, and a genuinely low $1.99/month price for unlimited use.
Cloudflare Gateway: A free plan generous enough for a real small business (50 users), backed by Cloudflare’s global network, with transparent self-serve pricing above that.
OpenDNS / Cisco: Free baseline resolvers for home use, plus enterprise-grade support, integrations, and compliance credentials once you’re a Secure Access customer.
Cons
NextDNS: No dedicated business tier, centralized device management, or SSO — it’s built for personal use, not fleets of managed endpoints.
Cloudflare Gateway: DNS-only filtering won’t stop much on its own; real value requires adopting more of the Zero Trust/Cloudflare One stack, which adds complexity.
OpenDNS / Cisco: No public pricing anywhere, a confusing Umbrella-to-Secure-Access rebrand in progress, and a sales-led buying process that’s slow for smaller teams.
Who It’s a Good Fit For
Choose NextDNS if you manage your own home or small-office network and want fast, cheap, highly configurable filtering without an IT department. Choose Cloudflare Gateway if you run a small or growing business, already touch Cloudflare for DNS or CDN services, and want Zero Trust-style web filtering without committing budget up front. Choose OpenDNS/Cisco Secure Access if you’re a mid-size or large organization that needs enterprise support contracts, deep integration with existing Cisco security tooling, and can tolerate a quote-based sales cycle.
Who Should Look Elsewhere
Businesses that want one predictable, self-serve price with no sales call should skip Cisco’s business line entirely and look at NextDNS or Cloudflare Gateway instead. Households that need zero setup and don’t care about granular logs may find NextDNS’s configuration options unnecessary and prefer plugging straight into OpenDNS’s free resolver addresses.
Bottom Line
For most individuals and small teams, NextDNS and Cloudflare Gateway’s free tiers already cover the core job — blocking known-bad domains and unwanted content categories before they load — at a price point of $0 to roughly $7 per user. Cisco’s OpenDNS/Secure Access lineage still matters for enterprises that want a single vendor relationship and dedicated support, but you should budget time for a sales conversation, not a checkout page, and expect the Umbrella-to-Secure-Access transition to keep reshaping what’s on offer.
FAQ
Is DNS filtering enough security on its own? No. It blocks lookups to known-bad or policy-blocked domains, but it can’t inspect encrypted traffic content or stop every threat. Most teams pair it with endpoint protection and, for businesses, a broader secure-access or email-security layer.
Can I use NextDNS and Cloudflare Gateway on the same network? Not usefully at the same time for the same traffic — a device or router can only point to one DNS resolver at a time. You’d pick one as your primary filter.
Does Cloudflare Gateway’s free plan expire or get capped? It’s an ongoing free tier (not a trial) for up to 50 users, though Cloudflare’s service terms set usage expectations around DNS query volume per seat; sustained heavy overage can require moving to a paid plan.
What happened to Cisco Umbrella? Cisco’s own product pages describe Umbrella as being folded into Cisco Secure Access, with Umbrella itself in a planned end-of-sale and end-of-life transition. Current Umbrella customers keep their existing terms, but new buyers are directed to Secure Access packages.
Is OpenDNS’s free resolver still available for home use? Yes — Cisco continues to document the free public resolver addresses and the FamilyShield variant for pre-configured parental filtering, with no account required.
Every public API eventually needs a way to say “slow down.” Rate limiting protects backends from overload, keeps one noisy client from starving everyone else, and turns an otherwise unpredictable traffic spike into a predictable 429 response. But “add rate limiting” isn’t one algorithm — it’s a choice between at least four meaningfully different approaches, each with its own memory cost, burst behavior, and accuracy trade-off. This explainer walks through token bucket, leaky bucket, fixed window, and sliding window counters, grounded in how AWS API Gateway and Stripe actually implement and document their own limits.
The simplest approach divides time into fixed windows (say, one-second or one-minute buckets) and keeps a single counter per client per window. A request increments the counter; once the counter hits the limit, further requests are rejected until the window resets. It’s cheap — one integer per client — but it has a well-known flaw: a client can send its full quota at the very end of one window and its full quota again at the very start of the next, doubling its effective rate in a short burst spanning the boundary. For anything beyond a rough quota, this flaw usually rules fixed windows out.
Sliding Window: Fixing the Boundary Problem
Sliding window approaches fix the boundary-burst flaw by not resetting cleanly at fixed intervals. There are two common implementations:
Sliding window log: store a timestamp for every request in a client’s recent history (often in a sorted set), and on each new request, count how many timestamps fall within the trailing window. This is exact, but memory grows with request volume — O(n) per client — which makes it expensive at high request rates.
Sliding window counter: keep two fixed-window counters (current and previous) and estimate the sliding count as a weighted combination — for example, the current window’s count plus a fraction of the previous window’s count proportional to how much of that previous window still overlaps the trailing interval. This keeps memory at O(1) per client while closely approximating the exact sliding log, and it’s the approach most commonly cited in CDN- and edge-level rate limiting write-ups because it balances precision against the cost of tracking state for millions of concurrent clients.
Token Bucket: The Industry Default
Token bucket is the algorithm most production API gateways actually ship. AWS documents it directly for API Gateway: each client bucket holds tokens, tokens are added at a constant steady-state rate (requests per second), and each incoming request consumes one token. AWS’s own developer guide defines the two knobs plainly: the rate limit is “the rate, in requests per second, that tokens are added to the token bucket,” and the burst limit is “the capacity of the token bucket” — the maximum number of concurrent request submissions API Gateway will fulfill before returning 429 Too Many Requests. When the bucket is full, a client can momentarily burst well above the steady-state rate; once empty, requests are throttled until tokens refill. AWS is explicit that these are “best-effort” targets rather than hard guarantees, since other regional and account-level limits can also apply.
Stripe takes the same approach from the other side of the API relationship: its documented global rate limit is 100 requests per second in live mode and 25 requests per second in its sandbox, measured per Stripe account, with lower per-endpoint limits layered on top (for example, 25 requests per second for most individual endpoints, 20 read/write per second for the Files API). Stripe’s own documentation explicitly recommends that client integrations implement “a client-side token bucket rate-limiting algorithm” to smooth their own request rate below these ceilings, rather than hammering the API and relying on retries.
Token bucket’s appeal is that one simple state — a token count and a last-refill timestamp — captures both a sustained rate and a controlled burst allowance, which matches real traffic (which is rarely perfectly smooth) better than a hard per-second cap would.
Leaky Bucket: Smoothing Instead of Bursting
Leaky bucket flips the token bucket’s intent. Instead of allowing bursts up to a capacity, incoming requests fill a queue (the “bucket”), and that queue drains — is processed — at a constant, fixed rate, regardless of how bursty the input was. If the queue fills up, new requests are dropped or rejected. This produces a perfectly smoothed output rate, which is valuable when the thing being protected (a downstream service, a physical network link) genuinely cannot tolerate bursts at all, but it adds queuing latency that token bucket doesn’t: a request arriving when the queue is nearly full waits longer before being served, even if it would otherwise be well within an average rate. Leaky bucket is more associated with network traffic shaping than with modern HTTP APIs, where client-perceived latency usually matters more than perfectly flat throughput.
A Minimal Token Bucket in Pseudocode
struct Bucket:
tokens: float
capacity: float
refill_rate: float // tokens per second
last_refill: timestamp
function allow_request(bucket):
now = current_time()
elapsed = now - bucket.last_refill
bucket.tokens = min(bucket.capacity, bucket.tokens + elapsed * bucket.refill_rate)
bucket.last_refill = now
if bucket.tokens >= 1:
bucket.tokens = bucket.tokens - 1
return true // allowed
else:
return false // reject with 429
Choosing Between Them
Token bucket — default choice for most public APIs and gateways (AWS API Gateway, Stripe’s own guidance to clients). Good when occasional legitimate bursts are fine and you want O(1) memory per client.
Leaky bucket — best when downstream capacity is rigid and you need a perfectly smoothed output rate, accepting added latency.
Fixed window counter — fine for coarse, low-stakes quotas (e.g., “1,000 requests per day”) where the boundary-burst flaw doesn’t matter much.
Sliding window log — use when exactness matters and request volume per client is low enough that O(n) memory is affordable.
Sliding window counter — the practical middle ground for high-volume, distributed rate limiting (e.g., Redis-backed limiters at the edge), trading a small approximation error for O(1) memory.
Most real systems layer several of these: a token bucket or sliding window counter at the account level, tighter fixed windows on specific expensive endpoints, and a hard concurrency limit (a separate mechanism from rate limiting, capping simultaneous in-flight requests rather than requests per second) for long-running operations. Stripe, for instance, documents its global per-account rate limit and its separate concurrency limit — 50 in-progress requests by default in live mode — as two distinct protections that trigger different error headers.
Trade-offs Summary
Pros of token bucket: O(1) memory, tolerates natural burstiness, easy to reason about with two parameters (rate, capacity).
Cons of token bucket: a client can burst its entire bucket instantly if it has been idle, which can momentarily spike downstream load.
Cons of leaky bucket: adds queuing delay; a sudden burst is delayed rather than rejected, which can be worse for latency-sensitive clients.
Pros of sliding window counter: closely approximates exact behavior at O(1) memory, avoids the fixed-window boundary flaw.
Cons of sliding window counter: still an approximation, with a small, bounded error versus a true sliding log.
The Bottom Line
There’s no single “best” rate limiting algorithm — there’s a best algorithm for a given traffic pattern and failure mode. Token bucket is the closest thing to an industry default because it’s cheap, tolerates real-world burstiness, and is what both a major cloud provider (AWS API Gateway) and a major API company (Stripe) actually document and recommend. Leaky bucket earns its place when burst tolerance is actively undesirable. Sliding window counters are the pragmatic choice when you need sliding-window accuracy without sliding-log memory costs. Knowing all four means you can match the algorithm to the actual failure you’re trying to prevent, instead of defaulting to whatever a library ships.
FAQ
What HTTP status code signals rate limiting? Almost universally 429 Too Many Requests, often with a Retry-After header. Stripe additionally returns a Stripe-Rate-Limited-Reason header identifying whether the limit was global, endpoint-specific, or a concurrency limit.
Is rate limiting the same as throttling? In practice the terms are used interchangeably, including in AWS’s own documentation, which describes “throttling” as the mechanism and the token bucket as the algorithm behind it.
Is a concurrency limit a type of rate limit? No — it’s a related but distinct protection. A rate limit caps requests per unit time; a concurrency limit caps how many requests can be in-flight simultaneously, regardless of how fast they arrive. Stripe documents both separately, since long-running or resource-intensive requests can exhaust concurrency without ever exceeding the rate limit.
Should I rate limit on the client side too? Yes, and both AWS and Stripe effectively recommend it. Stripe’s documentation specifically suggests client-side token bucket limiting with exponential backoff and jitter, so a client self-regulates instead of discovering the limit only via repeated 429 errors.
Which algorithm should a new API default to? Token bucket, unless you have a specific reason to smooth output (leaky bucket) or need exact sliding-window accuracy at low volume (sliding window log). It’s well understood, cheap to implement, and matches how both AWS and Stripe limit their own APIs.
Every retrieval-augmented generation (RAG) pipeline, semantic search box, and recommendation engine built since 2023 depends on the same underlying problem: given a query vector, find the handful of vectors in a database of millions (or billions) that are closest to it. Doing this exactly, by comparing the query to every stored vector, is called k-nearest neighbor (kNN) search, and it does not scale — brute-force comparison is O(N) per query. So almost every real vector database instead does approximate nearest neighbor (ANN) search: trading a small, tunable amount of recall for orders-of-magnitude faster lookups. Two families of ANN algorithm dominate production systems in 2026: graph-based methods, led by HNSW, and partition-based methods, led by IVF. This piece explains how each actually works, what their real trade-offs are, and when to reach for which.
At a Glance
Factor
HNSW (graph-based)
IVF (partition-based)
Core idea
Multi-layer navigable graph; search by walking edges toward the query
Cluster vectors into cells with k-means; search only the nearest cells
Key build parameters
M (connections per node), efConstruction
nlist (number of cells)
Key query parameter
efSearch
nprobe (cells searched)
Query speed
Very fast, roughly logarithmic in dataset size
Fast, scales with nprobe/nlist fraction scanned
Memory overhead
Higher — stores the full graph on top of vectors (~M × 2 × 4 extra bytes/vector)
Lower — mainly list IDs plus chosen vector encoding
Build time
Slower to build, especially at high M/efConstruction
Faster to build; k-means training step is comparatively cheap
FAISS, Milvus (IVF variants), many large-scale offline pipelines
Why Exact Search Doesn’t Scale
An embedding model turns text, images, or audio into a dense vector, typically a few hundred to a few thousand floating-point numbers, positioned so that semantically similar inputs land close together under a distance metric like cosine similarity or Euclidean distance. Finding the true nearest neighbors to a query vector means computing that distance against every vector in the collection. At a few thousand vectors this is trivial. At tens of millions, it means billions of floating-point operations per query — workable for a batch job, unworkable for an interactive RAG endpoint that needs to return results in tens of milliseconds. ANN algorithms accept a small, measurable chance of missing a true nearest neighbor in exchange for search that scales sub-linearly.
How HNSW Works
HNSW (Hierarchical Navigable Small World) was introduced by Yu. A. Malkov and D. A. Yashunin in their 2016 paper “Efficient and Robust Approximate Nearest Neighbor Search Using Hierarchical Navigable Small World Graphs,” building on earlier skip-list and small-world-graph ideas. Conceptually, HNSW organizes vectors into several stacked graph layers, like a multi-level transit map:
The top layer is sparse, with a small number of nodes connected over long links — good for covering large distances quickly.
Each layer below is progressively denser, with more nodes and shorter, more local connections.
The bottom layer contains every vector in the collection, densely interconnected.
A search starts at an entry point in the top layer and greedily walks toward the query vector, hopping to whichever neighbor is closer at each step. When no neighbor in the current layer is closer, the search drops down a layer and continues, refining its position until it bottoms out with a set of nearby candidates. This is similar to zooming from a country-level map down to a street-level map rather than scanning every street in the country directly.
Three parameters control the trade-off, as documented by vector database vendors such as Qdrant:
M — the maximum number of connections per node (commonly 8–64; Qdrant defaults to 16). Higher M improves recall but increases memory and build time.
efConstruction — how many candidate neighbors are evaluated when inserting a new vector into the graph (commonly 100–500). Higher values build a better-connected graph at the cost of slower indexing.
efSearch (sometimes called hnsw_ef) — how many candidates are evaluated per query at search time (commonly 50–200+). This is the main dial for trading query latency against recall, and unlike the other two, it can be changed per query without rebuilding the index.
HNSW’s practical downside is memory and mutability. The graph’s edges sit on top of the raw (or quantized) vectors, adding roughly M × 2 × 4 bytes per vector according to FAISS’s own documentation, and removing a vector cleanly is not supported because deleting a node can disconnect the graph around it — most implementations instead mark vectors as deleted and periodically rebuild.
How IVF Works
IVF (Inverted File index), as implemented in Meta’s FAISS library, takes a completely different approach: partition first, then search only the relevant partitions. FAISS’s own wiki documentation describes it as a “cell-probe method”:
During index training, a coarse quantizer (usually k-means) splits the vector space into nlist cells, each represented by a centroid.
Every vector in the collection is assigned to exactly one cell — whichever centroid it’s closest to — and stored in that cell’s inverted list.
At query time, the query vector is compared only against the nlist centroids to find the nprobe closest cells, then compared against the actual vectors inside just those cells.
FAISS’s documentation gives a rule of thumb for sizing nlist at roughly C × sqrt(n) for a dataset of n vectors. The fraction of the database actually scanned per query is approximately nprobe / nlist (in practice usually a bit more, since cells are rarely perfectly balanced). Raising nprobe improves recall by checking more cells, at a roughly linear cost in query time. Recall suffers specifically when a query’s true nearest neighbor happens to sit in a cell that wasn’t among the nprobe probed — a structural risk near cell boundaries that has no direct HNSW equivalent.
IVF is commonly paired with vector compression. IVFFlat stores full-precision vectors (about 4d + 8 bytes per vector, where d is dimensionality); IVFPQ (product quantization) compresses vectors much further at some recall cost, making it attractive for billion-scale, memory-constrained deployments. Because cells are just lists, adding and removing vectors is straightforward compared to HNSW’s graph surgery problem.
A Minimal Illustration of the Search Logic
The pseudocode below is a simplified sketch of the two query paths — not production code — meant only to show where each algorithm spends its effort.
function ivf_search(query, nprobe):
centroids = get_cell_centroids()
nearest_cells = top_k(centroids, query, k=nprobe)
candidates = []
for cell in nearest_cells:
candidates.extend(cell.vectors)
return top_k(candidates, query, k=final_k)
function hnsw_search(query, ef_search):
layer = top_layer
current = entry_point
while layer > 0:
current = greedy_walk(layer, current, query)
layer = layer - 1
candidates = explore_neighbors(current, query, ef=ef_search)
return top_k(candidates, query, k=final_k)
HNSW vs IVF: When to Use Which
Neither structure is strictly better; they sit at different points on the recall/speed/memory curve, and the right choice depends on dataset size, update frequency, and hardware budget.
Choose HNSW when query latency matters most, the dataset fits comfortably in memory, recall needs to stay high even at low latency, and updates are frequent but deletions are rare (most RAG and real-time semantic search use cases). It’s the default or primary index type in Qdrant, Weaviate, and pgvector’s HNSW mode.
Choose IVF (often IVF+PQ) when the collection is very large (hundreds of millions to billions of vectors), memory is tight, and some recall can be traded for dramatically smaller index size. It’s also easier to shard and rebuild incrementally, which is why it shows up heavily in FAISS-based offline and batch retrieval pipelines.
Hybrid approaches exist: FAISS supports using an HNSW graph as the coarse quantizer inside an IVF index (IVF_HNSW), combining fast coarse routing with inverted-list storage.
In practice, most teams don’t hand-pick an algorithm from first principles — they pick a vector database (Qdrant, Weaviate, Pinecone, Milvus, or Postgres with pgvector) and then tune its exposed parameters. Pinecone’s newer serverless indexes go a step further and abstract the index type away entirely, separating storage from query compute and exposing on-demand read capacity rather than a pod size the user has to choose. That’s a trend worth watching: the HNSW-vs-IVF decision is increasingly made by the database vendor, not the application developer, with the practitioner left tuning recall targets and cost rather than graph parameters directly.
Trade-offs Summary
Pros of HNSW: excellent recall-to-latency ratio, logarithmic-ish query scaling, tunable at query time via efSearch without rebuilding.
Cons of HNSW: larger memory footprint, slower builds at high quality settings, poor support for deletions.
Pros of IVF: lower memory overhead (especially with PQ), faster builds, straightforward updates and deletions, scales well to very large, sharded datasets.
Cons of IVF: recall is more sensitive to data distribution and cell boundaries; needs careful nlist/nprobe tuning and periodic retraining of centroids as data shifts.
The Bottom Line
HNSW and IVF solve the same problem — fast approximate retrieval over dense vectors — with opposite structural bets: a navigable graph versus a partitioned index. For most RAG and application-facing semantic search workloads where the data fits in memory and queries need to be fast and fresh, HNSW’s recall-per-millisecond is hard to beat, which is why it has become the default in most purpose-built vector databases. For very large-scale, storage-constrained, or heavily batch-oriented retrieval, IVF (particularly IVF+PQ) remains the more economical choice. The practical skill isn’t memorizing one algorithm — it’s knowing which knobs (efSearch, nprobe, M, nlist) to turn when recall, latency, or memory becomes the bottleneck in production.
FAQ
Is ANN search ever exact? No — by definition, approximate nearest neighbor search can miss some true nearest neighbors. Both HNSW and IVF expose parameters (efSearch, nprobe) that push recall closer to exact search as you increase them, at the cost of query speed.
Can I combine HNSW and IVF? Yes. FAISS supports using an HNSW graph as the coarse quantizer inside an IVF index, and several systems layer quantization (scalar or product quantization) on top of either structure to shrink memory further.
Which one do most vector databases use by default? Most purpose-built vector databases aimed at application developers — Qdrant, Weaviate, Milvus’s default configuration, pgvector’s HNSW index type — default to HNSW because of its strong recall-to-latency ratio on in-memory datasets. IVF (and IVF+PQ specifically) is more common in large-scale, cost-sensitive, or research/offline retrieval pipelines built directly on FAISS.
Does deleting vectors work the same way in both? No. FAISS’s own documentation notes that HNSW does not support true vector removal because deleting a node can disconnect the graph; most systems instead tombstone and periodically rebuild. IVF’s list-based structure makes removal and insertion more straightforward.
How does this relate to RAG? A RAG pipeline embeds a user’s query, runs ANN search (HNSW or IVF, depending on the vector store) against a corpus of pre-embedded chunks, and feeds the top results into an LLM’s context window as retrieved evidence. The ANN index’s recall directly caps how good the retrieved context — and therefore the generated answer — can be.
Every major AI lab now ships something that can drive a web browser on your behalf: clicking buttons, filling in forms, and working through multi-step errands while you do something else. In 2026 the field has already gone through one round of consolidation. Google shut down its standalone “Project Mariner” research prototype in May. OpenAI discontinued its standalone Atlas browser in August, folding the technology back into ChatGPT. Only Anthropic’s Claude in Chrome is still shipped as a dedicated browser extension. Here is what each company’s current product actually does, who can use it, and what guardrails are documented on their own support pages — not what was announced a year ago and never updated.
At a Glance
Product
Maker
What It Does
Availability / Tier
Claude in Chrome
Anthropic
Chrome extension that reads pages, clicks, types, fills forms, and runs multi-step and background tasks across tabs
Runs multi-step tasks in a visual browser, terminal, and code environment inside ChatGPT; absorbed the old Operator and the shut-down Atlas browser
Pro, Plus, Business, Enterprise, Edu. Not yet in EEA/Switzerland for full features
Gemini in Chrome (“auto browse”) and Gemini Tasks
Google
Completes shopping, booking, and research tasks in Chrome or a remote browser; Tasks absorbed much of the discontinued Project Mariner’s browsing engine
Google AI Pro or Ultra, personal account, 18+, US only for auto browse; Tasks excludes EEA, UK, Switzerland, Nigeria
Claude in Chrome (Anthropic)
Anthropic’s support documentation now calls the product “Claude in Chrome” rather than the “Claude for Chrome” name used at its August 2025 research-preview launch. It is a browser extension that works alongside the person using it: Claude can read a page, click, type, navigate between tabs, and fill out forms. According to Anthropic’s own help article, it can also handle background work that keeps running while you switch tabs (as long as Chrome stays open), take on multiple tabs at once if you drag them into Claude’s tab group, run tasks on a recurring schedule, save prompts as reusable shortcuts, and read console output, network requests, and DOM state for debugging purposes. A beta integration with 1Password on macOS lets Claude request logins without ever seeing the password itself.
Access is restricted to paid Claude plans: Pro, Max, Team, and Enterprise. There is no free tier and, per the documentation, no waitlist mentioned at this stage — it is simply gated by subscription. It only runs in Chrome itself, not other Chromium browsers, and it is not available on mobile. Enterprise and Team admins get the most granular control: they can enable or disable the extension outright, and set allowlists or blocklists that restrict which domains Claude is permitted to touch.
ChatGPT Agent Mode and the End of the Atlas Browser (OpenAI)
OpenAI’s browser-agent story has consolidated twice in the past year. First, in July 2025, OpenAI’s own announcement describes “ChatGPT agent” as a “natural evolution” that folded the earlier Operator research preview directly into ChatGPT — the standalone Operator site was sunset shortly after. Then, in 2026, OpenAI tried a second approach: a standalone Atlas desktop browser, launched in October 2025. That experiment was short-lived. OpenAI’s own help center article on the deprecation states plainly that the company is “deprecating Atlas and moving browser-based agentic capabilities into ChatGPT and Codex,” with Atlas stopping functioning on August 9, 2026 — about nine months after its debut. OpenAI pointed users toward the ChatGPT desktop app (which gained multi-tab support, downloads, and account-login handling) and a ChatGPT Chrome extension/sidebar for lighter in-browser assistance, while deeper agentic work lives in “agent mode” inside ChatGPT itself.
As it stands today, agent mode works from a visual browser, a text browser, a terminal, and direct API access, plus connectors to apps such as Gmail and GitHub. OpenAI’s documentation says it can browse and interact with websites, fill out forms, run code, analyze data, build slideshows and spreadsheets, and even make purchases — with a confirmation step first. Typical tasks take roughly 5 to 30 minutes. It is available on Pro, Plus, Business, Enterprise, and Edu plans (not the free tier), with monthly message caps of 40 for Plus/Business/Enterprise and 400 for Pro. Full availability has been rolling out gradually and was not yet complete in the EEA and Switzerland as of OpenAI’s published guidance.
Gemini in Chrome and the Shutdown of Project Mariner (Google)
Google’s path has been the most fragmented of the three. Project Mariner launched as a DeepMind research prototype in December 2024 and reached a stable release for Google AI Ultra subscribers in the US in May 2025, with plans to expand into the Gemini API, Vertex AI, and Search’s AI Mode. Multiple reports — corroborated by Google’s own Project Mariner page as cited in its Wikipedia history — confirm the standalone experiment was discontinued on May 4, 2026, with its underlying browsing technology folded into other Google products rather than continued as its own brand.
Two live Google products now carry that technology forward, and both are documented on Google’s own support site. The first is “auto browse” inside Gemini in Chrome, an experimental feature that lets Gemini “complete multi-step tasks for you on the web,” including comparing products, adding items to a cart, booking travel and restaurant reservations, buying event tickets, and drafting messages. It requires a Google AI Pro or Ultra plan, a personal Google account (not work/school, not Incognito), the latest Chrome build, and residency in the US while 18 or older; it is desktop-only and still rolling out gradually. Usage is capped at 20 multi-step tasks per day on AI Pro and 200 per day on AI Ultra. The second is “Tasks” within the broader Gemini app (mobile, Mac, and web), which can assign Gemini a goal to work on in the background or on a schedule — including web shopping and bookings through either the local Chrome browser or a remote browser Gemini controls itself. Tasks requires a Pro or Ultra subscription, a personal account, and is not available in the EEA, UK, Switzerland, or Nigeria; up to 15 tasks can run at once.
Feature Comparison
Capability
Claude in Chrome
ChatGPT Agent Mode
Gemini in Chrome / Tasks
Navigates sites & clicks/types
Yes
Yes
Yes
Fills out web forms
Yes
Yes (listed as a confirmed action)
Yes (requires confirmation)
Multi-step / long-running tasks
Yes, including background work across tabs
Yes, 5-30 minute typical tasks
Yes, scheduled or background Tasks; Chrome auto browse is session-based
Can complete a purchase
Not emphasized in documentation
Yes, with confirmation first
Yes, with confirmation; user bears responsibility for outcomes
Runs on a schedule
Yes, scheduled tasks and shortcuts
Yes, daily/weekly/monthly recurring tasks
Yes, Tasks can run on schedule or trigger on events
Org-level domain controls
Allowlist/blocklist for Team & Enterprise
Enterprise owners can block domains
Admin opt-in/out at domain or group level (Workspace)
Lowest qualifying paid tier
Claude Pro
ChatGPT Plus
Google AI Pro
Safety Guardrails Compared
All three vendors converge on a similar basic shape of safeguard, even though they describe it in different language. Anthropic’s support article says Claude in Chrome is “enhanced with our safety classifiers but is still risky,” and recommends reading its separate safety guide before use; the extension reviews each action and pauses to ask for approval when needed, and organizations can restrict it to specific domains via allowlists and blocklists, or disable it entirely. OpenAI’s documentation for ChatGPT agent mode describes a “takeover mode” that hands control of the virtual browser back to the user for logins (screenshots stop being captured while the user is in control), a “watch mode” that requires active supervision on certain sites, a confirmation step before high-impact actions, and an enterprise-configurable domain blocklist; the company also cites refusal patterns for disallowed tasks and ongoing monitoring for prompt-injection attempts.
Google’s support pages for both Gemini in Chrome’s auto browse and the broader Gemini Tasks feature are the most explicit about financial exposure: Gemini is required to ask for confirmation before sending communications, modifying data, submitting forms, making a purchase, or accessing sites with sensitive financial, health, or government-ID data — and that confirmation step applies even if a user has set permissions to “Always allow.” For sign-ins and payments, Gemini must hand control back to the user rather than entering credentials itself, and Google’s own guidance explicitly tells users not to type passwords or card numbers directly into a task thread. All three companies state, in their own words, that these measures reduce but do not eliminate risk, and that users remain responsible for monitoring the agent’s actions — particularly anything involving money, legal matters, or health information.
Trade-offs
Claude in Chrome is the most developer-leaning of the three, with console/network/DOM access built in for debugging, but it is Chrome-only, desktop-only, and gated entirely behind a paid plan with no lightweight free tier to try first.
ChatGPT agent mode has the broadest task surface (code execution, file analysis, app connectors, plus browsing) and the clearest purchase-confirmation flow, but it inherited two product pivots in twelve months — Operator folded in, then the standalone Atlas browser shut down after nine months — which is worth factoring in if you build a workflow around it.
Gemini in Chrome / Tasks has the tightest documented daily usage caps (20-200 tasks a day depending on tier) and the narrowest geographic availability of the three, restricted largely to the US for Chrome auto browse and excluding the EEA, UK, Switzerland, and Nigeria for the broader Tasks feature — a result of Project Mariner’s technology being redistributed into regionally gated products rather than a single global one.
Bottom Line
Browser-controlling AI agents are real and shipping today, but none of the three majors has settled on a final form yet. Anthropic has the most stable, single-product offering in Claude in Chrome, aimed at people already paying for Claude and comfortable with a developer-flavored tool. OpenAI has the most capable all-in-one agent once you’re inside ChatGPT, after abandoning the idea of a separate browser entirely. Google has split the old Project Mariner’s capabilities across two different surfaces — Chrome’s auto browse and the Gemini app’s Tasks — each gated by its own narrower eligibility rules. For teams evaluating these tools for productivity, QA, or site-scanning use cases, the practical advice is the same across all three: start with low-stakes, reversible tasks, keep an eye on the confirmation prompts rather than clicking through them, and expect the product you pick today to look different in six months. For a broader look at the agent landscape beyond browsers, see our explainers on what AI coding agents are and how the leading AI agent frameworks compare.
FAQ
Is OpenAI’s Atlas browser still available? No. OpenAI’s own help center confirms Atlas was deprecated, with the browser stopping functioning on August 9, 2026, roughly nine months after launch. Its agentic capabilities moved into ChatGPT’s agent mode and Codex, and lighter browsing help is available through a ChatGPT Chrome extension/sidebar.
What happened to Google’s Project Mariner? The standalone research prototype was discontinued on May 4, 2026. Its browsing technology was folded into Gemini in Chrome’s “auto browse” feature and into the broader “Tasks” capability inside the Gemini app, rather than continuing as its own branded product.
Can any of these agents make purchases on their own? ChatGPT agent mode and Gemini’s Tasks/auto browse both document the ability to complete purchases, but both require an explicit confirmation step first and place responsibility for unexpected charges on the user. Anthropic’s documentation for Claude in Chrome does not emphasize purchasing as a core capability.
Do I need a paid subscription to use any of these? Yes, for all three. Claude in Chrome requires a paid Claude plan (Pro and up), ChatGPT agent mode requires Plus and up, and Gemini in Chrome’s auto browse and Tasks both require a Google AI Pro or Ultra subscription.
Are these available outside the US? Coverage varies and is still expanding. Gemini in Chrome’s auto browse is documented as US-only at this stage; Gemini Tasks excludes the EEA, UK, Switzerland, and Nigeria; ChatGPT agent mode’s full rollout had not yet reached the EEA and Switzerland as of OpenAI’s published guidance. Claude in Chrome’s own documentation does not state a country restriction but is limited to paid-plan Chrome users.
Databases and CDNs handle billions of lookups a day where the honest answer is almost always “no” — this key isn’t cached, this partition doesn’t hold that row, this URL isn’t on a blocklist. Hitting disk, making a network call, or scanning a table just to confirm an absence is expensive at that scale. The Bloom filter is the classic fix: a compact, probabilistic structure that can say “definitely not in the set” instantly, and “probably in the set” the rest of the time — never the reverse. Invented by Burton H. Bloom in 1970 to cut down expensive dictionary lookups, it now sits quietly inside Apache Cassandra, a PostgreSQL index type, Akamai’s CDN caching logic, and (historically) Chrome’s malicious-URL checks. Here’s exactly how it works, the math behind tuning it, and where it’s verifiably used today.
At a Glance
What it is
A fixed-size bit array plus k independent hash functions, used to test set membership
Guarantees
Zero false negatives — a “not in the set” answer is certain. False positives are possible, and their rate is tunable.
Typical use cases
Skipping unnecessary disk reads, network round-trips, or cache lookups for keys that almost certainly don’t exist
Space cost
About 9.6 bits per item for a 1% false-positive rate — independent of how large the items themselves are
Trade-offs
Can’t enumerate members, standard version can’t delete items, and accuracy degrades once more items are inserted than it was sized for
Origin
Burton H. Bloom, “Space/Time Trade-offs in Hash Coding with Allowable Errors,” Communications of the ACM (1970)
How a Bloom Filter Works
A Bloom filter is just an array of m bits, all starting at 0, plus k independent hash functions that each map any item to one position in that array.
Insert: run the item through all k hash functions and set each resulting bit position to 1.
Query: run the candidate item through the same k hash functions. If any of those bit positions is 0, the item was definitely never inserted. If all of them are 1, the item is probably in the set.
The “definitely not” answer is airtight: a bit can only be set by an insertion, so a 0 means no insertion ever touched it. The “probably yes” answer is where the trade-off lives. Because many items share the same small bit array, two or more different items can collectively set all k bits that a third, never-inserted item would also hash to. That coincidence is a false positive — the filter claims membership for something that was never added. This is also why standard Bloom filters can’t support deletion: clearing a bit to remove one item might silently remove another item that happens to share that bit.
The Math: Choosing Size and Hash Count for a Target False-Positive Rate
Three numbers determine everything: m (bits in the array), n (items you plan to insert), and k (hash functions). For a filter with m bits holding n items and using k hash functions, the probability of a false positive is approximately:
p ≈ (1 − e−kn/m)k
For a fixed ratio of bits to items (m/n), there’s a value of k that minimizes this probability:
koptimal = (m/n) × ln 2
And working backward from a target false-positive rate p, the array size needed for n items is:
m = −(n × ln p) / (ln 2)2
Plugging in a 1% target (p = 0.01) gives m/n ≈ 9.6 bits per item and k ≈ 7 hash functions — and dropping the target rate by another order of magnitude costs only about 4.8 more bits per item, not ten times more space. This is a textbook result, and it checks out against a real deployed system: early Chrome Safe Browsing shipped a client-side Bloom filter sized at roughly 10 bits per URL hash with 7 hash functions, landing almost exactly on the formula’s 1%-false-positive point for a filter of that size — for a list of around 100 million malicious URLs, that compressed an ~8 GB blocklist into roughly 125 MB on-device.
Real-World Uses (Verified)
The mechanics above are standard computer science, but it’s worth separating the textbook idea from where it’s actually proven to run in production. Here are four uses confirmed against primary sources:
System
How it uses a Bloom filter
Apache Cassandra
Every SSTable on disk carries a Bloom filter so a read can skip SSTables that provably don’t contain the requested partition, avoiding needless disk I/O. The target false-positive rate is a per-table setting (bloom_filter_fp_chance), defaulting to 0.01–0.1 depending on compaction strategy, per Cassandra’s own operations documentation.
PostgreSQL (bloom module)
The official bloom contrib extension is an index access method that stores a lossy multi-column signature per row so queries can quickly exclude non-matching rows before rechecking the actual heap row — useful for equality filters across many columns where building one B-tree per column would be wasteful.
Google Chrome (historical)
Early versions of Chrome’s Safe Browsing feature stored a Bloom filter of malicious-URL hashes on the device itself, so most page loads were cleared instantly with no network call; only a filter “hit” triggered a narrow server lookup. Chrome has since moved to a different hash-prefix design, but the original implementation is preserved in Chromium’s source history.
Akamai CDN
In the peer-reviewed “Algorithmic Nuggets in Content Delivery” paper, Akamai researchers Bruce Maggs and Ramesh Sitaraman describe using a Bloom filter to detect “one-hit wonders” — objects requested only once — and apply a cache-on-second-hit rule so first-time requests aren’t written to disk. Their traffic logs found over three-quarters of objects were one-hit wonders, and the filtering raised byte hit rate from about 74% to 83% while cutting disk writes by 44%.
Cassandra’s SSTable Bloom filters work alongside two other structural decisions covered in more depth elsewhere on this site: the choice between B-tree and LSM-tree storage engines (Cassandra is LSM-based, which is exactly why unnecessary SSTable reads are worth avoiding), and consistent hashing, which decides which node a key lives on before a Bloom filter ever gets asked whether that node’s local data might contain it.
Variants: Counting Bloom Filters and Cuckoo Filters
Two well-known extensions address the standard filter’s biggest limitation — no deletions:
Counting Bloom filters replace each single bit with a small counter, typically 3–4 bits. Inserting increments the relevant counters; deleting decrements them. A position only reads as “empty” once its counter hits zero, so one item’s removal doesn’t erase another’s. The cost is 3–4× the memory of a plain bit array.
Cuckoo filters take a different approach: they store short item fingerprints in a cuckoo hash table instead of setting bits. They support deletion natively, often use less space than a Bloom filter at the same false-positive rate, and have better memory locality since a lookup touches only one or two table buckets instead of k scattered bit positions.
A Minimal Implementation
The core logic fits in about twenty lines. This version uses only the Python standard library, deriving k independent hash positions from SHA-256 with a different integer salt per round:
import hashlib
import math
class BloomFilter:
def __init__(self, n_items, false_positive_rate):
self.size = self._optimal_size(n_items, false_positive_rate)
self.hash_count = self._optimal_hash_count(self.size, n_items)
self.bits = bytearray(self.size)
@staticmethod
def _optimal_size(n, p):
m = -(n * math.log(p)) / (math.log(2) ** 2)
return max(1, int(math.ceil(m)))
@staticmethod
def _optimal_hash_count(m, n):
k = (m / n) * math.log(2)
return max(1, int(round(k)))
def _indexes(self, item):
data = item.encode("utf-8")
for i in range(self.hash_count):
digest = hashlib.sha256(data + i.to_bytes(4, "big")).digest()
yield int.from_bytes(digest[:8], "big") % self.size
def add(self, item):
for idx in self._indexes(item):
self.bits[idx] = 1
def might_contain(self, item):
return all(self.bits[idx] for idx in self._indexes(item))
bf = BloomFilter(n_items=1000, false_positive_rate=0.01)
bf.add("user:4821")
print(bf.might_contain("user:4821")) # True: definitely inserted
print(bf.might_contain("user:9999")) # False, almost always — never a false negative
This stores one byte per bit for clarity; a production implementation would pack eight slots per byte to hit the real 9.6-bits-per-item target. Swapping SHA-256 for a faster non-cryptographic hash (MurmurHash3 is the common production choice) is the usual next optimization once correctness is confirmed.
Trade-offs
No enumeration: you can ask “is X in here?” but never get the list of what was actually inserted.
No deletion (standard version): requires switching to a counting or cuckoo variant if removal is needed.
Sizing matters: a filter sized for n items degrades past that false-positive rate once significantly more items are inserted — it doesn’t fail outright, but accuracy quietly worsens.
Hash quality matters: the independence assumption behind the math above breaks down with poorly distributed hash functions, inflating the real false-positive rate above the computed one.
Bottom Line
A Bloom filter isn’t a general-purpose set — it’s a narrow, specific tool for one job: cheaply ruling out “definitely not here” so an expensive lookup only runs when there’s actually a chance of a hit. That narrowness is the whole point. Cassandra uses it to skip SSTables, Postgres uses it to skip heap-row rechecks, Akamai used it to skip caching objects nobody will request again, and Chrome used it to skip network calls for safe URLs. If you’re weighing whether to add one to your own system, the real design question isn’t “should I use a Bloom filter,” it’s what false-positive rate you can tolerate and whether you’ll ever need to delete an entry — the first sets your memory budget via the formulas above, and the second decides whether you need the plain version or a counting/cuckoo variant.
FAQ
Can a Bloom filter ever produce a false negative? No. If an item was inserted, every bit it set is still set, so a query for it will always find all relevant bits at 1. “Not in the set” is a guaranteed-correct answer.
Can I delete an item from a standard Bloom filter? Not safely. Clearing a bit could un-set membership for a different item that happens to hash to the same position. Use a counting Bloom filter or a cuckoo filter if deletion is a requirement.
How is this different from just using a hash set? A hash set stores the actual items (or their full hashes) and is always exact. A Bloom filter stores neither — only a shared bit array — which is why it can be an order of magnitude smaller, at the cost of occasional false positives.
What false-positive rate should I actually pick? It depends on what a false positive costs downstream. Cassandra’s own defaults — 0.01 for most compaction strategies, 0.1 for leveled compaction — are a reasonable starting range: lower if a false positive means an expensive fallback check, higher if memory is tighter and an occasional unnecessary lookup is cheap.
Nearly every AI coding assistant is sold on a speed promise, and most developers who use one report feeling faster. But when researchers set out to measure that speedup directly, rather than asking developers how fast they felt, the results have been far messier than either side of the AI debate suggests. The most rigorous study available, a 2025 randomized controlled trial from the AI evaluation nonprofit METR, found that experienced open-source developers were actually slower when using AI tools on their own familiar codebases, even though they believed they had sped up. Other research, including GitHub’s own studies and the 2025 DORA report from Google Cloud, points toward real gains, at least for certain tasks, tools, and organizations. This piece walks through what each credible, citable study actually measured, where its conclusions stop, and why the evidence as a whole is still unsettled rather than one-sided.
At a Glance
Study
Who Ran It
What It Found
Key Caveat
Early-2025 RCT (“Measuring the Impact of Early-2025 AI…”)
METR (independent AI research nonprofit)
Experienced developers were 19% slower on real issues when allowed to use AI, despite forecasting a 24% speedup and later believing they were about 20% faster
Only 16 developers and 246 tasks, all on large, familiar open-source codebases, using Cursor with Claude 3.5/3.7 Sonnet in early 2025
2026 follow-up / uplift update
METR
Weak signal of a swing toward speedup (returning developers around 18% faster, new developers around 4% faster), but both confidence intervals cross zero
METR itself calls the evidence “very weak” due to selection bias: developers most convinced AI helps increasingly refused to do tasks without it
Copilot productivity research (2022)
GitHub (vendor-run)
95 professional developers writing a new HTTP server from scratch were about 55% faster with Copilot (1h11m vs. 2h41m) and had a higher task-completion rate
Single, well-defined greenfield task; tested 2022 Copilot Technical Preview, not today’s agentic tools; GitHub is the product’s maker
2025 DORA State of AI-Assisted Software Development
Google Cloud / DORA
90% of developers now use AI; AI adoption is newly linked to higher team delivery throughput, reversing the prior year’s finding; over 80% self-report individual productivity gains
Based on self-reported survey data and organizational correlations, not controlled, task-level timing
2025 Stack Overflow Developer Survey
Stack Overflow
68% of professional developers use AI tools daily or weekly, yet favorable sentiment fell from over 70% in 2023–2024 to about 61%, and only roughly a third trust AI output’s accuracy
Measures usage and sentiment, not measured speed or output quality
METR’s Randomized Trial: Slower, Not Faster, Despite Feeling Faster
The study generating the most debate is METR’s “Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity,” published in July 2025. METR recruited 16 developers who were already experienced, long-tenured contributors to large open-source repositories, averaging more than 22,000 GitHub stars and over a million lines of code. The developers brought 246 real issues, mostly bug fixes, features, and refactors, averaging roughly two hours of expected work each. Each issue was randomly assigned to either allow or disallow AI assistance; when allowed, developers mostly used Cursor Pro with Claude 3.5 or 3.7 Sonnet. Work was screen-recorded and self-timed, and developers were paid $150 an hour.
The result ran against expectations on all sides: when AI was allowed, developers took about 19% longer to complete their issues, with a 95% confidence interval spanning roughly 2% to 39% slower. Just as notable was the gap between belief and reality. Before starting, developers forecast that AI would speed them up by about 24%. Afterward, having just experienced the slowdown, they still estimated that AI had made them roughly 20% faster. METR itself is careful about the limits of this finding: 16 developers is a small sample, participants may differ systematically from developers who declined to take part, and the results describe experienced contributors working in large, familiar codebases with high internal standards for documentation and testing. METR also notes it cannot rule out that developers were still climbing the learning curve on Cursor, and that the results reflect tools as they existed in early 2025.
METR’s 2026 Update: A Walk-Back on Certainty, Not a Reversal
METR did not stop there. In a February 2026 update, the organization described a second, larger study begun in August 2025: 57 developers (10 returning from the original study, 47 new), 143 repositories, and more than 800 tasks, this time paid $50 an hour. The raw numbers moved toward speedup: returning developers were estimated to be about 18% faster, and new developers about 4% faster. But both confidence intervals cross zero, meaning the data cannot statistically distinguish those numbers from no effect at all.
More important than the point estimates is what METR says drove them. Between roughly 30% and 50% of surveyed developers reported skipping tasks in the study because they didn’t want to do them without AI, which likely strips out the tasks where AI would have helped the most and biases the measured result toward looking slower than reality. Lower pay than the original study may have compounded the selection problem. METR’s own conclusion is blunt: developers are probably more sped up by AI in early 2026 than the original study found for early 2025, but the organization calls its evidence for the actual size of that improvement “very weak,” and it is redesigning the experiment rather than standing behind a new number. For anyone tracking how autonomous coding agents like Claude Code and Codex differ from older autocomplete-style tools, this matters: the tools used in the second study were materially more advanced than Cursor with Sonnet 3.5, yet the research still couldn’t pin down a confident number.
GitHub’s Own Research: A Large Speedup on a Narrow Task
GitHub’s most frequently cited productivity research dates to 2022, published on its own research blog while Copilot was still in technical preview. It combines two studies. The first was a survey of more than 2,000 developers who had signed up for the Copilot preview, built around the SPACE framework for developer productivity; over 90% agreed they completed repetitive tasks faster, but this is self-reported perception from an early-adopter population, not a measurement.
The second part is a genuine controlled experiment: 95 professional developers were randomly split into two groups and asked to write an HTTP server in JavaScript from scratch, with correctness and completeness scored automatically by a test suite. The group with Copilot access finished in an average of 1 hour 11 minutes versus 2 hours 41 minutes without it, a 55% speed gain that GitHub reports as statistically significant (P=.0017, 95% CI of 21% to 89%), and also had a higher completion rate (78% vs. 70%). The gap with METR’s finding is explained largely by what was being measured: a short, well-specified, greenfield task with no existing codebase conventions to learn or preserve, versus real maintenance work inside large, idiosyncratic repositories. It’s also a vendor-run study of a now-outdated tool version, which is worth weighing alongside the result itself.
DORA 2025: Near-Universal Adoption, and a Flip at the Organizational Level
The DORA (DevOps Research and Assessment) team at Google Cloud takes a different approach entirely: a large annual survey of software professionals correlating AI adoption with team-level delivery outcomes rather than timing individual tasks. The 2025 report found that AI adoption among software professionals had reached about 90%, up 14 points from the prior year, with professionals spending a median of roughly two hours a day working with AI tools. More than 80% of respondents said AI had improved their individual productivity, and 59% reported a positive effect on code quality, both self-reported.
The headline organizational finding is a reversal: in DORA’s 2024 report, higher AI adoption had been associated with lower software delivery throughput and stability; in 2025, adoption is now linked to higher throughput. DORA frames this cautiously, describing AI as a “mirror and a multiplier” that amplifies the strengths of cohesive, well-run engineering organizations and exposes the weaknesses of fragmented ones, rather than a tool with a fixed, universal productivity effect. Trust remains mixed: only about 24% of respondents report a great deal or a lot of trust in AI output. None of this is a controlled measurement of how much faster any individual developer becomes; it is a correlational, self-reported picture of how AI use tracks with outcomes across many organizations.
Stack Overflow 2025: Heavy Use, Cooling Trust
The 2025 Stack Overflow Developer Survey adds a sentiment and adoption layer rather than a productivity measurement. Among professional developers, 50.6% reported using AI tools daily and another 17.4% weekly, for a combined 68%. But favorable sentiment toward AI tools, which had been above 70% in both 2023 and 2024, fell to about 61% among professionals in 2025. Trust in the accuracy of AI output is notably thin: roughly a third of professional respondents say they trust it, while close to half say they distrust it. Over 40% rated AI as bad or very poor at handling complex tasks specifically. Read together with the benchmark scores covered in our explainer on SWE-bench, HumanEval, and what AI coding benchmarks actually measure, this survey is a useful reminder that benchmark performance, daily usage, and developer confidence can all move independently of each other.
Why the Findings Diverge
These studies aren’t simply contradicting each other; they’re measuring different things under different conditions, and the gaps line up with a few recurring variables.
Task familiarity and codebase complexity. METR’s slower result came from maintenance work inside large, idiosyncratic, long-lived codebases where developers already had deep tacit knowledge; GitHub’s faster result came from a short, self-contained, greenfield task with no existing conventions to navigate. AI assistance appears to help more when there’s little context to absorb and less when a developer already knows the codebase better than the model does.
Experience level and expectations. METR’s participants were highly experienced and had high internal quality bars (tests, documentation, linting), which may make AI-generated suggestions a net cost to review and correct. Less experienced developers, or those working outside their specialty, may see larger relative gains, though METR’s data doesn’t directly test that.
Measurement method. Self-reported speed (GitHub’s 90%+ “faster” figure, DORA’s 80%+ productivity figure, developers’ own post-task estimates in METR’s study) consistently reads more positive than directly timed, randomized measurement. METR’s own developers believed they were faster even while a stopwatch showed otherwise, which is a strong argument for discounting pure self-report.
Tool and model generation. GitHub’s 2022 result used an early Copilot preview; METR’s 2025 result used Cursor with Claude 3.5/3.7 Sonnet; METR’s 2026 follow-up involved more capable agentic tools like Claude Code and Codex. Capability has moved quickly, and a result anchored to one tool generation may not hold for the next.
Selection bias in who gets studied. METR explicitly flagged that developers most convinced of AI’s value increasingly refused to complete tasks without it, skewing later data. The direction of that bias is toward understating AI’s benefit in the newer study, which is part of why METR won’t commit to a number yet.
Bottom Line
There is no single honest answer to “do AI coding tools make developers faster,” because the best available evidence doesn’t converge on one. The most methodologically rigorous study of experienced developers working in familiar, complex codebases found them slower with AI, not faster, despite feeling faster, a finding worth taking seriously precisely because it cuts against both marketing claims and developer intuition. At the same time, a controlled study of a short, well-defined task found a large, statistically significant speedup, and broad industry survey data shows adoption climbing toward near-universal along with self-reported productivity and, newly, a positive link to team-level delivery throughput. What’s genuinely unsettled is magnitude and conditions, not existence: AI coding tools can speed some work up and slow other work down, and the honest position in late 2026 is that task type, codebase familiarity, developer experience, and tool generation all swing the outcome, with METR’s own follow-up research still unable to put a reliable number on where things stand today.
FAQ
Did the METR study prove AI coding tools make developers slower? It proved that, for 16 experienced developers doing real maintenance work in large, familiar open-source codebases with early-2025 tools, measured time was about 19% longer with AI allowed. It did not establish that this holds for all developers, all tasks, or current tools; METR’s own 2026 follow-up suggests the picture may now be more favorable to AI, while cautioning that its new evidence is weak.
Why did developers in the METR study believe they were faster when they weren’t? METR doesn’t fully explain the mechanism, but notes that developers forecast a 24% speedup beforehand and still estimated a roughly 20% speedup afterward despite the opposite result. This mirrors a broader pattern across the research covered here: self-reported speed consistently runs more positive than directly timed results.
Is GitHub’s 55%-faster Copilot statistic still relevant? It’s a real, statistically significant result from a controlled study, but it dates to a 2022 Copilot preview and a single greenfield task (writing a new HTTP server), and it was run by the tool’s own maker. It says more about short, well-defined, from-scratch tasks than about day-to-day maintenance in large codebases.
Does the DORA report contradict METR’s findings? Not directly; they measure different things. DORA tracks self-reported individual productivity and organization-level delivery throughput across a large survey population, while METR directly times a controlled sample of experienced developers on real tasks. DORA’s 2025 finding that AI adoption now correlates with higher throughput is an organizational, correlational result, not a controlled measurement of individual task speed.
What should a team take away from this research? Treat vendor-reported and self-reported speedups skeptically, expect AI assistance to help more on unfamiliar, well-specified, or boilerplate-heavy work than on deep maintenance of complex systems a developer already knows well, and watch for the gap between how fast AI use feels and how fast it actually is.
Every local development workflow that touches containers eventually runs into the same question: what’s actually running the containers on your laptop? For years the answer was simply “Docker Desktop,” but two real alternatives — Podman Desktop and OrbStack — have matured enough that the choice is no longer automatic, especially since Docker Desktop’s free-use terms changed for larger companies back in 2021. This review compares all three on 2026 pricing and licensing, platform support, resource-usage claims, and Kubernetes support, pulling every figure directly from each vendor’s own site.
Individuals, non-commercial open source projects, and commercial businesses under 250 employees AND under $10M annual revenue
Windows, macOS, Linux
Teams already standardized on Docker tooling who qualify for the free tier, or who are willing to pay for it
Podman Desktop
$0 — fully free and open source
Everyone, regardless of company size or revenue; optional paid enterprise support available separately from Red Hat
Windows, macOS, Linux
Teams of any size that want a daemonless, free runtime with native Kubernetes workflows
OrbStack
$0 (personal use); $8/user/mo or $96/user/yr (Pro); custom (Enterprise)
Personal, non-commercial use only — any business use requires Pro or Enterprise
macOS only
Mac-based developers who want the fastest, lightest-weight local runtime and don’t need Windows or Linux hosts
Short Verdict
Docker Desktop is still the default because it’s the most feature-complete and runs everywhere, but its free use is explicitly capped by company size and revenue, and government entities must pay regardless of size. Podman Desktop is the only one of the three with no commercial-use gate at all — it’s free and open source for a one-person shop or a 10,000-person enterprise alike, and it runs on the same three platforms Docker does. OrbStack is the odometer-reset option for Mac-only teams: it’s built as a lighter, faster native replacement for Docker Desktop on macOS, but it doesn’t run on Windows or Linux at all, and any commercial use requires its $8/user/month Pro plan.
What Each Tool Is
Docker Desktop is Docker, Inc.’s GUI application that bundles the Docker Engine, CLI, Compose, and an optional local Kubernetes cluster into a single installer for Windows, macOS, and Linux. It’s the tool most engineers learned containers on, and it remains the reference implementation most tutorials and CI images assume.
Podman Desktop is an open source graphical front end for Podman, the daemonless, rootless-capable container engine originally built by Red Hat and now a CNCF Sandbox project. Instead of a single background daemon running as root (Docker’s traditional architecture), Podman runs containers as child processes of the user who started them, which is the basis for its security pitch. Podman Desktop adds Docker-Desktop-style container and image management, plus dedicated screens for creating and managing local Kubernetes clusters.
OrbStack is a macOS-native replacement for Docker Desktop, built as a native Swift app rather than running inside a general-purpose Linux VM the way Docker Desktop traditionally has. It markets itself on startup speed, low idle resource use, and compatibility with the standard Docker CLI and Docker Compose files, so existing workflows mostly just point at a different backend.
Pricing and Licensing Breakdown
Docker’s free-use terms are the most consequential fact in this comparison, and they’re spelled out in Section 4.2(a) of the Docker Subscription Service Agreement: Docker Desktop can be used without a paid subscription only “for a non-commercial open source project” or “in a commercial undertaking with fewer than 250 employees and less than US $10,000,000 (or equivalent local currency) in annual revenue.” Both conditions have to be true. Government entities aren’t covered by either exception and must subscribe regardless of size. Cross that line and you need Pro ($11/user/month, or $9 billed annually), Team ($16/user/month, or $15 billed annually, up to 100 users), or Business ($24/user/month, billed annually only, unlimited users).
Podman Desktop has no equivalent test. It’s free and open source software with no per-seat charge and no company-size clause — a 5,000-person enterprise can run it in production the same way an individual hobbyist can. Red Hat sells the “Red Hat Build of Podman Desktop,” a supported distribution with long-term maintenance, but that’s an optional support contract layered on top of a tool that’s already free to use.
OrbStack’s free tier is explicitly scoped to personal, non-commercial use. Any business or commercial use requires Pro, priced at $8 per user per month (or $96 per user billed annually — the same effective rate, just a different billing cadence), which adds a container debug shell, priority support, and batch purchasing for organizations. Enterprise is quote-based and adds SAML SSO and invoice/PO payment options.
Platform Support
Docker Desktop and Podman Desktop both run on Windows, macOS, and Linux, so platform support isn’t a differentiator between those two. OrbStack is the outlier: its own site describes it throughout as a native Swift app built around Apple Silicon, Rosetta, and macOS-specific integrations like the menu bar and Activity Monitor, with no Windows or Linux host support mentioned anywhere. If your team is mixed-OS, OrbStack is only ever going to cover part of it.
Resource Usage and Performance Claims
OrbStack is the only one of the three that publishes specific resource-usage figures on its own site: it claims less than 0.1% background CPU usage on Apple Silicon, under 10 MB of disk space used out of the box, and “low initial memory usage,” along with a general claim of starting “in seconds.” Its one quantified head-to-head comparison is a self-published development-environment provisioning benchmark from August 2023 showing roughly 17 minutes for OrbStack versus 45 minutes for Docker Desktop — useful directionally, but a vendor-run, multi-year-old benchmark that neither we nor you can independently re-verify against current versions of either product, so treat it as a data point rather than a current guarantee. Docker Desktop and Podman Desktop don’t publish comparable head-to-head benchmarks on their own sites, so we aren’t including unsourced memory or CPU numbers for either here.
Kubernetes Support
All three include local Kubernetes support, but the implementations differ. Docker Desktop bundles a standalone Kubernetes server and client that runs inside Docker containers, with a choice of provisioner: kubeadm for a single-node cluster, or kind for a multi-node cluster where you control the node count and version. On Linux, Docker Desktop doesn’t install kubectl for you — you add it yourself.
Podman Desktop leans on Podman’s native Kubernetes support and lets you spin up local Kind or Minikube clusters, or connect to remote clusters, directly from the GUI. From there you can inspect, configure, and orchestrate pods, services, and deployments, plus pull logs and metrics for debugging — all without leaving the app. If your team’s Kubernetes needs eventually outgrow a laptop, our comparison of Kubernetes, Amazon ECS, and HashiCorp Nomad for production orchestration covers where each of those fits.
OrbStack also lists Kubernetes among its supported features and includes a Kubernetes category in its own benchmark comparisons, though — consistent with the rest of its site — it doesn’t publish configuration details like node counts or provisioner choices the way Docker’s documentation does.
Pros
Docker Desktop: Runs on all three major desktop OSes, the most tutorials and CI images assume it by default, bundles a flexible single- or multi-node local Kubernetes cluster.
Podman Desktop: No commercial-use restriction at any company size, daemonless/rootless-capable architecture, cross-platform (Windows/macOS/Linux), CNCF Sandbox project with optional Red Hat enterprise support.
OrbStack: Native macOS app with fast startup and low idle resource claims, drop-in compatible with existing Docker CLI and Compose workflows, simple two-tier commercial pricing.
Cons
Docker Desktop: Free use is explicitly gated by a 250-employee / $10M-revenue test, government entities must pay regardless of size, and per-seat costs scale with every developer once you cross the threshold.
Podman Desktop: Smaller ecosystem and fewer third-party tutorials than Docker; teams migrating existing Docker-specific tooling may hit small compatibility gaps worth testing before a full switch.
OrbStack: macOS only — no path to Windows or Linux hosts at all; the free tier is personal-use only, so any business use requires a paid seat from day one; its headline speed benchmark is vendor-published and over two years old.
Who It’s a Good Fit For
Small teams and solo developers who qualify under Docker’s revenue and headcount limits, or who are happy to pay for Pro/Team/Business, are well served by Docker Desktop’s breadth and ecosystem. Teams of any size — especially larger ones that would trip Docker’s commercial-use threshold — that want a genuinely free, cross-platform runtime with a security-conscious daemonless architecture are the best fit for Podman Desktop. All-Mac engineering teams who want the fastest possible local container experience and don’t need Windows or Linux parity should look at OrbStack, budgeting for its Pro tier the moment the work becomes commercial.
Who Should Look Elsewhere
Mid-sized or larger commercial teams who want to avoid a subscription entirely should skip Docker Desktop’s free tier and look at Podman Desktop instead. Mixed-OS shops with Windows or Linux developers on the team should skip OrbStack, since it simply doesn’t run there. And anyone who needs a single tool with the largest body of existing documentation and third-party integrations should be cautious about moving fully off Docker Desktop, even if Podman or OrbStack fit the budget better.
Bottom Line
There’s no universally “best” pick here — the right tool depends on company size, operating system mix, and how much weight you put on ecosystem maturity versus licensing cost. Docker Desktop remains the safest default for small, qualifying teams and for anyone needing Windows/macOS/Linux parity, but it’s the only one of the three with an explicit paywall tied to how big your company is. Podman Desktop is the strongest option for any team, of any size, that wants to remove that licensing question entirely without giving up cross-platform support or Kubernetes workflows. OrbStack is worth it specifically for Mac-first teams chasing the fastest local dev-loop experience, as long as everyone on the team is on a Mac.
FAQ
Does my small business qualify for free Docker Desktop? Only if your commercial undertaking has fewer than 250 employees AND less than US $10,000,000 in annual revenue — both conditions must hold, per Section 4.2(a) of the Docker Subscription Service Agreement. Non-commercial open source projects are free regardless of size. Government entities must subscribe regardless of size or revenue.
Is Podman Desktop really free for a large company? Yes. Podman Desktop is open source with no company-size or revenue clause in its licensing. Red Hat sells optional paid enterprise support (the Red Hat Build of Podman Desktop) for teams that want it, but using the tool itself costs nothing at any scale.
Can I run OrbStack on Windows or Linux? No. OrbStack is built as a native macOS app and its own site describes it entirely in terms of macOS-specific technology (Apple Silicon, Rosetta, the menu bar). There’s no Windows or Linux host version.
Do all three support Kubernetes locally? Yes, though differently. Docker Desktop bundles a kubeadm (single-node) or kind (multi-node) cluster. Podman Desktop uses Podman’s native Kubernetes support plus local Kind/Minikube clusters and a pod/service/deployment management UI. OrbStack lists Kubernetes as a supported feature but publishes fewer configuration details about it.
Is the OrbStack speed claim versus Docker Desktop still accurate? Unclear. OrbStack’s own published benchmark showing roughly 17 minutes versus 45 minutes for a development-environment provisioning task is dated August 2023 and was run by OrbStack itself. Both products have shipped multiple releases since, so treat the gap as directional rather than a current, independently verified figure.
Every public or partner-facing API eventually needs a documentation site, and in 2026 that almost always means picking between three very different approaches: ReadMe’s all-in-one developer hub, Mintlify’s docs-as-code platform built for AI-native teams, and Stoplight’s design-first, spec-driven workflow, now owned by SmartBear. Each one solves “API docs” differently enough that the right pick depends heavily on how your team already works, not just which has the nicest demo.
At a Glance
ReadMe
Mintlify
Stoplight (SmartBear)
Free plan
Starter: $0/mo, 1 project, custom domain, interactive API reference
Starter: $0/mo, 5 editor seats, full platform, API playground
Basic: $41/user/mo (annual, 3 users included) or $52/mo billed monthly
Interactive API explorer
Yes — “interactive API reference” on every tier, including free
Yes — “API playground” on every tier, including free
Yes — “API console (try it out)” plus interactive API docs
OpenAPI/Swagger import
Yes — dedicated OpenAPI upload and resync tooling
Yes — documented OpenAPI setup for the API playground
Yes — OpenAPI/JSON Schema visual designer and OpenAPI export
Versioning
1 published version free, unlimited on Pro/Enterprise
Not clearly documented on the pricing page
Listed as a standard documentation feature on paid tiers
Custom domain
Included, even on the free Starter plan
Included, even on the free Starter plan
Included, but with Stoplight branding unless removed on a paid tier
AI-assisted docs
AI Dropdown, LLMs.txt and MCP Server free; Ask AI, AI Writer, AI Linter on Pro+ ($150/mo add-on)
AI Assistant, Automations and writing Agent on Pro/Enterprise with monthly credits
Not advertised as a feature on the public pricing/compare pages
Best for
Developer-facing product docs with branching and AI add-ons
Docs-as-code teams wanting Git-based workflows and AI automation
Spec-first API design paired with SmartBear’s broader API toolchain
Short Verdict
ReadMe is the strongest pick for teams that want a polished, interactive developer hub with minimal setup and built-in AI docs assistance, but its jump from a one-project free plan to a $250/month Pro tier is steep. Mintlify is the best fit for engineering teams that already think in Git and want their docs built the same way they build software, with AI automation layered on top — though its Pro tier is priced even higher, and per-credit AI overages need watching. Stoplight, now part of SmartBear’s API portfolio, is the most design-and-governance-oriented of the three, built around OpenAPI specs and visual API design rather than hand-written docs, and it remains the most affordable entry point per seat for small teams.
What It Is
ReadMe is a hosted developer hub: you upload or sync an OpenAPI document, and it generates an interactive, try-it-now API reference alongside guides, changelogs, and a markdown-based content editor. It’s aimed squarely at companies that treat their API docs as a product surface in their own right, with metrics on who’s reading what and where developers get stuck.
Mintlify takes a docs-as-code approach: documentation lives in a Git repository (often alongside the codebase), written in MDX, and Mintlify renders it into a branded site with an OpenAPI-powered API playground. It has leaned hard into AI over the past year, adding an AI Assistant that can answer reader questions and an Automations feature that keeps docs in sync with code and API changes.
Stoplight started as a spec-first API design platform: a visual OpenAPI/JSON Schema editor, mocking, and linting, with documentation as one output of that workflow rather than the whole product. SmartBear acquired Stoplight in August 2024. Since then, SmartBear has been folding Stoplight’s open-source tools — Spectral (linting), Elements (docs rendering), and Prism (mocking) — into its Swagger product line as part of a broader “API Hub” portfolio, while Stoplight’s own commercial platform continues to be sold and priced as a standalone product at stoplight.io.
Pricing Breakdown
ReadMe: Starter is free forever and includes one project, one published version, a custom domain, bi-directional OpenAPI sync, an interactive API reference, usage analytics, a markdown editor, and customizable themes, plus some AI basics (AI Dropdown, LLMs.txt, an MCP server). Pro is $250/month (billed annually) and adds unlimited published versions, team invites, multiplayer editing, branching and review workflows, private docs, a landing page, changelogs, custom MDX components, and lighter AI features (Ask AI Lite, AI Linter, AI Writer). A 14-day Pro trial is available with no credit card required. Enterprise is custom-quoted and adds unlimited seats, combined multi-project metrics, white-labeling, SSO/OAuth, audit logs, and full Ask AI API access. A standalone “Ask AI” add-on costs $150/month on both Starter and Pro if you want the fuller AI assistant without upgrading everything else.
Mintlify: Starter is free with 5 editor seats, the full platform, custom domain, web-based editor, authentication, an MCP server, and the API playground — no AI credits included. Pro is $450/month billed annually (or $540/month billed monthly) and removes the seat cap, adding the AI Assistant, Automations, a writing Agent, preview deployments, and Admin APIs, bundled with 10,000 credits per month before $0.01-per-credit overages kick in (Assistant answers cost roughly 25 credits each, Automations updates around 250 credits, and the writing agent itself is unlimited). Enterprise is custom-quoted and layers on SSO, SCIM, RBAC, a performance SLA, and committed-volume AI credit discounts. A 14-day Pro trial with 5,000 credits is available without a credit card.
Stoplight: The Free plan covers 1 user and 1 project with Stoplight branding on your docs. Basic runs $41/user/month billed annually (or $52/month billed monthly) for 3 included users, with extra seats at $10/month annually or $13/month-to-month. Startup is $105/user/month annually ($137 monthly) for 8 included users. Pro Team is $338/month annually ($423 monthly) for 15 included users and supports up to 20 teams, with extra seats at $20/month annually or $25/month-to-month. All paid tiers support unlimited projects; Enterprise pricing and user counts are custom. Removing Stoplight branding and adding custom domains without that branding requires moving off the Free plan.
Core Features Compared
All three tools support importing an OpenAPI/Swagger definition and generating an interactive, try-it-now API explorer from it — this is table-stakes in the category now, not a differentiator. ReadMe calls out dedicated “OpenAPI Support” and resyncing documentation for keeping a live reference in step with an evolving spec. Mintlify documents an OpenAPI setup flow specifically for powering its API playground. Stoplight goes a step further on the design side with a visual OpenAPI/JSON Schema editor for building specs from scratch, not just rendering an existing one, which fits its “spec-first” origins.
Versioning is handled most explicitly by ReadMe, where the free plan caps you at one published version and paid tiers unlock unlimited versions — useful if you support multiple live API versions simultaneously. Stoplight lists versioning as a standard documentation capability on its paid tiers. Mintlify’s own pricing page doesn’t spell out a versioning feature, so if strict multi-version doc hosting is a hard requirement, confirm directly with Mintlify before committing.
Custom domains are included on all three platforms’ entry tiers, though Stoplight’s free plan keeps Stoplight branding visible — removing it needs a paid plan. AI assistance is where the three diverge most: ReadMe and Mintlify both ship AI writing/answering features gated mostly behind paid tiers (ReadMe’s fuller Ask AI is a $150/month add-on even on paid plans; Mintlify meters AI use by credits with overage billing), while Stoplight’s current public pricing and comparison pages don’t advertise reader-facing AI features at all — its AI emphasis under SmartBear seems concentrated in the Swagger/API Hub side of the business instead.
Pros and Cons
ReadMe pros: genuinely free single-project tier with a real interactive API reference and custom domain; strong analytics on reader behavior; mature OpenAPI sync. Cons: Pro jumps straight to $250/month with no mid-tier step; full AI features cost extra even on Pro.
Mintlify pros: true docs-as-code workflow that fits existing engineering practices; generous 5-seat free tier; AI Automations can keep docs from drifting out of sync with the API. Cons: Pro is the most expensive entry-level paid tier of the three at $450–540/month; AI usage is metered by credits, which adds billing complexity.
Stoplight pros: cheapest per-seat entry point of the three; strongest spec-design tooling (visual OpenAPI/JSON Schema editor); scales cleanly by user count. Cons: free plan keeps Stoplight branding; no advertised AI-assisted writing features; its roadmap now sits inside SmartBear’s broader, somewhat fragmented API tooling strategy.
Who It’s a Good Fit For / Who Should Look Elsewhere
ReadMe fits product and developer-relations teams that want a dedicated, hosted API hub with minimal infrastructure to manage and solid out-of-the-box analytics — look elsewhere if your budget can’t stretch past the free single-project tier to the $250/month Pro plan. Mintlify fits engineering-led teams already comfortable with Git-based content workflows who want AI to help maintain accuracy as APIs change — it’s a weaker fit for non-technical writers who’d rather work in a web editor without touching a repo, and budget-conscious teams should watch the credit-metered AI costs closely. Stoplight fits teams whose real need is API design and governance — building and linting specs collaboratively — with documentation as a byproduct, and its per-seat model scales affordably for small teams; it’s a weaker fit if AI-assisted doc writing is a priority, since that isn’t a feature it currently markets.
Bottom Line
There’s no single winner here because the three tools optimize for different jobs: ReadMe for a polished, analytics-rich developer hub; Mintlify for docs-as-code teams that want AI woven into their existing engineering workflow; and Stoplight for spec-first API design and governance at a lower per-seat cost, now backed by SmartBear’s broader API tooling. If your API docs are a core product surface and you want AI help writing and maintaining them, start with ReadMe or Mintlify’s free tiers and compare the AI workflow directly. If your bigger problem is designing and governing the API itself — and docs are just one output — Stoplight is worth testing first.
FAQ
Is Stoplight still sold as its own product after the SmartBear acquisition? Yes. SmartBear acquired Stoplight in August 2024 and has since integrated several of Stoplight’s open-source tools (Spectral, Elements, Prism) into its Swagger/API Hub lineup, but Stoplight’s commercial platform is still marketed and priced on its own at stoplight.io as of this writing.
Do all three tools support importing an existing OpenAPI/Swagger file? Yes. ReadMe has dedicated OpenAPI upload and resync tooling, Mintlify documents an OpenAPI setup flow for its API playground, and Stoplight includes a visual OpenAPI/JSON Schema editor plus OpenAPI export.
Which of these has the most generous free plan? By seat count, Mintlify’s free Starter plan (5 editor seats) is the most generous. By per-seat dollar cost once you outgrow free, Stoplight’s Basic tier ($41/user/month annually) is the cheapest entry point among the paid plans.
Does any of these charge extra specifically for AI features? Yes. ReadMe sells a standalone “Ask AI” add-on for $150/month even on paid plans, and Mintlify meters AI Assistant and Automations usage through a monthly credit allowance with per-credit overage billing on Pro and Enterprise.
Retail media is now a line item in most brand marketing budgets, not a side experiment. The three networks advertisers ask about most are Amazon Ads, Walmart Connect, and Instacart Ads — each sitting on top of a different first-party purchase dataset and a different mix of self-serve and managed access. None of the three publish a flat rate card or a universal minimum spend, because retail media runs on auction-based bidding, not a price list. What follows is pulled from each platform’s own official pages, so the numbers that do appear (and the ones that don’t) are what each company actually discloses, not estimates.
At a Glance
Platform
Ad Formats
Access Model
Best For
Amazon Ads
Sponsored Products, Sponsored Brands, and unified Display/Video/Audio (DVA) campaigns — formerly separate Sponsored Display and Amazon DSP products
Self-serve for sponsored ads (Professional selling account); self-serve or managed for DVA; managed DVA+/advanced settings typically needs a much larger budget
Sellers and vendors wanting the largest retail audience plus Amazon’s streaming and Twitch inventory
Walmart Connect
Sponsored Products, Sponsored Brands, Sponsored Videos, Onsite/Offsite Display, in-store and Store ads
Self-serve through Ad Center (Seller Center/Supplier Center login) or managed through Walmart Platform Partners; brand formats require Brand Portal onboarding
Marketplace sellers and 1P suppliers wanting omnichannel reach, including physical stores
Self-service Ads Manager/API; Sponsored Products is described as “available to brands only”
CPG brands that want fast activation against high-intent grocery and delivery search
What a Retail Media Network Actually Is
A retail media network lets brands pay to place ads inside a retailer’s own shopping environment — search results, product pages, the retailer’s app or site, and increasingly its streaming and in-store screens — using that retailer’s logged-in purchase and browsing data for targeting. The appeal over open-web advertising is the data: a retailer knows what a shopper actually bought, not just what they clicked, and can close the loop on sales attribution without relying on cookies or device IDs. The trade-off is reach: each network only covers its own shoppers, so most serious advertisers run campaigns on more than one at the same time.
Amazon Ads: Sponsored Products, Sponsored Brands, and DVA (formerly Sponsored Display / Amazon DSP)
Amazon’s advertising lineup went through a significant restructuring in 2026. Sponsored Products and Sponsored Brands remain distinct, cost-per-click, auction-based formats: Sponsored Products targets by keyword or product and requires a Professional selling account with a Featured Offer-eligible listing, while Sponsored Brands (video, image, or product-collection ads at the top of search and on product pages) additionally requires the account’s brand to be enrolled in Amazon Brand Registry, and can be bought on CPC or cost-per-1,000-viewable-impressions (VCPM).
What used to be two separate products — Sponsored Display and the standalone Amazon DSP — have been folded into unified Display, Video, and Audio (DVA) campaigns inside a new platform Amazon calls Amazon Ads Agent, announced at its unBoxed 2026 event. DVA runs across Amazon.com, Prime Video, Twitch, Fire TV, Echo Show, Thursday Night Football, and thousands of third-party apps and sites. Advertisers who want manual, DSP-style control can still reach it through an “advanced settings” toggle inside the same console. On pricing, Amazon’s own advertiser FAQ states Sponsored Products self-serve has a $1.00 minimum daily budget and DVA self-serve campaigns carry no stated minimum, while working with an Amazon Ads account executive on managed-service display, video, or advanced DVA+ campaigns “typically requires a minimum spend of $50,000 (USD)” (audio managed service is typically $25,000). That $50,000 figure is the one hard number Amazon discloses for managed service — self-serve access has none.
Amazon’s targeting edge comes from first-party shopping signals feeding both campaign targeting and two measurement tools: Amazon Attribution, a free tool that measures how off-Amazon marketing (search, social, display, email) drives on-Amazon detail-page views and purchases inside a 14-day window, open to vendors, sellers, Brand Registry owners, and KDP authors who sell and advertise on Amazon; and Amazon Marketing Cloud (AMC), a pseudonymized clean room for deeper, event-level analysis. As of an October 2024 change, AMC no longer requires DSP usage to register, but direct advertisers running only Sponsored Ads still can’t register for AMC on their own — they need to go through an Amazon Ads registered partner.
Walmart Connect: Sponsored Search, Sponsored Brands, and Display
Sponsored Products on Walmart Connect appear in search in-grid results, carousels, the Buy Box, “My Items” in-grid, and “Stock up” placements, won through an auction combining bid and product relevancy; the product must be in stock, winning the Buy Box, and published on Walmart.com. Targeting is automatic — Walmart’s own documentation says the system selects keywords on the advertiser’s behalf rather than offering manual keyword targeting as the primary option. Sponsored Brands and Sponsored Videos sit a step higher in eligibility: the brand owner must be based in the US, China, Hong Kong, the UK, or India, hold a USPTO-registered trademark, and be onboarded to the Walmart Brand Portal. All three formats are cost-per-click.
Access runs through the self-serve Walmart Connect Ad Center, signed into with an existing Seller Center or Supplier Center account, or through a Walmart Platform Partner for a managed setup. Walmart’s own marketing page does not state a minimum spend for either path, describing the platform as open to “businesses of all sizes.” On the data side, Walmart Connect’s pitch is targeting built on both online and in-store transaction data — a genuine differentiator from Amazon and Instacart, since Walmart can tie digital ad exposure to brick-and-mortar purchases. Reporting is described as “closed-loop” inside Ad Center; advertisers who want deeper shopper and category research can separately license Walmart Luminate, Walmart’s standalone retail data and analytics platform (renamed from Data Ventures/DSS in 2024), which sits alongside — not inside — standard ad-campaign reporting.
Instacart Ads: Sponsored Products, Display, and Shoppable Formats
Instacart’s ad formats, per its own advertiser documentation, span Sponsored Products (shown on the homepage, in search results, and while browsing), standard Display banners across storefronts and departments, Shoppable Display (brand imagery paired with a bundle of complementary items in search results), Shoppable Video, and Brand Pages — shoppable landing destinations with their own URL. Sponsored Products use a second-price CPC auction: Instacart’s documentation states advertisers are charged “$0.01 more than your next-best competitor’s bid,” with a choice of optimized or manual bidding and either a lifetime or daily budget.
Access is explicitly self-service, through what Instacart’s advertiser terms call the “Instacart Self-Service Platform” (branded externally as Ads Manager), or via its advertiser API for larger operators managing campaigns programmatically. Instacart’s own Sponsored Products documentation notes the format is “available to brands only,” meaning advertisers set up as registered CPG brands rather than arbitrary third parties. No minimum spend is stated in Instacart’s published advertising terms. On measurement, Instacart advertises real-time, closed-loop reporting tied to purchases across more than 80,000 partner retail stores; one case figure the company discloses is a 15%+ average incremental sales lift from Sponsored Products, based on an internal four-week test ending February 2023 — a self-reported result, with Instacart’s own page noting results may not be maintained or replicated for every advertiser.
Side-by-Side Comparison
Dimension
Amazon Ads
Walmart Connect
Instacart Ads
Core self-serve formats
Sponsored Products, Sponsored Brands, DVA (self-serve)
Closed-loop Ad Center reporting; Walmart Luminate (separate paid product)
Closed-loop reporting via Ads Manager/API
Trade-Offs
Reach vs. data specificity: Amazon’s audience and inventory (including streaming and Twitch) are the broadest of the three, but Walmart’s in-store transaction data and Instacart’s grocery-delivery intent data each capture purchase moments Amazon doesn’t see.
Self-serve access isn’t equal across formats: on all three networks, the basic sponsored-product format is comparatively easy to start; brand-level formats (Sponsored Brands/Videos, and Amazon’s Brand Registry-gated options) add registration requirements that smaller or unregistered sellers can’t clear.
Managed service changes the math: Amazon is the only one of the three that discloses a managed-service spend threshold ($50,000 for DVA+/advanced display, video, and audio); Walmart and Instacart simply don’t publish one, which could mean no strict floor, or could mean pricing is negotiated case by case — their public pages don’t say which.
Measurement maturity varies: Amazon’s two-tier system (free Attribution, partner-gated AMC) is the most documented; Walmart’s Luminate is a separate, non-bundled product; Instacart’s reporting is the most self-contained but the least detailed in public documentation.
Bottom Line
Pick Amazon Ads if reach and streaming/CTV inventory matter most and you’re prepared for Brand Registry requirements on the formats that need them. Pick Walmart Connect if omnichannel measurement — tying digital ad exposure to in-store purchases — is the differentiator you actually need, and you can clear the trademark and Brand Portal bar for anything beyond basic sponsored search. Pick Instacart Ads if your product sells through grocery delivery and you want the fastest path from signup to a live, self-serve campaign without a managed-service relationship. None of the three will hand you a published price list or a universal minimum spend beyond what’s noted above — that’s standard for retail media, and budgets are better planned around auction dynamics and test-and-learn spend than around a number no platform will confirm in writing. For a look at how these retail formats compare to open-web programmatic buying, see our programmatic advertising platform comparison.
FAQ
Is there a minimum ad spend to advertise on these networks? Only Amazon discloses one, and only for managed service: its advertiser FAQ states display, video, and advanced DVA+ campaigns run through an account executive typically require a $50,000 minimum. Self-serve Sponsored Products on Amazon has a $1.00 minimum daily budget. Walmart Connect and Instacart Ads do not publish any minimum spend for their self-serve platforms.
What happened to “Amazon DSP”? At Amazon’s unBoxed 2026 event, the standalone DSP console was folded into a new unified platform called Amazon Ads Agent, with Display, Video, and Audio (DVA) campaigns as the default workflow. An “advanced settings” toggle still exposes a more traditional, manually controlled DSP-style experience for advertisers who want it.
Do I need to sell products on the retailer’s site to advertise there? On Amazon, DVA campaigns are open to both sellers and non-sellers; Sponsored Products and Sponsored Brands require a Professional selling account. On Walmart Connect, Sponsored Products requires the product to be live and winning the Buy Box on Walmart.com. Instacart’s Sponsored Products are described as available to registered brands rather than open to any advertiser.
Which platform has the best targeting data? Each is strongest on its own purchase context: Amazon on broad e-commerce and streaming behavior, Walmart on combined online-plus-in-store transactions, and Instacart on grocery and delivery intent. None of the three publish granular detail on audience segment counts or match rates, so comparisons beyond format and access are necessarily qualitative.
Slack, Microsoft Teams, and Discord all get lumped into “team chat” conversations, but they solve a narrower problem than the video-meeting tools that often get compared alongside them. This article is specifically about day-to-day text chat — channels, threads, search, and app integrations — not video conferencing. If you’re trying to pick a meeting platform instead, our Google Meet vs Microsoft Teams vs Zoom comparison covers that separately. Every price and limit below was pulled directly from each vendor’s own pricing or product pages as of November 2026.
Yes — unlimited users, but message history capped at 90 days and apps capped at 10
Teams that want polished channels, search, and the deepest app ecosystem
Microsoft Teams
Essentials: $4/user/mo billed annually
Yes — a free consumer/small-business tier exists; group meetings run free up to 60 minutes and 1:1 calls up to 30 hours, with 100 meeting participants and 5 GB storage per user. Microsoft’s own pages don’t publish a chat-history cap for this tier.
Companies already on Microsoft 365 that want chat bundled with meetings and Office apps
Discord
Nitro Basic: $2.99/mo (optional — chat itself is free)
Yes — core text and voice chat is free with no seat limit; Discord’s own pricing pages don’t publish a message-history cap the way Slack does
Communities and informal teams that want always-free, unlimited-history chat with voice channels built in
Short Verdict
Slack is still the most polished dedicated business chat tool, but its free plan’s 90-day message-history cutoff is the single biggest limitation among the three. Microsoft Teams makes the most sense if you’re already paying for Microsoft 365, since chat, file sharing, and search come bundled rather than priced separately. Discord is the odd one out — built for communities and gaming, not enterprises — but its free tier doesn’t impose Slack’s history cap, and for small, informal, or dev-adjacent teams that don’t need admin controls or compliance features, it’s a genuinely usable (and free) alternative.
What It Is
Slack is a channel-based business messaging app owned by Salesforce, built around organizing conversations by topic (channels), threading replies so discussions don’t bury the main channel, and a large third-party app directory. Microsoft Teams is Microsoft’s chat-and-collaboration hub, bundled into Microsoft 365 alongside Outlook, Word, and Excel, combining persistent chat with its own channels and integrated Office file collaboration. Discord started as a gaming-community chat app and has since picked up genuine workplace use among startups, open-source projects, and remote teams, offering text channels, threads, and voice channels (always-on voice rooms, not scheduled meetings) in the same server.
Pricing Breakdown
Plan
Price
Message history
Key chat features
Slack Free
$0
90 days
Channels, search, up to 10 app integrations, 1:1 huddles, 1 workspace
Slack Pro
$7.25/user/mo annual ($8.75 monthly)
Unlimited
Unlimited apps, group huddles, Slack Connect, Canvases, Lists, AI thread/channel summaries
Slack Business+
$15/user/mo annual ($18 monthly)
Unlimited
Adds Slackbot AI daily recaps, file summaries, AI search, AI translations, AI workflow generation, and Slack CRM features
Slack Enterprise+
Custom (contact sales)
Unlimited
Adds enterprise search and frontline-teams add-on
Teams (free)
$0
Not published by Microsoft for this tier
Chat via email/phone, file sharing, tasks, polls, 5 GB storage/user
1 TB storage/user, 250+ integrated business apps, 30+ language live captions
Business Standard w/ Copilot
$23.50/user/mo ($20.30 without Teams)
Same chat as above
Bundles Microsoft 365 Copilot across Teams, Word, Excel, and Outlook
Discord (free)
$0
Not capped on the pages Discord publishes
Text channels, threads, voice channels, bot/app integrations via Discord’s app directory, basic emoji and stickers
Discord Nitro Basic
$2.99/mo
Unaffected — Nitro changes perks, not history
50 MB file uploads, 2 Server Boosts, custom emoji/stickers/soundboard, messages up to 4,000 characters
Discord Nitro
$9.99/mo
Unaffected
1 GB file uploads, HD video streaming, custom profiles, all Basic perks
One flag worth calling out: Microsoft’s own Teams pricing and comparison pages don’t state an explicit chat/message-history retention limit for the free or Essentials tiers the way Slack does for its Free plan (90 days). We’re noting that gap rather than guessing at a number. Similarly, Discord’s Nitro and pricing pages don’t publish a standalone price for purchasing a single Server Boost outside of a Nitro subscription (a Nitro subscription simply includes 2 Boosts), so we’re leaving that figure out rather than citing an unverified third-party estimate.
Pros
Slack
Cleanest channel/thread organization of the three for structured, topic-based conversations
Largest and most mature third-party app directory (2,600+ apps on paid plans)
AI features (summaries, daily recaps, search) are built into Business+ rather than sold as a separate add-on
Microsoft Teams
Cheapest paid entry point of the three ($4/user/month for Essentials)
Deep native integration with Outlook, Word, Excel, and SharePoint if you’re already on Microsoft 365
Highest meeting participant cap (300) bundled in at the entry paid tier
Discord
Core chat (channels, threads, voice channels) is entirely free with no seat limit
No published 90-day history cutoff the way Slack’s free plan has
Built-in voice channels work as always-available drop-in rooms, which neither Slack nor Teams chat plans offer natively
Cons
Slack
Free plan’s 90-day message history and 10-app cap are the tightest limits of any free tier compared here
Per-seat pricing climbs quickly once you need Business+ for AI and compliance features
Microsoft Teams
Pricing structure is the most layered of the three — Essentials, Business Basic, and Business Standard each gate different storage, caption, and AI capabilities
Copilot AI is an add-on ($18/user/month) or bundled only at the pricier $23.50/user/month Business Standard tier, not included at the entry price
Free and Essentials tiers don’t publish a clear chat-history retention policy, which makes it harder to plan around than Slack’s stated 90 days
Discord
No official admin/compliance tooling comparable to Slack’s or Teams’ enterprise tiers
Nitro perks are aimed at individual users (profiles, emoji, boosts), not team productivity features like app integrations or AI assistants
Free-tier file upload size is well below both Nitro tiers (50 MB on Nitro Basic, 1 GB on Nitro), and Discord’s own pages don’t state the free-tier figure
Who It’s a Good Fit For
Slack fits teams that live in channels and threads all day and want a mature app ecosystem — marketing, product, and cross-functional teams that juggle a lot of tools tend to get the most out of it, especially once Business+ unlocks AI recaps and search. Microsoft Teams fits organizations already paying for Microsoft 365, where chat, file storage, and Office apps sharing one login and one bill genuinely saves money and admin overhead. Discord fits small teams, open-source projects, creator businesses, and dev-adjacent groups that want free, unlimited-history chat with built-in voice channels and don’t need formal compliance or enterprise admin controls.
Who Should Look Elsewhere
Skip Slack’s free plan if you need to search further back than 90 days of history without paying — that cap is firm. Skip Microsoft Teams if you’re not on Microsoft 365 and don’t want Office apps bundled into your chat bill; the standalone value proposition is weaker outside that ecosystem. Skip Discord if you need SSO, audit logs, data-loss prevention, or any formal compliance certification — none of that is part of its consumer-facing pricing pages, and it’s not built for that use case.
Bottom Line
There’s no universal winner, because these three tools solve the “team chat” problem for different kinds of teams. Slack remains the most purpose-built business chat tool, with the caveat that its free tier’s 90-day history cap is a real constraint. Microsoft Teams is the pragmatic default if you already pay for Microsoft 365, since the chat layer is effectively bundled rather than an added cost. Discord is the free, no-compromise-on-history option for smaller or less formal teams willing to trade enterprise admin tooling for zero cost and built-in voice channels. Match the tool to whichever ecosystem — Salesforce/Slack, Microsoft 365, or neither — your team is already closest to.
FAQ
Which of the three has the longest free message history?
Slack explicitly caps its Free plan at 90 days of searchable message history. Microsoft Teams and Discord don’t publish an equivalent cap on their own pricing or product pages for their free tiers, so Discord in particular is commonly used as a free, effectively unlimited-history chat tool — but neither vendor states a guaranteed retention period in writing the way Slack does.
Is this about video calls too?
No — this comparison is specifically about text chat features: channels, threads, search, and integrations. All three tools also offer video calling, but we cover video-meeting platforms separately in our Google Meet vs Microsoft Teams vs Zoom comparison.
Does Slack or Teams include AI chat features for free?
Slack’s Free plan includes only basic AI features like Slackbot and AI search per its pricing page; the fuller set — daily recaps, file summaries, AI translations, and AI workflow generation — requires Business+ at $15/user/month (annual). Microsoft’s Copilot for Teams is either a $18/user/month add-on or bundled only into the pricier $23.50/user/month Business Standard plan — it isn’t included at the free or Essentials tiers.
What does Discord charge for, if chat itself is free?
Discord charges for Nitro ($2.99/month for Nitro Basic, $9.99/month for full Nitro), which unlocks personal perks like larger file uploads (50 MB and 1 GB respectively), custom emoji and profiles, HD streaming, and Server Boosts that unlock perks for an entire server. Core text and voice chat for any server remains free regardless of Nitro.
Which tool is cheapest for a small team that needs more than the free plan?
Microsoft Teams Essentials, at $4/user/month billed annually, is the cheapest paid entry point among the three. Slack Pro starts at $7.25/user/month billed annually. Discord has no required per-seat paid tier at all — Nitro is optional and purchased per individual, not per team.
If you shopped for live chat software any time before 2024, “Intercom vs. Drift vs. Tidio” was a straightforward three-way comparison. It isn’t anymore. One of those three names has been acquired, folded into a different product category, and is no longer something you can sign up for and see a price on. We checked all three vendors’ own current pages before writing a word of this, and the pricing picture has shifted more than most comparison posts online are letting on.
At a Glance
Tool
Starting Price
Free Plan
AI Chatbot
Best For
Intercom
$19/seat/mo (promo rate; $29 standard) + Fin AI from $0.99 per resolution
No free plan — trial only
Fin AI Agent, ~76% average resolution rate across 12,000+ customers
Support/sales teams that want one platform for chat, helpdesk, and AI
Lyro AI, vendor-claimed ~75% average resolution rate
Small businesses, Shopify and WordPress stores on a budget
Drift (now under Salesloft, “1mind”-powered)
Not publicly listed — sales quote only
No
1mind-powered conversational AI (replaced Drift’s original bot)
Sales teams already bought into Salesloft’s revenue platform
Short Verdict
For most businesses shopping for website live chat in 2026, this is really a two-horse race between Intercom and Tidio, with Drift sitting in a different lane entirely. Intercom is the more complete, more expensive platform — a full AI-powered helpdesk with live chat as one piece of it. Tidio is the lighter, cheaper option built for small teams and ecommerce stores that want a working chat widget and an AI bot without a big monthly commitment. Drift, meanwhile, is no longer a self-serve live chat product you can compare on price at all; it was acquired by Salesloft in February 2024 and has since been absorbed into Salesloft’s sales engagement platform, with its original chatbot replaced by a third-party AI called 1mind.
What It Is
Intercom is a customer communications platform built around a Messenger-style chat widget, a shared team inbox, and Fin, its AI agent. Fin now ships as both a built-in feature of Intercom and a semi-independent product at fin.ai, where Intercom states it averages a 76% resolution rate across more than 12,000 customers and can work across chat, email, voice, social, and Slack — not just the website widget. Fin also plugs into helpdesks beyond Intercom’s own, including Salesforce, Zendesk, HubSpot, and Freshdesk.
Tidio is a live chat and helpdesk tool aimed squarely at small and mid-sized businesses, with Lyro, its AI chatbot, as an add-on or bundled quota depending on plan. Tidio’s own pricing page lists integrations with Shopify, WordPress, Messenger, Instagram, WhatsApp, HubSpot, Salesforce, Zendesk, Pipedrive, Microsoft Dynamics, and Zapier, which covers most of what a small ecommerce or services business would need to connect chat to a CRM or storefront.
Drift was originally built as a “conversational marketing” chatbot aimed at qualifying website visitors into sales pipeline. That product no longer exists as an independent, publicly priced tool. Salesloft’s own newsroom confirms it acquired Drift in February 2024, and Salesloft’s current site states plainly: “We’ve transitioned from Drift to 1mind,” meaning the chat widget on Salesloft’s platform is now powered by a different AI vendor, with Drift reduced to a legacy login link. Neither drift.com/pricing nor salesloft.com/pricing lists a price — both route to a “talk to sales” flow.
Pricing Breakdown
Plan
Price
What You Get
Intercom Essential
$19/seat/mo (promo; $29 standard rate)
Fin AI add-on from $0.99/resolution, Messenger widget, shared inbox and ticketing, pre-built reports, public help center
Intercom Advanced
$85/seat/mo
Everything in Essential, plus multiple team inboxes, workflow automation builder, round-robin assignment, private/multilingual help center, 20 free “Lite” seats
Intercom Expert
$132/seat/mo
Everything in Advanced, plus SSO, HIPAA support, SLAs, multibrand messenger/help center, 50 free Lite seats
Intercom Fin AI Agent (standalone)
From $0.99 per resolution, no seats required
Works on top of Intercom or other helpdesks (Salesforce, Zendesk, HubSpot, Freshdesk)
Tidio Free
$0/mo
50 conversations/mo, 10 seats, 50 lifetime free Lyro AI chats, live chat, ticketing, email management, basic analytics
Bundled into Salesloft’s broader revenue orchestration platform; no self-serve signup or published seat/usage pricing
Pros
Intercom
One platform covers live chat, a shared inbox, a public help center, and an AI agent, so you’re not stitching together separate tools
Fin’s 76% average resolution rate (per fin.ai) is a real, vendor-published number, not a guess, and it keeps climbing by about a point a month according to Intercom
Fin works across channels beyond the website widget — email, voice, social, and Slack — and connects to helpdesks you may already run, including Salesforce and Zendesk
Early-stage startups can apply for steep discounts (up to 93% off, per Intercom’s program)
Tidio
An actual usable free plan — 10 seats and 50 conversations a month, not a 7-day trial dressed up as “free”
Entry paid pricing (around $24–$49/mo) is a fraction of Intercom’s per-seat cost, which matters for small teams
Deep, out-of-the-box ecommerce integrations: Shopify, WooCommerce-adjacent tooling, WordPress, Messenger, and Instagram are all listed on Tidio’s own integrations page
Lyro AI is sold modularly, so you can add a small AI quota without upgrading your whole plan
Drift (Salesloft)
If you’re already a Salesloft customer, chat is now a native part of the same revenue workflow — buyer intent from a chat can route directly into a seller’s prioritized task list
Backed by a larger, well-funded sales engagement company rather than a standalone chat startup
Cons
Intercom
No free plan at all — you’re committing to a paid seat before you’ve tested it beyond a trial
Fin’s $0.99-per-resolution usage fee stacks on top of seat pricing, so costs can climb fast for high-chat-volume businesses
Jumping from Essential ($19–$29/seat) to Advanced ($85/seat) is a steep price cliff for features like multiple inboxes and automation that smaller competitors include much earlier
Tidio
The free plan’s 50 conversations a month runs out quickly for any site with real traffic
Lyro AI conversations beyond the free lifetime quota are billed separately, and that add-on pricing (from $32.50/mo for 50 chats) adds up on top of the base plan
Higher tiers (Plus at $300/mo+, Premium at custom pricing) jump well past what a small business budget usually expects from a “small business” chat tool
Drift (Salesloft)
You cannot see a price, sign up self-serve, or compare cost against Intercom or Tidio without talking to sales first
The product you’d be buying isn’t the Drift chatbot people compared for years — Salesloft confirms the AI underneath is now 1mind, not Drift’s original technology
It’s packaged as part of a broader sales engagement suite rather than sold as a standalone website live-chat tool, so it’s a poor fit if that’s literally all you need
Who It’s a Good Fit For / Who Should Look Elsewhere
Intercom fits support and sales teams that want AI chat resolution, a help center, and a helpdesk inbox under one roof and don’t mind paying per seat plus per-resolution for it. It’s a poor fit for a solo founder or very small team that just wants a chat widget on a marketing site without a recurring per-agent bill.
Tidio fits small businesses, agencies, and ecommerce stores (especially Shopify and WordPress sites) that want live chat and a modest AI bot without committing real budget up front. It’s a poor fit for larger support operations that will blow past the conversation caps every month and end up paying nearly Intercom-level prices for Tidio’s top tiers anyway.
Drift/Salesloft only makes sense if you’re already evaluating or using Salesloft’s broader sales engagement platform and want chat-driven lead routing as part of that. It should be ruled out immediately by anyone shopping specifically for an affordable, self-serve website live chat tool — that’s simply not what’s being sold anymore.
Bottom Line
Pick Intercom if you want the most capable AI resolution and the most complete support stack and are prepared to pay per seat for it. Pick Tidio if you want live chat and a usable AI bot on a tight budget, especially for an ecommerce or WordPress site. Don’t go into this comparison expecting to put Drift on the same shortlist as a self-serve live chat purchase — it’s now a feature of Salesloft’s sales platform, sold through a sales conversation, not a pricing page. If integrations and automating the handoff between chat and your other apps matter to you, it’s worth also reading our comparison of Zapier, Make, and n8n, since all three live chat tools here can be wired into those platforms for custom workflows.
FAQ
Does Intercom have a free plan? No. Intercom’s pricing page lists paid seats starting at $19/mo under a current promotional rate (standard rate $29/mo), plus a usage-based Fin AI fee from $0.99 per resolution. There’s a free trial, but no permanent free tier.
Is Tidio’s free plan actually usable? Yes, within limits. Tidio’s official pricing page lists 50 conversations a month and 10 seats on the Free plan, plus 50 lifetime-free Lyro AI conversations. It’s enough to test the product or run a very low-traffic site, but most growing businesses outgrow it quickly.
What actually happened to Drift? Salesloft acquired Drift in February 2024, confirmed on both companies’ own press releases. Salesloft has since moved Drift’s chat capability onto a different AI engine, stating on its own site that it has “transitioned from Drift to 1mind.” Drift is no longer available as a standalone, self-serve, publicly priced product.
How accurate are the AI resolution rate claims? They’re vendor-reported, not independently audited. Intercom’s Fin page (fin.ai) states a 76% average resolution rate across 12,000+ customers, with some customers above 85%. Tidio’s Lyro page claims a 75% average. Treat both as marketing figures that will vary a lot based on your own content and conversation volume, and verify against your own data once you’re live.
Which tool has the best CRM integration? Intercom’s Fin connects directly to Salesforce, Zendesk, HubSpot, and Freshdesk in addition to Intercom’s own helpdesk. Tidio’s integrations page lists Salesforce, HubSpot, Pipedrive, and Microsoft Dynamics alongside ecommerce tools like Shopify and WordPress. Drift/Salesloft is built to sync chat data into Salesloft’s own CRM-adjacent sales workflow rather than acting as a general-purpose chat-to-CRM connector.
Signal, WhatsApp, and Telegram get lumped together in casual conversation as “the encrypted messaging apps,” but that framing hides a real architectural split. Two of the three build end-to-end encryption (E2EE) into every default chat. The third encrypts only a feature most people never turn on. Here’s what each app’s own documentation says about how its encryption actually works, what’s encrypted by default versus opt-in, and what each company can see even when your messages can’t be read.
At a Glance
App
Default chat encryption
Group chat encryption
Backup encryption
Open source
Metadata collection
Signal
End-to-end by default, every chat and call (Signal Protocol)
End-to-end by default
Opt-in; end-to-end encrypted when enabled (on-device passphrase or cloud recovery key)
Fully open source — client and server
Minimal by design: no stored contact/social graph, sealed sender hides who’s messaging whom from Signal’s own servers
WhatsApp
End-to-end by default, using a licensed implementation of the Signal Protocol
End-to-end by default
Opt-in; off by default. Standard Google Drive/iCloud backups are not end-to-end encrypted by WhatsApp
Client apps are closed source; only the underlying protocol library is open
Phone number, contacts (if uploaded), device/connection data, usage metadata (who you interact with, how often, for how long), shared across Meta’s family of companies
Telegram
Not end-to-end by default — only opt-in “Secret Chats” are E2E; default “Cloud Chats” use server-client encryption (MTProto)
Not end-to-end — group chats are Cloud Chats only; Secret Chats don’t support groups
No dedicated E2E backup; Cloud Chat history is stored on Telegram’s servers by design
Client apps are open source; server-side code is not published
Cloud Chat data is stored on Telegram’s servers (split across jurisdictions, per Telegram); Secret Chat content is not retained
Signal: Encryption Is the Entire Product
Signal is built around the Signal Protocol, the open-source cryptographic protocol it developed and that the Signal technology documentation lists as a public specification with freely available software libraries (including libsignal on GitHub). Every one-to-one chat, group chat, voice call, and video call is end-to-end encrypted by default — there’s no setting to turn on, because there’s no unencrypted mode to fall back to.
Signal also goes further than encrypting content. Its “sealed sender” feature, described in Signal’s own technical blog post, encrypts the sender’s identity inside the message envelope itself, so Signal’s servers handle delivery without being able to read who sent a given message — only who it’s being delivered to. Signal states it is designed to retain as little user data as possible: by its own account, it does not store users’ contact lists, conversation lists, location, profile avatars, or group membership information. Chat backups are optional. Signal’s support documentation describes two mechanisms — an on-device backup protected by a local passphrase, and an optional “Secure Backup” restored via a recovery key — both end-to-end encrypted, neither on by default.
WhatsApp: Signal’s Encryption, Meta’s Metadata
WhatsApp’s end-to-end encryption is not a separate invention — it’s a licensed implementation of the Signal Protocol. Signal’s own 2016 announcement confirmed the integration was “fully complete” across WhatsApp’s chats, group chats, attachments, voice notes, and voice calls, on all supported platforms. WhatsApp’s own “End-to-End Encryption” page states plainly that “every call you make, and every message, photo, video, file, and voice message you send, is end-to-end encrypted by default, including group chats” on current app versions. On the encryption math itself, WhatsApp and Signal are effectively equivalent.
Where the two diverge is backups and metadata. WhatsApp’s end-to-end encrypted backup option — detailed in a Meta engineering post — is opt-in: it generates a unique backup key, which you either store yourself or protect with a password held in an HSM-based vault that WhatsApp says it cannot read. Without opting in, chat backups still go to Google Drive or iCloud, and WhatsApp’s own description of that default path says only that “WhatsApp does not have access to these backups, and they are secured by the individual cloud-based storage services” — not that they’re end-to-end encrypted by WhatsApp. On metadata, WhatsApp’s privacy policy is explicit: it collects your phone number, contact list (if you opt into contact upload), device and connection details, and usage information covering how you interact with others and the timing, frequency, and duration of that activity — and that data is shared with and received from other Meta Companies for purposes including safety, personalization, and advertising across Meta’s products. None of that touches message content, but it is a meaningfully larger metadata footprint than Signal’s.
Telegram: Encryption Is the Exception, Not the Rule
This is where the comparison usually goes wrong in casual coverage, because Telegram markets itself as a security-focused app and does offer real end-to-end encryption — just not for the chats most people actually use. Telegram’s own FAQ and developer documentation describe two distinct chat types. “Server-client encryption is used in Cloud Chats (private and group chats),” per Telegram’s FAQ — meaning the connection between your device and Telegram’s servers is encrypted (via Telegram’s MTProto protocol), but Telegram’s servers can access the plaintext content, since that’s what lets messages sync across your devices and live in the cloud. Telegram’s end-to-end encryption documentation defines Secret Chats separately, describing them as “one-on-one chats wherein messages are encrypted with a key held only by the chat’s participants” — and critically, Secret Chats are device-specific, not synced to the cloud, and not available for group chats at all.
In practice, that means the default chat you open with a contact, and every group or channel on Telegram, is not end-to-end encrypted — Telegram’s own servers can technically access that content, even if the company’s stated policy is not to hand it over without legal compulsion in multiple jurisdictions. Getting actual E2EE on Telegram requires deliberately starting a Secret Chat with each contact individually, and it’s simply unavailable for groups. Telegram’s client applications (such as Telegram Desktop) are published as open source, but the server-side code that handles Cloud Chats is not, so independent researchers can’t verify server-side behavior the way they can with Signal’s fully open stack.
Comparison Table
Property
Signal
WhatsApp
Telegram
Encryption protocol
Signal Protocol (original implementation)
Signal Protocol (licensed implementation)
MTProto (Cloud Chats); separate E2E layer for Secret Chats only
E2E by default for 1:1 chats
Yes
Yes
No — must manually start a Secret Chat
E2E available for group chats
Yes, by default
Yes, by default
No — not supported in any form
Who can see message content
Only participants, even with server access
Only participants, even with server access
Telegram’s servers can access Cloud Chat content; only participants for Secret Chats
Sender identity hidden from the service
Yes, via sealed sender
Not described in public documentation
No
Company’s metadata visibility
Very limited by design
Phone numbers, contacts, usage patterns; shared across Meta
Full Cloud Chat metadata and content stored server-side
Trade-Offs
No app here is strictly “best” for every use case. Signal’s minimal metadata collection and fully open-source stack give it the strongest privacy guarantees on paper, but that also means fewer convenience features tied to a social graph the app deliberately doesn’t retain, and it has a smaller install base than the other two. WhatsApp’s cryptography is just as strong as Signal’s for message content — the Signal Protocol doesn’t get weaker because Meta licenses it — but its business model depends on metadata and cross-app data sharing that Signal’s doesn’t, and its backups require an extra opt-in step to get the same end-to-end protection Signal and WhatsApp both apply to live chats by default. Telegram’s biggest advantage is features — large public channels, bots, massive group sizes, cross-device cloud sync — and all of those features exist specifically because Cloud Chats aren’t end-to-end encrypted; building sync and 200,000-member groups on top of true E2EE is a much harder problem that Telegram has not solved for its default chat type. Treating Telegram as “the secure one” because it talks about encryption, without checking whether a given chat is actually a Secret Chat, is the most common mistake in this comparison.
The Bottom Line
If end-to-end encryption by default, for every chat type, with the smallest possible metadata trail, is the priority, Signal is the most defensible choice, backed by a fully open-source client and server. WhatsApp offers the same underlying encryption for message content and is far more convenient if the people you talk to already use it, but accept that Meta collects and shares meaningfully more metadata than Signal does, and that you have to manually opt into end-to-end encrypted backups to close that one gap. Telegram is the odd one out: despite its security-forward branding, the chats and groups almost everyone actually uses on it are not end-to-end encrypted at all — only one-on-one Secret Chats are — so it should be evaluated as a cloud-synced messaging and broadcast platform with an optional, limited encryption mode, not as an encrypted messenger by default.
FAQ
Is Telegram end-to-end encrypted? Only in Secret Chats, which are one-on-one, device-specific, and not synced to the cloud. The default chats and all group chats/channels use server-client encryption (MTProto) instead, meaning Telegram’s servers can technically access that content.
Is WhatsApp’s encryption as strong as Signal’s? For message content, yes — WhatsApp uses a licensed implementation of the same Signal Protocol, confirmed complete by Signal in 2016 and covering chats, group chats, and calls. The difference is in metadata collection and backup defaults, not the core encryption math.
Are WhatsApp chat backups encrypted? Only if you opt into WhatsApp’s end-to-end encrypted backup feature, which uses a user-held key or password-protected vault. Without opting in, backups go to Google Drive or iCloud, and WhatsApp’s own documentation says those are “secured by the individual cloud-based storage services” rather than end-to-end encrypted by WhatsApp itself.
Can Telegram read my group chats? Group chats on Telegram are Cloud Chats by design — Secret Chats don’t support groups at all — so Telegram’s servers can technically access that content, consistent with how Telegram’s own FAQ describes server-client encryption for Cloud Chats.
Which app collects the least metadata? Signal, by a wide margin. Its own documentation states it does not store contact lists, conversation lists, group membership, or location, and its sealed sender feature hides sender identity from its own servers. WhatsApp collects phone numbers, device data, and usage patterns that are shared across Meta’s companies. Telegram stores full Cloud Chat content and metadata on its own servers.
E-commerce and performance marketers have a trust problem with their own ad dashboards. Meta says a campaign drove 400 conversions. Google says 350 of those same conversions. TikTok claims another 200. Add them up and you get a number that is nowhere near what Shopify or Stripe actually recorded. Marketing attribution platforms exist to fix that: they pull cross-channel data into one model, run incrementality tests to see which spend is actually causing sales, and give marketers a single, platform-independent number to budget against.
Triple Whale, Northbeam, and Rockerbox are three of the best-known names in this space. All three combine multi-touch attribution (MTA) with some form of incrementality testing and marketing mix modeling (MMM), but they differ sharply in who they’re built for and how (or whether) they publish pricing. We pulled every claim below directly from each vendor’s own site as of November 2026.
At a Glance
Tool
Pricing Model
Best For
Key Features
Triple Whale
Self-serve plans published: Free ($0), Starter (~$179/mo), Advanced (~$259/mo), each requiring a 12-month commitment, for brands under roughly $2M in annual GMV. Above that, pricing scales with GMV and larger/Custom tiers require a quote.
DTC and Shopify-first brands that want MTA, MMM, and incrementality without a lengthy sales cycle.
No self-serve checkout. Every plan (Growth, Starter, Professional, Enterprise) is listed as “contact us for a quote,” with indicative reference figures tied to monthly ad spend rather than fixed prices.
Mid-market to enterprise performance teams spending six to seven figures a month on paid media.
First-party MTA with infinite lookback, Clicks + Deterministic Views (view-through credit), Apex direct-to-platform signal passback, MMM Plus, incrementality as a paid add-on on higher tiers.
Rockerbox
Pricing is not published anywhere on the official site. Every plan is demo-led; there is no indicative figure at all.
Enterprise marketing and analytics teams that want attribution delivered as warehouse-native data they control.
Unified MTA + MMM + incrementability testing (results in 1–2 weeks), native BigQuery/Redshift/Snowflake delivery, 100+ integrations spanning digital and offline channels.
Short Verdict
Triple Whale is the only one of the three that lets you see and buy a plan without talking to anyone, which makes it the default choice for smaller DTC brands. Northbeam and Rockerbox are both quote-only platforms aimed at brands with meaningfully larger ad budgets and in-house analytics or media teams. Of the two, Rockerbox leans harder into data-warehouse-native delivery (BigQuery, Redshift, Snowflake) for teams that want to own and query their own attribution data, while Northbeam leans into closed-loop optimization, feeding its attribution signal directly back into ad platform algorithms through its Apex product.
What It Is
Triple Whale is an e-commerce measurement and operations platform built around a product called Compass, which combines continuously calibrated multi-touch attribution, weekly-calibrated marketing mix modeling, and GeoLift holdout-based incrementality testing into one unified read on marketing performance. Triple Whale also ships an AI assistant, Moby, that it positions as an “AI analyst” for reporting and (increasingly) campaign operations.
Northbeam markets itself as an independent source of ad performance data, intended to replace the inflated, siloed numbers each ad platform reports about itself. Its core product is first-party multi-touch attribution with an “infinite lookback window,” layered with a Clicks + Deterministic Views (C+DV) feature that gives credit for verified video/display views, not just clicks. Incrementality and marketing mix modeling (MMM Plus) are sold as adjacent products rather than bundled into every plan.
Rockerbox frames its pitch most directly against platform self-reported numbers, with language on its site promising to “replace biased platform data with objective truth.” It runs multi-touch attribution, marketing mix modeling, and controlled incrementality experiments on a single underlying data foundation, and is built to hand that data back to a brand’s own BigQuery, Redshift, or Snowflake warehouse so internal teams can query it directly in their own BI tools rather than being locked into a vendor dashboard.
Pricing Breakdown
Triple Whale is the only vendor of the three with genuinely self-serve pricing. Its published plans are Free ($0/month, 12-month lookback, first- and last-click attribution, 10 users), Starter (around $179/month on a 12-month commitment, adding multi-touch attribution and unlimited lookback), and Advanced (around $259/month on a 12-month commitment, adding subscription data, cohort analysis, product/creative analytics, and a SQL editor). These tiers are scoped to brands doing up to roughly $2M in annual GMV. Above that threshold, Triple Whale uses a GMV-based calculator that recommends a higher-priced tier (shown on the site as roughly $1,290/month for larger brands), and its top “Custom” tier — aimed at $20M+ GMV brands wanting custom integrations and SLAs — is an explicit “tailored quote,” not a fixed price. Compass’s incrementality testing (GeoLift) sits under a separate add-on with no published price.
Northbeam publishes no self-serve prices at all. Its site lists four named tiers — Growth, Starter, Professional, and Enterprise — each tied to a monthly ad-spend band (for example, Starter for brands under $1.5M/year in ad spend, Professional for up to $500K/month), but every tier’s call to action is “contact us for a quote.” The site does show reference figures next to Starter (around $1,500) and Professional (around $3,500/month), and its FAQ clarifies that Starter runs on month-to-month, usage-based pricing while Professional and Enterprise are annual contracts — but it explicitly states that exact pricing requires a sales call, so these figures should be read as starting estimates, not list prices. Incrementality testing is sold as an optional add-on available only on Professional and Enterprise.
Rockerbox discloses no pricing information whatsoever on its official site — no tiers, no reference figures, no usage bands. Every call to action (“Get a Demo,” “Talk to an Expert”) leads to a sales conversation. Prospective buyers cannot get even a ballpark number without contacting the company directly.
Core Features Compared
Incrementality testing. All three offer it, but packaging differs. Triple Whale runs GeoLift holdout tests inside Compass, which also feeds results back into its MMM. Northbeam sells incrementality as a stand-alone add-on, limited to its Professional and Enterprise tiers. Rockerbox describes a structured testing process — controlled experiments that can start producing results in 1–2 weeks — whose outputs calibrate its MTA model and serve as priors for its MMM, making it the most explicit of the three about how the different measurement methods feed each other.
Data warehouse integration. Rockerbox is the clearest here: it names direct integrations with BigQuery, Redshift, and Snowflake, explicitly positioning itself as a source of “analytics-ready datasets” for a brand’s own BI tools. Triple Whale’s pricing page mentions “flexible data warehouse and custom integrations” only at its highest, quote-only Custom/Enterprise tiers, with no specific warehouses named. Northbeam’s site does not mention data warehouse integration at all.
Platform/channel coverage. Northbeam names the longest list of ad-platform integrations on its own site — Meta, Google Ads, Microsoft Advertising, Snapchat, Yahoo, X, Amazon Ads, Pinterest, TikTok, The Trade Desk, AdRoll, Criteo, MediaMath, MNTN, Tatari, Rakuten, plus affiliate/influencer tools like Grin and Impact — and its Apex product pushes attribution signal directly back into platform bidding algorithms. Rockerbox advertises “100+ integrations” and explicitly covers offline and hard-to-track channels (CTV, linear TV, direct mail, podcasts) using promo codes and post-purchase surveys, on top of the usual paid social, search, and video platforms. Triple Whale’s integration list centers on Meta, Google, TikTok, Pinterest, and Reddit, plus Klaviyo for email and native Shopify/Amazon/TikTok Shop commerce integrations, with more “Moby Media Buyer” platform connections described as coming soon.
Pros
Triple Whale
Transparent, self-serve pricing with a free tier to start on
Bundles MTA, MMM, and incrementality testing under one Compass product instead of selling them separately
Moby AI assistant adds reporting and forecasting on top of the raw attribution data
Northbeam
Broadest named list of ad-platform and channel integrations of the three
Apex feeds attribution signal directly back into ad-platform bidding algorithms, not just into a dashboard
Clicks + Deterministic Views gives credit for verified view-through, useful for brands running heavy video/display
Infinite lookback window avoids the attribution-window caps built into ad platforms
Rockerbox
Clearest, most explicit methodology for how incrementality results calibrate MTA and feed MMM
Native delivery into BigQuery, Redshift, or Snowflake rather than keeping data locked in a vendor UI
Strong offline/hard-to-track channel coverage (CTV, linear TV, direct mail, podcasts) via promo codes and surveys
100+ integrations spanning both digital and offline channels
Cons
Triple Whale
Published self-serve tiers require a 12-month commitment, which is a real lock-in for a brand still evaluating the tool
Incrementality testing (GeoLift) lives behind the Compass add-on, not the base plans, and that add-on has no published price
No named data-warehouse integrations (BigQuery, Snowflake, etc.) outside the top, quote-only tier
Pricing above roughly $2M GMV requires a custom quote, so the “self-serve” story only goes so far for growing brands
Northbeam
Zero self-serve pricing; every tier, including the lowest, requires a sales conversation
Incrementality testing is gated behind the two most expensive tiers as an add-on, not included by default
No mention of data warehouse integration on its own site
The reference dollar figures shown for Starter and Professional are explicitly estimates, not prices you can lock in without a call
Rockerbox
No pricing information published anywhere, not even a ballpark, making it hard to budget before engaging sales
Fully demo-led buying process adds friction for teams that want to self-evaluate quickly
Smaller brands with lean budgets will likely find the sales-led model mismatched to their scale
Who It’s a Good Fit For / Who Should Look Elsewhere
Choose Triple Whale if you’re a Shopify-first DTC brand doing roughly seven figures or less in GMV, want to see pricing and start without a sales call, and are comfortable adding incrementality testing later as a paid add-on.
Choose Northbeam if you’re spending six to seven figures a month across a wide mix of ad platforms (including CTV/streaming partners like MNTN and Tatari), want attribution signal fed straight back into platform bidding via Apex, and have the budget and patience for a quote-based enterprise sales process.
Choose Rockerbox if your team has its own data warehouse and BI stack and wants attribution delivered as raw, queryable data rather than a locked dashboard, and if you run significant offline/CTV spend that needs promo-code or survey-based tracking.
Look elsewhere if you need a fixed, published price before you can get budget approval from finance — only Triple Whale’s lower tiers offer that, and even those require a 12-month commitment.
Bottom Line
None of these three platforms is simply “attribution software” in the old single-touch sense — all three now sell a bundle of MTA, MMM, and incrementality testing, because no single method is trusted on its own anymore. The real differences are commercial and architectural: Triple Whale is the only one you can actually buy online today, Northbeam is built to feed its numbers straight back into ad-platform algorithms, and Rockerbox is built to hand its numbers straight into your own data warehouse. Teams should pick based on buying process tolerance and where they want the data to ultimately live, not just on feature checklists, since the headline capabilities (MTA + MMM + incrementality) now look similar across all three on paper. If your stack already includes server-side tracking or a Conversions API setup, pairing it with whichever attribution tool you choose will materially improve the data quality feeding these models — see our breakdown of server-side tracking and Conversions APIs for that layer. Brands running affiliate programs alongside paid media should also check our comparison of affiliate tracking platforms, since none of the three attribution tools above are built to manage affiliate payouts.
FAQ
Is any of these three free to try?
Only Triple Whale publishes a free tier ($0/month), and it’s limited to a 12-month lookback and first- and last-click attribution rather than full multi-touch attribution. Northbeam and Rockerbox have no published free tier; both require a sales conversation to even see a quote.
Which of the three includes incrementality testing by default?
None includes it unconditionally at the entry level. Triple Whale’s GeoLift testing is part of its Compass add-on; Northbeam limits incrementality to its Professional and Enterprise tiers; Rockerbox describes incrementality testing as a core methodology but doesn’t publish which plans include it, since it discloses no plan details at all.
Can I get exact pricing without talking to sales?
Only for Triple Whale’s Free, Starter, and Advanced tiers, which are scoped to brands under roughly $2M in annual GMV. Beyond that GMV level, and for Northbeam and Rockerbox at any size, a sales conversation is required to get a real number.
Do any of these tools write directly to a data warehouse?
Rockerbox is the only one of the three to name specific warehouse integrations (BigQuery, Redshift, Snowflake) on its own site. Triple Whale mentions warehouse integration only at its highest, quote-only tier, without naming specific warehouses. Northbeam’s site does not mention data warehouse integration.
Picking a video editor in 2026 usually comes down to three names: DaVinci Resolve, Adobe Premiere Pro, and CapCut Pro. Each one takes a different approach to pricing and workflow — one is built around a free tier with an optional one-time paid upgrade, one is subscription-only with no free desktop plan, and one is a mobile-first AI editor that has grown into a serious desktop and web tool. This guide compares what each actually costs today, what its free plan does and doesn’t include, and which creators each one suits best, using figures pulled directly from each vendor’s own pricing pages.
At a Glance
Tool
Starting Price
Free Plan
Best For
DaVinci Resolve
Free; Studio is a one-time $295 purchase (listed as $236 on a current promotion)
Yes — full color grading, editing, and VFX tools up to Ultra HD (3840×2160), 60fps, 8-bit
Color grading, high-end finishing, and anyone who wants a professional NLE without a subscription
Adobe Premiere Pro
$22.99/mo (single app, annual plan billed monthly); Creative Cloud Pro (20+ apps) from $34.99/mo promo, $69.99/mo standard
No standalone free plan — 7-day free trial only
Professional and team workflows already inside the Adobe/Creative Cloud ecosystem
CapCut Pro
$19.99/mo, with an annual plan advertised at “up to 30% off”
Yes — free templates and basic editing tools, no stated export limit on the pricing page
Short-form social content, mobile editing, and fast AI-assisted cuts
Short Verdict
If budget matters and you care about color and finishing quality, DaVinci Resolve wins — the free version is extraordinarily capable, and the $295 Studio upgrade is a one-time cost rather than a recurring bill. Adobe Premiere Pro remains the default for teams that live inside Creative Cloud, need deep integration with After Effects and Photoshop, and don’t mind a monthly subscription. CapCut Pro is the easiest on-ramp for creators making short-form video on a phone, with AI tools and templates that the other two don’t try to compete with, but it’s the least suited to serious color work or long-form professional output.
What Each Tool Is
DaVinci Resolve is Blackmagic Design’s desktop editing, color grading, visual effects, and audio post-production suite (Fairlight). It ships as two versions: the free edition, which already includes multi-user collaboration tools and HDR grading, and DaVinci Resolve Studio, a one-time paid upgrade that unlocks the DaVinci Neural Engine AI tools, extra noise reduction, Magic Mask, 10-bit video support at higher frame rates, and resolutions beyond 4K. It runs on Mac, Windows, and Linux; Blackmagic does not market a full-featured mobile app in the way the other two tools do.
Adobe Premiere Pro is the timeline-based editor at the center of Adobe’s video workflow, tightly linked to After Effects, Audition, and Photoshop through Creative Cloud. Adobe’s own plans page states plainly that “Premiere is available only through a monthly or annual Creative Cloud subscription” — there is no permanently free desktop tier, only a 7-day trial (14 days on business plans). It’s available on desktop and mobile.
CapCut Pro is ByteDance’s cross-platform editor — web, desktop, and mobile — built around fast, template-driven, AI-assisted editing for short-form content. The free plan covers basic editing and templates with no subscription; CapCut Pro adds expanded cloud storage, more monthly AI credits, and the full premium template and effects library.
Pricing Breakdown
Plan
Price
What You Get
DaVinci Resolve (Free)
$0
Editing, color grading, VFX, and audio tools up to Ultra HD 3840×2160, 60fps, 8-bit; multi-user collaboration and HDR grading included
DaVinci Resolve Studio
$295 one-time license (shown as $236 on a limited-time promotion at the time of writing)
Adds AI-powered noise reduction, DaVinci Neural Engine tools (auto region tracking, Magic Mask), text-based editing, 10-bit video up to 120fps, resolutions beyond 4K, stereoscopic tools, and extra Fairlight audio plugins
Premiere Pro (single app)
$22.99/mo, billed monthly on an annual plan
Full Premiere Pro desktop and mobile app; no bundled Adobe apps
Creative Cloud Pro (All Apps)
Introductory $34.99/mo (first 3 months 50% off for new subscribers), $69.99/mo standard rate, billed monthly on an annual plan
Premiere Pro plus 20+ Creative Cloud apps including After Effects, Photoshop, and Audition
CapCut (Free)
$0
Basic editing tools and free templates; the official pricing page does not list a specific export or watermark limit
CapCut Pro
$19.99/mo (yearly plan advertised as “up to 30% off” monthly, exact annual figure not published)
1 TB cloud storage, 1,200 monthly AI credits, all premium templates and Pro features
Pros
DaVinci Resolve
Best-in-class color grading tools, free, with no watermark or time limit
Studio is a one-time purchase — no recurring bill after $295
Multi-user collaboration built in, even on the free version
Professional audio post-production (Fairlight) included
Adobe Premiere Pro
Deepest integration with After Effects, Photoshop, and Audition
Available on both desktop and mobile
Mature, widely taught, with the largest plugin and tutorial ecosystem
Regular feature updates tied to an active subscription
CapCut Pro
Fastest path from phone footage to a finished short-form video
Large AI toolset (1,200 monthly credits on Pro) for captions, generation, and effects
Works across web, desktop, and mobile with synced projects
Generous 1 TB of cloud storage on the Pro plan
Cons
DaVinci Resolve
Steeper learning curve than CapCut, especially in Fairlight and Fusion
No officially promoted full mobile editing app
Free version caps out at 8-bit, Ultra HD, 60fps — serious 10-bit/high frame rate work needs Studio
Adobe Premiere Pro
No permanent free plan — only a 7-day trial
Full-suite pricing ($69.99/mo standard) is the most expensive option here once promotional pricing ends
Subscription cost never stops as long as you need the software
CapCut Pro
Not built for professional color grading or complex multi-track audio finishing
Official pricing page doesn’t disclose the exact annual price or free-plan export limits upfront
AI credits are consumed by generation features, so heavy AI use can run out faster than expected
Who It’s a Good Fit For
DaVinci Resolve — colorists, documentary and indie filmmakers, and anyone who wants professional-grade finishing tools without an ongoing subscription.
Adobe Premiere Pro — video teams, agencies, and editors already paying for Creative Cloud who need tight integration across Adobe’s app lineup.
CapCut Pro — social media creators, marketers, and anyone editing primarily for TikTok, Reels, or Shorts who wants speed and AI assistance over deep manual control.
Who Should Look Elsewhere
Editors who need a true mobile-first workflow with heavy AI generation should skip Resolve’s free tier and look at CapCut Pro instead.
Budget-conscious solo creators who don’t need Adobe’s ecosystem will likely find Premiere Pro’s subscription harder to justify than Resolve’s one-time Studio fee.
Anyone doing serious color grading, VFX compositing, or professional audio mixing should look past CapCut toward Resolve or Premiere Pro.
Bottom Line
There isn’t a single “best” editor in 2026 — there’s a best fit per workflow. DaVinci Resolve offers the strongest value for anyone willing to learn a more technical tool, especially since the Studio upgrade is a one-time $295 cost rather than a subscription. Adobe Premiere Pro justifies its ongoing $22.99–$69.99/mo pricing mainly through ecosystem integration, not through anything Resolve or CapCut can’t otherwise do. CapCut Pro, at $19.99/mo, is the fastest and most accessible option for short-form, AI-assisted content, but it isn’t designed to replace a professional color and finishing pipeline. For readers also comparing Adobe’s broader app bundle, our Adobe Creative Cloud Review breaks down the full Creative Cloud plan structure in more detail.
FAQ
Is DaVinci Resolve really free, or is it a trial? The standard DaVinci Resolve edition is permanently free with no trial period, per Blackmagic Design’s own product page. Only the Studio edition requires payment, and that payment is a one-time license rather than a subscription.
Does Adobe Premiere Pro have a free version? No. Adobe’s plans page states Premiere Pro is available only through a paid Creative Cloud subscription, with just a 7-day free trial (14 days for business plans) to test it first.
How much does CapCut Pro cost per month? CapCut’s official pricing page lists CapCut Pro at $19.99/month, with a yearly plan advertised as “up to 30% off” the monthly rate; CapCut does not publish the exact annual total on that page.
Which of the three is cheapest long-term? DaVinci Resolve Studio is generally the cheapest over time because it’s a one-time $295 purchase rather than a recurring subscription — Premiere Pro and CapCut Pro both bill monthly or annually for as long as you use them.
Can I edit video on my phone with any of these? CapCut is built mobile-first and is the strongest option for phone editing. Premiere Pro also offers a mobile app alongside its desktop version. DaVinci Resolve is primarily a desktop application without an equivalent full-featured mobile editor.
Nvidia builds the chips. AWS builds the plumbing. When Amazon talks about AI infrastructure, the conversation usually turns to Trainium chips or Bedrock’s managed models — but underneath both sits a less-discussed layer that is arguably just as important: the networking and virtualization stack that lets AWS wire tens of thousands of GPUs together into something that behaves like one giant computer. That stack has two main pieces — the Nitro System and the Elastic Fabric Adapter (EFA) — and this piece looks specifically at how they work and what they actually do.
At a Glance
Component
What It Is
Key Fact
Nitro System
Custom hypervisor and offload hardware underlying modern EC2 instances
Moves virtualization, networking, and storage I/O off the host CPU onto dedicated cards
Elastic Fabric Adapter (EFA)
OS-bypass network interface for HPC/AI workloads
Free add-on on supported instances; EFA on P5 delivers 3,200 Gbps per instance — 8× the prior generation
EC2 UltraClusters
Petabit-scale, non-blocking network connecting large GPU fleets
AWS and Nvidia described scaling to 20,000 H100 GPUs and 20 exaFLOPS (announced March 2023)
Short Verdict
AWS doesn’t win AI infrastructure on chips alone. The Nitro System and EFA are the plumbing that let it treat a rack — or tens of thousands of GPUs across many racks — as a single machine for training. Most of this is invisible unless you’re running distributed training or HPC workloads at scale, but it’s a real part of why AWS can credibly host frontier-scale training jobs at all.
What the Nitro System Actually Does
Every modern EC2 instance type is built on the Nitro System, AWS’s combination of dedicated offload hardware and a lightweight hypervisor. Instead of running networking, storage, and management functions as software on the same CPU that runs customer workloads, Nitro moves them onto dedicated cards:
Nitro Cards handle I/O offload for VPC networking, EBS storage, and instance storage, plus a Nitro Card Controller that coordinates them.
Nitro Security Chip moves virtualization and security functions to dedicated hardware and enforces a locked-down model that blocks administrative access — including, AWS states, by Amazon’s own employees.
Nitro Hypervisor is a lightweight hypervisor that only manages memory and CPU allocation; AWS describes its performance as indistinguishable from bare metal.
Nitro Isolation Engine enforces isolation between instances and between instances and AWS operators.
AWS Nitro Enclaves and NitroTPM provide isolated compute environments and a TPM 2.0-conformant module for cryptographic attestation, respectively — used for sensitive workloads handling PII, healthcare, or financial data.
The practical effect, per AWS’s own description, is that instances get “practically all” of the host’s compute and memory resources, because the host no longer has to reserve capacity for hypervisor or management overhead. That matters for GPU instances specifically: a Nitro-based host spends less CPU and memory on virtualization bookkeeping and more on feeding data to the GPUs.
What EFA Adds on Top
Nitro handles a single instance. Elastic Fabric Adapter (EFA) is what lets many instances act together. EFA is an optional network interface, available at no additional cost on supported instance types, that gives applications a custom OS-bypass hardware interface for inter-instance communication.
Normally, network traffic goes through the operating system’s TCP/IP stack and a standard network driver (AWS’s ENA). EFA skips that path: applications talk to the EFA device through the Libfabric API — the user-space API of the OpenFabrics Interfaces framework — bypassing the kernel entirely. Underneath, EFA uses AWS’s Scalable Reliable Datagram (SRD) protocol, which provides built-in congestion control and low-latency, reliable transport tuned for HPC and ML traffic patterns.
Because most HPC programming models (MPI) and ML collective-communication libraries (notably Nvidia’s NCCL, used by PyTorch, TensorFlow, MXNet, and others) already support Libfabric, AWS says existing distributed training code can usually move to EFA with little or no modification. On GPU instances, EFA also integrates with Nvidia GPUDirect RDMA, letting data move between GPU memory on different instances without an extra trip through host memory.
EFA Has Generations, and Support Varies by Instance
EFA isn’t one fixed spec — it has shipped in multiple versions tied to the underlying Nitro hardware generation, and not every EC2 instance family supports it. AWS’s own EC2 User Guide lists support roughly as follows:
Nitro Generation
EFA Version
Representative Instance Families
Nitro v3
EFA v1
p3dn, p4d/p4de, g4dn, g5, c5n, m5n/m5dn
Nitro v4
EFA v2
p5/p5e, trn1/trn1n, g6/g6e, c6i/c7i, hpc6a/hpc7a
Nitro v5
EFA v3
p5en, trn2/trn2u, c7gn, hpc7g
Nitro v6
EFA v4
p6-b200, p6e-gb200, g7/g7e, hpc8a
RDMA support also varies: older Nitro v3 instances mostly lack RDMA write support, while Nitro v4 and later support RDMA read broadly and RDMA write on most types. EFA traffic cannot cross Availability Zones or VPCs and is not routable — it’s built for tightly-coupled, low-latency communication within a cluster placement group, not general-purpose networking.
How It Comes Together in EC2 UltraClusters
Nitro and EFA combine most visibly in EC2 UltraClusters — AWS’s term for large-scale deployments of GPU instances connected by a petabit-scale, non-blocking network and backed by Amazon FSx for Lustre for high-throughput storage. When AWS and Nvidia announced EC2 P5 instances in March 2023, each P5 instance packed eight Nvidia H100 GPUs, 640 GB of high-bandwidth GPU memory, and 16 petaFLOPs of mixed-precision performance — and used AWS’s second-generation EFA to deliver 3,200 Gbps of networking per instance, eight times the prior generation, integrated with GPUDirect RDMA. AWS and Nvidia stated that UltraClusters built from P5 instances could scale to 20,000 H100 GPUs working together, delivering up to 20 exaFLOPS of aggregate performance, and that some customers were already training models across more than 10,000 GPUs.
This is a different layer from the one covered in our look at AWS’s Trainium and Inferentia chips or Bedrock and SageMaker’s managed AI services. Nitro and EFA are infrastructure that underpins both Nvidia-GPU-based instances (P5, P6) and AWS’s own Trainium-based instances (Trn1, Trn2) — the networking fabric doesn’t care which chip is doing the math.
Trade-offs and Limitations
Not every instance qualifies. EFA is tied to specific instance families and Nitro generations; older or smaller instance types don’t support it at all.
It’s AWS-specific plumbing. EFA competes conceptually with Nvidia’s own InfiniBand and NVLink/Spectrum-X networking (covered in our piece on Nvidia’s networking stack), so workloads tuned tightly for one fabric may need adjustment to move to another cloud or on-prem InfiniBand cluster.
Documented benchmarks are vendor-published. AWS’s own pages cite internal figures (the 4x CFD scaling improvement over its standard ENA networking, for instance) rather than independent third-party benchmarks; treat vendor performance claims as directional, not guaranteed for every workload.
EFA is not routable. It only works within a single cluster placement group in one Availability Zone, so it solves tightly-coupled cluster communication, not general cross-region networking.
Who Should Care
ML infrastructure engineers and platform teams evaluating cloud GPU providers for large-scale distributed training are the main audience — if you’re comparing cloud GPU platforms, the networking fabric underneath the GPU count is often the deciding factor for how well training actually scales past a handful of nodes. If your workloads are single-instance, inference-only, or small-batch, Nitro’s general virtualization benefits still apply, but EFA’s benefits are mostly invisible to you.
Bottom Line
The Nitro System and EFA are the unglamorous but essential layer that turns a pile of GPU instances into a cluster that can actually train large models efficiently. Nitro lowers virtualization overhead on every instance; EFA, where supported, removes the kernel networking bottleneck between instances and lets AWS wire tens of thousands of GPUs into UltraClusters with petabit-scale, non-blocking networking. None of it replaces chip choice or managed-service convenience — it’s the plumbing that makes both of those actually scale.
FAQ
Is EFA free to use? Yes — AWS states EFA is available at no additional cost on supported instance types; you pay the normal EC2 instance price.
Does EFA work with Nvidia GPUs? Yes. On GPU instances like the P5 family, EFA integrates with Nvidia GPUDirect RDMA to move data between GPU memory on different instances with lower latency.
What is SRD? Scalable Reliable Datagram is AWS’s custom transport protocol underlying EFA. AWS describes it as providing built-in congestion control and low-latency, reliable delivery suited to HPC and ML traffic patterns, as an alternative to standard TCP.
How large can an EC2 UltraCluster get? In their March 2023 joint announcement, AWS and Nvidia described UltraClusters built on P5 instances scaling to 20,000 H100 GPUs, delivering up to 20 exaFLOPS of aggregate compute performance.
Nvidia’s GPUs get most of the attention in the AI infrastructure conversation, but Google has been building and running its own AI chips since 2015 — and today they train and serve a meaningful share of the world’s largest AI workloads, including Google’s own Gemini models. Tensor Processing Units (TPUs) are purpose-built silicon that Google rents out through Google Cloud, and in 2026 the lineup looks very different from even a year ago. Here’s what a TPU actually is, what Google currently offers, what it costs, and how the trade-offs against Nvidia GPUs really break down.
At a Glance
What it is
Google’s custom ASIC accelerators for AI training and inference, available only on Google Cloud
Current flagship generations
Ironwood (7th gen) and Trillium (6th gen) — both generally available
Coming soon
TPU 8t (large-scale pre-training) and TPU 8i (post-training and inference)
Core architecture
Systolic-array Matrix Multiplier Unit (MXU), not a general-purpose GPU core
On-demand price
$1.20/chip-hour (TPU v5e) up to $12.00–$13.20/chip-hour (Ironwood), region-dependent
Where you can get one
Google Cloud only — not available from other cloud providers or on-prem
Software support
JAX and OpenXLA natively; PyTorch via TorchTPU; vLLM and SGLang for inference
Short Verdict
TPUs are a legitimate, fast-moving alternative to Nvidia GPUs for teams already building on Google Cloud or on JAX/PyTorch-XLA — especially at the largest training scales, where Google’s co-designed networking and software stack pay off. They are not a drop-in GPU replacement: you’re locked into Google Cloud, the software ecosystem is narrower than CUDA’s, and the newest chip (Ironwood) carries a steep per-chip-hour price. For most teams outside Google’s own ecosystem, Nvidia GPUs remain the path of least resistance; for teams running JAX-based research or large-scale inference on Google Cloud already, TPUs are worth serious evaluation.
What a TPU Actually Is
A TPU is an application-specific integrated circuit (ASIC) — silicon designed from the ground up for one job, rather than a general-purpose chip adapted to that job. Google designs TPUs specifically to accelerate the matrix multiplication and tensor operations that dominate neural network training and inference, and it co-designs the chip alongside the software stack that runs on it.
The core of every TPU is the Matrix Multiplier Unit (MXU), built around a systolic array: thousands of arithmetic logic units (ALUs) arranged so that data is read from memory once and then flows continuously through the array, with partial results accumulating as they pass from one ALU to the next. That’s fundamentally different from a GPU’s architecture, where thousands of general-purpose cores repeatedly read and write to memory as they execute many parallel threads (an approach called SIMT, or single-instruction, multiple-thread). The systolic-array design cuts down on memory traffic for the specific pattern of repeated matrix multiplications in a neural network, which is where TPUs get much of their efficiency advantage for that one workload — at the cost of being far less flexible for other kinds of computation.
TPUs also lean heavily on reduced-precision arithmetic (16-bit and 8-bit floating point formats) to push more computations through the same silicon without sacrificing the accuracy modern AI models need. And they’re designed from day one to work in large groups: a pod is a big cluster of TPU chips wired together over Google’s high-speed interconnect (described by Google as Optical Circuit Switching, branded “Virgo”), and a slice is a smaller, rentable chunk of a pod — which is what you actually provision on Google Cloud.
The Current Lineup: Ironwood and Trillium
As of 2026, Google lists two generally-available flagship TPU generations on its Cloud TPU product page:
Generation
Status
What Google says it’s for
Headline spec Google cites
Ironwood (7th gen)
Generally available
Training, reasoning, and inference
9,216 liquid-cooled chips per pod; 42.5 ExaFLOPS per pod; up to 4x the performance per chip versus Trillium
Trillium (6th gen)
Generally available
Training and inference
4.7x higher peak compute per chip than TPU v5e; 67% more energy-efficient than v5e
TPU v5p / v5e
Still available, lower cost
General training (v5p) and cost-efficient training/inference (v5e)
Used by Google as the baseline Trillium is measured against
TPU 8t / TPU 8i
Coming soon (announced, not yet GA)
8t: large-scale pre-training and embedding-heavy workloads. 8i: post-training and low-latency inference
8t: 9,600 chips per superpod, ~3x compute per pod vs. the prior generation. 8i: Google claims an 80% performance-per-dollar improvement over previous generations for low-latency inference on large mixture-of-experts (MoE) models
Google also says its Google Kubernetes Engine (GKE) can scale a single cluster up to 130,000 nodes, and that a cluster can span up to 1 million TPU chips — figures aimed squarely at the handful of organizations training frontier-scale models, not at a typical engineering team.
What It Costs
Cloud TPU pricing is quoted per chip-hour, though the Google Cloud console bills by VM-hour (a single TPU host can bundle multiple chips, so the displayed hourly rate is higher than the per-chip figure). On-demand, region-dependent prices from Google’s own pricing page:
Generation
Representative on-demand price (per chip-hour)
Ironwood (v7)
$12.00 (us-central1) to $13.20 (europe-west2)
Trillium (v6e)
$2.70 (us-east1 / us-east5) to $3.24 (asia-northeast1)
TPU v5p
$4.20 (us-east1 / us-east5)
TPU v5e
$1.20 (most US regions) to $1.56 (Europe/Asia)
Committed-use discounts, spot pricing, and reservations can all bring these numbers down substantially; the figures above are the standard on-demand rate. Note that these prices exist only on Google Cloud — unlike Nvidia GPUs, which you can rent from dozens of providers (AWS, Azure, Oracle, CoreWeave, Lambda, and many more) or buy outright, a TPU is a Google Cloud exclusive.
TPU vs. Nvidia GPU: The Honest Trade-Offs
Google doesn’t publish head-to-head TPU-vs-GPU benchmarks on its own product pages, and neither does Nvidia for the reverse comparison, so treat any specific “TPU is X% faster/cheaper than GPU Y” claim you see elsewhere with caution unless it cites a reproducible, apples-to-apples benchmark. What can be said reliably, based on how each platform is actually built and sold:
Dimension
TPU
Nvidia GPU
Architecture
Purpose-built systolic array (MXU) for matrix multiplication
General-purpose SIMT cores, usable for AI and non-AI parallel workloads alike
Software ecosystem
Native JAX/OpenXLA; PyTorch via TorchTPU; narrower third-party tooling
CUDA — the most mature, widely supported accelerator software ecosystem in the industry
Where you can run it
Google Cloud only
Virtually every major cloud, specialized GPU clouds, and on-prem
Best-documented strength
Large, co-designed pods for frontier-scale training and inference within Google’s own stack
Breadth — the default choice for nearly any framework, model, or deployment target
Vendor lock-in
High — tied to Google Cloud and (mostly) to JAX/XLA-friendly workflows
Low to moderate — GPUs and CUDA code are portable across many providers
Who Should Care
Teams already standardized on Google Cloud, or using JAX for research, are the clearest fit — Google’s own frontier models (including Gemini) are trained on TPUs, which is the strongest existing proof that the stack scales. Teams running PyTorch workloads that need broad framework and library compatibility, multi-cloud flexibility, or on-prem hardware are better served sticking with Nvidia GPUs, at least until TorchTPU support matures further. Cost-sensitive inference workloads on large MoE models are worth watching closely once TPU 8i reaches general availability, given Google’s stated performance-per-dollar target.
Bottom Line
TPUs are not a marketing afterthought — they’re a real, continuously-updated chip line that powers a meaningful share of the industry’s largest AI workloads, and the jump from v5e to Trillium to Ironwood represents genuine architectural progress. But “best chip” depends entirely on where you already live: inside Google Cloud with JAX-friendly code, TPUs are a strong and often cheaper-at-scale option; everywhere else, Nvidia’s ecosystem breadth is still the safer default.
FAQ
Can I buy a TPU and run it myself? No. TPUs are not sold as hardware; they are only available as a rented Google Cloud service.
Does TPU support mean I have to rewrite my PyTorch code? Not entirely — Google supports PyTorch on TPUs through TorchTPU, but JAX and OpenXLA remain the most natively supported and best-documented path.
Is Ironwood always the right choice over Trillium? Not necessarily. Ironwood costs roughly 4–5x more per chip-hour than Trillium, so unless your workload needs Ironwood’s extra headroom, Trillium (or even v5e for lighter jobs) may be the more cost-effective choice.
Are TPU 8t and TPU 8i available now? No — as of this writing, Google lists both as “coming soon” rather than generally available. Check Google’s Cloud TPU release notes for the current launch status before planning around them.
Oracle talks about “AI” in two very different senses, and the two get blurred together in a lot of coverage. One is a feature inside the database engine: Oracle Database 23ai’s AI Vector Search, which lets you store and query embeddings alongside ordinary rows without standing up a separate vector database. The other is an infrastructure deal: Oracle’s expanding partnership with Nvidia to put GPU capacity — from H200s to Blackwell-generation GB200 NVL72 racks — inside Oracle Cloud Infrastructure (OCI). This piece pulls those two threads apart and checks what Oracle’s own documentation actually supports.
At a Glance
Thing
What Oracle states
Core DB feature
AI Vector Search — native vector data type, approximate (HNSW) and exact/partitioned indexes, built into SQL
Cost of Vector Search
No additional charge on Autonomous Database, Exadata Database Service, and Oracle Database Free (cloud services); on-prem Standard/Enterprise Edition pricing isn’t stated on the feature page
23ai status
Long-term support release, renamed from “23c” to “23ai” and made generally available for enterprises in 2024
Nvidia GPUs on OCI
H200 Tensor Core (GA), GB200 NVL72 (live, liquid-cooled racks), Vera Rubin NVL72 (listed, no specs given)
OCI Supercluster scale
Up to 260 exaFLOPS with Hopper GPUs; 2.4 zettaFLOPS with Blackwell GPUs (Oracle’s own figures, not independently benchmarked)
DGX Cloud
GB200 NVL72 racks available through both NVIDIA DGX Cloud and OCI directly
Pricing transparency
No public per-GPU or per-cluster price list for OCI Nvidia instances
Short Verdict
AI Vector Search is a genuinely useful, well-documented feature if you’re already an Oracle Database shop — it saves you from bolting on a separate vector database for retrieval-augmented generation (RAG). The Nvidia partnership is real and substantial (Oracle is one of the launch partners for GB200 NVL72 at scale), but Oracle’s own marketing pages give performance superlatives (“largest, fastest AI supercomputer in the cloud”) without GPU counts, bandwidth figures, or prices to back them up. Treat the database feature as verified and ready to evaluate; treat the infrastructure claims as directionally true but not independently confirmed.
What It Is: Two Separate Stories Under One Banner
Oracle Database 23ai (first shown as “23c” at Oracle CloudWorld in September 2023, and renamed and made broadly available in 2024) is a long-term support release of the core database. Its headline addition is AI Vector Search: a native VECTOR data type, so embeddings sit in the same tables as your relational, JSON, text, spatial, and graph data instead of in a bolted-on vector store. That is the product story.
Separately, Oracle and Nvidia have an infrastructure partnership that predates and extends past 23ai: Oracle Cloud Infrastructure offers Nvidia GPUs — up through the latest Blackwell-generation GB200 NVL72 racks — as “OCI Superclusters,” and Nvidia’s own DGX Cloud service runs some of its training capacity on that same OCI hardware. The database feature doesn’t require this specific Nvidia hardware to work; the two are related mainly in that Oracle markets both under an “AI” umbrella and because AI Vector Search can call out to Nvidia NIM inference containers for embedding generation.
How AI Vector Search Actually Works
Capability
What it does, per Oracle’s documentation
Native VECTOR type
Stores vectors directly in ordinary tables, supporting multiple dimension counts/formats; sparse vectors store only non-zero values
Vector generation
Import an embedding model in ONNX format and generate vectors inside the database, call out to NVIDIA NIM containers, or import pre-computed vectors
Indexes
In-memory HNSW (approximate) graph index for speed; neighbor-partition indexes for very large datasets; hybrid indexes combine full-text and vector search
Distance metrics
Built-in Euclidean, cosine, and dot product, plus user-defined custom distance functions
Query model
Similarity search is plain SQL, combinable in the same query with relational, JSON, text, spatial, and graph predicates
RAG support
A LlamaIndex integration and a “Select AI” feature that turns natural-language prompts into SQL using OCI Generative AI or third-party LLMs
Iceberg support
Similarity search can run directly over Apache Iceberg tables without first loading embeddings into the database
Oracle also says Exadata System Software 24ai adds an “AI Smart Scan” that offloads part of vector search to storage servers, and that OCI GoldenGate 23ai can replicate vectors in real time across different vector stores. Both are Exadata/cloud-tier features rather than something every 23ai installation gets automatically.
The Nvidia Side: OCI Superclusters and DGX Cloud
On the infrastructure side, Oracle’s current Nvidia lineup (per oracle.com/cloud/nvidia) includes general availability of OCI Supercluster with H200 Tensor Core GPUs, live liquid-cooled GB200 NVL72 racks available through both OCI directly and NVIDIA DGX Cloud, and an announced (but unspecified) Vera Rubin NVL72 tier for future training and inference workloads. Oracle’s claimed Supercluster scale is up to 260 exaFLOPS on Hopper-generation GPUs and 2.4 zettaFLOPS on Blackwell — figures Oracle presents as capable of training trillion-parameter models, with “ultrafast RDMA cluster networking” tying nodes together, bare-metal instances with no virtualization overhead, and orchestration through OCI Kubernetes Engine (OKE).
Oracle doesn’t publish the GPU counts behind those FLOPS figures, the actual network bandwidth, or a price list for renting Supercluster capacity — all of that requires talking to Oracle sales. NVIDIA AI Enterprise software is available natively inside the OCI console (Oracle cites “more than 160 AI tools”), and NIM inference endpoints are distributed through the OCI Marketplace, which is the most concrete link back to the database side: a 23ai instance can call a NIM container running on this same Nvidia infrastructure to generate the embeddings it stores.
Pros
Vector search lives inside the database you already run — no separate vector-database vendor, no separate data-sync pipeline
AI Vector Search is explicitly free of additional charge on Autonomous Database, Exadata Database Service, and Oracle Database Free
Multiple index types (HNSW for speed, partitioned for scale) and built-in distance metrics cover most RAG use cases out of the box
The Nvidia partnership gives Oracle customers a path to current-generation GB200/Blackwell capacity without a separate relationship with Nvidia or a hyperscaler
Cons
Oracle’s “free” claim for AI Vector Search is documented for its own cloud services and the Free edition — it is not clearly stated whether on-premises Standard or Enterprise Edition customers get it at no extra licensing cost, and third-party licensing-advisory sites report enough ambiguity here that you should confirm directly with Oracle or a licensing specialist before assuming
Supercluster performance figures (exaFLOPS, zettaFLOPS) are Oracle’s own marketing numbers, not independently benchmarked, and the underlying GPU counts aren’t disclosed
No public pricing for OCI Nvidia GPU instances or Superclusters — budgeting requires a sales conversation
The database feature and the GPU infrastructure are only loosely coupled; you can use 23ai’s vector search with any embedding model and don’t need Oracle’s Nvidia capacity to benefit from it
Who It’s a Good Fit For
Teams already standardized on Oracle Database who want to add RAG or semantic search without introducing a new vector-database dependency are the clearest fit for AI Vector Search. For the Nvidia infrastructure side, organizations that are already OCI customers, or that specifically want GB200/Blackwell capacity without negotiating directly with Nvidia or AWS/Azure/GCP, have a legitimate reason to look at OCI Superclusters — though they should get firm pricing in writing before committing.
Who Should Look Elsewhere
If you’re not already running Oracle Database, the vector-search feature alone isn’t a strong reason to migrate — dedicated vector databases and extensions for Postgres (pgvector) or other engines solve the same problem with less lock-in. For raw GPU capacity, teams that need transparent, published per-hour pricing should compare OCI’s actual quoted rates against AWS, Azure, and GCP before assuming Oracle is cheaper or faster; none of the performance superlatives on Oracle’s page are independently verifiable from the page itself.
Bottom Line
“AI Database” at Oracle really means two things bundled under one marketing phrase: a solid, well-documented set of in-database vector search and RAG capabilities in Database 23ai, and a large but opaque Nvidia GPU infrastructure deal that supplies the compute for training and inference elsewhere in Oracle’s cloud. The database feature is concrete enough to evaluate today. The infrastructure claims are the kind of numbers you verify with a sales rep, not the kind you take from a marketing page.
FAQ
Is Oracle Database 23ai the same as 23c? Yes. Oracle renamed the long-term support release from “23c” to “23ai” and made it generally available for enterprises in 2024, citing the AI-focused features as the reason for the rename.
Do I need Nvidia GPUs to use AI Vector Search? No. Vector generation can use an imported ONNX embedding model, pre-computed vectors, or an NVIDIA NIM container — the last option is convenient if you’re already on OCI, but it isn’t a requirement.
Is AI Vector Search really free? Oracle states it’s available at no additional charge on Autonomous Database, Exadata Database Service, and Oracle Database Free. Whether that extends to on-premises Standard or Enterprise Edition licenses isn’t stated on Oracle’s feature page, so confirm with Oracle directly if that’s your deployment model.
What’s the difference between OCI Supercluster and NVIDIA DGX Cloud? They can be the same underlying hardware. Oracle says GB200 NVL72 racks are available through both OCI directly and through NVIDIA DGX Cloud running on OCI infrastructure — the choice is mainly about which company’s service layer and support you’re buying.
Where can I get actual OCI Nvidia GPU pricing? Oracle does not publish per-GPU or per-cluster rates for its Nvidia Supercluster offerings on its marketing pages; pricing requires contacting Oracle sales.
Running a handful of containers is easy. Running hundreds of them across dozens of servers, restarting the ones that crash, routing traffic to healthy instances, and rolling out updates without downtime is not — that’s the job of a container orchestrator. Three tools dominate this space in 2026: Kubernetes, the open-source standard; Amazon ECS, AWS’s own simpler alternative; and HashiCorp Nomad, the lightweight scheduler that handles containers and non-container workloads alike. They are not interchangeable, and the right pick depends heavily on how much operational complexity a team is willing to take on.
At a Glance
Tool
License / Cost Model
Control Plane Cost
Best For
Learning Curve
Kubernetes
Open source (self-hosted) or managed via a cloud provider
Free self-hosted; $0.10/cluster/hour on Amazon EKS (standard support)
Large, multi-cloud or portable workloads with complex scaling needs
Steep
Amazon ECS
AWS proprietary service
Free — no orchestration fee at all
Teams already committed to AWS who want less operational overhead
Low to moderate
HashiCorp Nomad
Business Source License 1.1 (not OSI-approved open source since 2023)
Free (Community edition); Enterprise is quote-based, not publicly priced
Mixed fleets running containers alongside VMs, batch jobs, or raw binaries
Low to moderate
Short Verdict
Kubernetes wins on ecosystem and portability but costs the most in engineering time to run well. Amazon ECS is the pragmatic choice if a team is AWS-only and wants orchestration without the Kubernetes tax — it genuinely has no control-plane fee. Nomad is the dark horse: a single lightweight binary that schedules containers, Java apps, and raw executables side by side, but it’s worth knowing upfront that it is no longer open source in the traditional sense, and its Enterprise pricing is not public.
What Each Tool Actually Is
Kubernetes is a Cloud Native Computing Foundation (CNCF) graduated project that automates deployment, scaling, and management of containerized applications. It’s cloud-agnostic by design — the same YAML manifests can, in principle, run on Amazon EKS, Google GKE, Azure AKS, or a self-managed cluster on bare metal. That portability comes with genuine operational weight: etcd, control-plane upgrades, networking plugins (CNI), and a sprawling ecosystem of add-ons that most teams end up needing (ingress controllers, service meshes, autoscalers).
Amazon ECS (Elastic Container Service) is AWS’s own orchestrator, tightly integrated with IAM, VPC networking, Application Load Balancer, and CloudWatch. It supports two launch types: the EC2 launch type, where you manage the underlying instances yourself, and Fargate, a serverless mode where AWS manages the servers and you simply specify how much vCPU and memory each task needs. ECS deliberately trades portability for simplicity — it only runs on AWS, but there’s no cluster software to patch or upgrade.
HashiCorp Nomad is a single-binary scheduler that treats containers as just one of several supported “task drivers” — it can also run raw executables, Java applications, QEMU virtual machines, and more, all from one tool. It has no etcd-equivalent dependency and is often praised for being easier to operate at small-to-mid scale than Kubernetes. Since August 2023, Nomad (along with most of HashiCorp’s products) has shipped under the Business Source License 1.1 rather than the Mozilla Public License it previously used — the source is visible on GitHub, but BUSL restricts competing commercial use, so it is not an OSI-approved open-source license. HashiCorp itself was acquired by IBM, which closed in 2025, and Nomad is now sold and supported as part of IBM’s HashiCorp product line.
Pricing Breakdown
Tool
What You Actually Pay
Kubernetes (self-hosted)
$0 in licensing; you pay only for the servers it runs on. Operational/engineering-time cost is the real expense.
Amazon EKS (managed Kubernetes)
$0.10 per cluster per hour under standard support (first ~14 months after a Kubernetes version’s release), rising to $0.60 per cluster per hour once that version enters extended support — plus the cost of the EC2/Fargate capacity the pods run on, per AWS’s EKS pricing page.
Amazon ECS
No orchestration fee on either launch type. EC2 launch type: standard EC2/EBS rates only. Fargate launch type: billed per second (one-minute minimum) at roughly $0.000011244 per vCPU-second and $0.000001235 per GB-second in US East (N. Virginia), per AWS’s ECS pricing page — AWS does not publish a simple flat hourly rate, only these per-second figures.
Nomad Community
Free, self-hosted, under BUSL-1.1.
Nomad Enterprise / HCP Nomad
Not publicly priced. HashiCorp’s and IBM’s own pricing pages list rates for Terraform, Vault, Packer, and Boundary but do not list a Nomad Enterprise figure — it is sold through a sales quote.
Pros and Cons
Kubernetes
Pros: Enormous ecosystem (Helm, operators, service meshes); runs identically across any cloud or on-premises; the de facto industry standard, so hiring and documentation are easiest here.
Cons: Steep learning curve; managed control planes still cost money per cluster; teams frequently need a dedicated platform engineer just to keep it healthy.
Amazon ECS
Pros: Genuinely no orchestration fee; deep native integration with IAM, ALB, and CloudWatch; Fargate removes server management entirely.
Cons: AWS-only — no portability to other clouds; smaller ecosystem of third-party tooling than Kubernetes; less flexible for teams with complex, custom scheduling needs.
HashiCorp Nomad
Pros: Single lightweight binary, simple operational model; can schedule non-container workloads (VMs, batch jobs, raw binaries) alongside containers; lower overhead than Kubernetes at small-to-mid scale.
Cons: No longer OSI-approved open source (BUSL-1.1 since 2023); much smaller ecosystem and community than Kubernetes; Enterprise pricing is opaque and quote-only.
Who It’s a Good Fit For
Choose Kubernetes if the team needs multi-cloud portability, already has (or is building) platform-engineering expertise, or needs the breadth of the CNCF ecosystem. Choose Amazon ECS if the organization is AWS-only, wants orchestration with the least possible operational burden, and doesn’t need to run outside AWS. Choose Nomad if the workload mix includes more than just containers — batch jobs, VMs, or legacy binaries — and the team wants a simpler single-binary tool, while accepting that its licensing is more restrictive than classic open source and that enterprise support pricing isn’t public.
Who Should Look Elsewhere
Small teams running a handful of services should think twice before adopting full Kubernetes — the operational overhead often outweighs the benefit at that scale, and a simpler option (ECS Fargate, or even a PaaS) usually gets the job done faster. Teams that need a strictly open-source (OSI-approved) license with no commercial-use restrictions should be cautious with Nomad given its BUSL-1.1 terms, and should confirm current licensing directly with HashiCorp/IBM before committing.
Bottom Line
There’s no universally “best” orchestrator — only the one that matches a team’s cloud strategy and appetite for operational complexity. Kubernetes remains the safest long-term bet for portability and hiring; Amazon ECS is the lowest-friction choice for AWS-committed teams; and Nomad is worth a serious look for mixed workloads, as long as its current licensing terms are acceptable for the use case.
FAQ
Is Kubernetes free? The Kubernetes software itself is free and open source (CNCF project). What costs money is either the servers you run it on yourself, or a managed control plane like Amazon EKS, which charges $0.10–$0.60 per cluster per hour depending on Kubernetes version support status.
Does Amazon ECS really have no extra fee? Correct — AWS’s own ECS pricing page states there is no additional charge for ECS orchestration on either the EC2 or Fargate launch type. You only pay standard rates for the compute, storage, and networking resources the tasks use.
Is HashiCorp Nomad still open source? Its source code is publicly visible on GitHub, but since August 2023 it has been licensed under the Business Source License 1.1, not the Mozilla Public License it used before. BUSL is not an OSI-approved open-source license because it restricts certain competing commercial uses, even though the Community edition remains free to use for most purposes.
Can Nomad really run things other than containers? Yes — Nomad’s “task driver” model supports Docker containers, raw executables (exec driver), Java applications, and QEMU virtual machines, among others, all managed by the same scheduler.
IBM’s enterprise AI infrastructure gets covered for its silicon — the Power11 chip and the Telum II mainframe accelerator. But IBM is also running a separate, less hardware-centric play: an AI platform called watsonx.ai, paired with a family of openly licensed foundation models called Granite. Together they’re IBM’s answer to the question developers actually ask — not “whose chip is fastest,” but “can I build on this without getting locked into a single vendor’s weights.” Here’s what watsonx.ai and Granite actually offer as of early 2026, verified against IBM’s own documentation and model cards.
At a Glance
Platform
watsonx.ai (IBM’s AI development platform) + Granite (IBM’s open foundation model family)
Granite license
Apache 2.0 (per IBM’s Granite 4.2 release)
Latest Granite generation
Granite 4.2 (language models at 3B, 8B, and 30B parameters)
Model types in the family
Language, vision, speech, embedding, guardrail (“Guardian”), and time-series models
Where to run Granite
watsonx.ai, Hugging Face, Ollama, LM Studio, OpenRouter, Replicate, Weights & Biases, Unsloth, AnythingLLM, Red Hat Enterprise Linux AI
Reported SWE-Bench Verified (pass@1)
47.67 (8B), 57.00 (30B) — IBM’s own published figures
Best for
Enterprises and developers who want an open-weight model they can self-host, fine-tune, or audit, plus a managed platform to deploy it
Short Verdict
Granite is a genuinely open (Apache 2.0) model family that’s small enough to self-host cheaply and is distributed across nearly every popular runtime, which is unusual for a model backed by a large enterprise vendor. watsonx.ai is the more conventional piece: a managed platform for deploying Granite, Meta’s Llama, Mistral’s models, and others, with API-level controls aimed at regulated enterprises. Neither is the most capable option on raw benchmarks against today’s frontier models, but the combination — open weights plus an enterprise deployment layer — is IBM’s real differentiator.
What Is watsonx.ai?
watsonx.ai is IBM’s hosted platform for building, tuning, and deploying AI models, available on IBM Cloud and on-premises through watsonx as a Service. It isn’t a single model — it’s a catalog-and-tooling layer. Developers pick a foundation model from a growing list (IBM’s own Granite family alongside third-party models such as Meta’s Llama and Mistral’s releases), then use watsonx’s APIs, notebooks, and AutoAI tooling to prompt, tune, or build retrieval-augmented pipelines on top of it.
IBM’s own changelog shows a platform under active, fairly rapid iteration. Recent additions include a chat API with explicit controls over model reasoning depth and response detail (added November 2025), a preview “model gateway” that routes requests across multiple LLM providers through one resource hub (October 2025, Toronto region only at launch), a text-classification API for pre-sorting documents before extraction, and a dedicated watsonx Developer Hub with quick-start guides (November 2025). On the other side of the ledger, IBM has also been retiring older capabilities — prompt tuning was removed from all data centers in October 2025, and Federated Learning was removed in September 2025 — which is worth knowing if you’re building on a feature you saw in older IBM marketing material.
What Is the Granite Model Family?
Granite is IBM’s line of foundation models, released under the Apache 2.0 license — meaning the weights are downloadable and usable commercially without the restrictions some competing “open” models carry. The family spans more than text: IBM groups language, vision, speech, embedding, a safety/content-moderation line called Guardian, and time-series forecasting models under the Granite name, though not all of those sub-families have reached the same generation number.
The current flagship generation, Granite 4.2, ships language models at three sizes — 3B, 8B, and 30B parameters — small enough that the 8B and even the 30B variant can realistically run on a single modern GPU or a well-resourced CPU server, rather than requiring a data-center cluster. IBM publishes its own benchmark results for these three sizes:
Benchmark
Granite 4.2 3B
Granite 4.2 8B
Granite 4.2 30B
MMLU-Pro (5-shot)
67.84
74.04
77.60
GPQA (pass@1)
54.80
64.14
66.41
AIME25 (pass@1)
78.33
86.67
89.17
SWE-Bench Verified (pass@1)
N/A
47.67
57.00
Arena-Hard-V2 (win rate)
34.96
65.19
67.93
These are IBM’s self-reported figures from its own Granite documentation, not an independent third-party leaderboard, so treat them as a starting point rather than the final word — as with any vendor-published benchmark, it’s worth checking an independent leaderboard for the specific use case you care about before committing.
Where You Can Actually Use Granite
This is the part that distinguishes Granite from most enterprise-backed model families: IBM has pushed it onto nearly every popular runtime rather than keeping it inside watsonx. According to IBM’s own Granite page, the models are available through:
Hugging Face (the models are hosted directly under the ibm-granite organization)
Ollama and LM Studio, for running locally on a laptop or workstation
watsonx.ai, for IBM’s managed enterprise deployment path
OpenRouter and Replicate, for pay-per-call hosted inference
Weights & Biases and Unsloth, aimed at fine-tuning workflows
AnythingLLM, for retrieval-augmented chat apps
Red Hat Enterprise Linux AI, IBM’s own enterprise Linux distribution with built-in support for running Granite
On Hugging Face, the individual model pages back this up with real usage signals rather than marketing claims: granite-4.2-8b shows roughly 69,000 downloads and granite-4.2-30b around 36,000, with smaller but active download counts on the speech and switch-routing variants — evidence that developers outside IBM’s own customer base are actually pulling these weights.
Pros
Granite’s Apache 2.0 license is genuinely permissive — no field-of-use restrictions to parse before you ship a commercial product
Small model sizes (3B–30B) make self-hosting realistic without a large GPU cluster
Distributed across almost every popular open-model runtime, not locked into IBM’s own platform
watsonx.ai gives enterprises a managed, auditable deployment path if they don’t want to run inference infrastructure themselves
Dedicated Guardian models for content moderation/safety are a distinct, less common offering among open model families
Cons
Benchmark figures are IBM’s own; there’s no independent third-party confirmation cited on the official page
Granite’s largest published language model (30B) is well below the parameter count of today’s frontier proprietary models, so it’s not positioned to compete on raw general-purpose capability
watsonx.ai’s feature set is still being actively reshuffled — capabilities like prompt tuning and Federated Learning have already been removed within the last several months, so documentation and tutorials age quickly
Some Granite sub-families (vision, embedding) lag the language models in generation number and weren’t fully visible in IBM’s own published model list at the time of writing
Who It’s a Good Fit For
Granite suits teams that want to self-host or fine-tune an open-weight model without wading through restrictive licensing, and that don’t need frontier-level general capability — document processing, internal chat assistants, classification, and retrieval-augmented generation are reasonable fits at the 8B–30B range. watsonx.ai suits regulated enterprises (finance, healthcare, government) that want a single managed platform to deploy Granite alongside other models like Llama or Mistral, with IBM’s audit and governance tooling layered on top.
Who Should Look Elsewhere
If you need the strongest possible general-purpose reasoning or coding performance regardless of openness, today’s frontier proprietary models will generally outperform Granite’s current 30B ceiling. And if you have no interest in IBM’s platform tooling and just want an open model, you may find a more actively-benchmarked open-weight alternative with a larger community already built around it.
Bottom Line
IBM’s AI infrastructure story isn’t only about silicon. Granite is a legitimately open, portable model family that doesn’t try to compete at the frontier, and watsonx.ai is a maturing — if fast-changing — managed platform for enterprises that want governance and deployment tooling around it. If your priority is license freedom and runtime flexibility over raw benchmark supremacy, it’s worth evaluating; if you need the absolute top of the leaderboard, look elsewhere first.
FAQ
Is Granite free to use commercially? Yes — IBM releases Granite models under the Apache 2.0 license, which permits commercial use without the field-of-use restrictions some other “open” model licenses carry.
Do I need watsonx.ai to run Granite? No. Granite is also distributed through Hugging Face, Ollama, LM Studio, OpenRouter, Replicate, and other runtimes, so you can self-host it entirely outside IBM’s platform.
How big is the largest Granite 4.2 language model? 30 billion parameters, according to IBM’s own Granite 4.2 documentation, alongside 8B and 3B variants.
Is watsonx.ai only for Granite models? No — IBM’s own changelog shows the platform also hosting Meta Llama and Mistral models for deployment, alongside Granite.
Every time a web server streams a file, a message broker ships a log segment, or a CDN node serves a cached asset, the operating system has a choice: copy that data through the application’s own memory, or hand it off inside the kernel and skip the detour. The second option is “zero-copy” I/O, and it’s one of the quieter reasons systems like Kafka, Nginx, and Netty can push huge amounts of data without burning CPU cycles on work that never needed to happen.
At a Glance
What it solves
Unnecessary copying of data between kernel space and user space during I/O
Core Linux syscalls
sendfile(2), splice(2), mmap(2); newer workloads also use io_uring
Typical savings
Eliminates the application-level copy steps (OS cache → app buffer → socket buffer) on the read/transfer path
Platform
Linux-specific syscalls (sendfile/splice); conceptually available on other Unix-likes with different APIs
Well-known adopters
Apache Kafka, Netty, Nginx
Main trade-off
Less flexibility — the data can’t be inspected or transformed by the application mid-transfer
The Problem: What a “Normal” Copy Actually Costs
A naive file-to-network transfer — read a file, then write it to a socket — looks cheap in code but isn’t cheap in hardware. As Kafka’s own design documentation and independent breakdowns of its internals describe, a conventional path pulls data from disk into the OS page cache, then copies it again into the application’s buffer, then copies it a third time into the socket buffer the kernel uses for the network stack, before the network card finally sends it. Each of those hops crosses the boundary between kernel space and user space, and each one costs CPU time and memory bandwidth to move bytes that the application never actually needed to touch — it was just a pass-through.
This matters most for high-throughput, pass-through workloads: a message broker relaying log segments to consumers, a static file server, or a proxy forwarding a response body. In all of these, the application doesn’t need to read or modify the bytes — it just needs to move them from point A to point B as fast as possible.
How Zero-Copy Works
Zero-copy techniques let the kernel move data directly — disk cache to network card, or one file descriptor to another — without routing it through a user-space buffer at all. The core Linux mechanism is the sendfile(2) system call:
According to its Linux manual page, sendfile() “copies data between one file descriptor and another,” and because the data never travels to user space and back, it is more efficient than a matching pair of read(2) and write(2) calls. A related call, splice(2), moves data between two file descriptors where at least one is a pipe — its man page is explicit that the point is to move data “without copying between kernel address space and user address space,” by passing around reference-counted pointers to kernel memory pages rather than the page contents themselves. mmap(2) offers a third route: mapping a file directly into a process’s address space so reads happen via memory access instead of an explicit copying syscall. More recently, Linux’s io_uring interface has given low-level network and storage code another way to cut syscall and copy overhead, though it’s a broader asynchronous I/O framework rather than a drop-in replacement for sendfile().
Traditional read + write
Zero-copy (sendfile)
Disk → OS page cache
Yes
Yes
OS cache → application buffer
Yes (extra copy)
Skipped
Application buffer → socket buffer
Yes (extra copy)
Skipped
OS cache / socket buffer → NIC
Yes
Yes, directly
Application touches the bytes
Yes
No
That table reflects the walkthrough popularized by engineering explainers of Kafka’s design: in the traditional path, data makes extra stops at the application layer and the socket buffer before reaching the network card; with sendfile(), the OS page cache hands data to the network card directly, and the broker process never has to allocate a buffer for it or touch it at all.
Real-World Uses
Apache Kafka — Kafka brokers lean on zero-copy transfer to move log segments from disk to consumers without the broker process copying the bytes through its own heap, which is a documented part of why a single broker can sustain very high read throughput.
Netty — Netty’s FileRegion abstraction represents a region of a file sent through a channel, and Netty’s own API documentation describes it as supporting zero-copy file transfer; it’s the mechanism behind efficient file-serving code built on Netty (which underlies parts of gRPC and many Java web servers).
Nginx — Nginx exposes a sendfile on; directive specifically so static file responses can be served via the kernel’s zero-copy path instead of being read into a worker’s buffer and written back out.
Trade-Offs and Limitations
No mid-flight processing. Because the application never sees the bytes, zero-copy only works for pure pass-through transfers — not for workloads that need to compress, encrypt, parse, or transform the data first.
Platform-specific.sendfile() and splice() are Linux syscalls with their own constraints (for example, sendfile()‘s input descriptor has historically needed to support mmap-like access, so it can’t be a socket); the man pages themselves warn against relying on sendfile’s exact semantics in portable code.
Partial transfers still happen. A single sendfile() call can transfer fewer bytes than requested, so correct code has to handle looping until the transfer completes, same as with write().
Not always a true zero-copy in practice. The splice(2) man page itself notes that actual page copies can still occur when the kernel can’t just move pages around — for instance when buffers don’t align to full pages.
Bottom Line
Zero-copy I/O isn’t a trick or a benchmark gimmick — it’s a direct consequence of recognizing that a lot of server-side work is pure data relay, and that every unnecessary copy between kernel and user space costs real CPU time and memory bandwidth at scale. For teams building anything that moves large volumes of bytes — a broker, a proxy, a file server — knowing that sendfile(), splice(), and friends exist (and why Kafka, Nginx, and Netty already use them) is a useful piece of systems literacy, even if you never call the syscall directly yourself.
FAQ
Is zero-copy I/O only relevant to C/systems programming? No. Most developers encounter it indirectly — through a sendfile on; setting in Nginx, Kafka’s broker-side design, or a Java NIO/Netty file-transfer API — without ever calling the underlying syscall themselves.
Does zero-copy mean literally no copying happens anywhere? No. Data still moves from disk into the OS page cache, and from there to the network card. What’s eliminated are the extra copies into and out of the application’s own user-space buffer.
Can I use sendfile() if I need to encrypt or compress the data first (e.g. TLS)? Not directly — since the application never sees the bytes, it can’t transform them. That’s why plain zero-copy static file serving and TLS-terminated responses are handled by different code paths; some systems use kernel TLS (kTLS) offload to regain some of the benefit even with encryption, but that’s a separate mechanism from the plain sendfile/splice path described here.
Every time a new AI model launches, its announcement includes a chart of benchmark scores — and coding benchmarks are usually front and center. But “74.5% on SWE-bench Verified” means very little unless you know what the benchmark is actually testing, how the number is computed, and what it leaves out. This guide breaks down the three benchmarks that dominate AI coding discussions — HumanEval, SWE-bench (and its Verified subset), and LiveCodeBench — and what their scores can and can’t tell you about a model you’re considering using for daily coding work.
At a Glance
Benchmark
What It Measures
Maintained By
Size
HumanEval
Whether generated code passes hand-written unit tests for a self-contained function
OpenAI (now archived/unmaintained)
164 hand-written problems
SWE-bench / SWE-bench Verified
Whether a model can resolve a real, previously-filed GitHub issue in an existing codebase
Independent academic team; Verified subset curated with OpenAI
2,294 instances (full); 500 (Verified)
LiveCodeBench
Code generation, self-repair, execution prediction, and test-output prediction on fresh contest problems
UC Berkeley, MIT, and Cornell researchers
Growing pool of dated contest problems from LeetCode, AtCoder, Codeforces
Short Verdict
No single benchmark tells the whole story. HumanEval tests isolated, textbook-style functions and is now considered too easy and too familiar to current models to be a meaningful differentiator. SWE-bench Verified is the closest thing the industry has to a real-world coding test, because it uses actual GitHub issues and actual codebases — but it is Python-only and still doesn’t capture everything about a messy, undocumented production repo. LiveCodeBench’s main contribution isn’t a different skill test so much as a defense against contamination: by dating every problem, it can tell you whether a model is actually reasoning or just recalling training data. Read all three together, and read them skeptically.
Why Coding Benchmarks Exist — and Why There Are So Many
A benchmark is only useful if it’s hard to game. The earliest code-generation tests simply asked a model to complete a function and checked whether the output compiled or looked plausible — which told you almost nothing about correctness. As models got better, each new benchmark had to raise the bar: first by actually running the generated code against tests, then by using realistic, large-codebase tasks instead of toy problems, and most recently by controlling for the possibility that a model has simply memorized the answer from its training data. HumanEval, SWE-bench, and LiveCodeBench represent three successive generations of that arms race.
HumanEval: The Original Pass@1 Test
HumanEval was introduced by OpenAI in the 2021 paper “Evaluating Large Language Models Trained on Code” (the paper behind the original Codex model) and shipped as an open evaluation harness, openai/human-eval, on GitHub. It consists of 164 hand-written programming problems, each made up of a function signature, a docstring describing the task, a reference solution, and a set of unit tests. A model is given the signature and docstring and has to generate the function body; the harness then runs the generated code against the hidden unit tests.
Scoring uses the pass@k metric: a model generates k independent samples for a problem, and pass@k estimates the probability that at least one of those k samples passes all tests. Pass@1 — a single attempt — is the figure most commonly quoted today. OpenAI’s own repository now flags human-eval as “deprecated and unmaintained,” kept only for historical reference; frontier models have been scoring near-ceiling on it for a while, which is exactly why the field moved on to harder tests.
SWE-bench Verified: Real GitHub Issues, Not Toy Problems
SWE-bench takes a fundamentally different approach: instead of writing new problems, it pulls 2,294 real, previously-resolved GitHub issues from 12 popular Python repositories. For each instance, the model is handed the original issue description and the state of the codebase at that commit, and has to produce a patch. That patch is graded by running the project’s actual test suite, including the tests that were added by the human-authored fix (so the model can’t pass by accident).
Because some of the original 2,294 instances turned out to be ambiguous, under-specified, or effectively unsolvable even by a correct human-equivalent patch, the SWE-bench team partnered with OpenAI to release SWE-bench Verified in August 2024: a 500-instance, human-filtered subset that has become the de facto standard that vendors quote at launch. It’s run inside a sandboxed agent scaffold (the official leaderboard’s default view uses a “Bash Only” mini-agent environment) so that different vendors’ agent setups are compared on a more even footing.
A useful, verified data point on what these scores mean in practice: in its own release notes for Claude Opus 4.5 (November 2025), Anthropic reported that the model matched its predecessor Sonnet 4.5’s best SWE-bench Verified score at a medium reasoning-effort setting while using 76% fewer output tokens, and exceeded Sonnet 4.5’s best score by about 4.3 percentage points at its highest reasoning-effort setting while using 48% fewer tokens — illustrating that on this benchmark, efficiency (tokens spent per correct patch) has become as much of a competitive axis as raw accuracy. Because every major lab resubmits new models to the public SWE-bench Verified leaderboard on a rolling basis, any specific score printed here would be stale within weeks — check the live leaderboard at swebench.com for current standings rather than relying on a single quoted figure.
LiveCodeBench: Fighting Contamination With Dates
The biggest problem with any fixed benchmark is contamination: once a benchmark’s problems and solutions circulate on the internet, they can end up in a later model’s training data, inflating its score without reflecting real reasoning ability. LiveCodeBench, built by researchers at UC Berkeley, MIT, and Cornell, addresses this directly by continuously collecting new competitive-programming problems from LeetCode, AtCoder, and Codeforces and tagging each one with its original release date. Because every problem is dated, a model can be evaluated only on the subset of problems released after its training cutoff — the leaderboard’s “scrolling over time” view lets you pick that window yourself.
LiveCodeBench also tests more than plain code generation: it scores models on self-repair (fixing a broken program from error feedback), code execution (predicting a program’s output without running it), and test-output prediction, in addition to generation — all measured with pass@1. That breadth makes it useful for spotting models that are good at writing code but weak at actually reasoning about what code does.
Comparing the Three
Benchmark
Strength
Main Limitation
HumanEval
Simple, fast, cheap to run; good historical baseline
Saturated — top models now near the ceiling; tests isolated functions, not real codebases
SWE-bench Verified
Uses real, previously-merged fixes to real GitHub issues in real codebases
Actively guards against training-data contamination via dated problems
Competitive-programming problems (LeetCode/Codeforces-style) still differ from day-to-day engineering work
What a Benchmark Score Doesn’t Tell You
It doesn’t measure performance on your actual codebase, your language/framework mix, or your team’s conventions.
It doesn’t capture agentic behaviors like asking clarifying questions, respecting existing architecture, or avoiding unnecessary refactors.
Scaffold and tooling differences (which agent harness, how many retries, how much “thinking” budget) can shift a score by several points independent of the underlying model.
A high score can still coexist with contamination risk if the benchmark’s problems predate the model’s training cutoff and aren’t excluded.
Who Should Care About These Benchmarks
Engineering leaders evaluating which AI coding assistant to standardize on should treat SWE-bench Verified as a reasonable first filter for raw problem-solving capability, but should still run a pilot on their own repositories before committing. Individual developers choosing between tools day-to-day will get more signal from hands-on trials and from LiveCodeBench’s self-repair and execution-prediction scores (which correlate better with “does this model actually understand what the code does”) than from a single headline HumanEval number, which is now close to meaningless as a differentiator.
Bottom Line
HumanEval told the industry that language models could write small, correct functions; it’s now largely retired as a serious differentiator. SWE-bench Verified is the current standard for measuring whether a model can act as a software engineer on a real, if still relatively clean, codebase. LiveCodeBench adds a contamination check that the other two lack. None of them replace testing a model on your own code — but together, they’re the most credible public signal available for comparing AI coding ability across vendors.
FAQ
Is a higher SWE-bench Verified score always better? Generally yes for raw problem-solving ability, but check what agent scaffold and reasoning-effort setting produced the score — vendors often report their best configuration, which may cost more tokens or run slower than a default setting.
Why don’t vendors still report HumanEval scores prominently? Because frontier models now score so close to the ceiling on HumanEval that it no longer meaningfully distinguishes between them; the benchmark’s own maintainers have marked the original repository deprecated.
Can a benchmark score be inflated by contamination? Yes — if a benchmark’s problems and solutions appear in a model’s training data, its score can rise without a real improvement in reasoning. LiveCodeBench was built specifically to counter this by timestamping every problem.
Where can I see current, up-to-date scores? The official SWE-bench Verified leaderboard is published at swebench.com and updates as labs submit new runs; LiveCodeBench’s leaderboard is hosted on Hugging Face. Treat any benchmark number quoted in an article (including this one) as a snapshot, not a live figure.
Every API your company exposes needs something standing in front of it: an API gateway that handles authentication, rate limiting, routing, and analytics so individual services don’t have to reinvent that logic. The three names that come up most often in 2026 are Kong, Amazon’s native AWS API Gateway, and Google’s Apigee — and they represent three fundamentally different approaches to the problem, and three very different pricing philosophies. This review compares them on real, vendor-published numbers.
At a Glance
Tool
Model
Starting Price
Best For
Kong
Self-hosted OSS or managed Konnect SaaS
Free (Gateway OSS) / Konnect Plus from $25/mo + usage
Teams wanting open-source flexibility or a hybrid/multi-cloud control plane
AWS API Gateway
Pure pay-per-use, no subscription
From $1.00 per million HTTP API calls
Teams already built on AWS wanting zero infrastructure to manage
Google Apigee
Pay-as-you-go (public) or annual subscription (quote-only)
From $365/month/region (Base, pay-as-you-go)
Large enterprises needing full API lifecycle management, monetization, and analytics
Short Verdict
If you’re already deep in AWS and just need routing, auth, and throttling in front of Lambda or containerized services, AWS API Gateway is the path of least resistance and the cheapest per-call option. If you want an open-source gateway you can run anywhere — on-prem, multi-cloud, Kubernetes — Kong Gateway’s free Apache-2.0-licensed core is hard to beat, with Konnect available if you want a managed control plane on top. Apigee is the heaviest and most expensive of the three, but it’s also the only one built for full API productization: developer portals, monetization, and enterprise-grade analytics baked in.
What Each One Is
Kong started as an open-source API gateway built on NGINX and Lua, and Kong Gateway remains available under the Apache License 2.0 — free to download, self-host, and modify. Kong Inc. monetizes through Konnect, a SaaS control plane that adds a hosted dashboard, analytics, developer portals, AI gateway features for proxying LLM traffic, and optional fully-managed “Dedicated Cloud Gateways” so you don’t have to run data planes yourself.
AWS API Gateway is a fully managed service with no software to install or servers to patch. You define REST APIs, HTTP APIs (a newer, cheaper, lower-latency option), or WebSocket APIs, and AWS handles scaling, throttling, and integration with Lambda, EC2, or any HTTP backend. There’s no subscription — you pay strictly for what you use.
Apigee (part of Google Cloud) is an enterprise API management platform rather than a lightweight gateway. It bundles traffic management with API monetization, a developer portal for external API consumers, and deep analytics, aimed at organizations that treat their APIs as products.
Pricing Breakdown
Tool
Tier
Price
Notes
Kong
Gateway OSS
Free
Apache 2.0 license, fully self-hosted
Konnect Plus
From $25/mo + usage
1M requests/mo included; +$200 per extra 1M; Dedicated Cloud Gateway +$500/mo per region
Konnect Enterprise
Custom (annual contract)
Volume discounts, SSO, audit logging, CSM, 24×7 support tiers
AWS API Gateway
HTTP API
$1.00 per 1M calls (first 300M), $0.90/1M beyond
Cheapest option, newer feature set
REST API
$3.50 per 1M calls (first 333M), down to $2.38/1M at scale
Older, more feature-rich API type
WebSocket API
$1.00 per 1M messages + $0.25 per 1M connection-minutes
Plus $0.09/GB data transfer out (public APIs only)
Apigee
Pay-as-you-go
From $365/mo/region (Base) + $20 per 1M standard proxy calls
Comprehensive tier is $3,431/mo/region with autoscaling and 99.9%+ SLA
Predictable pricing, monetization and hybrid entitlements included
AWS gives new accounts a 12-month free tier covering 1 million REST calls, 1 million HTTP calls, and 1 million WebSocket messages per month. Kong offers a 30-day Konnect trial with no card required. Apigee offers a 60-day free sandbox evaluation rather than an ongoing free tier.
Pros
Kong: Genuinely free self-hosted core; plugin ecosystem; works identically on-prem, in Kubernetes, or across multiple clouds; AI-gateway features for routing LLM traffic.
AWS API Gateway: Zero infrastructure to manage; tightly integrated with Lambda, IAM, and the rest of AWS; cheapest raw per-call pricing of the three, especially on HTTP APIs.
Apigee: Full API lifecycle management including monetization and developer portals; strong analytics and security add-ons; scales to tens of billions of calls under enterprise subscriptions.
Cons
Kong: The free tier is the gateway only — Konnect’s managed convenience costs extra, and advanced features (SSO, audit logging, event gateways) are Enterprise-only with custom pricing.
AWS API Gateway: Costs can balloon with caching, response streaming, and PrivateLink add-ons; it’s AWS-only, so it doesn’t help in multi-cloud setups.
Apigee: By far the most expensive entry point ($365+/month per region before a single API call); its richer subscription tiers are quote-only, so true enterprise cost isn’t public.
Who It’s a Good Fit For
Choose Kong if you want control over your own infrastructure, need multi-cloud or on-prem flexibility, or are already comfortable operating open-source infra. Choose AWS API Gateway if your backend already lives on AWS and you want the simplest possible pay-per-use gateway with no operational overhead. Choose Apigee if you’re exposing APIs externally as a product — to partners, customers, or a developer ecosystem — and need monetization and lifecycle tooling, not just traffic routing.
Who Should Look Elsewhere
Small teams with simple internal APIs and tight budgets will find Apigee’s $365+/month-per-region floor hard to justify. Teams that need to run outside AWS shouldn’t rely solely on AWS API Gateway. And teams that want a fully managed, zero-ops gateway without learning Kubernetes or managing self-hosted infrastructure may find Kong Gateway OSS more operational work than they bargained for — Konnect’s Dedicated Cloud Gateway tier exists specifically to solve that, at a price.
Bottom Line
These three aren’t quite interchangeable: AWS API Gateway is the cheapest and simplest if you live inside AWS, Kong is the most flexible and the only genuinely free option if you self-host, and Apigee is the most complete but the most expensive by a wide margin. The right choice depends less on raw price and more on where your infrastructure already lives and whether you’re routing internal traffic or productizing APIs for external partners.
FAQ
Is Kong Gateway really free?
Yes — Kong Gateway’s open-source core is released under the Apache License 2.0 and is free to self-host. Kong Inc. charges for Konnect, its managed SaaS control plane, and for Enterprise features like SSO and audit logging.
Which is cheapest for a low-traffic API?
For a small, low-volume API on AWS, AWS API Gateway’s HTTP API type is typically the cheapest, especially within the 12-month free tier covering the first 1 million calls per month. Apigee’s $365+/month regional floor makes it the most expensive for low traffic.
Can I use Apigee’s pricing calculator to get exact enterprise costs?
Not fully. Apigee publishes pay-as-you-go environment and per-call rates, but its Standard, Enterprise, and Enterprise Plus subscription tiers — which include monetization and higher call volumes — are quote-only through Google Cloud sales.
“AI agent” products for end users — the kind that autocomplete your code or summarize your inbox — are only half the story. Underneath most of them sits an open-source framework that developers use to wire large language models into autonomous, multi-step workflows. Three names dominate that layer in 2026: LangChain (with its agent-orchestration companion LangGraph), Microsoft’s AutoGen, and CrewAI. They solve the same basic problem — getting one or more LLM-driven “agents” to plan, call tools, and hand off work — but they take meaningfully different approaches, and one of the three has just been formally retired in favor of a successor. Here’s what each actually offers, verified against their own repositories and pricing pages.
At a Glance
Framework
License
Development Status (2026)
Core Model
Paid Tier
LangChain / LangGraph
MIT (open source)
Actively developed
Chains and graphs of LLM calls, tools, and agents
LangSmith: free Developer plan, Plus $39/seat/mo + usage, custom Enterprise
AutoGen (Microsoft)
MIT (open source)
Maintenance mode — bug/security fixes only
Multi-agent conversation (agents “chat” to solve tasks)
None; community-managed. Successor: Microsoft Agent Framework
If you want the biggest ecosystem, the most integrations, and don’t mind a steeper learning curve, LangChain (via LangGraph for the agent-orchestration layer) is the default choice. If you want agents that behave like a structured team with clear roles and tasks, CrewAI is the more opinionated, often faster-to-prototype option. AutoGen is the one to be careful with: Microsoft’s own repository now states it is in maintenance mode and points new projects to Microsoft Agent Framework instead, so it’s a poor choice for anything you plan to build on for the next few years.
What Each One Is
LangChain describes itself, in its own GitHub README, as “a framework for building agents and LLM-powered applications.” It’s the oldest and most sprawling of the three, with hundreds of integrations for models, vector stores, and tools. LangGraph, a companion library, is what most teams now use specifically for building controllable, stateful agents on top of LangChain’s primitives. The company behind both also sells LangSmith, a separate paid observability and deployment platform — the open-source framework itself remains free and MIT-licensed.
AutoGen is Microsoft’s framework for “creating multi-agent AI applications that can act autonomously or work alongside humans,” per its own README. As of 2026, Microsoft’s repository carries an explicit notice: “AutoGen is now in maintenance mode.” It will not receive new features, remains under the microsoft GitHub organization, and is described as “community managed going forward,” with contributions limited to bug fixes, security patches, and documentation. Microsoft directs new users to a separate project, Microsoft Agent Framework, which it calls the “enterprise-ready successor to AutoGen,” along with a migration guide for existing AutoGen users.
CrewAI bills itself as a “Framework for orchestrating role-playing, autonomous AI agents.” Rather than modeling agents as a graph of arbitrary steps, CrewAI organizes work around a “crew”: a set of agents, each with a role, goal, and backstory, assigned to specific tasks. Its own FAQ describes it as a “standalone Python framework with its own primitives” rather than a layer built on top of LangChain.
A Minimal Example
CrewAI’s role-based model is easiest to show in a few lines. This illustrates the shape of the API, not a guaranteed-working script — check current docs for exact argument names before running it:
from crewai import Agent, Task, Crew
researcher = Agent(
role="Researcher",
goal="Find and summarize recent facts on a topic",
backstory="An analyst who double-checks every claim."
)
task = Task(
description="Research current AI agent framework adoption trends",
agent=researcher,
expected_output="A short bulleted summary"
)
crew = Crew(agents=[researcher], tasks=[task])
result = crew.kickoff()
Pros and Cons
LangChain / LangGraph
Pros: Largest integration ecosystem of the three; LangGraph gives fine-grained control over agent state and branching; active, well-funded development; optional LangSmith adds tracing and evaluation.
Cons: Steeper learning curve and more abstractions to learn; LangSmith’s usage-based pricing (billed in “LangChain Standard Units”) can be hard to estimate in advance; some teams find the API surface large relative to what a simple agent needs.
AutoGen
Pros: Still free, open-source (MIT), and usable for existing projects or learning the underlying conversation-pattern concepts; backed by a large existing codebase and community of past adopters.
Cons: Officially in maintenance mode with no new features; Microsoft is actively steering new and existing users toward Microsoft Agent Framework; a risky foundation for a new, long-lived project in 2026.
CrewAI
Pros: Role-based model maps intuitively onto real team workflows; standalone design with its own primitives rather than a wrapper on another framework; free Cloud tier for small workloads; actively developed.
Cons: Less infrastructure-agnostic tooling (tracing, evaluation) than the LangChain ecosystem out of the box; Enterprise pricing isn’t public, so cost at scale requires a sales conversation.
Who It’s a Good Fit For
Teams that need maximum flexibility, lots of third-party integrations, and are willing to invest in learning a bigger framework should default to LangChain/LangGraph. Teams that think of their problem as “a small team of specialists handing off tasks” will likely prototype faster in CrewAI. Teams currently running AutoGen in production should start planning a migration to Microsoft Agent Framework, since Microsoft’s own repository says plainly that AutoGen won’t gain new features going forward.
Who Should Look Elsewhere
Anyone starting a brand-new multi-agent project in 2026 should not pick AutoGen as the long-term foundation, given its maintenance-mode status. Teams wanting a fully managed, no-code agent builder rather than a Python framework should also look elsewhere — all three of these are developer-facing libraries, not low-code platforms.
Bottom Line
All three frameworks are free and MIT-licensed at their core, so the real decision is architecture and longevity, not price. LangChain/LangGraph is the broad, extensible default; CrewAI is the faster, more structured option for role-based workflows; AutoGen is a known quantity that Microsoft itself is winding down in favor of Microsoft Agent Framework. For a new project, weigh LangGraph against CrewAI based on how your problem is shaped, and treat AutoGen as legacy.
FAQ
Is AutoGen dead?
Not dead, but no longer actively developed by Microsoft. Its own repository states it’s in maintenance mode, limited to bug fixes, security patches, and documentation, with Microsoft Agent Framework positioned as its successor.
Is CrewAI built on top of LangChain?
No. CrewAI’s own FAQ describes it as a standalone Python framework with its own primitives, independent of LangChain.
Do I have to pay to use any of these?
No — the core frameworks (LangChain, LangGraph, AutoGen, and CrewAI) are all free and open source under the MIT license. Paid tiers only apply to optional hosted add-ons: LangSmith for LangChain/LangGraph, and CrewAI’s Enterprise/Cloud offering.
Which one is easiest to learn first?
Most developers find CrewAI’s role/task/crew model quicker to grasp for a first project, while LangGraph’s graph-based state model takes longer to learn but scales to more complex, custom agent behavior.
Add or remove one server from a cache cluster that uses naive hashing, and almost every key can end up pointing at a different node — triggering a stampede of cache misses. Consistent hashing is the technique that keeps this from happening, and it quietly runs underneath systems like Apache Cassandra, Amazon DynamoDB, and the client libraries behind memcached. Here is what it actually does, how it works, and where you’ll find it in production.
At a Glance
Problem solved
Mass key remapping when nodes are added or removed from a distributed cache, store, or load balancer
Core idea
Map both nodes and keys onto a fixed circular hash space (a “ring”); a key belongs to the next node clockwise
Keys remapped on node change
Roughly 1/N of keys (N = number of nodes), versus nearly all keys with naive modulo hashing
Key refinement
Virtual nodes (vnodes) — each physical node owns many positions on the ring instead of one
Known production users
Amazon DynamoDB (originally Dynamo), Apache Cassandra, memcached client libraries (Ketama), many CDN and load-balancer designs
Origin
Karger et al., “Consistent Hashing and Random Trees” (1997), developed for web cache load distribution
The Problem: Why Naive Hashing Breaks at Scale
The obvious way to spread keys across N servers is hash(key) % N. It’s simple and balances load evenly — right up until N changes. Adding or removing a single server changes the modulus, which changes the bucket almost every key maps to. In a cache, that means a near-total wipeout: every client suddenly misses, hits the database at once, and the system can fall over from the resulting load spike. In a sharded data store, it means moving almost all the data in the cluster just to add one disk’s worth of capacity.
How Consistent Hashing Works
Consistent hashing fixes this by hashing nodes onto the same space as keys, rather than deriving a bucket from a count that can change.
Imagine a ring of hash values from 0 to some large maximum, wrapping back to 0.
Each server is hashed to one or more positions (tokens) on that ring.
Each key is also hashed onto the ring.
A key belongs to the first server found by walking clockwise from the key’s position — its “token range.”
When a server is added, it only takes over the token range immediately counter-clockwise from its new position — keys that used to belong to its clockwise neighbor. Every other server’s assignments are untouched. Apache Cassandra’s own architecture documentation describes this directly: in an eight-node ring with evenly spaced tokens, a key’s replicas are found by walking clockwise until three distinct nodes (for replication factor 3) are reached, and only the token range between two adjacent tokens needs to move when the ring changes.
Why One Token Per Node Isn’t Enough: Virtual Nodes
A ring with exactly one token per physical node has two practical problems, both laid out in Amazon’s original 2007 Dynamo design (via Werner Vogels’ engineering blog) and in Cassandra’s architecture docs: random placement produces uneven load across nodes, and it can’t reflect the fact that real hardware isn’t uniform — some nodes have more CPU, memory, or disk than others.
The fix is virtual nodes (vnodes): each physical node is assigned many tokens on the ring instead of one. Dynamo’s design ties the number of tokens a node holds to its capacity, so a beefier machine simply claims more positions and absorbs a proportionally larger share of keys. Cassandra’s documentation lists the same three benefits:
Failure handling: when a node goes down, its load spreads across many remaining nodes instead of dumping entirely onto one neighbor.
Rebalancing: a node that joins or returns takes a roughly equal slice of data from every other node, not just its ring neighbor.
Heterogeneity: a node’s vnode count can be set to match its hardware capacity.
Cassandra notes a real trade-off here too: more tokens per node means more neighbors on the ring (up to 2 × (RF−1) per token), which increases the number of node-failure combinations that can cause partial unavailability, and more discrete repair operations. Early Cassandra 2.x defaulted to 256 random tokens per node to keep balance; later versions added a deterministic token allocator that balances the ring with far fewer tokens, trading some of that flexibility for lower operational overhead.
A Simple Walkthrough
Picture a ring labeled 0 to 359 (like a clock face). Three nodes hash to positions 40, 160, and 280. A key that hashes to position 200 walks clockwise and lands on the node at 280. If a fourth node joins at position 100, it only absorbs the slice of keys between 40 and 100 — keys that used to belong to the node at 160. Nothing assigned to the nodes at 160 or 280 moves. That’s the entire benefit in one sentence: changing the ring only touches the token range next to the change, not the whole dataset.
Real-World Uses
System
How it’s used
Amazon DynamoDB (originally Dynamo)
Core partitioning mechanism; virtual nodes sized to node capacity for incremental, low-disruption scaling
Apache Cassandra
Token ring with vnodes; SimpleStrategy and NetworkTopologyStrategy walk the ring to place replicas across nodes, racks, and datacenters
memcached client libraries (e.g. Ketama)
Client-side consistent hashing so adding/removing a cache server doesn’t invalidate the whole cache
Load balancers / CDNs
Routes a given client or object key to a stable backend/edge node even as the pool of backends changes
Trade-offs to Know
Not perfectly even without vnodes: a small number of nodes with single random tokens can still produce uneven ranges; virtual nodes are what actually make load distribution smooth in practice.
More tokens, more neighbors: higher vnode counts spread load more evenly but widen the blast radius of correlated failures and increase repair/maintenance overhead, per Cassandra’s own documentation.
It solves placement, not consistency: consistent hashing decides which node a key belongs to; it says nothing on its own about replication guarantees, quorum reads/writes, or conflict resolution, which systems like Dynamo and Cassandra layer on top separately.
Bottom Line
Consistent hashing is a narrow, specific fix for a narrow, specific problem: keeping key-to-node assignment stable when the set of nodes changes. On its own it’s just a ring and a clockwise lookup; the engineering that makes it usable in production — virtual nodes, capacity-aware token counts, and allocator strategies that cap how many tokens a node needs — is what Dynamo and Cassandra actually spend their design effort on. If you’re building or evaluating a distributed cache, sharded store, or load balancer, the question isn’t whether it uses “consistent hashing” as a buzzword, but how it handles virtual nodes and rebalancing cost, since that’s where the real trade-offs live.
FAQ
Is consistent hashing the same as a hash table? No. A hash table maps keys to array indices for in-memory lookup. Consistent hashing maps keys to nodes in a distributed system, specifically designed so that changing the number of nodes moves as few keys as possible.
Do I need virtual nodes, or is one token per node enough? For anything beyond a handful of nodes, virtual nodes are what actually deliver even load distribution and capacity-aware placement in practice; single-token rings are mostly a teaching simplification at this point.
Does consistent hashing guarantee data isn’t lost when a node fails? No — it only decides which node a key should live on. Durability and availability come from replication (storing a key on multiple nodes along the ring) and quorum logic layered on top, as in Dynamo and Cassandra.
Database schema changes are one of the easiest ways to break production, which is why most engineering teams eventually adopt a migration tool: something that tracks every schema change as a versioned, repeatable script instead of a mix of manual ALTER TABLE statements and tribal knowledge. Three names dominate this space — Flyway, Liquibase, and the newer Atlas — and all three now split their offering into a free, open-source core and a paid tier aimed at teams and enterprises. This review compares what you actually get for free, what’s gated behind a paid plan, and which tool fits which kind of team in 2026.
Polyglot teams wanting format flexibility and governance
Atlas
Community Edition (core schema diff/apply for MySQL, Postgres, SQLite, MariaDB)
Apache 2.0
Pro (seats) + Pipelines + Schema Monitoring (quote-based)
Teams wanting declarative, Terraform-style schema-as-code
Short Verdict
All three tools give away a genuinely usable free core, which is unusual in this category. Flyway’s Community edition is the simplest path for plain versioned SQL migrations and has the longest track record. Liquibase Community offers the most format flexibility (SQL, XML, YAML, JSON) and the richest changelog model, but its best governance and security features now sit behind the newly renamed “Liquibase Secure” tier. Atlas takes a different, more modern approach — declarative, diff-based schema management closer to Terraform than to hand-written migration scripts — but its free Community Edition is the most restricted of the three, holding back linting, drift detection, and several database drivers for the Pro tier. None of the three vendors publish a flat dollar price for their paid tiers; all three sell through a quote.
What These Tools Actually Do
Flyway (originally by Boxfuse, now owned by Redgate) tracks schema changes as numbered, immutable SQL (or Java-based) migration files, applied in order and recorded in a schema history table. It’s intentionally simple: write a file like V1__create_users_table.sql, run flyway migrate, and Flyway tracks what’s already been applied.
Liquibase uses “changesets” defined in a changelog file, which can be written in SQL, XML, YAML, or JSON. Each changeset is a discrete, trackable unit of change, and Liquibase can also auto-generate rollback statements for many common change types — something Flyway’s Community edition doesn’t do out of the box.
Atlas (by Ariga) flips the model: instead of writing migration scripts by hand, you declare your desired schema state (often in Atlas’s own HCL-based language, or inferred from an ORM), and Atlas computes the diff and generates the migration automatically — similar to how Terraform plans infrastructure changes. This “declarative” style can be faster for teams that want their schema defined as code, but it’s a bigger conceptual shift than Flyway or Liquibase’s script-based approach.
Pricing and Licensing Breakdown
Tool
Free tier covers
Paid tier structure
Published dollar price?
Flyway
Full Community CLI; database support for 5 years from each DB’s GA release
Teams (10-year DB support window, up to 100 schemas, licensed per user) and Enterprise (required beyond 100 schemas, also per user)
No — Redgate sells Teams/Enterprise via quote; legacy per-schema licenses are handled separately through sales
Liquibase
Full Community changelog engine, CLI, and broad database driver support
Liquibase Secure in four named plans — Starter, Team, Business, Enterprise — differentiated by number of database types, number of database “targets,” and support SLA (standard vs. 24/7 premium)
No — every Secure plan page says “Get a Quote,” and each requires a separate professional-services package
Atlas
Core schema diff/apply/status for MySQL, Postgres, SQLite, and MariaDB only
Pro is sold as three separate line items — per-developer CLI/Web seats, CI/CD “Pipelines” (priced per project and target database, two free targets per project), and Schema Monitoring (priced per monitored database); Enterprise adds SSO and dedicated support
No — Atlas’s pricing page breaks down the billing dimensions but lists no per-unit dollar figures; it offers 10 free seats, one free project, and one free monitored database per company
In practice, this means the real cost comparison has to happen in a sales conversation with each vendor — this article can tell you what’s gated and how pricing is structured, but not what you’ll actually pay, because none of the three publish that.
Pros
Flyway: Simplest mental model (plain numbered SQL files), huge ecosystem adoption, Apache 2.0 Community edition with no artificial feature caps on the core migration engine.
Liquibase: Multi-format changelogs (SQL/XML/YAML/JSON), built-in rollback generation, widest official database driver list of the three, strong changeset-level tracking for audits.
Atlas: Declarative, Terraform-style workflow that can auto-generate migrations from a desired-state schema; a Kubernetes Operator, Terraform provider, and GitHub Actions integration exist for teams that are already infrastructure-as-code shops (though these integrations require the standard/Pro distribution, not Community).
Cons
Flyway: Community edition has no built-in automatic rollback generation or drift detection; those and extended database-version support sit behind Teams/Enterprise.
Liquibase: The best governance, policy-enforcement, drift detection, and audit-trail features were moved into the renamed “Secure” tier, and every paid plan bundles in a mandatory professional-services package, which makes it harder to buy “just a little more” than Community.
Atlas: The Community Edition is the most limited of the three — it excludes linting, testing, drift detection, several database drivers (SQL Server, ClickHouse, Oracle, Snowflake, Spanner), and common integrations; you need to log in and start a 30-day Pro trial to unlock most of what makes Atlas distinctive.
Who It’s a Good Fit For
Teams that just need reliable, versioned SQL migrations with no frills are well served by Flyway’s free Community edition. Teams that want changelog flexibility across formats, auto-generated rollbacks, and are willing to pay for governance as they scale should look at Liquibase. Teams already comfortable with a declarative, “schema-as-code” workflow — especially those running Kubernetes or Terraform-heavy infrastructure — are the best fit for Atlas, as long as they budget for a Pro login once they outgrow basic diff/apply.
Who Should Look Elsewhere
Teams that need enterprise drift detection, policy enforcement, or audit trails without engaging a sales process should expect friction with all three, since that functionality is paid and quote-gated everywhere. Teams needing day-one support for databases like Oracle, SQL Server, Snowflake, or Spanner for free will find Atlas Community too restrictive and should compare Flyway’s and Liquibase’s driver support instead.
Bottom Line
There’s no bad choice among these three at the free tier — each is a legitimate, production-grade migration engine with no time bomb. The decision mostly comes down to workflow philosophy: script-based and simple (Flyway), format-flexible with changeset auditing (Liquibase), or declarative and diff-based (Atlas). Budget for a sales conversation if you need governance, drift detection, or extended database support, since none of the three will give you a self-serve dollar price for that tier.
FAQ
Is Flyway really free? Yes — Flyway Community is Apache 2.0 licensed and free to use, with database support guaranteed for 5 years from each database’s general-availability release. Teams and Enterprise add longer support windows and are licensed per user through a quote.
Is Liquibase Community still maintained now that Liquibase Secure exists? Yes. Liquibase 5.0 Community remains the free, self-managed engine under the Functional Source License, and the vendor states that accepted Community changes flow into future Secure releases.
Does Atlas require a paid plan to use in CI/CD? Not strictly — the standard Atlas CLI distribution (separate from the stripped-down Community Edition) includes all database drivers and integrations like the Kubernetes Operator and GitHub Actions, but running atlas login to unlock linting, testing, and other Pro features starts a 30-day trial, after which continued use requires a license.
Can I migrate from Flyway or Liquibase to Atlas (or vice versa)? There’s no official one-click converter between these tools’ history tables. Switching generally means baselining your existing schema as the starting point in the new tool and migrating forward from there; this is a project of its own and worth planning for separately rather than assuming a drop-in swap.
If you run a partner or affiliate program, the tracking platform underneath it decides how accurately you pay commissions, how fast you catch fraud, and how much manual spreadsheet work your team does every month. Everflow, Tune, and Impact (impact.com) are three of the most established names in this space, but they take very different approaches to both pricing and scale. Here’s how they actually compare in 2026.
At a Glance
Platform
Starting Price
Best For
Pricing Model
Everflow
Not publicly listed (custom quote, 6-month minimum commitment)
Performance marketing teams running large affiliate + media-buying operations
Custom contract
Tune
$1,500/mo (Scale plan, billed annually)
Mid-size to enterprise partner programs needing a dedicated CSM
Flat fee + custom tier
Impact (impact.com)
$30/mo + 2.5% of revenue (Starter, ecommerce only)
Ecommerce brands of nearly any size, from small shops to $15M+ enterprises
Tiered, revenue-based at entry, flat + payout cap above that
Short Verdict
Impact is the only one of the three with genuinely public, tiered pricing, which makes it the easiest to evaluate and the best starting point for smaller or ecommerce-first brands. Tune publishes one real price point (its $1,500/mo Scale plan) but pushes larger programs into a custom quote. Everflow publishes no pricing at all — every plan is quoted individually and locked into a 6-month minimum term, which makes it a harder platform to recommend without first talking to sales.
What They Are
Everflow is a partner marketing and affiliate tracking platform built for performance marketers, with strong media-buying attribution, a managed-payouts product called Everflow Pay, and fraud/traffic-health monitoring. It markets itself heavily toward agencies and networks running affiliate and paid traffic side by side.
Tune (formerly HasOffers) is one of the oldest names in affiliate tracking software, built around a self-service SaaS model with its own partner marketplace, real-time reporting, and a dedicated Customer Success Manager included even on its published Scale tier.
Impact (impact.com) is the broadest of the three, covering affiliate tracking plus influencer/creator management (Creator), customer referrals (Advocate), and enterprise partnership automation. Its lowest tier is restricted to specific ecommerce platforms (Shopify, WooCommerce, BigCommerce, Adobe Commerce, Squarespace, Ecwid, Shoplazza, nopCommerce, and Zoho Commerce), while higher tiers serve any business model.
Pricing Breakdown
Platform
Tier
Price
Notes
Everflow
All tiers
Custom quote only
No public price list; requires a 6-month minimum commitment; free migration from Tune, Cake, and HitPath
Tune
Scale
$1,500/mo, billed annually
2,500 conversions/mo included; Customer Success Manager; email, chat, and phone support
Tune
Custom
Quote-based
2,500+ conversions/mo; adds a dedicated developer support team
Impact
Starter
$30/mo + 2.5% of revenue
Ecommerce-platform-only; for brands around $300K/year in marketing spend
Impact
Essentials
$500/mo
Up to $2M/year ecommerce revenue; includes up to $2,500/mo in partner payouts (minimum $2,500/mo processed)
Impact
Pro
$2,500/mo
$2M–$15M/year revenue; includes up to $14,300/mo in payouts, API tracking, custom commissions
Impact
Enterprise
Custom quote
$15M+/year or multi-channel operations; white-labeled partner portal, advanced fraud scoring
Note that Everflow’s comparison table lists roughly 20 features without clearly mapping which plan tier includes which — a limitation of its marketing site, not something this review can resolve without a sales quote. The same applies to a chunk of Tune’s feature list.
Pros
Everflow: Strong media-buying and traffic-health/fraud monitoring; free migration tooling from competing platforms; good fit for agencies running affiliate and paid traffic together.
Tune: At least one real, published price point; dedicated Customer Success Manager from the entry paid tier; long track record in the affiliate-tracking space.
Impact: Fully transparent, tiered public pricing from $30/mo up to $15M+ enterprise; broadest feature set (affiliate + influencer + referral) under one platform; clear revenue-based tiers make self-qualification easy.
Cons
Everflow: Zero public pricing; 6-month minimum commitment is a real lock-in risk if the platform turns out to be a poor fit.
Tune: Only one tier has a public price; the Custom tier (needed by larger programs) is quote-only, same as Everflow.
Impact: Starter tier is locked to specific ecommerce platforms; Essentials and Pro layer a flat fee on top of a payout cap, so costs can rise quickly once payout volume grows past the included amount.
Who It’s a Good Fit For
Impact is the best starting point for most ecommerce brands and marketing teams that want to see real numbers before talking to a salesperson. Tune suits mid-size programs that want a published entry price with a dedicated success manager. Everflow fits agencies and performance-marketing teams already comfortable with a sales-led buying process and a 6-month contract, especially if their stack includes heavy media-buying attribution.
Who Should Look Elsewhere
Small teams that want to avoid sales calls entirely should start with Impact’s published tiers rather than Everflow or Tune’s Custom plan. Non-ecommerce businesses below Impact’s Essentials threshold, or brands outside its supported Starter platforms, will need to go straight to Essentials pricing or look elsewhere.
Bottom Line
There isn’t a single winner here — there’s a winner for transparency (Impact), a winner for an old-school SaaS price point (Tune), and a platform that simply expects you to talk to sales first (Everflow). If pricing transparency and self-service evaluation matter to you, start with Impact. If you’re already running meaningful affiliate or media-buying volume and don’t mind a quote process, Everflow and Tune’s Custom tier are worth a conversation.
FAQ
Does Everflow publish any pricing at all? No. As of this review, Everflow’s pricing page only offers a quote request, with a stated 6-month minimum commitment for its plans.
Is Tune’s $1,500/mo plan its cheapest option? It’s the cheapest tier with a published price (Scale, billed annually). Smaller or larger programs needing different limits go through Tune’s Custom, quote-based tier.
Can any business use Impact’s $30/mo Starter plan? No — Starter is restricted to specific ecommerce platforms (Shopify, WooCommerce, BigCommerce, Adobe Commerce, Squarespace, Ecwid, Shoplazza, nopCommerce, and Zoho Commerce) and is aimed at brands around $300K/year in marketing spend. Other businesses start at Essentials ($500/mo).
Which platform is easiest to budget for in advance? Impact, because its Starter, Essentials, and Pro tiers all have published flat or percentage-based prices. Everflow and Tune’s higher tiers require a sales conversation before you’ll know the real cost.
Datadog, Grafana Cloud, and New Relic are the three platforms engineering teams reach for most often when they need metrics, logs, and traces in one place. All three are usage-based, which makes them powerful and genuinely confusing to price. This review pulls the actual numbers from each vendor’s own pricing page so you can see where the real cost differences are before you commit.
At a Glance
Platform
Free Tier
Entry-Level Pricing
Pricing Model
Best For
Datadog
Up to 5 “Basic” infra hosts (1-day retention); no free logs/APM
Infra Pro from $15/host/mo (annual)
Per host + per GB/million events, modular by product
Teams that want one platform for everything and can manage per-product billing
Grafana Cloud
Full feature set with usage caps (10k metric series, 50GB logs/traces, 14-day retention)
Small teams and solo developers who want a generous permanent free tier
Short Verdict
New Relic has the most forgiving free tier (100GB of data a month, forever, no credit card), which makes it the easiest to try and the cheapest for small teams. Grafana Cloud is the best value if your team already thinks in Prometheus/Loki/Tempo terms and wants to self-serve on usage-based pricing without a sales call. Datadog is the most complete single platform — infrastructure, APM, logs, security, and dozens of integrations under one roof — but its per-product, per-host pricing adds up fast and the most useful retention and indexing tiers are gated behind “contact sales.”
What It Is
All three are observability platforms: they collect metrics (numeric time series), logs (text records), and traces (request-level timing across services) so engineers can find out why something broke or slowed down. Datadog and New Relic are commercial SaaS platforms built from the ground up as all-in-one products. Grafana Cloud is the hosted, managed version of the open-source Grafana stack (Grafana for dashboards, Prometheus-compatible Mimir for metrics, Loki for logs, Tempo for traces, Pyroscope for profiles) — so it’s the natural fit for teams who want OSS-compatible tooling without running the infrastructure themselves.
Enterprise Infra from $23/host/mo; custom retention via sales
Custom, $25,000/year minimum commit
Contact sales
A practical note on reading these numbers: Datadog and Grafana Cloud both split “ingest,” “process,” and “retain/index” into separate line items, so the headline per-GB figure is rarely the whole story — a GB of logs can be billed for ingestion and again for indexed retention. New Relic collapses this into one ingest price per GB, which is simpler to estimate but means heavier log or trace volume hits the same meter as your metrics.
Pros
Datadog — the broadest product catalog (APM, RUM, security, CI visibility, synthetics) with deep integrations (900+); best if you want one vendor for nearly everything.
Grafana Cloud — OSS-compatible (Prometheus/Loki/Tempo APIs), so you can self-host part of the stack and move workloads in or out without lock-in; transparent public pricing calculator.
New Relic — simplest mental model (GB ingested, full vs. basic users), a genuinely usable permanent free tier, and unlimited free “Basic” (read-only) users for stakeholders.
Cons
Datadog — per-host, per-product billing compounds quickly across infra + APM + logs; several retention/indexing tiers require contacting sales rather than self-serve pricing.
Grafana Cloud — the number of separately metered products (14+ line items on the pricing page) makes forecasting a bill harder than it should be; Enterprise jumps straight to a $25,000/year commit.
New Relic — Pro-tier full users are expensive ($349–$418.80/user/month), and once you exceed the 100GB free ingest in a month, data stops flowing until you upgrade or the month resets.
Who It’s a Good Fit For
Small teams and solo developers who want to try real observability without a credit card should start with New Relic’s free 100GB tier. Teams already running Prometheus, Loki, or Grafana OSS and want a managed, scalable version of the same stack should look at Grafana Cloud. Organizations that want a single vendor covering infrastructure, APM, security, and user-experience monitoring — and have the budget to negotiate annual contracts — are the clearest fit for Datadog.
Who Should Look Elsewhere
Budget-conscious teams with high log or trace volume should be cautious with Datadog, since ingestion, indexing, and retention are billed separately and can surprise you. Teams that want a single flat number with no usage math should be wary of all three usage-based platforms generally; a flat-rate competitor may suit them better. Teams that need deep enterprise support and compliance guarantees from day one will find New Relic’s self-serve Standard/Pro tiers too limited and will need to go straight to its Enterprise sales process.
Bottom Line
There’s no single winner — the right pick depends on which meter you’re most afraid of. If you want to avoid a credit card and a learning curve, start with New Relic’s free tier. If you want open standards and predictable, self-serve usage pricing, Grafana Cloud is the better long-term bet. If you want maximum feature breadth and are prepared to manage a more complex, negotiated bill, Datadog remains the category leader.
FAQ
Which is cheapest for a small startup?
New Relic, in most cases — its 100GB/month free tier and single free full-platform user cost nothing, and additional data is a flat $0.40/GB beyond that on the Standard plan.
Can I self-host any of these to avoid cloud pricing?
Only Grafana’s underlying stack (Grafana, Prometheus/Mimir, Loki, Tempo) is open source and self-hostable. Datadog and New Relic are closed, cloud-only SaaS platforms.
Do these prices include support?
Standard support is generally included; premium/enterprise support (faster SLAs, dedicated contacts) is an add-on or bundled only into Enterprise-tier contracts on all three platforms.
Every Meta (Facebook and Instagram) advertiser starts with the same free tool: Ads Manager. The question this article answers is when it stops being enough, and whether AdEspresso or Madgicx — the two best-known third-party layers built on top of Meta’s ad API — are worth paying for in 2026.
At a Glance
Tool
Best For
Starting Price
Free Trial
Platforms Covered
Meta Ads Manager
Anyone running Meta ads — the required baseline
Free (you only pay your ad spend)
N/A — always free
Facebook, Instagram, Messenger, Audience Network
AdEspresso by Hootsuite
Small teams wanting split-testing and client reporting
$49/mo (Starter, up to $1,000/mo ad spend)
14 days
Facebook, Instagram
Madgicx
Larger spenders wanting AI-driven automation and tracking
Price disclosed only after signup, tiered by ad spend; $49/mo Tracking Pro add-on is public
7 days
Facebook, Instagram (plus Google/TikTok tracking via add-on)
Short Verdict
Meta Ads Manager itself is free to use — Meta charges only for the ads you run, not for access to the tool — and it already includes guided campaign creation, Advantage+ automated budget and audience optimization, A/B testing during setup, and a reporting tab with premade dashboards and custom pivot tables. For a single advertiser managing one or two ad accounts, that is often genuinely enough. AdEspresso earns its $49–$259/month fee mainly for agencies and teams that need structured split-testing, white-label client reports, and multi-account bulk creation. Madgicx targets a higher-spend audience with AI-driven budget reallocation and creative analytics, but it is unusually opaque about its core pricing, disclosing numbers only after signup.
What These Tools Actually Do
None of these three replace Meta Ads Manager — AdEspresso and Madgicx both connect to your Meta ad account through Meta’s official API and add a management layer on top. Think of Ads Manager as the engine and these tools as dashboards that make specific jobs (testing variations, automating rules, reporting to clients) faster than doing them natively.
Meta Ads Manager: The Free Baseline
Ads Manager is free to access; you are only billed for the ads you actually run. It supports guided and quick campaign-creation modes across six campaign objectives, structures campaigns into campaigns/ad sets/ads, and leans heavily on AI-driven automation — Advantage+ campaign budgets shift spend toward better-performing ad sets automatically, and Advantage+ can automate audience, placement, creative, and destination selection in a single step. You can set up A/B tests during campaign creation, and the Ads Reporting tab offers premade dashboards plus custom pivot tables with breakdowns by day, time, action, or delivery format. What it does not offer natively: cross-account bulk creation, white-label client reporting, or user-defined automated rules with the granularity that dedicated third-party tools provide.
AdEspresso by Hootsuite: Split-Testing and Reporting Add-On
AdEspresso’s pricing is public and tiered by ad spend, not by feature access to its core toolset:
Cross-campaign performance triggers, multi-page bulk creation, campaign approval, up to 15 seats, white-label reports
Enterprise
From $259/mo
Unlimited
Dedicated Facebook marketing consultant, 1+ hour live strategy/month, unlimited seats, API access, Salesforce sync
Every tier includes AdEspresso’s core feature set: importing existing campaigns, automated promotion of Facebook posts, split-testing breakdowns through its “Inspector” analysis, automatic contact syncing for lead campaigns, tag-based aggregated reporting, schedulable reports, and customizable performance triggers. The jump from Starter to Plus is really about ad spend headroom and team/client-facing features, not core functionality.
Madgicx: AI-Driven Optimization Layer
Madgicx bundles automation, audience targeting, analytics, and ad management into a single “Pro Complete” plan, with monthly, quarterly, and annual billing (quarterly/annual advertised at roughly 30% off monthly). The notable gap: Madgicx does not publish a specific dollar price for this plan on its own pricing page. Instead, prospective customers answer a monthly-ad-spend question (ranges from under $1,000 to over $30,000) and the exact price is revealed only after starting a 7-day free trial inside the app. The one number Madgicx does publish openly is its Tracking Pro add-on at $49/month, which provides server-to-server conversion tracking and enhanced Meta Click ID matching for more accurate attribution as browser tracking continues to erode. Because the core plan’s price depends on an ad-spend tier revealed post-signup, readers comparing total cost should request that figure directly before committing rather than relying on any third-party estimate.
Pros and Cons
Meta Ads Manager
Pros: free, native, Advantage+ automation handles a lot of optimization automatically, no learning curve for basic use
Cons: weaker for formal split-testing at scale, no white-label client reporting, no cross-account bulk tools
AdEspresso
Pros: transparent published pricing, strong split-testing and client-reporting features, good for agencies
Cons: Starter tier caps ad spend at $1,000/month, Enterprise pricing starts high for small businesses
Madgicx
Pros: AI-driven budget and creative optimization, dedicated first-party tracking add-on, free trial covers full feature set
Cons: core plan pricing is not public, must sign up and answer a spend questionnaire before seeing a price
Who It’s a Good Fit For
Solo advertisers and small businesses running a handful of campaigns are usually well served by Meta Ads Manager alone — Advantage+ automation covers most of what a paid tool would otherwise add manually. Agencies managing multiple clients, needing white-label reports, or running structured A/B tests across many ad sets are the clearest fit for AdEspresso. Larger advertisers (roughly $5,000/month and up in spend) who want AI-driven budget reallocation and are comfortable providing spend details to see a quote are the target audience for Madgicx.
Who Should Look Elsewhere
If your monthly ad spend is under $1,000 and you just need to launch and monitor campaigns, paying $49+/month for AdEspresso or Madgicx on top of your ad spend is hard to justify — Meta’s own Advantage+ automation covers most of that ground for free. Businesses that need pricing certainty before any commitment should be cautious with Madgicx until they get a direct quote.
Bottom Line
Start with Meta Ads Manager — it is free and, thanks to Advantage+ automation, more capable than it was a few years ago. Upgrade to AdEspresso when you need agency-style reporting and structured testing at a transparent, published price. Consider Madgicx once your spend is high enough to justify AI-driven optimization, but get an exact quote before assuming what it will cost.
FAQ
Is Meta Ads Manager really free? Yes. There is no subscription fee to access or use Ads Manager; advertisers are only charged for the ads they run.
Do AdEspresso and Madgicx replace Meta Ads Manager? No. Both connect to your existing Meta ad account through Meta’s API and add management, testing, or automation features on top — you still need a Meta ad account.
Why doesn’t Madgicx publish its core pricing? Madgicx ties its main plan’s price to a monthly-ad-spend tier that it reveals only after you start the 7-day free trial. Its Tracking Pro add-on ($49/month) is the only core price published on its site.
Can I use these tools for Google or TikTok ads too? AdEspresso is Facebook/Instagram-focused. Madgicx’s core product is also Meta-focused, though its Tracking Pro add-on extends attribution tracking to other channels.
Workflow automation tools let you connect apps so data moves between them without manual copy-pasting. Zapier popularized the category, Make (formerly Integromat) built a more visual, branching alternative, and n8n took a different route entirely: open-source and self-hostable, with a cloud version for anyone who’d rather not run their own server. Picking between them comes down to how you’re billed for usage, how much visual control you want over the automation logic, and whether you ever want to self-host.
At a Glance
Tool
Free plan
Billing unit
Entry paid plan
Self-hostable
Zapier
100 tasks/month, 2-step Zaps only
Tasks (one per action executed)
Professional, from $19.99/mo
No
Make
1,000 operations/month
Operations/credits (most actions = 1 credit)
Core (exact USD price not published on Make’s own pricing page at time of review)
No
n8n
Community Edition, no published usage cap, self-hosted only
Workflow executions (cloud) or free (self-hosted)
Starter cloud, €20/mo
Yes (Community Edition, via GitHub)
Short Verdict
Zapier is the easiest to start with and has the deepest library of app integrations, but its per-task billing gets expensive fast once a workflow runs often. Make is cheaper per action for complex, branching automations and gives you a visual canvas that shows the whole flow at once, though its published pricing page is less transparent about exact dollar costs. n8n is the pick if you want to self-host for free, need on-premise data control, or want to write custom JavaScript/Python logic directly inside a node — its cloud plans are also the most affordable of the three on a pure price basis, but the richest developer features (custom nodes, tracing) are self-hosted only.
What Each Tool Is
Zapier connects over 7,000 apps through pre-built “Zaps”: a trigger in one app sets off one or more actions in others. It’s built for speed of setup rather than visual complexity — most Zaps are a simple top-to-bottom list of steps.
Make uses a node-based visual canvas where you drag modules onto a board and connect them with lines, including branches, loops, and routers that Zapier’s linear builder doesn’t handle as naturally. It bills in “operations” (credits) rather than flat tasks.
n8n is open-source automation software you can self-host for free (the Community Edition, distributed on GitHub) or run on n8n’s own cloud. It supports writing custom JavaScript or Python directly inside a workflow node, which makes it the most developer-oriented of the three.
Pricing Breakdown
Zapier: Free (100 tasks/mo, 1 user, two-step Zaps only); Professional from $19.99/mo with task tiers up to 2 million/month, multi-step Zaps, premium apps, and webhooks; Team from $69/mo for up to 25 users with a shared workspace and SSO; Enterprise is custom-priced with unlimited users. Annual billing saves roughly a third off the monthly rate.
Make: Free gives 1,000 operations/month, 1 MB of data storage, and 1 data store. Paid tiers are named Core, Pro, Teams, and Enterprise and are billed by operations purchased per month, with extra credits available as auto-top-ups on Core/Pro/Teams. Make’s own pricing page does not display a flat USD figure per tier without selecting an operations volume first, so treat any specific dollar number you see elsewhere as an estimate tied to a particular credit tier rather than a fixed plan price.
n8n: Community Edition is free and self-hosted, with no published execution cap, but you run and maintain the server yourself. Cloud Starter is €20/mo for 2,500 executions/month with a 5-minute max execution time; Cloud Pro is €50/mo for 10,000 executions/month with a 40-minute max execution time and more Assistant AI credits. Business (€667/mo) is self-hosted only at time of review, with the cloud version on a waitlist. Enterprise is custom, available on cloud or self-hosted.
Pros and Cons
Zapier
✅ Largest app library and fastest learning curve
✅ Built-in AI Copilot and AI troubleshooting on every paid plan
❌ Task-based billing scales poorly for high-volume or frequently-polling workflows
❌ No self-hosting option
Make
✅ Visual canvas handles branching, loops, and routers more naturally than a linear builder
✅ Operations-based billing can be cheaper than Zapier’s task billing for multi-step scenarios
❌ Pricing page doesn’t show plain USD figures without picking a credit volume first
❌ No self-hosting option
n8n
✅ Free, self-hosted Community Edition with no vendor lock-in
✅ Native support for custom JavaScript/Python code inside workflow nodes
❌ Richest features (custom nodes, LangSmith/OpenTelemetry tracing, bash scripts) are self-hosted only, not on the cloud plans
❌ Self-hosting means you own the uptime, updates, and security patching
Who It’s a Good Fit For
Choose Zapier if you want the fastest setup, need a long-tail app integration that only Zapier supports, and don’t mind paying a premium for that convenience.
Choose Make if your automations branch, loop, or need a visual map of the whole process, and you’re comfortable working out costs from an operations-based model rather than a flat monthly fee.
Choose n8n if you have the technical capacity to self-host (or don’t mind the cloud plan’s self-hosted-only advanced features), want to write custom code inside your automations, or need to keep workflow data on your own infrastructure for compliance reasons.
Who Should Look Elsewhere
If you need guaranteed flat monthly pricing with no credit or task math at all, all three platforms require some comfort with usage-based billing — budget-sensitive teams should run a test workflow on each free tier before committing to a paid plan, since real-world costs depend heavily on how many steps each automation runs and how often it triggers.
Bottom Line
There’s no single winner here — Zapier wins on integration breadth and ease of use, Make wins on visual control for complex logic, and n8n wins on cost control and openness for anyone willing to self-host. Start with each tool’s free tier on your actual use case before paying for any of them; the billing models are different enough that a workflow cheap on one platform can be expensive on another.
FAQ
Is n8n really free? The self-hosted Community Edition is free, but you pay for the server it runs on and the time to maintain it. n8n’s own cloud plans start at €20/month and are not free.
Which tool has the most app integrations? Zapier has the largest published app library by a wide margin, which matters most if you need a niche or less common app connected.
Can I switch between these platforms later? Not automatically — each platform uses its own workflow format, so moving from one to another means manually rebuilding automations rather than importing them directly.
Do any of these support AI features? Yes. Zapier includes an AI Copilot and AI-assisted troubleshooting on paid plans; n8n’s cloud plans include monthly AI Assistant credits (self-hosted use relies on your own API key); Make also markets AI agent capabilities within its automation scenarios.
Google Workspace and Microsoft 365 are the two suites almost every small and mid-size business ends up choosing between for email, documents, storage, and meetings. Both have reshaped their lineups around built-in AI in 2026 – but they’ve gone about it very differently, and that difference shows up directly in the price you pay per seat. Here’s how the current plans, storage, and AI inclusion actually compare, based on each vendor’s own pricing pages.
At a Glance
Category
Google Workspace
Microsoft 365 Business
Entry price (annual commitment)
$7/user/mo (Business Starter)
$7.00/user/mo (Business Basic, with Teams)
Entry-tier storage
30 GB pooled per user
1 TB per user + 100 GB mailbox
Built-in AI assistant
Gemini, included on every tier (limited on Starter)
Copilot, bundled into specific “with Copilot” SKUs at a higher price
Top business tier
Business Plus – $22/user/mo, 5 TB
Business Premium with Copilot – $32/user/mo, 1 TB + 1.5 TB archive mailbox
Best for
Teams that want AI and generous storage bundled in cheaply
Teams already standardized on Windows, Outlook, and Microsoft security tooling
Short Verdict
If your team is AI-curious and storage-hungry on a budget, Google Workspace gives you more for less – Gemini is included at every tier, and even the mid-tier Business Standard plan jumps to 2 TB of pooled storage per user. Microsoft 365 is the better fit if you’re already locked into Outlook, Teams, and Windows device management, and you’re willing to pay a premium to bundle Copilot in – but Copilot’s pricing is layered and easy to misread, so budget carefully before you commit.
What It Is
Google Workspace bundles Gmail, Calendar, Drive, Docs/Sheets/Slides, Meet, and Chat under one admin console, with Gemini woven into the apps rather than sold as a separate product. Microsoft 365 bundles Outlook, OneDrive, Word/Excel/PowerPoint, Teams, and Exchange-hosted email, with Copilot available either bundled into specific SKUs or as an add-on for other tiers. Both suites pool storage per user, both offer admin and security controls scaled to plan tier, and both are sold on monthly or annual-commitment billing (annual commitment is cheaper per seat in both cases).
Pricing Breakdown
Plan
Price per user/mo (annual commitment)
Price per user/mo (flexible/monthly)
Storage
Google Workspace Business Starter
$7.00
$8.40
30 GB pooled
Google Workspace Business Standard
$14.00
$16.80
2 TB pooled, full Gemini
Google Workspace Business Plus
$22.00
$26.40
5 TB pooled, full Gemini
Google Workspace Enterprise
Contact sales
Contact sales
5 TB+, expandable
Microsoft 365 Business Basic
$7.00 (with Teams) / $5.40 (no Teams)
Higher month-to-month rate applies
1 TB + 100 GB mailbox, 50 GB archive
Microsoft 365 Business Standard with Copilot
$23.50 (with Teams) / $20.30 (no Teams)
Higher month-to-month rate applies
1 TB + 100 GB mailbox
Microsoft 365 Business Premium with Copilot
$32.00 (with Teams) / $28.80 (no Teams)
Higher month-to-month rate applies
1 TB + 1.5 TB archive mailbox
One pricing quirk worth flagging: Microsoft currently runs a promotion dropping its standalone Copilot add-on from $21 to $18 per user/month between July and December 2026 for existing eligible customers on other plans – that’s separate from the “with Copilot” bundled SKUs above, and it’s worth confirming which path applies before you buy, since Microsoft’s packaging around Copilot has changed more than once in the last two years.
Pros
Google Workspace: Gemini is included rather than a paid add-on from Business Standard up; storage jumps are generous (2 TB, then 5 TB); simpler, flatter pricing with no separate AI SKU to track.
Microsoft 365: Deeper enterprise security and compliance tooling even at the Business tier; tightest fit for organizations already standardized on Windows, Active Directory/Entra ID, and Outlook; Teams is a stronger fit for large, structured meetings and webinars.
Cons
Google Workspace: Business Starter’s 30 GB pooled storage is thin for teams that share large files; fewer enterprise-grade compliance add-ons than Microsoft at equivalent price points.
Microsoft 365: Copilot pricing and packaging is genuinely confusing – bundled-in-SKU vs. stand-alone add-on vs. promotional pricing can all apply differently depending on your existing plan; entry-tier Business Basic lacks the desktop versions of Word/Excel/PowerPoint (web and mobile only).
Who It’s a Good Fit For / Who Should Look Elsewhere
Good fit for Google Workspace: startups and small teams that want AI assistance included without an extra line item, teams that collaborate primarily in-browser, and anyone prioritizing cheap, generous storage. Good fit for Microsoft 365: businesses already running Windows/Active Directory, teams that need desktop Office apps and deep Exchange/Outlook features, and organizations with compliance requirements Microsoft’s security stack already satisfies. Look elsewhere if: you need only a handful of the apps in either bundle – in that case, standalone tools (a dedicated video app, a dedicated file-sharing service) can cost less than a full suite seat.
Bottom Line
Dollar for dollar, Google Workspace currently bundles more storage and AI into its stated price than Microsoft 365 does – but Microsoft’s tooling is harder to replace once an organization has built its identity and security stack around it. For a new team choosing from scratch with no prior lock-in, Google Workspace’s simpler, AI-inclusive pricing is the easier sell. For a team already standardized on Windows and Outlook, Microsoft 365 Business Premium is still the more defensible choice despite the higher price per seat.
FAQ
Is Gemini really included free with Google Workspace? Yes, on Business Standard and above Gemini is fully included in the subscription price with no separate add-on; Business Starter gets limited Gemini access.
Is Copilot included in Microsoft 365 Business plans? Only in the specific “with Copilot” SKUs of Business Standard and Business Premium shown above. Other Microsoft 365 plans require Copilot as a separate paid add-on.
Which suite gives more storage per user? Google Workspace, once you’re past the entry tier – Business Standard jumps to 2 TB pooled per user versus Microsoft 365’s 1 TB across its Business plans.
Can a company run both suites at once? Yes, and some do during migrations or for specific teams, but running both long-term doubles licensing cost and complicates admin and identity management, so most businesses standardize on one.
Which is cheaper for a 10-person team? On entry tiers they’re close ($700/mo for Google Business Starter vs. $700/mo for Microsoft Business Basic with Teams, both annual commitment). The gap widens at the mid-tier, where Google Business Standard ($1,400/mo) undercuts Microsoft Business Standard with Copilot ($2,350/mo) because Microsoft’s mid-tier price already has Copilot built in.
Scheduling links have quietly replaced “what time works for you?” email threads for most teams. Calendly is still the household name, Cal.com pitches itself as the open, customizable alternative, and SavvyCal has built a loyal following among people who find the whole category a little impersonal. Here’s how the three actually compare on price and features as of late 2026.
At a Glance
Tool
Starting paid price
Free plan
Self-hosted option
Best for
Calendly
$10/seat/mo (Standard)
Yes — 1 event type, 1 calendar
No
Sales and CS teams needing routing and CRM sync
Cal.com
$12/user/mo billed yearly (Teams)
Yes — unlimited event types, 1 user
Yes (open-source, self-hosted or Docker)
Developers and teams who want control over data and code
SavvyCal
$12/user/mo (Basic), $10 billed yearly
Limited — can’t take bookings without a paid plan
No
People who want a more personal, overlay-style booking page
Short Verdict
Calendly remains the safest default for sales and customer-facing teams because of its routing forms, Salesforce/HubSpot integrations, and sheer ubiquity — people already know how to use it. Cal.com is the best pick if you want an actually usable free plan or the option to self-host and customize the booking flow in code. SavvyCal is worth the premium if you care about the booking experience itself: its signature feature lets you overlay your availability on top of the other person’s calendar link, which Calendly and Cal.com don’t offer.
What Each Tool Is
Calendly is the market-leading scheduling platform, built for individuals up through enterprise sales orgs. Its strength is breadth: routing forms that qualify a lead before showing them a calendar, round-robin distribution across a team, and native integrations with HubSpot, Marketo, Salesforce, and Microsoft Dynamics depending on plan tier.
Cal.com is an open-source scheduling platform available as a hosted cloud product or self-hosted via Docker from its GitHub repository. Its free plan is unusually generous — unlimited event types and calendar connections for one user — and paid tiers add team scheduling, routing forms, and enterprise compliance certifications (SOC 2, HIPAA, ISO 27001) on the Organizations tier.
SavvyCal focuses on the booking experience rather than sales-pipeline features. Its core differentiator, “overlay,” lets you send a link that shows your own availability directly on top of the recipient’s calendar when you both use SavvyCal-compatible calendars, making back-and-forth scheduling feel less transactional.
Unlimited links, round robin/collective/group modes, API/webhooks, AI assistant (MCP)
SavvyCal Premium
$20/user/mo ($17 billed yearly)
Adds delegated access, custom domains, no SavvyCal branding, Stripe payments
Calendly’s page does not publish separate monthly-billed rates for Standard and Teams beyond the per-seat figures shown, and add-on pricing for its Notetaker and “Callie” AI assistant is not disclosed publicly. Cal.com’s $12 and $28 figures are the yearly-billed per-user rates; monthly-billed pricing isn’t listed separately on its pricing page. SavvyCal offers a 30-day money-back guarantee instead of a self-serve free trial, and requires every host on a team subscription to be on the same plan tier.
Pros and Cons
Calendly
Widest name recognition — recipients already trust the link
Strong CRM and marketing-automation integrations at the Teams/Enterprise tiers
Free plan is limited to one event type, which pushes most real use to paid tiers
Enterprise pricing requires a 50-seat minimum and a six-figure-adjacent annual commitment
Cal.com
The only one of the three with a genuinely usable free plan (unlimited event types for one user)
Self-hosting option appeals to privacy- and compliance-conscious teams
Open developer ecosystem with APIs, webhooks, and 100+ app integrations
Team and org tiers cost more per seat than Calendly’s equivalent tiers
SavvyCal
Overlay feature is a genuinely different (and more personal) booking experience
Includes API, webhooks, and AI assistant access even on its entry Basic plan
Free plan can’t actually take bookings, so it’s a demo tier, not a usable free product
Smaller integration ecosystem than Calendly or Cal.com
Who It’s a Good Fit For — and Who Should Look Elsewhere
Pick Calendly if you’re on a sales or customer success team that needs lead routing and deep CRM sync, and where the extra per-seat cost is justified by pipeline integrations. Pick Cal.com if you want the most generous free tier, need to self-host for compliance reasons, or want to customize the booking flow with code. Pick SavvyCal if you schedule a lot of external meetings one-on-one and want the process to feel less like filling out a form — but skip it if you need a free plan that can actually take bookings, or if you rely heavily on CRM integrations.
Bottom Line
There’s no universally “best” scheduling app here — the three have genuinely different priorities. Calendly sells breadth and brand recognition, Cal.com sells openness and a real free tier, and SavvyCal sells a better booking experience at a premium. Match the pick to what you actually need integrated, and don’t assume the biggest name is automatically the right one for a two-person team.
FAQ
Is Cal.com really free forever for one user? Yes — its Free plan includes unlimited event types and calendar connections for a single user, with no stated usage limits, though team features require a paid plan.
Can I self-host Cal.com instead of paying monthly? Yes, Cal.com is open-source and can be self-hosted via Docker using its public GitHub repository, which avoids per-seat fees but shifts hosting and maintenance to you.
Does SavvyCal have a usable free plan? Not for taking real bookings. The free tier lets you connect calendars and set up links, but recipients can’t actually book through them without a paid plan — functionally a trial rather than a free product.
Which tool integrates best with Salesforce? Calendly’s Teams and Enterprise tiers include direct Salesforce integration with lookup fields at the Enterprise level; Cal.com also lists Salesforce sync on its Free plan’s integration list. SavvyCal’s integration roster is smaller and doesn’t prominently feature Salesforce.
Individuals and teams who want one flexible workspace for notes, docs, wikis, and lightweight project tracking
Free plan
Yes – unlimited pages/blocks for solo use; block limit applies once a workspace has 2+ members
Entry paid plan
Plus, $10 per member/month (billed monthly; Notion advertises up to 20% off with annual billing but does not publish the exact annual per-seat rate)
Top plan
Business, $20 per member/month; Enterprise is custom-priced
File upload limit
5 MB per file on Free; 5 GB per file on Plus, Business, and Enterprise
Page history
7 days (Free), 30 days (Plus), 90 days (Business), custom (Enterprise)
AI features
Limited trial of Notion Agent on Free/Plus; full Notion Agent, AI Meeting Notes, and Enterprise Search (beta) on Business; Custom Agents are billed separately via Notion credits
Pricing and limits verified against Notion’s official pricing page as of late 2026; always check notion.com/pricing before buying, since SaaS pricing changes without much notice.
Short Verdict
Notion remains one of the most flexible workspace tools available, and for a single user its free plan is genuinely generous – unlimited pages and blocks, with no seat-based nag screens. The calculus changes the moment a second person joins the workspace: Free workspaces with 2+ members hit a block limit, and most of the features that make Notion useful for teams – version history beyond seven days, larger file uploads, and any serious AI assistance – sit behind the $10/month Plus plan or the $20/month Business plan. For a solo note-taker, stay on Free. For a small team that shares a wiki or project tracker, Plus is close to mandatory rather than optional.
What It Is
Notion is an all-in-one workspace that combines notes, documents, wikis, databases, and lightweight project management inside a single block-based editor. Instead of separate apps for docs, spreadsheets, and task boards, Notion lets you build all three from the same primitive – a “block” – and link them together. A page can embed a database that renders as a table, a kanban board, a calendar, or a gallery, all pulling from the same underlying data. That flexibility is Notion’s main selling point and also its main learning curve: it is closer to a construction kit than a ready-made app, so new users often spend their first week building templates rather than using them.
Over the past two years Notion has layered AI features on top of that base: a “Notion Agent” that can search and act across a workspace, AI-generated meeting notes, and “Custom Agents” that run on a separate credit-based pricing model ($10 per 1,000 Notion credits after a free trial). These sit on top of the core per-seat subscription rather than replacing it.
Pricing Breakdown
Plan
Price (per member/month)
Who it’s for
Key features added
Free
$0
Individuals
Unlimited blocks for solo use (block limit applies with 2+ members), 7-day page history, 5 MB file uploads, limited AI trial
Plus
$10
Small teams
Unlimited blocks for the whole team, 30-day page history, 5 GB file uploads, basic page analytics
Business
$20
Growing companies (Notion’s “Recommended” tier)
Private teamspaces, SAML SSO, granular database permissions, full Notion Agent + AI Meeting Notes + Enterprise Search (beta), advanced page analytics, 90-day history
Enterprise
Custom
Large organizations
SCIM provisioning, audit log, domain management, admin content search, zero data retention with LLM providers, custom page history
Guests can be invited to specific pages at no extra cost on any plan; they only see what they’re explicitly given access to. Custom AI Agents run on a separate, usage-based credit system layered on top of whichever seat plan you’re on, so heavy AI automation use can add meaningfully to the per-seat price above.
Pros
Extremely flexible block-based editor that can replace docs, wikis, and simple project trackers in one tool
Free plan has no page or block limit for a solo user, which is rare among competitors
Databases with multiple views (table, board, calendar, gallery, timeline) from the same dataset
Guests can be added to specific pages for free, useful for freelancers and client collaboration
Large template ecosystem, both official and community-built
Cons
Block limit kicks in immediately for any workspace with 2 or more members on the Free plan
Meaningful AI features (full Notion Agent, Enterprise Search) are gated behind the $20/month Business plan
Steeper learning curve than purpose-built apps – building a usable system takes real setup time
Offline support and raw performance on very large databases lag behind dedicated note or database tools
Custom AI Agents use a separate credit-based charge on top of the seat price, which can make AI-heavy usage harder to budget for
Who It’s a Good Fit For
Solo users who want one place for notes, planning, and light databases will find the Free plan hard to beat. Small teams of 2–10 people who need a shared wiki, light project tracking, and don’t require enterprise security controls are well served by Plus. Companies that need SSO, granular permissions, or workspace-wide AI search should budget for Business.
Who Should Look Elsewhere
Teams that mainly need structured task/sprint management with heavier automation (dependencies, time tracking, Gantt views out of the box) are often better served by a dedicated project-management tool. Teams that need robust offline access or handle very large databases may hit friction that a purpose-built database tool wouldn’t have. If AI automation is the primary goal rather than a nice-to-have, the separate credit-based pricing for Custom Agents is worth modeling carefully before committing.
Bottom Line
Notion earns its popularity: the free tier is one of the most usable in the category for individuals, and Plus at $10/month is a reasonable price for a small team that outgrows solo block limits. Business at $20/month is where the real AI and security features live, so teams evaluating Notion for AI-assisted search or SSO should budget at that tier rather than Plus. Shop the official pricing page directly, since Notion periodically adjusts limits and AI feature gating.
FAQ
Is Notion really free for personal use? Yes – a single-user Notion workspace has no page or block limit on the Free plan. The block limit only applies once a workspace has two or more members.
Do I need Plus or Business to use Notion AI? Free and Plus include only a limited trial of Notion Agent. The full Notion Agent, AI Meeting Notes, and Enterprise Search (beta) are Business-plan features.
Can I add external collaborators without paying for extra seats? Yes. Guests can be invited to specific pages for free on any plan; they only see what they’ve been explicitly granted access to.
How much does annual billing save? Notion’s pricing page advertises “save up to 20% with yearly” billing but does not publish the exact discounted per-seat rate on the page, so check the live checkout flow for the current annual price before committing.
Go doesn’t get the kind of chip-launch coverage that Nvidia or AWS silicon gets, but it quietly underpins a huge share of the infrastructure those chips run on. Kubernetes, Docker, Terraform, Prometheus, and etcd are all written in Go, and that’s not a coincidence — the language was designed from the start around two things cloud infrastructure needs constantly: handling many things happening at once, and staying simple enough for large teams to maintain. Here’s what’s actually in the language, including the 2022 addition of generics, and why so much of the infrastructure layer keeps choosing it.
At a Glance
Feature
What It Does
Added
Goroutines
Lightweight concurrent functions multiplexed onto OS threads
Go 1.0 (2012)
Channels
Typed pipes for goroutines to communicate and synchronize
Go 1.0 (2012)
Generics (type parameters)
Functions/types that work across multiple types without losing type safety
Go 1.18 (March 2022)
Built-in fuzzing
Automated test-input generation via go test -fuzz
Go 1.18 (March 2022)
Goroutines: Concurrency Without the Thread Management
A goroutine is, in Go’s own documentation, “a function executing concurrently with other goroutines in the same address space.” The Go team deliberately avoided calling them threads, because goroutines are much cheaper: each one starts with a small stack that grows and shrinks as needed, and the Go runtime multiplexes many goroutines onto a much smaller number of OS threads. Starting one is as simple as putting the keyword go in front of a function call — the goroutine runs independently, and the caller doesn’t wait for it to finish. That cost difference is a big part of why Go code can comfortably run tens of thousands of concurrent operations — incoming requests, open connections, background jobs — that would be expensive to run as that many OS threads in other languages.
Channels: How Goroutines Actually Talk to Each Other
Goroutines aren’t very useful on their own if they can’t coordinate, and that’s what channels are for. A channel, created with make(chan T), is a typed conduit that one goroutine can send values into and another can receive values from. An unbuffered channel blocks the sender until a receiver is ready, which gives you communication and synchronization in a single operation; a buffered channel (make(chan T, N)) lets a sender proceed until the buffer fills. Go’s own documentation sums up the resulting style this way: “Do not communicate by sharing memory; instead, share memory by communicating.” Rather than multiple goroutines fighting over a shared variable with locks, they pass values through channels instead.
A simple worker-pool pattern, a staple of Go network and infrastructure code, looks like this:
package main
import "fmt"
func worker(id int, jobs <-chan int, results chan<- int) {
for j := range jobs {
results <- j * 2
}
}
func main() {
jobs := make(chan int, 5)
results := make(chan int, 5)
for w := 1; w <= 3; w++ {
go worker(w, jobs, results)
}
for j := 1; j <= 5; j++ {
jobs <- j
}
close(jobs)
for a := 1; a <= 5; a++ {
fmt.Println(<-results)
}
}
Here, three worker goroutines all read from the same jobs channel; whichever one is free next picks up the next job, and each result is sent back on a separate channel for the main goroutine to collect. Patterns like this — a fixed pool of goroutines draining a shared channel — show up constantly in Go services that need to process many requests concurrently without spawning an unbounded number of goroutines.
Generics: Go 1.18’s Biggest Change
For its first decade, Go had no way to write a function or type that worked across multiple types without either duplicating code or falling back to interface{} and losing type safety. Go 1.18, released in March 2022, fixed that by adding type parameters. A function or type declaration can now take type parameters in square brackets, and interfaces can define “type constraints” — sets of types a type parameter is allowed to be, rather than just sets of methods. Go 1.18 also introduced two new predeclared identifiers: any, an alias for interface{}, and comparable, the set of types that support == and !=. The change was designed to be fully backward-compatible — existing Go code didn’t need to change — though the Go team cautioned at the time that generic code “has not had much production testing” and recommended appropriate caution deploying it. The same release shipped Go’s built-in fuzz testing support (go test -fuzz), a register-based calling convention extended to more CPU architectures for a roughly 10% performance gain on some platforms, and a revised append growth strategy, among other runtime changes.
Why Cloud Infrastructure Keeps Choosing Go
None of this explains, by itself, why Go became the default language for so much cloud-native tooling — Kubernetes, Docker, Terraform, Prometheus, and etcd are all implemented in Go. But the companies that have published their own reasons for adopting it, via Go’s official case studies, point to a consistent pattern. Dropbox moved performance-critical backends off Python for, in its words, “better concurrency support and faster execution speed.” Monzo called Go “a perfect language for creating microservice architectures.” Stream said Go’s “fast performance, solid support for concurrency” helped it power real-time feeds and chat for more than 500 million users. CockroachDB’s team cited “performance benefits, garbage collection, and low barrier to entry.” Netflix picked Go in part because it offers lower latency than Java while being more approachable than C, and because it can comfortably handle tens of thousands of simultaneous connections — precisely the shape of problem infrastructure tools like a container orchestrator or a reverse proxy have to solve. Compiled, statically-linked Go binaries also deploy as a single file with no separate runtime to install, which matters a great deal for software that has to run identically across thousands of servers or inside minimal containers.
Trade-offs
Goroutines are cheap, but cheap doesn’t mean free — spawning millions of them without a limiting pattern like a worker pool or semaphore can still exhaust memory.
Generics closed a real gap, but Go’s own 1.18 release notes flagged real limitations (no type declarations inside generic functions, no field access on type-parameter values) that shaped how cautiously teams adopted them early on.
Go’s simplicity is also a constraint: the language and standard library deliberately omit features, like exceptions or certain forms of operator overloading, that some teams coming from other languages miss.
Being the language cloud-native tooling is written in doesn’t mean every team building on Kubernetes or Terraform needs to write Go themselves — most only interact with those tools’ APIs or CLIs.
Bottom Line
Go’s core pitch hasn’t changed much since 2012 — goroutines and channels make concurrency manageable, and the language stays deliberately small — but generics in 2022 closed one of its longest-standing gaps without breaking that simplicity. Combined with fast compilation and single-binary deployment, that combination is why so much of the software managing cloud infrastructure itself, rather than running on top of it, continues to be written in Go.
FAQ
What’s the difference between a goroutine and a thread? A goroutine is managed entirely by the Go runtime, not the operating system. It starts with a small, growable stack, and many goroutines are multiplexed onto a much smaller number of OS threads, which makes goroutines far cheaper to create than OS threads.
Do I need a channel every time I use a goroutine? No, but without some way to communicate or synchronize — a channel, a sync.WaitGroup, or similar — there’s no way to know when a goroutine has finished or to safely exchange data with it.
When were generics added to Go? Go 1.18, released in March 2022, added type parameters (generics) to the language, along with the any and comparable predeclared identifiers.
Why are so many cloud infrastructure tools written in Go? Companies that have published their reasoning cite Go’s concurrency model, fast execution, and simple deployment as a single static binary as recurring reasons, according to Go’s own published case studies.
IBM’s broader Power11 and watsonx push covers enterprise AI generally. But IBM’s mainframe line has its own, much narrower AI story: a processor called Telum II, built into the z17 mainframe, that puts an AI accelerator on the same die as the processor cores running a bank’s core transaction workload. It’s a fundamentally different approach to AI acceleration than the GPU clusters behind most generative-AI infrastructure — and it exists for a specific reason: scoring transactions for fraud in real time, without sending data anywhere else.
At a Glance
Item
Detail
Processor
Telum II — 8 cores, 5.5GHz, built on Samsung 5nm process
Mainframe
IBM z17 — announced April 8, 2025; generally available June 18, 2025
On-chip AI accelerator
Up to 24 TOPS per chip; up to 192 TOPS per fully configured 8-chip drawer
Companion accelerator
IBM Spyre Accelerator — 32 AI cores per PCIe card, stackable
IBM’s claimed throughput
More than 450 billion inference operations/day (IBM-reported, ~50% more than z16)
IBM’s claimed latency
1 millisecond response time (IBM-reported internal/extrapolated benchmark)
What Telum II Actually Is
Telum II is IBM’s latest mainframe processor, introduced alongside the z17 system. IBM describes it as built on Samsung’s 5-nanometer process with eight high-performance cores running at 5.5GHz. Cache capacity grew roughly 40% over the prior generation, reaching a virtual L3 cache of 360MB and a virtual L4 cache of 2.88GB shared across the system — large on-chip caches that matter because mainframe transaction workloads are extremely cache-sensitive. Telum II also adds a dedicated data processing unit (DPU) to handle I/O acceleration, offloading that work from the main cores.
The On-Chip AI Accelerator
The part that matters here is Telum II’s integrated AI accelerator — a block of matrix-math hardware sitting on the same die as the processor cores, not a separate card reached over a bus. IBM says each accelerator’s compute capacity is roughly 4x higher than the previous Telum generation, reaching 24 trillion operations per second (TOPS), and added INT8 precision support, which IBM says improves efficiency and enables newer model types. In a fully populated processor drawer, any of the system’s cores can dispatch work to any of the drawer’s eight AI accelerators, which IBM says improves load balancing — and across all eight, IBM cites up to 192 TOPS available when fully configured.
Why This Is Different From GPU-Based AI Acceleration
A GPU cluster is a separate pool of compute that data has to travel to — over PCIe, NVLink, or a network fabric — before and after inference. That round trip adds latency and is usually fine for workloads like training large models or running chatbots, where milliseconds of network time don’t matter. It’s a poor fit for scoring a credit card swipe before the transaction is approved, where the system has a few milliseconds, total, to decide. IBM’s answer is to put a comparatively much smaller AI accelerator directly on the processor die, right next to the cores already executing the transaction. There’s no separate card, no PCIe hop, and no network call: the model runs in the same silicon, close to the same memory, as the business logic it’s scoring. IBM frames the payoff this way in its own benchmarking: more than 450 billion inference operations per day on z17, a claimed 50% increase over z16, with a 1 millisecond response time — figures IBM describes as extrapolated from internal tests using a synthetic credit-card fraud detection model, so they should be read as IBM’s own reported benchmark rather than an independently audited figure.
IBM Spyre: A Second, Complementary Accelerator
Not every AI workload fits on Telum II’s on-chip accelerator, which is sized for high-volume, low-latency scoring rather than large generative models. For that, IBM pairs the mainframe with the IBM Spyre Accelerator, a separate PCIe card containing 32 AI accelerator cores built on an architecture similar to Telum II’s on-chip engine. Multiple Spyre cards can be attached to a single z17 or LinuxONE system, and IBM positions it for generative-AI and larger-model workloads that complement, rather than replace, the real-time scoring done on-chip.
The Fraud Detection Use Case
IBM’s flagship example for Telum II is an ensemble approach to fraud and compliance. A traditional, relatively small neural network running on the on-chip accelerator gives an initial risk score for a transaction in real time; that score can then be combined with a large language model (typically run elsewhere, such as on Spyre) to improve accuracy without slowing down the initial decision. IBM describes applying the same ensemble pattern to detecting suspicious financial activity and supporting regulatory compliance work — cases where the first-pass model has to run inline with the transaction, and a heavier model can refine the result afterward.
On-Chip vs Spyre vs a Typical GPU Accelerator
Accelerator
Location
Connects Via
Best For
Latency Profile
Telum II on-chip
Same die as CPU cores
Integrated — no external link
Small models, real-time transaction scoring
Sub-millisecond, in-line with transaction
IBM Spyre
Separate card
PCIe
Larger models, generative AI
Low, but higher than on-chip
Typical GPU accelerator
Separate card or node
PCIe or network fabric (NVLink/InfiniBand/Ethernet)
Training, large-scale inference
Higher — depends on network hop
Trade-offs
The on-chip accelerator’s 24 TOPS per chip is tiny next to a modern training GPU, but it isn’t trying to compete on raw throughput — it’s optimized to never leave the transaction path.
IBM’s headline performance figures (450 billion inferences/day, 1ms latency) come from IBM’s own internal and extrapolated benchmarks, not third-party testing, and should be treated as vendor-reported.
Running AI on a mainframe only makes sense for organizations already running core transaction workloads on IBM Z; it isn’t a general-purpose AI platform the way a GPU cloud is.
Spyre adds generative-AI capacity, but it’s a separate card with different latency characteristics than the on-chip accelerator — the two aren’t interchangeable.
Bottom Line
Telum II and the z17 represent a narrower, more specific bet than GPU clusters: instead of moving data to a big pool of accelerators, IBM moved a small AI accelerator onto the same chip as the workload it needs to score. For something like real-time fraud detection, where the entire decision window is a few milliseconds, that architecture has a real structural advantage over any design that requires a PCIe or network hop — even though the raw compute numbers look small next to a data-center GPU.
FAQ
Is Telum II a GPU? No. It’s a general-purpose mainframe CPU with an integrated AI accelerator block on the same die, designed for inline inference on structured transaction data rather than the large matrix workloads GPUs handle.
How fast is the z17’s AI accelerator really? IBM states up to 24 TOPS per Telum II chip and up to 192 TOPS across a fully configured 8-chip processor drawer. For context, that’s a small fraction of a modern data-center GPU’s throughput — it’s built for latency on small models, not raw volume.
What’s the difference between Telum II’s accelerator and IBM Spyre? Telum II’s accelerator is built into the processor die for the fastest possible, real-time inference on the transaction path. Spyre is a separate PCIe card with 32 AI cores aimed at larger generative-AI workloads that don’t need to run inline with a single transaction.
Are IBM’s performance claims independently verified? No. IBM’s published figures — more than 450 billion inferences/day and 1ms latency — come from IBM’s own internal and extrapolated benchmarks using a synthetic fraud-detection model, and IBM itself notes results may vary.
AWS’s custom Trainium and Inferentia chips get a lot of attention as the hardware story behind Amazon’s AI push, but almost no developer touches that silicon directly. Most people building AI applications on AWS work through two higher-level services sitting on top of it: Amazon Bedrock and Amazon SageMaker. They solve different problems, and AWS itself publishes a decision guide explaining when to use which. Here’s what each one actually does.
At a Glance
Service
What It Is
Best For
Expertise Needed
Amazon Bedrock
Fully managed, serverless platform for building AI apps and agents on pre-trained foundation models
Prompting, retrieval-augmented generation, light model customization
Limited ML expertise
Amazon SageMaker AI
Platform for training, customizing, and deploying ML and foundation models with full infrastructure control
Custom training, fine-tuning, reinforcement learning, production ML pipelines
Deeper ML/infrastructure expertise
What Amazon Bedrock Actually Offers
AWS describes Bedrock as “a fully managed, serverless platform to build, run, and operate AI applications and agents at production scale.” In practice, Bedrock gives developers API access to more than 100 foundation models from multiple providers — including Amazon’s own Nova models, Anthropic’s Claude, and models from DeepSeek, Moonshot AI, MiniMax, OpenAI, and xAI — without provisioning any compute instances themselves. Bedrock exposes several API styles through its bedrock-runtime endpoint, including a Converse API, a Messages API, and OpenAI-compatible Responses and Chat Completions APIs, so teams can call different model providers through a largely consistent interface. AWS also builds customization directly into Bedrock: fine-tuning, continued pre-training, and model distillation, along with features like cross-Region inference for throughput and a built-in web search tool for grounding certain models in current information. AWS’s own guidance is direct about who this is for: “Amazon Bedrock is particularly useful if you have limited machine learning (ML) expertise or resources.”
What Amazon SageMaker Actually Offers
SageMaker sits a layer lower. AWS now positions the SageMaker family as “the center for all your data, analytics, and AI,” combining several components: SageMaker AI (the renamed core service) for training, customizing, and deploying models on managed infrastructure; SageMaker HyperPod for distributed training and orchestration across thousands of accelerators; SageMaker JumpStart, a catalog of pre-built and foundation models that can be deployed or further trained; SageMaker Unified Studio, a single development environment with a serverless notebook, SQL editor, and generative-AI app-building tools; and SageMaker Catalog and Lakehouse, which handle data governance and unified access to S3, Redshift, and other sources. Where Bedrock mostly abstracts infrastructure away, AWS recommends SageMaker AI specifically “when you need to access the container or orchestration layer to directly manage cost-latency-throughput and other tradeoffs” — in other words, when a team needs to actually control how and where a model runs.
How They Differ, Side by Side
Category
Amazon Bedrock
Amazon SageMaker AI
Model access
100+ pre-trained foundation models via API
JumpStart catalog of roughly 1,000 models, plus fully custom models
Customization
Automated fine-tuning, continued pre-training, distillation, custom model import
Serverless SFT/DPO, reinforcement learning (RLVR/RLAIF), full training jobs, HyperPod
Infrastructure
Serverless, no instances to manage
Serverless for light customization; full instance/endpoint/HyperPod control otherwise
Pricing model
Per-token, with Priority/Flex/Reserved tiers and batch discounts up to 50%
Per-token for serverless customization; usage-based compute pricing otherwise, with Savings Plans up to 64% off
Typical user
App teams with limited ML expertise
ML/infrastructure teams needing deep control
Where the Custom Silicon Actually Shows Up
This is where the chips re-enter the picture. AWS’s own architecture diagram for this comparison places “AI chips (Trainium, Graviton, NVIDIA GPUs)” at the base layer of the stack, with Bedrock and SageMaker both sitting above it as “models training and inferencing” services. In practice, the two expose that hardware very differently. SageMaker is explicit about it: AWS states that “SageMaker AI also supports cost-optimized hardware including AWS Trainium for training and AWS Inferentia for inference,” and customers choose instance types much as they would with EC2. Bedrock is serverless by design, so AWS does not publish which chips back a given model call — customers choose a model, not a chip. AWS does describe a common progression between the two: prototype with Bedrock using prompting and Knowledge Bases for retrieval-augmented generation, move to SageMaker AI’s serverless fine-tuning or reinforcement learning when prompting alone isn’t enough, and optionally deploy the resulting custom model back into Bedrock for serverless inference, or onto SageMaker endpoints or HyperPod for more granular control. Nova models customized on SageMaker, for example, can be imported directly into Bedrock.
Trade-offs
Bedrock trades control for speed: teams move faster but can’t choose the underlying instance type, chip, or container.
SageMaker trades simplicity for control: more powerful, but it requires a team that understands training jobs, instance types, and orchestration.
AWS’s “common path” framing — start on Bedrock, graduate to SageMaker — is AWS’s own recommendation, not a requirement; some teams skip straight to SageMaker, and others never leave Bedrock.
Neither service is useful without the AWS AI chip layer underneath, but only SageMaker lets customers choose which chip family runs their workload.
Bottom Line
Trainium and Inferentia are the hardware story, but Bedrock and SageMaker are the services most AWS customers actually touch. Bedrock is the fast path to a working generative-AI application with minimal ML overhead; SageMaker is the full-control platform for teams that need to own the training process, the hardware choice, and the deployment infrastructure. AWS’s own documentation treats them as complementary stages of the same pipeline rather than competitors — and that’s the most useful way to think about when to reach for each.
FAQ
Do I need to pick Bedrock or SageMaker, or can I use both? AWS explicitly designs them to work together. A common pattern is prototyping on Bedrock, moving to SageMaker AI for fine-tuning or reinforcement learning once prompting isn’t enough, and then deploying the resulting model either back into Bedrock or onto SageMaker endpoints/HyperPod.
Does Bedrock run on Trainium chips? AWS doesn’t publish per-model chip assignments for Bedrock, since it’s a serverless service. Trainium and Inferentia are explicitly named as supported hardware for SageMaker AI training and inference jobs, where customers choose the instance type directly.
What foundation models are available on Bedrock? AWS lists more than 100 models from providers including Amazon (Nova), Anthropic (Claude), DeepSeek, Moonshot AI, MiniMax, OpenAI, and xAI, accessible through a shared set of APIs.
Is SageMaker only for training models from scratch? No. SageMaker JumpStart provides a large catalog of pre-built and foundation models that can be deployed or further customized rather than trained from zero, alongside the option for fully custom training.
When Nvidia talks about AI infrastructure, the GPU gets most of the attention — but a cluster of thousands of GPUs is only as fast as the links between them. Nvidia’s networking stack, built around NVLink, InfiniBand, and the newer Spectrum-X Ethernet platform, is what turns racks of individual accelerators into a single, coordinated system. This piece looks at what each technology actually does, why interconnect bandwidth is now as important as raw compute for large training runs, and how Nvidia’s 2020 acquisition of Mellanox put all three technologies under one roof.
At a Glance
Technology
Scope
Typical Bandwidth
Primary Use
NVLink / NVLink-C2C
Chip-to-chip, GPU-to-GPU within a server or module
Up to 1,800 GB/s per GPU (Blackwell, 5th-gen NVLink)
Scale-up links inside a node (GPU-GPU, CPU-GPU)
NVLink Switch
Rack-scale, multi-node GPU fabric
130 TB/s aggregate per NVL72 domain (Blackwell)
Making 72 GPUs act as one accelerator
InfiniBand (Quantum-2)
Server-to-server, scale-out cluster fabric
400 Gb/s per port; 51.2 Tb/s per switch
Connecting thousands of GPU servers in dedicated AI/HPC clusters
Spectrum-X
Server-to-server, Ethernet-based AI fabric
Up to 1.6x stock Ethernet performance; scales to 128K GPUs (Nvidia claim)
Standards-based Ethernet for AI clouds
Why the Network Matters as Much as the GPU
Training a large model is a tightly synchronized job spread across hundreds or thousands of GPUs. At set intervals, every GPU has to exchange gradients or activations with many others before the next step can start — a pattern built on collective operations like all-reduce and all-to-all. If the network is slow or congested, GPUs sit idle waiting for data no matter how fast they can individually compute. That’s the practical reason Nvidia sells networking silicon alongside GPUs: a cluster’s effective throughput is capped by whichever is slower, compute or communication, and at the scale of a modern training cluster the network is frequently the binding constraint.
NVLink and NVLink-C2C: Wiring Chips and Servers Together
NVLink is Nvidia’s direct GPU-to-GPU interconnect, and it operates at a different layer from a traditional data-center network. Nvidia states that the 5th-generation NVLink used in Blackwell GPUs provides 1,800 GB/s of bidirectional bandwidth per GPU across 18 links — roughly double the prior Hopper generation’s 900 GB/s. Nvidia’s roadmap lists a 6th generation for its upcoming Vera Rubin platform at 3,000 GB/s per GPU across 36 links, though the company explicitly labels these as preliminary specifications that may change.
A related technology, NVLink-C2C, extends the same coherent, high-bandwidth connection down to the chip-to-chip level — for example, linking a Grace CPU to Blackwell GPUs inside a single “Superchip” module. Nvidia says NVLink-C2C can deliver up to 6x the energy efficiency and 3.5x the area efficiency of a PCIe Gen 6 physical layer. Through a licensing program called NVLink Fusion, Nvidia also opens this chip-to-chip link to partners who want to pair custom CPUs or ASICs with Nvidia GPUs in semi-custom designs.
NVLink Switch and the Rack-Scale Fabric
On its own, NVLink only connects the GPUs inside one server. NVLink Switch chips extend that same all-to-all connectivity across multiple servers in a rack. In Nvidia’s NVL72-class systems, NVLink Switches tie 72 Blackwell GPUs into a single non-blocking domain, with Nvidia citing 130 TB/s of aggregate GPU bandwidth inside that domain — letting the rack behave, from a software standpoint, like one very large accelerator rather than 72 separate ones.
InfiniBand: Nvidia’s Scale-Out Fabric for Supercomputing Clusters
Once a workload needs more GPUs than a single rack can hold, it moves from NVLink’s “scale-up” domain to a “scale-out” network connecting many servers — InfiniBand’s job. Nvidia’s current Quantum-2 platform runs each port at 400 Gb/s, with a single switch offering 64 such ports (or 128 ports at 200 Gb/s) for 51.2 Tb/s of aggregate bidirectional throughput and more than 66.5 billion packets per second. A key feature is in-network computing: Nvidia’s third-generation SHARP technology performs data aggregation and reduction operations inside the switch itself rather than making GPUs handle that work, which Nvidia says delivers up to 32x more AI acceleration power per switch than the prior generation. Nvidia states the platform can scale to more than a million 400 Gb/s nodes in a three-hop DragonFly+ topology.
Spectrum-X: Making Ethernet Behave Like a Supercomputer Network
InfiniBand has long been the default fabric for HPC and AI supercomputers, but most enterprise and cloud data centers run on Ethernet. Spectrum-X is Nvidia’s attempt to bring InfiniBand-like performance to standards-based Ethernet. The platform pairs Spectrum-X switches (the SN5000 and SN6000 series) with “SuperNICs” — network accelerators that handle RDMA over Converged Ethernet (RoCE) between GPU servers. Nvidia says Spectrum-X delivers up to 1.6x the network performance of off-the-shelf Ethernet, and a companion technology, Spectrum-XGS, is built to link multiple data centers together, with Nvidia citing 1.9x higher NCCL (GPU collective-communication) performance across sites. Nvidia also markets Spectrum-X Ethernet Photonics, using co-packaged optics the company says deliver 5x better power efficiency. On scaling, Nvidia describes Spectrum-X as able to reach 128,000 GPUs in a flat two-tier topology — a figure the company says is 64 times larger than single-plane networks can reach. Importantly, Nvidia positions this as fully standards-based Ethernet that supports open network operating systems like SONiC, not a proprietary fabric.
The Mellanox Acquisition: How Nvidia Became a Networking Company
None of this would exist in its current form without Nvidia’s purchase of Mellanox Technologies, the company that built much of the industry’s InfiniBand and high-performance Ethernet silicon. Nvidia announced the deal in March 2019 and closed it on April 27, 2020, for roughly $7 billion. At the time, Nvidia CEO Jensen Huang said, “With Mellanox, the new NVIDIA has end-to-end technologies from AI computing to networking.” That combination is the direct ancestor of today’s stack: Mellanox’s ConnectX network adapters and switch silicon became the base for both the Quantum InfiniBand line and the Spectrum Ethernet line, while Mellanox’s SHARP in-network computing technology was folded into Nvidia’s collective-communication software. In effect, the acquisition gave Nvidia control of both ends of the AI data center — the GPUs doing the computing and the fabric moving data between them — which is part of why Nvidia can now sell a complete rack-scale system rather than just a chip.
NVLink vs InfiniBand vs Spectrum-X
Dimension
NVLink (+ NVLink Switch)
InfiniBand (Quantum-2)
Spectrum-X
Connects
GPUs/CPUs within a node or rack
Servers across a cluster
Servers across a cluster
Network type
Proprietary coherent interconnect
Proprietary lossless fabric
Standards-based Ethernet
Typical scale (claimed)
Up to 72 GPUs per NVL72 domain
Over 1M nodes
Up to 128K GPUs
In-network compute
N/A (direct links)
SHARPv3
RoCE with congestion control, adaptive routing
Best fit
Tightest-coupled training within a rack
Dedicated AI/HPC supercomputers
Multi-tenant AI clouds wanting Ethernet operability
Trade-offs
NVLink’s bandwidth is unmatched, but it only works within Nvidia’s own rack-scale systems — it isn’t a general data-center network.
InfiniBand offers the most mature in-network computing, but it requires a dedicated fabric and ecosystem separate from a customer’s existing Ethernet operations.
Spectrum-X is more familiar to enterprise network teams, but Nvidia’s performance multipliers (1.6x, 1.9x, 5x, etc.) are vendor-reported figures, not independently audited benchmarks.
All three layers are now Nvidia-controlled end to end, which concentrates the AI networking supply chain around a single vendor.
Bottom Line
GPUs get the headlines, but Nvidia’s AI data center pitch increasingly rests on the fabric connecting them. NVLink and NVLink-C2C handle the tightest-coupled links inside a server or module, NVLink Switch extends that into 72-GPU “single accelerator” domains, InfiniBand remains the proven scale-out fabric for the largest dedicated AI/HPC clusters, and Spectrum-X is Nvidia’s bet that most future AI clouds will want Ethernet-level interoperability without giving up supercomputer-grade performance. The thread tracing back through all of it is Mellanox — the 2020 acquisition that gave Nvidia the silicon to build a full-stack data center rather than just a chip.
FAQ
Is InfiniBand faster than Ethernet for AI workloads? Nvidia’s Quantum-2 InfiniBand switches support 400 Gb/s ports and in-network computing features like SHARP that have historically given InfiniBand an edge in latency and collective-operation performance. Spectrum-X narrows that gap for Ethernet with similar congestion control and offload features, and Nvidia reports up to 1.6x better performance than stock Ethernet — but that is a vendor figure, not a neutral third-party benchmark.
What’s the difference between NVLink and InfiniBand? NVLink connects GPUs (and increasingly CPUs) directly, within a server or, via NVLink Switch, within a rack-scale system like the NVL72. InfiniBand connects separate servers to each other across a cluster. They operate at different layers of the same system and aren’t interchangeable.
Why did Nvidia buy Mellanox? Mellanox brought Nvidia the InfiniBand and high-performance Ethernet silicon — switches, NICs, and software — that Nvidia lacked. The roughly $7 billion deal, completed in April 2020, let Nvidia pair its GPUs with its own networking stack instead of depending on third-party network vendors.
Can Spectrum-X replace InfiniBand entirely? Nvidia sells both and positions them for different buyers: InfiniBand for dedicated AI/HPC supercomputers, Spectrum-X for Ethernet-based, often multi-tenant, AI clouds. Nvidia has not stated that either is being discontinued.
Every cloud-native pipeline eventually hits the same question: where do the API keys, database passwords, and TLS certificates actually live, and who can rotate them without a 2am page? HashiCorp Vault, AWS Secrets Manager, and Doppler answer that question in three structurally different ways — self-hosted and dynamic, deeply AWS-native, and developer-experience-first SaaS, respectively.
At a Glance
Tool
Deployment
Dynamic Secrets
Best For
HashiCorp Vault
Self-hosted or HCP Vault Dedicated (managed)
Yes — native, for databases and multiple cloud providers
Platform/security teams needing short-lived, on-demand credentials across heterogeneous infrastructure
AWS Secrets Manager
Fully managed AWS service only
Rotation via Lambda; not true on-demand dynamic generation
Teams fully committed to AWS wanting zero infrastructure to run
Doppler
Fully managed SaaS (self-hosted available on Enterprise)
Enterprise tier only
Developer-experience-focused teams syncing secrets across many CI/CD and cloud targets
Short Verdict
Vault is the most capable option and the only one of the three with true on-demand dynamic secrets out of the box, but it costs the most in setup and operational effort unless you buy the managed HCP Vault Dedicated tier. AWS Secrets Manager is the easiest choice if your workloads already live entirely in AWS and you just need rotation and IAM-gated access. Doppler sits in between: it’s not a vault in the cryptographic sense, but it’s the fastest way to get consistent secrets into every CI/CD pipeline and cloud target a team actually uses day to day.
What They Are
HashiCorp Vault is a secrets management and data protection system that can issue short-lived, dynamically generated credentials for databases and cloud providers on request, in addition to storing static secrets, all gated by a policy engine. It can run self-hosted (open source or Enterprise) or as HCP Vault Dedicated, HashiCorp’s managed cluster offering (now sold under IBM).
AWS Secrets Manager is a fully managed AWS service for storing secrets and automating their rotation using a Lambda function you provide (or one of AWS’s built-in rotation templates for RDS, Redshift, and DocumentDB), with access controlled through IAM policies.
Doppler is a SaaS secrets orchestration platform built around syncing one source of truth for environment variables and secrets out to CI/CD systems, cloud providers, and local developer environments, with a strong focus on developer workflow (CLI, config inheritance, change requests) rather than cryptographic primitives.
Pricing Breakdown
Tool / Tier
Price
Notes
Vault (self-hosted, open source)
$0 (software)
Business Source License 1.1; you run and operate it yourself
HCP Vault Dedicated — Extra Small (Development)
$0.61644/hour
Official IBM-listed hourly rate for the smallest dev cluster
HCP Vault Dedicated — Small Cluster
$1.57799/hr (Essentials) or $1.84299/hr (Standard)
Official IBM-listed rate; scales up through Medium and Large cluster sizes
HCP Vault Dedicated — Product Client fee
$72.92/month
Per-client charge in addition to cluster hourly rate
AWS Secrets Manager
$0.40 per secret per month + $0.05 per 10,000 API calls
Official AWS rate; new AWS customers may apply up to $200 in Free Tier credit
This is where the three products diverge most. HashiCorp’s own documentation describes dynamic secrets as credentials “generated on demand” by Vault for a target system — a database, a cloud IAM role — and automatically revoked after a defined lease, meaning no static, long-lived credential exists in the first place for an attacker to steal. AWS Secrets Manager’s rotation model is different in kind: it stores a persistent secret and rotates its value on a schedule using a Lambda function (AWS ships ready-made rotation templates for RDS, Redshift, and DocumentDB in its official documentation), but the secret is still a stored, static value between rotations rather than issued fresh per request. Doppler’s own pricing page lists “dynamic secrets” and “automatic secret rotation” as features, but automatic rotation is a Team-tier feature while true dynamic secrets are gated to the Enterprise tier — making Doppler’s dynamic-secrets capability narrower in availability than Vault’s, which ships it in the open-source core.
CI/CD Integration
Vault integrates with CI/CD primarily through its API, CLI, and dedicated plugins (GitHub Actions, GitLab CI, Jenkins) that authenticate a pipeline run and fetch short-lived credentials just for that run. AWS Secrets Manager integrates natively with anything already running under an IAM role or using the AWS SDK — simplest inside AWS-native CI/CD (CodeBuild/CodePipeline) and requires more setup from GitHub Actions or other third-party runners. Doppler is explicitly built around this use case: its Team tier lists CI/CD integration and config syncs as core features, and the CLI is designed to inject secrets as environment variables into almost any pipeline or local shell with minimal configuration, which is the product’s main differentiator against both Vault and Secrets Manager.
Pros / Cons
Vault pros: true dynamic secrets in the open-source core, broadest feature set, works across any cloud or on-prem environment.
Vault cons: self-hosted operation is genuinely complex; HCP Vault Dedicated adds both a per-hour cluster charge and a flat per-client fee.
AWS Secrets Manager pros: zero infrastructure to run, simple per-secret/per-API-call pricing, deep native IAM integration.
AWS Secrets Manager cons: AWS-only; rotation (not true dynamic generation) requires writing or adopting Lambda functions; per-API-call pricing can add up at high request volumes.
Doppler pros: best developer experience and CI/CD sync story of the three, generous free tier for small teams, fast setup.
Doppler cons: true dynamic secrets and self-hosting are Enterprise-only; it’s an orchestration layer over secrets rather than a secrets engine with its own cryptographic backends like Vault’s.
Who It’s a Good Fit For
Security/platform teams needing on-demand, short-lived credentials across multiple clouds or databases: Vault.
Teams fully inside AWS wanting the least operational overhead: AWS Secrets Manager.
Product teams who mainly need one clean source of truth synced into many CI/CD pipelines and clouds, with minimal ops burden: Doppler.
Who Should Look Elsewhere
Small teams without dedicated platform/security engineers should think twice before self-hosting Vault — the operational overhead is real.
Multi-cloud or on-prem organizations should look past AWS Secrets Manager, since it only manages AWS-side secrets natively.
Organizations that need true dynamic, on-demand credential issuance without an Enterprise contract should look past Doppler’s lower tiers toward Vault’s open-source core.
Bottom Line
There isn’t a single winner here because the three products solve different problems: Vault is a secrets engine, AWS Secrets Manager is an AWS-native secrets store with rotation, and Doppler is a developer-experience layer for distributing secrets consistently. Teams that need genuine dynamic, short-lived credentials across heterogeneous infrastructure should default to Vault; teams fully committed to AWS should default to Secrets Manager; teams optimizing for how fast engineers can get secrets into a new pipeline should default to Doppler.
FAQ
What’s the difference between secret rotation and dynamic secrets? Rotation changes the value of an existing, persistent secret on a schedule (AWS Secrets Manager’s model). Dynamic secrets are generated fresh, on demand, with a short lease, and don’t exist as a stored static value at all (Vault’s model).
Is HashiCorp Vault still open source? Vault’s open-source edition is licensed under the Business Source License 1.1, the same license HashiCorp applied across its product line in 2023 — most uses are permitted, but building a competing commercial offering on it is restricted.
Does AWS Secrets Manager support non-AWS secrets? Yes, you can store arbitrary key-value secrets there, but automatic rotation templates and the deepest integrations are built around AWS services like RDS, Redshift, and DocumentDB.
Can Doppler generate dynamic secrets? Only on its Enterprise tier, per Doppler’s own pricing page; automatic rotation (not the same as dynamic generation) is available starting at the Team tier.
What does HCP Vault Dedicated cost beyond the cluster rate? IBM’s official pricing table lists a separate flat “Product Client” fee of $72.92/month in addition to the per-hour cluster charge, which scales with cluster size (Extra Small through Large).
Three tools now dominate how teams provision cloud infrastructure declaratively, and a 2023 licensing fight permanently reshaped the field. Terraform is still the default most engineers reach for, OpenTofu is the Linux Foundation-governed open-source fork that exists because of that licensing fight, and Pulumi takes the opposite bet entirely: real programming languages instead of a domain-specific one. Here’s how they actually compare in 2026.
At a Glance
Tool
License / Governance
Language
Best For
Terraform / HCP Terraform
Business Source License 1.1 (HashiCorp, now part of IBM)
HCL (HashiCorp Configuration Language)
Teams already standardized on Terraform/HCP, wanting official vendor support
OpenTofu
Mozilla Public License 2.0, Linux Foundation project
HCL (drop-in compatible)
Teams that want Terraform’s workflow without BUSL restrictions or vendor lock-in
Pulumi
Apache 2.0 (core engine); Pulumi Cloud is proprietary SaaS
TypeScript, Python, Go, .NET, Java, YAML, or HCL
Teams that want infrastructure code in a general-purpose language with full IDE/test tooling
Short Verdict
If your team is already on Terraform and doesn’t compete with HashiCorp commercially, HCP Terraform’s managed platform still works fine and the BUSL doesn’t functionally change day-to-day use. If you want the same workflow and HCL syntax but without a vendor-controlled license, OpenTofu is a genuine drop-in replacement under community governance. If your engineers would rather write infrastructure in a language they already know, with unit tests, loops, and real type systems, Pulumi is the only one of the three built for that from the ground up.
What They Are
Terraform is HashiCorp’s infrastructure-as-code tool, configured in HCL, that plans and applies changes against cloud provider APIs using a declarative state file. HCP Terraform (formerly Terraform Cloud) is HashiCorp’s managed SaaS layer on top of it, adding remote state, policy as code, and run automation.
OpenTofu is a fork of Terraform’s codebase (from the last MPL-licensed release) created by a coalition including Gruntwork, Spacelift, Harness, env0, and Scalr, directly in response to HashiCorp’s 2023 license change, and it now operates under the Linux Foundation’s stewardship with multi-vendor governance rather than a single company controlling the roadmap.
Pulumi is an infrastructure-as-code platform that lets you define cloud resources using general-purpose programming languages instead of a DSL, compiling your program down to the same kind of resource graph and state model, then applying changes through its own engine and providers (many of which wrap the Terraform provider ecosystem under the hood).
The Licensing Story
On August 10, 2023, HashiCorp announced it was moving “all future releases of HashiCorp products” — Terraform included — from the open-source MPL 2.0 to the Business Source License (BUSL) 1.1. Under the BUSL, anyone can still copy, modify, and redistribute the code for commercial or non-commercial use, with one carve-out: you cannot use it to build a “competitive offering” to HashiCorp. Vendors who did so lose access to future releases, bug fixes, and security patches; regular end users and partners see no practical change. In direct response, a group of vendors forked the last MPL-licensed Terraform codebase and launched OpenTofu, which the Linux Foundation now hosts, giving it a governance model no single company controls. Pulumi was never part of this dispute — its core engine has been Apache 2.0 licensed independently of Terraform’s code.
Pricing Breakdown
Tool / Tier
Price
Notes
HCP Terraform Free
$0
Up to 500 managed resources, unlimited users, SSO, Sentinel/OPA policy as code included
HCP Terraform Essentials
$0.00013 / resource-hour
≈$0.095 per managed resource/month at full-time usage; official IBM-listed rate
HCP Terraform Standard
$0.00064 / resource-hour
≈$0.47 per managed resource/month; adds concurrency add-ons
HCP Terraform Premium
$0.00135 / resource-hour
≈$0.99 per managed resource/month; highest concurrency tier
HCP Terraform Enterprise
Custom
Contact sales; self-managed option also available
OpenTofu (open source)
$0
No paid tier exists from the OpenTofu project itself; third-party vendors sell hosted runners/state backends around it
Pulumi Free
$0
1 user, unlimited stacks/projects, up to 500 workflow minutes/month
Pulumi Essentials
$40/month
Up to 500 managed resources, unlimited users, CI/CD, automatic secrets rotation
Pulumi Pro
$400/month
Up to 2,000 managed resources, SSO/SAML, policy enforcement, drift detection
Pulumi Enterprise
From $2,000/month (contract pricing above that)
Up to 4,750 managed resources, self-hosting option, compliance conformance packs
Language and Workflow
Terraform and OpenTofu both use HCL, a purpose-built declarative configuration language — easy to read, limited as a programming language (loops and conditionals are expressed through functions like for_each and count rather than native control flow). Pulumi’s official documentation lists support for TypeScript/JavaScript, Python, Go, .NET (C#/F#/VB), Java, and a declarative YAML option — plus the ability to author in HCL via a converter for teams migrating from Terraform. That means Pulumi code gets real loops, functions, unit tests, and IDE autocomplete/type-checking for free, at the cost of a steeper initial learning curve for teams without strong general-purpose programming skills.
OpenTofu has also started shipping features Terraform doesn’t have in the open-source line, notably native state and plan file encryption at rest (supporting AWS KMS, GCP KMS, Azure Key Vault, OpenBao, or passphrase-based keys, with AES-GCM and rollover support for changing providers) — a direct result of community-driven development no longer gated by a single vendor’s roadmap.
Pros / Cons
Terraform/HCP Terraform pros: largest provider ecosystem, official vendor support, mature tooling and documentation, IBM-backed enterprise contracts.
Terraform/HCP Terraform cons: BUSL restricts competitive commercial use of the open-source code; HCP pricing scales per managed resource and per concurrent run.
OpenTofu pros: fully open-source (MPL 2.0) under neutral Linux Foundation governance; drop-in compatible with existing Terraform configs; built-in state encryption.
OpenTofu cons: smaller core team than HashiCorp; no official first-party managed SaaS from the project itself (third-party platforms fill that gap); younger ecosystem for niche providers.
Pulumi pros: real programming languages, strong testing story, can share logic/abstractions as normal code libraries, generous free tier.
Pulumi cons: smaller community/provider ecosystem than Terraform’s, team needs programming fluency, Pulumi Cloud itself is closed-source SaaS.
Who It’s a Good Fit For
Enterprises already standardized on HashiCorp’s stack and needing vendor accountability and support contracts: HCP Terraform.
Teams migrating off Terraform purely over licensing concerns, who want zero config rewrite: OpenTofu.
Software engineering-heavy teams that want infrastructure code reviewed, tested, and abstracted the same way as application code: Pulumi.
Who Should Look Elsewhere
Vendors building a competing managed IaC product should not build on Terraform’s BUSL-licensed code — OpenTofu’s MPL 2.0 license is the appropriate alternative.
Teams without general-purpose programming experience on staff may find HCL (Terraform/OpenTofu) a gentler on-ramp than Pulumi.
Organizations wanting a fully open-source managed control plane with no proprietary SaaS component should lean toward OpenTofu plus a third-party or self-hosted runner rather than HCP Terraform or Pulumi Cloud.
Bottom Line
The 2023 BUSL change didn’t kill Terraform, but it did permanently split the ecosystem: HashiCorp (now IBM) keeps the commercial, vendor-backed track, OpenTofu keeps the fully open-source, community-governed track with real technical advantages like built-in state encryption, and Pulumi continues to serve a different audience entirely — one that wants infrastructure as actual code rather than a DSL. None of the three is strictly obsolete; the right pick depends on whether your constraint is licensing, ecosystem maturity, or language preference.
FAQ
Is Terraform still open source? No, not under the OSI definition — it’s under the Business Source License 1.1, which permits most uses but restricts building a competing commercial offering on it.
Can I migrate existing Terraform configs to OpenTofu without rewriting them? Yes — OpenTofu was forked from Terraform’s codebase specifically to stay a drop-in replacement, including HCL syntax and provider compatibility.
Does Pulumi support HCL? Yes, Pulumi’s official documentation lists HCL as a supported authoring option alongside TypeScript, Python, Go, .NET, Java, and YAML, mainly to ease migration from Terraform.
Who governs OpenTofu? It operates under the Linux Foundation’s stewardship as a multi-vendor project, rather than being controlled by a single company.
Is HCP Terraform the same as the old Terraform Cloud? Yes — HashiCorp renamed Terraform Cloud to HCP Terraform; it’s the managed SaaS layer billed per managed resource rather than a separate product.
Buffer overflows, use-after-free, dangling pointers, double frees — these bug classes have been showing up in CVE databases since before most working engineers were born, and they’re still there. A 2023 joint guidance from CISA, the NSA, the FBI, and international partners states plainly that “two-thirds of reported vulnerabilities in memory unsafe programming languages still relate to memory issues.” Rust’s answer isn’t a runtime garbage collector or extra discipline — it’s a compile-time checker that refuses to build programs with certain classes of memory bugs at all. Here’s how that actually works.
At a Glance
Approach
Strengths
Best For
Manual memory management (C/C++)
Maximum control, zero forced overhead
Legacy systems, environments where a GC or borrow checker genuinely can’t fit
Garbage collection (Java, Go, Python)
Simple mental model, no manual frees, no borrow-checker learning curve
Most application code where occasional GC pauses are acceptable
Rust ownership + borrow checker
Compile-time memory safety with no runtime GC pause, zero-cost abstractions
Systems code, performance-critical services, and anywhere memory-safety CVEs are unacceptable
Why C and C++ Keep Producing These Bugs
In C and C++, nothing in the type system tracks who owns a piece of memory or how long a pointer into it stays valid. A pointer can outlive the memory it points to (use-after-free), two pointers can alias the same memory while one mutates it (data races and aliasing bugs), and free() can be called twice on the same block (double free). The compiler has no concept of “this pointer is no longer valid” — that bookkeeping is entirely the programmer’s job, by convention, across every function that touches the pointer. CISA’s guidance is a response to just how often that convention fails in practice, at scale, across the industry.
Ownership: One Owner at a Time
Rust’s foundational rule is that every value has exactly one owner, and when that owner goes out of scope, the value is dropped (its memory freed) automatically — no free() call required, and no way to forget one. Moving a value (assigning it to a new variable, passing it by value) transfers ownership; the old variable becomes invalid and the compiler rejects any later use of it. This alone eliminates double frees and most use-after-free bugs, because there’s only ever one place responsible for cleanup, and the compiler tracks when that place goes away.
Borrowing: References Without Giving Up Ownership
Ownership alone would force constant copying, so Rust also lets code “borrow” a value through a reference (&T for a shared, read-only reference, &mut T for an exclusive, writable one) without taking ownership. The official Rust book states the core rule compactly: at any given time, you can have either one mutable reference or any number of immutable references to the same value — never both, and never two mutable references at once. This is what the borrow checker actually enforces, and it’s what rules out data races at compile time: immutable readers can never be surprised by a concurrent writer, because the compiler won’t let a writer and readers coexist in the first place.
Here is a real violation of that rule, and the exact error rustc 1.97.0 produces for it:
fn main() {
let mut v = vec![1, 2, 3];
let first = &v[0]; // immutable borrow starts here
v.push(4); // ERROR: tries to mutate while borrowed
println!("{}", first);
}
error[E0502]: cannot borrow `v` as mutable because it is also borrowed as immutable
--> src/main.rs:4:5
|
3 | let first = &v[0];
| - immutable borrow occurs here
4 | v.push(4);
| ^^^^^^^^^ mutable borrow occurs here
5 | println!("{}", first);
| ----- immutable borrow later used here
This is not a pedantic compiler being overly cautious: Vec::push can reallocate the vector’s backing buffer to make room, which would leave first pointing at freed memory — a use-after-free, caught before the program ever runs. The fix is to not hold a live borrow across the mutation. Since i32 implements Copy, the simplest fix is to copy the value instead of borrowing it:
fn main() {
let mut v = vec![1, 2, 3];
let first = v[0]; // copies the i32, no outstanding borrow
v.push(4); // fine -- no live reference into v
println!("{}", first); // prints 1
}
This version compiles and runs cleanly, printing 1 (verified with rustc 1.97.0). Note also that the Rust book points out a reference’s scope runs from where it’s introduced to its last use, not to the end of the enclosing block — so in cases where you do need the original reference, simply moving the println! before the mutation, or wrapping the borrow in its own inner scope, also fixes the error without copying.
Lifetimes: Making “How Long Is This Valid” Explicit
Every reference has a lifetime — the scope for which it’s guaranteed valid — and the borrow checker’s job is to confirm no reference ever outlives the data it points to. Most of the time lifetimes are inferred silently. They become visible as explicit annotations ('a) only when the relationships between multiple references are ambiguous to the compiler, most commonly in a function signature that returns a reference derived from more than one input. The classic example from the Rust book:
fn longest(x: &str, y: &str) -> &str {
if x.len() > y.len() { x } else { y }
}
This fails to compile with error[E0106]: missing lifetime specifier, because the compiler can’t tell whether the returned reference is tied to x‘s lifetime or y‘s. The fix makes that relationship explicit:
fn longest<'a>(x: &'a str, y: &'a str) -> &'a str {
if x.len() > y.len() { x } else { y }
}
This doesn’t change how long anything actually lives at runtime — lifetime annotations are purely a compile-time contract. It tells the compiler the returned reference is valid only as long as bothx and y are valid, so if a caller uses the result after the shorter-lived of the two arguments has already been dropped, the compiler rejects it with error[E0597]: ... does not live long enough instead of letting a dangling reference slip through — exactly the class of bug that shows up as a use-after-free CVE in C and C++ code.
Comparison Table
Dimension
C / C++
GC Languages (Java, Go)
Rust
Use-after-free
Possible; caught only by testing/sanitizers, if at all
Prevented at runtime by the collector
Prevented at compile time by the borrow checker
Double free
Possible
Not applicable (GC owns freeing)
Prevented by single-ownership + drop
Runtime overhead
None beyond the code you write
GC pauses and heap overhead
None — checks happen at compile time
Learning curve
Low syntax, high bug risk
Low
Steep initially (borrow checker), easier over time
Trade-offs
The borrow checker rejects some programs that are actually memory-safe but that it can’t prove are safe using its current rules — this is why Rust also offers an explicit, clearly-marked unsafe escape hatch for the rare cases that need it.
Fighting the borrow checker is a real, well-documented onboarding cost for teams new to Rust; it front-loads work that C/C++ would otherwise defer to production incidents.
Because the checks are static, there’s no runtime cost and no GC pause — a meaningful advantage over garbage-collected languages in latency-sensitive systems code.
Bottom Line
Rust doesn’t eliminate memory bugs by making programmers more careful — it eliminates an entire category of them by making the compiler refuse to build programs where ownership is ambiguous or a reference could outlive its data. That trade (a steeper initial learning curve for compile-time guarantees with zero runtime cost) is precisely the trade CISA and the NSA are now telling the industry to make more often, given how persistently memory bugs dominate vulnerability reports in memory-unsafe languages.
FAQ
Does the borrow checker add runtime overhead? No. All borrow and lifetime checking happens at compile time; the compiled binary has no extra runtime bookkeeping for it.
Can Rust still have memory bugs? Inside unsafe blocks, yes — Rust’s guarantees don’t extend past code explicitly marked unsafe, which exists for cases like FFI or low-level data structures the checker can’t verify. Outside unsafe, the compiler won’t accept code that violates the ownership/borrowing rules.
Is the borrow checker the same as a garbage collector? No. A garbage collector tracks and frees memory at runtime; the borrow checker is a static analysis that runs once, at compile time, and then disappears — the compiled program has no GC.
Why do I need explicit lifetime annotations sometimes? Only when the compiler’s lifetime-elision rules can’t infer a unique relationship between input and output references on their own — most commonly in functions that return a reference derived from more than one reference parameter.
Does this mean Rust programs can’t leak memory? The borrow checker targets use-after-free, double-free, and dangling references — not all forms of leaks. It’s possible, for example, to leak memory intentionally or via reference cycles in Rc/Arc-based structures.
Every compiler, interpreter, linter, config-file loader, and query engine starts with the same problem: turning a flat stream of characters or tokens into a structured representation a program can act on. That’s parsing. Three approaches dominate how working engineers solve it today: hand-written recursive descent, parser combinators, and PEG (Parsing Expression Grammar) tooling. Each trades off control, declarativeness, and performance differently, and picking the wrong one for a project tends to show up later as unreadable code or incomprehensible error messages.
At a Glance
Approach
Strengths
Best For
Recursive Descent
Full control over control flow and diagnostics; no dependencies; fast; easy to debug
Production compilers/interpreters that need custom, high-quality error messages
Parser Combinators
Composable and declarative; parsers are ordinary values you can test in isolation; stays inside the host language
Grammar lives in a separate, declarative file; unambiguous by construction; generated code is typically fast
Config languages, DSLs, and projects that want a formal grammar artifact (Pest, PEG.js)
What Parsing Actually Does
A parser takes a sequence of tokens (produced by a lexer/tokenizer) and builds a tree-shaped representation, usually an Abstract Syntax Tree (AST), that reflects the grammar’s structure and operator precedence. The three approaches below differ mainly in how that grammar gets expressed: as imperative code, as composed function values, or as a separate declarative grammar file.
Recursive Descent Parsing
Recursive descent is, as Robert Nystrom puts it in Crafting Interpreters, “the simplest way to build a parser.” It’s a top-down, predictive technique: each grammar rule becomes a function, terminals become code that matches and consumes a token, alternatives (|) become if/switch statements, and repetition (*, +) becomes a loop. When a rule refers to itself, that becomes a recursive function call — hence the name: the parser “walks down” the grammar. Nystrom notes that recursive descent parsers are “fast, robust, and can support sophisticated error handling,” and that production compilers including GCC, V8, and Roslyn use it.
Here is a minimal, correct recursive descent parser for arithmetic expressions with standard precedence (*// binds tighter than +/-), written in JavaScript and verified to run:
// Grammar:
// expr -> term (("+" | "-") term)*
// term -> factor (("*" | "/") factor)*
// factor -> NUMBER | "(" expr ")"
function parse(tokens) {
let pos = 0;
const peek = () => tokens[pos];
const next = () => tokens[pos++];
function parseExpr() {
let left = parseTerm();
while (peek() === "+" || peek() === "-") {
const op = next();
const right = parseTerm();
left = { type: op === "+" ? "Add" : "Sub", left, right };
}
return left;
}
function parseTerm() {
let left = parseFactor();
while (peek() === "*" || peek() === "/") {
const op = next();
const right = parseFactor();
left = { type: op === "*" ? "Mul" : "Div", left, right };
}
return left;
}
function parseFactor() {
const token = next();
if (token === "(") {
const expr = parseExpr();
next(); // consume ")"
return expr;
}
return { type: "Num", value: Number(token) };
}
return parseExpr();
}
const tokens = ["2", "+", "3", "*", "(", "4", "-", "1", ")"];
console.log(parse(tokens));
// Evaluating the resulting tree gives 11, matching 2 + 3 * (4 - 1)
Notice the loop in parseTerm and parseExpr instead of a recursive call back into themselves at the start of the rule — that’s the standard fix for left recursion in hand-written recursive descent, and it’s exactly the technique Crafting Interpreters uses for the same reason: a rule that calls itself as its very first action would recurse forever and overflow the stack.
Parser Combinators
Parser combinators express a grammar as ordinary functions (or values) that you compose with higher-order combinators like sequence, choice, and many. Instead of writing a function per grammar rule by hand, you build a parser for “digit” and combine it with “many” to get “number,” then combine that with “plus” and “number” to get “sum.” This style originates in functional programming (Haskell’s Parsec is the canonical example) and is popular in Rust via the nom crate, which documents itself as a parser-combinator library built around byte- and bit-level parsers. The appeal is composability and testability: each small parser is a first-class value you can unit-test on its own and reuse across grammars.
The trade-off is that stack traces and error messages come from the combinator library’s generic machinery rather than code you wrote for that specific rule, so by default errors tend to be less tailored than a hand-rolled recursive descent parser’s — libraries like nom mitigate this with dedicated error-context combinators, but it’s extra work layered on top of the base approach.
PEG Grammars
A Parsing Expression Grammar looks like a context-free grammar (BNF-style rules) but is interpreted differently: alternatives are tried in order and the first one that matches wins — “ordered choice” — which makes PEGs unambiguous by construction, unlike classic CFGs where multiple derivations can be possible. Pest, a widely used PEG parser generator for Rust, describes PEGs on its own documentation site as “eager, ordered, and unambiguous,” and compiles a separate .pest grammar file into a Rust parsing function at build time. PEG.js and similar tools apply the same idea to JavaScript. A toy version of the arithmetic grammar above, written in Pest’s grammar syntax, looks like this:
expr = { term ~ (("+" | "-") ~ term)* }
term = { factor ~ (("*" | "/") ~ factor)* }
factor = { number | "(" ~ expr ~ ")" }
number = { ASCII_DIGIT+ }
The grammar is now a declarative artifact, separate from the code that walks the resulting parse tree. The catch is left recursion: standard PEGs cannot express a rule like expr = expr ~ "+" ~ term | term directly, because the rule would try to match itself at the same input position before consuming anything and loop forever. Academic work on this problem — notably Warth, Douglass, and Millstein’s “Left Recursion in Parsing Expression Grammars” — proposes algorithms to support it, and some modern PEG tools implement variants of those algorithms, but plain PEG tooling generally expects you to rewrite left recursion as repetition, exactly as in the recursive descent example above.
Comparison Table
Dimension
Recursive Descent
Parser Combinators
PEG Grammars
Performance
Fast; no abstraction overhead
Good, but combinator/closure overhead can add up without optimization
Fast; generated code is comparable to hand-written parsers
Readability
Reads like the grammar, but grammar and code are interleaved
Reads like the grammar if combinators are named well; can get dense
Grammar is separate and declarative, often the clearest artifact
Left recursion
Must be manually rewritten as loops/repetition
Must be manually rewritten; combinators don’t solve it for you
Not supported by default; needs a rewrite or an extended algorithm
Error messages
Best in class — you write exactly the diagnostic you want
Depends on the library; often needs extra “context” combinators
Generated; quality depends on the tool (Pest reports expected rules)
Trade-offs
Recursive descent costs the most up-front code but gives the most control, which is why production compilers favor it when error-message quality matters.
Parser combinators minimize boilerplate and maximize reuse, at the cost of needing to learn a combinator vocabulary and sometimes fighting generic error output.
PEG grammar tools give you a formal, swappable grammar file and strong tooling (syntax highlighting, grammar linting), but you depend on the generator’s runtime and its specific left-recursion and error-reporting behavior.
Bottom Line
If you’re building a language or tool where error messages are a feature — a compiler users will stare at all day — hand-written recursive descent is still the pragmatic default, which is exactly why GCC, V8, and Roslyn use it. If you’re parsing something smaller and want composability and quick iteration inside an existing codebase, reach for a parser-combinator library like nom. If you’d rather keep the grammar as a separate, formal artifact and let a generator produce the parser, PEG tools like Pest or PEG.js are the right fit — just plan for the left-recursion rewrite up front.
FAQ
Is a lexer the same thing as a parser? No. A lexer (tokenizer) turns raw characters into a flat stream of tokens; a parser turns that token stream into a tree. All three approaches in this article assume a token stream already exists.
Do any of these three handle left recursion automatically? Not by default. Hand-written recursive descent, basic parser combinators, and standard PEG tools all require you to rewrite left-recursive rules as repetition. Specialized algorithms exist for left-recursive PEGs, but they’re an extension, not the baseline behavior.
Why do PEGs guarantee no ambiguity while classic context-free grammars don’t? Because PEG alternation (|) is ordered choice — the first alternative that matches wins, full stop — rather than a set of possibilities a general CFG parser must disambiguate.
Which approach is fastest? Hand-written recursive descent and generated PEG parsers are typically the fastest, since both compile down to direct, specialized code. Parser combinators can match that speed but depend on how well the library inlines and avoids allocation.
Can I mix approaches? Yes — it’s common to hand-write the top-level recursive descent structure for a language’s statements while using a small PEG or combinator-based parser for an embedded sub-language like a format string or query expression.
Autonomous AI coding agents — tools like Claude Code, Cursor’s agent mode, and Copilot workspace agents — can now read a codebase, write and run code, call external tools, and open pull requests with minimal human intervention. That autonomy is exactly what makes them productive, and exactly what makes them a new class of security risk. OWASP’s own guidance tracks this: in its GenAI Security Project’s 2026 update, prompt injection held the number-one spot for a third straight year, and “excessive agency” — the risk of a model having too much functionality or too many permissions — jumped from eighth to third place as agentic tool use has spread. This piece explains the core risks and gives a practical checklist for running coding agents safely.
At a Glance: Top Risks and Mitigations
Risk
What It Means for a Coding Agent
Primary Mitigation
Prompt Injection (OWASP LLM01)
Malicious instructions hidden in a file, README, issue comment, or fetched webpage change the agent’s behavior
Treat all retrieved content as untrusted data, never as instructions; sandbox and scope tool access
Excessive Agency (OWASP LLM06)
The agent has broader permissions or tool access than the current task needs (e.g., it can both read and delete files)
Least-privilege permission scoping per task/session; approval gates for destructive actions
Sensitive Information Disclosure (OWASP LLM02)
Agent reads or echoes credentials, API keys, or secrets it encounters while browsing a repo or terminal output
Secrets management outside the agent’s reach (vaults, env injection at runtime), output filtering
Supply Chain (OWASP LLM03)
Agent installs or runs a malicious dependency, plugin, or MCP server it was tricked into trusting
Pin and review dependencies/tools; restrict which registries and MCP servers an agent may use
Improper Output Handling (OWASP LLM05)
Agent-generated code or shell commands execute without review and introduce injection or logic flaws
Human-in-the-loop review before merge/deploy; automated static analysis gates in CI
What Prompt Injection Actually Is
OWASP’s Top 10 for LLM Applications defines a prompt injection vulnerability as occurring when user or external input alters a model’s intended behavior in a way the developer did not anticipate — including input the model retrieves on its own, such as a web page, a file, or a tool’s output. It has been ranked the number-one LLM risk in OWASP’s list for three consecutive editions. As Steve Wilson, co-chair of the OWASP GenAI Security Project, has put it, large language models “cannot differentiate between data and instructions” the way traditional software can, which is why OWASP frames prompt injection as something to be continuously managed rather than a bug that can be definitively patched the way SQL injection can.
For a coding agent, this risk is concrete and not theoretical: a comment in a GitHub issue, a string inside a dependency’s README, or text embedded in a web page the agent fetches while researching a bug can all contain instructions crafted to hijack the agent — for example, telling it to exfiltrate a secret, modify a CI config, or install a malicious package, phrased as if it were part of the legitimate task.
Why Agentic Tool Use Raises the Stakes
OWASP’s LLM06 category, Excessive Agency, covers what happens when a model is given more functionality, more tool access, or more autonomous decision-making power than a task requires. In OWASP’s 2026 update, this category rose to third place, up from eighth two editions earlier — a shift OWASP’s own co-chair attributes directly to AI systems now being able to browse the web, call external tools, and reach into business systems on their own. A coding agent that only needs to read a repository but is also wired up with file-delete, network-access, or production-deployment tools turns a single successful prompt injection into a much larger incident. OWASP’s suggested mitigation is explicit: tightly scoped permissions combined with continuous behavioral monitoring, rather than assuming the model will simply “know” not to misuse a capability it has been handed.
OWASP has also launched a dedicated Agentic Security Initiative (ASI), publishing threat-modeling guidance specifically for agentic systems and mapping it to established frameworks such as MITRE ATLAS, CWE, and NIST — a signal that agentic risk is now treated as its own discipline rather than a subset of general LLM security.
The Checklist: Deploying Coding Agents Safely
Sandbox execution. Run the agent’s shell, code execution, and file access inside a container or VM that is isolated from production credentials, your broader network, and other developers’ environments — never on a developer’s primary machine with full access.
Scope permissions per task, not per project. Grant only the tools and filesystem/network access a specific task needs (e.g., read-only repo access for research tasks; write access only for the specific directory being edited), and treat any request for broader access as something to approve explicitly, not assume.
Treat all fetched content as untrusted data. Web pages, issue comments, dependency READMEs, and tool outputs the agent reads should never be able to directly trigger privileged actions — apply the same mistrust you’d apply to unsanitized user input in a web app.
Keep secrets out of the agent’s reach. Inject credentials at the point of use via a secrets manager or short-lived tokens rather than placing them in files, environment dumps, or chat history the agent can read, log, or echo back.
Require human-in-the-loop review for anything destructive or externally visible. Code merges, deployments, infrastructure changes, and any action that sends data outside the sandbox (network calls, package installs, PR creation to public repos) should require explicit human approval, not run on autopilot.
Pin and vet tools, plugins, and MCP servers. Only connect agents to tool integrations (including Model Context Protocol servers) that have been reviewed, and pin versions rather than letting an agent dynamically discover and install new ones mid-task.
Run static analysis and dependency scanning on agent-generated code. Don’t exempt AI-authored commits from the same SAST/SCA gates applied to human-authored code — agents can introduce the same vulnerability classes, and prompt injection can specifically aim to make them do so.
Log and monitor agent actions continuously. Keep an audit trail of every tool call, file change, and command the agent executes, so an injected or misbehaving session can be detected and rolled back quickly.
Set hard limits on resource and API consumption. OWASP’s Unbounded Consumption category (LLM10) applies to agents too — cap how many tool calls, tokens, or cloud resources a single agent session can use to limit the blast radius of a runaway or hijacked loop.
Review system prompts and configuration for leakage risk. Agent instructions and internal tool definitions can themselves be exposed (OWASP’s System Prompt Leakage, LLM07); avoid embedding secrets or overly sensitive business logic directly in system prompts.
Trade-Offs to Expect
Every mitigation above trades some agent autonomy for safety, and that trade-off is the point, not a flaw. Tight permission scoping and mandatory human review will slow an agent down and reduce the “fire and forget” appeal that makes these tools attractive in the first place. Sandboxing adds infrastructure overhead. Treating all external content as untrusted will occasionally cause an agent to ask for clarification on something genuinely benign. Teams that skip these controls to move faster are accepting the same prompt injection and excessive-agency risks that OWASP has ranked at the top of its list for three years running — the checklist above is about managing that risk deliberately rather than eliminating friction by accident.
Bottom Line
Prompt injection cannot be fully “patched” the way a traditional vulnerability can — OWASP itself frames it as a risk to be continuously managed. For teams running autonomous coding agents, that means defense-in-depth: sandboxed execution, least-privilege permission scoping, secrets kept outside the agent’s reach, mandatory human review for destructive or externally-visible actions, and the same static analysis and dependency scanning you’d apply to any other code, applied without exception to agent output.
FAQ
Is prompt injection the same as a jailbreak?
They’re related but distinct. A jailbreak typically targets the model’s own safety guardrails directly in the conversation; prompt injection more broadly covers any input — including content the model retrieves on its own from a file, webpage, or tool output — that changes its behavior in unintended ways. OWASP’s Prompt Injection category covers both.
Can sandboxing alone solve the problem?
No. Sandboxing limits the blast radius of a compromised agent session, but it doesn’t stop prompt injection from happening — an injected agent can still exfiltrate data, corrupt code, or waste resources within the sandbox. It needs to be combined with permission scoping, secrets isolation, and human review.
Why did “excessive agency” rise so much in OWASP’s ranking?
According to OWASP’s GenAI Security Project, it’s a direct consequence of AI systems increasingly being able to browse the web, call tools, and access business systems autonomously — capabilities that barely existed at the scale seen in earlier editions of the list.
Does this apply to tools like GitHub Copilot’s simpler autocomplete mode, not just full agents?
The risk is much lower for autocomplete-style suggestions that a developer reviews before accepting, because there’s no autonomous tool use or multi-step execution involved. The checklist in this article is specifically about agentic modes that can read, write, execute, and act without a human approving each step.
Where can I read OWASP’s full guidance?
OWASP publishes the Top 10 for LLM Applications and a separate Agentic AI Threats and Mitigations guide through its GenAI Security Project at genai.owasp.org, both linked in the Sources section below.
Feature flagging has grown from a simple on/off switch into a full experimentation and progressive-delivery layer. In 2026, the field is shaped by one notable piece of market consolidation: Split Software, long considered one of the “big three” alongside LaunchDarkly and Unleash, was acquired by Harness in 2024 and now ships as Harness Feature Management & Experimentation (FME). This piece still compares the three under their familiar names, since Split’s engine lives on inside Harness, but buyers should know the standalone Split.io product and self-serve pricing page no longer exist independently.
At a Glance
Platform
Starting Price
Free / Open Tier
Best For
LaunchDarkly
Foundation: pay-as-you-go, no platform fee, from $10/service connection/month and client-side MAU usage
Enterprises wanting the most mature targeting, release automation, and experimentation suite as a managed SaaS
Split (now Harness FME)
Not publicly listed; sales-only since the 2024 Harness acquisition
None published independently of Harness’s broader plans
Existing Harness customers who want flags and experimentation bundled with CI/CD, as part of a larger platform deal
Unleash
Pay-As-You-Go (Cloud or self-hosted, 5-seat minimum): $75/seat/month
Open Source (self-hosted, AGPL-3.0): free, unlimited use
Engineering teams that want full self-hosting control or to avoid per-MAU SaaS billing
Short Verdict
LaunchDarkly remains the most feature-complete SaaS platform, with a genuinely useful free Developer tier and a pay-as-you-go Foundation tier that avoids a big upfront commitment. Unleash is the clear choice if self-hosting, open-source licensing, or avoiding vendor lock-in on your flag data matters — its core is free under AGPL-3.0 and its paid Cloud tier is simple per-seat pricing. Split’s independent identity has effectively dissolved into Harness FME, so it’s really now a question of whether you want feature flags as a standalone product (LaunchDarkly, Unleash) or bundled into a broader Harness CI/CD/security platform deal.
What They Are
LaunchDarkly is a SaaS feature management and experimentation platform offering flag targeting, progressive rollouts, and built-in A/B testing (including Bayesian, frequentist, sequential, and multi-armed bandit analysis methods per its own feature comparison). It is primarily cloud-hosted; a Relay Proxy component can be self-hosted to cache flag data and reduce latency or outbound connections, but the core control plane remains LaunchDarkly’s SaaS.
Split built its reputation on pairing feature flags tightly with experimentation and real-time impact monitoring. Harness announced its acquisition of Split Software in May 2024, and the product is now sold as Harness Feature Management & Experimentation (FME), integrated with Harness’s AIDA AI capabilities and its wider CI/CD and software delivery platform rather than sold as a freestanding product with public pricing.
Unleash is an open-source feature flag platform (core engine under AGPL-3.0, per its GitHub repository) that can be fully self-hosted via Docker, or consumed as Unleash-hosted Cloud/Enterprise plans. It emphasizes “host it on-premise or in the cloud” flexibility as a core selling point, which distinguishes it from the SaaS-first LaunchDarkly model.
Targeting and Rollout Features
LaunchDarkly: user/account/device-level targeting, segments, percentage-based rollouts, and a full experimentation suite (A/B/n testing, Bayesian and frequentist analysis, sequential testing, multi-armed bandits) shown across its plan comparison table, plus Enterprise-tier advanced targeting, custom roles, approval workflows, and release automation.
Split / Harness FME: targeting rules, environments, and pipeline-aware rollouts are documented in Harness’s developer docs, but current self-serve plan-by-plan feature gating is not published, since the product is now quoted through Harness sales.
Unleash: flexible hosting plus standard targeting strategies and multi-environment/project support; Enterprise and Pay-As-You-Go tiers add advanced access control, private hosted instances, multi-region Edge, and access logs/IP restrictions as add-ons.
Pricing Breakdown
Platform / Tier
Price
Notes
LaunchDarkly Developer
$0/month, forever
Unlimited seats and flags, 100K experimentation MAU/month, 1K client-side MAU, 5K AI runs/month
LaunchDarkly Foundation
Pay-as-you-go, billed yearly; ~$10 per service connection/month and per-1K client-side MAU usage
No platform or seat fees; 14-day trial; 5K AI runs included, extra at $5/1K
LaunchDarkly Enterprise
Custom
Advanced targeting, custom roles/teams, approval workflows, release automation, SSO/SAML (included at every tier); separately priced Guardian add-on for automatic rollback
Split / Harness FME
Not publicly listed
Sold through Harness sales as a module within Harness’s broader platform; see Harness pricing page for context
Unleash Open Source
$0
Self-hosted, AGPL-3.0 licensed, unlimited use
Unleash Pay-As-You-Go
$75/seat/month
Unleash-hosted Cloud by default, or self-hosted with a 5-seat minimum; 53M API requests/month included, then $5/million; 99.9% uptime SLA
Unleash Enterprise
Custom, annual contract
Cloud, self-hosted, or hybrid; 99.99% uptime SLA, guided onboarding, add-ons for private hosted instance and multi-region Edge
Pros and Cons
LaunchDarkly
Pros: strongest free tier of the three for getting started, no seat caps on Developer, mature experimentation methodology options, SSO included at every tier.
Cons: SaaS-only control plane (the Relay Proxy only caches, it doesn’t replace the cloud backend), usage-based billing on service connections and client-side MAU can get expensive at scale.
Split / Harness FME
Pros: deep integration potential with Harness’s CI/CD, security, and AIDA AI tooling for teams already standardized on Harness.
Cons: no public pricing or free self-serve tier any more; evaluating it now means engaging Harness sales rather than trying it independently.
Unleash
Pros: genuinely free and open-source core, full self-hosting control over flag data, simple flat per-seat pricing with no MAU metering on the hosted plans.
Cons: AGPL-3.0 licensing has stricter obligations than permissive licenses for some commercial redistribution scenarios, and its experimentation/analytics feature depth is generally considered less mature than LaunchDarkly’s.
Who It’s a Good Fit For / Who Should Look Elsewhere
LaunchDarkly is the easiest default for teams that want a managed SaaS platform, strong out-of-the-box experimentation statistics, and a free tier to start on before scaling into usage-based pricing. It’s a weaker fit for teams with strict data-residency or self-hosting requirements for the control plane itself.
Split / Harness FME is worth evaluating only if you’re already in, or planning to move to, the Harness ecosystem for CI/CD and want flags as part of that bundle. It’s a poor fit if you want transparent self-serve pricing or a product that can be adopted independently of a larger platform decision.
Unleash is the strongest fit for engineering organizations that want to self-host, need to keep targeting data in their own infrastructure for compliance reasons, or simply want predictable flat per-seat pricing instead of MAU-based billing. It’s a weaker fit for teams that want the deepest built-in statistical experimentation tooling without building more themselves.
Bottom Line
For most teams starting fresh, LaunchDarkly’s free Developer tier and pay-as-you-go Foundation plan offer the lowest-friction path to a mature feature-flag and experimentation platform. Teams that need self-hosting or want to avoid SaaS lock-in should look at Unleash’s open-source core first. Split is no longer really a third independent option — it’s now a decision about whether to buy into the broader Harness platform.
FAQ
Is Split.io still sold as a standalone product?
No. Harness announced its acquisition of Split Software in May 2024, and the product is now marketed as Harness Feature Management & Experimentation (FME) with pricing handled through Harness sales rather than a public self-serve page.
Can I self-host LaunchDarkly entirely?
Not the control plane. LaunchDarkly offers a self-hostable Relay Proxy that caches flag data and manages SDK connections closer to your infrastructure, but the core management service remains LaunchDarkly’s SaaS.
Is Unleash’s free tier really unlimited?
The Open Source edition, self-hosted under its AGPL-3.0 license, has no seat or usage caps imposed by Unleash itself — you run and scale it on your own infrastructure. Paid Cloud/Enterprise tiers exist for teams that want Unleash to host it, with support SLAs and additional features.
Which platform is cheapest for a small team?
For a very small team, LaunchDarkly’s free Developer plan or Unleash’s self-hosted Open Source edition both cost $0, but Unleash requires you to run the infrastructure yourself, while LaunchDarkly’s free tier is fully managed with usage caps.
Static analysis has become a baseline expectation in modern software delivery, but “static analysis tool” now covers everything from lightweight linters to deep semantic query engines backed by large research teams. SonarQube, Semgrep, and CodeQL are three of the most widely deployed options in 2026, and each takes a meaningfully different approach to finding bugs and vulnerabilities before they ship. This comparison looks at what each tool actually does, what it costs, and which teams it suits.
At a Glance
Tool
Starting Price
Free / Open Tier
Best For
SonarQube
Cloud Team from $34/month; self-hosted Developer/Enterprise/Data Center priced per instance by lines of code (contact sales)
Community Build (self-hosted, free); Cloud free for public OSS repos and up to 50k private LOC
Teams wanting broad code-quality dashboards plus security, including legacy enterprise languages
Semgrep
Teams from $30/contributor/month per product (Code, Supply Chain); Secrets add-on $15/contributor/month
Free Edition: up to 10 contributors, Code + Supply Chain included
Engineering teams wanting fast, customizable, developer-friendly SAST/SCA/secrets with low false-positive noise
CodeQL (via GitHub)
GitHub Code Security $30/active committer/month (plus GitHub Team $4 or Enterprise $21 per user/month)
Free for public repositories on GitHub
Teams already on GitHub Enterprise wanting deep dataflow/semantic vulnerability analysis
Short Verdict
There is no single winner here because the three tools solve overlapping but distinct problems. SonarQube is the strongest choice for organization-wide code quality governance across a huge range of languages, including mainframe-era ones. Semgrep is the fastest to adopt and customize, and it bundles SAST, software composition analysis (SCA), and secrets detection with a genuinely useful AI triage layer. CodeQL, delivered through GitHub’s Code Security product, does the deepest semantic dataflow analysis of the three but is tied tightly to the GitHub ecosystem and its per-committer billing. Many security-mature teams end up running more than one of these together rather than picking a single winner.
What They Are
SonarQube (SonarSource) is a code quality and security platform built around “Clean Code” principles and quality gates that can block a merge or release. It ships as a free, self-hosted Community Build, as paid self-hosted editions (Developer, Enterprise, Data Center) licensed per instance based on lines of code, and as SonarQube Cloud, a hosted SaaS product with its own free and paid tiers. Detection is primarily rule-based static analysis — pattern and structure matching across the codebase — supplemented by targeted dataflow checks for specific rule categories, plus an AI CodeFix capability on higher tiers that can use bring-your-own-key (BYOK) large language models to suggest fixes.
Semgrep is a static analysis engine built around a readable, pattern-matching rule syntax (its own open-source CLI/engine) plus a hosted AppSec Platform that adds organization-wide dashboards, CI gating, SCA, secrets detection, and an AI layer called Semgrep Assistant/Multimodal. Detection combines classic syntactic pattern matching with semantic, AST-aware analysis and cross-function taint tracking in its paid engine, and the AI layer is used specifically for triage (suggesting which findings are false positives, with an explanation), business-logic flaw detection such as broken authorization, and generating pull-request-ready autofixes.
CodeQL is GitHub’s semantic code analysis engine, originally built by Semmle. Rather than scanning text patterns, CodeQL compiles source code into a relational database and lets security researchers write dataflow queries against it in a dedicated query language (QL) — the approach that makes it strong at tracing how untrusted input moves through a program to a dangerous sink. CodeQL itself is free to run against public GitHub repositories; using it on private repositories requires GitHub’s Code Security add-on, which replaced the older bundled “GitHub Advanced Security” SKU.
How Each One Finds Issues
SonarQube: rule-based static analysis across 35+ languages on SonarQube Cloud’s Team tier and 45+ on Enterprise (including ABAP, COBOL, PL/I, RPG, and Apex, alongside Java, JavaScript/TypeScript, Python, C#, C++, Go, Rust, Kotlin, and PHP); organizes findings around a “Clean Code” taxonomy and enforceable quality gates rather than a single vulnerability feed.
Semgrep: pattern-based rules written in a simple, language-agnostic syntax, extended with semantic/AST awareness and taint-tracking dataflow in its commercial engine, plus an AI layer that reasons about business logic (e.g., IDORs, broken auth) that pure pattern rules tend to miss.
CodeQL: true semantic dataflow analysis — code becomes a queryable database, and vulnerability classes are expressed as dataflow queries tracing sources to sinks, which is why it tends to surface deeper, multi-step vulnerabilities that pattern-matching tools miss, at the cost of more setup and longer scan times.
Pricing Breakdown
Tool / Tier
Price
Notes
SonarQube Cloud Team (free)
$0
Private projects up to 50k LOC, no card required; free for public OSS repos regardless of size
SonarQube Cloud Team (paid)
From $34/month
Up to 100k private LOC; aimed at teams under 50 developers
SonarQube Cloud Enterprise
Custom
SSO/SCIM, portfolios, OWASP/MISRA compliance reports, zero data retention, BYOK LLMs; commercial support starts at 5M LOC
SonarQube Server (self-hosted) Developer / Enterprise / Data Center
Per instance per year, by LOC (not publicly listed)
Self-hosted deployment; Community Build remains free and open-source
Semgrep Free Edition
$0
Up to 10 contributors, Code + Supply Chain, up to 10 private repos, 60 AI credits
Semgrep Teams
From $30/contributor/month (Code or Supply Chain); Secrets $15/contributor/month
Up to 500 private repos, 20 AI credits/developer/month; products can be mixed and matched
Requires GitHub Team ($4/user/month) or Enterprise ($21/user/month) base plan
GitHub Secret Protection
$19 per active committer/month
Separate add-on; not required to use CodeQL
CodeQL on public repos
$0
Free regardless of GitHub plan
Pros and Cons
SonarQube
Pros: broadest language coverage of the three (45+ on Enterprise), strong quality-gate workflow for enforcing standards, flexible self-hosted or SaaS deployment, free Community Build.
Cons: self-hosted edition pricing is opaque (sales-only, LOC-based), rule-based engine can be noisier on complex vulnerability classes than CodeQL’s dataflow approach, Community Build lacks many security-specific checks found in paid tiers.
Semgrep
Pros: fast scans, highly readable custom rules, bundled SAST+SCA+secrets, AI-assisted triage that specifically targets false-positive fatigue, generous free tier for small teams.
Cons: per-contributor-per-product pricing can add up quickly once Secrets and SCA are both enabled; its dataflow analysis, while real, is not as exhaustive as CodeQL’s for deep cross-file vulnerability chains.
CodeQL
Pros: the most rigorous semantic/dataflow analysis of the three, free for public/open-source repositories, deeply integrated into GitHub’s pull request and code scanning UI.
Cons: private-repo use requires GitHub Code Security at $30 per active committer/month on top of a Team or Enterprise seat, writing custom QL queries has a steep learning curve, and it is effectively a GitHub-first tool.
Who It’s a Good Fit For / Who Should Look Elsewhere
SonarQube fits organizations that need a single pane of glass for code quality across a very wide range of languages — including regulated enterprises still running COBOL, ABAP, or PL/I — and that want enforceable quality gates tied into their build pipeline. It’s a weaker fit for small teams that just want fast, narrowly-scoped security scanning without a full quality-governance layer.
Semgrep fits product-engineering teams on modern stacks who want a developer-friendly tool that’s easy to write custom rules for, bundles SCA and secrets scanning, and uses AI specifically to cut down on triage time. It’s a weaker fit for teams needing certified compliance reporting for legacy enterprise languages, where SonarQube’s Enterprise tier is more mature.
CodeQL fits teams already standardized on GitHub Enterprise who want the deepest available dataflow analysis and are willing to pay the per-committer premium, plus open-source maintainers who get it for free on public repos. It’s a weaker fit for teams on GitLab, Bitbucket, or self-hosted git who don’t want to adopt GitHub purely for security tooling.
Bottom Line
Pick SonarQube for enterprise-wide code quality governance and language breadth, Semgrep for fast, customizable, AI-assisted SAST/SCA/secrets with a generous free tier, and CodeQL for the deepest semantic vulnerability research inside the GitHub ecosystem. Many mature AppSec programs run Semgrep or SonarQube for breadth and velocity, and layer CodeQL on top for deep dataflow checks on their highest-risk repositories.
FAQ
Is any of these three fully free for a private company codebase?
SonarQube’s Community Build and Semgrep’s Free Edition (up to 10 contributors) can both be used on private code at no cost, with feature limits. CodeQL is free only on public GitHub repositories; private use requires GitHub Code Security.
Which tool has the lowest false-positive rate?
There’s no independently audited, vendor-neutral benchmark we could verify for 2026, so treat any specific percentage claim with skepticism. Semgrep’s AI-assisted triage and CodeQL’s dataflow precision are both specifically designed to reduce noise versus simple pattern matching, but actual results depend heavily on rule tuning.
Can I run more than one of these together?
Yes — they’re not mutually exclusive, and many teams run SonarQube or Semgrep for broad, fast coverage in every pull request, and CodeQL for periodic deep scans on security-critical services.
Do these tools replace a human security review?
No. All three are designed to catch classes of known issues automatically; none of the vendors claims to replace manual code review or penetration testing for business-logic or novel vulnerability classes.
Programmatic buying runs most of the display, video, and streaming TV ad market now, and three demand-side platforms (DSPs) dominate serious budgets: The Trade Desk, Google’s DV360, and Amazon’s DSP. None of the three publish a price list or a minimum-spend number — that’s normal for enterprise DSPs, and we won’t invent figures that don’t exist. What we can tell you, from each company’s own materials, is how you actually get access, what inventory you’re buying, and who each platform is realistically built for.
At a Glance
Platform
Pricing Model
Self-Service Option
Best For
The Trade Desk
Not published; negotiated per account
No public signup — sales conversation required for every account; limited self-service now available through certified partners for SMBs
Agency trading desks, enterprise brands, and holding-company media teams
Google DV360
Not published; enterprise sales-led
Existing users sign in directly; new advertisers are routed to a sales contact
Advertisers already inside the Google Marketing Platform/ads ecosystem wanting tight YouTube and exchange integration
Amazon DSP (now under “Amazon Ads Agent”)
Not published; no stated minimum spend
Yes — both self-service and managed-service options, open to sellers and non-sellers on Amazon
Advertisers wanting direct access to Amazon’s retail, streaming, and Twitch audiences without a large minimum commitment
Short Verdict
Amazon’s DSP (newly rebranded under “Amazon Ads Agent”) is the most accessible of the three for smaller and mid-size advertisers, since Amazon explicitly offers a self-service path with no stated minimum spend. The Trade Desk and DV360 are both effectively closed to advertisers without an existing agency relationship or a sales conversation — pick The Trade Desk for independence from the Google and Amazon ecosystems and the broadest open-web/CTV reach, and pick DV360 if you’re already standardized on Google’s ad stack and want deep YouTube integration.
What They Are
The Trade Desk describes itself as “the leading independent DSP built for data-driven marketers,” buying display, video, audio, digital out-of-home, and Connected TV inventory across hundreds of data and inventory partners, with its own “OpenPath” supply-path product aimed at cutting out resellers between advertisers and publishers. Independent reporting is consistent that there has never been a public self-serve signup: every account starts with a sales conversation, and the platform is built around agency trading desks (including staff certified through The Trade Desk’s own Edge Academy), enterprise brands, and holding companies. In 2025 the company launched a Partner Program that extends more self-service-style access to small and medium businesses, but only through certified service partners, not directly from The Trade Desk.
Google Display & Video 360 (DV360) is Google Marketing Platform’s enterprise DSP, positioned by Google as “end-to-end campaign management for enterprises in one tool” — covering media planning, creative, measurement, and bid automation, with native integration into Google Analytics 360. Its own marketing page routes existing users to a direct sign-in, while anyone without an account is routed to a sales contact rather than a public signup form. On inventory, DV360 gives advertisers access to YouTube (including Google Preferred and TrueView placements) and dozens of third-party ad exchanges.
Amazon’s DSP has just gone through a significant rebrand: at its “unBoxed” 2026 event, Amazon folded the DSP console and its ads console into a single AI-first platform called “Amazon Ads Agent,” with a new default campaign type called DVA (display, video, audio) and an AI-optimized variant, DVA+, rolling out from late October 2026. A toggle under “advanced settings” still exposes the “traditional DSP-type experience” for advertisers who want it. Per Amazon’s own product page, access is open to both sellers and non-sellers on Amazon, through either self-service or managed-service options, with no stated minimum spend — registration happens directly through an Amazon Ads account. Inventory spans Amazon’s own properties (Amazon.com, Prime Video, Twitch, Thursday Night Football, Fire TV) plus thousands of third-party publisher sites and apps, and now explicitly the open web as part of DVA+.
Access & Inventory Breakdown
Platform
How You Get In
Inventory Access
The Trade Desk
Sales conversation for every account; SMB access only via certified Partner Program partners (e.g., Goodway Group)
Open web display/video/audio, digital out-of-home, Connected TV, plus OpenPath supply-path deals
Google DV360
Existing Google Marketing Platform users sign in directly; new advertisers go through Google sales
YouTube (Preferred/Reserve/TrueView), dozens of third-party programmatic exchanges
Amazon Ads Agent / DVA(+) (formerly “Amazon DSP”)
Self-service signup via Amazon Ads account, or managed service via an Amazon account executive; open to non-Amazon-sellers too
Amazon.com, Prime Video, Twitch, Fire TV, Thursday Night Football, thousands of third-party publishers, and the open web under DVA+
Pros and Cons
The Trade Desk — Pros: fully independent of any walled-garden retailer or publisher, deepest CTV/open-web reach, OpenPath aims to reduce supply-chain markup.
The Trade Desk — Cons: no public self-service path for most advertisers; realistically requires agency or partner access.
DV360 — Pros: deep YouTube integration, native tie-in with Google Analytics 360 and the broader Google Marketing Platform stack.
DV360 — Cons: positioned purely for enterprise; Google’s own page gives new prospects no path except contacting sales.
Amazon DSP/Ads Agent — Pros: genuine self-service option with no stated minimum spend; open to advertisers who don’t sell on Amazon; access to unique retail/streaming/Twitch audiences.
Amazon DSP/Ads Agent — Cons: mid-rebrand as of late 2026, so documentation, naming (“Amazon DSP” vs “DVA/DVA+”), and the exact scope of what’s AI-managed by default vs. manually controlled are actively shifting.
Who It’s a Good Fit For / Who Should Look Elsewhere
Choose The Trade Desk if you’re an agency or enterprise brand that needs independent, cross-publisher reach and already has (or can get) a direct sales relationship. Look elsewhere if you’re a smaller advertiser without agency representation and want to self-serve immediately.
Choose DV360 if your media stack is already built around Google (Analytics 360, Google Ads, YouTube) and you have an existing Google Marketing Platform relationship. Look elsewhere if you want a public self-service signup with no prior Google enterprise relationship.
Choose Amazon’s DSP/Ads Agent if you want to start programmatic buying without going through an agency gatekeeper, especially if Amazon’s retail, streaming, or Twitch audiences matter to your brand. Look elsewhere if you need the broadest possible independent, cross-retailer open-web reach that isn’t tied to Amazon’s own properties and data.
Bottom Line
None of these three DSPs will tell you a price upfront, and that’s by design — enterprise programmatic buying runs on negotiated, volume-based deals, not rate cards. The real differentiator in 2026 is access: Amazon is the only one of the three offering a straightforward, publicly described self-service path with no stated spend minimum, while The Trade Desk and DV360 both gate access behind a sales relationship (directly, through an agency, or through a certified partner). Choose based on which walled garden — or lack thereof — fits your inventory needs, not on price you won’t find published anywhere.
FAQ
Is there really no minimum spend for any of these DSPs? None of the three publish one. Amazon’s own product page explicitly states advertisers set their own budgets with no stated DSP minimum; The Trade Desk and DV360 simply don’t publish a rate card or minimum at all — pricing and access are negotiated individually.
What happened to “Amazon DSP” as a name? As of Amazon’s unBoxed 2026 event, the DSP console was merged with the Amazon Ads console into a unified platform called “Amazon Ads Agent,” with a new AI-driven campaign type (DVA/DVA+) replacing the old DSP-only workflow as the default — though a “traditional DSP-type experience” toggle still exists for advertisers who want manual control.
Can a small business realistically use The Trade Desk or DV360? Only indirectly in most cases — through an agency that already has access, or, for The Trade Desk, through its newer certified-partner Partner Program aimed at SMBs. Neither offers a public self-service signup the way Amazon’s DSP does.
Which DSP gives access to the most inventory outside its own ecosystem? The Trade Desk positions itself most explicitly around independent, cross-publisher open-web and CTV reach, since — unlike Google and Amazon — it doesn’t own a major walled-garden property itself.
Invalid clicks quietly drain ad budgets every day — bots, click farms, and competitors clicking your ads all show up as “traffic” unless something is actively filtering it out. ClickCease, Lunio, and TrafficGuard are three of the most established tools built to catch that traffic before it burns your Google Ads or Meta Ads budget. Here’s how they actually compare on price, platform coverage, and how blocking works, based on each vendor’s own current pricing pages.
At a Glance
Tool
Starting Price
Free Option
Best For
ClickCease
$99/month (Starter, annual billing)
7-day free trial
Small businesses on Google, Meta, and Microsoft Ads wanting a self-serve dashboard
Lunio
Custom — priced as a fraction of ad spend, no public rate card
14-day free traffic audit
Mid-size to large advertisers running Google, Meta, LinkedIn, and TikTok who want full-channel coverage
TrafficGuard
$49/month (Shield, Google Ads only, up to $30k/mo spend)
Advertisers wanting real-time, pre-bid blocking rather than after-the-fact exclusion lists
Short Verdict
TrafficGuard is the strongest pick for advertisers who want fraud stopped before it’s ever billed, since its model is pre-bid blocking rather than post-click exclusion. ClickCease is the best fit for small businesses that want a simple, transparently priced, self-serve dashboard across Google, Meta, and Microsoft Ads. Lunio is worth a serious look for larger, multi-channel advertisers, but you’ll need a sales call to get an actual price.
What They Are
ClickCease is a self-serve click-fraud and bot-protection platform that monitors traffic to your website and automatically blocks fraudulent IPs and users on Google, Meta, and Microsoft Ads. It also sells adjacent products — Bot Mitigation for WordPress sites and Lead Shield for filtering fake HubSpot form submissions.
Lunio (formerly PPC Protect) scores every click in real time as legitimate, suspicious, or invalid using click, device, network, location, and post-click behavior signals, then acts differently per platform: it adds offending IPs to Google Ads exclusion lists, while on Meta — which doesn’t support IP blocking — it builds and continuously updates custom audiences of invalid users to exclude from targeting. It also covers Microsoft Ads, LinkedIn, TikTok, and other channels.
TrafficGuard markets itself on pre-bid, real-time prevention rather than post-click cleanup — the company’s own positioning is that catching fraud before a click is billed protects both budget and campaign data, where after-the-fact filtering only recovers some spend. Its core Shield plan covers Google Search and Performance Max, with higher Scale/Enterprise tiers adding Meta, affiliate, and mobile app install fraud protection.
Pricing & Access Breakdown
Plan
Price
Covers
ClickCease Starter
$99/month (or $69/month for first 3 months promo)
1 website domain, ~5,000 monthly visits
ClickCease Pro
$149/month (or $104/month promo)
Up to 5–10 domains depending on table viewed, ~10,000–40,000 monthly visits
ClickCease Advanced
$349/month (or $244/month promo)
Up to 20 domains, ~50,000–80,000 monthly visits
Lunio
Custom quote, billed as a percentage of ad spend
Google, Meta, Microsoft, LinkedIn, TikTok, and other channels; scope depends on contract
TrafficGuard Shield
$49/month
Google Search Ads, up to $30,000/month spend, 1 domain
TrafficGuard Scale/Enterprise
Custom, via sales
Adds Meta, Affiliate, and Mobile app-install fraud protection, unlimited ad accounts
Note: ClickCease’s own plan cards and its detailed comparison table list slightly different domain/traffic limits for the Pro and Advanced tiers — confirm your exact limits with ClickCease sales before subscribing.
Pros and Cons
ClickCease — Pros: transparent published pricing, self-serve signup, covers Google/Meta/Microsoft from one dashboard, add-on bot and lead-fraud products.
ClickCease — Cons: limits are measured in website visits rather than ad clicks, which can be confusing to budget around.
Lunio — Pros: widest channel coverage (Google, Meta, LinkedIn, TikTok, Microsoft and more), sophisticated per-platform blocking logic, cookieless.
Lunio — Cons: no public pricing at all; smaller advertisers may find the sales process slower than a self-serve signup.
TrafficGuard — Pros: true pre-bid prevention model, cheapest published entry price of the three, clear ad-spend cap per tier.
TrafficGuard — Cons: entry Shield plan is Google Search/PMax only — Meta, affiliate, and mobile protection require the custom-priced Scale tier.
Who It’s a Good Fit For / Who Should Look Elsewhere
Choose ClickCease if you’re a small business or agency that wants a transparent, self-serve price and simple multi-platform coverage. Look elsewhere if you need protection measured directly in ad clicks/spend rather than site visits.
Choose Lunio if you run meaningful spend across more than just Google and Meta — LinkedIn, TikTok, and other channels included. Look elsewhere if you need an instant, published price without a sales call.
Choose TrafficGuard if preventing fraud before it’s billed matters more to you than after-the-fact exclusion lists, and your core channel is Google Search/PMax. Look elsewhere if you need Meta or mobile coverage on a budget — that requires the custom Scale tier.
Bottom Line
All three tools genuinely reduce wasted ad spend, but they solve the problem differently: ClickCease is the easiest to buy and understand, Lunio is the most channel-flexible for bigger multi-platform budgets, and TrafficGuard’s pre-bid approach is the most technically aggressive about stopping fraud before it costs you anything. Match the tool to how your budget is structured rather than picking on price alone.
FAQ
Do these tools work on Meta/Facebook Ads the same way they work on Google Ads? No. Google Ads supports IP-level exclusion lists, which all three vendors use. Meta does not support IP blocking, so Lunio and others instead build and exclude custom audiences of flagged users — a meaningfully different, less precise mechanism.
Is pre-bid blocking better than post-click exclusion? In principle, yes — pre-bid prevention (TrafficGuard’s model) stops a fraudulent click from ever being billed, while post-click exclusion (the more common approach) can still let some fraudulent clicks through before the offending IP/user is blocked.
Why doesn’t Lunio publish prices? Lunio prices itself as a percentage of your ad spend rather than a flat tier, so the cost scales with your account — the company requires a conversation to quote an exact number.
Can I try before I buy? Yes for all three: ClickCease offers a 7-day free trial, Lunio offers a 14-day free traffic audit, and TrafficGuard offers a 30-day free trial of its Shield plan in detection-only mode (no blocking, card required).
Ransomware, laptop theft, and plain old hard-drive failure don’t care how big your business is. For small teams without a dedicated IT department, the right cloud backup tool is the difference between a bad afternoon and a company-ending event. Three names dominate the small-business conversation in 2026: Backblaze, Acronis, and IDrive. Each takes a different approach to price, storage, and ransomware defense — here’s how they actually compare, based on their current official pricing pages.
At a Glance
Tool
Starting Price
Free Option
Storage Model
Best For
Backblaze
$99/year per computer (Personal or Business)
14–15 day free trial, no card required
Unlimited per licensed computer
Solo users and small teams wanting flat-rate, truly unlimited backup
Acronis Cyber Protect Home Office
Advanced tier from $56.99/year (Essentials/Premium pricing not published)
No free plan
Up to 500GB (Advanced); larger cloud allotment on Premium
Businesses that want backup bundled with active antivirus/anti-ransomware
IDrive
Free 10GB Basic plan; paid plans from $11.99/month
Yes — permanent free 10GB Basic tier
5TB–500TB shared across devices/users depending on plan
Multi-device teams and offices with servers, NAS, or mixed OS fleets
Short Verdict
For most small businesses, IDrive’s Team or Business plan is the best all-around pick in 2026: it covers many computers, servers, and NAS devices under one shared storage pool, and its free Snapshots feature gives you ransomware rollback without extra cost. Backblaze remains unbeatable for simplicity and price if you just need unlimited backup for a handful of individual computers, while Acronis is the right call if you specifically want active anti-ransomware and antivirus bundled into the same license as your backup.
What They Are
Backblaze is a no-frills, flat-rate backup service built around one promise: unlimited storage per licensed computer for one price. Its Business tier adds centralized, web-based admin, group billing, SSO, and silent MSI/JAMF/Munki deployment for IT teams, but the core backup engine and price are the same as the Personal plan.
Acronis Cyber Protect Home Office (the current name for what used to be called Acronis True Image) pairs file/image backup with a built-in cybersecurity stack — behavioral, AI-based ransomware detection, one-click automatic recovery of files hit by ransomware, on-demand and real-time antivirus scanning, and (on U.S. Advanced/Premium subscriptions) identity protection. It’s sold in Essentials, Advanced, and Premium tiers, all covering up to five PCs/Macs plus unlimited mobile devices.
IDrive backs up Windows, Mac, Linux, iOS, and Android devices into one account and is built around shared storage pools rather than unlimited-per-device backup. Its Team plan scales from 5 to 500 computers on a single quota, and its Business plan supports servers, NAS devices, and Microsoft Exchange/SQL alongside unlimited users.
Pricing & Storage Breakdown
Plan
Price
Storage / Devices
Backblaze Personal
$99/year (or monthly/2-year options)
Unlimited, one computer
Backblaze Business
$99/year per computer
Unlimited per computer + admin console, SSO, group billing
Not published on the official pricing tool at time of writing
Local/device backup plus security features; cloud storage amount not disclosed publicly
Acronis Advanced
From $56.99/year
Up to 500GB cloud storage, 5 devices
Acronis Premium
Not published on the official pricing tool at time of writing
Largest cloud allotment of the three tiers; adds U.S. identity protection
IDrive Basic
Free
10GB
IDrive Personal
$11.99–$119.99/month
5TB–100TB, one user/multiple computers
IDrive Team
$11.99–$1,199.99/month
5TB–500TB shared across 5–500 computers
IDrive Business
$59.99–$2,779.99/month
1.25TB–100TB, unlimited users, servers/NAS/Exchange/SQL support
A note on fairness: Acronis’s own pricing/comparison pages render their price table dynamically, and at the time of writing only the Advanced tier’s price loaded reliably. We’re intentionally not guessing at Essentials or Premium figures — check acronis.com directly before buying, since real published numbers can differ from what secondary retailers list.
Ransomware Protection & Restore Options
This is where the three products diverge most. Acronis is the only one of the three with active ransomware defense built in: behavioral AI monitoring that aims to catch zero-day ransomware as it runs, plus one-click automatic recovery of any files it encrypted before being stopped. IDrive doesn’t market itself as an active ransomware blocker, but its Snapshots feature — included at no extra cost on every plan — keeps up to 30 historical file versions you can roll back to if an attack slips through, and snapshot storage doesn’t count against your quota. Backblaze takes the lightest-touch approach: there’s no dedicated ransomware detection, but its version history (30 days free, one year free, or “Forever” for $0.006/GB per month on files older than a year) serves the same practical purpose — restore to a pre-attack version.
For restores, Backblaze offers free web/app downloads plus a mailed external hard drive (up to 8TB) for $279, refundable if you return the drive within 30 days. IDrive restores through its web console and mobile apps. Acronis restores locally from image backups or from the cloud through its own console.
Backblaze — Cons: no active ransomware/malware protection; per-computer licensing can get pricey for large fleets.
Acronis — Pros: backup and cybersecurity (anti-ransomware, antivirus) in one agent; strong independent detection claims cited by the vendor.
Acronis — Cons: capped cloud storage tiers instead of unlimited; full pricing transparency is inconsistent across its own site.
IDrive — Pros: shared storage pools scale cheaply across many devices/servers; free Snapshots add ransomware rollback at no extra cost; supports NAS/Exchange/SQL.
IDrive — Cons: no dedicated active ransomware blocking; storage is capped and shared rather than unlimited.
Who It’s a Good Fit For / Who Should Look Elsewhere
Choose Backblaze if you run a small office with a handful of computers and want the simplest possible unlimited backup with no storage math. Look elsewhere if you need active malware/ransomware defense built into the same tool.
Choose Acronis if you’d rather pay for one license that handles both backup and endpoint security. Look elsewhere if you back up large media libraries and need unlimited, uncapped cloud storage.
Choose IDrive if you have a mixed fleet of computers, servers, and NAS devices and want one shared quota plus free snapshot-based rollback. Look elsewhere if you want truly unlimited storage per device rather than a shared cap.
Bottom Line
There’s no single winner for every small business — the right pick depends on whether you value unlimited simplicity (Backblaze), bundled active security (Acronis), or flexible multi-device coverage with built-in rollback (IDrive). If forced to pick one default recommendation for a typical small business with a mix of laptops, a NAS, and maybe a server, IDrive’s Team or Business plan offers the best balance of flexibility, ransomware rollback, and predictable pricing in 2026.
FAQ
Does any of these three stop ransomware before it encrypts files? Only Acronis markets active, behavior-based ransomware detection designed to intervene while an attack is running. Backblaze and IDrive rely on version history/snapshots to recover afterward rather than blocking the attack itself.
Is Backblaze really unlimited? Yes, per Backblaze’s own pricing page, for Computer Backup there’s no cap on data volume, file size, or file type for a licensed computer — only mailed restores are capped (zip downloads up to 500GB per web request).
Can IDrive back up a server or NAS device? Yes — that’s specifically what the IDrive Business plan is built for, alongside Microsoft Exchange and SQL support, which neither Backblaze’s consumer/business tier nor Acronis’s home-office product targets.
Do I need to pay extra for long-term version history? With Backblaze, yes beyond one year ($0.006/GB/month for Forever retention on older files); IDrive’s Snapshots (up to 30 versions) are included free on every plan.
Todoist, TickTick, and Things 3 represent three different philosophies for managing tasks on your phone: broad cross-platform flexibility, an all-in-one feature bundle, or a polished, Apple-only, one-time-purchase app. We checked current pricing directly on Todoist’s and TickTick’s official pricing pages, and confirmed Things 3’s prices on Apple’s own App Store listings.
At a Glance
Tool
Starting Price
Platforms
Best For
Todoist
$0/mo (Beginner), $5/mo (Pro)
iOS, Android, Mac, Windows, web, Apple Watch, Wear OS
Cross-platform users and teams wanting AI task capture
TickTick
$0/mo (Free), $49.99/yr (Premium)
iOS, Android, Mac, Windows, web, Apple Watch, Wear OS
All-in-one users who want built-in habit tracking and a Pomodoro timer
Things 3
$9.99 (iPhone/Watch, one-time)
Mac, iPhone, iPad, Apple Watch, Vision Pro only
Apple-only users who want a beautifully designed app with no subscription
Short Verdict
TickTick is the best overall pick for most people, because it bundles task management, habit tracking, and a Pomodoro-style focus timer into one cheap, truly cross-platform subscription. Todoist is the better choice if you want the most mature AI-assisted capture tools and the widest ecosystem of integrations. Things 3 is unmatched for design and is a one-time purchase rather than a subscription — but only if you’re fully inside the Apple ecosystem.
What They Are
Todoist
Todoist is a cross-platform to-do list app built around natural-language task entry, filters, and labels, with a newer AI layer (Task Assist, Email Assist, and “Ramble,” a voice-to-task feature) on its paid tiers. It’s designed to scale from a single person’s list up to shared team workspaces.
TickTick
TickTick is an all-in-one productivity app combining task lists, a calendar, native habit tracking, and a built-in Pomodoro/focus timer (called “Focus”) with white-noise options and session stats — features that are usually separate apps elsewhere.
Things 3
Things 3, by Cultured Code, is a GTD-inspired task manager available only on Apple platforms (Mac, iPhone, iPad, Apple Watch, and Vision Pro). It’s sold as separate one-time purchases per platform rather than a subscription, and is known for its natural-language Quick Entry and refined, minimal interface.
Pricing Breakdown
Tool / Plan
Price
Key Limits / Features
Todoist — Beginner (Free)
$0/mo
5 personal projects, 3 filters, 5MB uploads, 1-week report history
Widest platform and integration coverage of the three (90+ integrations)
Most generous AI feature set for turning voice/rambling notes into tasks
Scales cleanly from solo use to team workspaces
No native habit tracker or focus timer built in
Free plan is noticeably limited (5 projects, 1-week history)
Full AI features require the Pro tier
TickTick
Built-in habit tracking and Pomodoro/focus timer — no extra app needed
Cheapest subscription of the two cross-platform options ($49.99/year)
Generous free tier (9 lists, 99 tasks each)
Less mature AI features than Todoist
Interface can feel busier than Todoist’s or Things’ minimalism
No published monthly billing option on the official upgrade page — annual only
Things 3
One-time purchase, no subscription, ever
Widely regarded as the best-designed task manager in the category
Excellent natural-language Quick Entry and keyboard shortcuts on Mac
Apple-only — no Windows, Android, or web version at all
No native habit tracking or focus timer
Three separate purchases (Mac, iPhone/Watch, iPad) add up to roughly $80 total
Who It’s a Good Fit For / Who Should Look Elsewhere
Todoist fits people and teams spread across multiple operating systems who want AI-assisted capture and deep integrations. Look elsewhere if you specifically want built-in habit tracking or a focus timer without add-ons.
TickTick fits anyone who wants tasks, habits, and focus sessions in a single cheap app, regardless of platform. Look elsewhere if you want the most polished, minimal interface or the deepest AI features.
Things 3 fits Apple-only users who value design and want to pay once instead of subscribing. Look elsewhere immediately if you use Windows or Android on any of your devices, or if you need team/shared-project features — Things 3 has neither.
Bottom Line
Choose Things 3 if you’re all-in on Apple hardware and want a gorgeous app you buy once. Choose Todoist if you need to work across different operating systems with teammates and want the strongest AI task-capture tools. Choose TickTick if you want the best overall value — tasks, habits, and a focus timer in one subscription that’s cheaper than either alternative’s paid tier.
FAQ
Is Things 3 a subscription?
No. Each platform version (Mac $49.99, iPhone/Apple Watch $9.99, iPad $19.99) is a one-time purchase confirmed on Apple’s official App Store listings, with no recurring fee.
Does Todoist have built-in habit tracking?
Not natively — Todoist is built around tasks, projects, and filters rather than habit streaks. TickTick is the one of these three with native habit tracking built in.
Can I use Things 3 on Windows or Android?
No. Things 3 is exclusive to Apple platforms — Mac, iPhone, iPad, Apple Watch, and Vision Pro — with no Windows, Android, or web version.
What does TickTick’s Premium plan cost per month?
TickTick’s official upgrade page lists only an annual price of $49.99/year, which works out to roughly $4.17/month; it doesn’t publish a separate month-to-month plan.
Which app is best for team task management?
Todoist, via its Business plan ($8/user/month billed yearly), is the only one of the three built for shared team workspaces with roles and permissions. Neither TickTick’s consumer tiers nor Things 3 offer equivalent team features.
Power users who live in their inbox tend to gravitate to one of three tools: Superhuman, famous for speed and keyboard-driven triage; Spark, an AI-forward client built to run everywhere; or Outlook, the default for anyone already paying for Microsoft 365. We checked current pricing on each vendor’s own site, including Superhuman’s official help-center pricing article, to see what you actually get for the money in 2026.
At a Glance
Tool
Starting Price
AI Features
Best For
Superhuman
$30/mo (Starter)
Superhuman AI triage; Business adds Auto Drafts, Ask AI
High-volume email power users on Mac/mobile
Spark
$0/mo (Free), $10/mo (Plus)
Spark+AI assistant, AI Meeting Notes, Autopilot (Pro)
AI-assisted email across every platform, including Windows
Outlook (via Microsoft 365)
$9.99/mo (Personal, includes Copilot)
Copilot chat and drafting built into the subscription
Microsoft 365 households and power users needing full platform coverage
Short Verdict
Superhuman is the best pick for dedicated email power users on Mac and mobile who want the fastest, most opinionated inbox-zero workflow and can justify its premium price. Outlook via Microsoft 365 is the practical default for anyone who needs a true Windows app and already pays for the Microsoft ecosystem. Spark is the best middle ground — solid AI features at a fraction of Superhuman’s cost, on every platform.
What They Are
Superhuman
Superhuman is a premium email client layered on top of Gmail or Outlook accounts, built around speed: instant load times, exhaustive keyboard shortcuts, and AI features for triage and drafting. It has native apps for Mac, iPhone, and Android, plus a Chrome extension for desktop browsers — but no dedicated native Windows app.
Spark
Spark Mail (by Readdle) is an AI-assisted email client designed to work consistently across Mac, Windows, iOS, and Android. Its Spark+AI features — summarization, AI Assistant, AI Meeting Notes, and (on Pro) Autopilot and Auto-Drafts — are available on Plus, Pro, and Premium tiers.
Outlook
Outlook is Microsoft’s email client, bundled into Microsoft 365 subscriptions alongside Word, Excel, and now Copilot AI. It runs natively on Windows, Mac, iOS, Android, and the web, making it the most platform-complete option of the three, and a free, more limited version is also available through Outlook.com.
Pricing Breakdown
Tool / Plan
Price
Notes
Superhuman — Starter
$30/mo or $300/yr ($25/mo equivalent)
Most Superhuman AI features
Superhuman — Business
$40/mo or $396/yr ($33/mo equivalent)
Adds Auto Drafts, Ask AI, Custom Auto Labels, CRM integrations
Superhuman — Enterprise
Custom (contact sales)
Adds SSO, advanced security, dedicated support
Spark — Free
$0/mo
Limited AI preview, 5 lifetime AI Meeting Notes
Spark — Plus
$10/mo or $8.25/mo annual ($99/yr)
40 AI Meeting Notes/month, AI Assistant
Spark — Pro
$20/mo or $16.58/mo annual ($199/yr)
Unlimited AI Meeting Notes, Autopilot, Auto-Drafts
Outlook — Free (Outlook.com)
$0/mo
Basic Outlook, limited/no Copilot
Outlook — Microsoft 365 Personal
$9.99/mo or $99.99/yr
Full desktop Outlook + Copilot included, 1 person
Outlook — Microsoft 365 Family
$12.99/mo or $129.99/yr
Same as Personal; Copilot usage limited to the subscription owner
Pros and Cons
Superhuman
Fastest, most refined keyboard-driven workflow of the three
AI triage and drafting feel purpose-built for high email volume
Works on top of existing Gmail/Outlook accounts
By far the most expensive option ($30-40/month per person)
No native Windows app — desktop access is via a Chrome extension
No free plan to try before buying
Spark
True cross-platform support, including Windows
Usable free tier, with paid AI starting at $10/month
AI Meeting Notes and Autopilot are distinctive, practical features
Less polished/fast than Superhuman for pure speed-focused workflows
Full AI feature set requires Pro ($20/month) for unlimited use
Team pricing is handled on a separate page, less transparent upfront
Outlook
Broadest platform support: Windows, Mac, iOS, Android, web
Copilot AI included in the Microsoft 365 price, not a separate add-on
Best value if you already pay for Microsoft 365 for Word/Excel/Teams
Not purpose-built for inbox-zero speed the way Superhuman is
Copilot usage limits apply even on paid plans
Family plan AI features are restricted to the subscription owner only
Who It’s a Good Fit For / Who Should Look Elsewhere
Superhuman fits Mac- and mobile-based professionals processing huge email volumes who treat inbox speed as a competitive advantage. Look elsewhere if you need a native Windows app or are price-sensitive.
Spark fits individuals and small teams who want solid AI email features on whatever device they use, including Windows, without Superhuman’s price tag. Look elsewhere if raw speed and the most refined power-user shortcuts are your top priority.
Outlook fits anyone already in the Microsoft 365 ecosystem, or who needs guaranteed parity across every device including Windows. Look elsewhere if you want an email client built from scratch around speed rather than a general productivity suite.
Bottom Line
Pick Superhuman if you’ll genuinely use its speed and can accept Mac/mobile-first limitations and a premium price. Pick Outlook if you’re already paying for Microsoft 365 and need full platform coverage. Pick Spark if you want meaningful AI assistance across every device at a fraction of Superhuman’s cost.
FAQ
Does Superhuman have a Windows app?
Not a native one. Superhuman’s official download page lists apps for Mac, iPhone/iPad, and Android, plus a Chrome extension for desktop browsers — but no standalone Windows application.
Is Copilot included with Outlook, or is it a separate cost?
Copilot is bundled into Microsoft 365 Personal ($9.99/month) and Family ($12.99/month) plans at no extra charge, per Microsoft’s official pricing page, though usage limits apply.
Does Spark have a free plan?
Yes. Spark’s Free plan includes a limited preview of its AI features and 5 lifetime AI Meeting Notes; full AI access starts on the Plus plan at $10/month.
Is Superhuman worth the price over Gmail or Outlook alone?
It depends on email volume. For people processing dozens to hundreds of emails a day, the speed and AI triage can pay for themselves in time saved; casual users are unlikely to need a $30-40/month add-on layer.
Can I use Superhuman or Spark with my existing Gmail or Outlook account?
Yes, both are designed to connect to existing Gmail, Google Workspace, Outlook, or Microsoft 365 mailboxes rather than replacing your email provider.
HelloSign doesn’t exist as a brand name anymore — Dropbox rebranded it to Dropbox Sign after acquiring it, though plenty of people (and search bars) still call it HelloSign. Alongside DocuSign and PandaDoc, it’s one of the three e-signature tools small businesses compare most. We pulled current pricing directly from each vendor’s site to see how they actually stack up in 2026.
At a Glance
Tool
Starting Price
Free Plan
Best For
DocuSign
$11/mo (Personal)
No permanent free plan
Compliance-heavy teams needing enterprise trust and APIs
PandaDoc
$19/seat/mo (Starter)
Yes — 5 documents/mo
Sales teams that build proposals and quotes, not just sign them
HelloSign (Dropbox Sign)
$15/mo (Essentials)
Yes — limited, signing-only
Individuals and small teams wanting lean, affordable e-signing
Short Verdict
PandaDoc is the best overall pick for small and mid-sized businesses, because it bundles document creation (proposals, quotes) with e-signing rather than charging for signing alone. DocuSign remains the safer choice for regulated industries and large enterprises that need the deepest compliance credentials. Dropbox Sign is the best value if all you need is straightforward signing at the lowest price.
What They Are
DocuSign
DocuSign is the e-signature market’s biggest name, built around its eSignature product plus a wider agreement-management suite. It emphasizes compliance (eIDAS, ESIGN Act, SOC 2, optional HIPAA/FedRAMP on Enhanced) and a very large integration catalog, advertised at 1,000+ connected apps.
PandaDoc
PandaDoc combines a document editor with e-signatures, positioning itself for sales teams that need to build proposals, quotes, and contracts — not just sign existing PDFs. Business and Enterprise tiers add deal rooms, approval workflows, and CRM integrations.
HelloSign (Dropbox Sign)
Dropbox Sign (formerly HelloSign) is a straightforward e-signature tool acquired and rebranded by Dropbox. It’s aimed at individuals and small teams who want unlimited-feeling signing without DocuSign’s enterprise price tag, with native integrations into Google Drive, Microsoft Word, and HubSpot.
Pricing Breakdown
Tool / Plan
Price
Envelope / Document Limits
DocuSign — Personal
$11/mo (annual commitment, $132/yr)
1 user, 5 envelopes/month
DocuSign — Standard
$30/user/mo ($360/yr)
Up to 50 users, 100 envelopes/user/year
DocuSign — Business Pro
$45/user/mo ($540/yr)
Up to 50 users, 100 envelopes/user/year; adds bulk send, PowerForms, payment collection
1 user; “unlimited signature requests” per the official pricing page
Dropbox Sign — Standard
$25/user/mo
2+ users (contact sales for 5+)
Dropbox Sign — Premium
Custom (sales)
5+ users
DocuSign also offers monthly (non-annual-commitment) Standard and Business Pro plans with a lower allotment of about 10 envelopes per user per month, plus pay-as-you-go overage once allowances run out. PandaDoc’s Starter and Business tiers include trial usage credits for API/automation features, which pause once exhausted unless you buy more.
Pros and Cons
DocuSign
Industry-leading compliance credentials and name recognition
Massive integration ecosystem (1,000+ apps)
AI-assisted document summaries built into every tier
Most expensive of the three at comparable tiers
Envelope allowances are measured per year, which can feel stingy on monthly budgets
No real free plan — Personal is the cheapest paid tier
PandaDoc
Genuinely useful free plan (5 docs/month) with real e-signatures
Best document-building tools of the three (proposals, quotes, content library)
Deal rooms and CRM integrations built for sales workflows
API and automation usage requires separately purchased credits on Starter/Business
Priced per seat, which adds up for larger teams
Business pricing pushes toward “request a demo” rather than self-serve checkout
HelloSign (Dropbox Sign)
Lowest entry price among the three paid options
Unlimited signature requests advertised across paid tiers
Simple, uncluttered interface and native Dropbox/Google Drive integration
Fewer document-creation and proposal features than PandaDoc
Lighter compliance/enterprise credentials than DocuSign
Official pricing page doesn’t clearly publish per-tier feature breakdowns, so some details require contacting sales
Who It’s a Good Fit For / Who Should Look Elsewhere
DocuSign fits legal, financial, healthcare, and government-adjacent teams that need the strongest compliance story and are willing to pay for it. Look elsewhere if you’re a small team mainly signing simple documents on a budget.
PandaDoc fits sales and marketing teams that create proposals and quotes in-house and want signing bundled in. Look elsewhere if you just need to send a handful of PDFs for signature and don’t need a document editor.
HelloSign (Dropbox Sign) fits freelancers, small teams, and Dropbox-centric workflows that want affordable, no-frills signing. Look elsewhere if you need advanced compliance certifications or a built-in proposal/quote editor.
Bottom Line
If your business builds the documents it sends — proposals, quotes, contracts — PandaDoc’s combination of editor and e-signature earns the top spot. If compliance and brand trust outweigh cost, DocuSign is still the safest bet. And if you just need clean, affordable signing without extra bells and whistles, Dropbox Sign (HelloSign) does that job for less.
FAQ
Is HelloSign still called HelloSign?
Officially, no — Dropbox rebranded it to Dropbox Sign after acquiring the company. “HelloSign” is still widely used informally and in search, but current pricing and features live under the Dropbox Sign name.
Does DocuSign have a free plan?
Not a permanent one for sending documents. DocuSign’s cheapest paid tier is Personal at $11/month (billed annually), limited to 5 envelopes per month for a single user.
Which tool is cheapest for a solo freelancer?
Dropbox Sign’s Essentials plan ($15/month) and PandaDoc’s free plan (5 documents/month) are the cheapest routes; DocuSign Personal ($11/month) is competitive but caps you at 5 envelopes/month.
Which has the best integrations?
DocuSign advertises the largest integration catalog (1,000+ apps). PandaDoc has strong native CRM integrations (Salesforce, HubSpot, Pipedrive). Dropbox Sign integrates with Google Drive, Microsoft Word, and HubSpot, among others.
Do any of these charge extra for identity verification or SMS?
Yes. DocuSign charges add-on fees for SMS delivery (from $0.36/delivery) and ID verification (from $2.40/attempt) on Standard and Business Pro plans. PandaDoc’s Business and Enterprise tiers include passcode and SMS verification as part of annual plans.
If you freelance, you need software that sends invoices, tracks expenses, and keeps you ready for tax season — without eating your margins. QuickBooks, FreshBooks, and Wave are the three names that come up most often. But one name in that trio has changed in a way most comparisons haven’t caught up to: QuickBooks Self-Employed is no longer open to new customers. Intuit has folded the freelancer tier into QuickBooks Solopreneur (and pushed existing users toward QuickBooks Online Simple Start). We checked current pricing and features directly on each vendor’s site in October 2026 and compare the real, currently-sold products below.
At a Glance
Tool
Starting Price
Free Plan
Best For
QuickBooks (Solopreneur / Simple Start)
$20/mo (Lite), $38/mo (Simple Start)
Yes — very limited (2 invoices/mo)
Freelancers who want built-in quarterly tax help
FreshBooks
$23/mo (Lite)
No permanent free plan (30-day trial only)
Service-based freelancers who invoice clients directly
Wave
$0/mo (Starter), $19/mo (Pro)
Yes — full invoicing and bookkeeping
Budget-first freelancers and micro-businesses
Short Verdict
FreshBooks is the best overall pick for freelancers who regularly bill clients, thanks to its balance of invoicing, proposals, time tracking, and tax-ready reports. Wave is the better choice if $0 software is the priority and you can live with transaction fees on payments. QuickBooks’ freelancer tier (now Solopreneur) is worth a look specifically if estimated quarterly taxes are your biggest pain point.
QuickBooks Self-Employed — the mileage-tracking, Schedule-C-focused app many freelancers grew up on — stopped accepting new sign-ups in late 2024. Intuit’s current freelancer product is QuickBooks Solopreneur, an “all-in-one platform for one-person businesses” built around automatic transaction sorting, income/expense goals, and tax readiness. Freelancers who outgrow Solopreneur, or who need a second user or an accountant seat, move up to QuickBooks Online Simple Start.
FreshBooks
FreshBooks is invoicing-first accounting software built for people who bill clients by the project or the hour. It layers on proposals, e-signatures, retainers, and double-entry accounting reports as you move up its tiers, with every plan including unlimited invoices and estimates, mobile mileage tracking, and tax-time reports.
Wave
Wave is free double-entry accounting and invoicing software for freelancers and very small businesses, monetized mainly through payment-processing fees and optional paid add-ons (automatic bank feeds, payroll, bookkeeping services). Its free “Starter” plan includes unlimited invoices, bills, estimates, and bookkeeping records — a rarity in this category.
FreshBooks’ listed monthly prices above are before its introductory discount (currently 80% off for 4 months on new sign-ups); annual billing adds a further 10% off. QuickBooks’ promotional rates run for the first three months and revert to list price after.
Pros and Cons
QuickBooks Solopreneur / Simple Start
Built-in Expert Assisted Tax and Schedule-C-style categorization
Deep ecosystem: TurboTax integration, payroll add-on, large accountant network
Free plan exists, but it’s extremely limited (2 invoices/month)
The product freelancers remember (Self-Employed) is gone; naming is now confusing
More expensive than FreshBooks or Wave at every comparable tier
Promotional pricing reverts to a noticeably higher list price after 3 months
Unlimited invoices and estimates on every paid tier
Mobile mileage tracking and tax-time reports built in from the cheapest plan
No permanent free plan — only a 30-day trial
Client limits on lower tiers can force an early upgrade
Team members and Advanced Payments are paid add-ons even on mid tiers
Wave
Genuinely free, unlimited invoicing and double-entry bookkeeping
Pro plan is cheap ($19/mo) relative to competitors’ entry tiers
Transparent per-transaction payment pricing, discounted on Pro
No dedicated tax-filing or quarterly-estimate tools like QuickBooks
Receipt capture and bookkeeping support cost extra ($11/mo and $149+/mo respectively)
Fewer integrations and a smaller feature set for scaling businesses
Who It’s a Good Fit For / Who Should Look Elsewhere
QuickBooks Solopreneur / Simple Start fits freelancers who most dread quarterly estimated taxes and want guided help inside the app, or anyone already using TurboTax. Look elsewhere if you want the cheapest possible tool, or if you’re frustrated that the old Self-Employed product no longer exists.
FreshBooks fits consultants, agencies-of-one, and service providers who send detailed invoices and proposals to a rotating set of clients. Look elsewhere if you have more than a handful of clients on a tight budget, since client caps push you up the pricing ladder quickly.
Wave fits freelancers and micro-businesses who want solid free bookkeeping and invoicing and don’t mind card-processing fees instead of a subscription. Look elsewhere if you need built-in tax guidance, multi-currency depth, or dedicated accountant collaboration tools.
Bottom Line
There’s no universal winner here — only a best fit. If you want $0 software and can tolerate payment fees, start with Wave. If client-facing polish (proposals, retainers, e-signatures) matters more than price, FreshBooks earns its higher cost. And if taxes are what keep you up at night, QuickBooks’ freelancer tier — now called Solopreneur rather than Self-Employed — still does that job best, just at a premium.
FAQ
Is QuickBooks Self-Employed still available?
No. QuickBooks Self-Employed is closed to new sign-ups. Intuit now sells QuickBooks Solopreneur for freelancers, with QuickBooks Online Simple Start as the next step up; existing Self-Employed customers are being migrated to Simple Start.
Does FreshBooks have a free plan?
No permanent free plan — FreshBooks offers a 30-day free trial, after which you need a paid plan starting at $23.00/month (Lite).
How does Wave make money if it’s free?
Wave charges per-transaction fees on card and bank payments (2.9%+$0.60 per card transaction on the free Starter plan, slightly discounted on Pro) and sells optional add-ons like receipt capture, payroll, and bookkeeping services.
Which tool is cheapest for a brand-new freelancer?
Wave’s Starter plan, at $0/month with unlimited invoicing and bookkeeping, is the cheapest functional option. You’ll only pay when you accept a card or bank payment.
Can I switch between these tools later without losing data?
All three let you export reports and transaction data, but moving between them isn’t seamless — budget time to re-enter clients, templates, and historical categorization if you switch providers.
Google doesn’t get the same AI-infrastructure headlines as Nvidia or OpenAI, but it quietly runs two pieces of foundational tech that power a huge share of the industry: custom TPU chips for AI training and inference, and the Go programming language that underpins much of the cloud-native world’s backend infrastructure. Neither gets much coverage on its own; together they say a lot about how Google builds for scale.
At a Glance
Technology
Category
Current state
Ironwood (TPU v7)
AI accelerator chip
GA; Google’s 7th-gen TPU, built for inference
Trillium (TPU v6e)
AI accelerator chip
GA; prior generation, still widely used
Go (Golang)
Programming language
Go 1.27 (Aug 2026), patch 1.27.3 (Oct 2026)
Short Verdict
TPUs are now a credible third option alongside Nvidia GPUs and AWS’s Trainium for serious AI workloads — Anthropic’s decision to scale Google TPU usage toward a million chips is hard to argue with. Go, meanwhile, has become unglamorous infrastructure plumbing in the best sense: not exciting, but running Kubernetes, Docker, and a huge share of cloud-native backend systems, with steady, incremental language improvements rather than hype-driven changes.
TPU Chips: Google’s AI Silicon
Google’s current-generation TPUs span two chips. Trillium (TPU v6e), generally available, delivers 918 TFLOPs of bf16 compute and 32GB of HBM per chip at 1,638GB/s bandwidth, scaling to 256-chip pods; Google claims it’s 67% more energy-efficient and offers 4.7x higher peak compute per chip than the previous generation. Ironwood (TPU v7), which Google calls its “first TPU built for the age of inference,” is the newer chip: 192GB of HBM per chip at 7.37TB/s bandwidth, scaling to pods of up to 9,216 chips delivering a claimed 42.5 exaflops. Google has described Ironwood as roughly 2x more power-efficient than Trillium in its original launch materials, though a separate Google Cloud page frames the generational jump as “4x better performance per chip” — both are Google’s own figures from different pages, worth noting as evolving marketing language rather than a hard contradiction.
TPUs are rented through Google Cloud as “slices” — a dedicated portion of a pod that behaves as one unified machine, orchestrated through Google Kubernetes Engine. The software stack leans heavily on JAX (a NumPy-style array computation library with composable transforms) and the XLA/OpenXLA compiler, though PyTorch and TensorFlow are also supported.
The clearest validation of TPUs at frontier scale comes from Anthropic, which announced in late 2025 that it’s expanding its use of Google Cloud TPUs to up to 1 million chips, adding well over a gigawatt of capacity coming online through 2026. Anthropic uses TPUs alongside Nvidia GPUs and AWS Trainium as part of a deliberate multi-chip strategy, rather than relying on any single vendor. Other named Google Cloud TPU customers include Citadel Securities (claiming 2–4x faster workloads at 30% lower cost) and Lightricks (claiming 40% more daily training steps after migrating to JAX/TPU). Reports that Apple trained some of its on-device Apple Intelligence models on TPUs rather than Nvidia GPUs are well-corroborated by tech press but are best described as “reportedly,” since this piece did not independently verify that detail against Apple’s own primary technical documentation.
Go: Quiet Infrastructure for the Cloud-Native World
Go was designed at Google starting in 2007 by Robert Griesemer, Rob Pike, and Ken Thompson, out of frustration with the build times and complexity of existing languages at Google’s scale, and open-sourced in 2009. Today go.dev describes it simply as “an open-source programming language supported by Google” — language evolution now runs through a public change-proposal process, though Google retains some structural control over the project’s infrastructure (code review runs on Google’s own Gerrit instance, and certain compliance rules require Google employee involvement in some changes).
The current stable release is Go 1.27 (released August 2026, with security patch 1.27.3 in October 2026), which added generic methods, new strict JSON handling packages, post-quantum cryptographic signature support, and cheaper small-object allocation. The prior release, Go 1.26, enabled a new garbage collector by default (claimed 10–40% reduction in GC overhead) and added faster cgo calls. Go’s defining feature remains its concurrency model: goroutines are lightweight functions the runtime multiplexes onto OS threads, cheap enough to create hundreds of thousands of at once, communicating through channels modeled on Hoare’s CSP rather than shared-memory locking.
Go’s real impact shows up in what’s built with it: Kubernetes, Docker, and Terraform — three of the most widely used pieces of cloud infrastructure software in existence — are all written in Go, which is part of why it’s become the default language for cloud-native tooling, CLIs, and backend network services, generally favored over Python for performance and over Java/C++ for its simpler build model and faster compile times.
Pros
TPUs: proven at frontier scale via Anthropic’s million-chip commitment, with a mature JAX/XLA software stack and strong perf-per-watt claims from Google.
TPUs: Cloud TPU slices let teams rent a fraction of a pod rather than committing to an entire cluster.
Go: exceptionally fast compile times and a concurrency model that scales to hundreds of thousands of lightweight goroutines without heavyweight thread management.
Go: steady, backward-compatible releases on a predictable six-month cycle, rather than disruptive breaking changes.
Cons
TPUs: tied exclusively to Google Cloud, unlike Nvidia GPUs which run on every major cloud.
TPUs: Google’s own marketing language around generational performance gains (Ironwood’s “2x” vs “4x” framing in different materials) isn’t always perfectly consistent.
Go: its standard library and idioms deliberately avoid some abstractions (generics arrived late, no traditional class hierarchy), which some developers coming from Java or C++ find limiting.
Who It’s a Good Fit For
Teams already on Google Cloud training large models at scale are a natural fit for TPUs, especially with JAX-based workflows. For Go: teams building cloud infrastructure tooling, CLIs, network services, or anything where fast compilation, simple deployment (a single static binary), and high-concurrency networking matter more than maximal runtime performance or compile-time memory safety.
Who Should Look Elsewhere
Teams not already on Google Cloud, or needing cross-cloud portability, will find Nvidia GPUs or AWS’s Trainium more practical than TPUs. For Go: teams needing compile-time memory-safety guarantees without a garbage collector should look at Rust; teams needing dynamic prototyping speed over performance may still prefer Python.
Bottom Line
TPUs and Go don’t get bundled together often, but both reflect the same Google trait: building deeply vertically integrated infrastructure, then letting the results speak through adoption rather than marketing noise. TPUs have earned a real seat at the AI-chip table via Anthropic’s scale commitment; Go has quietly become the default language underneath most of the cloud-native stack most engineers use every day.
FAQ
Can I use TPUs outside Google Cloud? No. TPUs are proprietary Google silicon, available only through Google Cloud’s Cloud TPU service.
Is Go still controlled by Google? Go is open-source and changes go through a public proposal process, but Google retains meaningful structural control — the canonical repository, code review tooling, and certain compliance requirements still run through Google.
What major software is written in Go? Kubernetes, Docker, and Terraform are among the best-known infrastructure projects written in Go, which is a large part of why it’s the default language for cloud-native tooling.
Every custom AI chip from AWS, Google, and everyone else gets measured against one thing: Nvidia’s data center GPU lineup and the CUDA software stack built around it. Nvidia’s advantage isn’t just silicon anymore — it’s a decade-plus of software that makes its GPUs the default choice even when a competitor’s chip is cheaper on paper. Here’s what’s actually in the current lineup.
Compiler, inference engines, prebuilt model microservices
Short Verdict
Nvidia’s hardware lead is real but no longer the whole story — H200’s gains over H100 are almost entirely about memory, not raw compute, and custom chips from AWS, Google, and others are closing the hardware gap in specific workloads. What keeps Nvidia dominant is CUDA: a massive, mature software ecosystem (cuDNN, TensorRT, NIM microservices, the AI Enterprise suite) that every major cloud supports natively, which makes switching away from Nvidia a real engineering cost even when a competitor’s chip looks better on a spec sheet.
The Current Lineup: Hopper and Blackwell
The H100 and its successor H200 (both Hopper-generation) remain widely deployed. Nvidia’s own spec sheets show something worth calling out directly: H200’s FP8 and FP16 compute throughput is identical to H100’s on paper — the real upgrade is memory, with H200 carrying 141GB of HBM3e at 4.8TB/s versus H100’s smaller, slower memory pool. Nvidia claims this translates to roughly 1.6–1.9x faster inference on large models like Llama 2 70B and GPT-3 175B, which tracks with memory-bound inference workloads benefiting disproportionately from more bandwidth.
The newer Blackwell generation is a bigger architectural jump. The Blackwell GPU die itself packs 208 billion transistors across two reticle-limited dies fused by a 10TB/s link, presented to software as a single GPU. At rack scale, the flagship GB300 NVL72 combines 72 Blackwell Ultra GPUs with 36 Grace CPUs (2,592 Arm Neoverse V2 cores) into one liquid-cooled unit, with 20TB of GPU memory at up to 576TB/s of aggregate bandwidth and NVLink providing 130TB/s of GPU-to-GPU bandwidth within the rack. Nvidia claims this delivers up to 65x more AI compute than Hopper-based systems for reasoning-style inference workloads — a large claim worth treating as a vendor benchmark rather than an independently verified figure, since Nvidia doesn’t publish the full comparison methodology.
Nvidia has also announced its next architecture, Vera Rubin, as a rack-scale “agentic AI supercomputer” built from co-designed Rubin GPUs and Arm-based Vera CPUs. At the time of writing, Nvidia’s own dedicated spec page for Vera Rubin wasn’t accessible for detailed verification, and most specific numbers circulating about it (core counts, exact shipping dates) come from secondary tech press rather than Nvidia’s own published specs — treat Vera Rubin as a confirmed-to-exist roadmap product with unconfirmed specifics for now.
The Real Moat: CUDA and the Software Stack
Hardware specs only tell half the story. Nvidia’s CUDA Toolkit — the compiler, libraries, and runtime that let developers program GPUs directly from C++, Python, or Fortran — has over a decade of accumulated tooling built around it: cuDNN for deep-learning primitives (accelerating PyTorch, TensorFlow, JAX, and others), TensorRT for inference optimization (Nvidia claims up to 36x speedup versus CPU-only inference in some configurations, an unqualified marketing figure worth independently benchmarking for your own workload), and NIM (NVIDIA Inference Microservices), which packages optimized foundation models into containers deployable with a single command and an OpenAI-compatible API.
Above that sits NVIDIA AI Enterprise, a commercial software suite bundling NIM, pre-built “Blueprints,” the NeMo framework for LLM training, and Omniverse — available through every major cloud marketplace (AWS, Azure, GCP, and OCI) as well as direct from Nvidia. This is the part of Nvidia’s business that’s genuinely hard for AWS, Google, or anyone else to replicate quickly: switching chip vendors means re-validating an entire software stack, not just swapping hardware.
Available Everywhere, Unlike the Alternatives
Unlike AWS’s Trainium or Google’s TPUs, Nvidia GPUs are available across every major cloud: AWS (P5/P5e/P5en for Hopper, P6-B200/B300 and P6e-GB200 UltraServers for Blackwell), Azure (ND H200 v5 series), Google Cloud (A3/A3 Ultra for Hopper, A4/A4X for Blackwell), and Oracle Cloud Infrastructure (H100 through GB200 at supercluster scale). That universal availability, combined with CUDA’s maturity, is why Nvidia GPUs remain the default starting point for most AI teams even as custom silicon alternatives multiply.
Pros
Available on every major cloud, with no single-vendor lock-in the way custom chips (Trainium, TPUs) require.
CUDA’s software maturity (cuDNN, TensorRT, NIM, broad framework support) remains unmatched by any competing chip ecosystem.
Rack-scale Blackwell systems (GB200/GB300 NVL72) deliver genuine architectural advances in interconnect bandwidth and memory, not just incremental clock-speed bumps.
NIM microservices meaningfully lower the barrier to deploying optimized models in production without deep inference-engineering expertise.
Cons
Many of Nvidia’s headline performance multipliers (“50x,” “65x,” “36x”) are vendor benchmarks without disclosed methodology — useful as directional signals, not hard guarantees for your workload.
H200’s gains over H100 are almost entirely memory-driven, not compute-driven, which is easy to miss if you only read the marketing bullet points.
Production use of NIM and AI Enterprise requires a paid license beyond the free developer tier.
Demand still regularly outstrips supply for the newest Blackwell-class hardware, which can mean real-world lead times longer than cloud providers advertise.
Who It’s a Good Fit For
Teams that want cloud portability, access to the broadest possible software ecosystem, or need to deploy pre-optimized models quickly via NIM rather than building custom inference pipelines. Also the default safe choice for teams without the engineering bandwidth to port workloads to a custom-chip SDK like AWS’s Neuron or Google’s JAX/TPU stack.
Who Should Look Elsewhere
Teams locked into a single cloud who are willing to invest engineering time to port to that cloud’s custom silicon (Trainium on AWS, TPUs on Google Cloud) may find meaningfully lower costs at scale, trading some ecosystem breadth for price-performance.
Bottom Line
Nvidia’s hardware is still excellent, but the real reason it remains the default is CUDA — the software ecosystem built around its GPUs over more than a decade, which every cloud supports and almost every AI framework targets first. Custom chips are catching up on raw price-performance for specific workloads, but replicating Nvidia’s software depth is a much longer project than matching its silicon specs.
FAQ
Is H200 faster than H100? Only in memory-bound workloads. Nvidia’s own specs show identical FP8/FP16 compute throughput between the two — H200’s advantage is its larger, faster memory (141GB HBM3e vs H100’s smaller pool), which Nvidia claims yields up to 1.9x faster inference on large models.
What is NIM? NVIDIA Inference Microservices — prebuilt, optimized containers for deploying foundation models with an OpenAI-compatible API, requiring a paid AI Enterprise license for production self-hosting beyond the free developer tier.
Can I run Nvidia GPUs on any cloud? Yes. Current-generation Nvidia GPUs are available on AWS, Azure, Google Cloud, and Oracle Cloud Infrastructure, among others — unlike custom chips such as AWS Trainium or Google’s TPUs, which are tied to their respective clouds.
AWS has spent years building its own silicon rather than relying entirely on Nvidia for AI compute — Trainium for training, Inferentia for inference. The pitch is simple: comparable or better performance at meaningfully lower cost than GPU instances, at a scale few other companies can match. Anthropic’s enormous “Project Rainier” cluster is the proof point AWS leans on hardest. Here’s what these chips actually are and how AWS’s own numbers hold up.
At a Glance
Chip
Role
Current instance types
Trainium2
Large-scale model training
Trn2 (16 chips), Trn2 UltraServer (64 chips)
Trainium3
Next-gen training (3nm process)
UltraServers up to 144 chips
Inferentia2
Inference
Inf2 (up to 12 chips/instance)
Short Verdict
Trainium and Inferentia are real, shipping, and used at serious scale — this isn’t vaporware. Anthropic’s Project Rainier cluster, reportedly built from hundreds of thousands of Trainium2 chips, is the single strongest piece of evidence that these chips can handle frontier-scale training. AWS’s own cost/performance claims (30–40% better price-performance than its Nvidia-based instances) are real numbers from AWS, but AWS is comparing against its own GPU instance pricing, not publishing head-to-head benchmarks naming Nvidia directly, so treat the comparison as AWS-favorable by construction rather than neutral.
What Trainium and Inferentia Are
Trainium is AWS’s custom silicon for large-scale model training. The current generation in general availability, Trainium2, ships in the Trn2 instance (16 chips connected via NeuronLink, rated at 20.8 peak petaflops) and the Trn2 UltraServer, which combines four Trn2 servers into a single 64-chip unit with 83.2 peak petaflops. AWS’s own GA announcement claims Trn2 delivers 30–40% better price-performance than its existing Nvidia GPU-based P5e/P5en instances — a real AWS-published number, though it’s a comparison against AWS’s own competing instance line rather than an independent benchmark.
Trainium3, announced at re:Invent in December 2024, is AWS’s first chip built on a 3nm process. Per-chip, AWS claims roughly 2x the compute throughput of Trainium2 and 144GB of HBM3e memory at 4.9TB/s bandwidth (1.7x Trainium2’s bandwidth). Trainium3 UltraServers scale up to 144 chips, with AWS claiming roughly 4x the performance of Trainium2 UltraServers. AWS’s own materials describe “UltraClusters 3.0” scaling to hundreds of thousands of chips.
On the inference side, Inferentia2 powers the EC2 Inf2 instance family (up to 12 chips per instance) and is the first Inferentia generation to support distributed inference across multiple chips. AWS claims up to 4x higher throughput and up to 10x lower latency than the original Inferentia, with up to 190 TFLOPS of FP16 performance per chip and 32GB of HBM — four times the memory of the first-generation chip.
The Anthropic Connection
The clearest evidence that Trainium works at frontier scale is Anthropic’s “Project Rainier” cluster, confirmed directly by AWS: a compute cluster built from nearly half a million Trainium2 chips, organized into tens of thousands of 64-chip UltraServers spread across multiple U.S. data center sites (AWS names one, in St. Joseph County, Indiana). AWS describes the cluster as giving Anthropic more than 5x its previous training compute, with Claude expected to run on more than a million Trainium2 chips across training and inference combined. It’s worth noting Anthropic uses a multi-chip strategy — it also runs workloads on Nvidia GPUs and, separately, on Google’s TPUs — so Trainium is one leg of its infrastructure, not the only one.
AWS’s own Trainium2 GA announcement also names Databricks (claiming up to 30% lower total cost of ownership) and poolside (claiming 40% savings versus AWS’s P5 GPU instances) as customers, alongside integrations with Hugging Face’s Optimum Neuron and Google’s JAX via OpenXLA. Reports that Apple also uses Trainium chips come from secondary tech press rather than an AWS- or Apple-published primary source, so that specific claim should be read as “reportedly,” not confirmed.
The Software Layer: Neuron SDK
Both chip families run on AWS’s Neuron SDK, which includes a compiler and runtime, native integration with PyTorch, JAX, and TensorFlow, and support for more than 100,000 models from the Hugging Face hub. For teams that want lower-level control, the Neuron Kernel Interface (NKI) allows writing custom kernels directly. Orchestration is supported through Ray, Slurm, Amazon EKS, ECS, AWS Batch, and SageMaker HyperPod — meaning teams aren’t locked into a single orchestration tool to use these chips.
Pros
Proven at genuinely enormous scale — Anthropic’s Project Rainier cluster is one of the largest AI training clusters AWS has ever disclosed.
AWS-published price-performance claims (30–40% better than its own Nvidia-based instances) are real numbers, not vague marketing language.
Broad framework support (PyTorch, JAX, TensorFlow) and orchestration flexibility (EKS, Slurm, SageMaker HyperPod, Ray) reduce lock-in risk at the tooling layer.
A full generational roadmap already in motion — Trainium3 is shipping on a new 3nm process rather than being a one-off project.
Cons
AWS’s cost/performance comparisons are against its own GPU-based instances, not independently verified head-to-head benchmarks against Nvidia hardware on neutral terms.
Available only on AWS — there’s no equivalent of running Trainium workloads on another cloud, unlike Nvidia GPUs which are available everywhere.
Ecosystem and tooling maturity, while improving fast, still trails the sheer breadth of the CUDA ecosystem that’s grown around Nvidia GPUs over more than a decade.
Who It’s a Good Fit For
Teams already committed to AWS who want meaningfully lower training or inference costs than Nvidia-based EC2 instances and can tolerate some additional porting/tuning work via the Neuron SDK. Large-scale training teams in particular, given the proof point of Project Rainier running at this scale successfully.
Who Should Look Elsewhere
Teams that need portability across clouds, rely heavily on CUDA-specific tooling or libraries with no Neuron equivalent, or are running smaller workloads where the cost difference won’t offset the porting effort, may be better served staying on standard Nvidia GPU instances for now.
Bottom Line
Trainium and Inferentia are no longer experimental — they’re running some of the largest AI training workloads in the world, with real, AWS-published cost advantages over the company’s own GPU instances. Whether that translates into an advantage over Nvidia hardware broadly depends on workload specifics AWS doesn’t publish in a neutral, third-party-verified form, but the scale at which these chips are now deployed is itself a serious data point.
FAQ
Is Trainium only usable on AWS? Yes. Trainium and Inferentia are custom AWS silicon, available exclusively through AWS EC2 and related AWS services.
Does Anthropic only use AWS chips? No. Anthropic uses a multi-chip strategy that includes AWS Trainium, Nvidia GPUs, and Google’s TPUs, in addition to the large Trainium2-based Project Rainier cluster built with AWS.
How does Trainium’s software ecosystem compare to CUDA? The Neuron SDK supports PyTorch, JAX, and TensorFlow and is actively developed, but it’s newer and narrower than Nvidia’s CUDA ecosystem, which has had over a decade to accumulate libraries, tools, and community support.
While AWS, Google, and Microsoft fight over GPU supercluster bragging rights, IBM is running a different playbook: AI infrastructure built around its own Power chips, dedicated AI accelerator silicon, and a software layer (watsonx) aimed squarely at regulated enterprises that want AI running on-premises, not just in a public cloud. Here’s what’s actually in IBM’s stack.
At a Glance
Component
What it is
Status
Power11
IBM’s current server CPU family
Shipping since July 2025
Telum II
Mainframe processor with on-chip AI accelerator
Powers IBM z17 / LinuxONE 5
Spyre Accelerator
Dedicated AI accelerator card (32 cores)
Commercially available on Z/LinuxONE; rolling out to Power11
watsonx
IBM’s AI platform (ai / data / governance / Orchestrate)
Runs on Red Hat OpenShift AI, on-prem or IBM Cloud
Short Verdict
IBM isn’t trying to out-GPU Nvidia’s hyperscaler customers, and it shouldn’t be judged on that basis. Its bet is that a large slice of enterprise AI workloads — banking, insurance, government, telecom — need to run where the data already lives, under existing compliance controls, with hardware-level reliability guarantees that general-purpose cloud VMs don’t offer. Power11 plus the Telum II/Spyre accelerator lineup plus watsonx is a coherent answer to that specific problem. It is a weak answer if what you actually want is the cheapest possible path to training a frontier-scale foundation model.
What’s in IBM’s AI Infrastructure Stack
Power11 is IBM’s current-generation Power server CPU family, announced in July 2025 and the first time IBM simultaneously launched high-end, mid-range, and edge/low-end Power models together. The lineup spans the S1112 (edge/remote deployments with built-in AI acceleration), the S1122 and S1124, the E1150 (up to 120 Power11 cores, 16TB of DDR5 per 4U chassis), and the flagship E1180. IBM’s own materials don’t publish per-chip clock speeds or process node for Power11 — a genuine gap in IBM’s public documentation — but IBM does claim, in its own internal benchmarks, up to 55% faster core performance than Power9 on commercial workloads and up to 45% more processor resources than Power10 on its lower-end systems, along with roughly double the performance-per-watt of comparable x86 servers.
IBM’s AI-specific silicon sits one layer up. Telum II, built on a 5nm process and first detailed at Hot Chips in 2024, is the processor inside IBM’s z17 mainframe and LinuxONE 5 systems; it carries an on-chip AI accelerator and, in a fully configured system drawer, is rated for up to 192 TOPS of on-chip AI inference — aimed at running fraud-detection and risk models directly alongside transaction processing, with no round trip to a separate AI system. The Spyre Accelerator is IBM’s dedicated AI accelerator card: 32 AI cores on a 5nm, 75-watt PCIe card, now commercially available for IBM Z and LinuxONE systems (GA’d in late 2025) and extended to Power11 shortly after. Up to 48 Spyre cards can be clustered on Z/LinuxONE, and up to 16 on Power systems, for larger on-premises inference workloads.
watsonx: The Software Layer
watsonx is IBM’s umbrella AI platform, split into several named products: watsonx.ai (a studio for building and deploying custom AI applications, including IBM’s own Granite foundation models), watsonx.data (data integration and governance across hybrid and multicloud sources), watsonx.governance (AI risk management, regulatory compliance, and explainability tooling), and watsonx Orchestrate (building and deploying AI agents for business process automation).
Critically, watsonx is built on top of Red Hat OpenShift, and watsonx.ai specifically uses OpenShift AI’s accelerator support (which includes GPU kernel contributions from Nvidia, AMD, and Intel) and KServe for model serving. That means watsonx isn’t locked to IBM’s own chips — it can serve models like Llama 3 and Mistral alongside IBM’s own Granite models, and can be deployed fully air-gapped for workloads with strict data-isolation requirements. IBM has also confirmed that watsonx.data is being made available directly on Power11 and that Power11 integrates with Red Hat OpenShift AI.
Pros
On-chip AI acceleration (Telum II) built directly into transaction-processing hardware, aimed at real-time fraud/risk use cases banks and insurers actually run.
watsonx runs on open infrastructure (Red Hat OpenShift AI) rather than a proprietary stack, and supports third-party models alongside IBM’s own Granite models.
Strong hybrid/on-prem story: workloads can run fully air-gapped where data residency or regulatory rules require it.
Built-in quantum-safe encryption and a hardware-level ransomware detection feature (“Power Cyber Vault”) on Power11.
Cons
IBM does not publish basic chip specs (clock speed, process node, per-core detail) for Power11 the way competitors routinely do — third-party outlets fill in some of these numbers, but they aren’t confirmed directly by IBM.
Not positioned, and not competitive, for large-scale foundation-model pretraining at the scale AWS, Google, or Oracle’s GPU superclusters support.
The AI accelerator story is currently split across two different chip families (Telum II for mainframes, Spyre as an add-in card) rather than one unified roadmap, which adds complexity to evaluating the lineup.
Who It’s a Good Fit For
Banks, insurers, telcos, and government agencies that already run IBM Z, LinuxONE, or Power infrastructure and need AI inference (fraud detection, risk scoring, document processing) running close to transactional data under strict compliance and uptime requirements. Also a fit for enterprises that want a hybrid-cloud AI platform built on open infrastructure (OpenShift) rather than a single public cloud’s proprietary stack.
Who Should Look Elsewhere
Teams training large foundation models from scratch, or anyone who just wants the cheapest/fastest path to a large GPU cluster, should look at AWS, Google Cloud, Oracle, or Nvidia’s own cloud partners instead — IBM’s AI hardware story is about enterprise inference and governance, not frontier-scale training.
Bottom Line
IBM’s AI infrastructure play is narrower than the hyperscalers’ but more coherent for its target customer: enterprises that need AI inference running on the same hardware as their core transaction systems, under compliance regimes that make “just use a public cloud GPU instance” a non-starter. Power11, Telum II, Spyre, and watsonx add up to a real, differentiated hybrid-AI stack — just not a frontier-training one.
FAQ
Is watsonx only for IBM hardware? No. watsonx runs on Red Hat OpenShift AI and can be deployed on IBM Power, IBM Cloud, other public clouds, or on-premises, and it can serve non-IBM models like Llama 3 and Mistral alongside IBM’s own Granite models.
What’s the difference between Telum II and Spyre? Telum II is the main processor inside IBM’s z17 mainframe and LinuxONE 5 systems, with an AI accelerator built into the chip itself. Spyre is a separate, dedicated AI accelerator card that plugs into Z, LinuxONE, or Power systems for additional AI inference capacity.
Can IBM’s infrastructure train large language models from scratch? It’s not positioned or marketed for that. IBM’s AI hardware emphasizes on-premises inference and governance for enterprise workloads; large-scale pretraining is better suited to GPU-cluster-focused clouds like AWS, Google Cloud, or Oracle.
Oracle spent most of the cloud era as an afterthought behind AWS, Azure, and Google Cloud. In AI infrastructure, that’s changed: Oracle Cloud Infrastructure (OCI) now runs some of the largest publicly disclosed GPU superclusters in the industry, and it’s become a default landing spot for AI labs that need massive GPU capacity fast. Here’s what OCI actually offers for AI training and inference, and where its claims hold up.
At a Glance
Offering
What it is
Scale (per Oracle)
OCI Supercluster
Bare-metal GPU clusters with RDMA networking
Up to ~131,000 NVIDIA B200 GPUs; roadmap to 1M+ GPUs by end of 2027
GPU shapes
NVIDIA H100/H200/B200/GB200, AMD MI300X
Bare-metal, 8-GPU instances, no hypervisor overhead
OCI Enterprise AI / Generative AI
Managed LLM, RAG, and AI agent tooling
Built on OCI Data Science and OCI’s generative AI service
Short Verdict
OCI is a legitimate option for large-scale GPU training, not just a marketing claim. Oracle publishes real bare-metal pricing per GPU-hour (rather than burying it behind a sales call for every tier), its RDMA cluster networking numbers are credible, and it has landed genuine customers like Databricks/MosaicML and Cohere. It is not yet a broad AI platform the way AWS or Google Cloud are — OCI’s AI-specific managed services are thinner, and some of its own marketing pages are inconsistent on basic numbers. For teams that mainly need raw GPU capacity at competitive pricing, OCI is worth a serious look. For teams that want a mature ecosystem of managed AI services around the GPUs, AWS and Google Cloud are still further ahead.
What OCI’s AI Infrastructure Actually Is
OCI’s pitch for AI workloads centers on bare-metal GPU instances — meaning customers get direct hardware access with no hypervisor layer between them and the silicon — connected by Oracle’s own RDMA cluster network. Oracle calls the resulting pooled hardware an “OCI Supercluster.” According to Oracle’s own AI infrastructure page, a single OCI Supercluster can scale up to roughly 131,000 NVIDIA B200 GPUs, more than 100,000 GB200 Grace Blackwell Superchips, 65,536 H200 GPUs, or 16,384 AMD MI300X GPUs, depending on which generation of hardware a customer provisions. Oracle has also stated a roadmap target of extending this architecture to more than 1 million NVIDIA GPUs with over 3 gigawatts of capacity by the end of 2027 — a forward-looking target, not a currently deployed figure.
Worth flagging directly: Oracle’s own AI infrastructure page is not perfectly internally consistent. The written copy cites “up to 131,072” B200 GPUs in one place while an accompanying diagram on the same page shows 128,000 — a minor discrepancy, but one that suggests these maximum-scale figures should be read as approximate marketing ceilings rather than exact, audited numbers.
GPU Shapes and Pricing
Unlike some competitors, Oracle publishes real per-GPU hourly pricing for several of its bare-metal shapes directly in its own product announcements:
BM.GPU.H200.8 — 8x NVIDIA H200 GPUs (141GB HBM3e each, 4.8TB/s bandwidth) via NVLink, dual 56-core Intel Sapphire Rapids CPUs, 3TB DDR5 RAM, 8×3.84TB local NVMe. Oracle’s own GA announcement states this ships at $10 per GPU per hour — the same price as the prior-generation H100 shape.
BM.GPU.MI300X.8 — 8x AMD MI300X GPUs (192GB HBM3 each, ~1.5TB total), dual 56-core Sapphire Rapids CPUs, 2TB DDR5 RAM. Oracle’s own GA announcement states this ships at $6.00 per GPU per hour.
GB200 NVL72 / B200 — Oracle’s current Blackwell-generation shapes, offered via OCI Supercluster at scale; Oracle does not publish a flat per-GPU hourly rate for these on its main marketing pages, and we could not independently confirm a specific dollar figure for this tier from an Oracle-published source.
Oracle’s cluster-level networking claims include RDMA over Converged Ethernet (RoCE v2) using NVIDIA ConnectX-7 NICs, cluster bandwidth up to 3,200 Gb/s per 8-GPU instance, and sub-10-microsecond network latency (Oracle’s own materials give slightly different numbers in different places — as low as 2.5 microseconds in one spot and a 2.5–9.1 microsecond range in another, which is worth noting rather than papering over). RDMA networking, block storage, and the first 10TB of monthly egress are included at no additional charge, which is a genuine differentiator versus cloud providers that meter network egress aggressively.
Managed AI Services on Top of the Hardware
Above the raw GPU layer, Oracle offers OCI Data Science (managed notebooks and an Accelerated Data Science SDK, billed only for the compute and storage actually consumed) and a generative AI layer that Oracle has marketed under more than one name over time — it has documented an “OCI Generative AI Service” for LLM and RAG workflows, and its current top-level marketing increasingly uses the name “OCI Enterprise AI” for AI app, agent, and governance tooling. Readers evaluating this layer specifically should check Oracle’s current docs directly, since the branding appears to be in flux.
On the partnership side, Oracle has a deep full-stack relationship with NVIDIA (NVIDIA AI Enterprise is built into the OCI Console, NVIDIA NIM is available via OCI Marketplace, and GB200/GB200 NVL72 racks are deployed on OCI) and a separate relationship with AMD around the MI300X shape.
Pros
Published, bare-metal per-GPU-hour pricing for H200 and MI300X, rather than quote-only pricing for every tier.
No hypervisor overhead on bare-metal shapes, and RDMA networking, storage, and the first 10TB of egress included free.
Real supercluster scale, with concrete customer wins (Databricks/MosaicML, Cohere, Palantir, Stanford among others cited by Oracle).
Both NVIDIA and AMD GPU options, rather than a single-vendor lock-in.
Cons
Thinner managed-AI-service ecosystem than AWS Bedrock/SageMaker or Google Vertex AI, and the branding of Oracle’s generative AI layer has shifted, which makes it harder to evaluate from the outside.
Oracle’s own marketing pages contain small internal inconsistencies in headline numbers (GPU counts, latency figures), so treat maximum-scale claims as approximate.
Oracle rarely names AWS, Azure, or Google directly in comparative claims (“up to 220% better pricing than other cloud providers”), which makes its competitive claims hard to independently check.
Flat per-GPU pricing isn’t published for every GPU generation, so budgeting for the newest Blackwell-class shapes may still require a sales conversation.
Who It’s a Good Fit For
Teams training large models who need a lot of bare-metal GPU capacity, want predictable per-GPU pricing without egress surprises, or are already running Oracle Database/applications and want to keep AI workloads in the same cloud. It’s also a reasonable second-cloud option for teams hedging against GPU scarcity on AWS or Azure.
Who Should Look Elsewhere
Teams that want a deep, mature managed-AI-services layer (fine-tuning pipelines, model registries, a wide first-party model catalog) with less DIY infrastructure work will likely find AWS, Google Cloud, or Azure more complete today. Teams that need the absolute newest Blackwell-class hardware at a clearly published flat rate may also need to get a quote rather than relying on OCI’s public pricing pages alone.
Bottom Line
OCI’s AI infrastructure claims are largely backed by real, Oracle-published numbers — bare-metal GPU shapes with transparent per-GPU-hour pricing on at least two major tiers, credible RDMA networking specs, and genuine large customers. It’s a credible fourth option alongside AWS, Azure, and Google Cloud for raw GPU capacity, with the caveat that its managed AI-service layer and some of its headline marketing numbers are less polished and less consistent than its hyperscaler rivals.
FAQ
Does OCI support both NVIDIA and AMD GPUs? Yes. OCI offers NVIDIA H100, H200, B200, and GB200 Grace Blackwell Superchip shapes, plus AMD MI300X bare-metal shapes.
Is OCI cheaper than AWS or Azure for GPU training? Oracle claims significantly better price-performance than “other cloud providers,” but does not name competitors directly or publish a verifiable methodology, so this should be benchmarked for your specific workload rather than taken at face value.
Who is actually using OCI for AI training? Oracle has publicly named Databricks/MosaicML, Cohere, Palantir, Stanford, Suno, and together.ai, among others, as customers running AI workloads on OCI.
Once a system splits into enough microservices, securing and observing the traffic between them becomes its own problem, separate from the application code. A service mesh handles that by moving encryption, routing, and telemetry into infrastructure that sits alongside your services, and Istio and Linkerd are the two CNCF-graduated projects that dominate this space.
At a Glance
Istio
Linkerd
Data plane proxy
Envoy (general-purpose), or ztunnel/waypoint in ambient mode
Yes, automatic via the Identity control-plane component
What a Service Mesh Actually Does
A service mesh provides mutual TLS (mTLS) encryption between services, layer-7 traffic management (routing, retries, timeouts, circuit breaking, fault injection), and observability (metrics, tracing, and logs), all without requiring changes to application code. It typically works by intercepting network traffic through a proxy running alongside each service, which is also why the two major implementations differ mainly in what that proxy looks like and how heavy it is.
Istio
Istio supports two data-plane modes. Sidecar mode pairs an Envoy proxy with each service, coordinated by the Istiod control plane. Ambient mode removes the sidecar entirely: node-level ztunnel proxies handle layer-4 traffic, and optional waypoint proxies add layer-7 features only where needed, communicating over Istio’s own HBONE secure-tunneling protocol. Istio’s feature set, per its own documentation, includes mTLS with certificate management, rich traffic management (routing, traffic shifting, fault injection, timeouts, circuit breaking, traffic mirroring, locality-aware load balancing), observability integrations with Prometheus, Grafana, Kiali, and Jaeger, JWT-based authorization, and WASM/Lua extensibility for the proxy itself. Istio’s own blog states it graduated within the CNCF on July 12, 2023; it had been accepted into the CNCF (at the incubation stage) back on September 30, 2022, which is a separate, earlier milestone from graduation.
Linkerd
Linkerd’s control plane consists of three components: Destination (service discovery, policy, and service-profile data), Identity (a certificate authority that issues short-lived certs to proxies at startup), and the proxy injector (an admission controller that adds sidecars via a simple namespace or pod annotation). Its data plane, linkerd2-proxy, is a purpose-built Rust proxy rather than a general-purpose one like Envoy, offering zero-config HTTP/HTTP2/WebSocket/TCP proxying, latency-aware load balancing, automatic mTLS (certificates issued transparently by the Identity component), Prometheus metrics, and on-demand “tap” diagnostics. As of Linkerd 2.20, its proxy runs as a native Kubernetes sidecar by default. Linkerd was the first service mesh to reach CNCF graduation, announced July 28, 2021, roughly two years before Istio reached the same milestone.
The Real Difference: General-Purpose vs. Purpose-Built
Istio’s choice of Envoy as its proxy (in sidecar mode) gives it a broader, more configurable feature set, including scriptable extensibility via WASM and Lua, at the cost of a heavier footprint and a steeper learning curve — criticisms that pushed Istio toward building its sidecar-free ambient mode. Linkerd’s purpose-built Rust proxy is deliberately narrower in scope, trading some configurability for a simpler operational model and a lighter resource footprint, a positioning difference both projects’ own communities have highlighted since Linkerd’s earlier graduation. Neither project’s official documentation currently publishes a specific CPU or memory benchmark comparing the two proxies directly, so treat any specific numbers you see in third-party comparisons as that source’s own test, not an official spec from either project.
Who It’s a Good Fit For
Istio fits organizations that need the broadest traffic-management and extensibility feature set, including WASM-based custom policy logic, and have the operational capacity to manage a more complex system (or are willing to adopt ambient mode to reduce sidecar overhead). Linkerd fits teams that want mTLS, observability, and basic traffic management with the simplest possible operational model and lowest resource overhead, without needing Istio’s deeper extensibility.
Bottom Line
Both Istio and Linkerd are mature, CNCF-graduated projects solving the same core problems — encrypted service-to-service traffic, traffic management, and observability — through genuinely different engineering choices. Istio bets on Envoy’s generality and depth (with ambient mode addressing its historical weight), while Linkerd bets on a narrower, purpose-built proxy for simplicity. Neither is objectively “better”; the right choice depends on whether your team needs Istio’s extensibility or values Linkerd’s operational simplicity more.
FAQ
Which service mesh graduated from CNCF first? Linkerd, in July 2021. Istio followed roughly two years later, graduating in July 2023.
What is Istio’s ambient mode? A sidecar-free data-plane mode that uses node-level ztunnel proxies for layer-4 traffic and optional waypoint proxies for layer-7 features, aimed at reducing the resource overhead associated with Istio’s traditional per-pod Envoy sidecars.
Do both provide automatic mTLS? Yes. Istio manages certificates through Istiod, and Linkerd issues short-lived certificates to proxies automatically through its Identity control-plane component, in both cases without requiring application code changes.
Message queues and brokers decouple services so one part of a system can keep working even if another is slow or temporarily down. Kafka, RabbitMQ, and Amazon SQS solve this with three genuinely different architectures, and picking the wrong one for your ordering and delivery needs tends to surface as a production bug months later.
At a Glance
Kafka
RabbitMQ
Amazon SQS
Model
Distributed log, partitioned topics
Traditional broker, exchanges & queues (AMQP 0-9-1)
Fully managed queue service
Ordering
Guaranteed within a partition only
No explicit official guarantee stated
Standard: best-effort; FIFO: strict within a message group
Delivery
At-least-once by default; exactly-once via idempotent producer + transactions
At-least-once with consumer acks; redelivery on failure
Standard: at-least-once; FIFO: exactly-once via dedup ID
Operated by you or managed
Self-managed (or via a managed Kafka service)
Self-managed (or via a managed RabbitMQ service)
Fully managed by AWS
Kafka: A Distributed Log
Kafka organizes data into topics split across partitions, with a cluster of broker servers replicating each partition (commonly with a replication factor of 3) for durability. A producer writes an event to one partition (events sharing a key always land on the same partition), and producers and consumers are fully decoupled from each other. Ordering is guaranteed only within a single partition, not across an entire topic. By default, Kafka delivers at-least-once; at-most-once delivery is possible with a fire-and-forget producer, and exactly-once delivery is achievable through an idempotent producer (broker-assigned producer IDs and sequence numbers that dedupe retried sends, available since version 0.11.0.0) combined with transactions that write atomically across partitions, paired with a consumer set to read_committed isolation to ignore aborted messages. Kafka’s own documentation describes its scalability and performance qualitatively rather than citing one fixed throughput number, so be cautious of any single “messages per second” figure presented as an official spec.
RabbitMQ: A Traditional Message Broker
RabbitMQ implements the AMQP 0-9-1 protocol: publishers send messages to exchanges, which route them into queues via bindings and routing keys. Exchange types include direct, fanout, topic, and headers, and every queue is automatically bound to a nameless default direct exchange by its own name. Consumers must acknowledge a message before the broker removes it; an unacknowledged message is redelivered if its consumer disconnects, and a negative-acknowledgment (nack) extension supports bulk rejection. Persistence requires both a durable queue and a message sent in persistent mode — missing either one means messages won’t survive a broker restart. RabbitMQ’s official documentation does not explicitly state a strict ordering guarantee at the queue level; in practice, a single consumer reading from a single queue without any redeliveries behaves in FIFO order, but that isn’t stated as a formal guarantee the way Kafka’s partition ordering or SQS’s FIFO queues are.
Amazon SQS: Fully Managed Queues
SQS offers two queue types with genuinely different guarantees. Standard queues deliver at-least-once (duplicates are possible) with best-effort, not guaranteed, ordering, and AWS describes their throughput as very high and effectively unlimited API calls per second, scaling automatically. FIFO queues guarantee exactly-once processing (via a message deduplication ID or content-based deduplication) and strict ordering within each message group; throughput without batching is up to 300 API calls per second per action, up to 3,000 messages per second with batching (10 messages per call), and up to 30,000 transactions per second with High Throughput Mode enabled, at the cost of only maintaining strict order within each group rather than the whole queue. Because SQS is fully managed, there’s no broker or cluster to operate yourself, which simplifies operations at the cost of being locked into AWS’s specific semantics and pricing model.
Choosing Between Them
Kafka fits high-throughput event streaming where consumers need to replay history and where partition-level ordering is sufficient, such as log aggregation, activity tracking, or feeding multiple downstream systems from one event stream. RabbitMQ fits classic task-queue and routing patterns where you want flexible exchange-based routing (direct, fanout, topic) and don’t need Kafka’s replay/retention model. SQS fits teams already on AWS who want a managed, ops-free queue and are willing to choose between Standard’s higher throughput/looser ordering and FIFO’s strict ordering/exactly-once semantics for a given use case.
Bottom Line
These three aren’t really competing for the same job: Kafka is a distributed log built for high-throughput streaming and replay, RabbitMQ is a flexible traditional broker built for routing and task distribution, and SQS is a managed queue built to remove operational overhead on AWS. The right choice depends more on your ordering and delivery requirements than on raw throughput numbers.
FAQ
Does Kafka guarantee message order? Only within a single partition. There is no ordering guarantee across an entire topic if it has multiple partitions.
What’s the difference between SQS Standard and FIFO queues? Standard queues offer very high throughput with best-effort ordering and possible duplicates. FIFO queues guarantee strict ordering within a message group and exactly-once processing, at lower throughput unless High Throughput Mode is enabled.
Can RabbitMQ guarantee exactly-once delivery? Not natively in the way Kafka’s idempotent producer plus transactions or SQS FIFO’s deduplication ID do. RabbitMQ’s acknowledgment and redelivery model is at-least-once, and avoiding duplicate processing typically requires building idempotency into the consumer itself.
Every database has to decide how it physically arranges data on disk, and that decision shapes everything else about its performance. Two structures dominate: the B-tree, which has backed relational databases for decades, and the LSM-tree, which newer, write-heavy systems adopted instead. Neither is strictly better; they trade off reads against writes in opposite directions.
At a Glance
B-Tree
LSM-Tree
Writes
In-place page updates; slower under random writes
Append-only; fast sequential writes
Reads
Single tree traversal; generally faster point/range reads
May check multiple files/levels; mitigated by Bloom filters
A B-tree is a multi-way balanced tree where each level consists of pages connected by pointers; leaf pages hold the actual data (or pointers to it), and internal pages hold downlinks used to navigate to the right leaf. Inserting a row that doesn’t fit on its page triggers a page split, which can cascade upward through the tree and, in the worst case, add an entirely new root level. PostgreSQL’s B-tree implementation, for example, supports deduplication (merging duplicate key values into compact posting-list tuples) and, since version 14, “bottom-up index deletion,” which proactively removes version-churn tuples left behind by MVCC updates so pages don’t split unnecessarily. In practice, over 99% of a B-tree index’s pages are typically leaf pages. MySQL’s InnoDB storage engine uses B-trees for every index except spatial data (which uses R-trees); its default page size is 16KB, and it deliberately leaves roughly 1/16th of each page free on insert to absorb future growth, merging pages that fall below a configurable fill threshold. SQLite also uses B-tree pages for both its tables and its indexes.
How an LSM-Tree Storage Engine Works
A log-structured merge-tree takes a different approach: writes go first into an in-memory structure (a memtable) and an append-only commit log for durability, then flush to immutable, sorted files on disk called SSTables once the memtable fills up. A background compaction process periodically merges these SSTables, applying updates and deletes along the way, since the files themselves are never modified in place. Apache Cassandra uses this model, with a shared commit log across tables and a configurable sync mode (batch, which waits for an fsync before acknowledging a write, or periodic, which acknowledges immediately at the risk of data loss on a crash); a given partition’s data can be spread across several SSTables, each carrying a Bloom filter so reads can skip files that don’t contain the requested key. RocksDB, which underlies systems like MyRocks, TiDB, and CockroachDB, documents several compaction strategies: leveled (its default, which minimizes space amplification at the cost of higher write and read amplification), universal/tiered (lower write amplification, higher read and space amplification), and FIFO (built for cache-like data that simply expires). Neither Cassandra’s nor RocksDB’s official documentation gives a single universal write-amplification multiplier — it depends on the chosen strategy and tuning, so treat any specific number you see quoted elsewhere with some skepticism unless it cites its configuration.
Why the Trade-off Exists
B-trees update data in place, which keeps related data physically close together for fast reads but means random writes have to find and modify the right page on disk, sometimes triggering a cascading split. LSM-trees never modify data in place; they just append new data and let compaction clean up later, which makes writes fast and sequential (ideal for spinning disks and even SSDs) but means a read might have to check several files across multiple levels before it finds the most recent version of a key, and the background compaction work itself consumes disk I/O and CPU that would otherwise go to serving queries.
When Each One Is Preferred
B-trees fit workloads with a healthy mix of reads and writes, or read-heavy workloads where consistent, predictable read latency matters most — which is why they remain the default choice for general-purpose relational databases like PostgreSQL and MySQL. LSM-trees fit write-heavy workloads, such as event logging, time-series ingestion, or high-throughput key-value storage, where the ability to absorb a continuous stream of writes cheaply matters more than shaving milliseconds off every individual read.
Bottom Line
Neither structure is a universal winner; they encode opposite bets about whether your workload will stress reads or writes harder. Relational databases that need predictable read latency across varied queries default to B-trees, while systems built for ingesting large, continuous write volumes — wide-column stores, embedded key-value engines, and time-series databases — tend to default to LSM-trees.
FAQ
Why do LSM-trees need compaction? Because writes are append-only and nothing is ever modified in place, old and updated versions of the same data accumulate across multiple SSTables. Compaction merges these files, discarding obsolete versions and keeping the number of files a read has to check under control.
Can a database use both structures? Yes. Some systems let you choose a storage engine per use case (MySQL supports pluggable storage engines, for instance, with MyRocks offering an LSM-tree-based alternative to InnoDB’s B-tree), and some newer databases combine techniques internally.
Are Bloom filters only used in LSM-trees? They’re most associated with LSM-trees, where they let a read skip SSTables that definitely don’t contain a given key, but the technique itself is general-purpose and shows up in other systems too.
Writing unit tests has historically eaten a disproportionate share of developer time relative to how interesting the work is, which makes it a natural target for AI automation. The landscape here has shifted quickly, though, and the branded products worth knowing in 2026 aren’t always the ones that made headlines a year or two ago.
At a Glance
Tool
Status
What it claims
Qodo Cover (open source)
Unmaintained since June 2025
Aimed to increase code coverage; no benchmark numbers published in its own README
Qodo Gen
Active (current product)
Test generation folded into Qodo’s broader IDE extension and agentic platform
Diffblue Cover / Testing Agent
Active, vendor-marketed
Vendor claims 81% autonomous code coverage, “2.5x more than AI coding tools alone”
Short Verdict
The open-source tool many articles still reference, Qodo Cover, is no longer maintained; current test-generation capability from that vendor now lives inside Qodo Gen. Diffblue is the more actively marketed standalone player, with bold coverage-percentage claims that come directly from the vendor’s own press materials rather than an independently replicated benchmark — worth treating as a starting point for your own evaluation, not a guarantee.
Qodo Cover Is Deprecated
Qodo Cover, the open-source CLI tool previously known as “cover-agent,” carries an explicit notice on its GitHub repository, dated June 15, 2025, stating the repository is no longer maintained. Its original README described the goal as helping “increase code coverage” but never published specific before/after coverage benchmark numbers. Current test-generation functionality from Qodo now lives in the “Qodo Gen” IDE extension, part of the same broader platform that sells Qodo Merge for code review (covered in our AI code review comparison). Anyone evaluating Qodo for test generation today should look at Qodo Gen’s current capabilities rather than referencing the archived Cover project as if it were still active.
Diffblue
Diffblue markets a “Testing Agent” product built around autonomous unit test generation for Java codebases. In its own press materials, the company states its Testing Agent “delivers 81% code coverage autonomously, 2.5x more than AI coding tools alone,” and separately claims a “20x productivity advantage” compared with AI coding assistants used for test writing. These are vendor-published marketing figures from Diffblue’s own press release, and we found no independent, third-party benchmark replicating them during this research. That doesn’t make them false, but it does mean they should be read as a claim to verify against your own codebase, not an externally audited result.
Why This Matters for Teams Evaluating These Tools
Automated test generation tools are judged almost entirely on coverage improvement and the quality of the tests they produce (do they actually catch regressions, or just pad a coverage metric), and vendors in this space have strong incentive to publish favorable numbers. The most reliable way to evaluate any of these tools is still a trial run against your own codebase, comparing coverage and mutation-testing results before and after, rather than taking a vendor’s published percentage as representative of your specific code.
Pros and Cons
Qodo Gen pros: part of a broader, actively maintained agentic platform with IDE integration. Cons: test-generation-specific pricing isn’t broken out separately from Qodo’s general credit-based plans.
Diffblue pros: focused specifically on autonomous Java unit test generation, actively marketed and developed. Cons: headline coverage and productivity figures are vendor-published, not independently verified; no public pricing page was found during this research.
Who It’s a Good Fit For
Teams already using Qodo for code review should evaluate Qodo Gen’s test-generation features as a natural extension rather than looking for the now-unmaintained Qodo Cover. Java-heavy teams specifically interested in autonomous unit test generation as a standalone capability are the target audience for Diffblue, though they should request a trial and measure results against their own codebase before trusting the vendor’s published figures.
Bottom Line
AI test generation is a real and fast-moving category, but branding has shifted quickly (Qodo Cover to Qodo Gen) and the biggest numbers you’ll see quoted are typically vendor marketing claims rather than independently audited benchmarks. Evaluate any tool in this category against your own codebase’s coverage and mutation-testing results before trusting a headline percentage.
FAQ
Is Qodo Cover still usable? The code may still run, but its GitHub repository has been explicitly marked unmaintained since June 2025, so it will not receive updates or fixes going forward.
Are Diffblue’s coverage claims independently verified? Not as far as we could find. The 81% coverage and 2.5x/20x productivity figures come from Diffblue’s own press release, with no independent third-party benchmark replication located during this research.
Does AI-generated test coverage guarantee good tests? No. Coverage percentage measures how much code is executed by tests, not whether those tests would actually catch a real regression — mutation testing or manual review is still the better way to judge test quality.
AI code review has moved from a novelty into a standard part of the pull-request workflow at many teams. Three real, current products dominate the conversation: CodeRabbit, a dedicated PR-review bot; Qodo, a broader agentic developer platform; and GitHub Copilot’s built-in code review and Autofix features for teams already paying for Copilot.
At a Glance
Tool
Model
Entry price
CodeRabbit
Dedicated PR review bot
Essentials: $24/user/mo, no permanent free tier
Qodo
Agentic review (Qodo Merge) + broader dev platform
Credit-based, $0.012/credit; no permanent free tier
GitHub Copilot code review/Autofix
Bundled into Copilot
Included in Pro ($10/mo), Pro+ ($39/mo), Max ($100/mo)
Short Verdict
If you already pay for GitHub Copilot, its built-in code review (generally available since April 2025) is the lowest-friction place to start, since it adds no new vendor relationship. If you want a dedicated review bot with transparent per-seat pricing and features built specifically around pull-request review, security prioritization, and unit test generation, CodeRabbit is the more purpose-built option. Qodo offers the broadest agentic surface, combining review, rules, and IDE/Git integrations, but its credit-based pricing is less predictable and its branding has shifted across products (Qodo Merge, Qodo Gen) in ways worth double-checking before you buy.
CodeRabbit
CodeRabbit is a dedicated AI code review bot that runs against pull requests, the CLI, and IDEs. Its pricing: Essentials at $24/user/mo (1 repo, 5 reviews per developer per hour, 5 MCP connections, Slop Detection for flagging low-quality AI-generated PRs, Pre-Merge Checks, and Autofix); Team at $48/user/mo (adds unit test generation, Finishing Touches, Post-Merge Actions like changelog updates, and a prioritized review queue, covering 5 repos); Advanced at $72/user/mo (adds security-informed prioritization, Blast Radius/architecture-impact analysis, and continuous security monitoring, covering 10 repos); and Enterprise by custom quote with self-hosting and custom RBAC. CodeRabbit integrates with Jira and Linear on every tier and offers only a 14-day trial rather than a permanent free plan, aside from an unspecified exception for qualifying open-source projects.
Qodo
Qodo, formerly known as CodiumAI, sells its PR-review product under the name Qodo Merge through a credit-based Pro Team plan at $0.012 per credit, with pooled team credits translating to roughly 18-144 reviews per month depending on the pack purchased. Enterprise (30+ users) is sold by custom quote with SSO/SAML, audit logs, and bring-your-own-key or on-premises/air-gapped deployment. Like CodeRabbit, Qodo offers no permanent free tier, only a 14-day trial plus free access for qualifying open-source projects. One naming note worth knowing: Qodo’s older open-source test-generation tool, Qodo Cover, is explicitly marked unmaintained by its own GitHub repository as of mid-2025, with current test-generation capability having moved into the “Qodo Gen” IDE extension instead.
GitHub Copilot Code Review and Autofix
Code review inside GitHub Copilot went to public preview in February 2025 and reached general availability in April 2025. It’s included at no extra cost in the Pro ($10/mo), Pro+ ($39/mo), and Max ($100/mo) Copilot plans. GitHub does not publish a simple standalone price for Copilot’s code-review feature on its Business or Enterprise tiers in the same comparison table, so confirm current rates for those tiers through your organization’s GitHub billing rather than assuming a commonly-cited figure. Separately, Copilot Autofix generates one suggested fix per supported CodeQL code-scanning alert with an explanation, and these fixes don’t consume AI credits; a related “agentic autofix” feature that opens a draft pull request automatically does consume AI credits and Actions minutes. Autofix is free for public repositories; private or internal organization repos need a GitHub Advanced Security / Code Security license, priced separately from Copilot itself.
Pros and Cons
CodeRabbit pros: transparent, predictable per-seat pricing; purpose-built for PR review. Cons: no permanent free tier; separate vendor relationship to manage.
Qodo pros: broadest agentic feature set (review, rules, IDE integration); flexible credit packs. Cons: credit-based cost is less predictable than flat per-seat pricing; product naming has shifted and can confuse buyers.
GitHub Copilot pros: zero extra tool to adopt if you already pay for Copilot; Autofix integrates natively with CodeQL scanning. Cons: Business/Enterprise code-review pricing isn’t clearly published; private-repo Autofix needs a separate Advanced Security license.
Who It’s a Good Fit For
Teams already paying for Copilot Pro or above should try its built-in review and Autofix first, since it costs nothing extra to turn on. Teams that want a dedicated, security-focused review bot independent of their AI coding assistant vendor should look at CodeRabbit for predictable pricing or Qodo for a broader agentic toolset.
Bottom Line
All three tools are real, actively developed products as of this writing, and none offers a permanent free plan beyond trials and open-source exceptions. The practical starting point is whatever you’re already paying for: Copilot users should flip on its review and Autofix features before adding a second vendor, while teams not using Copilot should compare CodeRabbit’s flat per-seat tiers against Qodo’s credit-based pricing based on how predictable they need their monthly bill to be.
FAQ
Is Qodo Cover still Qodo’s test-generation product? No. Qodo Cover’s GitHub repository is marked unmaintained as of mid-2025; current test-generation capability lives in the “Qodo Gen” IDE extension instead.
Does Copilot Autofix cost extra? Fixes for CodeQL code-scanning alerts don’t consume AI credits. A separate “agentic autofix” that opens a draft PR automatically does consume AI credits and Actions minutes, and private-repo use requires a GitHub Advanced Security license.
Do any of these tools have a free tier? None of CodeRabbit or Qodo offer a permanent free tier for commercial use; both offer time-limited trials and exceptions for qualifying open-source projects. GitHub Copilot’s review features require a paid Copilot plan.
API testing tools have split into two philosophies: cloud-account-based tools like Postman and Insomnia that sync collections to the cloud by default, and offline-first tools like Bruno that store everything as plain files on disk. The right pick depends less on features and more on where you want your API collections to actually live.
At a Glance
Postman
Insomnia
Bruno
Storage model
Cloud-account based (local mode available)
Cloud-account based (local mode available)
Offline-first, plain-text files on disk
Free tier
1 user, 10,000 API calls/mo
Unlimited projects, Git Sync for up to 3 users
Free and open-source, no imposed usage caps
Entry paid tier
Solo: $9/user/mo (annual)
Pro: $12/user/mo (annual)
Paid “Golden”/”Ultimate” editions for extra features
Collaboration model
Cloud team workspaces
Cloud team workspaces
Via Git, since collections are plain files
Short Verdict
Postman remains the most feature-complete choice for teams that want mature scripting, monitoring, and a large collaborative workspace, and it’s the closest thing to an industry default. Insomnia (now owned by Kong) is a strong, slightly leaner alternative with a generous free tier. Bruno is the one to pick if you specifically want your API collections stored as plain, git-diffable files with no account or cloud dependency at all — a deliberate, stated design choice by its maintainers rather than a missing feature.
Pricing Breakdown
Postman: Free tier includes 1 user, 10,000 Postman API calls per month, up to 5 integrations, 25 Automation Flow credits per month, 1,000 API monitoring requests per month per team, public workspaces, the Collection Runner, and native Git support, but no private workspaces or webhooks. Solo is $9/user/mo billed annually; Team is $19/user/mo billed annually; Enterprise is by custom quote.
Insomnia: The free “Essentials” tier offers unlimited cloud or local projects for all users, Git Sync for up to 3 users, the Inso CLI for CI/CD, unlimited collection runs and environments, 1,000 mock-server requests per month, end-to-end encryption, custom linting, and plugin access. Pro is $12/user/mo, with roughly 15-17% savings for annual billing over monthly. Enterprise is $45/user/mo self-serve for up to 50 users, with larger teams requiring a custom quote.
Bruno: The core app is open-source (MIT-licensed) and free with no imposed usage caps. Paid “Golden Edition” and “Ultimate Edition” license keys exist for additional features, though Bruno doesn’t prominently publish exact pricing for these the way Postman and Insomnia do their tiers — check usebruno.com directly if you need those extras.
The Real Differentiator: Where Your Collections Live
Postman and Insomnia are both primarily cloud-account products: your collections sync to their servers by default, with local/offline modes available as an option. Bruno inverts that: collections are stored as plain-text files (its own “Bru” markup) directly on your filesystem, with no account or login system at all. Bruno’s maintainers have explicitly stated they have no plans to ever add cloud sync, framing it as a privacy stance rather than a temporary limitation. Because Bruno’s collections are just files, teams collaborate on them through Git the same way they would with source code, rather than through a built-in cloud workspace.
Scripting and Testing
Postman has the most mature scripting support of the three, with pre-request and test scripts, a Collection Runner, and scheduled monitors. Insomnia supports unlimited collection runs and environments on even its free tier, plus a plugin system. Bruno supports JavaScript-based scripting as well, though its plugin ecosystem is smaller, reflecting its younger age and leaner team.
Pros and Cons
Postman pros: most mature feature set, huge user base, strong monitoring. Cons: free tier is the most limited of the three (1 user, 10,000 calls/mo); cloud-first by default.
Insomnia pros: generous free tier, Git Sync built in, CLI for CI/CD. Cons: mock-server requests capped at 1,000/mo even on Essentials; smaller plugin ecosystem than Postman’s.
Bruno pros: fully offline, git-diffable, no account required, genuinely free core. Cons: no built-in cloud collaboration; smaller ecosystem and community than the other two.
Who It’s a Good Fit For
Postman fits teams that want a mature, all-in-one API platform and don’t mind paying per seat as they scale. Insomnia fits teams that want a similar cloud-workspace experience with a more generous free tier and native CI/CD tooling. Bruno fits developers and teams who specifically want API collections to live in their own git repository alongside their code, with no vendor account in the loop.
Bottom Line
There’s no universally “best” tool here — Postman wins on maturity and ecosystem, Insomnia wins on free-tier generosity, and Bruno wins on privacy and git-native workflows. Teams that already store infrastructure-as-code or configuration in git will likely find Bruno’s model the most natural fit; everyone else will probably be happiest with Postman or Insomnia’s cloud workspace.
FAQ
Is Bruno really free? The core desktop app is free and open-source (MIT-licensed) with no usage caps. Optional paid “Golden” and “Ultimate” editions exist for extra features.
Can Postman and Insomnia be used fully offline? Yes, both support local/offline modes, but their default and most-marketed workflow is cloud-account based, unlike Bruno which is offline by default.
Who owns Insomnia? Insomnia is developed by Kong, the API gateway company, which also maintains Kong Gateway and other API infrastructure tooling.
For years, advertisers measured conversions by letting a browser pixel or mobile SDK fire directly from a user’s device. iOS App Tracking Transparency and the decline of third-party cookies broke a lot of that measurement, which is why most ad platforms now push advertisers toward server-side tracking: sending conversion data from your own server instead of relying solely on the browser.
At a Glance
Approach
Platform
What it sends
Conversions API
Meta
Web, app, business messaging, and offline/CRM events, tied to a dataset ID
Enhanced Conversions
Google Ads
Hashed first-party customer data (e.g. email) from site tags or imported offline events
What Server-Side Tracking Actually Is
Server-side tagging and Conversions APIs send conversion and event data directly from an advertiser’s own server, such as a website backend, CRM, or point-of-sale system, straight to the ad platform, rather than relying only on a browser pixel or device-level SDK. The goal is to recover measurement signal that client-side tracking lost after iOS’s App Tracking Transparency prompt reduced device-level tracking consent, and after browsers increasingly restrict or block third-party cookies.
Meta Conversions API
According to Meta’s own developer documentation, the Conversions API connects an advertiser’s marketing data, whether from web, app, business messaging, or offline and CRM events, to Meta through a single server-to-endpoint connection rather than separate connections per data source. Server events must be linked to a specific dataset ID; once connected, they’re processed for measurement, reporting, and ad optimization the same way Pixel or SDK events are. Meta’s stated goals for advertisers using it are better ad targeting, lower cost per result, and clearer outcome measurement. Setup follows a standard pattern: pick an integration method, confirm prerequisites, send server-to-server POST requests with event data, then verify events are received and properly deduplicated against any existing browser-side Pixel events for the same conversion.
Google Ads Enhanced Conversions
Google’s version, Enhanced Conversions, supplements existing conversion tracking by sending hashed first-party customer data, such as an email address, from a site’s tags or from imported offline conversion events. Google’s own documentation states the benefit as improving “the accuracy of your conversion measurement” and helping “unlock more powerful bidding.” The setup has three parts: normalize the data before hashing (trim whitespace, lowercase text, format phone numbers to the E.164 standard, and strip periods from Gmail/Googlemail addresses); hash it using SHA-256, a one-way hash so raw personal data is never transmitted; and choose the right implementation — “Enhanced Conversions for web” for online events, or “for leads” for offline conversions that started as a web lead.
A Note on Marketing Claims
Both Meta and Google describe the benefits of server-side tracking only in directional terms — “improve accuracy,” “lower cost,” “unlock more powerful bidding” — without a universal percentage guarantee. Specific lift numbers you’ll see in marketing blogs (“24% more conversions,” for example) typically come from an individual advertiser’s own test and shouldn’t be treated as a platform-wide benchmark you can expect to replicate.
Who Should Implement This
Any business running meaningful Meta or Google Ads spend and relying on browser- or app-based conversion tracking alone should prioritize setting up Conversions API and Enhanced Conversions, since both platforms now treat server-side signal as a core input to bidding algorithms, not an optional extra. Smaller advertisers running limited budgets through a well-supported e-commerce platform (many of which now offer one-click Conversions API integrations) have a comparatively low-effort path to implementing this; advertisers with custom-built checkout flows will need engineering time to implement the hashing and API calls correctly.
Bottom Line
Server-side tracking isn’t optional anymore for advertisers who want reliable measurement and bidding performance on Meta and Google — it’s the direct response to privacy changes that broke client-side tracking. The setup requires some technical lift (hashing, deduplication, dataset linking) but both platforms provide detailed official documentation, and most major e-commerce platforms now offer managed integrations that remove much of that burden.
FAQ
Does server-side tracking replace pixels entirely? No. Most implementations run server-side events alongside browser/SDK events and rely on deduplication to avoid double-counting the same conversion, rather than removing the pixel entirely.
Is customer data sent in plain text? No. Google’s Enhanced Conversions requires hashing personal data (such as email addresses) with SHA-256 before it’s sent, a one-way process so the raw data itself is never transmitted.
Why did advertisers need to do this at all? iOS’s App Tracking Transparency prompt and the broader decline of third-party cookies reduced how much conversion activity ad platforms could see directly from browsers and devices, pushing platforms to rely more on first-party data sent directly from the advertiser’s own server.
Creative, not targeting, is increasingly the bottleneck in paid social and display advertising, since most platforms now auto-optimize bidding and placement. A wave of “creative automation” tools has grown around that gap, from affordable AI banner generators to enterprise platforms that connect creative directly to live product data.
At a Glance
Tool
Best for
Pricing model
AdCreative.ai
Small-to-mid DTC brands, solo marketers, agencies
Published credit-based tiers from $39/mo
Smartly.io
Large enterprises managing high-volume, multi-channel spend
Custom quote, sales-contact only
Celtra
Large brands and media owners needing dynamic, catalog-driven creative
Custom quote, sales-contact only
Short Verdict
AdCreative.ai is the only one of these three with transparent self-serve pricing, which makes it the practical starting point for small teams and agencies that want AI-generated ad variations fast and cheap. Smartly.io and Celtra are both enterprise platforms sold exclusively through a sales process, aimed at organizations managing large, multi-channel ad budgets where creative automation needs to plug into live product catalogs and cross-platform media buying, not just generate single images.
AdCreative.ai
AdCreative.ai generates ad banners, images, and video from templates or a URL (“Instant Ads”), produces multi-size and multi-platform variations for A/B testing, generates UGC-style video and AI product/fashion photography, and writes AI ad copy. It also offers a Creative Scoring feature and a Compliance Checker. Pricing, as published directly on its site, runs: Starter at $39/mo (20 credits, 1 brand), Professional at $249/mo (300 credits, roughly 3-10 brands), Ultimate at $999/mo (300 credits, 25 brands), with Enterprise available by custom quote and a discount for quarterly billing. Credit-based pricing means cost can climb quickly for teams generating high volumes of creative, and like most SaaS pricing pages, exact credit allotments per tier are worth confirming at signup since they can shift.
Smartly.io
Smartly.io is built around three connected suites: Creative (AI Studio for generative creative at scale), Media (AI-driven budget allocation and automated campaign setup across platforms), and Intelligence (AI-generated performance dashboards). It supports Google, Meta, YouTube, TikTok, Pinterest, Reddit, Snapchat, connected TV across 200+ streaming services, and open-web demand-side platforms. Smartly.io does not publish pricing anywhere on its site; every path leads to a demo request or sales chat, consistent with an enterprise, high-spend customer base.
Celtra
Celtra focuses on creative automation for omnichannel campaigns, including Dynamic Product Ads that generate image and video creative directly from a product catalog, and “Creative Enablement” tooling for media owners and operators. It also markets automated brand governance and live-data creatives that update pricing or inventory automatically across more than 100 media platforms. Celtra states (in its own marketing, not independently verified) more than 450 enterprise customers and over 20 million ads produced per year. Like Smartly.io, Celtra publishes no dollar pricing; quotes are based on which product (Creative Automation vs. Creative Enablement), team and creative scale, and ad-serving volume a customer needs.
Pros and Cons
AdCreative.ai pros: transparent pricing, fast turnaround, accessible to small teams. Cons: credit-based cost can scale unpredictably; its “accuracy” scoring claims aren’t independently verifiable.
Smartly.io pros: deepest cross-channel media, creative, and analytics integration in one platform. Cons: no public pricing, clearly built for large ad budgets rather than small teams.
Celtra pros: strong dynamic, catalog-driven creative and brand governance tooling. Cons: no public pricing, enterprise-only positioning.
Who It’s a Good Fit For
Solo marketers, small e-commerce brands, and agencies that need fast, affordable creative variations should start with AdCreative.ai. Large enterprises managing paid social, connected TV, and open-web spend across many platforms at once are the target market for Smartly.io. Brands and media owners that need creative to update automatically with live product or pricing data at scale should look at Celtra.
Bottom Line
This is really a market split by company size rather than a single best tool: AdCreative.ai serves the self-serve end with real published prices, while Smartly.io and Celtra serve large, high-spend advertisers through custom enterprise contracts. Expect to request a demo for either of the latter two rather than finding a price list.
FAQ
Do Smartly.io and Celtra publish pricing? No. Both are sold exclusively through a sales/demo process with custom quotes based on scale and feature needs.
Is AdCreative.ai good enough for a small business? Its Starter tier at $39/mo is aimed at exactly that use case, with enough credits for a single brand’s regular ad variation needs, though costs rise if you need high creative volume.
What does “dynamic creative” mean? It refers to ads that are generated or updated automatically from a live data feed, such as a product catalog, so pricing, inventory, or imagery stays current without manual re-editing — a core feature of Celtra’s platform in particular.
Two significant pricing changes reshaped this comparison in 2026: Dashlane quietly discontinued its free plan, and 1Password raised its Individual and Family prices. Bitwarden also raised its Premium price, but remains the only one of the three with a genuinely full-featured free tier. Here’s where all three stand now.
At a Glance
Dashlane
1Password
Bitwarden
Free plan
None (discontinued September 2025)
None (14-day trial only)
Yes, always free, unlimited passwords/devices
Individual paid plan
Premium: $4.99/mo (annual)
Individual: $4.99/mo (as of March 2026 increase)
Premium: $1.65/mo ($19.80/yr)
Family plan
Friends & Family (10 members): $7.49/mo
Families: $7.99/mo (as of March 2026 increase)
Families (6 users): $3.99/mo
Passkey support
Yes
Yes
Yes, including on the free tier
Short Verdict
Bitwarden is the easiest recommendation for most people: it’s the only one of the three with a real free tier that includes unlimited passwords, unlimited devices, and passkey management, and its paid Premium tier is still the cheapest at under $20 a year. 1Password and Dashlane both compete on polish and support rather than price — 1Password’s recent price increase and Dashlane’s removal of its free tier both make them harder to justify unless you specifically want their particular business features or support experience.
Dashlane: No More Free Plan
Dashlane discontinued its free plan on September 16, 2025, meaning there’s no longer a way to use Dashlane without paying. Current plans:
Premium (1 user): $4.99/mo, billed annually.
Friends & Family (up to 10 members): $7.49/mo, billed annually.
Business Standard (up to 10 users): $20/mo flat.
Business (2+ users): $8/user/mo.
Business Plus (100+ users): $5/user/mo.
All plans come with a 30-day money-back guarantee, and Dashlane markets passkey protection prominently across its business tiers.
1Password: Prices Went Up in 2026
1Password raised its Individual and Family subscription prices effective March 27, 2026, applying at each customer’s next renewal after that date. The new monthly prices are $4.99 for Individual (up from $3.99) and $7.99 for Family (up from $6.95). 1Password continues to offer a 14-day free trial but no permanent free tier; Teams Starter Pack and Business tiers are priced separately and are best confirmed directly on 1Password’s pricing page, since several third-party trackers reported conflicting figures for those tiers at the time of this research. Enterprise is sold by custom quote.
Bitwarden: Still Free, But Premium Costs More
Bitwarden’s Free plan remains genuinely free with no forced downgrade, long marketed as supporting unlimited passwords and unlimited devices across every tier including Free, and includes passkey management as a core feature at every level. Where Bitwarden changed in 2026 is its Premium price, which multiple independent trackers report roughly doubled, from about $10/yr historically to $19.80/yr ($1.65/mo) now. Premium adds a built-in 2FA authenticator, 5GB of encrypted attachment storage, emergency access, and vault health reports. Families is $3.99/mo ($47.88/yr) for up to 6 users; Teams is $4/user/mo annually; Enterprise is $6/user/mo annually and adds SSO, self-hosting, and enterprise policies.
Pros and Cons
Dashlane pros: polished interface, strong dark web monitoring, flexible business tiers. Cons: no free plan at all anymore, among the pricier options for solo users.
1Password pros: well-regarded family and travel-mode features, strong enterprise/Business tooling. Cons: recent price increase, no permanent free tier.
Bitwarden pros: genuinely free tier with passkeys and unlimited passwords/devices, open-source core, cheapest paid tiers. Cons: interface is less polished than Dashlane or 1Password; Premium price nearly doubled in 2026.
Who It’s a Good Fit For
Bitwarden fits anyone who wants a capable password manager at the lowest cost, including people who never want to pay anything — its free tier is not a crippled trial. Dashlane and 1Password fit people who want a more polished consumer experience or specific business/admin tooling and are willing to pay a premium for it; 1Password in particular has strong name recognition in business IT environments.
Who Should Look Elsewhere
Anyone who specifically wants to try a password manager for free before committing should skip Dashlane, which no longer offers that option, and either use Bitwarden’s free tier or 1Password’s 14-day trial first.
Bottom Line
2026 has been a year of price increases across password managers, and Bitwarden is the only one of these three that still offers a real free tier. Unless you have a specific reason to prefer Dashlane’s or 1Password’s interface or business features, Bitwarden’s combination of a capable free plan and the cheapest paid tiers makes it the default recommendation.
FAQ
Does Dashlane have a free plan? No. Dashlane discontinued its free plan on September 16, 2025; every current plan requires payment.
Did 1Password really raise its prices? Yes. Effective March 27, 2026, 1Password raised Individual from $3.99 to $4.99/mo and Family from $6.95 to $7.99/mo, applied at each customer’s next renewal.
Is Bitwarden’s free plan actually usable long-term? Yes. Bitwarden has long marketed unlimited passwords and unlimited devices on its free tier, including passkey management, which is more generous than the free offerings most competitors provide.
Phishing remains the most common way attackers get into a small business’s systems, and most of the damage happens inside email, not a browser. The confusing part for buyers is that most dedicated email security vendors don’t publish per-seat pricing the way SaaS tools usually do — so comparing options means comparing capability and positioning more than a price list.
At a Glance
Tool
Best for
Public pricing?
Microsoft Defender for Office 365 (Plan 1/2)
Microsoft 365 shops wanting built-in protection
Bundled into Microsoft 365 tiers; standalone pricing not publicly itemized on Microsoft’s own site
Proofpoint Essentials
SMBs up to roughly 500 users, especially on Microsoft 365
Not listed publicly by the vendor
Mimecast
Mid-market and larger orgs wanting archiving + security + training
Not listed publicly; sold through resellers
Short Verdict
If you’re already on Microsoft 365, start with what you already have: Exchange Online Protection ships with every cloud mailbox and handles baseline anti-malware, anti-spam, and anti-phishing with a published SLA. Add Defender for Office 365 Plan 1 or 2 if you need Safe Links, Safe Attachments, and automated investigation. If you need something broader or vendor-neutral, Proofpoint Essentials is explicitly built for the SMB segment, while Mimecast leans toward mid-market and larger organizations that also want archiving and security-awareness training bundled in. None of the three publish simple per-seat pricing, so budgeting means requesting a quote.
What’s Built Into Microsoft 365 Already
Every cloud mailbox on Microsoft 365 already includes Exchange Online Protection (EOP): anti-malware and anti-spam filtering, anti-phishing and spoof intelligence, zero-hour auto purge, quarantine, and tenant-level allow/block lists, all on by default and not fully disableable. Microsoft’s own documentation states a service level of greater than 99% spam-catch effectiveness and a false-positive ratio of less than 1 in 250,000, with 99.999% service uptime. Defender for Office 365 Plan 1 and Plan 2 sit on top of EOP: Plan 1 adds Safe Links (time-of-click URL scanning) and Safe Attachments (sandboxing); Plan 2 adds automated investigation and response. Both are sold standalone or bundled into Microsoft 365 Business Premium and E5. Microsoft’s public documentation covers these features in detail but does not list a simple standalone per-seat price on the page we could verify — pricing is best confirmed through your Microsoft 365 admin center or a partner.
Proofpoint Essentials
Proofpoint Essentials is explicitly positioned for small and mid-size businesses, particularly those running Microsoft 365, and reviewers note it isn’t recommended for organizations above roughly 1,500 users or those needing granular group-based policy. Features include email warning banners (flagging external senders, DMARC failures, or high-risk messages), one-click message pull for Microsoft 365, Predictive URL Defense that sandboxes links before delivery, Advanced BEC Defense using behavioral analysis of headers and sender reputation, dual-engine antivirus with sandboxing, and DMARC/SPF/DKIM analysis alongside spam and bulk-mail filtering. Proofpoint does not list pricing publicly; third-party estimates exist but should be treated as analyst approximations rather than confirmed list prices.
Mimecast
Mimecast is an enterprise-grade secure email gateway that bundles targeted threat protection, email archiving, and security-awareness training, typically sold through a reseller/channel model with quote-based pricing rather than public rate cards. It tends to show up more often in mid-market and larger deployments than in the smallest-business segment, where its archiving and compliance features carry more weight relative to cost.
Pros and Cons
Microsoft Defender for Office 365: Pros — baseline protection already included, no new vendor relationship needed, documented SLA. Cons — full feature set requires Plan 2 and a Microsoft 365 tier that includes it; standalone pricing isn’t simple to find publicly.
Proofpoint Essentials: Pros — purpose-built for SMBs, strong behavioral BEC defense. Cons — pricing is opaque; not recommended for larger organizations or granular policy needs.
Mimecast: Pros — bundles archiving, security, and training together. Cons — reseller-driven pricing can be harder to predict; multiple sources note recent price increases affecting MSPs and smaller customers.
Who It’s a Good Fit For
Microsoft 365 shops that just want a stronger baseline should start with Defender for Office 365 before shopping elsewhere. Small businesses outside the Microsoft ecosystem, or those wanting a vendor purpose-built for their size, should request a Proofpoint Essentials quote. Organizations that also need archiving and compliance-grade retention alongside security, and have budget for an enterprise-style vendor relationship, should look at Mimecast.
Who Should Look Elsewhere
Very small teams with tight budgets may find that Microsoft 365’s built-in EOP protection, combined with basic staff training, covers their risk adequately without paying for a dedicated add-on vendor. Organizations above roughly 1,500 users should look past Proofpoint Essentials toward Proofpoint’s enterprise product line or a comparable enterprise-tier competitor.
Bottom Line
None of the three major options here publish simple per-seat pricing, which is itself a useful fact for budgeting purposes — expect to request a quote regardless of which you choose. The practical starting point for most small businesses is to fully use what’s already included in Microsoft 365 (EOP, and Defender for Office 365 if licensed) before adding a third-party layer on top.
FAQ
Is Microsoft 365’s built-in email security enough on its own? For many small businesses, baseline Exchange Online Protection plus good staff awareness covers common threats. Organizations handling sensitive data or facing targeted phishing (business email compromise) typically benefit from adding Defender for Office 365 Plan 1 or 2, or a dedicated third-party tool.
Why don’t these vendors publish pricing? Email security is typically sold through channel partners and scaled to deployment size, user count, and feature tier, which makes a simple published rate card less common than it is for self-serve SaaS products.
What is business email compromise (BEC)? BEC attacks impersonate executives, vendors, or partners to trick employees into wiring money or sharing credentials, often without any malware or malicious link involved — which is why behavioral and sender-reputation analysis, not just link/attachment scanning, matters for defending against it.
Every major cloud storage provider gives you a small amount of space for free and then tries to upsell you into its wider productivity ecosystem. The real differences between Dropbox, Google Drive, and OneDrive in 2026 show up in how storage is packaged, what counts as a “plan,” and how deeply each one is tied to its parent company’s office suite.
At a Glance
Dropbox
Google Drive / Google One
OneDrive / Microsoft 365
Free storage
2GB
15GB (shared across Gmail, Drive, Photos)
5GB
Cheapest paid storage
Plus: $9.99/mo for 2TB
Basic: 100GB, ~$19.99/yr standard rate
Microsoft 365 Basic: $1.99/mo for 100GB
Standalone storage-only plan?
Yes
Yes (Google One)
No — always bundled with a Microsoft 365 tier
Office suite included
No (third-party integrations instead)
Yes, Docs/Sheets/Slides
Yes, Word/Excel/PowerPoint (on higher tiers)
Short Verdict
If you just want cheap bulk storage with no office suite attached, OneDrive’s $1.99/mo Microsoft 365 Basic tier for 100GB is hard to beat on price, though it’s technically a Microsoft 365 plan rather than a pure storage product. If you want storage bundled with the most capable free collaborative office suite, Google Drive (via Google Workspace or Google One) wins. If you want the most mature third-party integrations, sharing controls, and e-signature tools independent of any office suite, Dropbox is still the most flexible, business-focused option, at a higher starting price.
Every Google account comes with 15GB shared across Gmail, Drive, and Photos at no cost. Beyond that, Google One sells storage in tiers that Google has recently repackaged around its “Google AI” branding, and it has run promotional first-year pricing that reverts to a standard annual fee after 12 months. As of this research, the standard (non-promotional) annual pricing reported was roughly $19.99/year for a 100GB Basic plan and roughly $99.99/year for a 2TB Premium plan, with a higher “AI Pro” 2TB tier around $199.99/year that bundles expanded Gemini AI features. Because Google has run limited-time discounted introductory pricing on these same tiers, confirm the live price at one.google.com/about/plans before buying, since the promotional and standard rates differ meaningfully.
OneDrive / Microsoft 365 Pricing
Microsoft no longer sells a storage-only consumer OneDrive plan. Instead, OneDrive capacity is bundled into Microsoft 365 tiers:
Free Microsoft account: 5GB of OneDrive storage.
Microsoft 365 Basic: $1.99/mo (about $19.99/yr) — 100GB storage, ad-free Outlook and some extra security, but no desktop Office apps.
Microsoft 365 Personal: $9.99/mo or $99.99/yr — 1TB storage, full desktop Office apps, for 1 person.
Microsoft 365 Family: $12.99/mo or $129.99/yr — a shared storage pool (recently restructured; multiple independent outlets reported Microsoft shifted this from a per-person 1TB allotment to a smaller shared pool across up to 6 people in 2026) for up to 6 people.
Microsoft also sells standalone OneDrive for Business plans, but these are being retired: new sales end May 31, 2026, no renewals are accepted after January 2027, and the plans shut down entirely in December 2029, pushing business customers toward bundled Microsoft 365 Business tiers instead.
Features Beyond Storage
All three claim AES-256 encryption at rest and TLS in transit, offline sync, and link-based sharing with permission controls. Google Drive and OneDrive both have deeper native co-editing through their own office suites (Docs/Sheets vs. Word/Excel Online); Dropbox has no first-party office suite and instead focuses on third-party app integrations and its own e-signature product, Dropbox Sign.
Pros and Cons
Dropbox pros: mature sharing/permission controls, strong third-party app ecosystem, Dropbox Sign built in. Cons: smallest free tier (2GB), no bundled office suite, priciest entry paid tier.
Google Drive pros: generous 15GB free tier shared across Google services, tightly integrated with Docs/Sheets/Slides and Gemini AI. Cons: plan names and prices have shifted repeatedly around AI branding, making it harder to compare long-term cost.
OneDrive pros: cheapest path to 100GB via Microsoft 365 Basic, deep Word/Excel/Outlook integration on higher tiers. Cons: no pure storage-only plan, recent reports of Family plan storage being reduced from a per-person to a shared pool.
Who It’s a Good Fit For
Dropbox suits businesses that need strong sharing/permission controls and e-signature without committing to an office suite. Google Drive suits anyone already using Gmail and Google Workspace who wants the most storage for free and native Docs collaboration. OneDrive suits Windows and Microsoft 365 households that want the cheapest path to meaningful storage, as long as they’re comfortable buying it as part of a Microsoft 365 subscription rather than a standalone product.
Bottom Line
There’s no pure storage-only winner anymore — Google and Microsoft both tie meaningful storage to their broader AI and office ecosystems, and Microsoft has eliminated the standalone OneDrive consumer plan entirely. Dropbox remains the most “just storage and sharing” focused of the three, at a real price premium. Pick based on which ecosystem (Google Workspace, Microsoft 365, or neither) you’re already paying for.
FAQ
Can I buy OneDrive storage without a Microsoft 365 subscription? No. Microsoft has discontinued standalone OneDrive consumer storage plans; all paid OneDrive storage now comes bundled with a Microsoft 365 tier.
How much free storage does each service give? Dropbox gives 2GB free, Google gives 15GB shared across Gmail/Drive/Photos, and OneDrive gives 5GB free with any Microsoft account.
Which is cheapest for just storage? Microsoft 365 Basic at roughly $1.99/mo for 100GB is currently the cheapest entry point, though it includes some Outlook and security features beyond raw storage. Always confirm current pricing directly with the vendor, since all three have changed their plans within the past year.
Note-taking apps split into two camps: cloud-first services that sync everything for you, and local-first tools that store your notes as plain files you control. Evernote and OneNote are the cloud-first veterans; Obsidian is the local-first alternative that has pulled a large community away from both. Here is how they actually compare on price and structure in 2026.
At a Glance
Evernote
OneNote
Obsidian
Storage model
Cloud-first, proprietary format
Cloud-first (OneDrive), proprietary format
Local-first, plain Markdown files
Free tier
50 notes, 1 notebook, 1GB storage
Free with Microsoft account, 5GB storage (shared with OneDrive)
Free, unlimited, for personal and commercial use
Cheapest paid tier
Starter: $14.99/mo or $99/yr
Bundled into Microsoft 365 Personal: $9.99/mo
Sync add-on: $4/user/mo (yearly) or $5/mo
Plugin ecosystem
Limited, built-in integrations only
Limited, deep Office integration instead
Large community plugin ecosystem
Short Verdict
If you want your notes to live as plain files you can back up, version-control, or move between apps, Obsidian is the clear choice, and it’s free for personal use. If you’re already paying for Microsoft 365, OneNote is effectively free and deeply integrated with Word, Outlook, and Teams. Evernote has become the hardest of the three to justify since cutting its free tier down to just 50 notes in 2026 and raising its paid prices — it still has strong AI search and web-clipping features, but the free plan is no longer a realistic way to try it.
Evernote: Pricing and What Changed
Evernote restructured its plans in 2026, and the free tier is now quite restrictive: 50 notes total, 1 notebook, 5 spaces, 20 tags, 200 attachments, 1 synced device, and 1GB of storage. Paid tiers are:
Advanced: $24.99/mo or $249.99/yr — unlimited notes, notebooks, spaces, tags, attachments, and devices (subject to unspecified “safeguard limits”), unlimited storage.
Flexible/Enterprise and Unlimited: custom pricing via sales.
All paid tiers include an AI Assistant, semantic search, AI transcription/editing tools, MCP connections to AI tools, and integrations with Google, Outlook, and Slack. A 40% student discount applies to one year of Advanced.
OneNote: Free, Bundled, or Both
OneNote’s core app is free with any Microsoft account on web, desktop, and mobile, with unlimited notebooks synced across devices, backed by 5GB of storage shared with OneDrive. You don’t need a Microsoft 365 subscription to use OneNote itself. What a Microsoft 365 Personal subscription ($9.99/mo) adds is 1TB of cloud storage, the full desktop Office suite (Word, Excel, PowerPoint, Outlook) with Copilot features, Microsoft Defender security, and support for use on up to five devices. In practice, most people who already pay for Microsoft 365 for Word and Excel get OneNote’s storage and Copilot upgrade for free as part of that bundle.
Obsidian: Local-First and Mostly Free
Obsidian’s core app is free without limits for personal use, and the company does not technically block commercial use either — it “encourages” organizations using it for work to buy a Commercial license at $50/user/year, on the honor system rather than through enforced license checks. The real differentiator is that every note is stored as a plain Markdown file on your own device; there’s no proprietary format and no forced cloud dependency. Two optional paid add-ons exist for teams that want convenience features Obsidian doesn’t build in by default:
Obsidian Publish: turns a vault into a public website, $8/site/mo billed yearly or $10/mo billed monthly.
Obsidian has no built-in real-time collaboration the way Evernote and OneNote do; teams typically layer Sync or a third-party service (like a shared cloud folder or Git) on top instead.
Pros and Cons
Evernote pros: strong AI search and transcription, web clipper, mature cross-platform apps. Cons: free tier now very restrictive (50 notes), among the priciest of the three.
OneNote pros: genuinely free core app, deep Office/Outlook/Teams integration, good handwriting and freeform canvas support. Cons: weaker plugin ecosystem, proprietary notebook format makes exporting elsewhere harder.
Obsidian pros: local-first plain-text files, huge community plugin ecosystem, cheap optional sync. Cons: no built-in real-time collaboration, steeper setup for non-technical users who want things to “just sync.”
Who Each One Fits
Evernote fits people who lean on its AI search and web-clipping and are willing to pay a premium subscription for it. OneNote fits anyone already inside the Microsoft 365 ecosystem who wants notes integrated with Word, Outlook, and Teams at no extra cost. Obsidian fits people who want full ownership of their notes as portable files, plus the flexibility of community plugins, and don’t mind a bit more setup to get sync or publishing working.
Bottom Line
There’s no universal winner here — it depends on whether you value AI-powered search (Evernote), free Office-suite integration (OneNote), or file ownership and extensibility (Obsidian). For most people starting fresh in 2026, Obsidian’s combination of a genuinely free core app and cheap optional sync makes it the easiest to recommend by default, with OneNote a close second for anyone already paying for Microsoft 365.
FAQ
Is Obsidian really free? Yes, for personal use the core app has no limits and no required sign-up. Commercial use is on an honor-system license ($50/user/year) rather than an enforced paywall.
Do I need to pay for OneNote separately from Microsoft 365? No. The OneNote app itself is free with any Microsoft account. A Microsoft 365 subscription adds storage and Copilot features but is not required to use OneNote’s core functionality.
Why did Evernote’s free plan get worse? Evernote restructured its plans in 2026, cutting the free tier to 50 notes and 1GB of storage, far below its historical limits, while adding AI features across its paid tiers.
Smartsheet and monday.com both promise to replace your spreadsheets-and-email project workflow, but they start from different premises: Smartsheet is a spreadsheet-grid tool that grew Gantt charts and automation, while monday.com is a visual board tool that grew spreadsheet-like views. For a team picking between them in 2026, the difference shows up fastest in pricing structure and in how native Gantt and resource planning feels day to day.
At a Glance
Smartsheet
monday.com (Work Management)
Free plan
No permanent free plan (30-day trial)
Yes, up to 2 seats, 3 boards
Entry paid tier
Pro: $9/member/mo annual, 1-10 members
Basic: $9/seat/mo annual, 3-seat minimum
Mid tier
Business: $19/member/mo annual, 3+ members
Pro: $19/seat/mo annual, 3-seat minimum
Native Gantt chart
Included from Pro tier
Only from Standard tier ($12/seat/mo) up
Enterprise
Custom quote
Custom quote
Short Verdict
Choose Smartsheet if your team already thinks in spreadsheets and needs Gantt charts, resource tracking, or complex formulas out of the box, since it is the more spreadsheet-native, project-management-literal tool. Choose monday.com if your team wants a visually driven board-and-automation experience and is comfortable paying extra (moving to its Standard tier) to unlock timeline views. Both lock their best enterprise features (SSO, portfolio management) behind custom-quote plans, so large organizations will end up negotiating either way.
What Each Tool Is
Smartsheet looks and behaves like a spreadsheet first: rows, columns, and cell-level formulas, with Gantt, card, and calendar views layered on top of that grid. It leans toward teams coming from Excel who want automation and reporting without giving up the row-and-column mental model. monday.com leads with colorful, customizable boards and only secondarily offers grid/table views; it is built around visual status tracking, with automation recipes and dashboards as the connective tissue between boards. Both products have grown well beyond classic “project management” into broader work-management platforms, and both also sell separate CRM, dev, and service-desk products built on the same underlying engine.
Neither vendor publishes a non-annual per-seat price as prominently as the annual rate, and both require a minimum headcount on their lowest paid tiers (Smartsheet’s Pro plan caps at 10 members; monday.com requires at least 3 seats on every paid tier). Smartsheet’s Pro plan is also currently marked “new customers only” on its pricing page, which is worth confirming at signup time.
Gantt and Resource Management
This is the clearest functional difference between the two. Smartsheet includes a native Gantt view starting at its entry Pro tier, consistent with its spreadsheet-and-PM-tool identity. monday.com only unlocks Timeline and Gantt views once you move up to its Standard tier ($12/seat/mo annual), and true portfolio/resource-management features are reserved for its Enterprise tier. If Gantt charts and resource allocation are central to how your team plans work, Smartsheet gets you there at a lower tier.
Pros
Smartsheet: Native Gantt/resource tools from the entry tier; powerful formulas for teams that think in spreadsheets; unlimited automations on Business tier.
monday.com: Free plan available for very small teams; more visually intuitive for non-spreadsheet users; large template library and broader non-PM product line (CRM, Dev, Service).
Cons
Smartsheet: No permanent free tier; UI feels more utilitarian than monday.com’s boards; entry Pro tier caps at 10 members.
monday.com: Gantt/Timeline locked behind Standard tier, not Basic; every paid tier has a 3-seat minimum even for very small teams; automation/API call limits are more granular and easier to outgrow.
Who It’s a Good Fit For
Smartsheet fits operations, finance, and PMO teams that are migrating off Excel and want Gantt charts and formula-driven reporting without relearning their mental model. monday.com fits marketing, creative, and cross-functional teams that want a more visual, customizable board experience and are willing to pay for the Standard tier to get timeline views.
Who Should Look Elsewhere
Very small teams (1-2 people) who want to pay nothing should look at monday.com’s free plan or a dedicated free tool, since Smartsheet has no permanent free option. Teams that need resource/portfolio management on a budget should note that monday.com pushes that functionality to Enterprise, while Smartsheet offers it as a named add-on (Scenario Planning, Portfolios) at its own Enterprise tier — so budget-constrained teams needing that specific capability should compare both Enterprise quotes directly rather than assuming either is cheaper.
Bottom Line
At matching $19/seat/mo headline prices, Smartsheet’s Business tier and monday.com’s Pro tier deliver different things: Smartsheet gives you unlimited automations and 1TB of attachment storage, while monday.com gives you deeper workflow automation actions and private boards. The decision mostly comes down to whether your team’s planning habit is spreadsheet-native (pick Smartsheet) or board-and-visual-native (pick monday.com).
FAQ
Does Smartsheet have a free plan? No. Smartsheet offers a 30-day free trial with no credit card required, but there is no permanent free tier the way monday.com has one for up to 2 seats.
Which has better Gantt charts, Smartsheet or monday.com? Smartsheet includes Gantt views from its entry Pro tier. monday.com only unlocks Timeline/Gantt views starting at its Standard tier, one step up from Basic.
Can small teams use either tool cheaply? monday.com has a genuinely free plan for up to 2 seats. Smartsheet does not have a free tier, and both vendors require a minimum of 3 seats on most of their paid tiers above the entry level.
AI pair programming has split into two camps: standalone AI-native editors like Cursor, and AI layered onto the editor you already use, like GitHub Copilot or JetBrains AI Assistant. We already published a full standalone review of GitHub Copilot’s plans; this piece instead compares all three head-to-head so you can decide which fits your workflow, your IDE, and your budget in 2026.
At a Glance
Tool
Starting paid price
Free tier
Best for
Cursor
Pro, $20/month
Yes — Hobby plan, limited agent/chat usage
Developers who want an AI-first editor built around agentic, multi-file workflows
GitHub Copilot
Pro, $10/month
Yes — 2,000 inline suggestions/month, limited chat & agent use
Teams already standardized on GitHub who want AI woven into existing IDEs and GitHub.com
JetBrains AI Assistant
AI Pro, $20/month (JetBrains’ help docs also show a $10 price point for this tier — see note below)
Cursor (by Anysphere) is a standalone code editor forked from VS Code and rebuilt around AI from the ground up, rather than an extension bolted onto an existing IDE. Its core features are a codebase-aware Chat, inline Cmd+K edits, Tab-based multi-line autocomplete, and an Agent mode that can plan and execute multi-file changes, run commands, and iterate against test results with far less hand-holding than a basic autocomplete tool. Cursor also offers Cloud/background agents that work asynchronously and a Bugbot feature for automated pull-request review. It supports multiple underlying models (Anthropic, OpenAI, and Google model families among them) that you can switch between per task.
On pricing: Cursor’s published plan structure is Hobby (free, limited usage), Pro ($20/month), Pro+ ($60/month), and Ultra ($200/month) for individuals, with Teams plans starting around $40/user/month and custom Enterprise pricing. We’ll be straightforward about sourcing here: Cursor’s own pricing page did not render reliably through our research tooling during this session, so these figures are cross-checked against Cursor’s Wikipedia entry (which cites Cursor’s own site for the $20 Pro price) and independent, recently updated pricing trackers rather than a single live fetch. AI tool pricing changes often — confirm current numbers at cursor.com before buying.
GitHub Copilot
GitHub Copilot integrates into most major IDEs (VS Code, JetBrains IDEs, Visual Studio, Xcode, and more) plus a CLI, GitHub.com, and mobile. Per GitHub’s official plans page, the current lineup is Free, Pro ($10/month), Pro+ ($39/month), and Max ($100/month), each priced around a pool of “GitHub AI Credits” that cover chat and agent usage beyond unlimited inline suggestions (Free is capped at 2,000 inline suggestions/month). Business and Enterprise tiers add SAML SSO, usage metrics, IP indemnity, and org-wide user management, but GitHub’s plans page doesn’t publish their price or credit allotment — it routes that to a sales conversation. All paid tiers share the same model list and now support delegating work to third-party coding agents (Anthropic’s Claude and OpenAI’s Codex, in preview) from Pro+ and Max.
JetBrains AI Assistant runs inside JetBrains’ own IDEs (IntelliJ IDEA, PyCharm, WebStorm, Rider, and the rest of the family) and is priced on a credit system rather than flat feature tiers. Per JetBrains’ official AI Assistant licensing documentation, the tiers are AI Trial (free, time-limited), AI Free (3 credits per 30 days, unavailable in Android Studio and the Community editions), AI Pro, AI Ultimate, and AI Enterprise (organizations only). One AI credit equals $1 USD, and roughly: 10 AI Chat code-generation requests, 40 editor code-generation requests, 25 code explanations, or 280 documentation requests per credit — though “expensive” models and agentic use burn through credits faster.
A transparency note: JetBrains’ own licensing page currently shows two different price/credit pairings for the same tiers — one set lists AI Pro at $10 for 10 credits and AI Ultimate at $30 for 35 credits, while another set on the same page lists AI Pro at $20 for 20 credits and AI Ultimate at $60 for 70 credits — without clarifying which is current. We’re flagging that discrepancy explicitly rather than picking one number and presenting it as settled; check JetBrains’ store page directly for the figure that applies to your account before purchasing.
How the Coding Experience Differs
All three tools can generate a working function from a comment, but the depth of “agentic” behavior differs. A simple prompt like “write a function that calculates a discounted price and rejects invalid input” produces similar completions across all three — the differentiator shows up on multi-file, multi-step tasks, where Cursor’s Agent and GitHub Copilot’s agent mode will edit several files and run tests autonomously, while JetBrains AI Assistant leans more on in-editor chat and targeted code generation inside the file you’re already in.
// Typical completion all three tools can produce from a single comment prompt
function getDiscountedPrice(price, discountPercent) {
if (price <= 0 || discountPercent < 0 || discountPercent > 100) {
throw new Error("Invalid input");
}
return price - (price * discountPercent) / 100;
}
Whichever assistant you use, treat its output as a draft, not a finished patch — our AI-Generated Code Security in 2026 guide covers the review checklist every team should run against AI-generated code before it merges.
Pricing Comparison
Tier level
Cursor
GitHub Copilot
JetBrains AI Assistant
Free
Hobby — limited agent/chat
Free — 2,000 inline suggestions/month
AI Free — 3 credits/30 days
Entry paid
Pro, ~$20/month
Pro, $10/month
AI Pro, ~$10–$20/month (see note above)
Mid paid
Pro+, ~$60/month
Pro+, $39/month
AI Ultimate, ~$30–$60/month (see note above)
Top individual
Ultra, ~$200/month
Max, $100/month
Not published beyond Ultimate
Team/Enterprise
Teams from ~$40/user/month; Enterprise custom
Business/Enterprise — priced via sales
AI Enterprise — organizations only, via sales
Pros and Cons
Cursor pros: deepest agentic, multi-file workflow; fast Tab completion; flexible model choice.
Cursor cons: another editor to adopt instead of your current one; usage-based costs beyond the included pool can add up.
GitHub Copilot pros: works inside the IDE you already use; tightest GitHub.com/PR integration; cheapest entry paid tier of the three.
JetBrains AI Assistant pros: native to JetBrains IDEs; bundled free with some JetBrains subscriptions (per its licensing page); granular credit-based billing.
JetBrains AI Assistant cons: locked to the JetBrains IDE family; JetBrains’ own pricing documentation currently contains conflicting price/credit figures.
Who Should Pick Which
Pick Cursor if you’re willing to switch editors for the most autonomous, agentic coding experience available today. Pick GitHub Copilot if your team is already on GitHub and you want AI assistance inside your current IDE without changing tools, at the lowest individual entry price of the three. Pick JetBrains AI Assistant if your team already lives in IntelliJ, PyCharm, WebStorm, Rider, or another JetBrains IDE and you’d rather not add a second AI subscription from a different vendor.
Bottom Line
There’s no single winner — the right choice follows your existing toolchain more than any one feature. GitHub Copilot is the safest, cheapest default if you’re GitHub-centric. JetBrains AI Assistant is the obvious choice if you’re already paying for JetBrains IDEs. Cursor is worth the editor switch if agentic, multi-file autonomy is the thing you actually need. Whichever you choose, verify current pricing directly with the vendor — all three companies update tiers and credit allowances more often than most review articles get updated.
FAQ
Can I use GitHub Copilot inside a JetBrains IDE? Yes — GitHub’s plans page confirms IDE/editor support across major editors including JetBrains IDEs, so Copilot and JetBrains AI Assistant can technically coexist in the same editor.
Is Cursor based on VS Code? Yes, Cursor is built as a fork of Visual Studio Code, which is why most VS Code extensions and keybindings carry over.
Does JetBrains AI Assistant work in the free Community editions? Per JetBrains’ licensing documentation, AI Free is not available in Android Studio or in PyCharm/IntelliJ IDEA Community editions or trial licenses — you need a paid or All Products Pack-eligible JetBrains product.
Which tool is cheapest to start with? GitHub Copilot Pro has the lowest published entry price of the three at $10/month, versus roughly $20/month for Cursor Pro and JetBrains AI Pro (subject to the pricing discrepancy noted above).
Do any of these tools have a free tier? Yes — all three do: Cursor’s Hobby plan, GitHub Copilot’s Free plan (2,000 inline suggestions/month), and JetBrains’ AI Free tier (3 credits/30 days).
“Turn on two-factor authentication” has been standard security advice for over a decade. “Set up a passkey” is the newer instruction, and it’s starting to replace the old advice rather than sit alongside it. The two aren’t quite the same category of thing: most two-factor authentication (2FA) methods add a second step on top of a password, while a passkey is designed to remove the password entirely. Here’s what each one actually does under the hood, what the FIDO Alliance and NIST say about their relative security, and which one you should set up first — for your own accounts and, if you run a site, for your users.
At a Glance
Method
Resists phishing?
Setup friction
Device dependency
Passkey (FIDO2/WebAuthn)
Yes — FIDO Alliance describes passkeys as always strong and “phishing-resistant” by design
Low once set up (unlock device/biometric); initial setup is per-site
Tied to a device or synced via a platform keychain (iCloud Keychain, Google Password Manager, etc.)
SMS one-time code
No — NIST restricts use of the public phone network for this reason
Lowest — works on any phone, no app needed
Tied to a phone number, vulnerable to SIM swapping/number porting
TOTP authenticator app
Partial — codes can still be phished and relayed in real time by the user
Medium — requires installing and configuring an app per account
Tied to whichever device holds the app, unless backed up
How Passkeys Actually Work
A passkey is a credential built on FIDO2/WebAuthn, the open authentication standard maintained by the FIDO Alliance. Apple’s own developer documentation describes the mechanism clearly: when you register a passkey with a site, your device generates a unique public/private key pair for that specific account. The public key is sent to the site’s server; Apple explicitly notes this key “isn’t a secret,” so there’s nothing sensitive to steal if the server is breached. The private key never leaves your device. To sign in, the site sends a challenge, your device signs it with the private key after you unlock the device (Face ID, Touch ID, fingerprint, or a screen PIN), and the server verifies the signature against the public key it already has.
That structure is what makes passkeys resistant to phishing by design rather than by user vigilance: a fake look-alike login page has no way to extract a private key that never leaves your device, and a passkey registered for one domain simply will not produce a valid signature for a different, impersonating domain. The FIDO Alliance states this directly — passkeys “use public key cryptography” in a challenge-response protocol and are “always strong and phishing-resistant” compared with passwords, in part because there are no shared secrets stored on the server for an attacker to steal in a database breach. Apple’s documentation separately calls passkeys “highly phishing-resistant” and notes each key pair is generated “securely and uniquely, for every account.” Google describes the same property more plainly in its own help documentation: passkeys offer “stronger protection against threats like phishing,” and unlike a password, a passkey “can’t be shared, copied, written down, or accidentally given to someone else.”
Passkeys can live in different places. Apple devices sync them end-to-end encrypted through iCloud Keychain; Google can register them automatically for Android devices or sync through Google Password Manager; and FIDO2 hardware security keys can hold device-bound passkeys that never sync anywhere. Microsoft Authenticator also supports creating and storing passkeys for Microsoft and third-party accounts. The FIDO Alliance distinguishes between these: device-bound passkeys on a dedicated hardware key offer the highest assurance level, while synced passkeys back themselves up through a password-protected cloud keychain, which the Alliance notes can itself become a target if that account is compromised.
How Two-Factor Authentication Actually Works
Two-factor authentication keeps the password as the first factor and adds a second proof of identity on top of it. The two most common second factors are an SMS/voice one-time code sent to your phone, and a time-based one-time passcode (TOTP) generated by an authenticator app (Google Authenticator, Microsoft Authenticator, Authy, etc.) using the algorithm defined in RFC 6238, which both factors reference.
These two methods are not treated as equally secure, including by the U.S. government’s own digital identity guidelines. NIST Special Publication 800-63B restricts the use of the public switched telephone network (which covers SMS and voice calls) for out-of-band verification, stating specifically that verifiers “SHOULD consider risk indicators” such as a recent SIM change, device swap, or number porting before relying on it — precisely because an attacker who takes over your phone number can intercept the code. TOTP app codes avoid the SIM-swap problem since they’re generated locally on a device rather than delivered over the phone network, but they still rely on you (or an attacker who tricks you) typing the code into whatever page is asking for it. If that page is a real-time phishing proxy sitting between you and the real site, a TOTP code can be captured and relayed within its short validity window just like a password can — the code itself doesn’t know or verify which domain is asking for it. That’s the structural difference from a passkey: a passkey’s cryptographic signature is tied to the requesting domain automatically, while a one-time code is just a string of digits that works wherever it’s typed.
NIST’s framework separately defines Authenticator Assurance Level 3 (AAL3), its highest tier, which requires a hardware-based authenticator and what it calls “verifier impersonation resistance.” A FIDO2 hardware security key is the kind of authenticator built to satisfy that bar; SMS and basic TOTP combinations are not positioned at that level in NIST’s model.
Comparison Table
Property
Passkey
SMS 2FA
TOTP app 2FA
Underlying mechanism
Public-key cryptography (FIDO2/WebAuthn)
One-time code sent over the phone network
One-time code generated locally (RFC 6238)
Vulnerable to phishing proxy/relay
No — signature is domain-bound
Yes
Yes
Vulnerable to SIM swap
No
Yes — explicitly flagged as a risk by NIST
No
Works without a password at all
Yes — designed to replace the password
No — adds to a password
No — adds to a password
Cross-device setup
Syncs via platform keychain or requires a hardware key
Tied to one phone number
Tied to app install unless manually backed up
Universally supported today
Growing but not universal — per FIDO Alliance-commissioned survey data, 53% of surveyed users had enabled a passkey on at least one account as of 2024
Nearly universal
Widely supported, slightly less universal than SMS
Which Should You Use?
As an end user: enable a passkey everywhere it’s offered — on Google, Apple, Microsoft, and major financial and shopping accounts that support it — since it removes the password-phishing risk entirely for that login. Where a passkey isn’t offered yet, use a TOTP authenticator app over SMS whenever you have the choice, since it isn’t exposed to SIM-swap attacks. Keep SMS 2FA as a fallback/recovery option rather than your primary second factor if the service allows you to choose.
As a site owner deciding what to support: supporting passkeys via WebAuthn gives your most security-conscious users the strongest available option and, per vendor-reported figures cited by the FIDO Alliance, can reduce sign-in friction (Google has reported roughly a 4x improvement in sign-in success rate with passkeys versus passwords). But don’t drop 2FA to do it — passkey adoption is still growing, device and browser support varies, and account-recovery flows for lost devices need careful design. A pragmatic rollout order is: keep passwords as a baseline, add TOTP-based 2FA as the default second factor, and offer passkeys as the preferred, promoted option for users whose devices support them, with SMS reserved for account recovery rather than as a primary factor.
The Bottom Line
Passkeys and two-factor authentication solve overlapping but different problems. 2FA is a patch on top of passwords that makes stolen credentials less useful on their own; passkeys are a replacement for passwords that removes the shared secret attackers are after in the first place. Both the FIDO Alliance and the platform vendors (Apple, Google) describe passkeys as phishing-resistant by construction, while NIST’s own guidelines flag SMS-delivered codes as the weakest widely used second factor because of SIM-swap risk. If you can only do one thing this year, turning on a passkey wherever it’s available is the higher-leverage move; keeping a TOTP app as your 2FA fallback everywhere else is the second-best option, well ahead of relying on SMS codes alone.
FAQ
Is a passkey a type of two-factor authentication? Not exactly. A passkey is a single credential that proves both “something you have” (the device) and “something you are/know” (the biometric or PIN that unlocks it), so services like Google count a passkey as satisfying 2-Step Verification on its own rather than needing a separate second factor layered on top.
What happens if I lose the device my passkey is on? If your passkey synced through a platform keychain (iCloud Keychain, Google Password Manager, etc.), you can usually recover it by signing into that keychain on a new device, subject to that platform’s own recovery process. Apple’s own documentation warns that iCloud Keychain recovery uses a limited number of attempts, after which the keychain is permanently lost, which is why most services still require a backup sign-in method.
Why does NIST treat SMS codes as weaker than an app-based code? NIST SP 800-63B specifically restricts use of the public switched telephone network for one-time codes and instructs verifiers to weigh risk signals like a recent SIM change or number port before trusting it, because a phone number can be hijacked independently of the account itself. An authenticator app’s code isn’t exposed to that particular attack.
Can passkeys be phished at all? The FIDO Alliance and platform vendors describe passkeys as resistant to the classic phishing pattern (a fake site capturing a password the user types in) because the cryptographic signature is bound to the real site’s domain. That doesn’t make every part of an account’s security unphishable — account-recovery flows, the device’s own unlock mechanism, and the cloud account syncing the passkey can still be separate targets.
Should a WordPress or small business site bother supporting passkeys yet? If your site or its login plugin supports WebAuthn, enabling it as an option costs little and benefits your more security-conscious users immediately; just don’t remove existing password/2FA options, since passkey support and adoption are still uneven across browsers and devices.
Supply-chain attacks target the pipeline, not just the application — a compromised dependency, a stolen deploy token, or a tampered build step can ship malicious code without ever touching the source repository a reviewer actually read. Three frameworks give teams a shared, non-vendor-specific vocabulary for defending against this: OWASP’s Top 10 CI/CD Security Risks, the SLSA (Supply-chain Levels for Software Artifacts) specification, and NIST’s Secure Software Development Framework (SP 800-218, SSDF). This checklist translates them into concrete controls you can actually implement.
At a Glance
Risk Category
Core Control
Why It Matters
Dependency / supply-chain abuse
Pin dependencies to exact versions or hashes; generate an SBOM
Unpinned or unverified dependencies let attackers slip malicious code in through a routine update (OWASP CICD-SEC-3)
Pipeline execution hijacking
Treat pipeline config files (and anything they can trigger) as code requiring review; restrict what forked-PR workflows can run
Attacker-controlled pipeline definitions can run arbitrary commands with the pipeline’s privileges (OWASP CICD-SEC-4, “Poisoned Pipeline Execution”)
Identity & access
Least-privilege, short-lived, scoped credentials for every runner and service account
Overly broad or long-lived pipeline credentials are a top target once an attacker gets any foothold (OWASP CICD-SEC-2, CICD-SEC-6)
Artifact integrity
Sign commits and build artifacts; verify signatures before deploy
Without verification, a tampered artifact is indistinguishable from a legitimate one (OWASP CICD-SEC-9)
Build provenance
Generate signed provenance describing how an artifact was built (SLSA Build track)
Lets consumers verify an artifact came from the expected source and build process, not a tampered one
Secrets management
Centralized secrets manager, no plaintext secrets in config or environment files, automatic rotation
Leaked long-lived credentials are one of the most common real-world pipeline breach vectors
Logging & visibility
Centralized, tamper-resistant logs of every pipeline run and who triggered it
Without logs, a compromise can go undetected indefinitely (OWASP CICD-SEC-10)
Dependency and Supply-Chain Controls
Most real-world software supply-chain incidents start with a dependency, not a hand-written line of code. OWASP’s Top 10 CI/CD Security Risks names this “Dependency Chain Abuse” (CICD-SEC-3): attackers compromise or impersonate a package your build pulls in, and your pipeline happily builds it into your release.
Pin dependencies to exact versions, and where your package ecosystem supports it, to a content hash — not a floating version range.
Generate a Software Bill of Materials (SBOM) for every build so you can quickly answer “are we affected?” when a new CVE breaks.
Vet new and updated third-party components before they’re approved for use, per NIST SSDF practice PW.4 (“Reuse Well-Secured Software”), rather than letting any package anyone adds get built automatically.
Mirror or proxy public package registries internally so a registry-level compromise or a removed package can’t silently break or poison your builds.
Trade-off: strict pinning slows down picking up security patches automatically — you need a deliberate, scheduled update process (with automated vulnerability scanning) rather than relying on floating versions to “self-heal,” which is itself an attack surface.
Pipeline Execution and Configuration
OWASP calls out “Poisoned Pipeline Execution” (CICD-SEC-4) as a distinct risk: if an attacker can modify the pipeline definition itself — a CI config file, a build script, an included template — they can make the pipeline run arbitrary commands with whatever privileges that pipeline holds, often including access to production secrets.
Require code review on any change to pipeline configuration files, exactly as you would for application code.
Run workflows triggered by forked-repository pull requests with no access to secrets, or require explicit maintainer approval before they run at all.
Disallow pipeline steps from being defined by untrusted, dynamically fetched content at build time.
Address “Insufficient Flow Control” (CICD-SEC-1) by enforcing required approvals/gates between code merge and production deploy — a pipeline that can push straight from an unreviewed commit to production has no human check left in the loop.
Identity, Access, and Secrets
OWASP groups several related risks here: “Inadequate Identity and Access Management” (CICD-SEC-2), “Insufficient PBAC / Pipeline-Based Access Controls” (CICD-SEC-5), and “Insufficient Credential Hygiene” (CICD-SEC-6). The common thread is that pipelines, build agents, and service accounts routinely get more access than the specific job they run actually needs, and that access doesn’t expire on its own.
Give each runner and service account the minimum scope needed for its specific job — a job that only needs to read one repository should not hold a token that can push to all of them.
Prefer short-lived, automatically rotated credentials (OIDC-based cloud role assumption, for example) over static API keys and tokens.
Store secrets exclusively in a dedicated secrets manager, never in plaintext environment variables, config files, or source control.
Separate credentials and access between non-production and production pipelines; a compromised staging pipeline shouldn’t be able to reach production deploy keys.
This also maps directly onto NIST SSDF’s “Prepare the Organization” group, specifically PO.5, which calls for separating and hardening development, build, test, and distribution environments rather than running everything on shared, loosely controlled infrastructure.
Artifact Integrity and Build Provenance
“Improper Artifact Integrity Validation” (OWASP CICD-SEC-9) covers the gap where a build output is deployed without any check that it’s actually the artifact the pipeline produced, unmodified. The SLSA framework (slsa.dev) gives this a formal, incremental structure through its Build track levels:
SLSA Build L1: provenance (metadata describing how the artifact was built) exists and is distributed, but it isn’t signed — useful for catching honest mistakes, not for stopping a determined attacker.
SLSA Build L2: builds run on a dedicated, hosted build platform (not a developer’s laptop), and the provenance is cryptographically signed and tied to that platform — this is the level at which post-build tampering becomes detectable.
SLSA Build L3: the build platform additionally isolates each build run from every other run and keeps the signing material inaccessible to user-defined build steps — this is the level that defends against tampering during the build itself, including by insiders or compromised build definitions.
Practical controls that implement this:
Require signed commits so every change in history can be attributed to a verified identity (NIST SSDF PS.1).
Sign build artifacts and container images, and enforce signature verification as a hard gate before deployment, not an optional check.
Generate and publish cryptographic hashes or SLSA-format provenance for every release so downstream consumers (or your own deploy tooling) can verify it (NIST SSDF PS.2).
Archive release artifacts and their provenance/SBOM data so a future vulnerability disclosure can be traced back to exactly which builds are affected (NIST SSDF PS.3).
Trade-off: SLSA L3-equivalent build isolation is meaningfully harder to operate than L1 or L2 — it typically means adopting a managed, ephemeral build platform rather than long-lived self-managed runners. Most teams are better served by reaching L2 broadly (signed provenance from a hosted, non-developer-machine build) before chasing L3 everywhere.
Third-Party Services and Logging
Two more OWASP risks round out the list: “Ungoverned Usage of 3rd Party Services” (CICD-SEC-8) — pipeline integrations and marketplace actions adopted without security review, each one a new potential access path into your build — and “Insufficient Logging and Visibility” (CICD-SEC-10), where a compromise can persist undetected simply because no one is watching pipeline activity closely enough to notice it.
Maintain an approved allowlist of third-party CI actions/plugins, and pin them to a specific commit or version rather than a floating tag.
Review the permissions any new third-party integration requests before approving it, the same way you’d review an OAuth app request.
Centralize pipeline logs outside the CI system itself, so an attacker who compromises the CI platform can’t also erase the evidence.
Alert on anomalous pipeline behavior — new secrets accessed, unusual deploy targets, runs triggered outside normal hours — rather than only reviewing logs after an incident.
Vulnerability Response
NIST SSDF’s “Respond to Vulnerabilities” (RV) group is the piece teams most often skip because it isn’t about prevention — it’s about what happens after something is found. RV.1 calls for gathering vulnerability information from public sources and researchers and maintaining a disclosure policy; RV.2 calls for assessing and remediating each one based on actual risk; RV.3 calls for root-cause analysis so the same class of issue doesn’t recur. A secure pipeline that can’t quickly answer “which of our artifacts contain this dependency” — which is exactly what an SBOM and build provenance are for — turns a routine disclosure into a multi-week fire drill. If you’re also managing AI-assisted development, our AI-generated code security review checklist covers the related question of reviewing code your pipeline builds but nobody fully hand-wrote.
The Checklist
Dependencies pinned to exact versions or hashes, with an SBOM generated per build
New/updated third-party components vetted before approval
Pipeline configuration files reviewed like code, with no untrusted dynamic content executed at build time
Forked-PR workflows blocked from secrets or gated behind maintainer approval
Required approval gates between merge and production deploy
Least-privilege, short-lived credentials per runner/service account; no static long-lived tokens where avoidable
Secrets stored only in a dedicated secrets manager, never in plaintext config or source control
Production and non-production pipeline credentials fully separated
Commit signing required; signature verification enforced before merge where feasible
Build artifacts signed, with signature verification as a hard gate before deployment
Builds run on a dedicated, hosted build platform — not a developer workstation — targeting at least SLSA Build L2
Release artifacts and provenance/SBOM data archived for future vulnerability lookups
Third-party CI actions/plugins allowlisted and version-pinned
Pipeline logs centralized outside the CI platform, with alerting on anomalous activity
A documented vulnerability disclosure and response process, with root-cause analysis after remediation
Bottom Line
Securing a CI/CD pipeline against supply-chain attacks isn’t one control, it’s the accumulation of many small ones: pin what you depend on, treat pipeline config as code, scope credentials tightly, sign what you build, and log everything so a breach doesn’t stay invisible. OWASP’s Top 10 names the specific risks, SLSA gives you a concrete, incremental ladder for build integrity, and NIST’s SSDF ties it all into a broader secure-development lifecycle. None of these require buying a specific vendor’s product — they’re a checklist you can start implementing with the CI system you already have.
FAQ
What’s the single highest-priority control to start with?
Least-privilege, short-lived credentials for pipeline runners and service accounts. Overly broad, long-lived credentials are consistently the mechanism that turns a minor pipeline compromise into full production access.
What’s the difference between SLSA and an SBOM?
An SBOM (Software Bill of Materials) lists what components are in an artifact. SLSA provenance describes how the artifact was built — the build platform, process, and inputs — and, at higher levels, is cryptographically signed so it can’t be forged or altered after the fact. They’re complementary, not substitutes.
Do we need to reach SLSA Build L3 to be considered secure?
Not necessarily. L3 defends specifically against tampering during the build, including by insiders — a real but narrower threat than what L2 (signed provenance from a hosted build platform) already addresses. Most organizations get the majority of practical benefit by reaching L2 consistently before investing in L3’s build-isolation requirements.
Is dependency pinning enough to stop supply-chain attacks?
No. Pinning stops a dependency from silently changing out from under you, but it doesn’t catch a malicious package that was already malicious when you first pinned it. It needs to be paired with vetting new/updated components and scanning for known vulnerabilities on a deliberate schedule.
Where do these frameworks overlap?
Heavily. OWASP’s risks describe specific attack patterns in CI/CD systems; NIST’s SSDF describes organization-wide practices across the whole development lifecycle (of which pipeline security is one part); SLSA focuses narrowly and technically on verifying how a specific artifact was built. Using all three together covers the risk-identification, organizational-practice, and technical-verification angles respectively.
“Low-code” now covers a wide spread of products, from enterprise platforms that generate production Java and .NET behind a visual canvas, to browser-only tools that non-developers use to ship a working app in a weekend. OutSystems, Microsoft Power Apps, and Bubble sit at three different points on that spectrum. This comparison looks at what each one actually costs as of late 2026, who each is realistically built for, and the practical limits on what you can and can’t build on each — based on their current official pricing and platform pages.
At a Glance
Platform
Starting Price
Free Tier
Best For
OutSystems
Custom quote (no published starting price for production use)
Personal Edition — free, development-only, up to 100 internal users, no production deployment
Enterprise teams building complex, high-governance internal or customer-facing apps alongside professional developers
Microsoft Power Apps
Free (Developer Plan); $20/user/month for Premium, billed yearly
Developer Plan — free, includes Dataverse, connectors, and up to 750 automated flows/month, for development/testing environments
Organizations already on Microsoft 365 / Azure that want apps wired into Dataverse, Teams, and Microsoft’s connector ecosystem
Bubble
Free; paid plans from $59/month (Starter, billed annually)
Free plan — 50,000 workload units/month, full visual editor, no live custom domain
Founders, small teams, and agencies building web apps and MVPs without writing backend code
OutSystems targets large organizations building complex, integration-heavy applications that need to sit alongside — not replace — a professional engineering team. Its current public pricing page lists two things for individuals and prospects: a free “Personal Edition” for learning and prototyping, which is development-only (no production runtime, no uptime guarantee, no compliance certifications, capped at 100 internal users), and the “Agentic Systems Platform,” which is quote-based and requires talking to sales to get a number. OutSystems’ official pricing page states that real-world cost depends on “Application Objects” (screens, database tables, and API methods), the number of non-anonymous internal and external end users, and any add-ons — a usage- and scale-based model rather than a flat per-seat price. Add-ons such as 24/7 support, additional runtimes, higher uptime SLAs (99.95%), and compliance certifications like SOC 2 Type II and PCI DSS are also quote-based.
What you can build: full-stack web and mobile applications with substantial custom logic, integrations into legacy systems, and workflow/business-process apps — the platform generates real application code and is explicitly positioned for applications professional developers extend, not purely citizen-developer projects. What you typically can’t do cheaply: see your real production cost before engaging sales, since there’s no self-serve paid tier published.
Microsoft Power Apps: Low-Code Inside the Microsoft Ecosystem
Power Apps is priced per user, with two self-serve tiers on Microsoft’s official pricing page. The Developer Plan is free and includes three development environments, Dataverse, prebuilt/custom/on-premises connectors, and up to 750 automated flow runs per month — intended for building and testing, not for distributing an app to end users. The production tier, Premium, is $20 per user per month billed yearly for unlimited use of Power Apps and Power Pages by that licensed user, Dataverse storage, and (per Microsoft’s page) agentic features and Microsoft 365 Copilot chat inside apps. A separate Premium tier with a 2,000-seat minimum brings the per-user price down to $12/user/month billed yearly, aimed at large-scale internal rollouts. Additional Dataverse database capacity is billed separately at $40/GB/month (pooled at the tenant level, billed yearly). Microsoft’s page notes that displayed prices are for planning purposes and the exact price is confirmed at checkout and can vary by region and currency.
What you can build: forms-over-data business apps, workflow automation tied to Power Automate, and apps that read/write Dataverse or hundreds of prebuilt connectors to other Microsoft and third-party services — a strong fit if your organization already runs on Microsoft 365, SharePoint, Dynamics, or Azure. What’s harder: Power Apps is less suited to highly custom, pixel-perfect consumer-facing UI or workloads that don’t map well onto Dataverse’s data model, and per-user licensing can get expensive quickly for apps meant to be used by a large, undefined public audience rather than named internal users.
Bubble: No-Code for Web Apps and MVPs
Bubble is the most self-serve and the most clearly tiered of the three. Its official pricing page lists a Free plan (50,000 workload units/month, full editor, no live custom domain — meant for apps still under construction), then four paid tiers billed per project: Starter at $59/month (175,000 workload units, live website with custom domain, basic version control, mobile build submissions), Growth at $209/month (250,000 workload units, premium version control, two-factor authentication, more server-log retention), Team at $549/month (500,000 workload units, multiple app editors, sub-apps), and a custom-quote Enterprise tier with dedicated hosting and support. All prices on the page are for annual billing, which Bubble says can save up to 20% versus monthly. Extra file storage is billed at $3 per 100 GB/month, and plugin subscriptions are separate.
What you can build: full web applications — including backend logic, database, and workflow automation — entirely through Bubble’s visual editor, without writing conventional backend code, plus a large plugin and API-connector ecosystem for extending functionality. What’s harder: Bubble’s workload-unit pricing model ties cost directly to runtime usage (database operations, workflow executions, API calls), so an app with a lot of backend activity can become expensive faster than its sticker price suggests, and Bubble does not generate portable source code the way OutSystems or Power Apps’ Dataverse-backed model can be extended with pro-code.
Pricing Comparison
Platform
Free Option
Entry Paid Tier
Pricing Model
OutSystems
Personal Edition (dev-only, 100 users)
Custom quote only — no published self-serve paid tier
Usage-based: Application Objects + end users + add-ons
Power Apps
Developer Plan (dev/test only)
$20/user/month (Premium, billed yearly)
Per named user per month, plus metered Dataverse storage add-ons
Bubble
Free plan (50K workload units/mo)
$59/month (Starter, billed annually)
Per project, tiered by monthly workload units with metered overage
Pros and Cons
OutSystems
Pros: built for complex, high-governance enterprise apps; generates real application code developers can extend; strong integration and compliance options as paid add-ons.
Cons: no published self-serve production pricing — you need a sales conversation to know your real cost; overkill for a simple app or MVP.
Microsoft Power Apps
Pros: deep, native integration with Microsoft 365, Teams, Dynamics, and Azure; predictable published per-user pricing; strong for internal line-of-business apps.
Cons: per-user licensing scales awkwardly for public-facing apps with many or anonymous users; less natural fit outside the Microsoft ecosystem.
Bubble
Pros: fastest path from idea to a live, usable web app with no backend coding; transparent published tiers; large plugin ecosystem.
Cons: workload-unit billing means cost can grow with usage in ways that are hard to predict upfront; less suited to deep enterprise system integration or strict compliance requirements than OutSystems.
Who Should Pick Which
Choose OutSystems if you’re a mid-size-to-large organization building a mission-critical, integration-heavy application that professional developers will maintain long-term, and you need enterprise support and compliance options more than you need a published self-serve price. Choose Microsoft Power Apps if your organization already runs on Microsoft 365 or Dynamics and you’re building internal tools for a known, named set of employees — the per-user pricing and Dataverse integration are built for exactly that case. Choose Bubble if you’re a founder, small team, or agency that needs to get a real, usable web application in front of users quickly, without hiring backend engineers, and can tolerate usage-based pricing that scales with your app’s actual activity.
Bottom Line
These three platforms aren’t really interchangeable options for the same job. OutSystems competes for enterprise app-dev budgets and prices accordingly (opaque until you talk to sales). Power Apps is the default choice if you’re already paying for Microsoft 365 and want apps that plug into that ecosystem. Bubble is the fastest, cheapest way to get an independent web app live, with pricing that’s transparent but tied to how much your app actually does. Match the platform to your organization’s existing stack and your tolerance for usage-based billing before committing.
FAQ
Is OutSystems more expensive than Power Apps or Bubble?
It’s generally positioned for larger budgets, but OutSystems doesn’t publish a self-serve production price, so a direct number-for-number comparison isn’t possible from public pricing alone. Its free Personal Edition is development-only and can’t be used to run a production app.
Can I build a customer-facing public app on Power Apps without per-user licensing?
Power Apps’ Premium plans are licensed per named user. Microsoft’s pricing page describes Power Pages as included in Premium for building external-facing sites, but public, high-volume consumer apps generally fit better with usage-based platforms like Bubble or a custom build.
Does Bubble require any coding at all?
No — Bubble’s core value proposition is building both frontend and backend logic visually. Code-level extensibility comes through its plugin and API-connector ecosystem rather than writing conventional backend code directly.
What happens if a Bubble app exceeds its plan’s workload units?
Paid plans can enable metered overage tiers for extra workload, and Bubble emails account owners at 75% and 100% of their monthly allowance. The Free plan does not support overage.
Can I move off OutSystems, Power Apps, or Bubble later if I outgrow them?
OutSystems generates application code that is more portable in principle than a purely proprietary runtime. Power Apps’ logic and data (Dataverse) are more tightly bound to the Microsoft ecosystem. Bubble does not export to a conventional codebase, so migrating off it typically means rebuilding the application rather than exporting it.
Every long-running program allocates memory it eventually stops using, and someone has to reclaim that memory or the process eventually runs out. In languages like C, that someone is the programmer, and getting it wrong produces leaks, double-frees, and use-after-free bugs. Java, Go, and Python all take that job away from the programmer, but they do it with genuinely different mechanisms, tuned for different trade-offs between pause time, throughput, and memory overhead. This explainer sticks to what each language’s own official documentation and engineering blogs say about how their collectors actually work.
At a Glance
Runtime
Primary Strategy
Pause Behavior
Typical Use Case
JVM (HotSpot) — G1
Generational, mostly-concurrent tracing collector
Targets a pause-time goal “with high probability”, default on most hardware
General-purpose server applications where response time matters more than raw throughput
JVM (HotSpot) — ZGC
Fully concurrent, generational tracing collector
Max pauses under one millisecond, independent of heap size
Low-latency applications with heaps from a few hundred MB up to 16 TB
Go runtime
Concurrent tracing mark-sweep collector, parallelized across cores
Runs concurrently with your goroutines; short stop-the-world phases for setup
General-purpose networked/cloud services
CPython
Reference counting, backed by a generational cyclic collector
Refcounting frees objects immediately; the cyclic collector runs periodically and can be tuned or disabled
General-purpose scripting; the cyclic collector exists specifically to catch reference cycles
Why Automatic Memory Management Exists
In a language with manual memory management, every allocation needs a matching, correctly-timed deallocation. Free too early and you get a use-after-free; never free and you get a leak; free twice and you get undefined behavior. Garbage collectors exist to make these bugs structurally impossible (or at least much rarer) by having the runtime itself figure out when memory is no longer reachable and reclaiming it automatically. The three ecosystems covered here solve that problem with different core techniques: tracing (follow references from a set of roots and reclaim what you don’t reach) and reference counting (track how many references point at an object and reclaim it when that count hits zero). Java and Go use tracing; Python uses reference counting as its primary mechanism, with a tracing collector as a backstop.
The JVM’s Collectors: G1 and ZGC
Oracle’s HotSpot documentation describes several collectors, but two matter most for modern server workloads. G1 (Garbage-First), enabled with -XX:+UseG1GC and the default on most hardware and OS configurations, is described by Oracle as “mostly concurrent”: it performs some of its most expensive work concurrently with the running application, and is designed to meet a pause-time goal with high probability while still achieving high throughput. It scales from small machines up to large multiprocessors with lots of memory, and Oracle recommends it when response time matters more than peak throughput.
ZGC, enabled with -XX:+UseZGC -XX:+ZGenerational for its generational mode, is fully concurrent rather than mostly concurrent. Oracle’s documentation states ZGC keeps maximum pause times under one millisecond, independent of heap size, and that it’s designed for low-latency applications with heap sizes ranging from a few hundred megabytes up to 16 terabytes — at some cost in throughput compared to G1. Oracle’s general tuning principle applies to both: throughput is inversely proportional to how much memory is available, because collections happen when a generation fills up, so total heap size is the single most important factor in GC performance. Oracle’s own starting-point guidance is straightforward: if peak throughput matters most and pauses of a second or more are tolerable, use the Parallel collector; if response time matters more than throughput, use G1; if response time is a high priority, use ZGC.
Go’s Concurrent Mark-Sweep Collector
Go’s runtime uses a tracing mark-sweep collector. According to the Go team’s own blog, the mark phase walks the object graph starting from roots (global and local variables) and marks every object it reaches; the sweep phase then frees everything that was never marked. Critically, this runs concurrently with your regular Go code and is parallelized across CPU cores, rather than stopping your whole program for the full collection the way older or simpler collectors do. The Go team’s own analysis found that marking accounts for roughly 90% of total GC cost, with sweeping making up the rest, and that the graph walk’s unpredictable jumps between objects and memory pages hurt CPU cache performance — a cost that’s grown worse as hardware trends (NUMA, lower per-core memory bandwidth, more cores contending on shared work queues) have progressed. Some Go programs reportedly spend 20% or more of their total CPU time in the garbage collector as a result.
To address this, the Go team has been developing “Green Tea GC,” an experimental redesign whose core idea, per the Go blog, is to “work with pages, not objects” — tracking whole memory pages on the work list instead of individual objects, with per-object “seen” and “scanned” bits on each page so the collector can scan a page’s pending objects in one in-memory-order pass. In Google’s internal benchmark suite, this cut GC CPU time by 10% to 40% (about 10% typical), though some workloads saw no benefit or slightly regressed. Green Tea GC is experimental in Go 1.25 (opt-in via GOEXPERIMENT=greenteagc) with plans to make it the default in Go 1.26.
CPython: Reference Counting Plus a Generational Cyclic Collector
Python’s approach is structurally different from Java’s and Go’s. CPython’s primary mechanism is reference counting: every object tracks how many references point at it, and when that count reaches zero, CPython frees the object immediately, with no separate “sweep” pass required. The problem reference counting cannot solve on its own is a reference cycle — two or more objects that reference each other (directly or indirectly) so their counts never reach zero, even after nothing outside the cycle can reach them. This is where CPython’s gc module comes in: Python’s own documentation describes it as an “optional cyclic garbage collector” that supplements reference counting specifically to catch these cycles.
A minimal example of the problem the cyclic collector exists to solve:
import gc
class Node:
def __init__(self):
self.other = None
a = Node()
b = Node()
a.other = b
b.other = a # a reference cycle: a -> b -> a
del a, b # reference counts never reach zero on their own
print(gc.collect()) # the cyclic collector finds and frees them
Per the official docs, the cyclic collector sorts tracked objects into three generations: new objects start in generation 0, and any object that survives a collection is promoted to the next older generation, with generation 2 being the oldest. A collection is triggered once the count of allocations minus deallocations exceeds threshold0; generation 1 is examined once generation 0 has been checked more than threshold1 times since generation 1 was last checked, with generation 2 following its own, more involved rules. The thresholds are tunable via gc.set_threshold(), and automatic collection can be disabled entirely by setting threshold0 to 0 — something the docs note is reasonable only if you’re confident your program creates no reference cycles. Unreachable objects that still can’t be freed (typically from C extension types with certain finalizer slots) land in the gc.garbage list rather than silently leaking without a trace.
Comparing the Mechanisms
Mechanism
Core Technique
Concurrent With App?
Generational?
Handles Reference Cycles?
JVM G1
Tracing (mark-and-reclaim)
Mostly — some work runs concurrently
Yes
Yes, inherently (tracing collectors don’t rely on counts)
JVM ZGC
Tracing (mark-and-reclaim)
Fully concurrent
Yes (generational mode)
Yes, inherently
Go runtime
Tracing mark-sweep
Yes, concurrent and parallel across cores
No (Go’s collector is not generational)
Yes, inherently
CPython
Reference counting + tracing backstop
Refcounting: immediate, synchronous; cyclic GC: runs periodically, not continuously concurrent
Yes, for the cyclic collector (3 generations)
Only via the separate cyclic collector — refcounting alone cannot
Trade-offs
Pause time vs. throughput: ZGC buys sub-millisecond pauses at some throughput cost versus G1; Oracle’s own guidance frames this explicitly as a trade a team should choose deliberately, not a free upgrade.
Cache behavior vs. simplicity: Go’s object-by-object mark phase is conceptually simple but, per the Go team’s own analysis, jumps unpredictably through memory in ways that hurt CPU cache performance — which is exactly the problem the experimental Green Tea redesign targets by working in whole pages instead.
Immediacy vs. completeness: CPython’s reference counting frees most objects the instant they become unreachable, which is great for predictability and for releasing OS resources (file handles, sockets) promptly — but it cannot, by itself, free a reference cycle, which is why the generational cyclic collector exists as a second, separate mechanism layered on top.
If you’re interested in other core engineering mechanisms we’ve covered in depth, see our explainers on Unicode for developers and CRDTs, both of which deal with a similar theme: a runtime or protocol doing complex bookkeeping so application code doesn’t have to.
The Bottom Line
There’s no single “best” garbage collector, only a best fit for a workload’s latency and throughput requirements. The JVM gives you an explicit choice (G1 for balanced throughput and response time, ZGC when sub-millisecond pauses matter more than raw speed). Go gives you one well-tuned, concurrent mark-sweep collector with no manual collector selection, and active engineering work (Green Tea) aimed at reducing its CPU overhead without changing its external behavior. Python gives you fast, deterministic reference counting for the common case, with a separate, tunable cyclic collector that exists solely to catch the one class of object that counting can’t: reference cycles. Understanding which mechanism your runtime uses — and what it’s bad at — is usually more useful for diagnosing a memory problem than reaching for a tuning flag first.
FAQ
Which Java garbage collector is the default? G1 is the default on most hardware and OS configurations in modern HotSpot JVMs; Serial is the default only on certain limited configurations.
Does Go have generational garbage collection like Java? No. Go’s collector is a concurrent, parallelized mark-sweep collector, but per the Go team’s own description it is not generational the way G1 or ZGC are.
Can I turn off Python’s garbage collector? You can disable the cyclic collector with gc.disable() or by setting threshold0 to 0. Reference counting itself cannot be disabled — it’s built into how CPython manages every object.
Why does a reference cycle leak memory in Python if nothing can reach it? Because reference counting only looks at each object’s own count of incoming references. Two objects referencing each other keep each other’s count above zero even when nothing outside the cycle can reach either one — which is exactly the gap the generational cyclic collector is designed to close.
Is ZGC always better than G1 because its pauses are shorter? No. Oracle’s own documentation frames this as a trade-off, not a strict upgrade: ZGC’s sub-millisecond pauses come at some cost to overall throughput compared to G1, so the right choice depends on whether your application cares more about response time or total work done per second.
Google Calendar and Outlook Calendar are the two calendar apps almost every office worker ends up using, because each one ships bundled into a much bigger subscription: Google Calendar comes with Google Workspace, and Outlook Calendar comes with Microsoft 365. You rarely buy “just the calendar” — you buy the suite, and the calendar is one piece of it. That makes the real decision less about calendar features in isolation and more about which ecosystem your team already lives in, and what each tier of that ecosystem actually includes for scheduling. We pulled current plan structures and prices directly from Google’s and Microsoft’s own pricing and help pages to lay out exactly what you get.
At a Glance
Product
Starting price
Free option
Best for
Google Calendar (via Google Workspace)
Business Starter: $7/user/month (annual), $8.40 month-to-month
Yes — full-featured free personal Google Calendar with a Google account
Teams already on Gmail/Google Docs; businesses that want simple, fast scheduling and a built-in appointment booking page at every tier
Outlook Calendar (via Microsoft 365)
Business Basic: $7/user/month (annual commitment)
Yes — basic Outlook.com calendar with a free Microsoft account
Organizations standardized on Windows, Exchange, and Teams; teams that want a dedicated appointment-booking app (Microsoft Bookings) and deep Outlook desktop integration
Both calendars are free at the personal level and become paid add-ons the moment you need business email, shared company calendars, and admin controls. From there, the two products diverge in how scheduling, booking pages, and AI features are tiered.
Google Calendar: What You Actually Get
Google Calendar’s core features — shared calendars, color-coded events, Google Meet video links, and the ability to browse and reserve conference rooms — are available on every paid Google Workspace plan, starting with Business Starter. According to Google’s own pricing page, Business Starter includes 30 GB of pooled storage per user and Google Meet calls for up to 100 participants; Business Standard jumps to 2 TB and 150 participants; Business Plus goes to 5 TB and 500 participants.
The scheduling feature most small businesses actually want — a public booking page where clients pick an open slot — is called Appointment Schedules. Google’s support documentation confirms that the older “Appointment Slots” feature was retired: existing slots stopped accepting new bookings as of August 7, 2024, and the replacement, Appointment Schedules, is “a feature-rich appointment booking system” with automatic conflict checks against your calendar, one-time or recurring availability, and the option to add co-hosts. Per Google’s own breakdown, a personal Google account and every paid Workspace tier starting at Business Starter get at least one booking page; “eligible” Workspace and Google One subscriptions unlock premium extras like automatic email reminders, customizable availability windows, and paid appointments. Older or discontinued Workspace plans (Essentials, Frontline) cannot create appointment schedules at all.
Outlook Calendar: What You Actually Get
Outlook’s calendar is built around two tools: the built-in Scheduling Assistant, and the separate Microsoft Bookings app. Scheduling Assistant shows attendees’ free/busy status directly inside a meeting invite in both the desktop and web versions of Outlook, letting an organizer drag the meeting time until everyone’s calendar is clear — it ships with every Outlook license and needs no setup.
Microsoft Bookings is the closer equivalent to Google’s Appointment Schedules: a public, web-based booking page integrated with Outlook that lets customers pick a time with a specific staff member, with automated confirmation and reminder emails. Per Microsoft’s own documentation, Bookings is included with Microsoft 365 Business Basic, Business Standard, and Business Premium (as well as several Office 365/Microsoft 365 enterprise and frontline SKUs), and it’s also available as an app inside Outlook and Microsoft Teams, not just as a standalone web page. It is not available as a standalone purchase outside those subscriptions.
Where the plans differ is the version of Outlook you get. According to Microsoft’s product comparison page, Business Basic includes only the web and mobile versions of Outlook (no desktop app), while Business Standard and Business Premium include the full desktop, web, and mobile apps. If your team wants the installed Outlook desktop client without the rest of the Microsoft 365 suite, Microsoft also sells “Microsoft 365 Apps for business” at $10/user/month, which includes desktop and web Outlook but excludes Teams chat and calling.
Same calendar feature set as Standard, with more storage and larger Meet calls (500)
Microsoft 365 Business Basic
$7 (annual commitment)
Outlook web/mobile only; Scheduling Assistant and Microsoft Bookings included
Microsoft 365 Business Standard (with Copilot)
$23.50 (annual commitment)
Full desktop, web, and mobile Outlook; Bookings included
Microsoft 365 Business Premium (with Copilot)
$32.00 (annual commitment)
Everything in Standard plus advanced threat protection against phishing and malware
Microsoft 365 Apps for business
$10 (annual commitment)
Desktop + web Outlook calendar, no Teams chat/calling, no Bookings
Two caveats worth flagging. First, Google’s pricing page was showing a limited-time introductory discount at the time of writing (roughly half the standard rate for new customers through February 2027), reverting to the $7/$14/$22 figures above afterward — always check the live page before buying. Second, Microsoft’s Business Standard and Business Premium prices reflect Copilot now being bundled into those SKUs rather than sold separately, which is why they read higher than older published figures you may still see floating around the web.
Pros and Cons
Google Calendar pros: booking pages available starting at the cheapest paid tier; fast, browser-first interface; tight Gmail/Meet integration; cheaper entry price for the full suite.
Google Calendar cons: premium booking-page features (reminders, paid bookings) are gated to higher or “eligible” tiers in a way Google doesn’t spell out cleanly; no offline desktop app, browser/mobile only.
Outlook Calendar pros: Scheduling Assistant is included at every tier with no setup; Microsoft Bookings is a more full-featured, standalone booking product (staff management, group classes, SMS reminders); strong desktop app on Business Standard/Premium.
Outlook Calendar cons: entry-level Business Basic has no desktop Outlook app; the jump from Basic to a plan with the full desktop client and Copilot is a large price increase; Bookings appointments can currently only be edited from the Bookings web portal, not directly in the Outlook calendar.
Who Should Pick Which
Pick Google Calendar / Google Workspace if: you’re a small team or solo operator who wants a client-facing booking page from day one without upgrading tiers, your team already uses Gmail and Google Meet, or you want the lowest possible entry price for a full productivity suite.
Pick Outlook Calendar / Microsoft 365 if: your organization runs on Windows and Exchange, you need the installed desktop Outlook client for offline access and advanced mail rules, or your booking needs are more complex than a single calendar (multiple staff, service types, group classes) and justify a dedicated Bookings setup.
The Bottom Line
Neither calendar is objectively “better” — they’re near-feature-parity for the basics (shared calendars, video-call links, room booking, a public scheduling page) and the real differentiator is everything else bundled into the suite around them: Gmail and Docs on one side, Outlook desktop and Teams on the other. If you’re choosing from scratch with no existing ecosystem, Google Workspace gets you a usable booking page one tier cheaper than Microsoft 365 does; if you need the full desktop Outlook experience plus more advanced appointment/staff management through Bookings, budget for Microsoft 365 Business Standard or Premium.
FAQ
Can I use Google Calendar and Outlook Calendar together? Yes. Both support calendar subscriptions (iCal/ICS feeds) and CalDAV, so you can view one calendar inside the other read-only, though two-way sync between the two natively is limited and usually requires a third-party connector.
Do I need a paid plan to get a booking page? For Google, yes — Appointment Schedules requires at least a personal Google account or Business Starter and up; the older free-for-everyone Appointment Slots feature was retired in 2024. For Microsoft, Bookings requires Microsoft 365 Business Basic or higher; it isn’t available on a free Outlook.com account.
Why did Microsoft 365 Business Standard and Premium get more expensive? Microsoft now bundles its Copilot AI assistant into those SKUs by default rather than selling it as a separate add-on, which is reflected in the current list prices shown on Microsoft’s own pricing page.
Is there a free way to get a shared company calendar without buying either suite? Partially. Free personal Google and Microsoft accounts both support shared calendars between individuals, but neither offers the admin console, custom domain email, or booking-page features that come with a paid Workspace or Microsoft 365 plan.
Choosing a video meeting platform in 2026 usually comes down to three names: Google Meet, Microsoft Teams, and Zoom. All three now offer generous meeting-length limits and some form of built-in AI meeting assistant, so the real differences are in free-plan limits, participant caps, and how the AI features are bundled into pricing. We pulled every figure below directly from each vendor’s current pricing pages.
At a Glance
Platform
Starting paid price
Free plan
Best for
Google Meet (via Google Workspace)
Business Starter: $7/user/month
No dedicated free Workspace tier for Meet; Meet is bundled only into paid Workspace plans on this pricing page
Teams already living in Gmail, Docs, and Drive
Microsoft Teams
Teams Essentials: $4/user/month
A free consumer/small-business tier exists, but exact current limits aren’t detailed on Microsoft’s plan-comparison page we reviewed — confirm on Microsoft’s site
Organizations already standardized on Microsoft 365
Yes — Basic: 40 minutes per group meeting, 100 participants, local recording only
Teams that want the simplest, most dedicated meeting tool and a true free tier
Already decided on Zoom specifically? Our in-depth Zoom Review covers its full plan lineup and free-plan limits in more detail than we can in a three-way comparison.
Google Meet
Google doesn’t sell Meet as a standalone paid product on its main pricing page — it’s a feature bundled into Google Workspace, alongside Gmail, Docs, Sheets, and Drive. That means the entry price of $7/user/month for Business Starter buys you an entire productivity suite, not just video calling, which is worth factoring in if you’re comparing cost-per-meeting-tool against Zoom or Teams. Meet’s participant caps scale with the plan: 100 on Business Starter, 150 on Business Standard, 500 on Business Plus, and 1,000 on Enterprise. Meetings can run up to 24 hours on every plan, which is more generous than either competitor’s lower tiers.
AI features (Gemini in Meet, which can summarize, translate, and take notes) are only available from Business Standard upward, not on Business Starter. Studio Sound noise cancellation, Adaptive Audio, and saving recordings to Drive are also gated to Standard and above. Google is currently running an introductory discount for new customers — roughly half off list price for the first 20 users for 12 months, from November 10, 2026 through February 10, 2027 — but that offer is time-limited and new-customer-only, so don’t plan around it long-term.
Microsoft Teams
Microsoft’s pricing is the most layered of the three. Teams Essentials, at $4/user/month, is the cheapest paid entry point and gets you meetings up to 30 hours long with up to 300 participants, but only 10 GB of cloud storage per user and English-only live captions. Step up to Microsoft 365 Business Basic ($7/user/month with Teams included) and you get the same meeting limits plus 1 TB of storage per user and live captions in 30+ languages. The higher Business Standard tier currently bundles Microsoft 365 Copilot by default on Microsoft’s comparison page, at $23.50/user/month — a notably bigger jump than the Basic-to-Essentials gap, since you’re paying for Copilot across Word, Excel, PowerPoint, and Outlook, not just better meetings.
Microsoft also offers a free version of Teams for individuals and very small businesses, but the specific current meeting-length and participant limits for that free tier weren’t detailed on the plan-comparison page we reviewed, so we’re not going to guess at exact numbers here — check Microsoft’s site directly if the free tier is what you’re evaluating. For any paid plan, meeting duration (30 hours) and participant caps (300) are consistent across Essentials, Basic, and Standard.
Zoom
Zoom is the only one of the three with a clearly free, no-credit-card, dedicated video meeting plan: Basic allows unlimited one-on-one calls and group meetings of up to 100 participants, capped at 40 minutes per group meeting, with local-only recording. Pro ($14.16/user/month billed annually, or $16.99 billed monthly) removes the 40-minute cap, extends meetings to 30 hours, and adds 10 GB of cloud recording storage, still at 100 participants. Business ($18.33/user/month annually, or $21.99 monthly) raises the participant cap to 300 and adds cloud storage per license. Enterprise is sold on request; Zoom’s own pricing page is slightly inconsistent about the exact participant ceiling at that tier (one part of the page shows 1,000, another shows “500+”), so treat Enterprise capacity as something to confirm directly with Zoom sales rather than a fixed number.
Zoom’s AI Companion is also tiered: the free Basic plan gets a small monthly allowance (around 3 meeting summaries, 20 AI queries, 3 note-taking sessions, and 3 in-meeting questions), while Pro, Business, and Enterprise get unlimited summaries, note-taking, and in-meeting questions, with some AI search features still capped (around 10 agentic searches per month).
Pricing Comparison
Platform
Entry paid plan
Mid plan
Participant cap (entry → mid)
Meeting length (entry → mid)
Google Meet
Business Starter — $7/user/mo
Business Standard — $14/user/mo
100 → 150
24 hrs → 24 hrs
Microsoft Teams
Teams Essentials — $4/user/mo
Business Basic — $7/user/mo
300 → 300
30 hrs → 30 hrs
Zoom
Pro — $16.99/user/mo ($14.16 annual)
Business — $21.99/user/mo ($18.33 annual)
100 → 300
30 hrs → 30 hrs (vs. 40 min capped on free Basic)
Pros and Cons
Google Meet
Pros: 24-hour meeting length on every plan, tightest integration with Gmail/Calendar/Drive, dial-in numbers included even on the cheapest plan.
Cons: No standalone free tier for Meet on the main pricing page — you have to buy a Workspace plan; AI features locked out of the cheapest Business Starter tier.
Microsoft Teams
Pros: Highest participant cap at the entry paid tier (300), cheapest paid entry point at $4/user/month, deep Microsoft 365 integration for Office-centric companies.
Cons: Pricing structure is the most confusing of the three, with Copilot bundling pushing the next tier up sharply; free-tier limits aren’t clearly documented on the official comparison page.
Zoom
Pros: The only genuinely free, dedicated meeting plan among the three; simplest, most purpose-built interface for scheduling and running meetings; clear AI Companion usage tiers.
Cons: Free plan’s 40-minute group meeting cap is the tightest limit of any free offering here; Enterprise participant capacity is ambiguous on Zoom’s own pricing page.
Who Should Pick Which
If your team already lives inside Google Workspace or Microsoft 365, the video platform decision is largely already made for you — Meet or Teams will be free-ish in the sense that it’s included in a suite you’re probably already paying for, and switching to a dedicated tool just adds another login and another bill. Pick Google Meet specifically if long meetings (up to 24 hours) and tight Gmail/Calendar integration matter most. Pick Microsoft Teams if your organization is Office-centric and you want the highest participant ceiling without paying for a premium tier.
Pick Zoom if you want a tool built around meetings first, nothing else, and you want to actually test it for free before paying — just budget for Pro quickly if your meetings regularly run past 40 minutes with three or more people, since that’s the one hard wall on Zoom’s free plan.
Bottom Line
There’s no single winner here — the right platform mostly follows whichever productivity suite your company already uses. Zoom wins on having the clearest, most testable free tier and the simplest pricing logic. Microsoft Teams wins on participant capacity per dollar at the entry tier, if you can tolerate its more layered pricing. Google Meet wins on meeting length and suite integration, at the cost of having no truly standalone free plan. For a small team evaluating all three from scratch, start with whichever suite (Google Workspace or Microsoft 365) you’re closest to already adopting, and only default to Zoom if you’re not committed to either suite yet.
FAQ
Which of the three has a free plan?
Zoom has the clearest standalone free plan (Basic): unlimited one-on-one calls and group meetings up to 100 participants, capped at 40 minutes per group meeting. Google doesn’t sell a standalone free Meet tier on its main Workspace pricing page, and Microsoft’s free Teams tier exists but its exact current limits aren’t detailed on the plan-comparison page we checked.
Which platform allows the longest meetings on its cheapest paid plan?
Google Meet (via Business Starter) and Microsoft Teams (via Teams Essentials or Business Basic) both allow long meetings — Meet up to 24 hours, Teams up to 30 hours — on their respective entry tiers. Zoom’s Basic free plan is capped at 40 minutes for group calls, but Zoom Pro also extends to 30 hours.
Does any of these include AI meeting notes for free?
Zoom’s free Basic plan includes a small monthly allowance of AI Companion features (roughly 3 meeting summaries and a limited number of AI queries per month). Google Meet’s AI features (Gemini in Meet) require at least Business Standard, not the entry Business Starter tier. Microsoft’s free Teams AI access via Copilot is generally an add-on rather than included.
Which has the highest participant cap?
At entry-level paid tiers, Microsoft Teams (300 participants on Essentials and Business Basic) is ahead of Google Meet (100 on Business Starter) and Zoom Pro (100). At higher tiers, Google Meet Enterprise lists 1,000 participants; Zoom’s Enterprise tier shows conflicting figures (1,000 in one place, “500+” in another) on its own pricing page, so that number should be confirmed directly with Zoom.
“AI coding agent” has become one of the most overused phrases in developer tooling, applied to everything from inline autocomplete to systems that write, test, and ship code with almost no human in the loop. Those are genuinely different things. This explainer draws only on vendors’ own documentation and announcements to describe what today’s most-discussed coding agents actually claim to do, where those claims are vendor-reported versus independently verified, and how agents differ structurally from the assistants most developers already use.
At a Glance
Category
Autonomy Level
Typical Use
Examples
Autocomplete
None — predicts the next tokens as you type
Inline suggestions inside an editor
Classic Copilot-style inline completion
Coding Assistant (chat)
Per-request — acts only when asked, one exchange at a time
Answer questions, explain code, generate a snippet to review
Copilot Chat, ChatGPT used interactively for code
Autonomous Coding Agent
Multi-step — plans a task, uses tools in a loop, works with limited supervision
Research a repo, write and test code across files, open a pull request
Devin, GitHub Copilot coding agent, Claude Code / Claude Agent SDK applications, OpenAI Codex cloud agent
What Makes an “Agent” Different From an Assistant
The field hasn’t settled on one precise definition, and vendors use the word loosely, but the pattern that recurs across official descriptions is a loop: the system gathers context on its own, decides what action to take, uses a tool (a shell, an editor, a browser, a test runner) to take that action, observes the result, and repeats until it decides the task is done — rather than producing one reply and stopping. Anthropic’s own framing for its Agent SDK captures this directly: “An agent is an application that completes a task by planning its own steps and calling tools that read files, run commands, or edit code.” A plain autocomplete model has no loop at all; it predicts tokens. A chat-based assistant has a loop of exactly one turn, bounded by what you ask in that message. An agent’s loop can run for minutes, and in some vendors’ products, run many steps unattended inside a sandboxed environment before a human looks at the result. That last part — acting inside a real environment with real tools, across multiple steps, with the human reviewing an outcome rather than approving each line — is the structural thing that separates an “agent” from an “assistant” in vendor usage, even though the industry still argues about where exactly the line falls.
Devin (Cognition)
Cognition introduced Devin in March 2024 as, in the company’s own words, “the world’s first fully autonomous AI software engineer.” Per Cognition’s announcement, Devin plans and executes complex engineering tasks inside a sandboxed environment that includes a shell, a code editor, and a browser; the company says it can learn an unfamiliar tool from documentation, recall context across steps, and fix its own mistakes, while reporting progress and taking feedback from a human along the way. Cognition’s demonstrated examples included building and deploying a small web app, fixing a bug in an open-source codebase, and resolving real GitHub issues.
On the benchmark claim: Cognition’s launch post reported that Devin resolved 13.86% of a 25%-random-subset of SWE-bench issues end-to-end and unassisted, against a previous best of 1.96% unassisted (4.80% for models given the exact files to edit). This is important to flag clearly: this is Cognition’s own self-reported number from its own 2024 announcement, measured on a subset it selected, and we did not find an independently reproduced, third-party verification of that specific figure. Treat it as a vendor claim, not an audited benchmark result, and note that SWE-bench methodology and leaderboard figures across the industry have been debated since. Cognition said a fuller technical report would follow; our research for this article did not surface that report.
GitHub Copilot Coding Agent
GitHub’s own documentation describes Copilot’s cloud-based agentic capability this way: “Copilot can research a repository, plan changes, and implement them in the background.” It edits files and runs tests and linters inside a cloud sandbox or an Actions-based runner, then opens a pull request once you’ve reviewed its proposed changes or once your prompt explicitly asks for one. A related feature, Agent Merge, watches an open pull request and can automatically address failing Actions workflows or merge conflicts. GitHub is explicit about the limits: an Actions-based session can only touch the single repository it was assigned to and is capped at 59 minutes; the agent works on one branch and opens one pull request per task; it requires write access to operate, and session logs are meant to support your review, not replace it. GitHub also states plainly that the agent “can produce incorrect or insecure code,” so output must be reviewed and tested before use. As of October 28, 2026, GitHub’s cloud agent experience requires a paid Copilot plan, subject to organization policy; our site’s own GitHub Copilot Review covers plan pricing and tiers in detail.
Claude Code and the Claude Agent SDK (Anthropic)
Anthropic’s documentation positions Claude Code as a terminal-based coding agent, and the Claude Agent SDK as a library that lets developers “build production AI agents with Claude Code as a library,” exposing the same agent loop, built-in tools (read, write, edit files, run commands, search the web), permissions system, and session management that power Claude Code itself, programmable in Python or TypeScript. Anthropic’s docs list specific supported capabilities rather than marketing superlatives: hooks that run custom code at points in the agent’s lifecycle, subagents that can be spawned for focused subtasks, Model Context Protocol (MCP) connections to external tools and data, and configurable permissions that control which tool calls run automatically versus which require approval. This is a notably narrower, more mechanism-focused description than some competitors’ launch posts — Anthropic’s framing centers on the loop-plus-tools architecture rather than end-to-end autonomy claims.
OpenAI Codex
OpenAI’s current documentation describes Codex as “OpenAI’s coding agent for software development,” included in ChatGPT Plus, Pro, Business, Edu, and Enterprise plans, capable of writing code from a description, explaining unfamiliar codebases, reviewing code for bugs and edge cases, debugging failures, and automating workflows like refactors, test generation, and migrations. OpenAI’s original introduction of the cloud agent (May 2025) described it in more autonomous terms: a “cloud-based software engineering agent that can work on many tasks in parallel,” where each task runs in an isolated sandbox preloaded with the user’s repository, with internet access disabled by default during execution (a June 2025 update allowed enabling it). The agent reads and edits files, runs test harnesses, linters, and type checkers, iterates on failing tests, and on completion commits its changes so a human can review them, request revisions, or open a GitHub pull request. OpenAI states plainly that users must manually review and validate all agent-generated code before integrating or running it, and that users cannot course-correct the agent mid-task — only after it finishes a run.
Comparing the Four
Agent
Vendor
Runs In
Opens PRs
Human Review Point
Devin
Cognition
Sandboxed environment (shell, editor, browser)
Yes, per Cognition’s description
During task, via real-time progress and feedback
Copilot coding agent
GitHub (Microsoft)
Cloud sandbox or GitHub Actions runner
Yes, after review or on request
Before and after PR creation; logs for review
Claude Code / Agent SDK
Anthropic
Local terminal, CI, or custom app via SDK
Depends on how the integrator builds it
Configurable via permissions system
Codex cloud agent
OpenAI
Isolated cloud sandbox preloaded with the repo
Yes, after task completion
After the agent commits; manual review required before use
Vendor Productivity Claims vs. Independent Evidence
Every vendor above has, at some point, made a productivity or capability claim in its own marketing — faster resolution of issues, higher benchmark scores, fewer human hours per task. Treat any specific percentage or benchmark score from a vendor’s own blog post or press release as a vendor claim unless it has been independently reproduced by a third party using a published, auditable methodology. Benchmark suites like SWE-bench have known methodology sensitivities (which subset is used, whether a model is given the exact files to change, whether runs are cherry-picked), and different vendors have reported results on different subsets and conditions, which makes cross-vendor comparison unreliable without reading each methodology section carefully. We have not independently verified any vendor’s specific productivity multiplier in this piece, and none is repeated here as established fact.
The Real Risks
Letting a tool plan, edit, and commit code across a real codebase with limited supervision raises security and review questions that go well beyond what this explainer can cover responsibly. Every vendor above explicitly tells users to review and test agent output before relying on it, which is itself a signal about current reliability. For a detailed look at how often AI-generated code introduces vulnerabilities, how those risks map to the OWASP Top 10 for LLM Applications, and a practical review checklist for teams adopting these tools, see our companion piece, AI-Generated Code Security in 2026.
The Bottom Line
An autonomous coding agent isn’t a smarter autocomplete — it’s a system built around a plan-act-observe loop that uses real tools inside a real (usually sandboxed) environment, with the human reviewing outcomes rather than approving every keystroke. Devin, GitHub’s Copilot coding agent, Claude Code and the Claude Agent SDK, and OpenAI’s Codex cloud agent all fit that structural pattern, according to their own vendors’ documentation, even though they differ in where they run, how much a human can intervene mid-task, and how much marketing language surrounds their launch. The specific productivity numbers are the part to be skeptical of; the architectural shift toward tool-using, multi-step agents is the part that’s well documented and, at this point, not really in dispute.
FAQ
Is GitHub Copilot’s autocomplete the same thing as its coding agent? No. Copilot’s inline autocomplete predicts code as you type with no planning loop; Copilot’s coding agent is a separate, cloud-based feature that researches a repo, plans changes, implements them, and can open a pull request.
Can these agents be trusted to merge code without a human? Every vendor covered here explicitly states that output should be reviewed and tested before use, and most products require an explicit human action (merging a PR, approving a session) before code reaches production.
Is the Devin SWE-bench number (13.86%) still accurate today? That figure comes from Cognition’s original March 2024 announcement on a specific 25% subset of SWE-bench, measured under specific conditions. We did not find an independently audited, current reproduction of it, so it should be read as a historical vendor claim, not a current, verified benchmark.
What’s the difference between Claude Code and the Claude Agent SDK? Claude Code is the terminal application for interactive, daily use. The Claude Agent SDK is a library that lets developers embed the same underlying agent loop and tools inside their own Python or TypeScript applications.
Do these agents need internet access to work? It varies. OpenAI’s Codex cloud agent disables internet access by default during a task (with an option to enable it), largely for security reasons; other agents’ network access depends on how the sandbox or environment is configured by the vendor or integrator.
Every turn-by-turn GPS route, every enemy that paths around a wall in a video game, and every packet that finds its way across a network relies on a graph-search algorithm doing the same basic job: finding the cheapest route between two points. Two algorithms dominate that job, and they are closely related rather than competitors from different eras. Dijkstra’s algorithm, published in 1959, guarantees the shortest path in any graph with non-negative edge weights. A*, published in 1968, is Dijkstra’s algorithm plus a heuristic that steers the search toward the goal — often visiting far fewer nodes along the way.
This guide explains how each algorithm actually works, what their complexity guarantees are, when A*’s heuristic helps and when Dijkstra is the only correct choice, and where each shows up in production systems.
At a Glance
Algorithm
Time Complexity
When to Use
Dijkstra’s Algorithm (1959)
O(V²) with a simple array; O((V + E) log V) with a binary heap; Θ(E + V log V) with a Fibonacci heap
Non-negative weighted graphs, no usable sense of “direction” to the goal, or when you need shortest paths to every node from one source
A* Search (1968)
Same worst case as Dijkstra, but typically far fewer nodes expanded in practice; often described loosely as O(b^d) for branching factor b and solution depth d
Single-source, single-target searches where a cheap, reasonably accurate distance estimate (heuristic) to the goal exists, e.g. grid maps, road networks, puzzles
Dijkstra’s Algorithm: Shortest Paths Without Guessing
Edsger W. Dijkstra described the algorithm in his short 1959 paper “A Note on Two Problems in Connexion with Graphs,” published in Numerische Mathematik (he said later that he designed it in 1956, without a computer, as a demonstration of what a new machine could do). The algorithm solves the single-source shortest path problem: given a starting node, find the cheapest path from it to every other reachable node.
The mechanism is a greedy expansion from the start node. Every node is given a tentative distance — zero for the start, infinity for everything else. At each step, the algorithm picks the unvisited node with the smallest tentative distance, marks it “settled” (its distance is now final), and relaxes its outgoing edges: for each neighbor, it checks whether going through the current node produces a shorter distance than what’s currently recorded, and updates it if so. The algorithm repeats until every reachable node is settled, or until the target is settled if you only need one destination.
The guarantee comes from a simple invariant: because edge weights are never negative, the next unvisited node with the smallest tentative distance can never later be beaten by a path through a node that hasn’t been settled yet. That invariant breaks the moment negative edge weights are allowed — which is why Dijkstra’s algorithm is undefined on graphs with negative edges (use Bellman-Ford or Johnson’s algorithm instead).
Implementation determines the running time. A naive array scan to find the minimum each time gives O(V²), where V is the number of vertices — fine for dense graphs. Replacing that linear scan with a binary heap (priority queue) brings it to O((V + E) log V), where E is the number of edges. A Fibonacci heap improves it further to Θ(E + V log V), which matters at very large scale but adds implementation complexity most teams don’t bother with.
A*: Dijkstra With a Sense of Direction
A* was introduced in 1968 by Peter Hart, Nils Nilsson, and Bertram Raphael of the Stanford Research Institute, in the paper “A Formal Basis for the Heuristic Determination of Minimum Cost Paths” (IEEE Transactions on Systems Science and Cybernetics). Their goal was to prove, formally, when it’s safe to let a search use a “guess” about remaining distance to speed things up without sacrificing optimality.
A* expands nodes in order of f(n) = g(n) + h(n), where g(n) is the known cost from the start to node n, and h(n) is a heuristic estimate of the remaining cost from n to the goal. Dijkstra’s algorithm is the special case where h(n) = 0 for every node — it has no sense of which direction the goal is in, so it explores uniformly outward. A* uses h(n) to prioritize nodes that look like they’re heading toward the goal, which in practice means it expands a much smaller fraction of the graph before finding the answer.
The catch is that this speedup is only safe under specific conditions on the heuristic:
Admissible: h(n) must never overestimate the true remaining cost from n to the goal, for every node n. An admissible heuristic guarantees A* finds the optimal (cheapest) path, because it never prematurely discards a path that could turn out to be the best one.
Consistent (monotone): a stronger condition where, for every edge (x, y), h(x) ≤ cost(x, y) + h(y). A consistent heuristic is also admissible, and it guarantees that once A* settles a node, it never needs to revisit it — which is what makes A*’s practical running time so much better than Dijkstra’s in the cases it’s suited for.
On a 2D grid, straight-line (Euclidean) distance to the goal is always admissible, because no real path can be shorter than a straight line. Manhattan distance is admissible when movement is restricted to four directions. A heuristic that overestimates — for example, one that is miscalibrated to favor speed over correctness — can make A* run faster but can also return a suboptimal path, so it stops being “A*” in the formal sense and becomes a weighted or greedy variant.
Worked Example: Why the Heuristic Matters
Picture a road network as a grid, with a start point in the southwest corner and a destination in the northeast corner. Dijkstra’s algorithm expands outward from the start in all directions equally, like a flood fill — it has already explored the southeast and northwest regions before it even reaches the destination, because it has no information telling it those directions are wrong. A*, using straight-line distance to the destination as its heuristic, consistently favors nodes that reduce the remaining distance, so its search area looks more like a narrow cone pointed at the goal rather than a circle.
Both algorithms, given an admissible heuristic in A*’s case, return the same optimal path length. The difference is entirely in how many nodes had to be examined to get there — which is the whole reason A* exists.
A minimal pseudocode sketch of A*’s main loop:
open_set = {start}
g[start] = 0
f[start] = h(start, goal)
while open_set is not empty:
current = node in open_set with lowest f value
if current == goal:
return reconstruct_path(current)
remove current from open_set
for each neighbor of current:
tentative_g = g[current] + cost(current, neighbor)
if tentative_g < g[neighbor]:
g[neighbor] = tentative_g
f[neighbor] = tentative_g + h(neighbor, goal)
if neighbor not in open_set:
add neighbor to open_set
return failure // no path exists
Set h(n) = 0 everywhere in this same loop and it is, exactly, Dijkstra’s algorithm.
Dijkstra vs A*: Side-by-Side
Dimension
Dijkstra’s Algorithm
A* Search
Worst-case complexity
O(V²) naive; O((V+E) log V) with a binary heap
Same worst case as Dijkstra (it degrades to Dijkstra if h=0); typically much faster in practice with a good heuristic
Optimality guarantee
Always optimal, for non-negative edge weights
Optimal only if the heuristic is admissible
Heuristic required
None — it has no notion of a specific goal direction
Yes — requires an admissible (ideally consistent) heuristic function
Best suited for
Finding shortest paths to all nodes, or when no good distance estimate to a single goal exists
Single-target pathfinding where a cheap geometric or domain estimate to the goal is available
Typical use cases
Network routing protocols, all-pairs precomputation, graphs without spatial structure
GPS navigation, game AI pathfinding, robotics motion planning, puzzle solving
Real-World Use Cases
Navigation and routing. Modern mapping engines rarely run textbook A* directly on raw road graphs — they use heavily optimized variants (such as contraction hierarchies) layered on the same core idea — but the underlying principle is A*’s: use geographic distance to the destination as a heuristic so the search doesn’t waste time exploring roads headed the wrong way.
Game AI. A* is the default pathfinding choice in game development because levels are usually grids or navigation meshes with an obvious, cheap heuristic (straight-line or Manhattan distance to a known target), and frame-time budgets reward an algorithm that minimizes nodes expanded.
Network routing. Classic link-state routing protocols compute shortest paths from a router to every other router in the network — a one-to-all problem with no single fixed “goal” and no obvious geometric heuristic, which is exactly Dijkstra’s use case rather than A*’s.
Robotics motion planning. A* and its many descendants (D*, D* Lite, Jump Point Search) are used to plan collision-free paths through known or partially known maps, again relying on distance-to-goal heuristics to keep search times low enough for real-time control.
Which Should You Use?
Use Dijkstra’s algorithm when you need shortest paths from one source to all other nodes, when there’s no meaningful heuristic (the graph isn’t spatial, or you have no cheap way to estimate remaining distance), or when correctness with zero tuning risk matters more than raw speed.
Use A* when you have a single, specific target and a heuristic you can prove is admissible — most commonly a geometric distance in a spatial map. The heuristic is the entire value proposition of A*; without a good one, it collapses to Dijkstra’s algorithm with extra bookkeeping overhead, so it’s rarely a good choice for non-spatial or oddly structured graphs where a trustworthy estimate is hard to construct.
If you’re working with other distributed or graph-shaped data problems, our explainers on CRDTs and Unicode internals for developers cover two other areas where getting the underlying model exactly right avoids subtle, hard-to-debug failures later.
Bottom Line
Dijkstra’s algorithm and A* are not rival algorithms so much as the same algorithm with and without a compass. Dijkstra, unmodified, is the safe default for one-to-all shortest paths and non-spatial graphs. A* is Dijkstra plus a heuristic that, as long as it’s admissible, never sacrifices correctness and usually buys a large practical speedup — which is why it quietly runs inside most of the pathfinding you interact with daily, from games to navigation apps.
FAQ
Is A* always faster than Dijkstra?
Not necessarily. A* is faster when its heuristic is informative (closely tracks real remaining distance). With a weak or uninformative heuristic, A* can expand almost as many nodes as Dijkstra, and with h(n) = 0 it is literally identical to Dijkstra.
What happens if A*’s heuristic is not admissible?
A* can still terminate and return a path, but it is no longer guaranteed to be the shortest one, because the search can settle a node too early based on an overly optimistic-looking total that turns out to be wrong. This variant is sometimes called “weighted A*” and is used deliberately in some applications to trade optimality for speed.
Can Dijkstra’s algorithm handle negative edge weights?
No. Dijkstra’s algorithm requires non-negative edge weights; its correctness proof depends on it. Graphs with negative edges need Bellman-Ford or, for repeated queries, Johnson’s algorithm.
Is A* a type of Dijkstra’s algorithm, or a separate algorithm?
Formally, Dijkstra’s algorithm is a special case of A* where the heuristic function h(n) is zero for every node. A* generalizes Dijkstra by adding a goal-directed heuristic term.
What’s a good heuristic for a grid-based game map?
Manhattan distance for four-directional movement, diagonal (Chebyshev) distance for eight-directional movement, and Euclidean distance for free movement — all are admissible for their respective movement models, which is why they’re the standard choices in game pathfinding tutorials.
Sources
Dijkstra, E. W. (1959). “A Note on Two Problems in Connexion with Graphs.” Numerische Mathematik. Original paper (PDF)
Hart, P. E., Nilsson, N. J., & Raphael, B. (1968). “A Formal Basis for the Heuristic Determination of Minimum Cost Paths.” IEEE Transactions on Systems Science and Cybernetics. Paper (PDF)
Get Figma: Visit the official Figma pricing page to see live plan details.
At a Glance
Spec
Value
Free plan
Yes — unlimited file storage, 3 projects, 2 members, 30-day version history
Starting paid price
Professional: $12/editor/month billed annually, or $15/month billed monthly
Mid tier
Organization: $45/editor/month billed annually
Top tier
Enterprise: custom pricing, contact sales
Best for
Product, design, and engineering teams doing collaborative UI/UX design and prototyping
Platforms
Browser-based, plus desktop apps for Windows and macOS
Bundled tools
FigJam (whiteboarding) and Dev Mode (design-to-code handoff) are part of the same product family
Billing flexibility
Monthly or annual per-editor billing; viewers are free on all plans
Short Verdict
Figma remains the default choice for interface design and prototyping in 2026, mainly because it turned design into a real-time, multiplayer activity years before most competitors caught up. The free plan is genuinely usable for a solo designer or a two-person side project, but it caps out fast: once a team needs more than two members or more than three active projects, the jump to Professional at $12–15 per editor per month is close to mandatory. For most small teams, that’s still cheap relative to the hours it saves in handoff and feedback cycles — the real question isn’t whether Figma is good, it’s whether your team is small enough and simple enough for the free tier to last.
What It Is
Figma is a browser-based interface design and prototyping tool that lets multiple people edit the same file simultaneously, similar to how Google Docs works for text. It’s used heavily by product designers to create UI mockups, by teams to build and maintain shared component libraries (“design systems”), and by engineers to inspect finished designs for exact spacing, colors, and assets through its Dev Mode handoff tooling. Figma also owns FigJam, a separate but tightly integrated whiteboard product for brainstorming, flowcharts, and workshops, and Figma Slides for presentations — so a Figma subscription in practice often covers more than just screen design.
Because it runs in the browser (with optional desktop apps for Windows and macOS), there’s no installation friction for new collaborators — a stakeholder can be invited to view or comment on a file in seconds. That accessibility, combined with a plugin ecosystem and native support for interactive, clickable prototypes, is a big part of why Figma displaced desktop-only tools like Sketch for most team workflows over the past several years.
Pricing Breakdown
Plan
Price
Who it’s for
What you get
Free
$0
Individuals, students, very small or two-person teams
Unlimited file storage, 3 projects, 2 members, 30 days of version history, unlimited free viewers
Professional
$12/editor/month billed annually, or $15/month billed monthly
Freelancers and small-to-mid teams
Everything in Free plus unlimited projects and files, unlimited version history, a shared team library, and private projects
Organization
$45/editor/month billed annually (no public monthly rate)
Growing companies that need governance
Everything in Professional plus unlimited teams, draft ownership controls, organization-wide design systems, advanced access and privacy controls, enforced SSO/2FA, SAML-based SSO, and audit reports
Enterprise
Custom — contact sales
Large organizations with compliance or scale requirements
Figma does not publish Enterprise feature details on its pricing page; pricing and feature scope are negotiated directly
A couple of pricing details worth flagging for budgeting purposes: viewers are free on every plan, so you only pay for the people actually editing files, and editors added mid-cycle to an annual plan are billed at the monthly rate until the next renewal. Figma does not publish an Enterprise price list, so any specific enterprise quote should be confirmed directly with Figma’s sales team rather than assumed from third-party estimates.
Pros
Real-time multiplayer editing makes design reviews and co-design sessions far faster than file-based tools.
Viewers and commenters are free on every plan, so stakeholders outside the design team cost nothing to include.
Dev Mode gives engineers a dedicated inspection view for specs and assets without needing a separate handoff tool.
FigJam and Figma Slides extend the same account into whiteboarding and presentations, reducing tool sprawl.
Runs fully in the browser, so onboarding a new collaborator doesn’t require anyone to install software.
Cons
The free plan’s 2-member and 3-project caps are tight — most teams outgrow it almost immediately.
Governance features like enforced SSO and audit reports are locked behind the much pricier Organization tier, with no public monthly rate shown.
Enterprise pricing is entirely opaque until you talk to sales, making it hard to budget in advance.
Per-editor billing can get expensive for larger design organizations compared with flat-rate alternatives.
Heavy, complex files can still feel sluggish in the browser compared with native desktop design tools.
Who It’s a Good Fit For
Figma makes the most sense for product teams where designers, PMs, and engineers all need eyes on the same file — the free viewer access alone justifies adoption for cross-functional teams. Small design teams of three to ten people land comfortably on the Professional plan, and the unlimited projects and files there remove most of the friction the free tier creates. Agencies and freelancers who need to share polished, interactive prototypes with clients also benefit from the no-install, link-based sharing model.
Who Should Look Elsewhere
A true solo user who only occasionally needs to design something — and never needs a second collaborator or a fourth project — can likely stay on the free plan indefinitely, but anyone building a real team workflow should budget for Professional from the start rather than assuming free will hold. Enterprises with strict security and compliance checklists should treat the Organization tier’s $45/editor/month annual rate as a floor, not a ceiling, since Enterprise-level requirements will likely mean a custom (and higher) quote. Teams whose primary need is heavy, high-complexity technical diagramming rather than UI design may be better served by a dedicated diagramming tool.
Bottom Line
Figma’s free plan is a legitimate way to try the product or run a two-person project, but it is not a long-term solution for any team with normal growth plans — the 2-member, 3-project ceiling is low by design. Once you’re ready to commit, Professional at $12–15 per editor per month is reasonably priced for what it unlocks, and the jump to Organization is really about governance and security rather than core design functionality. For most small teams evaluating Figma in 2026, the practical plan is: start free to confirm fit, then move to Professional the moment a third project or third collaborator shows up.
FAQ
Is Figma free to use?
Yes. Figma’s free plan includes unlimited file storage, up to 2 members, 3 projects, and 30 days of version history, with unlimited free viewers on any plan.
What’s the real difference between Professional and Organization?
Professional removes the free plan’s project and file limits and adds a team library and private projects. Organization is aimed at larger companies and adds unlimited teams, organization-wide design systems, enforced SSO and 2FA, SAML-based SSO, and audit reports — governance features rather than new design capabilities.
Does Figma have a desktop app, or is it browser-only?
Figma runs fully in the browser and also offers desktop apps for Windows and macOS for people who prefer a native window and offline-friendly caching, though real-time collaboration still requires an internet connection.
How much does Figma Enterprise cost?
Figma does not publish Enterprise pricing on its website; it’s sold through a custom quote after talking to Figma’s sales team, so any number you see elsewhere should be treated as an estimate rather than an official figure.
Is Figma’s free plan enough for a small team in 2026?
Only for the smallest possible team — the free plan caps out at 2 members and 3 projects. Most “small teams” in the normal sense of 3+ people or more than a handful of active projects will need at least the Professional plan.
Every team that ships code eventually asks the same question: which CI/CD platform is worth paying for? In 2026 the honest answer is “it depends on where your code already lives and how you want to pay for compute,” because GitHub Actions, GitLab CI/CD, and CircleCI have converged on very similar feature sets but very different pricing models. This comparison sticks to what each vendor states on its own pricing and documentation pages as of October 2026, so you can see the real free-tier limits and overage costs before you commit.
At a Glance
Platform
Starting Price
Free Tier
Best For
GitHub Actions
Free for public repos; $0.002–$0.062 per minute beyond included minutes on private repos
Teams wanting source control, CI/CD, and security scanning in one platform
CircleCI
Free: $0/month — Performance: from $15/month
30,000 credits/month on both Free and Performance
Teams wanting a CI-focused tool with fine-grained machine types, usable with any Git host
How CI/CD Pricing Actually Works
The three platforms meter usage in three different units, which makes head-to-head comparison harder than it should be. GitHub Actions bills in minutes, with a per-minute rate that depends on the operating system and machine size of the runner. GitLab bills in compute minutes, calculated as job duration divided by 60 and multiplied by a runner-specific “cost factor” — GitLab is explicit that this cost factor is not a monetary price, just a usage multiplier. CircleCI bills in credits, an abstract unit that is consumed at different rates depending on the resource class (CPU, memory, and OS) a job uses. None of these units convert cleanly into the others, so the only reliable way to compare cost is to estimate your own typical job mix against each vendor’s calculator.
GitHub Actions in 2026
GitHub Actions remains free for workflows on public repositories, with no minute limit. For private repositories, GitHub Free includes roughly $12 of monthly compute (about 2,000 minutes on a standard 2-core Linux runner at $0.006/minute), GitHub Pro and Team include roughly $18 (about 3,000 minutes), and GitHub Enterprise Cloud includes $300 of compute (roughly 50,000 minutes). Per-minute rates on standard hosted runners range from $0.002 for a 1-core Linux “slim” runner up to $0.062 for a macOS runner; GitHub also offers much larger hosted runners (up to 96-core Linux and Windows, plus GPU runners) at correspondingly higher per-minute rates. As of January 1, 2026, GitHub cut hosted-runner prices by up to 39% depending on machine type. A separate plan to start charging $0.002/minute for self-hosted runner usage on private repositories, originally announced for March 1, 2026, has been postponed while GitHub re-evaluates the approach.
Pros:
No separate CI tool to connect — workflows live in the same repo and UI as your code and pull requests
Free, unlimited minutes for public/open-source repositories
Enormous marketplace of reusable community Actions
Cons:
Included minutes on the Free and Pro tiers are modest for active private-repo teams
macOS runners are the most expensive per minute of any platform compared here
Tied to GitHub as your source-control host
A minimal workflow file looks like this:
name: CI
on: [push]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: echo "Hello CI"
GitLab CI/CD in 2026
GitLab’s CI/CD is built into the same product as its Git hosting, issue tracking, and security scanning, which is the platform’s core pitch: one tool instead of several. On GitLab.com, the Free tier includes 400 compute minutes per month at no cost. Premium, at $29 per user per month billed annually, includes 10,000 compute minutes per month. Ultimate is custom-priced (GitLab does not publish a per-user rate) and includes 50,000 compute minutes per month. Runner cost factors on GitLab.com’s hosted runners range from 1x for a small Linux x86-64 runner up to 12x for a 2xlarge Linux runner or a beta macOS M2 Pro large runner; GPU runners carry a 7x factor. Public open-source projects get a 0.5x discount, and forks of those projects get a steep 0.008x discount, making GitLab notably cheap for qualifying open-source work.
Pros:
CI/CD, source control, and security scanning (SAST, dependency scanning) in a single integrated platform
Transparent, well-documented cost-factor formula
Strong discounts for public open-source projects
Cons:
Free tier’s 400 minutes/month is the smallest of the three platforms
Ultimate tier pricing isn’t public, which complicates budgeting at the high end
Per-seat pricing on Premium can get expensive for larger engineering orgs regardless of CI usage
CircleCI in 2026
CircleCI is a dedicated CI/CD product that connects to GitHub, GitLab, or Bitbucket rather than requiring a specific host. Its Free plan costs $0/month and includes 30,000 credits/month, 5 active users, 30x concurrency, 1GB network and 2GB storage, 1,000 Smarter Testing “atoms” (CircleCI’s test-splitting/insights unit), and 5 self-hosted runner tasks. The Performance plan starts at $15/month, also includes 30,000 credits/month but raises concurrency to 80x and adds larger resource classes; additional credits cost $15 per 25,000 (roughly $0.0006 per credit), and CircleCI also sells prepaid bulk credits (1 million for $600 or 5 million for $3,000, expiring after 12 months). The Scale plan is custom-priced, billed annually, and removes the concurrency cap entirely while adding GPU resource classes (Nvidia T4, A10G, V100, and P4) and SSO/config policies.
Pros:
Works with any major Git host, not locked to one vendor’s repos
Fine-grained resource classes (Docker, VM, Arm, macOS, GPU) and reusable config via “orbs”
Generous free-tier concurrency (30x) compared to the other two platforms’ defaults
Cons:
Credits are an abstract unit that takes effort to translate into a dollar budget
No native source control, issue tracking, or security scanning — it’s CI/CD only
Scale-tier pricing is custom and not published
Pricing Comparison
Plan
Monthly Price
Included Usage
Overage Cost
GitHub Free
$0
~2,000 min (2-core Linux equivalent)
$0.002–$0.062/min by runner type
GitHub Pro/Team
$4–$21/user
~3,000 min
$0.002–$0.062/min by runner type
GitHub Enterprise Cloud
Custom
~50,000 min ($300 compute)
$0.002–$0.062/min by runner type
GitLab Free
$0
400 compute min
Purchase additional minute packs
GitLab Premium
$29/user (annual)
10,000 compute min
Purchase additional minute packs
GitLab Ultimate
Custom
50,000 compute min
Purchase additional minute packs
CircleCI Free
$0
30,000 credits
Upgrade plan required
CircleCI Performance
From $15
30,000 credits
~$0.0006/credit ($15 per 25,000)
CircleCI Scale
Custom (annual)
Custom
Custom
Who Should Pick Which
Pick GitHub Actions if your code already lives on GitHub and you want CI/CD with zero extra integration work, especially for open-source projects where minutes are free.
Pick GitLab CI/CD if you want source control, CI/CD, and security scanning under one roof and can budget per-seat pricing, or if you qualify for GitLab’s open-source discounts.
Pick CircleCI if you want a best-of-breed CI/CD tool that works with whatever Git host you use, need high concurrency on a budget, or want granular control over machine resource classes including GPUs.
The Bottom Line
There is no universal winner here — the right platform is mostly determined by where your repositories already live and how predictable your build volume is. GitHub Actions wins on convenience for GitHub-hosted projects and is unbeatable for public repos. GitLab wins if you want an all-in-one DevSecOps platform and can absorb per-seat licensing. CircleCI wins on flexibility and concurrency if you want a dedicated CI/CD specialist rather than a bundled platform. Whichever you choose, run your actual job durations through the vendor’s own pricing calculator before committing — the free tiers are generous enough for side projects but can be exhausted quickly by an active team.
FAQ
Is GitHub Actions really free? It’s free with unlimited minutes for public repositories. Private repositories get a limited number of free minutes per month depending on your GitHub plan, then pay per minute beyond that.
What is a GitLab “compute minute” versus a regular minute? A compute minute is job duration divided by 60, multiplied by a runner-specific cost factor. A job on a more powerful runner (like a 2xlarge machine) consumes compute minutes faster than the same job on a small runner.
How much is a CircleCI credit worth in dollars? CircleCI doesn’t publish a flat per-credit price for the Free plan, but on the Performance plan, additional credits cost $15 per 25,000, which works out to about $0.0006 per credit.
Can I use CircleCI with GitHub or GitLab repos? Yes. Unlike GitHub Actions and GitLab CI/CD, which are built into their respective hosting platforms, CircleCI is host-agnostic and connects to GitHub, GitLab, or Bitbucket.
Did GitHub Actions pricing change in 2026? Yes. Hosted-runner per-minute rates dropped by up to 39% on January 1, 2026, depending on machine type. A planned charge for self-hosted runner usage on private repos, originally set for March 1, 2026, was postponed.
“Run your code at the edge” was the serverless pitch of the early 2020s: put logic close to users and cut latency. In 2026 the three platforms most associated with that pitch have taken noticeably different paths. We checked each one’s official documentation and pricing on October 28, 2026 to see where code actually runs today, what limits apply, and what it costs.
At a Glance
Spec
Cloudflare Workers
Vercel Functions
Deno Deploy
Where code runs
Cloudflare’s global network, across hundreds of locations
Configurable regions on Fluid compute; edge runtime runs nearest the request
2 regions on the new platform, plus self-hosted regions
Runtime
V8 isolates
Node.js (recommended) or Edge runtime (V8)
Deno 2, with Node app support
Free tier
100,000 requests/day, 10 ms CPU per invocation
Hobby: 1M invocations, 4 hrs Active CPU/month (non-commercial)
1M requests, 10 hrs Active CPU/month
Entry paid plan
$5/month minimum
Pro: $20/month with $20 usage credit
Pro: $20/month
Edge direction in 2026
Edge-first by design
Recommends migrating from Edge to Node.js
Fewer regions than Deploy Classic, which shut down July 20, 2026
Short Verdict
If “edge” is the requirement, meaning code that runs near every user by default, Cloudflare Workers is the platform still built around it, with a $5 paid plan and CPU-time billing that does not charge for time spent waiting on network calls. Vercel now steers developers away from its Edge runtime and toward Node.js on Fluid compute, which favors running functions near your data rather than near your users. The new Deno Deploy runs in two regions, so it is better viewed as a serverless platform than an edge network. Pick based on where your data lives: if your database sits in one region, compute next to it usually beats compute next to the user.
What “Edge” Means Here
Edge computing means processing a request in a location close to the user instead of in one central region. It shortens the network round trip for work that does not need a central database, such as redirects, authentication checks, personalization from cookies, A/B test assignment, and caching logic. It helps much less when every request must read from a single-region database, because the edge function then makes its own long round trip to that database.
Cloudflare Workers
Workers run on Cloudflare’s global network, which the company describes as thousands of machines across hundreds of locations, and a request arriving at any Cloudflare data center can invoke your Worker. Instead of a container or virtual machine per function, each Worker runs in a V8 isolate inside an existing runtime process. Cloudflare says an isolate can start around a hundred times faster than a Node process in a container or VM and uses an order of magnitude less memory at startup, which is why Workers avoid the classic cold-start penalty. Isolates can be evicted at any time, so global mutable state should not be relied on.
Plan
Requests
CPU time
Price
Free
100,000/day
10 ms per invocation
$0
Paid (Standard)
10M/month included, then $0.30 per million
30M CPU-ms/month included, then $0.02 per million CPU-ms; up to 5 minutes CPU per request (30 s default)
$5/month minimum
Cloudflare does not charge for duration, only CPU time, so a Worker that spends most of its time waiting on a fetch is billed only for the milliseconds it actually computes.
Vercel: From Edge Runtime to Fluid Compute
Vercel’s Edge runtime still exists and, by default, executes in the region closest to the incoming request. But Vercel’s own documentation now recommends migrating from Edge to Node.js “for improved performance and reliability,” notes that both runtimes run on Fluid compute with Active CPU pricing, and states that starting in Next.js 16.3, setting runtime = 'edge' is no longer supported. The Edge runtime also has real constraints: a subset of Web and Node.js APIs, no filesystem access, no eval, a requirement to begin responding within 25 seconds, and code size limits of 1 MB (Hobby), 2 MB (Pro), and 4 MB (Enterprise) after compression.
Resource
Hobby (included)
Pro (beyond included credit)
Active CPU
4 hours/month
From $0.128/hour
Provisioned memory
360 GB-hours/month
From $0.0106/GB-hour
Function invocations
1M/month
From $0.60 per million
Hobby is for personal, non-commercial use and cannot buy extra usage. Pro costs $20 a month, includes $20 of usage credit, and is pay-as-you-go beyond it.
Deno Deploy: Rebuilt, and Fewer Regions
Deno rebuilt Deploy on a new execution environment using Deno 2.0 that runs both Deno and Node apps, with first-class support for Next.js, Astro, and SvelteKit. Its documentation lists 2 regions for the new platform, compared with 6 for Deploy Classic, plus the option of self-hosted regions. Deno announced that Deploy Classic and the subhosting v1 API would shut down on July 20, 2026.
Plan
Price
Requests/month
Active CPU
Egress
Free
$0
1M
10 hours
20 GiB
Pro
$20/month
5M, then $2 per million
50 hours, then $0.10/hour
200 GiB, then $0.20/GiB
Builder
$200/month
25M, then $2 per million
500 hours, then $0.10/hour
2,000 GiB, then $0.20/GiB
Enterprise
Custom
Custom
Custom
Custom; 99.95% SLA
Pros and Cons by Platform
Cloudflare Workers pros: genuinely global by default, isolate-based startup, cheap $5 entry plan, no charge for waiting time. Cons: isolate runtime is not full Node.js, and the free tier’s 10 ms CPU cap is tight for heavier work.
Vercel pros: tight integration with Next.js and Fluid compute, configurable regions near your data. Cons: Edge runtime is being de-emphasized and is unsupported in Next.js 16.3+, and Hobby is non-commercial only.
Deno Deploy pros: generous free CPU allowance, Deno and Node apps, self-hosted regions, clear usage pricing. Cons: only 2 managed regions on the new platform, and teams on Deploy Classic had to migrate.
Bottom Line
The industry has quietly split “edge” in two. Cloudflare Workers still runs your code near the user everywhere, which is ideal for request-level logic that does not need a central database. Vercel and Deno have moved toward regional serverless compute placed near your data, which suits typical database-backed apps better. Decide which latency you are actually fighting, user-to-server or server-to-database, and the platform choice follows.
Frequently Asked Questions
Is Vercel’s Edge runtime deprecated? Vercel recommends migrating from Edge to Node.js, and setting runtime = 'edge' is no longer supported starting in Next.js 16.3.
How much does Cloudflare Workers cost? Free for 100,000 requests a day; the paid plan starts at $5 a month with 10 million requests and 30 million CPU milliseconds included.
Is Deno Deploy an edge platform? The new Deno Deploy lists 2 managed regions, so it behaves more like regional serverless; Deploy Classic, which had 6 regions, shut down on July 20, 2026.
When does edge computing not help? When every request must reach a single-region database, since the edge function then adds its own long round trip.
Role-based access control works until your product grows sharing: a document shared with a team, inside a folder shared with an organization, with one person blocked. At that point, permissions stop being a table of roles and become a graph of relationships. Google’s Zanzibar paper, published in 2019, described how Google handles that graph for services such as Drive, Calendar, YouTube, and Cloud. This explainer covers how Zanzibar works and how its two best-known open-source descendants, SpiceDB and OpenFGA, bring the model to everyone else.
At a Glance
Spec
Detail
What Zanzibar is
Google’s global system for storing and evaluating access control lists
Relationship-based access control (ReBAC) built on relation tuples
Scale reported in the paper
2+ trillion relation tuples, 10+ million client queries per second, 95th-percentile latency under 10 ms, availability above 99.999% over 3 years
Open-source implementations
SpiceDB (Apache-2.0) and OpenFGA (Apache-2.0, a CNCF project)
Best for
Products with sharing, nested groups, and hierarchies of resources
Short Verdict
If your permission rules sound like “anyone who can view the parent folder can view this file” or “members of a team inherit the team’s access,” a Zanzibar-style system models them directly instead of through ever-growing role tables. You do not need Google’s scale to benefit: SpiceDB and OpenFGA give you the data model and APIs as open source. The cost is a new piece of infrastructure to run and keep in sync with your application data, so simple apps with a handful of fixed roles are still better off with plain RBAC.
The Data Model: Relation Tuples
Zanzibar stores every permission fact as a relation tuple written object#relation@user. The paper’s example doc:readme#owner@10 means user 10 is an owner of the document readme. Objects are written namespace:object_id, and the “user” side can be either a user ID or a userset, which is another object#relation pair. That is what makes nested groups possible: a tuple can say “members of group X are viewers of this document,” and group membership is itself stored as tuples.
Each client defines a namespace configuration that lists its relations, such as owner, editor, and viewer, and optional userset rewrite rules that derive access instead of storing it. The paper describes three building blocks: _this (users stored directly on the relation), computed_userset (for example, every owner is also an editor, and every editor is also a viewer), and tuple_to_userset (for example, viewers of a document’s parent folder can view the document). These combine with union, intersection, and exclusion, which is how one small configuration expresses an entire permission hierarchy.
The APIs
API
What it does
Check
Answers “does this user have this relation to this object?” at a sufficiently fresh snapshot
Read
Returns stored tuples matching a filter, without applying rewrite rules
Write
Adds or removes tuples, with optimistic concurrency for read-modify-write
Watch
Streams tuple changes in timestamp order, so other systems can stay in sync
Expand
Returns the full effective userset as a tree, useful for building search indexes
The Hard Part: The “New Enemy” Problem and Zookies
One of the paper’s central ideas is how it keeps authorization consistent with content. Its example: Alice removes Bob from a folder, then adds new documents to it. If the system evaluates Bob’s access against an old copy of the permissions, Bob could see documents he should never see. Zanzibar calls this the “new enemy” problem. It solves it with external consistency built on Google Spanner’s timestamps, plus an opaque token called a zookie. When content changes, the client asks Zanzibar for a zookie encoding the current time and stores it with the content. Later checks send that zookie, guaranteeing evaluation against permissions at least that fresh, while most checks can still be answered quickly from nearby replicas.
For deeply nested groups, where following pointers one hop at a time gets slow, the paper describes a specialized index called Leopard that precomputes group-to-group and member-to-group sets so membership becomes a set intersection.
SpiceDB vs OpenFGA
SpiceDB
OpenFGA
Relationship to Zanzibar
Describes itself as the most mature open-source project inspired by Zanzibar; aims to stay true to the paper
Inspired by Zanzibar; ReBAC that can also express RBAC and some ABAC
License
Apache-2.0
Apache-2.0
Governance
Created by AuthZed; open-sourced September 2021
Owned by the Cloud Native Computing Foundation
Modeling
Schema language defining object types, relations, and permissions
Authorization models built from type definitions and relationship tuples
Consistency
Configurable per request, designed to prevent the new enemy problem
Supports contextual tuples supplied per request
Conditions / attributes
See SpiceDB docs
Conditional relationship tuples using CEL expressions
Storage
Pluggable: in-memory, Spanner, CockroachDB, PostgreSQL, MySQL
See OpenFGA docs for supported datastores
Pros
Permissions live in one service with one model, instead of being re-implemented in every microservice. Sharing, nested teams, and resource hierarchies are expressed directly rather than through role explosion. The Check API gives every service the same answer, and Watch-style change streams let search indexes respect permissions. Both leading implementations are permissively licensed open source.
Cons
It is another critical, latency-sensitive service to operate, and an outage blocks every access decision. Your application must write relationship tuples whenever ownership or membership changes, and drift between app data and authorization data becomes a new class of bug. Consistency tokens add complexity that teams need to understand to use correctly. For a small app with a few fixed roles, this is more machinery than the problem requires.
Bottom Line
Zanzibar showed that a single relationship-based model can cover permissions for products used by billions of people while staying fast and consistent. If your product has sharing and hierarchies, its model is worth adopting through SpiceDB or OpenFGA; prototype your permission rules in either tool’s schema and see whether they read more clearly than your current role checks. If they do not, plain RBAC is still fine.
Frequently Asked Questions
Is Zanzibar available to use? Zanzibar itself is internal to Google; SpiceDB and OpenFGA are open-source systems inspired by its paper.
What is a relation tuple? A stored fact of the form object#relation@user, such as “user 10 is an owner of doc readme.”
What is the new enemy problem? Evaluating access against stale permissions, so a removed user can see content added after the removal. Zanzibar prevents it with consistency tokens called zookies.
Is ReBAC a replacement for RBAC? It is a superset: roles can be modeled as relations, and OpenFGA notes its model can express RBAC and some ABAC scenarios.