What Superblocks does with an AI-built app
Everything in this section comes from Superblocks’ own announcement of app imports, dated 27 May 2026. It is a vendor’s description of its product, as this page is of ours.
- Import from many tools. The post lists Claude, Replit, Lovable, v0, Bolt, Base44, Streamlit, Retool and custom code.
- The app arrives on the platform. You upload the app, and the post describes the result as “a production-ready app on the platform”. It says the interface and business logic come over intact.
- The platform may change it. The post says its Skills “may even improve it against your standards automatically”, including enforcing a design system and coding standards.
- Checks on import. Policy agents look for exposed API keys, vulnerable packages and supply chain risks.
- Governance. The post names audit logs, SSO, role-based access control and integration auth, and replacing personal API keys with token exchange or service accounts.
- Deployment in your network. The post says apps can ship “inside your VPC so data never leaves your network”.
Superblocks is an established product with these features available now. intrium is pre-launch.
Where the two differ
The right-hand column describes intrium as planned.
| Superblocks | intrium (planned) | |
|---|---|---|
| What happens to the app | Imported into the Superblocks platform, where it may be modified to meet your standards | Built from source and run as written |
| Where the builder keeps working | The announcement does not say | In their own repository, with Claude Code, then intrium deploy again |
| Checks | Policy agents on import | A scan for secrets and dependency problems on every deploy. The code is not rewritten. |
| Who can open an app | SSO and role-based access control | Members of an Okta or Google group that IT chooses |
| Where it runs | In your VPC, per the announcement | Hosted by intrium to start. Your own AWS account is planned as the Enterprise option. |
| Stage | Generally available | Pre-launch |
The difference that matters is the first row. One approach brings the app into a platform that then owns how it is built and changed. The other leaves the code where it was written and governs where it runs, who can open it and what data it can reach.
When Superblocks is the better choice
- You need something in production now. intrium is not available yet.
- You need the app inside your own network today. intrium is hosted by us to start.
- You want one platform where apps are both built and governed.
- You want standards such as a design system applied to apps automatically.
- You need a vendor that is already in production at other companies.
When to look for something else
- Your company has standardized on Claude Code and wants builders to keep working there.
- You want the deployed app to be the code in the repository, unchanged.
- You want to govern hosting, access and data without adopting another place to build.
That set of requirements is what intrium is being built for.