Security, architecture & operations
A protected data space that fits into your existing IT.
Data sovereignty and traceability are built in, not bolted on. SQACE connects to your data sources, tools and CI/CD and runs on-premise or in an EU cloud, as an independent verification instance inside your architecture.
Integration
Connects to your data landscape, tools and processes.
SQACE replaces no infrastructure. It fits in: no data copies, no intermediate layers, no separate user management.
Data sources
JDBC databases (Oracle, Microsoft SQL Server, PostgreSQL and other JDBC-compatible systems) plus files in CSV, JSON, XML and fixed-width formats. Distributed data can be pulled into tests directly, without pre-processing.
Web services
Connects REST interfaces, both as a data source for tests and as a way to drive SQACE from the outside.
Test management
Test results, deviations and release status flow straight into Jira / Xray, with no manual transfer and no re-keying between systems.
DevOps & automation
Via the REST API, tests and workflows can be triggered from CI/CD pipelines (e.g. Jenkins, GitLab CI, Azure DevOps) or orchestration tools (e.g. Camunda). Results are reported back.
Identity & access
Integrates with central identity and access systems via Single Sign-On / Active Directory. User management and security policies stay consistent.
Multiple environments
Structured processes across separate stages (Dev → Test → Prod): tests, rule sets and connections are promoted in a controlled, version-controlled way.
This is the confirmed current state of our connectors. For other sources and the roadmap, let’s talk specifics. We only show here what holds today.
Operations & data sovereignty
In your infrastructure. Under your control.
SQACE is built to grow from a first pilot to an enterprise-wide standard, without data protection and traceability becoming a bottleneck.
On-premise or EU cloud
Containerised operation (Docker/Linux) in your infrastructure or an EU cloud. Your data does not leave your jurisdiction; updates are applied in line with your release processes.
Physically separate workspaces
Each test project gets an isolated workspace (Mission Base) with its own data, connections, rules and rights. Teams work in parallel without affecting one another.
Verification on production data
A separate production instance (Production Server) verifies directly on production data, without direct user access. Privacy by design, not by policy.
Licensed by project, not by head
Unlimited users, unlimited storage, unlimited CPU, on your hardware. Testers, business experts, auditors and viewers all take part, with no seat discussion.
Scales from pilot to standard
Step-by-step expansion from one project across several teams to an enterprise-wide platform, with one methodology instead of person-dependent silos.
Central connection management
Database, file and service connections are managed centrally and under control. System access stays clear and consistent, across multiple environments too.
Security & evidence
Traceability that convinces auditors.
What is checked, and who is allowed to do what, is traceable at any time. Evidence arises as a by-product of the work, not as a parallel compliance track.
Permission concept
Fine-grained, role- and rights-based access to data, connections, test definitions, execution and results, connectable to your existing permission systems.
Versioning & audit trail
Who defined, changed, ran and released what, and when? Released solutions are read-only, audit-proof and not deletable.
Automatic deletion
Defined retention periods and automated data-lifecycle management apply without manual per-project configuration.
Complete documentation
Every test run, every result and every rule change is documented automatically. Auditors get traceability without anyone documenting on the side.