Replit
Browser-based agentic vibe-coding platform with Agent 4 parallel multi-agent execution + infinite design canvas, Security Agent, and Auto-Protect.
Dimension breakdown
Score · confidenceBrowser-based agentic vibe-coding platform with Agent 4 parallel multi-agent execution + infinite design canvas, Security Agent, and Auto-Protect. Power mode auto-routes to Claude Opus 4.8 (launched 2026-05-28). $9B valuation ($400M Series D, Georgian), ~$1B ARR run-rate trajectory, 50M+ users, 85% of Fortune 500, NRR up to 300% — Market Leader viability.
Visa investment + Intelligent Commerce partnership (May 2026), Solution Partner Program (Accenture/Slalom/Hexaware), self-serve Enterprise up to $200K ACV. SOC 2 Type II, SSO/SAML/SCIM, SIEM audit logs.
reliability remains a problem (25 incidents/90d per StatusGator — just below downgrade-trigger threshold; Agent off-rails, context loss between sessions, loop-of-errors burns credits); Trustpilot 3.3/5 with predatory-billing as dominant complaint theme; no default spending cap; pricing-volatility cap active (June 18/July 1 2026 effort-based pricing = 6th restructure; clock reset, earliest lift ~July 2027); cloud-only (VPC isolation "coming soon", no FedRAMP/self-hosted).
Use cases
Not yet assessed — this section fills in as ACES research covers the tool.
Risk flags
Pricing volatility
enterpriseTemporaryFrequent pricing changes causing budget unpredictability
Caps Enterprise / Compliance at 60
Removed when — 12 months of pricing stability with no user complaints about billing surprises
Reliability complaints
trustTemporaryWidespread reliability complaints (breaks often, unreliable output)
Caps Autonomy at 60
Removed when — 90+ days of improved reliability with community acknowledgment
Status rationale
Assessed because Agent 4 with parallel multi-agent execution + infinite design canvas, Power-mode auto-routing to Claude Opus 4.8, and Security Agent + Auto-Protect provide meaningful agentic capability evidence; $9B valuation, Visa investment, Solution Partner Program (Accenture/Slalom/Hexaware), and ~$1B ARR run-rate trajectory signal strong market confidence (Market Leader viability); and SOC 2 Type II enterprise stack (SSO/SAML multi-provider, SCIM, SIEM audit logs, self-serve Enterprise to $200K ACV) is materially strong. However, pricing-volatility cap (6th restructure — June 18/July 1 2026 effort-based pricing reset the clock; cannot lift before ~July 2027; no default spending cap), reliability-complaints cap (25 incidents/90d just below downgrade trigger; Agent 4 off-rails/context-loss/loop-of-errors and launch bugs confirmed), cloud-only architecture (VPC isolation "coming soon", no FedRAMP, no self-hosted), and Trustpilot 3.3/5 with predatory-billing complaints prevent progress toward Adopted.
No status change recommended.
Movement triggers
Upgrade toward Adopted requires: (1) pricing model stable for 12+ consecutive months with no further restructuring (earliest ~July 2027, after the June 2026 6th restructure to effort-based pricing), (2) agent reliability improves with 90+ days of reduced incident frequency below 10/90d and community acknowledgment, (3) independent benchmark scores improve above 5/10, (4) spending caps or pre-approval controls ship to eliminate credit consumption surprises (no default spending cap as of May 2026), (5) FedRAMP, VPC isolation (currently "coming soon"), or self-hosted option launched for regulated industry access, (6) public deployment API or CLI for CI/CD integration enabling professional dev workflows. Downgrade to Watch if: incident frequency exceeds 25/90d sustained (currently 25/90d, just below trigger — one quarter above trips it), Trustpilot drops below 3.0 (currently 3.3), pricing complaints escalate causing measurable customer churn, production-safety incidents comparable to July 2025 DB incident recur, or enterprise customer loss signals emerge.
Risks & limitations
Reliability Complaints
ModerateRadar cap: reliability-complaints
Pricing Volatility
ModerateRadar cap: pricing-volatility
Integration surface
Not yet assessed — this section fills in as ACES research covers the tool.
Adoption & benchmarks
Not yet assessed — this section fills in as ACES research covers the tool.
Spotted something wrong or missing here? Suggest a change →
Per-source contributions
Click any dimension to see the underlying sources and citations.
More in this category