Developers

Korporus Developer Platform

Everything technical lives here: runtime composition, manifest contracts, slot boundaries, and deployment topology.

Getting StartedDocumentation Demo

Architecture at a glance

The shell host discovers manifests, loads remotes over Module Federation runtime, and mounts slot components.

Korporus is built around strict runtime boundaries. Hosts own shell UX and loading behavior. Remotes own app logic and state.

Runtime flow
manifest discovery -> schema validation -> remote registration -> bootstrap import -> slot mount

Technical Design Philosophy

The technical principles behind Korporus are explicit, inspectable, and operationally predictable.

Runtime contracts first

Integration is defined by stable contracts: manifests, schema validation, slot tags, and deterministic loading flow.

Federation boundaries by design

Hosts own orchestration and shell UX. Remotes own application logic. Module Federation keeps delivery decoupled at runtime.

Manifest guarantees

Every remote identity, entrypoint, and slot surface is declared through a strict manifest schema before becoming runnable.

Operational separation

App Runner runtime services and Amplify host surfaces can evolve independently, reducing coupling across deployment tiers.

Security and sandbox assumptions

Agent procedures run in isolated execution environments with explicit secret boundaries, keeping credentials outside agent containers wherever possible.

Procedure Studio

A first-class Korporus environment for developing agent procedures with strong safety and evaluation primitives.

Domain-specific language + runtime for async agent programs

Korporus provides a first-class development experience: an IDE with agent-assisted workflows for authoring Lua-based high-level DSL procedures that automate business processes and other long-running agent tasks.

The runtime is designed for hybrid AI/ML + programmatic procedures, including context-engineering controls and built-in task-level evaluation semantics so procedures can measure success against high-level goals.

Security is explicit. Procedures can run in isolated sandboxes (for example e2b or simple containers) while a zero-knowledge broker keeps API keys and service credentials outside agent containers to reduce exfiltration risk from prompt-injection or supply-chain compromise.

Developer Features

Technical capabilities for teams building and operating independent frontend modules.

SHELLREMOTE AREMOTE BREMOTE C
Shell Host

Shell Host Runtime

An OS-like host discovers app manifests and mounts slot components at runtime.
Feature Detail Docs
SHELLREMOTE AREMOTE BREMOTE C
Runtime Composition

Module Federation Composition

Remote bootstraps load over HTTP without build-time coupling to the host.
Feature Detail Docs
SHELLREMOTE AREMOTE BREMOTE C
Manifest Discovery

Manifest Contract

A strict manifest schema defines app identity, remote entry, and slot element names.
Feature Detail Docs
SHELLREMOTE AREMOTE BREMOTE C
Slot Contract

Web Component Slots

Titlebar, main, and settings custom elements provide a framework-agnostic mount boundary.
Feature Detail Docs

Cross-Framework Hosts

The same remote app renders in shell, React host, and Angular host implementations.
Feature Detail Docs
SHELLREMOTE AREMOTE BREMOTE C
Shared State

Shared State Model

Slot components synchronize through lightweight app-level state stores.
Feature Detail Docs

Integration Surfaces

Editor-like shells and external containers can adopt the same manifest and slot contract.
Feature Detail Docs

Docs Pipeline

Repository markdown is mapped into website docs routes for publishable technical documentation.
Feature Detail Docs

Procedure Runtime

Build and evaluate programmable procedures with agent-assisted IDE workflows, DSL semantics, and secure execution boundaries.
Feature Detail Docs

Deployment Topology

Amplify Gen2 hosts and App Runner runtime services are separated for independent rollout.
Feature Detail Docs

Developer paths

Choose where you want to go next.

Build Your First App

Follow the getting-started and guides tracks for manifests, slots, and styling.
Start guide →

Reference Contracts

Read API and schema details before integrating new hosts or remotes.
Open reference →

Deployment Model

Plan delivery across Amplify Gen2 hosts and runtime service boundaries.
View deployment guide →