01 — Workforce

Build your AI workforce.

Not a chatbot window. A company of agents with names, jobs, and a place they actually work.

The sceneScattered points drift apart in the dark: individual workers with nothing holding them together yet. Over the next eight scenes they gather into a company. Korps is the platform that does the gathering.

02 — Create

Create an agent.

Give them a role, a title, a face. They are employees, not tabs.

The sceneOne figure resolves out of the drifting points and holds still. Creating an agent takes a name, a job title and a short description of what it should do. Korps handles the rest: profile, runtime, connection and health check.

03 — Work

Agents actually working.

Tools, terminals, long jobs. You see the work, not a spinner pretending to think.

The sceneA terminal opens beside the figure and fills with output. Where Korps shows a state today, it reads it from the control plane and writes it in words as well as colour, so a status is never a guess. Live per-agent work status is still being built: today the workspace shows whether a server is connected, not what an agent is doing second by second.

04 — Team

One agent becomes a team.

Specialists, a lead, a shared board. The roster follows the account, not the machine.

The sceneFive figures leave the drift and take seats in a ring around the first one. A team has a lead who sequences the work, contributors who own tasks, and a reviewer who checks the result before anything is called done.

05 — Models

Many models, one Korps.

OpenAI, Anthropic, xAI, Gemini, DeepSeek, or your own keys. Korps routes. You stay in charge.

The sceneSpokes reach out from a centre marked Korps to five labelled points: OpenAI, Anthropic, xAI, Gemini and DeepSeek. Each agent is assigned its own model connection, so one team can mix providers, and the assignment is still there when you come back. Your API key is not: it stays on your own server, and Korps records only which provider an agent uses. Korps does not make the model call itself yet, so the routing happens on your runtime.

06 — Room

Real group collaboration.

A room of coworkers, not a round-robin of bots. People interrupt. Agents can stay quiet.

The sceneThe ring holds and the figures stay seated together in one room. The design Korps is built toward: everyone authorised for the room shares one history, only the agent who owns the next step runs it, your message commits straight away even while the room is busy, and Stop really stops the work. Group rooms are not in the web app yet. What exists today is the account, workspace, server and agent layer underneath them.

07 — Runtime

Your VPS is a runtime.

Connect a box. Replace it. The workforce does not live in the SSH key.

The sceneA wireframe box draws itself around the team: the server the agents run on. You get a one-time claim code from the browser and run a single command on the machine to attach it, and Korps shows you each step as it happens, including the ones that fail. Korps cannot provision a server for you yet, so that one command is the only place you still need a terminal. Agent identity, memory and history live in the control plane, so replacing the box does not cost you the workforce.

08 — Continuity

Desktop and mobile, same Korps.

Sign in. The workspace hydrates. Laptop or Android, same agents, same teams.

The sceneTwo outlines appear side by side, one desktop and one phone, both showing the same workspace. Leave and come back and the account, workspace, runtimes and agents are the state you left, not a fresh session.

09 — Begin

Build your Korps.

Create an account. Your workspace stays with you when you leave and come back.

The sceneThe scattered points from the first scene have closed into a single ring with KORPS at its centre. Signing up takes an email and a password. No terminal, no SSH and no install to read the rest of this page.