intrium: host internal apps built with Claude Code, behind your SSO

The problem: AI-built apps with nowhere approved to run

One security scan found about 5,000 AI-built apps made for corporate use. About 2,000 of them held sensitive data with no authentication.

Source: Red Access research, reported by TechTarget, June 2026.

Claude Code is Anthropic's AI coding tool. With it, people who are not engineers can build a working internal app in an afternoon. Most companies have no approved place to run it.

When a shared Artifact stops being enough

A shared Claude Artifact is a good home for many small tools. Some apps outgrow it. That happens when the app:

needs its own server, such as Streamlit, Dash or an API
needs shared, read-only access to Snowflake or Postgres, so viewers connect nothing
has to sit in one catalog with every other app, with a named owner and a deploy log

intrium is where those apps go. The longer version is in When a Claude Artifact is not enough.

Where the data comes from

Plenty of useful apps run on a spreadsheet, not a warehouse. intrium takes data both ways.

Files you drop in: Spreadsheets, CSVs and exported reports go into a private bucket by drag and drop, upload or file transfer. Drop in a new version when the numbers change and the app reads the latest one. Earlier versions are kept, and IT can see every upload.
Your database or warehouse: Postgres or Snowflake, read-only, through a credential the builder never sees.

What IT gets: a catalog, access by group and an audit log

A catalog: Every app, with a named owner and a last-used date.
Access by group: Each app opens only to the Okta or Google groups you choose.
An audit log: A record of who deployed what, and when.
A scan on every deploy: Each deploy is checked for secrets and dependency problems.
Limited outbound traffic: Apps can reach only the connections you approve.
Free viewers: Pricing is per builder. People who only use the apps are free, however many there are.

Where to start

You build apps: Send IT the one-page brief. It says what intrium does, how credentials are handled and what setup takes. Or ask about a pilot that starts with files you drop in and needs no database connection.
You run IT or security: Ask for an exposed-app check. We look for AI-built apps tied to your company that anyone can reach without signing in, and send what we find to you alone, at no charge. The security page has the design and what does not exist yet.

Pricing

A flat fee for the people who build, with as many apps as they like. People who only use the apps are free on every tier, however many there are. Compute is charged only past the hours included.

Team

$300 a month

For: One department, or a pilot
Builders: 5
Apps: Unlimited
Compute hours: 3,000 a month, then $5 per 100
Data: Files you drop in, Postgres
Where it runs: Hosted by intrium on AWS

Business

$1,200 a month

For: Companies of 200 to 2,000 people
Builders: 25, then $40 a month each
Apps: Unlimited
Compute hours: 15,000 a month, then $5 per 100
Data: Files, Postgres, Snowflake, and databases on a private network
Where it runs: Hosted by intrium on AWS
Also: User provisioning, audit log export

Enterprise

$36,000 a year, and up

For: Regulated or large companies
Builders: By agreement
Apps: Unlimited
Compute hours: Not metered. You pay AWS directly.
Data: As Business
Where it runs: Your own AWS account
Also: Policy rules, an SLA, support through your security review

A compute hour: One app in use for one hour. Fifty people using one app for an hour is one hour.
How far the hours go: An app nobody opens uses none. One checked twice a day uses about 20 hours a month. One kept open through the working day uses about 200, so Business covers about 75 apps in daily use.
No surprises: IT sees the hours used in the catalog and gets an email at 80% of the month's allowance.
Forgotten apps: An app nobody has opened for 90 days is archived. Its owner is told first and can restore it.

Every tier includes sign-in by Okta or Google group, the catalog, the audit log and the scan on every deploy. Bandwidth and file storage are included, within fair use.

Planned prices. intrium is pre-launch and they may change before it is available. Enterprise, in your own AWS account, is planned and not built yet.

Common questions

Kinds of app: Web apps with their own backend, including long-running Python servers such as Streamlit and Dash. intrium runs the code as written.
Apps written with other tools: Code from Cursor or another coding agent deploys the same way. Claude Code rollouts are who we build for first.
Where it runs: Hosted by intrium on AWS to start, at a URL under your own domain. Running in your own AWS account is planned as the Enterprise option. AWS comes first, with Azure and Google Cloud later. Regions are not chosen yet.
Not in the first version: Write access to your database, viewers outside your company, and data sources other than Postgres, Snowflake and files.
Leaving: intrium runs your code as written. The app in your repository is the whole app, and you can take it elsewhere.
Next to what you have: We compare intrium with Vercel, Databricks Apps and Superblocks, and say where each is the better choice.
Security: The design, and what we have not done yet, is on the security page.

Your team is building apps with Claude Code. Where do they run?

You are on the list.