Uraion Fabric Maintenance workflows In development
Pilot applications

Uraion Fabric

Turn maintenance tickets into checked, reviewable changes.

For owners of small software consultancies, roughly 1–10 people. Start with one recurring workflow in one Project—not a promise to automate your business. Source-build onboarding is subject to fit; no signed public beta is available.

$250 / 30 days. Proposed continuation: $49/operator/month. Pricing hypotheses; inference separate. See scope and terms.

One ticket. Checked. Reviewed. Applied.

Request. Give Fabric a bounded maintenance task. The agent changes an isolated Agent Workspace, not the primary Project.

Check. Run the Project’s executable checks. Read the actual results—not just the model’s claim that it is done.

Review. Inspect the diff. A human applies the change to the primary Project only after reviewing it.

A synthetic invoice-total bug Real software · local model · silent recording

97.8 seconds, unsped, with English captions. This is the source-build Desktop browser renderer connected to a real Runtime, not a packaged native-beta install or a customer result. The prompt specifies the known one-line fix and the write_file tool. It is a workflow demonstration, not an autonomous-discovery or speed benchmark. Operator actions in this recording were driven by browser automation, not a measured human trial. Read the four internal proof notes, including failures, interventions and unknown costs.

Text walkthrough and recording setup
  1. The request changes invoice.js from adding unit price and quantity to multiplying them. Tests and package.json must stay unchanged.
  2. The local model reads and writes the isolated Agent Workspace. The primary Project still contains the original addition at this point.
  3. Verify workspace runs Node build, lint and test commands. Here, build and lint are syntax checks; the two tests cover three units at 1,200 cents and zero units. All pass.
  4. Review shows one modified file and the exact addition-to-multiplication diff. The recorded check output is expanded for inspection.
  5. The operator-only Apply changes control is activated. The item becomes Applied and the primary Project receives the change. After recording, the same checks are run against the primary Project.

Prepared before recording: a synthetic three-file JavaScript Project, two failing assertions, a Coding session, a preconfigured execution grant, and the default npm build/lint/test checks. Recorded on macOS Apple Silicon, with Node 26.10.0, npm 11.19.1, Ollama 0.34.4 and qwen3.8:27b-nvfp4. No customer code, cloud model or fabricated UI state is used.

Open or download the recording. Use the player’s fullscreen control for the code and check output.

Know what you are trying.

01

A source-build pilot

The demonstrated environment is macOS on Apple Silicon with local Ollama. A signed, notarized beta and clean-machine onboarding are not yet available. Linux Desktop and cloud-provider first-run validation are not complete. We confirm your environment before accepting a pilot.

02

Your provider choice

Project state lives locally. This recording uses a local model. If you choose a cloud provider, selected Project context, prompts and tool results sent for inference leave the device for that provider. Bring your own credentials; provider charges are separate.

03

Checks have a boundary

Passing checks are evidence for those checks, not a guarantee of correctness. The demo’s two assertions are deliberately small. Real pilot work needs meaningful Project checks and human Review; no customer savings or reliability benchmark is claimed here.

04

Maintenance, not everything

This offer is for one recurring software-maintenance workflow. Editable Excel or PowerPoint deliverables, external-browser automation and general office workflows are not included or demonstrated.

$250 for 30 days.

One operator. One Project. One recurring maintenance workflow. Two hours total founder assistance for setup and the workflow. Bring-your-own-key inference charges are separate; additional services require a separate scope.

Proposed continuation: $49 per operator per month, shown before you apply. Both prices are hypotheses to test—not validated willingness to pay, customer traction or promised savings.

Applying does not pay, enroll you, or start an automatic renewal. We confirm availability, workflow fit, environment, scope, cancellation and refund terms before any charge. Onboarding and billing are manual; no signed-beta download is promised.