Atoms review: what it costs, what it builds, where it stops

What Atoms actually is, and how it works

Atoms sells itself as AI employees rather than a chat assistant. The homepage promises idea validation, product build and customer acquisition without coding. The AI Agents page names eight personas: Mike the Team Leader, Iris the Deep Researcher, Bob the Architect, Emma the Product Manager, Alex the Engineer, Sarah the SEO Specialist, Adrian the Ads Specialist and David the Data Analyst. The working interface is an input box with a Mode Switch control at the bottom left, and the agents run behind it.

The roster is not stable across Atoms’ own documentation. The help centre’s official ’Your Agents Team’ article documents only seven agents and omits Adrian the Ads Specialist entirely. It also heads David’s entry ’Data Scientist’ while his own bio text calls him a Data Analyst, against the marketing site’s Data Analyst. Where Adrian is documented, he works only with Google Ads, and he requires you to hold a Google Ads account and spend real money. Atoms does not fund the ads.

There are four documented modes but three different ways of reaching them. Engineer Mode runs Alex alone and is cheaper. Team Mode is multi-agent and costs more credits. Race Mode is Max-plan only. Deep Research Mode is Iris. The Mode Switch button only offers Engineer or Team. Deep Research is invoked by typing @Iris, and Race Mode is chosen separately at the chat box. Neither Atoms’ pricing page nor its help centre attaches a credit number to any of these, so ’more credits’ is the only guidance you get before you spend.

Atoms Cloud is the substantive part of the product. It provides six named services: a database, user authentication including Google social login, Stripe payments, custom domains, API key management and native LLM or agent integration, and it configures itself by detecting what the project needs. The launch blog describes the stack as OIDC authentication, an object-relational database, managed object storage, serverless compute and Stripe, provisioned by agents from a natural-language description. The blog does not name the database engine. The only place Atoms names PostgreSQL is a changelog entry dated 18 May 2026, which shipped an in-product database interface with table browsing, editing and CSV import and export.

Model choice is documented badly. The Models page lists 24 model cards and claims these are the models available on Atoms, with family counts of Claude 7, GPT 4, Gemini 2, DeepSeek 2, Qwen 4, GLM 1 and Grok 1. It states no credit cost and no plan availability for any of them, so you cannot tell from that page which models a Free, Pro or Max subscriber can actually select. The help centre’s model-selection guide is worse: it documents five selectable models, and four of them no longer appear on the Models page at all.

The trade-off is the whole bet of the product. If a team of personas plans and builds better than one strong model, the overhead is worth paying. The published evidence does not settle that. A Trustpilot reviewer argues directly that the multi-agent setup produces worse output than a single LLM such as Claude, with the agents hallucinating while consuming credits. Atoms’ own troubleshooting documentation concedes that agents can repeat actions without making progress and can enter infinite loops, and tells the user to stop and rewrite the prompt. In a metered product, a loop is a bill.

What it can really build, and what it cannot

The marketing claims widen as you move through the site. The homepage’s ’What can Atoms build?’ strip names six output types, including a video and a game alongside websites. The About page claims more, promising websites, apps, slides, videos, workflows and games from one idea. The homepage also claims that every app comes with user login, data storage and Stripe payments, under the heading ’Real apps, not just demos’, and advertises embedding third-party models such as Gemini and GPT into your own product with no API keys and no setup.

The Use Cases page is narrower and more revealing. It is organised into just three categories: Website, Deep Research and App. The overwhelming majority are industry-templated website builders for salons, dental practices, law firms, weddings, hotels, bands and spas. Games and full-stack apps do appear, under App, with the game entry promising scoring, accounts and multiplayer. If you want to know what Atoms is used for rather than what it can theoretically produce, that page is the better guide.

The most useful sentence Atoms has written about its own scope is in the help centre, not the marketing. The project-scope article says Atoms is optimised for rapid prototyping, data visualisation, web applications and custom mini-games, while it continues to work toward more complex systems. That is a prototyping tool describing itself accurately, and it should carry more weight in your decision than the six-output-type strip on the homepage.

Mobile is where the documentation openly conflicts. A May 2026 changelog entry added mobile app projects with preview, QR-code device testing and Android build support. The Build & Export article still says Atoms currently works with web apps and cannot export a project as an .apk or generate mobile app packages. The project-scope article says Atoms does not generate native iOS or Android binaries or desktop executables, and delivers mobile experiences via Progressive Web Apps and responsive web applications. Three documents, three positions. We could not establish which is current.

