Tell the Forge what you need in plain language and it builds it — custom registers, fields, workflows, board and calendar views — with no code. It composes real building blocks, so what you create is a first-class part of the workspace, not a throwaway.
Every building has something the standard registers don't cover — a sustainability log, a key register with its own rules, a contractor onboarding checklist. The Forge lets you describe that need in plain language and have Orveya build it: the register, its fields, the workflow and the views to work it from.
Crucially, the Forge composes real building blocks — the same primitives the core registers are made of — rather than generating throwaway code. What you build is a first-class part of the workspace: it lives alongside Tickets, Properties and Assets, it's searchable, it works with Theo, and it behaves like software that was always there.
There's no code and no waiting on a developer. Describe it, review what the Forge proposes, refine it in plain language, and it's live for your team — a register that's exactly shaped to how your building actually runs.
No. It composes the same building blocks the core registers are made of — not throwaway code-gen — so what you create is solid, consistent and a first-class part of the workspace.
Yes. A Forge module lives alongside Tickets, Properties and Assets — fully searchable, wired into the rest of Orveya, and usable by Theo just like the built-in registers.
Yes. Add a field, adjust a workflow or change a view by describing it in plain language. There are no migrations to run and no code to touch.
Custom registers with their own fields, workflows and board or calendar views — things like a sustainability log, an EV-charger fault register or a contractor onboarding checklist.
Yes. Theo can query, draft and act on your custom modules exactly as it does the core ones, with no extra setup.