FAQ | Jivoo

Questions about Jivoo.

42 answers, in 9 groups. Each one says only what this site can support; where a figure is not published, the answer says so. The assistant in the corner answers from this page. Where an answer turns on how the work is shaped, the patterns page sets out the implementations in full.

The factory

What is an AI software factory?

A governed way of building software where an approved AI agent drafts at every stage of delivery, a named person makes every decision, and the systems record the evidence as the work happens. It is assembled from tools an organisation already has, not a product to buy, and it does not depend on any one AI vendor.

Why should every organisation have one?

Because the alternative is speed without control. Each team uses AI in its own way, and without a common model the speed grows faster than the control and the spend grows faster than the value. A factory gives one answer for every product: who can change production, who approved a change, and whether an AI tool can touch the data.

Which AI vendor does the factory depend on?

None. The guardrails are configuration, independent of runtime: the rules live in one canonical AGENTS.md, generated into each runtime's rule file. An approved agent runtime is any one on the approved list, connected to the same MCP tools and the same model tiers, so changing runtime does not mean rebuilding the toolchain.

Who does Jivoo work with?

Organisations building or running software with AI agents: usually several product teams, a security function that owns the approved tools, and a sponsor who has to answer for how the software is made. The company has served the Fortune 500 and federal sectors for 30 years.

Orchestration

What does orchestration mean here?

How the work is directed: the six stations of delivery, the agent personas, the three model tiers and their effort, how a task finds its tier, the MCP tool map and the rules that keep token use down. Orchestration decides how work runs.

What are the six stations?

Plan, Design, Build, Verify, Release and Operate. At each one an agent drafts and a person decides: a story becomes an approved work item, a design becomes an architecture decision record, code becomes a pull request, tests and a review become a merged change, a release becomes a production release by digest, and operations become audit-ready evidence.

What are the three model tiers?

Tier 1 Fast for summarising, classifying, extracting and searching; Tier 2 Standard for code, tests and first-pass review; Tier 3 Deep for design trade-offs, security review and hard root cause. Each task starts on the smallest approved model that does it well, and a larger model is an escalation, never the default.

Do you build agents, or advise on them?

Jivoo builds the factory the agents work inside, and advises on which tasks should go to an agent at all. An agent that drafts into a weak architecture drafts faster into a worse place, so the design of the stations, the tiers and the harness comes first.

Do you work with our existing cloud and source control?

Yes, and it is the point. The factory is assembled from tools the organisation already has: its work management, its source control, its package registry and its cloud. The MCP tool connectors give an agent controlled access to those systems, so the traceability thread runs through the tools in use rather than a new platform.

About Jivoo

What is Jivoo?

Jivoo is an AI systems integrator that designs and installs software factories: a governed way of building software in which approved AI agents do the drafting at every stage of delivery, people make every decision, and the systems record the evidence as the work happens. It has spent 30 years on enterprise digital transformation for Fortune 500 and federal sectors.

How long has Jivoo been doing this?

30 years, and the About strip on the home page states 30+ years of leadership. That covers the .com era through to the current work on Agentic AI, and it is the longest running claim on this site.

What awards has Jivoo won?

The IoT Business Impact Award for transformative enterprise solutions, and a Microsoft Azure AI Most Valuable Professional credential for technical leadership and community contributions. The site does not publish an award year, because none has been confirmed for this page.

Where is Jivoo based?

The site does not publish a registered address. The contact form is the way to ask, and the reply comes from a person.

What does Jivoo do?

It designs the factory and installs it: the orchestration, the harness, the guardrails, the traceability and the evidence, inside the tools the organisation already runs. The homepage also lists the wider capability across data, platforms, agents and operations that the factory is built on.

Do you do proof of concept work?

The factory review is the first piece of work, and it is deliberately small: how work moves through the stations today, which tools hold the record, and where the harness is missing. Whether the next step is a design, a pilot or an installation depends on what the review finds, and the contact form starts it.

The harness

What is the harness?

What bounds the machine and what it must prove: the guardrail layers, the canonical standard generated into every runtime's rule file, the list of what never enters a model's context, identity and access, the named-human review, the evidence record and the gated pipeline. A harness decides what the machine may do and what it must prove.

How do you keep an agent away from production?