The deployment gaps are real and specific. Atoms generates full Next.js project code but cannot deploy Next.js applications on its own platform, so you download the project and host it elsewhere. Static standalone HTML output gets no one-click hosting, which sits awkwardly against an ’HTML Website Builder’ on the Use Cases page. The documented deployment options include no Atoms-hosted path for exported code at all. What Atoms hosts and what Atoms generates are not the same set.

Video Mode exists, with an in-product editor covering clip selection, splitting, zooming and local export. Access is gated to ’eligible users’ rather than open to everyone, and Atoms does not publish the eligibility criteria. Treat the video output type on the homepage as conditional until you have confirmed you qualify.

The trade-off: what Atoms reliably builds is a web application that lives on Atoms’ hosting with Atoms’ backend attached. Everything the marketing adds beyond that is either plan-gated, contradicted elsewhere in the docs, or requires you to take the code and host it yourself. Buy it for the first thing. Do not buy it for the list.

The credit system, and what a month really costs

There are three plans: Free at $0, Pro starting from $20 a month, and Max starting from $100. ’From’ is load-bearing. Pro is not one price but a set of monthly credit tiers: 100 credits for $20, which is the default, 250 credits for $50, and 350 credits for $70. Max runs 500 credits for $100 as the default, 1,000 for $200 and 1,500 for $300, with tiers extending up to 10,000 credits a month. The $20 headline is the floor of a ladder, not the price of the product.

The pricing page carries a billing-period toggle labelled ’Yearly · Save up to 21%’ and ’Monthly’. On yearly, Pro shows at $15.8 a month and Max at $79 a month, each badged 21% OFF against the $20 and $100 monthly figures. Our passes over the page did not agree on whether the monthly rates also appear struck through beside the yearly ones. Either way this is a billing-period toggle, not a limited-time discount off a list price. The help centre is more precise than the badge: annual billing gives 21% off on the first credit tier and 18% on tiers above it, measured against twelve consecutive monthly payments. No annual total is published anywhere, only per-month rates, so the multiplication is yours to do.

Every plan carries the same free allowance, and this is widely misread. The line ’Credits: 15 per day / 25 per month’ is printed under Free, Pro and Max alike. It is a baseline daily grant across tiers, not a Free-only perk, and it stacks on top of your plan credits. Credits are spent in a fixed order: daily free first, then subscription, then bonus, so your paid balance is only touched once the free allowance is gone. The daily figure is not fixed either. Atoms says the per-day amount may adjust based on earlier usage while the cycle total stays the same, and once the 25-credit cycle cap is hit the daily refresh stops until the next billing cycle.

Here is the gap that matters more than any price on the page. Atoms nowhere publishes what a credit buys. We expanded the pricing page’s own credit FAQ: the answer defines where credits come from and the order in which they are spent, and never states what one credit does. The Models page lists 24 models with no credit cost against any of them. Team Mode is documented as costing more than Engineer Mode, without a number. Race Mode costs extra credits, without a number. You are being sold a currency with no published exchange rate.

Rollover is thinner than it looks. On monthly billing, rollover applies to four specific credit sources only: mid-cycle upgrade surplus, special-circumstance bonus credits (explicitly excluding the daily 15-credit gift), referral credits and redemption-code credits. Those roll for one additional month and then expire, and the rollover is not cumulative. Ordinary unused subscription credits are not covered. On the pricing page, ’Credits rollovers’ appears in the Pro and Max feature lists only when the toggle is set to Yearly, and disappears from both when you switch to Monthly. Annual plans genuinely get better treatment: credits release in twelve equal monthly instalments, unused credits roll within the same billing year up to the annual limit, and leftovers can carry into the next annual cycle on renewal.

When you run out mid-month there is no small fix. Atoms documents no way to buy one-off credit top-ups. Asked directly whether you can buy extra credits if you run out, the pricing FAQ answers only that you can upgrade to a higher plan at any time, effective immediately. Upgrading does not reset your billing date, and Atoms says you pay the difference in plan price for the remainder of the period. But its own worked example charges the full difference rather than a day-weighted share: upgrading from a $20 plan to a $100 plan with 20 days left costs $80. The mid-month escape hatch is priced like a full month.

