Sea.dev runs inside your environment and keeps decisions with your team. On-premises there is no data egress — and we are on a path to the same in the cloud.
Three principles shape how we deploy for lenders and financial institutions.
Deployed on-premises or self-hosted, no data leaves your environment. The platform is built to run inside your own infrastructure — you keep the keys and the audit trail.
In cloud pilots, inference runs on OpenAI, which does not train on data sent through its API. Our roadmap is a fully self-hosted deployment, so cloud runs with no egress either.
Sea.dev surfaces extractions and exceptions for review; it does not make lending decisions. Every correction and rejection is logged, so workflows stay reviewable and governed.
RNHB, a specialist real-estate lender in the Netherlands, runs Sea.dev inside its origination workflow — grounded in its historical data and cleared against an agreed accuracy threshold before go-live, with the credit decision staying with an RNHB employee.
Independent third-party penetration testing every 3–6 months, covering cloud and container security. Most recent assessment Q2 2026; certificate available under NDA.
SOC 2 Type I is underway (Type II to follow). Live posture, policies, and our sub-processor list are on our Vanta Trust Center, with reports under NDA.
Read on this site or download as a PDF for security and procurement teams.
A single-page summary of our posture, deployment models, and compliance.
A detailed overview of deployment, data protection, legal, compliance, and testing.
We'll walk your security and procurement teams through deployment, data control, and the path to self-hosting.