Built for the environments that can’t afford to be wrong.

Specaria is designed for regulated, audit-grade estates — government, banking, insurance, telco, utilities. The security model starts from one premise: your systems and your data stay inside your perimeter, and everything privileged leaves a trace.

Runs inside your perimeter

Every product is self-hosted in your own VPC or data centre. Your data never transits our infrastructure to be processed.

Offline license verification

Licenses are JWKS-signed tokens verified locally. If our infrastructure goes dark, your products keep running.

Signed, queryable audit

Every privileged action is recorded with a named actor, a timestamp, and an exact diff — exportable for your auditors.

No customer data reaches us

Only operational metadata — version, health, license status — is ever sent back, and that channel is yours to disable.

Where your data lives

Your perimeter is the boundary. We designed around it.

Products run entirely in your environment. Discovery reads your services, mapping writes your contracts, observability watches your traffic — and none of it transits our infrastructure. The only thing that crosses the boundary is outbound operational metadata, and that channel is yours to throttle, audit, or switch off.

For fully disconnected estates, the same build runs air-gapped: license tokens verify offline and updates are applied from signed artifacts you stage yourself.

// data-flow · your perimeter your VPC ├── discover services · screens · payloads stays local ├── transform contracts · mappings stays local ├── observe traffic · latency · audit stays local └── outbound license verify · health metadata only → // no payloads · no PII · no source data ever leaves

Controls

The security model, control by control.

Every product inherits the same spine — identity, licensing, update integrity, and audit — so the security posture is consistent across the whole line-up.

Private by default

Services sit behind a private VPC and a load balancer that terminates TLS. No product surface is exposed to the public internet unless you choose to publish it.

Offline-first licensing

License tokens are signed with a key you can pin (JWKS). Verification is local and works air-gapped — no phone-home is required to run.

Signed update distribution

Every release is a signed manifest. Your deployment verifies the signature before it installs, so a tampered artifact never runs.

Enterprise SSO

Authenticate against your identity provider over OIDC or SAML. Specaria never stores your users’ passwords.

Role-based access, least privilege

Fine-grained roles gate every operator action. Access is scoped to what a role needs, and each grant is itself an audited change.

Audit trail, end to end

Discovery, mapping, approval, promotion, and rollback all leave a sequenced, signed record you can query and export — evidence-grade by default.

Your data residency

Data lives where you deploy — your region, your cloud, or on-prem. There is no shared multi-tenant store you are placed into.

Review before change

AI proposes; your team approves. No automated change reaches production without a human decision on the diff.

What leaves your environment

Metadata, not data. Outbound, never inbound.

To license and support your deployment, a product sends back a small, fixed set of operational signals: the product version, aggregate health, and license status. No payloads, no source records, and no personal data are ever included.

The channel is outbound-only and customer-revocable — you can inspect exactly what is sent, route it through your own egress, or disable it entirely and operate offline.

Sent back

Product version · aggregate health · license status. Nothing that identifies a person or a record.

Never sent

Your payloads, source systems, documents, credentials, and any personal or regulated data — these never leave.

Audit trail

Every privileged action, recorded as evidence.

Discovery, mapping, approval, promotion, and rollback are each written to a sequenced, signed record — a named actor, a UTC timestamp, an exact diff. It is queryable in-product and exportable for your auditors, so the evidence pack writes itself.

// audit · accounts.v3 · sequenced 14:02:18 discover accounts.wsdl → 47 operations 14:02:24 map deterministic → 47/47 fields 14:02:31 publish openapi 3.1 → /api/v3/accounts 14:02:34 observe live traffic → p50 41ms 14:11:09 approved by a named operator 14:11:09 promote staging → prod 14:11:10 rollback window open → 24h

Responsible disclosure

Found something? Tell us.

We welcome reports from security researchers and customers. If you believe you have found a vulnerability in a Specaria product or in this site, report it privately through our contact form and mark it as a security issue — please do not open a public issue or disclose it before we have had a chance to respond.

We acknowledge valid reports and keep you updated as we investigate and remediate.
Give us reasonable time to ship a fix before any public disclosure.
Do not access, modify, or exfiltrate data that is not yours, and do not run denial-of-service or disruptive tests against production systems.

Report a security issue

Due diligence

Bring us your security review.

Architecture, data-flow, and audit questions from your security team are welcome. Book a session with the founder and we’ll walk your reviewers through the model in detail.

Talk to us Read the privacy policy

Loading…