Skip to main content
RevoEngine brings application logic, data, integration, automation, identity, operations, and AI into one instance-scoped enterprise platform. Definitions are versioned and governed in the control plane; every execution uses those definitions under the current principal, ACL, policy, and quota. The platform can be approached as BaaS for application teams, an execution control plane for platform engineering, and an operational workspace for security and support. Those are views of the same application model—not separate products glued together.

​
Product surfaces

Older RevoEngine documentation used Resources and Schemas as top-level product concepts. Current documentation uses the concrete domains shown above. Database structures and endpoint input contracts remain explicit, but they are no longer presented as a generic Resources layer.

​
Typical end-to-end flow

  1. Establish identity, permission groups, service accounts, and resource ACLs.
  2. Model data in a database or connect to an external system.
  3. Author logic as a component, reusable library, or custom Node.js revision.
  4. Validate behavior in Sandbox and release a selected version.
  5. Publish through an Endpoint, Storage flow, automation trigger, or the Platform API.
  6. Observe logs, traces, activity, audit, job history, and execution results.
  7. Use the Assistant or an Agent to inspect, change, or operate the same governed resources within policy.

​
Choose the right entry point

Enterprise execution

Understand the BaaS control loop, SSO/IAM, evidence model, and governed AI.

Platform UI

Visual authoring, operations, governance, and AI workflows.

Platform API

Programmatic management of definitions and state.

Node.js SDK

Use the governed runtime from hosted or standalone Node.js.

CLI

Local component workflows, drift review, and environment promotion.
Last modified on September 5, 2026