RHOYLLE SOVEREIGNRHOYLLE Innovation Empire LLC
For clients choosing where it runs

Six ways to run it. One score, traced to the check that produced it.

RHOYLLE SOVEREIGN is the database governance console from RHOYLLE INNOVATION EMPIRE LLC. Pick the deployment that matches who operates the console. The collector still runs where the databases are.

RHOYLLE INNOVATION EMPIRE LLC

The company

RHOYLLE INNOVATION EMPIRE LLC

8340 East Baseline Road, Suite 3051
Mesa, AZ 85209

The company is on its own page

The logo, the address, the contacts, and the console screens sit at the top of the site. This page stays the place to choose where the product runs.

Choose a deployment

SaaS

A team that wants the console hosted and a score this month.

What runs
The console at rhoylle.com. Community, Quick Assessment, Pilot, and the Sovereign annual licence use this.
Where the data lives
Estate evidence is stored in the hosted console. Card payment goes to Stripe. The assistant calls OpenAI only after an administrator turns it on.

Hybrid

A regulated estate that will keep the console with us and keep the databases in its own network.

What runs
The hosted console, plus the collector on a machine that can reach the databases. This is the Sovereign annual licence.
Where the data lives
The collector posts check results to rhoylle.com. It does not copy table contents. The annual licence is quoted after an assessment or a pilot.

On-premises

A team that must run the console on its own server.

What runs
The self-hosted licence. Docker Compose, or the Windows or Linux installer, puts the console on that server. The collector runs beside the databases.
Where the data lives
The console stores data in the Supabase project named during install. That project can sit in the same network. Offline mode does not call rhoylle.com, and the console does not take card payments.

Standalone

A DBA who needs a scan on one machine before the rest of the estate is enrolled.

What runs
The collector is a script. The signed Windows collector scores SQL Server. The Python collector scores PostgreSQL, MySQL, MariaDB, Oracle, Db2, and MongoDB when it is run against that engine.
Where the data lives
Results post to the console the organisation already uses, hosted or self-hosted. The collector does not need its own database.

IaaS

A team that already operates virtual machines and wants the console on one of them.

What runs
The same self-hosted installer, on a virtual machine the client operates: VMware, an Azure VM, or an EC2 instance. There is no marketplace image.
Where the data lives
The virtual machine is theirs. The console still uses the Supabase project they name. Collectors stay next to the databases.

PaaS

A platform team that already runs containers and wants the console on that platform.

What runs
rhoylle.com itself runs as a container. A client can build the shipped Dockerfile onto their own container service. There is no separate PaaS price.
Where the data lives
Their platform runs the container. The data plane is still the Supabase project they configure. Stripe is not started in that mode.

What a buyer can verify

These are properties of the product a client can check in the console, in the collector, and on the trust page.

A missing scan is not a pass

An instance no collector has measured stays unscored. A report does not turn an empty check into a high score.

Every number traces to a check

The estate score is the severity-weighted result of the checks the collector ran. The finding shows what was observed.

The collector does not change the database

A scan is read-only. A change happens only after an administrator approves a runbook and someone on the operator machine runs it.

Where data goes is named

The console, Stripe during hosted checkout, and OpenAI only while the assistant is on. A self-hosted console does not add a card processor.

The same product, more than one place

Community can be hosted or self-hosted and does not expire. Production moves from an assessment, to a 60-day pilot, to a hosted or self-hosted licence.

The Windows collector is signed

SQL Server is the signed collector, and the signature can be checked. The other engines score the checks their own collector ran.

How we recommend selling it

The offer is a ladder. Advertising should send a buyer to the next rung they can accept, and the first meeting should use the sentence that matches the person in the room.

Let the free tier prove the score

Community covers two SQL Server instances, hosted or self-hosted, and it does not expire. A buyer sees a real score before a contract.

Sell the assessment, then the pilot

Quick Assessment is $1,000. The guided pilot is $1,500 for 60 days. Both are delivered with the founder. The annual licence comes after one of those.

Match the sentence to the room

A DBA hears read-only collection. A compliance officer hears a traceable score. Procurement hears a fixed first invoice and a quote only after evidence.

Use consulting when the estate is not ready for software

The same company does the baseline, the migration, and the recovery work. The software is the record. The consulting practice is how a messy estate gets there.

Database administrator

Run the signed collector, read the finding, and keep the scan from changing the instance.

Compliance officer

Take a score that names the check, the framework, and the date of the scan.

Procurement

Start on Community or a fixed assessment. The annual licence is quoted only after that evidence exists.

A note a client can forward

RHOYLLE SOVEREIGN scores a SQL Server estate from a signed, read-only collector. It is built by database administrators, for a job that has to stay reliable: the scan does not change the instance, a missing check is not a pass, and a change waits for a person. Community covers two instances at no charge. An assessment is $1,000 and a 60-day pilot is $1,500, both with the founder. The console can stay at rhoylle.com or run on your server. RHOYLLE INNOVATION EMPIRE LLC, Mesa, Arizona. rhoylle@rhoylle.com.