Reviewers report the predictable outcome. One says his $20 plan was exhausted after only a few basic prompts, that Atoms then asked for a further $50 a month, and that it is impossibly expensive to actually finish a website there. Another says the credit mechanics are not clearly explained, leaving users repeatedly buying more. Another reports $700 spent under continuous upgrade pressure with a website that still did not work. The trade-off is clean: Atoms starts cheaper than most of its rivals and includes more. What it does not give you is any way to predict the number at the bottom of the month.

The second bill: Atoms Cloud and the AI Wallet

Your subscription does not pay to run what you build. Atoms bills cloud and AI usage separately, from something called the Cloud & AI Wallet, covering compute, storage, serverless executions and LLM API calls once the free quota is used up. If you read only the pricing page you will not budget for this, because the pricing page is about build credits and the wallet is about running the result.

The free AI allowance inside the wallet is worth exactly $1. After that, running any AI feature in a published app requires topping the wallet up. Top-ups are prepaid, in amounts between $10 and $1,000, and they buy infrastructure, not build credits. This is the only thing Atoms sells on top of a subscription, which is a strange asymmetry: you can prepay for hosting but you cannot buy 50 more credits.

Free-plan users cannot top up the wallet at all. They must buy Pro or Max first. So any app that exceeds a dollar of AI usage forces a paid upgrade, no matter how many build credits you still have. If the thing you want to make calls a model on every page view, the free tier will not host it for long.

What happens when the wallet empties is documented, and it is the clearest published answer to the question of what takes a running Atoms app offline: the application stops when the wallet balance and the free quotas run out. That is worth reading twice if you were planning to point a client’s domain at this.

The spending cap is not a hard stop. The default monthly limit is $500, and the default action on hitting it is to pause every one of your apps. Atoms then warns that actual charges may exceed the cap, because billing is postpaid and storage is billed hourly. So the cap is a pause trigger with an overshoot warning attached, not a ceiling.

The unit rates are published in part, and the part that is missing is the part that scales. Atoms’ Billing & Refunds article states three: database storage at $0.525 per GB-month, serverless requests at $0.30 per million requests, and object storage at $0.025 per GB-month. Those are the cheap, predictable dimensions. It states no rate at all for compute, and none for AI model inference, which it describes only as API usage for GPT, Claude and LLM calls in published apps. Those two are the ones that move with traffic. So you can forecast what it costs to store your data and not what it costs to serve it, which is the wrong half to know. For contrast, Bolt publishes hosting quotas on its public pricing page: 1M web requests and a 100MB upload limit on Pro, 333k requests and 10MB on Free, with unlimited databases on both.

The trade-off: bundling hosting, auth, a database and Stripe is the substantive claim behind Atoms’ whole competitive pitch, and its own comparison page concedes Lovable has a backend product too. The price of that bundle is that your app’s running cost is a variable Atoms has chosen not to publish. Assume it is small for a brochure site. Do not assume anything for an app that talks to a model.

Refunds, cancellation, and the terms you are agreeing to

The default position is non-refundable. Atoms’ terms of service and its help centre both state that subscription fees stop being refundable as soon as credits begin to be consumed, with refunds or credit compensation granted only case by case. Almost everything else in this section follows from that one sentence.

The refund window is published in the terms, not in the help centre. EU, UK and Turkey users have 14 days from the charge. Everyone else has 24 hours. In both cases the clock stops the moment credits begin to be consumed, whichever comes first. A refund also requires that you have generated zero service call records, verified against Atoms’ system logs. In practice this means any use of the product at all disqualifies you, which is a meaningful thing to know before you type your first prompt after paying.

The two official channels contradict each other. The terms route refund applications to service@atoms.dev. The help centre says refunds must be requested through Help Center chat, reached via Avatar then Help Center then the chat icon, supplying your registered account email, an invoice screenshot and proof of payment, and choosing between a cash refund and credit compensation. The help centre commits to reviewing and responding within 24 hours. The terms state a five business day review and a Stripe payout of five to ten business days. Both are Atoms’ own documents.

The one refund route that survives credit consumption is a product bug, and the terms place the burden of proof entirely on the user while committing Atoms only to ’reasonable compensation’ rather than a cash refund. Compensation, where granted, is issued as credits that cannot be exchanged for cash. Credits spent on poor AI output are explicitly excluded: quality problems and unsatisfactory results do not qualify for compensation at all. One reviewer reports platform bugs burning through his credits, followed by his live website and custom domain going offline with no warning, fix or compensation.

