Nothing about your traffic leaves.
Swiftward runs on your own servers and never receives your data. It does not call us either: no usage data, no license check. Anything that does leave, leaves because one of your rules sent it: the prompt goes out when you point a rule at a hosted model. That call is versioned and in the record.
What your team verifies without asking us
| The binary is ours | cosign keyless signature, through the build's OIDC identity |
| What is inside it | SPDX bill of materials, shipped with every image |
| How it was built | SLSA provenance attestation |
| That it is clean | HIGH and CRITICAL scan on the digest, before the image publishes |
| How it holds up under attack | your penetration test, on your deployment. We support it |
| Where your data went | your network logs. Anything carrying your data is a call one of your rules makes |
Where each control is documented
What the audit trail records and how an alteration shows up, how operators sign in and how roles are derived, who may call what at request time, where credentials live, what is kept and for how long, and what happens when the engine is unreachable.
Regulated data
BAA, data processing agreement, residency terms — we work through whatever your legal team needs. There is little to negotiate, because we never receive your data.
Backing a young vendor
On-prem changes the risk: you run the binary yourself, so a problem at our company never takes your system down, and you keep the version you deployed for as long as you want. Source-code escrow is available where your board asks about continuity.
Your review, your format
During a pilot we complete your questionnaire in CAIQ or SIG and answer whatever it asks.