How it works
Two pieces. Both of them yours.
A Windows application on your team's workstations, and a database on the SQL Server your firm already runs. That is the whole system. There is no Soltris piece in a cloud somewhere, and the only outside connection is the AI provider your firm chooses, if it chooses one.
A license is a signed file beside the application. An AI credential, if your firm wants one, is written by IT with a provisioning script. Neither involves Soltris.
Deployment, in four steps.
Done by your IT, on your schedule, with nothing granted to anyone outside the firm.
Install
A code-signed installer, deployed to workstations the way your IT deploys everything else.
Database
A database on your SQL Server instance. Your authentication, your backups, your controls.
License
The signed license file is placed once per machine. Verified locally; no activation, nothing to reach.
AI credential
Optional. IT runs a provisioning script that encrypts your provider key into your database. The key never passes through the application.
Then the work, end to end.
- Bring transcripts in
- Court reporter text transcripts, PTF files, PDF, and packaged productions with synced video. Existing annotation and designation work arrives by CSV, mapped by column name, so a migration does not start from zero.
- Work the testimony
- Read, search, annotate with issue codes, designate with objection notes. The margins show the state of the page at a glance.
- Build the record
- Facts flow into a chronology with page-and-line citations that jump back to the testimony, exhibits linked where they are mentioned, AI summaries and extractions with verified citations where the matter allows it.
- Produce
- The Printed Transcript carrying the marks onto paper, reports to PDF and Excel, designation clips, and exports that leave nothing stranded.
An hour tells you more than a page.
The demo walks this exact path on a transcript: import, annotate, designate, extract, print. Bring the person who runs your SQL Server.