Cancellation is framed as a downgrade. You downgrade to the Free plan in Settings, under Plans and credits. It never takes effect immediately and never produces a refund: the paid tier runs to the end of the current cycle and Free starts the first day after. Cancellation must be completed before the current billing cycle starts, so a cancellation made after a new cycle has begun does not stop that cycle’s charge. Unused credits are forfeited at the end of the cycle. Atoms explicitly refuses refunds for partial usage periods, and refuses any refund or compensation for gifted credits. Both paid plans auto-renew every month unless you act.

The rest of the terms are mostly what you would expect, with a few worth flagging. The service is provided as is, with no uptime or availability commitment anywhere in the document. Total liability is capped at what you paid in the twelve months preceding the claim. You indemnify Atoms, its affiliates and its personnel for third-party liability or governmental penalties arising from your actions. Disputes are governed by Delaware and US federal law, so non-US customers pursue claims under a foreign legal system. Atoms may suspend or terminate access without prior notice where it believes you materially breached, and reserves the right to delete any materials or data associated with a terminated account. One point cuts the buyer’s way: there is no arbitration clause, no class-action waiver and no jury-trial waiver, which is unusual for a US-incorporated SaaS.

The privacy policy is thin in the places that matter to a business buyer. Atoms stores all content you post, send, receive or share through the service, alongside log, device and geolocation data and cookies. It commits only to ’commercially reasonable’ security and names no encryption standard and no certification such as SOC 2 or ISO 27001. It sets no fixed retention period. It warns that deletion requests may not fully take effect where data has already been backed up, with no deadline for eventual deletion. It allows personal data to be transferred to a successor company in a merger or acquisition, names no specific subprocessors or AI model providers, and hosts in the United States, treating continued use as your transfer of data there. It never names the GDPR or the CCPA. And in roughly 12,000 characters it never uses the words ’train’ or ’machine learning’, so Atoms makes no statement in either direction about whether your prompts, project content or generated code are used to train models. The trade-off here is simple to state: this policy set is internally consistent, and it is consistent in one direction.

Who is behind Atoms

The entity you contract with is MetaGPT LLC, described in Atoms’ terms of service as a US incorporated company with its principal place of business at Ste R 8 The Green, Dover, Delaware, document number 7606285. The privacy policy names the same entity and address. The team operating it is DeepWisdom, according to KrASIA’s reporting. Atoms’ own About page does not itself state that Atoms is built by DeepWisdom, and does not give its lead a founder or CEO title.

The lineage is stated openly. Atoms’ About page labels three eras: 2022 to 2023 MetaGPT, described as the first open-source multi-agent coding framework; 2024 to 2025 MetaGPT X, or MGX, billed as the World’s First AI Development Team; and now Atoms. Atoms is a rename of MGX announced on 13 January 2026, done, per KrASIA, because MGX was judged difficult to pronounce in English and poorly suited to consumer adoption. The South China Morning Post confirms Atoms was previously known as MGX. The MetaGPT, OpenManus and Foundation Agents links in Atoms’ footer are the company’s own research heritage rather than partnerships, and deepwisdom.ai now issues a 301 permanent redirect to atoms.dev/metagpt.

The funding is real and recent. DeepWisdom was founded in 2019 by Wu Chenglin, who previously led large-scale AI deployments at Huawei and Tencent. It raised roughly RMB 220 million across two rounds in the first half of 2025, about US$31 million, in Series A and A+ rounds led by Cathay Capital and publicly announced in January 2026. Reported backers include Ant Group, Cathay Capital, Jinqiu, Baidu Ventures, MindWorks Capital and Concept Fund. KrASIA reports the company had more than 80 employees, and a February 2026 report put it at about 100. KrASIA also notes MGX launched under financial strain, relying on server and model credits from UCloud and Amazon Web Services before the funding closed.

The academic standing is genuine. The MetaGPT paper was published at ICLR 2024 and lists Chenglin Wu and Jürgen Schmidhuber among its authors. Atoms claims roughly 30 papers including MetaGPT (ICLR 2024 Oral) and AFlow (ICLR 2025 Oral). Lead investor Cathay Capital writes that MetaGPT had ranked number one on GitHub Trending 17 times. MetaGPT is MIT licensed, was created on 30 June 2023, and on 1 September 2026 had 70,145 GitHub stars, 8,915 forks and 132 open issues.

