Kynetra X Prime command surface Request access

KYRx Pods / Agent Runtime / HBForge / Cloudflare

The agent-native SaaS command center.

Kynetra X turns product intent into checked Pods, approved agent runs, proof-backed releases, and Cloudflare deployments from one operating surface.

See the pipeline Choose a plan
Kynetra X / production plan x.kynetra.dev
Pod Registry Checked deployable units

Package Cloudflare Workers, KynetraFX routes, KynML jobs, Auth policies, DB schemas, OwlMQ workflows, and Web7 proof envelopes.

Schema 0.1
Targets 10
Gate Review
  1. 01Intent captured
  2. 02Pod manifest checked
  3. 03Human approval attached
  4. 04Cloudflare release prepared

What it is

One surface for the systems you already defined.

The KYRx platform spec defines one language, source profiles for ClearScript and NovaC, Pods as portable deployable units, HBForge as the registry and SaaS assembler, and Kynetra Agent Runtime as the execution layer.

Runtime

Agents operate where approvals, tools, and memory meet.

01

Kynetra Console

Human-facing control for prompts, approvals, logs, memory, tools, and deploy status.

02

Agent Runtime

Workers, Agents SDK, Durable Objects, Workflows, Queues, D1, R2, KV, and Vectorize.

03

Tool Registry

Every tool declares schema, risk, runtime, approvals, and allowed agents.

04

Memory Loop

Trace facts, score outcomes, update memory, and promote lessons through review.

KYRx Pods

Every product unit gets a contract before it gets a deploy.

A Pod declares entrypoints, inputs, outputs, targets, capabilities, bindings, secret slots, approval rules, proofs, budgets, tests, and rollback strategy.

Cloudflare KynetraFX HBForge KynML KynetraAuth KynetraDB KynetraConnect OwlMQ Web7 QuantumOS

Pipeline

Prompt to proof, without losing the audit trail.

01

Intent

Prime captures the goal, workspace, risk, and growth lever.

02

Plan

Planner and Router agents produce Action Plan JSON with approvals.

03

Pod

KYRx validates the manifest, source profile, target, and policies.

04

Assemble

HBForge packages the module and prepares SDK or app integration.

05

Release

Cloudflare deploys only after proof, rollback, and human gates pass.

Proof-backed operations

Designed for accountable AI work, not invisible automation.

Approvals before risk

High-risk actions like deploys, data writes, billing, email, and skill updates stop for human approval.

Artifacts before claims

Pods require tests, rollback, policy, and proof metadata before publish or deploy.

Memory before training

Agents improve through traces, evaluations, retrieval, scorecards, and reviewed skill updates.

Plans

Start with the surface you need now.

Studio

For internal teams shaping KYRx Pods, docs, and runtime contracts.

  • Pod schema and examples
  • Manual deploy review
  • Spec-first product workflow

Platform

For teams running approved agents, HBForge modules, and Cloudflare releases.

  • Agent runtime planning
  • Tool registry and approvals
  • Cloudflare Pages and Workers path

Enterprise

For product portfolios that need audit, tenancy, proof, and governance.

  • KynetraAuth and KynetraDB policies
  • Web7 proof envelopes
  • Private registry and release gates

Now hosted on x.kynetra.dev

A front door for KYRx, Pods, agents, and proof-backed SaaS.

Request platform access