Guides
For IT and security leads whose staff build apps with Claude Code, and for the people building them.
How to
- A policy template for internal apps built with AI coding tools
- A one-page internal policy for apps staff build with Claude Code and similar tools. Covers ownership, hosting, access, data and secrets. Copy and adapt.
- Put a Streamlit app built with Claude Code behind Okta
- How to put Okta sign-in in front of a Streamlit app, using Streamlit's built-in OIDC login or a proxy, and what each approach leaves for IT to solve.
- When a Claude Artifact is not enough
- A shared Claude Artifact is a good home for many internal tools. Four signs an app built with Claude Code has outgrown one, and where it can run instead.
Comparisons
Each one links its sources and says when the other product is the better choice.
- Databricks Apps, next to intrium
- What Databricks Apps offers for hosting internal data apps, how its access and data permissions work, and where intrium is being built to differ. Sources linked.
- Superblocks, next to intrium
- Superblocks imports apps built with Claude and other AI tools and adds governance. What that means, and where intrium is being built to differ. Sources linked.
- Vercel for internal apps, next to intrium
- What Vercel offers for hosting internal apps built with Claude Code, how its sign-in and SSO work, and where intrium is being built to differ. Sources linked.