SAML, OIDC & SCIM
Authenticate against Okta, Entra ID, or Ping with automatic role mapping and scoped SHA-256 API keys.
samlStrategy({ idpMetadataUrl })For CIOs · CISOs · Platform Engineering · Low-Code CoE
Turn shadow AI apps into governed enterprise software.
69% of enterprises detect unvetted AI-generated apps running outside IT. Standardize internal builders on a declarative TypeScript + Postgres framework with free SAML SSO, row-level RBAC, audit logs, and full VPC control.
✓Free SAML & OIDC in MIT✓Row-Level RBAC✓Self-Host or Private VPC✓Unlimited Fleet License
// SHADOW AI GOVERNANCEFROGBOT ARCHITECTURE
Don’t block internal builders. Govern the runtime.
When business teams prompt raw coding agents from scratch, they ship 15,000 lines of unvetted auth and exposed tables. FrogBot restricts AI agents to a 68-line declarative config where security, SSO, and access control are enforced by the engine.
68 lines
Auditable in 2 minutes.
InfoSec reviews one declarative frogbot.config.ts, not 15,000 lines of generated glue.
SAML + SCIM
Zero SSO tax.
Okta, Microsoft Entra ID, and Google Workspace SSO ship in the open-source core.
VPC / Docker
Runs on your metal.
Deploy on your AWS/Azure/GCP Kubernetes cluster, dedicated Dojo cloud, or hybrid Local Runner.
Vibe-Coding Security Audit (2026)CVE Reality
~60% of scanned raw vibe-coded internal apps ship with critical auth flaws or missing row-level security.
FrogBot Access EngineDefault Closed
Collections are closed by default; REST, Local API, and AI Agents enforce the exact same row-level RBAC.
Enterprise Security & Governance
Every control InfoSec asks for—built into the framework.
Six architectural guarantees enforced across every FrogBot application:
Row-Level RBAC
Access functions execute on every read, write, and AI tool call—agents can never read rows the user cannot see.
access: { read: isDepartmentMember }Model Allowlists & Caps
Restrict approved LLM providers, enforce per-user monthly USD budgets, and route via your corporate AWS Bedrock or Vertex keys.
aiPolicyPlugin({ monthlyBudget: 50 })Immutable Audit Logs
Track every document mutation, login, permission change, and agent tool invocation with full version history.
versions: { drafts: true }, trash: trueOutbound Local Runner
Reach on-prem SQL databases and internal VPC services over an authenticated outbound TLS tunnel with zero open inbound ports.
npx frogbot runner start --outboundZero Vendor Lock-In
Standard Next.js, TypeScript, and Postgres 16. Run 100% self-hosted in Docker or under a flat Dojo Enterprise fleet license.
docker compose up -dFrogBot Enterprise vs. legacy low-code and unvetted AI builds.
| Governance Dimension | FrogBot Enterprise | Retool / Appsmith Enterprise | Power Platform | Raw Vibe-Coded Apps |
|---|---|---|---|---|
| Licensing model | Flat fleet (unlimited apps/users) | $30k–$67k/yr + per-seat tiers | $20/user/mo + $150/bot/mo | Unmonitored P-card sprawl |
| Code & schema ownership | ✓ Standard Git + Postgres | ✕ Proprietary JSON / runtime | ✕ Dataverse lock-in | ✓ (15k lines of unvetted glue) |
| SAML / OIDC SSO included in OSS | ✓ Yes (MIT) | ✕ Enterprise paywall | Requires M365 licensing | ✕ Custom per app |
| AI agents obey row-level RBAC | ✓ Enforced in core | Bolt-on webhooks | Separate Copilot studio | ✕ Frequent data leaks |
| Self-hosted VPC / air-gapped Docker | ✓ First-class | ✓ ($30k+ floor) | ✕ Azure cloud only | DIY DevOps per app |
Enterprise fleet licenses include the Visual Editor and Flows plugins, SCIM provisioning, custom SLAs, and annual PO/Net-30 invoicing.
FAQs
Why is SAML and OIDC SSO free in the MIT open-source framework?
Security is a baseline requirement, not a luxury add-on. Gating SSO behind a $30,000 paywall forces teams to create shadow passwords; shipping it in MIT lets every internal app start on Okta from day one.
How does Enterprise Fleet licensing work compared to per-app or per-seat pricing?
One predictable annual contract covers unlimited internal apps and unlimited seats. Central IT gets a single PO with Net-30 invoicing instead of chasing departmental credit cards or counting end-user logins.
Can we deploy FrogBot entirely inside our own AWS, Azure, or GCP VPC?
Yes. FrogBot is a standard Node.js + Postgres application that deploys via Docker, ECS, or Kubernetes inside your own cloud account—or on dedicated single-tenant Dojo infrastructure.
How do you prevent AI agents from leaking sensitive rows or racking up token bills?
Agents run inside the user’s session permissions and @frogbotai/plugin-ai-policy. Every agent query passes through your collection access rules, and admins set allowed model lists and hard monthly dollar caps per user.
What happens when an internal builder’s $29 Dojo app grows to 200 users?
You adopt it without rewriting a line of code. Transfer the app into your corporate Dojo workspace or pull the Git repository and Postgres dump directly into your internal platform.
Standardize internal AI apps across your organization
Schedule an architecture review or spin up a 30-day VPC proof of concept with our engineering team.