Your product is ready. The security review is not.
Your buyers' security teams want on-prem, SSO, layered access control, an audit trail, and an answer to what the AI in your product is allowed to do. Building that takes a year of platform work that has nothing to do with your product.
This is the use case behind the fintech engagement.
Three ways to embed it
| Path | What you build | The trade-off |
|---|---|---|
| React SDK | drop our components into your own app | your design system, your components; weeks of work, and you own the front end |
| The API | any front end you like, talking to the engine | any front end you like; you build all of it, and nothing of ours ships |
| Embedded UI | full screens in an iframe: navigation stays inside them, links and clicks are limited to what you allow, and each user and tenant gets a short-lived token | days; our screens, branded per tenant |
Your customers never see Swiftward. Not a logo swap. Colors, fonts, heading sizes, table density, and which parts of the interface exist at all are declared, per tenant and per user. Your own stylesheet sits underneath for anything else. If your integration needs something none of the three cover, the platform is declarative, so adapting it is configuration.
What your buyer's security team gets
On-prem or in-tenant deployment, SSO, access control down to the row and the field, multi-tenancy, secrets handling, and an append-only audit trail.
Governance under your brand
The same engine gives your product versioned policy, shadow testing, human review and a decision record. When your customer stops asking "is it secure" and starts asking "can you prove what your AI did for our users", you answer from that record.
Who this page is for
Healthcare AI, legal AI, fintech, HR tech, accounting AI — anyone selling AI into a regulated industry rather than operating in one. Your problem is getting through procurement, and that is what this page answers.