The traction numbers around that research are looser, and worth handling carefully. Atoms claims 168K GitHub stars, but that is an aggregate across the team’s open-source projects, not stars on Atoms. Investor MindWorks Capital states MetaGPT and OpenManus have accumulated over 150,000 stars; the two repositories measured 128,287 between them on 1 September 2026. On MGX’s first month, 36Kr reports 500,000 registered users and US$1 million ARR, while MindWorks reports more than 700,000 users for the same period. By September 2025, 36Kr records 1.2 million monthly visits and more than 10,000 applications generated per day. Atoms itself claims over 1,000,000 builders across more than 170 countries and regions, plus a World Economic Forum Technology Pioneer naming in 2026 and a number one Product of the Day and Week on Product Hunt attributed to MGX. We did not independently verify any of those awards or user figures.

Two maintenance signals are worth weighing. MetaGPT, the project Atoms names as its foundation, had received no pushed commits since 21 January 2026, roughly seven months of inactivity as of 1 September 2026. OpenManus, built by MetaGPT team members and hosted in the same FoundationAgents GitHub organisation, was still receiving commits on 22 August 2026 and had 58,142 stars, 10,100 forks and 465 open issues. The FoundationAgents organisation itself was created in February 2025, has 23 public repositories and about 1,100 followers, is not GitHub-verified, and publishes no company name, location or contact metadata. The MetaGPT README still references the repository under a personal account path. Foundation Agents, the third footer link, presents itself as a research organisation, names no people, companies or institutions, and does not mention MetaGPT, OpenManus, DeepWisdom or Atoms anywhere on its site.

The trade-off: this is a well-funded team with real academic standing and an investor list that includes Ant Group and Baidu Ventures. None of that tells you whether your billing ticket will be answered. It is also worth knowing that the company’s headquarters is reported inconsistently. 36Kr and KrASIA place DeepWisdom in Shenzhen; the South China Morning Post reports Shanghai. As of February 2026 the company had not yet entered the US market and described the expansion as forthcoming. If where your vendor is legally and operationally based matters to your organisation, treat that as unsettled.

The contradictions in Atoms’ own documentation

The rebrand is not finished, eight months on. The help centre still refers to the product as MGX in its plan documentation. The terms of service, effective 13 January 2026, still assert ownership of the MGX brand and the mgx.dev domain. Front-end assets are served from a path named nuxt-mgx, and custom domain verification uses a TXT record whose host is literally _mgx_verify. On its own this is cosmetic. As a gauge of how much of the documentation has actually been reviewed since January, it is useful.

Several contradictions have a price attached. The homepage card for Race Mode describes running one prompt across multiple models and states no plan restriction; the pricing page lists Race mode only under Max, and the help centre says it is only available to Max Plan users. The homepage claims code export and GitHub sync are available ’anytime’ with no plan qualifier; the pricing page lists ’Download projects’ only under Pro and Max. Atoms’ own Base44 comparison page then states that Atoms offers code export and GitHub sync on all plans, while criticising Base44 for gating GitHub integration behind its Builder tier. Atoms’ marketing contradicts Atoms’ pricing page on a feature Atoms uses to attack a competitor.

Custom domains produce the strangest one. The Domain Management article gives step-by-step DNS instructions, pointing an A record at Atoms’ gateway IP 107.150.101.9 and adding a TXT record on host _mgx_verify, and then states in an FAQ on the same page that custom domains are not supported. The pricing page lists Custom domain as a Pro and Max feature, and Atoms resells domain registration inside the product through a partnership with IONOS. On balance the feature exists and the FAQ line is stale, but a buyer should not have to arbitrate that.

Counts disagree too. The pricing page gives Free users 2 Atoms backend projects; the Atoms Cloud help article says 1. That same article refers to a ’Pro+’ tier that does not exist on the pricing page, and notes that Free users’ cloud projects default to public with privacy requiring a paid upgrade. The marketing site names eight agents; the help centre documents seven and gives one of them a different job title from the one in his own bio.

Some pages are simply stale or empty. The model-selection guide documents five selectable models, four of which no longer appear on the Models page at all; only Qwen3 Coder Plus survives. The Models page’s own category filters are internally inconsistent: Kimi K3 is the sole entry under ’Video Models’ while Seedance 2.0, the one model the page describes as a video model, appears in no category; ChatGPT Images 2.0 is missing from ’Image Models’; and text-only models such as Claude Opus 4.6 are filed under ’Image Models’. The Tools page, linked from the main product navigation, renders a headline and then ’No tools found’.

