Core

Your autonomous system in a managed cloud boundary.

Core is Cruuvo’s managed-cloud placement: dedicated identity, scoped capabilities, policy outside prompts, authorized actions, and exact evidence—without infrastructure for your team to administer.

Request access See pricing
Who this is for

Growing operators who need leverage now, not next quarter.

Managed execution

You want tailored autonomous systems turned on this week, not after a multi-month build.

No cloud admin

Your team should not be administering a GCP project, rotating service account keys, or paging on Cloud Run errors.

Standard data sensitivity

Your workflow data fits within typical SaaS boundaries. Highly regulated or on-prem-only data belongs on Private Edge.

What's included

Everything to run autonomous systems in production.

Tailored workflow library — intake, documents, operations, and finance categories ready to enable.
Cruuvo workspace — operator surface for enabling, monitoring, and tuning workflows.
Per-firm budget cap — monthly token ceiling, per-job ceiling, anomaly detection at 2× baseline.
Step-level audit log — STARTED and COMPLETED/FAILED for every workflow step, queryable from the Console.
Human-review checkpoints — configurable gates that pause workflow steps for approval.
Scoped capabilities — least-privilege access to your CRM, email, documents, storage, and internal tools.
Complete lifecycle — teach, compile, execute, evaluate, and improve from one workspace.
Email support — priority response during business hours.
Architecture

Cloud-native, serverless, and fully managed.

Core workflows run in NWA-managed Google Agent Engine. Each tenant gets an isolated runtime with its own secret scope, KMS key, and budget guardrails. The Cruuvo workspace is your operator surface — workflows are catalog entries you assign and enable per account.

Read the full architecture →

Operating model

What you operate. What we operate. What the system handles.

NWA does

  • Cloud infrastructure (GCP, Agent Engine, Cloud SQL)
  • Workflow design and updates
  • Per-tenant security and isolation
  • Platform observability and SLOs
  • Customer support

You do

  • Choose which workflows to enable
  • Connect your existing tools (CRM, email, docs)
  • Configure human-review gates and thresholds
  • Set per-firm budget caps
  • Review and approve outputs

The system handles

  • Step-level audit logging (every step, every call)
  • Budget preflight before every LLM call
  • Retries and backoff on transient errors
  • Per-tenant data isolation
  • Graceful degradation on budget exhaustion
Priced for the system you operate
Scope, customer-scoped capabilities, evaluation, usage, and ongoing operation are priced together.
Compare placements
FAQ

Common questions about Core.

How is Core priced?

Core pricing reflects system scope, customer-scoped capabilities, evaluation, usage, and ongoing operation. We define the run-rate before you commit.

Where is my data stored?

In NWA-managed Google Cloud Platform infrastructure (US region). Each tenant gets an isolated runtime with its own secret scope and KMS key.

When data, credentials, retrieval, or actions must remain local, use the Edge placement.

Do I need to administer GCP?

No. Core is fully NWA-managed. You do not have a GCP project, do not configure cloud resources, and do not handle service account keys. Everything runs through the Cruuvo workspace.

How long does setup take?

Core is operated by NW Agentic. We teach and validate the system against your environment, bind its capabilities, and release an immutable version into the managed boundary.

What happens if I exceed my budget?

Cruuvo stops before a model call or external effect when the declared budget would be exceeded. You receive an alert and can update policy from the workspace.

Can I export my system evidence?

Yes. Run evidence, evaluations, and account data are exportable. System versions remain explicit and traceable throughout their lifecycle.

See Core in action — 30 minutes, free.

We'll walk through the Console, the workflow library, and what deployment timeline fits your operations.

Request access