Viorant Hub

# Compose your AI system locally.

Hub is an optional local-first workspace for authoring and inspecting the prompts, skills, memory, agents, policies, and other artifacts composed in a portable [.vio system definition](/vio).

✓ Local-first authoring and testing

✓ Bring your own providers and keys

✓ Prepare a portable .vio system definition

[Download the Hub](/download)

macOS

Windows

Linux

[Read the docs →](https://docs.viorant.ai)

Viorant Hub interface for composing and testing AI artifacts

Author Declarative .vio artifacts

Test With built-in quality gates

Prepare Portable, versioned, governed

Handoff To Helix, CI, or your own runner

## Designed for builders. Built for control.

Hub keeps authoring, testing, provider keys, and artifact preparation local. The output is a portable .vio bundle, not a dashboard state you have to trust.

Local-first

Work offline. Keep prompts, tools, keys, and artifacts where you choose.

Model-agnostic

Use explicitly supported models and providers without binding the system definition to one stack.

•••

Governed by design

Tests, policies, and checks ship with your artifacts.

unit.test ✓

safety.policy ✓

compliance.check ✓

Portable artifacts

One .vio bundle for prompts, skills, memory references, models, tools, and agents.

## The Hub workspace. One source for AI assets.

Edit the .vio contract, inspect attached files, test behavior, and keep provenance visible before any artifact leaves your machine.

Explorer

Organize projects, artifacts, skills, policies, and tests.

Editor

Syntax-aware editing for .vio files.

Test Panel

Run regression, safety, and policy checks locally.

Artifact Info

Metadata, versions, and provenance.

Terminal

Validate, package, and export the bundle.

## Author with clarity. Test with evidence. Prepare with control.

Hub turns local AI work into a versioned system definition that can be reviewed, checked by [Trust](/trust) when policy requires it, and handed to [Helix](/helix), CI/CD, or another supported workflow.

1

Author Write artifacts in .vio

2

Test Run quality, safety, and regression checks

3

Prepare Build and version your artifact

4

Handoff Export for Helix, CI/CD, or your runner

Test Results ×

✓ Unit tests ◉ Passed

✓ Quality gates ◉ Passed

✓ Safety checks ◉ Passed

✓ Regression ◉ Passed

✓ Policy checks ◉ Passed

Run Output

⧉ Copy

$ viorant run support-triage.vio --case happy_path

Loading artifact...

Running unit tests...

Running quality gates...

Running safety checks...

Running regression...

All checks passed ✓

Portable .vio bundle prepared.

Output: ./output/support-triage/

Unit tests

Quality gates

Safety checks

Policy compliance

Regression

## Build once. Reuse everywhere.

Hub prepares the same artifact for local runs, signed repositories, CI/CD, Helix, or another compatible runner.

Your machine

.vio

artifact

Local runtime

Helix or CI/CD

Compatible runner

## Built for the handoff between builders and production.

Hub gives each role a readable artifact instead of another opaque console. The same .vio file can be reviewed by engineers, security, and leadership.

Platform engineers

See which prompt, tool, model route, connector, and policy are attached before the artifact leaves the workstation.

Designed for reviewable infrastructure, not copy-pasted runtime state.

AI engineers

Iterate locally, compare providers with your own keys, and keep behavior changes tied to a versioned .vio bundle.

The model can change without hiding the reason it changed.

Security and leaders

Trace what changed, who prepared it, and which artifact is ready for signing or deployment.

Governance starts in the file, not after production incidents.

HUB QUESTIONS, ANSWERED.

## Frequently asked questions.

01 Is the Hub in my execution path? +

No. The Hub builds and prepares your AI; it does not broker your runtime. Your application calls your model provider directly.

02 Where do my API keys live? +

On your device, in your OS keychain, per user. Keys are validated against the provider before they are saved and never proxy through Viorant.

03 Do I need an API key to start? +

No. Your account includes 2,500 free credits for the managed Viorant models, so you can author, test, and run before configuring any provider of your own. No credit card is required to start.

04 Which models and providers are supported? +

Review the [current plan and model availability](/pricing) before choosing a provider. Keep model routing explicit in the [.vio system definition](/vio); compatibility follows the current support documentation.

05 Does the Hub work offline? +

Yes. The Hub is local-first and works offline; cloud is enrichment, never a dependency.

06 What can I manage in Hub? +

Hub is built for the AI assets that become a .vio bundle: prompts, skills, model routing, memory references, connectors, tools, policies, tests, and agents. It prepares the artifact; deployment can remain separate.

07 How is this different from an LLM gateway? +

A gateway is a proxy in your traffic. The Hub is a build layer that stays off the path: it makes the things that produce your tokens versioned, portable, and testable. Provenance, not a tollbooth.

## Prepare AI assets locally. Keep the artifact yours. Download Hub today.

[Download the Hub](/download)

macOS

Windows

Linux