Several headline features are narrower than the marketing implies. Sarah, the SEO agent, is locked to Team Mode, the more credit-expensive of the two build modes, so the SEO capability advertised on the homepage cannot be used in the cheaper mode. She also does not get your site indexed: the documented workflow has the agent generate meta tags and a sitemap while you personally register the site in Google Search Console, paste a verification meta tag back to the agent, submit the sitemap and request indexing. The Marketing module is a dashboard over your own Google properties, requiring you to own a Google account, create a GA4 property and connect Search Console. Deep Research is Team-Mode only, switches itself off after every single message or Remix, cannot run alongside Race Mode, and simply fails if credits run out mid-run. Race Mode takes five to ten minutes per run, costs extra credits, and is blocked entirely on projects that use Supabase or Stripe integrations.

The trade-off is worth stating fairly. Detailed documentation is a good sign, and Atoms’ credit, wallet and terms articles are more detailed than several rivals’. The problem is that the detail contradicts the marketing more often than it confirms it, and every hour spent reconciling the two is an hour of your own. Read the help centre and the terms before you pay. Treat the homepage as a brochure.

Atoms against Lovable, Bolt, v0 and Replit

Entry prices, taken from each vendor’s own pages on 1 September 2026. Atoms Pro: $20 a month for 100 credits, or $15.8 a month on yearly billing. Lovable Pro: $25 a month for 100 monthly credits, or $250 a year, an effective $21 a month. Bolt Pro: $25 monthly, $18 on annual, metered in tokens rather than credits, starting at 10M tokens a month with no daily limit and unused tokens rolling over. v0 Plus: $30 per user a month, buying $30 of included monthly credits plus $2 of free daily credits on login. Replit Core: $20 a month, $17 billed annually, including $20 towards its most powerful models and 2 parallel agents. Base44 Starter: $20 monthly or $16 billed annually, for 100 message credits and 2,000 integration credits.

Only Atoms and Lovable use directly comparable units at the entry tier: 100 credits for $20 against 100 credits for $25. Even there, a credit means whatever each vendor says it means, and neither publishes a conversion to actual work. Bolt’s tokens are at least a unit you can reason about if you have used an API. v0 and Replit sidestep the problem by denominating the allowance in dollars, $30 of credits and $20 towards models respectively, which is the most legible of the five approaches because you can compare it to a model bill you have already paid. Atoms is the only one of the five in this comparison that gives you neither a dollar figure nor a token count.

Free tiers vary more than the paid ones. Atoms gives 15 credits a day capped at 25 a month, 2GB of disk, unlimited project sharing and a single seat. Base44 gives 25 message credits a month, 100 integration credits and a cap of 5 apps. Lovable gives 5 build credits a day capped at 30 a month, plus monthly Cloud grants of 20 credits and AI grants of 4 that apply on Free, Pro and Business alike, and includes unlimited collaborators and 5 lovable.app domains. Bolt gives 300K tokens a day and 1M a month, with Bolt branding on what you build. v0 gives $5 of monthly credits and caps you at 7 messages a day. Replit’s free Starter lets you publish exactly one live project, with no comparable credit figure published. Atoms’ free monthly ceiling is level with Base44’s and just under Lovable’s.

Atoms wins clearly on seats. Both paid tiers include unlimited team members, centralised billing and centralised access management. Bolt charges $30 per member per month on Teams. Replit’s $100 Pro tier caps you at 15 collaborators and 50 viewers, with seat-unlimited access an Enterprise feature. That is a genuine price advantage for a small team. The catch is in Atoms’ own Team Workspace documentation: every member of a paid workspace draws from one shared credit pool, so ten collaborators on Pro share 100 credits a month, not 100 each. There are only two roles, Owner and Editor, with no viewer, reviewer or read-only option, and every Editor can send agent messages and edit code. Every seat can spend the pool.

Atoms loses on the mechanics around running out. Lovable and Base44 both sell mid-cycle credit top-ups; Lovable charges $15 per 50 credits on Pro and $30 per 50 on Business. Atoms sells none, so your only response to running dry is a full upgrade. Lovable offers credit rollover without an annual commitment; Atoms’ rollover is effectively an annual-billing feature and, on monthly, covers only four credit sources that exclude ordinary unused subscription credits. Base44 states plainly that apps stay live after cancellation; we could find no equivalent statement from Atoms. And Atoms sells no enterprise or contact-sales tier at all: its pricing page ends at Max, while Lovable, Bolt, Replit and Base44 all publish an Enterprise tier with SSO and security controls.

