How Q-Root Works
Everything you need to understand, set up, and master exception management with Q-Root.
Getting Started
From account creation to your first monitored Solution — in under 10 minutes.
Core Concepts
Errors vs Exceptions, Solutions, Modules, Workflows — understand the Q-Root model.
Integration
Connect your applications via SQL, REST API, or ready-made scripts.
Architecture
Hybrid deployment, customer databases, and how your data stays on your infrastructure.
Security & Access
Encryption, RBAC, customer-scoped permissions, and data protection.
Billing & Plans
Trials, subscriptions, plan changes, refunds, and payment methods.
Getting Started
Create Your Account
Q-Root is currently in active development. To register your interest and get early access, contact us at enquiries@rtbss.co.uk.
Set Up Your Organisation
After signing up, you'll be guided through creating your organisation. This is your isolated workspace within Q-Root — enter your company name, select your industry, and choose your timezone.
Create a Solution
A Solution represents the system, process, or application you want to monitor — for example, "Payroll ETL" or "Customer Onboarding Pipeline". Q-Root scaffolds everything you need: modules, exception types, status workflows, and configuration.
Connect Your Database
Download the Q-Root schema script from your workspace settings and run it on your SQL Server instance. Then enter your connection details — Q-Root connects securely and runs daily health checks to keep the schema in sync. Your raw data stays on your infrastructure at all times.
Integrate & Start Capturing
Choose your integration method — SQL stored procedures, REST API, or downloadable scripts — and start capturing exceptions and errors. Most developers are integrated in under 30 minutes. See the Integration section below for details.
Core Concepts
Errors vs Exceptions
Q-Root draws a sharp distinction between two types of issues that most tools conflate:
Errors
Technical failures — connection drops, 404s, incorrect data types, syntax issues. Things that break because of infrastructure or code.
Exceptions
Business logic failures — conditions defined by the business that must be specifically looked for. Missing data, broken processes, rule violations.
Solutions
A Solution is Q-Root's core organisational unit. It represents a system, process, or application you want to monitor — e.g., "Payroll ETL", "Customer Onboarding Pipeline", or "Nightly Data Sync". Each Solution has its own tabbed workspace containing modules, exception types, teams, SLA policies, documentation, and dashboards.
Modules
Modules are hierarchical sub-divisions within a Solution. They let you organise exception types by area, function, or team. Modules can be nested (parent → child) and are used for auto-assignment routing — when an exception fires in a module, it's automatically assigned to the team linked to that module.
Status Workflows
Every exception moves through a status workflow: New → In Progress → Resolved. You can add custom statuses, reorder them with drag-and-drop, and define which statuses count as "resolved". Every transition is recorded with a timestamp and user, providing a complete audit trail.
SLA Policies
SLA policies define how quickly exceptions of a given type must be responded to. Each policy specifies a response time and up to three escalation levels. SLA clocks are office-hours-aware — they pause outside business hours and resume automatically. Breach alerts notify the right people at the right time.
Integration
Q-Root offers three integration methods. Choose the one that fits your stack — or use a combination.
SQL Stored Procedures
Call standardised stored procedures directly from your T-SQL code to write exceptions and errors to your customer database. This is the simplest path if you're already working inside SQL Server.
@SolutionId = 1,
@ExceptionTypeId = 42,
@Message = 'Missing invoice for order #12345',
@Identifier = 'ORD-12345';
REST API
POST exceptions and errors via Sanctum-secured endpoints. Each Solution gets its own API token with fine-grained ability scoping (read, write, or both for exceptions and errors).
Authorization: Bearer <solution-token>
Content-Type: application/json
{
"exception_type_id": 42,
"message": "Missing invoice for order #12345",
"identifier": "ORD-12345"
}
Downloadable Scripts
Download ready-made script templates in PowerShell, Python, and C# directly from your Solution workspace. Customise the parameters and deploy — integration in minutes, not days.
Architecture
Hybrid Deployment
Q-Root uses a two-part architecture designed to maximise your control over sensitive data while adding structure and intelligence.
Your Infrastructure
- • SQL Server database on your own servers
- • Raw Activity, Error, and Exception logs
- • Data never leaves your systems
- • Schema managed via downloadable scripts
Q-Root Platform
- • Workflow, assignments, SLA enforcement
- • RBAC, teams, notifications
- • Dashboards, reporting, audit trails
- • Daily health checks & schema validation
Supported Databases
Q-Root currently supports Microsoft SQL Server. The customer database schema is provided as a downloadable SQL script that you run on your instance. Additional database engine support is on the roadmap.
Security & Access Control
Data Encryption
Database credentials are encrypted at rest. All connections use TLS. Your raw log data stays on your infrastructure — Q-Root reads, never copies.
Role-Based Access Control
Five system roles with customer-scoped permissions. Users only see Solutions and data they have access to. All actions are audit-logged.
API Token Scoping
Sanctum API tokens are scoped per Solution with fine-grained abilities: read, write, or both — for exceptions and errors independently.
Customer Isolation
Every customer operates in a fully isolated workspace. Data, configuration, teams, and users are scoped by customer at the database level.