Describe how your team works. Vrux builds the workspace, configures the statuses, rules and approvals, and helps execute the work with AI agents — inside the permissions you set.
Free workspace · no credit card required
Product preview with sample data. The walkthrough below shows the flow step by step.
One workspace for the process, the record and the agent
This is the loop Vrux is built for: describe the process, review the generated structure, then execute the work with people and agents.
Illustrative walkthrough using sample data — not a live workspace.
Stages, request types, approval rules and the words your team uses — described the way you would explain them to a colleague.
No schema editor required to start.
Vrux-AI reads the current setup, generates or selects a template, validates references and previews the result before applying it.
Configuration changes require a workspace admin. Updates merge by key; nothing is silently wiped.
@vrux-ai create an access request for the production dashboard.
Created #AC-142 and routed it to the platform manager. I can't move it past the approval gate; the decision has to come from the platform manager.
Agents act through server-enforced tool calls. Roles, policies and approval gates apply to them exactly as they do to people.
Transitions and approval decisions are written to the activity log; each agent run leaves a receipt.
For operations teams, the work is rarely the hard part. The handoffs, approvals and record-keeping around it are.
Statuses, work-item types, fields, permissions and automations have to be assembled before the team can run the process. Many teams give up and use a generic board instead.
The tracker records the work, but the decision lives in a chat thread or an email. The record is reconstructed later, if it is reconstructed at all.
An assistant can draft text. It cannot safely change a status model, route a request through an approval gate or leave a durable record of what it did.
Vrux is designed around a shared workspace that AI can both configure and operate.
Explain the stages, request types, owners and approval points in chat. Or start from one of eight starter templates and adapt it.
Vrux-AI generates the statuses, work-item types, transitions and rules, validates the references and shows you the result. You can edit it in the workspace or ask for a change in chat.
People work the board. Agents create and update records, write documents, run reports and move work — but only inside the roles, policies and approvals you configured.
See the complete capability map for what is implemented today.
A representative operations workflow, not a customer case study.
We will only publish outcomes after they are measured with a real customer. We are not claiming time savings or ROI today.
The difference is not a better chat box. It is a shared application model that both people and agents can use safely.
It reads the current setup and can create or update statuses, work-item types, phases and transitions — with a preview and an admin permission boundary.
Role restrictions, RCA requirements, conditions and approvals are evaluated on every transition. The model is not the authority.
More than 100 tool-backed actions across work items, documents, meetings, chat, reporting and settings. Each call is permission-checked and attributable.
| A generic AI assistant | Vrux |
|---|---|
| Answers questions and drafts text. | Answers, then executes structured actions in the workspace. |
| Has no model of your workflow. | Configures statuses, work-item types, transitions and rules. |
| Cannot enforce a role or an approval. | Server-enforced roles, agent policies and approval gates. |
| Leaves a transcript. | Leaves an activity log, approval decisions and agent receipts. |
This compares categories, not named products. Vrux is not a drop-in replacement for every Jira, ClickUp or Notion workflow today. It starts from a different place: the process is the configuration, and the agent operates inside it.
The core workspace, agent tools and governance layer are built. We are now looking for a small number of teams to validate which operations workflow to own first.
starter templates, plus generated templates
tool-backed agent actions
workflow rule types: role, RCA, condition, approval
workspace roles, plus agent policy controls
These are product capabilities, not customer metrics. Vrux is pre-seed.
We will tell you honestly whether Vrux is a fit, and what we would need to build to make it work.
Vrux is deliberately broader than a workflow builder. The process needs work items, knowledge, conversation and reporting in the same place.
Boards, phases, epics, stories, tickets, milestones and deliverables. Software workspaces add sprints, Gantt and releases.
Configurable statuses, transitions, role restrictions, RCA, approval gates and workflow lock — enforced by the server.
Collaborative documents, a nested knowledge base, version history, spreadsheets, slide decks and a media library.
Channels, DMs, threads, mentions and announcements. Every work item is a live, clickable link.
A resident agent with grounded retrieval, report generation and more than 100 tool-backed actions, governed by roles and policy.
Dashboards, workload, activity feed, automations, signed webhooks, a REST API, CSV import, Slack and GitHub event ingress.
Availability of individual integrations depends on deployment configuration. See the full capability map.
These are implemented controls, not certifications. We will be explicit about what we have and have not verified.
Keycloak OIDC authentication. Platform administration is separate from workspace membership.
PostgreSQL row-level security and tenant-scoped queries. Isolation is enforced below the application layer.
Seven workspace roles, enforced by the server. Agent calls are checked against the delegating user's role and policy.
A transition can create a pending approval. The server blocks the move until a decision is recorded.
Activity log, transition history, approval decisions, RCA history and agent run receipts.
Docker and Kubernetes deployment. Self-hosted or VPC deployment is available on the Custom plan.
Vrux has not completed SOC 2, ISO 27001 or a third-party penetration test. We do not claim those certifications today. We can document the controls in place for a specific pilot on request.
Every plan includes the core workspace. Plans differ by workspaces, members and daily agent runs.
For evaluating Vrux on one workflow.
For a small team running one or two processes.
For several teams and heavier agent usage.
Prices are in USD. Annual billing is available. AI usage is metered by runs and credits; top-ups are available. See full pricing.
Need SSO configuration, dedicated infrastructure or custom terms? Talk to us about the Custom plan.
An AI-native workspace. You describe a process; Vrux generates the statuses, work-item types, transitions and approval rules, and people and AI agents execute work inside them.
Our initial focus is operations teams running recurring processes with handoffs and approvals — for example access requests, incident reviews or vendor onboarding. Software teams can use the same workspace, including sprints, Gantt and releases.
The agent reads the current setup, generates or selects a template, validates entity references and previews the result. Applying changes requires a workspace admin. Updates merge by key; destructive reconfiguration is a separate action.
More than 100 tool-backed actions: create and update work items, write documents, spreadsheets and slide decks, schedule meetings, post in chat, read reports and configure boards. Each call is checked against the delegating user's permissions and the workspace policy.
Yes. Generated changes are previewed before they are applied, and you can edit statuses, work-item types, transitions and rules in the workspace or in chat. The structure is not locked in.
By the server, not the model. Workspace roles and workflow rules are evaluated on every transition. Agent policies can deny a tool, require a minimum role or require human approval. An approval gate blocks the transition until a decision is recorded.
Not as a drop-in replacement today. Vrux starts from the process rather than a fixed project model. CSV import covers task exports, but we do not claim feature parity with every tool.
The codebase includes Slack, GitHub event ingress, MCP transport, signed webhooks and a REST API. Availability depends on deployment configuration. Tell us which integration your pilot needs before relying on it.
Yes. Start a free workspace, or apply for a design-partner pilot if you want us to configure it with you.
Plans differ by workspaces, members and daily agent runs. AI usage also consumes credits, and top-ups are available. Current list prices are on the pricing page.
Vrux uses Keycloak OIDC, tenant-scoped PostgreSQL row-level security, encrypted integration secrets, signed webhooks and activity/audit records. It ships as Docker/Kubernetes and can be deployed self-hosted or in a VPC. No SOC 2, ISO 27001 or third-party penetration test is claimed.
Start free, or tell us about the process you want to run. We will configure a design-partner workspace with you.