ČEZ
Energy
52,000 reports a day across CZ, SK and HU, in one system.
Describe the process. Forge builds it.
One conversation forges the whole process template: data, forms, workflow and publication. Edit anything by hand, any time.
- ČEZ
- Tesco
- T-Mobile
- Generali ČP
- NAKIT
A ready-made solution, not a construction kit.
Four parts that fit. Studio designs the process; the Platform runs it, with the Designer to model and the Portal to work; Plugins extend it; Forge AI sits underneath, governed.
- Forge Studio
- Describe the process; it plans, asks, then builds the template.
- Designer
- Model data, forms and the BPMN workflow; promote Dev to Production.
- Portal
- Where teams work: inbox, queues, SLA countdown, sticky Complete.
- Forge Plugins
- Screens that mount inside a Portal task. The core stays untouched.
- Forge AI
- Underneath it all: governed, grounded in the platform’s own element rules.
One conversation builds the whole template.
Data model, forms, BPMN workflow, version settings and publication, on one surface. Forge Studio plans first, asks before guessing, and builds where you can watch.
You watch it build. Every element it touches pulses teal, and you can take over any field at any time.
forge·studioNew templatePurchase-order approvaldraft v1
Describe the process.
I’ll forge it.
Describe a process or say what to change…
Checked like the Designer
The same validation rules as the Designer. It corrects its own errors, and a publish gate blocks templates that could not run. Publish to TEST, STAGE or PRODUCTION.
Hands on, any time
Edit any of the 96 Designer-parity fields directly, point at any element to reference it, rewind, or clone a version.
Where you need it
Runs standalone, inside the Designer, or as a <forge-studio> web component.
One product, two faces.
The Designer to model, the Portal to work. One ⌘K spotlight, one click between them, and a task inbox built for triage.
⌘K spotlight“Search or run a command…” from anywhere, in both faces.
Designer | PortalOne click between modelling and work.
Live SLA countdownEvery task shows the time left: here, 1 day 19 h.
Preview paneTriage from the queue. The task then opens as a focused layer with a sticky Complete.
Models real processes
Approval, recommending and task phases, e-signing, notifications, webhooks, integrations, custom scripts, timers, escalations and milestones, promoted from Dev to Test, Acceptance and Production.
Built for triage
Queues, filters and a preview pane. A task opens as a focused layer with a live SLA countdown and a sticky Complete; it works on a phone and prints as a document.
AI where you model
⌘J opens the assistant in the Designer: it plans, asks and builds on the live canvas, and Ctrl+Z undoes a whole generation.
Light and dark, first-classA full rebrand is one theme file.
⌘J assistantRenames a gateway on request, then offers to check the process.
Extend it without forking the core.
Zero Java per plugin, and the core stays untouched. Plugin screens mount inside the Portal’s task, in its theme, in Czech and English; the Portal keeps Complete.
import { definePlugin } from '@forge-plugins/server/define';
import { z } from 'zod';
export const plugin = definePlugin({
name: 'notes',
version: '0.1.0',
displayName: { cs: 'Poznámky', en: 'Notes' },
screens: { main: { title: { cs: 'Poznámky', en: 'Notes' } } },
state: {
schema: z.looseObject({ note: z.string().max(2000).optional() }),
maxBytes: 16_384,
},
ops: {
saveNote: {
privileges: ['TASKS'],
task: true,
effects: true,
timeoutMs: 5_000,
input: z.object({ note: z.string().max(2000) }),
},
},
});- One front door
- Browsers talk only to the platform service. Plugins live on the internal network: no CORS, no login, no route back.
- Every call is signed
- Ed25519, scoped to the user, the task and the intersected privileges, valid for 60 seconds.
- No access to your database
- Plugin data is one versioned JSON document, kept and validated by the platform.
- Looks native
- Screens mount inside the Portal’s task, in its theme and language. The Portal keeps Complete.
For developers
bun forge new <name>- Scaffolds a typed plugin: server, React screens, fixtures and a Playwright test.
bun forge dev <name>- Mounts it exactly the way the Portal does.
bun forge doctor- The CI gate.
An AI that knows the platform, and its limits.
Forge AI grounds Studio and the ⌘J assistant in the platform’s own element rules. Some elements it places alone, some it leaves for a human, some it never touches.
- Your credentials never reach the AI
- A broker authenticates; the AI reads back through a narrow, audited gateway.
- Your choice of model provider
- OpenAI GPT‑5.x or Anthropic Claude. Switch without re-platforming.
- Runs next to your platform
- Its database, memory, queues and credentials are its own.
- Governed and observable
- A role-based operator console, with usage attributed per user and per feature.
You
“Add an escalation to HR if the manager does not decide within 3 days.”
Forge Studio
There is no role ‘HR’ in this workspace — only ADMIN and DESIGNER. Which role should I use?
No deck-ware — a working platform.
Tesco
Retail
Financial processes at till scale: 30,000 reports a day.
T-Mobile
Telco
The HR agenda, with integrated e-signature.
Generali ČP
Insurance
Central BPM for 6 insurance lines and 167 processes.
Also in production at NAKIT and FN Motol.
See what each of them runsTell us the process that's costing you.
Bring one real process to the demo. We describe it to Studio together and you watch it take shape on a working platform — not on slides.