◆ White-label offerings

Proposed offering

Private Knowledge Assistant

Put the source next to the answer.

Test a permission-aware assistant against the questions your team actually needs answered.

Discuss your workflow Explore the proposed workflow

Concept-stage implementation service. The foundation has been reviewed in source; this RZIFI offering has not been delivered or deployed for a customer.

The operating problem

Give the team a path from question to decision.

A confident answer is not useful if it cites the wrong policy, ignores document permissions or conceals that the source is out of date.

Use a source-grounded retrieval pattern as the starting point for a dedicated application. Add identity, document permissions, ingestion, evaluation and operating controls before connecting real enterprise knowledge. A local model runtime is an optional deployment choice, not a guarantee of privacy or answer quality.

Designed for

A financial-services or enterprise operations team with a defined document collection, named information owners and a measurable knowledge-retrieval problem.

Explore the workflow

Policy question with restricted evidence

Illustrative workflow with synthetic data. This is a static product concept, with proposed integration and control behavior to validate during a pilot.

QUESTION-DEMO-03Synthetic scenario · no live operation

Ask a bounded question
Proposed
Search a selected, versioned document collection.
Check access
To implement
Apply user and document permissions before retrieving content.
Inspect the source
Example pattern
Show the cited passage, document version and freshness.
Answer or refuse
Human review
Return qualified evidence or route to a document owner.

An inaccessible or unsupported source should produce a refusal. This static walkthrough does not run a model or prove permission enforcement.

Capabilities and scope

Start with what exists. Scope the rest.

Source review identifies building blocks. Integration, configuration and deployment acceptance still determine what the customer implementation can do.

Foundation behavior reviewed

Implementation found in upstream source. No runtime or production claim follows from this review.

Typed RAG Answer validates nonblank text and answer/citation consistency
Deterministic evidence preflight refuses before model request when evidence insufficient
Retrieval module defines chunk/search structures and embedding interface
Streamlit UI accepts uploaded/source documents and embedding mode

Technical source notes · 23 October 2026

Proposed customer implementation

New work to design, integrate and test against your requirements.

Enterprise identity and document-level access enforcement
Reliable ingestion, provenance, expiry and deletion
Evaluation, feedback triage and administrator controls

Roles, report access and data boundaries are mapped to the customer operating model. Shared multi-customer administration and enterprise identity require explicit scope.

Scope boundary

The upstream repository contains examples, not a finished enterprise product. Dify and Open WebUI alternatives have additional licensing/branding conditions. The first scope answers questions; it does not make financial decisions or execute payment instructions.

Business use cases

Choose the workflow worth improving.

Payment operations handbook

Ask a question against approved procedures and inspect the cited passage and document date.

Value to validate: Measure whether operators find correct evidence more reliably.
Integration needed: Approved documents, identity groups and a maintained evaluation set.

Program decision retrieval

Find the latest approved decision and distinguish it from an older draft.

Value to validate: Reduce ambiguity around the current decision.
Integration needed: Document lifecycle, version metadata and permissions.

Compare approaches

A custom implementation should earn its place.

An existing SaaS package may be the better choice for standard needs. Compare the same workflow, workload, geography, data boundary and support commitment. No savings or performance advantage is assumed.

Vendor observations checked 23 October 2026; not RZIFI prices or normalized sales quotes. Unknown setup cost does not mean zero.
Approach	When to consider it	Observed commercial basis	What needs checking
RZIFI proposalProposed offering	A specific workflow, integration or deployment requirement justifies dedicated engineering.	Scoped discovery and implementation, with optional recurring operations. Request a quote.	Selected license, tenant boundaries, integration acceptance, operating ownership and total cost.
Dify ↗	Teams seeking a visual workflow and knowledge-application platform.	Professional observed at $590/workspace/year: 3 members, 5,000 monthly message credits; taxes excluded.	Cloud subscription pricing does not grant rebranded multi-customer hosting rights. Model usage and commercial licensing need separate scope.
Microsoft Copilot business ↗	Organizations evaluating AI inside an existing Microsoft workspace.	Business Premium with Copilot displayed $32/user/month, paid yearly.	This is a suite bundle, not a bare retrieval service. Compare document permissions, connectors and advanced usage.
Glean ↗	Enterprises evaluating managed search, connectors and an agent platform.	No verified numeric public price in the retrieved page; sales enquiry.	Request workflow, access-control and integration scope; do not infer a seat price or white-label rights.

Deployment and customization

Choose the data boundary and the operating owner.

A dedicated customer environment is the preferred first design target. Managed hosting, customer cloud and on-premises delivery each require their own validated package and operating agreement.

Brand and experience: Agree domains, logos, interface theme, notification email, accessibility and the upstream notices that must remain.
Data and identity: Define users, roles, document or record access, secrets, retention and export. Validate separation with positive and negative access scenarios.
Operation and change: Name who monitors the service, handles incidents, maintains connectors and applies upgrades. Include backup, restore and rollback evidence.

Commercial scope

Price the implementation you actually need.

Request a scoped quote. Paid discovery defines the workflow and acceptance criteria, followed by a separate implementation scope and an optional operations agreement. Licenses, infrastructure, model/API usage, payment processing, taxes and unusual migration work are identified separately.

Bounded pilot

One workflow and agreed test data. Define the acceptance cases and limitations before implementation.

Production target

Validate the selected integrations, authorization, recovery, upgrades and operating handover. Release follows observed acceptance.

Enterprise extension

Scope buyer-specific identity, audit, regional deployment, recovery and support commitments. Certification is a separate requirement.

These are potential delivery scopes, not existing service tiers or committed calendar dates. Discovery is part of the agreed delivery scope; any separate discovery invoice is accounted for in the implementation quote.

Purchasing questions

Make the decision with the boundaries in view.

Does a local model keep all data private?

Only if the complete deployment supports that boundary. Embeddings, telemetry, logs, tools, backups and outbound network access must also be reviewed.

Can you guarantee correct answers?

No. Define an evaluation set, measure unsupported answers and refusals, and keep a clear route to the source and human review.

Can it take actions?

The initial evaluation is read-only. Tool execution requires separate permissions, approval, audit and recovery controls.

What does a scoped implementation include?

Discovery identifies the workflow, data boundary, selected edition, integrations and acceptance criteria. Implementation and optional ongoing operations are quoted against that scope. There is no standard package or committed list price at this concept stage.

Can it run in our environment?

A dedicated customer environment is the first design target. Customer cloud, managed hosting and on-premises options are evaluated separately against the chosen foundation, identity requirements and operating owner. A tested deployment and recovery procedure are required before a commitment.

What evidence is needed before launch?

The agreed scope should name authorization and integration tests, data migration checks, backup and restore, upgrades, vulnerability handling and operating responsibility. Certifications, regulatory approvals, service levels and performance outcomes are not implied by a proposed offering.

Start with your operating problem

Show us the workflow that is costing your team time.

Discuss the requirements, the foundation and the work needed before a launch. The next step is a scoped conversation.

Discuss this offering