Three rules. No AI tool merges to a protected branch, applies infrastructure or releases to production on its own. AI tools run with the person's own non-production access, and no AI identity holds production access. Automated and product model calls go through one model gateway, which applies the tiers and meters the tokens.

How do you make an agent safe to use?

By treating the harness as the design, not the afterthought. Rules live in one canonical standard generated into every runtime, AI runs on the person's own non-production access, a named person approves every change and every release, and the pipeline refuses to go on when a link in the chain is missing.

Is this a Claude product, or does it work with other tools?

It is a pattern, and Claude is one implementation of it. The patterns page sets out two that Jivoo uses: a hosted runtime with one model gateway in front of it, and Cline with its own orchestration and harness. The same stations, the same tiers and the same evidence either way, and a third runtime is a configuration change. What a runtime does not carry on its own is the gate: who decides, what done means, and what the machine must prove before it ships. That is the harness.

Can you help with compliance and audit readiness?

The factory is built so the evidence exists before the audit: every step leaves a record in a system of record, including which runtime, model, tier and policy version drafted the work, so an audit sample can be produced on demand. Jivoo does not describe any framework as certified unless the certification is published.

Evidence and data

What evidence can you give a board or an auditor?

The record the factory leaves as it runs. Every step writes to a system of record, including which runtime, model, tier and policy version drafted the work, and a query joins the work item, the pull request, the pipeline run and the approval into one chain. An audit sample is produced on demand, not assembled before an audit.

Do you sign an NDA?

The site does not publish Jivoo's position on NDAs. The contact form can start that conversation, and no claim about paper is made here until the owner confirms one.

How do you handle our data?

Engagement data is handled under the agreement for that engagement. For this website, the Privacy Policy names every field and every store the site writes, and the site's own analytics are first party and run only with consent.

The free resources

What free resources does Jivoo publish?

Four, and each is a real document: The AI Software Factory Playbook, Orchestration and the Harness, the Runtime Patterns guide and the Factory Readiness workbook. Each has its own request form on the resources page.

How is the factory playbook delivered?

By email. The form asks for your name, your email and your consent, then sends a private download link that expires in seven days. The PDF is never attached, and no account is needed.

What does the orchestration and harness guide cover?

The half most organisations skip: the six stations with the person who decides at each one, the agent personas, the tiers, how a task finds its tier, and the harness layers, the review rules and the evidence record that keep it safe.

What does the runtime patterns guide compare?

Two implementations of the same pattern: a hosted agent runtime with one model gateway in front of it, and Cline with its own orchestration and harness. Same stations, same tiers, same evidence, and the decision rules for choosing between them without a price list.

What is the factory readiness workbook?

A spreadsheet of the questions a factory answers, so a team can score itself before the first conversation: which work items carry a traceable ID, which changes have a named approver, whether any AI identity holds production access, and how the evidence is produced. It sends nothing anywhere.

Working together

How does an engagement start?

With a factory review: a short read of how work moves through the stations today, which tools hold the record, and where the harness is missing. If there is a fit, the design of the orchestration and the harness is the first deliverable, and the factory is installed from there.

How long does a project take?

The site does not publish a fixed timetable. The scope is set by the factory review, and the design of the orchestration and the harness is what makes an honest estimate possible.

What does it cost?

The site does not publish a price, a rate card or a fee schedule. Pricing follows a scoping conversation, so the first step is the contact form.

Do you work with subcontractors?

The site does not publish Jivoo's position on subcontracting. The contact form can ask, and the answer is confirmed in writing before an engagement rather than assumed from this page.

Referral programs

How does the referral program work?

You apply for a referral code, share the page for the business you want to introduce, and the person who visits it sees that the introduction may earn a fee before they contact Jivoo. The fee itself is confirmed in writing before any engagement starts; the current page does not state an amount, and it never adds to what the client pays.

Where are the referral rules written down?

The human program has its own terms at /refer-terms and a printable card at /refer-card. The agent program has its own terms at /ai-referral-terms, and the machine-readable record sits at /.well-known/ai-referral.json. The general terms of use are separate from both.

Is there an AI agent referral program?

Yes. The operator of an AI assistant, agent or autonomous browser agent can apply, and the person or company operating the agent is paid, never the model. The referred organisation sees a disclosure before it contacts Jivoo, and the terms are on the agent referral terms page.

Start a conversation

If the answer you need is not here, a person reads every message.

Ask Ziva

Ask Ziva a questionSend