Technical Overview

Deployment, Architecture, and Security.

This page is for security, data, and platform teams. It outlines how Rivlo integrates with your environment, how execution works, and what controls are available.

Back to Home Request a Demo

How Rivlo Works.

Rivlo is a desktop-first analytics workspace. It connects to your databases, helps generate SQL from natural language, and saves the outputs as re-runnable Reports. The goal is controlled, reviewable analysis - without creating more operational risk.

1) Connect

Connect to the databases you already run. Configure credentials and permissions according to your internal policy.

2) Draft SQL

Rivlo drafts SQL from questions and keeps the workflow reviewable. You can inspect and edit before execution.

3) Run + Save

Execute queries through the configured path and save results + SQL as Reports for repeatability and handoffs.

Deployment Options

Rivlo is desktop-first to fit environments where controlled access and review workflows matter. You can choose where the model endpoint runs based on your policy and infrastructure.

Desktop Distribution

macOS, Windows, and Linux clients. Designed to integrate with common enterprise deployment patterns.

Option 1

Customer-Hosted LLM (maximum control)

Customer-Hosted Model

Run Rivlo's finetuned language model entirely inside infrastructure you control.

•Model runs on your own cloud or on-prem environment
•Full control over execution, networking, and access policies
•Rivlo never operates or accesses the model runtime

Best for

Teams with strict security, regulatory, or residency requirements.

Option 2

Rivlo-Hosted LLM (schema-only, zero data retention)

Rivlo-Hosted Model (Schema-only)

Use Rivlo's managed LLM service without exposing your data.

•Only schema metadata (tables, columns, relationships) is sent to the model
•No row-level data, query results, or database contents are ever transmitted or stored
•Query execution always happens inside your environment

Best for

Teams that want a managed experience without data leaving their systems.

Next Step

If you share your stack and constraints, we propose the cleanest deployment path.

Request a Demo

Architecture

Rivlo is designed to keep execution close to your data and make the workflow easy to inspect. Exact deployment models vary by customer; the sections below describe the common control points.

Execution Path

Queries execute against your configured databases using the credentials and permissions you provide.

Review Point

SQL is visible and reviewable before execution, making it easier to enforce internal standards.

Reports Storage

Reports store the SQL and a snapshot of results so teams can reference what was shared and re-run intentionally.

High-Level Flow

Your Environment

Databases, permissions, and network controls stay under your policy.

Rivlo Desktop

• Connect to configured databases
• Draft and review SQL
• Execute and save Reports

Model Endpoint

Configure the model endpoint based on policy. Choose customer-hosted or a Rivlo-managed endpoint.

Implementation Note

The exact boundary and controls depend on your environment. We validate the deployment model during evaluation.

Security Model

Rivlo is built around clear control points: who can connect, what can be queried, and what gets saved. Specific controls vary by environment and policy.

Reviewable SQL

SQL is visible and can be inspected before execution. This supports internal review and training workflows.

Least Privilege

Rivlo uses the database permissions you configure. You decide what users can access and run.

Reports Retention

Reports store SQL and a results snapshot for repeatability. Retention and storage location can be aligned to policy.

Security questions we expect

Where does execution happen?

Against your configured databases using the credentials and permissions you provide.

Can we choose the model endpoint?

Yes. Rivlo can be configured with a managed or self-hosted OpenAI-compatible endpoint, depending on policy.

What gets saved in Reports?

Reports are designed to store the SQL and a results snapshot for consistent sharing and repeatability. Retention policy is typically set during evaluation.

Note

We’ll align the final controls and configuration with your compliance and IT requirements.

Technical FAQ

Questions from security, data, and platform teams.

Do you support SSO?

SSO expectations vary by customer. We’ll align authentication and access controls during evaluation.

Can we restrict query patterns?

Most teams enforce restrictions through database permissions and review workflows. We’ll validate your constraints during demo/eval.

How do you handle auditability?

The core workflow is designed to be reviewable and repeatable. Reporting and retention policies are configured to match internal needs.

What’s the best way to evaluate Rivlo?

Start with a sandbox schema and a small set of representative questions. We’ll propose a safe evaluation plan.

Request a Demo

Or go back to the home page.