The governance gap shows up in the footer. Lovable’s pricing page footer links Security, a Trust center, Status, a DPA, Report abuse and Report security concerns. Atoms’ site footer offers no security page, no trust centre, no status page, no DPA and no security-disclosure contact. If you are buying on behalf of an employer with a vendor review process, that difference will likely end the conversation before the pricing does.

Do not use Atoms’ own comparison pages as a shortcut. They overstate Replit’s entry price at $25 when Replit’s own page lists Core at $20, discounted to $17 annually. They name a ’v0 Team plan’ starting at $30; v0 has no plan by that name, its $30 per-user tier is called Plus. Bolt is not among the 29 products Atoms compares itself against, and atoms.dev/comparison/atoms-vs-bolt returns HTTP 410 Gone. The comparison set is padded with Asana, Salesforce, Circle and Airtable, which are not AI app builders. The Lovable figure of $25 is the one we checked and found correct, and even that page’s feature table concedes Lovable has a backend product. Separately, one independent comparison, disclosed as paid placement and containing no from-scratch build and no credit-consumption figures, found Atoms strongest with JavaScript and TypeScript and recommended switching to Replit for Python, Go or Rust. KrASIA notes that Atoms’ own performance claims against Lovable and Replit have not been independently verified. Neither have we verified them, because we did not run a build.

What users report, and how much of it to believe

Start with the fact that governs everything else in this section. Trustpilot has suspended Atoms’ star rating, displaying a warning that the company breached Trustpilot’s guidelines and stating that Trustpilot removed fake reviews from the profile. The suspension was still in force on 1 September 2026. That does not mean the negative reviews are true and the positive ones invented. It means the profile has been manipulated, so nothing on it is clean evidence in either direction.

The distribution is polarised almost to the point of being useless as an average. Of 62 reviews in the last 12 months, 42% are one star and 40% are five stars, with 8% at four, 7% at three and 3% at two. There is almost nothing in the middle. The most recent review is dated 22 August 2026.

The negatives are specific, which is what makes them worth reading even on a compromised profile. Named reviewers report $700 spent under repeated upgrade pressure with a site that still did not work; $100 spent for a broken codebase with a refund refused despite detailed technical evidence; a refund refused on the grounds that 13 credits had already been consumed; a $20 plan exhausted after a few basic prompts followed by a request for $50 a month; a live website and custom domain going offline with no warning, fix or compensation after platform bugs burned through the credits; agents that are slow, write incorrect code and break functionality that previously worked; agents that charge credits before verifying feasibility, forget earlier work, make unauthorised changes and report an audit as done when it was not; and recurring card charges for a service the reviewers say they were not using, in one case totalling around EUR 60 and in another $70. One reviewer who had upgraded to a paid plan reports emailing support about connecting a domain on 14 August 2026 and receiving no response by 22 August.

The positives exist, and some are specific. One reviewer reports turning an idea into a working app in under one afternoon. Another says the team investigated root causes on her meditation platform rather than applying quick fixes. Another says the team responded within one day. But the shape of the positive set is itself informative: most five-star reviews are short and non-specific, they cluster in the four weeks from late July to mid-August 2026, and of the 16 five-star reviews listed only four describe an identifiable project. The negatives, by contrast, name dollar amounts, dates and technical failures.

One recurring complaint is wrong, and it is only fair to say so. A reviewer states they could not find any abuse, legal or privacy contact anywhere on the Atoms site. Atoms does publish one: service@atoms.dev, named in the terms of service for complaints, appeals, abuse reports, refunds and privacy rights. Burying it in a legal document instead of the footer is a real usability failure. It is not an absence.

Everywhere else the evidence base is thin or contradictory. Product Hunt still lists the product under its old name, ’MGX (Now Atoms)’, with 4.4 out of 5 from just 24 reviews, all timestamped 11 months to a year old and therefore predating the rebrand entirely. Reviewers there who rate it positively still flag weak context handling, shallow integrations and reliability problems in real-world use. One reports roughly 16 hours across two days and, in his telling, 33 million credits, without ending up with a working website after the admin dashboard link turned out to be dead; that credit figure does not map onto the units Atoms sells today, which is itself an argument for discounting pre-rebrand reviews. Another reports the platform destroyed work already completed, with unresponsive and dismissive support. Capterra lists the product as ’Atoms AI’ with a perfect 5.0 from 10 reviews, which cannot easily be reconciled with the Trustpilot profile. AlternativeTo’s listing has one like and no comments or reviews. A search of the full Hacker News archive returns zero results for atoms.dev, though Atoms does run an official subreddit linked from its own help centre, so absence from search indexes is not absence of discussion.

