Introduction
intrnl.cloud is a governed internal-application platform where employees can create software with AI while their organization retains control over identity, data, security, deployment, and ownership.
The platform is designed for organizations whose app creators may be employees, administrators, or departmental workflow owners without a development background.
The v1 experience should allow that person to:
- Sign in through their organization’s Microsoft Entra ID.
- Create an application without Git, SSH, local tooling, or infrastructure knowledge.
- Use an approved Claude, ChatGPT, or Codex account to describe and modify the application.
- Review a protected preview populated with synthetic data.
- Request production deployment.
- Have intrnl enforce the organization’s approval, access, network, and security policies.
- Preserve the application as an organization-owned, versioned, maintainable software project.
Developers retain the ability to inspect code, use Git, connect an external repository, or take over an AI-created application without rebuilding it elsewhere.
The product is therefore not merely a hosting dashboard and not merely an AI code generator. It is an internal software governance and runtime platform.
How to use these docs
- Creators and business owners: start with the pilot workflow, governance, and AI change sets.
- Platform engineers: follow the architecture, runtime contract, and implementation plan.
- Security administrators: review identity, access policies, threats, and audit.
- Operators: use the operating model and the deployment, restore, upgrade, rotation, and incident runbooks.
Reading the baseline
Locked decisions are design constraints, not evidence of implementation. Phase 0 gates are open engineering choices. Pilot defaults are proposed, configurable values. SDK calls, manifests, endpoints, compatibility dates, and domains describe intended contracts; they are not released interfaces or deployment instructions.
This repository contains the documentation site. The platform monorepo layout describes a separate proposed codebase. The plan coverage index maps every original section to its documentation.