co.dev

Enterprise procurement / compliance-driven environments

• If an organization requires SOC 2 Type II, ISO 27001, or similar evidence before pilot, the lack of public documentation is a blocker.

Any workflow where third-party integration mistakes are catastrophic

• Avoid running the product against production databases with elevated permissions; integration behavior should be validated in isolated test projects. Community reports indicate the potential for severe consequences in some cases.

Highly regulated data or strict data residency requirements

• Absent clear public documentation on hosting and data handling, regulated workloads are high risk.

Teams wanting predictable costs at scale

• If model usage is pay-as-you-go and workflows are iteration-heavy, monthly costs may be difficult to forecast.

Complex, non-standard architectures

• Multi-service microservice architectures, advanced observability, and bespoke infrastructure needs are better served by conventional engineering stacks or cloud IDEs/agents combined with experienced engineering resources.

Current limitations acknowledged by the vendor

• No explicit limitations page was identified; the presence of migration guidance indicates an expected path from prototype to standard engineering hosting.

Features on the roadmap (not yet available)

• Blog posts indicate ongoing feature development (e.g., version forking, UI redesigns, model support updates) but do not provide a dated roadmap.

Scale limitations

• No public documentation on scale limits was identified in the sources reviewed.

Security or compliance gaps

• No public SOC 2 / ISO documentation or trust center artifacts were identified in the sources reviewed.

API limitations or integration constraints

• Not publicly documented; the reported Supabase incident highlights integration behavior as a potential high-risk area and suggests that precise permission scopes and automation behaviors should be confirmed in testing.

unique selling points supported by product materials

• Plus tier includes unlimited private projects, unlimited custom domains, code download, and GitHub integration.
• The vendor publishes migration guidance (for example, migrating a repository to a conventional host), which reduces platform lock-in risk in practice by enabling export and continuation of work outside the platform.

Differentiation validated by customer feedback (limited)

• Public user feedback is limited in sample size; Product Hunt and community mentions provide some validation of the code-export and Supabase integration story but do not constitute robust evidence.

Areas where competitors have advantages

• Larger competitors or adjacent tools may provide broader enterprise trust artifacts, deeper ecosystem integration, or greater mindshare in the developer community.

Availability of mainstream review-platform coverage

• Major enterprise review platforms (Gartner Peer Insights, G2, TrustRadius, Capterra) did not show a discoverable product listing or significant review coverage during this research run.

Product launch / community review signals

• Product Hunt listing shows a limited number of reviews and mixed feedback. Sample sizes are small and subject to selection bias.
• Community posts include allegations similar to the community report referenced elsewhere; these are anecdotal and should be independently validated.

Community / social feedback — representative themes

• Negative / high-severity: Community reports include an allegation that connecting to Supabase deleted data. These reports are anecdotal and not independently verified but are operationally relevant.
• Positive / mixed: Some community members report success using the product for prototyping and iteration; such comments are lightweight endorsements without quantified outcomes.

Why customers chose this product over alternatives (inferred)

• Code export and GitHub integration appear to be differentiators for users concerned about platform lock-in.
• Supabase integration is frequently cited as part of the full-stack provisioning workflow.

Why some customers left for competitors (churn drivers, inferred)

• Potential churn drivers include trust concerns following integration-related incidents, perceived support accessibility issues, and preference for more established platforms in the category.

Specific outcomes customers achieved (with metrics when available)

• No public, quantified case-study metrics were identified in the sources reviewed.

Deal-breakers and reasons prospective buyers did not purchase

• Key concerns for cautious buyers include lack of public enterprise security/compliance documentation, community reports of destructive behavior with Supabase integration, and unclear support channels.