Finally, be careful what you count as a review. Atoms’ ’Videos’ navigation item is not a product feature. It is a marketing feed of third-party YouTube reviews and tutorials, many of them explicitly sponsored or affiliate-linked, so the performance claims inside them are creator claims rather than Atoms’. The most-cited written comparison of Atoms against Lovable and Replit is disclosed paid placement and contains no from-scratch build, no credit-consumption figures and no side-by-side hands-on testing. The trade-off: this is a product with a loud review record and no trustworthy one. If you need external validation before spending, you will not find it. You will have to test it yourself, which is the strongest argument for starting on the free tier.

Lock-in, and who should actually buy this

The good news on lock-in first, because it is better than the rest of this review might suggest. Atoms claims no ownership of generated code and permits commercial use, modification, distribution and open-sourcing of it. Atoms Cloud is built on Postgres and standard HTTP APIs rather than a proprietary data store, according to the Atoms Cloud launch post, and the May 2026 changelog names PostgreSQL directly alongside an in-product database interface with CSV import and export. If you can get the code and the data out, what you are left with is an ordinary application on ordinary infrastructure.

Getting it out is not frictionless. Export is a .zip download from the Editor panel. Automated GitHub or GitLab push requires handing the agent a repository address and a Personal Access Token, and Atoms’ own documentation recommends manual upload over the automated route. GitLab sync is restricted to repositories on a publicly accessible domain. Both ’Download projects’ and data download are Pro and Max features and do not appear in the Free plan’s feature list. The first thing you need in order to leave is a paid subscription.

The backend travels less easily than the code. Migrating off Atoms Cloud at scale is not self-serve: the documented path is to contact Atoms for on-demand infrastructure support. Turning on Atoms Cloud also disables version history for the project, so only the latest build is retained, which removes your ability to roll back a bad agent run. Downgrading does not delete project data outright, but with disk dropping from 100GB on Max to 10GB on Pro to 2GB on Free, Atoms puts the burden on you to back up or delete files before the reduction takes effect.

Account-level risk sits above all of it. Atoms may suspend or terminate access without prior notice where it believes you have materially breached the terms, where it must comply with law, or where it judges immediate action necessary for security, and it reserves the right to delete any materials or data associated with a terminated account. If it terminates for what it judges a material breach, you forfeit any refund and Atoms reserves the right to pursue you for its losses. Free accounts inactive for over a year can be deleted with 30 days’ email notice. In the other direction, Atoms can terminate a paid subscription at any time on 30 days’ written notice with a pro-rata refund. The service is provided as is with no uptime commitment, and total liability is capped at what you paid in the preceding twelve months. Support channels are a Discord community, an AI bot in the help centre and email, with no human response-time commitment named, and Atoms Support is directed at paid users.

So, the practical sequence for someone deciding this week. Do not start by paying. The free tier gives 15 credits a day up to 25 a month, and that is enough to learn whether the agents can hold your actual project in their heads. Build the real thing, not a demo. Count how many credits one meaningful change costs, because Atoms will not tell you and that number is the only honest input to your budget. Be aware that on Free your projects are public by default, the Atoms badge stays on, direct code editing is off, and you cannot download what you make.

If the free run goes well, buy one month of Pro at $20 rather than committing to a year at $15.8 a month. The annual plan does have materially better credit mechanics, with twelve equal instalments, rollover within the billing year and leftovers carried on renewal, and that is precisely why you should not buy it until you know the product works for you. The refund window is 24 hours for most of the world, 14 days in the EU, UK and Turkey, and it closes the instant credits begin to be consumed. An annual commitment is effectively non-returnable from your first prompt.

Then decide your ceiling in advance. Set the Cloud & AI Wallet cap deliberately rather than accepting the $500 default, and remember Atoms warns that actual charges can exceed the cap because billing is postpaid and storage is billed hourly. Diarise the cancellation date, because cancelling after a new cycle has begun does not stop that cycle’s charge. The trade-off, stated plainly: Atoms is the cheapest route we found to a hosted full-stack web app generated from a prompt, from a research team with genuine credentials and unlimited seats included at $20. It is also the vendor in this comparison that publishes the least about what things cost and stands behind the least once you have paid.