Product overview
Before creating your first project, it helps to understand how RuleForge organizes things. There are four core concepts: organization, project, workspace, and version.
Core concepts
Organization
Your company's space inside RuleForge. It's the top level — an organization holds members, projects, integrations (Git, webhooks), identity settings, and the contracted plan.
If you belong to multiple companies (consultants, for example), you can be part of multiple organizations and switch as needed.
Project
Where work happens. A project gathers:
- rules and decoders;
- test cases;
- workspaces (drafts);
- reviews;
- versions;
- audit history.
An organization can have many projects. It's common to separate them by team, by monitored product, or by environment.
Workspace
A personal draft. It preserves your editor state without turning it into a formal version yet. Use workspaces to experiment, iterate, or pick something up later.
Review
When content leaves draft mode and you want approval before publishing, open a review. Another teammate evaluates, comments, requests changes, or approves — everything recorded.
Version
The official snapshot of a project, ready for publishing. Versions have history, pass through quality criteria, and can be compared.
Typical flow
- Create a project.
- Write or import rules and decoders in the editor.
- Validate the content.
- Test with real events.
- Save successful scenarios as regression cases.
- Save a workspace to park the draft.
- Open a review when you want approval.
- Create a version and publish.
Each step can be repeated. The flow works for a solo author and for a team collaborating.
Plans
RuleForge has different plans for different needs:
- Free — editor, validation, manual log test, cases, and workspaces.
- Pro — adds versions and API access.
- Team — adds reviews, quality criteria, and integrations.
- Enterprise — adds SSO, automatic provisioning, and private deployment.
Details on Billing and plans.