Migration snapshot
ActivePlatform
a Superblocks
DayZero Software Inc. (~50 employees) announced a $23M Series A on May 27, 2025 (Kleiner Perkins, Spark Capital, Greenoaks, Meritech Capital; total funding $60M per Business Wire). Repositioned as AI app-generation ('Clark'). Not acquired — the Banzai 'superblocks' acquisition (Nov 2025) refers to superblocks.xyz, an explicitly different company.
Typical timeline
6–10 weeks
Typical cost
$13K–$25K (agency, fixed)
Why teams leave a Superblocks
Superblocks is a safe platform bet for the next 18–24 months. Migration is differentiated here — Superblocks has a genuine React export path, so 'leaving' is closer to a graduation than a rescue. The triggers are control-plane dependency and pricing opacity at scale.
Proprietary control plane
The management/control plane lives in Superblocks Cloud — not on-prem. Even with the On-Premise Agent (OPA), the orchestration layer is cloud-dependent. Teams with strict on-prem compliance requirements (no outbound to Superblocks Cloud) cannot fully satisfy them with OPA alone.
SSO/audit gating at higher tiers
SSO, audit logs, and advanced RBAC are gated behind higher and Enterprise tiers. At team scale, cost escalates through a sales process with non-public Enterprise pricing.
React export — validate fidelity first
Superblocks advertises exporting apps as standard React apps via a GitHub Action (superblocksteam/export-action). This is a genuine differentiator, but export fidelity is vendor-claimed without extensive independent validation. Test the export on your actual application before planning a migration around it.
Clark AI lock-in risk
AI-generated app definitions (Clark, Superblocks' AI generator) may create tighter coupling to the Superblocks runtime than hand-built apps. Apps with heavy Clark usage may export with more runtime dependencies than simpler apps.
Enterprise pricing opacity
Like Retool, Enterprise-tier pricing is sales-gated and not publicly listed. Per-seat costs at scale are unknown until a sales conversation — making long-term cost modeling difficult.
What can you actually take with you?
Superblocks is the most code-portable option in the internal-tools category — run the export-action on your apps and assess fidelity before planning anything else.
| Asset | Can you export it? | How | Notes |
|---|---|---|---|
| Data | Yes | Superblocks connects to your own databases and APIs; no data is stored in the Superblocks platform itself | Integration secrets stored in Superblocks must be migrated to .env / Supabase Vault / Vercel env vars |
| Code | Partial | Superblocks advertises exporting apps as standard React apps; GitHub Action (superblocksteam/export-action) is available on GitHub, corroborating the vendor claim | Export fidelity is vendor-claimed — validate on YOUR app before committing to a migration plan; 'portability' is partly marketing |
| Design/UI | Partial | Exported as React components per the export-action output | Layout fidelity depends on export quality; test by rendering in a standalone Next.js project first |
| Logic/Workflows | Partial | Workflow and API call logic may export as React/JS through the export-action | Complex orchestration patterns and Clark AI-generated logic may not translate cleanly; audit export output |
| Users & Auth | Partial | SSO managed externally by your IdP — provider-side portable with redirect URL update | Password hash export not documented; SCIM user provisioning is not portable as-is |
| Integration Secrets | No | Secrets stored in Superblocks must be manually moved to new environment variable storage | Document all integration names and rotate secrets as part of migration — do not reuse secrets directly |
Swipe the table sideways to see the full breakdown.
Where each piece moves in code
The target stack is Next.js (App Router) + Supabase/PostgreSQL — using the React export as a starting point where fidelity is high, rebuilding where it is not.
a Superblocks
Superblocks Application
In code
Next.js app (App Router) with React components from export-action as starting point
Use exported React components as baseline if export fidelity is >80%; rebuild from screenshots if lower
a Superblocks
Superblocks API blocks (REST/GraphQL/DB queries)
In code
Next.js Route Handlers + Supabase queries via Drizzle
API block logic may appear in export as JS; move to server-side Route Handlers
a Superblocks
Superblocks On-Premise Agent (OPA, Docker)
In code
Eliminated — Next.js server-side runs within your VPC directly
Document what each OPA connection reaches; these become direct server-side connections
a Superblocks
Superblocks UI components (tables, forms)
In code
shadcn/ui + Radix UI; use exported React as a starting point or rebuild from spec
Even low-fidelity exports give structural hints for faster shadcn/ui rebuild
a Superblocks
Superblocks Workflows (scheduled, event-driven)
In code
Supabase Edge Functions or Vercel Cron
Document every scheduled workflow cadence before migration
a Superblocks
Superblocks RBAC
In code
Supabase RLS + role column; Next.js middleware for route guards
Map all role/permission combinations per page before cutover
a Superblocks
Superblocks SSO integration
In code
NextAuth v5 or Clerk (same SAML/OIDC provider, new redirect URL)
IdP config is provider-side portable; update redirect URLs at the identity provider
a Superblocks
Superblocks Clark (AI app generation)
In code
Custom AI SDK integration (Anthropic/OpenAI) via Next.js Route Handlers
Clark-generated logic may have runtime dependencies not captured in export; audit before assuming portability
The migration roadmap
Plan 6–10 weeks. The single most important early step is running the export-action and assessing output quality — this determines whether you're productionizing existing React code or rebuilding from a spec.
Export Validation
Week 1- Run superblocksteam/export-action on all your applications
- Test exported React components for render fidelity in a standalone Next.js project
- Score export quality: >80% render fidelity = productionization track; lower = rebuild track
- Document every integration/API block and the data source it connects to
- Identify all secrets stored in Superblocks; plan migration to environment variables
Watch out: Do not commit to a migration plan or timeline until you have assessed actual export fidelity — the export is the key decision input
Foundation Setup
Week 1–2- Scaffold Next.js (App Router) + Supabase project
- Move all integration secrets from Superblocks to .env / Vercel env vars (rotate if needed)
- Set up Supabase RLS schema mirroring Superblocks RBAC
- Document OPA connections — these become direct server-side connections
- List all scheduled workflows and their cadence
Component & Logic Integration
Week 2–6- For high-fidelity exports: adapt exported React components to Next.js App Router conventions
- For low-fidelity exports: rebuild pages with shadcn/ui using exported code as structural reference
- Implement API blocks as Next.js Route Handlers with Supabase queries
- Build auth guard middleware and RBAC from Supabase RLS policies
Watch out: Clark AI-generated components may have hidden Superblocks runtime dependencies not visible in the export; test each exported component in isolation
Workflow & OPA Migration
Week 4–8- Rebuild scheduled workflows as Supabase Edge Functions or Vercel Cron
- Eliminate OPA by implementing direct server-side database connections
- Verify data-sovereignty requirements are met by new VPC deployment if applicable
- Recreate SSO/SAML at identity provider with new redirect URLs
Parallel Run & Cutover
Week 8–10- Run Superblocks and new app in parallel; validate all data operations
- Update SSO redirect URLs at identity provider
- Rotate any secrets that were copied rather than regenerated
- Decommission Superblocks subscription after all teams confirm parity
Three ways to migrate — honestly
Every path has a real trade-off. Here is what each costs, how long it takes, and where it bites.
DIY (with AI tools)
$0–500 + your time
3–5 months part-time
Fits
Developers with React/Next.js experience whose export-action output showed high fidelity — productionization is closer to cleanup than rebuild
Risks
Low-fidelity export turns productionization into a rebuild without warning; Clark-generated logic may have runtime dependencies that fail silently in standalone React
Freelancer
$4K–10K
6–10 weeks
Fits
Apps where export fidelity is moderate (50–80%) and requires targeted rebuild of specific components; freelancer must understand Next.js App Router and Supabase RLS
Risks
Export fidelity assessment is the critical first step — a freelancer who skips it will underquote a rebuild; no fixed-price guarantee
Agency (RapidDev)
Done-for-you$13K–25K fixed price
6–10 weeks
Fits
Apps with complex OPA deployments, Clark AI logic, Enterprise SSO, or where export fidelity testing showed a full rebuild is needed — guaranteed parity and managed cutover
Risks
Highest upfront investment; model 12-month Superblocks Enterprise cost vs. migration cost before booking a free scoping call at rapidevelopers.com
The real risks — and how to defuse them
React export fidelity unknown
Mitigation: Export quality is vendor-claimed without extensive independent validation. Run the superblocksteam/export-action on your actual apps and test in a standalone Next.js project before making any migration plan. This is the first step, not a nice-to-have.
Control plane dependency in Clark output
Mitigation: Apps built with Clark's AI generation may have runtime dependencies on Superblocks' cloud orchestration layer that are not visible in the exported React code. Test each Clark-generated component in isolation before assuming it runs independently.
OPA ops continuity
Mitigation: Teams relying on OPA for data-never-leaves-network compliance must ensure the Next.js stack is deployed in the same VPC. Document every OPA connection before starting — these become direct server-side connections in the new stack.
SSO continuity
Mitigation: Enterprise SSO config must be recreated at the identity provider with new redirect URLs. Plan a parallel auth period where both platforms are accessible; do not cut over SSO until the new platform is fully validated.
Should you actually migrate?
Migrating is a real project. Sometimes staying is the right call — here is the honest split.
Stay if
- The $23M Series A funding and active roadmap make Superblocks a safe platform bet for the next 18–24 months — no shutdown risk to plan around
- The React export path provides meaningful optionality — you're not fully locked in, and can defer migration until the economics clearly favor it
- The OPA model meets your data-sovereignty compliance requirements more easily than a custom stack deployed in your VPC
Migrate if
- Control plane cloud dependency fails your on-prem compliance requirements even with OPA — the orchestration layer cannot be fully removed
- Per-seat Enterprise pricing has crossed the threshold where maintaining a Next.js stack is cheaper at your headcount
- React export validation showed low fidelity and you need to rebuild anyway — do it on your own infrastructure
Our honest verdict
Superblocks is the most code-portable option in this group. If you're considering leaving, run the export-action first — you may already have most of your React code and the migration is closer to a deployment project than a rebuild.
Do this today: pre-migration checklist
Whatever path you choose, protect yourself first. Work through this before you touch a line of code.
Run superblocksteam/export-action on all your applications and review output quality
Export fidelity determines your entire migration strategy — productionization vs. rebuild vs. stay
Test exported React components for render fidelity in a standalone Next.js project
Components that look correct in the export may have hidden Superblocks runtime dependencies that fail in isolation
Document every integration/API block and the data source it connects to
API blocks become Next.js Route Handlers; knowing the data source for each block is the prerequisite for rebuilding them
Identify all secrets stored in Superblocks and plan migration to environment variables
Secrets cannot be exported — they must be manually moved and rotated before cutover
List all scheduled workflows and their cadence
Scheduled workflows become Vercel Cron or Supabase Edge Functions; document before starting
Verify OPA deployment requirements if data-sovereignty constraints apply
OPA removal is a feature in the new stack, but compliance teams need to verify the replacement meets the same data-sovereignty requirements
Frequently asked questions
Can I export my Superblocks app as real React code?
Superblocks advertises exporting apps as standard React apps via the superblocksteam/export-action GitHub Action, and the action is publicly available on GitHub — corroborating the vendor claim. However, export fidelity is not independently validated at scale. Run the export on your actual application and test it in a standalone Next.js project before making any decisions.
What data can I take with me when leaving Superblocks?
All of it. Superblocks connects to your own databases and APIs — it stores no application data. Integration secrets stored in Superblocks must be manually migrated to .env / Vercel env vars and rotated. Your actual database data is already fully in systems you control.
How long does a Superblocks migration take?
Typically 6–10 weeks. If the React export-action produces high-fidelity output for your apps (>80% of components render correctly), the migration is a productionization project and can be done in 4–6 weeks. If export fidelity is low, it's a rebuild and takes 8–10 weeks. You cannot know which until you run the export.
What happens to my users and passwords when I migrate?
SSO users (SAML/OIDC) are managed by your identity provider — they migrate cleanly with redirect URL updates at the IdP. Password hash export is not documented for any built-in Superblocks users; plan a forced password reset for those users.
Is Superblocks shutting down?
No. Superblocks raised a $23M Series A in May 2025 (total $60M; Kleiner Perkins, Spark Capital, Greenoaks, Meritech Capital). The company is actively developing its platform including Clark AI app generation. Note: the Banzai acquisition of 'superblocks' in Nov 2025 refers to superblocks.xyz — an entirely different company explicitly disclaimed by DayZero Software.
What is the On-Premise Agent (OPA) and what happens to it after migration?
The OPA is a Docker-based agent that connects Superblocks Cloud to your internal data sources, enabling data to stay within your network while the orchestration layer runs in Superblocks Cloud. After migration, the OPA is eliminated — Next.js server-side code runs within your own VPC and connects directly to your databases, removing the cloud orchestration dependency entirely.
What is the hardest part of migrating from Superblocks?
Validating the React export-action output. If export fidelity is high, the migration is straightforward productionization. If Clark AI-generated components have hidden runtime dependencies that fail in standalone React, you're rebuilding more than expected. Testing the export on your actual app — not a demo — is the critical first step.
How much does a Superblocks migration cost, and can RapidDev help?
DIY with AI tools: $0–500 plus your time — most feasible when export fidelity is high. Freelancer: $4K–10K over 6–10 weeks. Fixed-price agency: $13K–25K over 6–10 weeks. RapidDev specializes in internal-tool migrations and can assess export fidelity and provide a fixed-price estimate — book a free scoping call at rapidevelopers.com before choosing an approach.
We migrate no-code apps to production code
- Fixed price — $13K–$25K (agency, fixed)
- No data loss, no downtime
- You own 100% of the code
30-min call. Quote within 48 hours.