← All products

Universal agent harness platform · Preview

Build the harness.
Choose the agents.
Deploy anywhere.

CoreHarness turns groups of AI agents, tools, workflows, identities, policies, and infrastructure into installable systems that can work, communicate, wait, resume, and evolve.

Platform previewProvider-neutralCustomer-controlled boundaries

What is an agent harness?

More than an agent.
A complete operating environment.

An agent harness is a deployable application and operating environment. It coordinates one or more agents, gives them identities and capabilities, manages durable state and lifecycle, connects tools and services, and governs consequential actions.

It can model a company, a research team, a personal advisory group, a technical workflow—or an operating model nobody has built before. The platform automates work, not accountability.

From conversation to deployment

Describe the system.
Inspect what it becomes.

Planned · Studio
YOU

“Create a software delivery harness with planning, coding, review, and testing agents. Require approval before production changes.”

COREHARNESS STUDIO
  • Roles, personas, relationships, avatars, voices, and styles
  • Models, tools, skills, MCP servers, and data access
  • Workflows, events, approvals, memory, and durable state
  • Deployment, security boundaries, installation, and teardown

Studio is planned. Today, manifests, validation, packaging, installation, and lifecycle APIs are implemented in the platform preview.

Multiple operating models

Place each part where it belongs.

Security, sovereignty, integration, performance, and operations determine placement. No single topology is mandatory.

Planned service

CoreVar Managed

Begin without owning a cloud or productivity tenant. Securely isolated shared and dedicated options are part of the service direction.

Preview

Customer Cloud

Provider adapters and foundations exist for Azure, AWS, and Google Cloud. Credentialed deployment validation and Marketplace certification remain release gates.

Planned service

Dedicated Managed

A dedicated environment operated by CoreVar, preserving isolation without transferring day-to-day operations to the customer.

Platform direction

Hybrid

Keep coordination or commerce managed while sensitive execution, connectors, data access, and workloads remain inside the customer boundary.

Optional integrations

Use an office suite—or don’t.

CoreHarness identities and policies exist independently of Microsoft 365, Google Workspace, or another collaboration provider.

Preview

Microsoft 365 integration

Admin consent, scoped capability brokering, subscription lifecycle, and governed communications are implemented. Live tenant validation remains authorization-gated.

Planned

Google Workspace and other suites

Connect existing or newly provisioned services where supported—or use no external productivity suite. Access remains explicit, scoped, audited, and policy-controlled.

Native communications

One place to work with persistent agents.

Planned experience
PeopleWeb · Mobile
Conversation backplaneDurable messages · events · handoffs
Agent groupsVoice · video · artifacts

The durable conversation domain is taking shape in preview. Native audio, video, screen presentation, stable avatars and voices, group meetings, and the CoreHarness mobile experience remain planned.

Event-driven by design

Work when needed.
Wait without wasting compute.

Preview
  1. 01
    Activate

    A message, schedule, callback, approval, or dependent result makes work ready.

  2. 02
    Execute

    Lease a bounded worker, container, VM, or desktop only for the required capabilities.

  3. 03
    Checkpoint

    Persist workflow state and release temporary infrastructure while the harness waits.

  4. 04
    Resume

    Continue when the next governed signal arrives.

Governed execution

Intent is not the same as execution.

Preview
01

Request

An agent proposes an email, call, infrastructure change, data operation, or computer action with its purpose and boundaries.

02

Evaluate

Role, capability lease, policy, scope, budget, and human-approval requirements are checked.

03

Execute—or hold

The harness reports an accurate state: pending approval, approved, rejected, executed, or failed.

Preview

Supervised cloud computers

Authorized agents can lease isolated Azure container, VM, or desktop workspaces for bounded tasks. The implementation includes short-lived credentials, constraints, evidence capture, revocation, and teardown. Broader provider coverage and live certification remain gated.

Package once

Deploy for one—or distribute to many.

Preview foundation

CoreHarness packages are versioned, remotely resolvable, dependency-locked, and lifecycle-managed. The preview supports installation planning, upgrades, health-gated rollout, rollback, repair, teardown, and signed offline bundles.

PersonalPrivate organizationCommercial publisherDirect installationPrivate catalogAir-gapped bundle
PROVIDER-NEUTRAL BY DESIGN

Models and tools are capabilities—not the platform’s identity.

A harness can combine native cloud AI, external model or agent APIs, locally hosted models, coding and computer-use agents, MCP servers, and organization-specific services. Each deployment selects only what its tasks and policies require.

Marketplace and commerce

Turn reusable harnesses into products.

Planned commercial layer
Public and private catalogsSigned packages and publisher verificationLicensing, entitlements, subscriptions, and trialsUsage metering and version managementCustomer-specific offersPublisher and service-partner revenue

Billing follows the deployment.

  • CoreVar bills managed platform usage directly.
  • Marketplace purchases may flow through the customer’s cloud bill.
  • Customer-cloud resources may remain billed by that provider.
  • Eligible resold subscriptions may use a future CoreVar or partner relationship.
  • Third-party services may stay directly billed while appearing in cost and entitlement views.
  • Publishers may charge for packages, subscriptions, seats, outcomes, or usage where supported.

Marketplace certification, reseller relationships, and unified billing are not generally available. The direction is consistent metering, entitlements, and cost visibility—not a promise of one invoice in every market or deployment.

Example harnesses

One platform. Different operating models.

Examples show what packages can model; they are not prebuilt products unless explicitly identified as such.

01

Agent-operated business

Executive, HR, sales, support, and engineering personas with accountable owners.

02

Software delivery

Coding and review agents using temporary cloud desktops and governed release actions.

03

Personal advisory team

Persistent specialist agents reached through a future CoreHarness mobile experience.

04

Customer service

Voice, email, CRM, workflow state, and approval policy working as one harness.

05

Research coordination

Multiple models, specialist agents, evidence, and durable delegated tasks.

06

Managed service delivery

A reusable package installed into a separately governed environment for each customer.

Turnkey onboarding · Planned

Understand the deployment before anything is created.

Onboarding is intended to present required capabilities, proposed architecture, data and network boundaries, permissions, costs, billing responsibility, created resources, and teardown behavior before installation.

CoreVar Managed ServicesDedicated managed environmentExisting customer cloudNew cloud where supportedOptional productivity integrationCoreHarness-native operation

CoreHarness

Build a governed system—not just another agent.

CoreHarness is currently a platform preview. Talk with CoreVar about design partnerships, deployment requirements, and the path to production readiness.