Serving institutions in
ITC · FCDO UK Trade Mission 2026 · ExCeL London Nov 11–12 · Sovereign AI

Your Senior Manager is accountable.
VELA creates the audit trail that proves the decision was sound.

Cloud AI sends your documents offshore on every query — triggering UK GDPR Chapter V obligations, violating FCA data governance expectations, and generating answers no Senior Manager can put their name next to. VELA runs sovereign inside your jurisdiction. Zero outbound calls. Every answer cited to the exact document and clause. The audit trail is the architecture.

FCA · SM&CR · CFATF · CIMA · NIST AI RMF 110 entries · 19-gate verification

Zero data offshore · Compare plans

On-premise · No cloud dependency
Every answer cited to source
Full audit trail · Every query logged
NIST AI RMF mapped

The problem VELA solves

Your institution creates intelligence every day.
Most of it leaves the jurisdiction to answer a question.

When staff query a cloud AI about your policies, your client files, your board minutes — that data crosses a border. It trains a model you don't own. It cites sources it won't show you. VELA closes the gap between the intelligence your institution already holds and the answers your people actually need — without your documents ever leaving the building.

01 — On-Premise Inference

No data leaves your building

Every query runs on hardware inside your jurisdiction. Zero outbound API calls during live inference. Your documents never touch a foreign server — not a configuration, the architecture.

02 — Structural Audit Trails

Every answer is citable in an exam room

Query, retrieved document, generated answer, timestamp — logged at the architecture level. Your compliance officer can trace every response to the source document and the moment it was produced.

03 — Sovereign Data Corpus

You own everything the system knows

Your corpus is markdown files with YAML front-matter. Your index is a standard vector format. Export it, audit it, migrate it — without VELA's involvement. No vendor lock-in by design.

Who VELA is built for

The Compliance Officer

You are accountable for the answers your institution gives regulators. VELA gives you answers with citations, logged timestamps, and an audit trail built at the architecture level — not bolted on after.

The Regulated Institution

Trust companies, financial service providers, law firms — any institution where the quality of the answer carries legal weight. VELA runs on your hardware, cites its sources, and never guesses.

The Government Agency

Ministries and agencies carrying the mandate to demonstrate that Bahamian-built AI infrastructure meets international standards. VELA is the operational proof — sovereign, compliant, and running now.

How VELA works

01

Your documents — indexed in your building

Policies, board minutes, compliance frameworks, client files — your corpus, structured and indexed on hardware inside your jurisdiction. Nothing leaves. Nothing is shared. The index is yours to keep.

02

VELA answers locally, every time

On-premise inference. Every query runs against your documents on hardware inside your building. The answer cites the source document, records the page, and logs the timestamp — automatically.

03

Your audit trail is always current

Every query, retrieval, and answer is logged structurally — not as a feature, as the architecture. When the examiner asks, the record exists in the system. Not in a person's inbox. Not conditional on anyone's memory.

Pillar 01 — On-Premise Inference

Answers that never leave the building.

Cloud AI sends your documents to a foreign server every time someone asks a question. VELA inverts this. Your corpus is indexed locally. Inference runs on hardware inside your building. The answer is generated without a single outbound API call. Your documents stay in your jurisdiction — not as a setting you configure, as the architecture you're running on.

VELA Engine — Document intelligence
AML_Manual_2026.md — Ingested
847 chunks · In-jurisdiction · Indexed 08:01
Live
Board_Minutes_Q3_2026.pdf — Indexed
Cited 3x today · Source verified
Cited
Inference node — Online
0 outbound calls · No cloud dependency
Secure
Corpus health — this session
47 queries answered · 143 sources cited
Healthy

VELA Engine — Audit trail
Query logged — 09:14:22
"AML threshold on beneficial ownership" · Operator: N. Astwood
Logged
Source cited — AML_Manual_2026.md · §4.2
Retrieved · Traceable · Examiner-ready
Cited
Answer verified — Threshold 25% or greater
Citable · No hallucination · Audit entry created
Verified
Audit log — 47 entries today
Exportable · Examiner-ready · 0 gaps
Export

Pillar 02 — Structural Audit Trails

Every answer your institution gives is traceable.

VELA logs every query, every retrieved document, every generated answer, and every timestamp — at the architecture level, not as a feature toggle. This is not a compliance add-on. It is the way the system works. When the examiner asks for the record, it is in the database. Not in a person's inbox. Not dependent on whether anyone kept the email.


Pillar 03 — Three Jurisdictions. One Sovereign Architecture.

UK GDPR Chapter V. SM&CR. CFATF. CIMA. All answered by the same architecture.

UK institutions cannot use cloud AI without triggering a GDPR Chapter V cross-border transfer obligation — the Bahamas has no ICO adequacy decision. Caribbean institutions face CFATF fifth-round mutual evaluations that demand documented, auditable compliance evidence. US-linked offshore entities face FinCEN BSA scrutiny that flows upstream from the Cayman entity to the New York relationship. VELA's answer to all three is the same: your data never moves. The obligation never arises. The audit trail already exists when the examiner arrives.

VELA Engine — Sovereignty status
Inference — Local · Nassau
0 bytes sent offshore · All queries on-premise
Sovereign
Open standards — NIST AI RMF
110-entry governance register · Auditable
Mapped
Exit rights — Corpus exportable
Markdown · FAISS · No vendor lock-in
Yours
Open-standards conditions — 6 of 6 met
Architecturally verified · Not a claim
Verified
Built on
110
NIST AI RMF governance entries
Every architectural decision documented: what was proposed, why it was chosen, what tradeoff was accepted. Nightly-verified. FCA supervisor-ready.
19
Automated verification gates
Every query, retrieval, and answer passes 19 automated checks before it reaches your compliance officer. Not a toggle — the architecture.
0
Data sent offshore during inference
Not a configuration option. The architecture. Every query runs on hardware inside your jurisdiction. Zero outbound API calls during live operation.

VELA vs. the cloud alternative

Your data never had to leave.

Cloud AI — ChatGPT, Copilot, Gemini

Data leaves your building

Every query trains a model you don't own

Documents cross a foreign border
No audit trail of queries or sources
Answers uncited — hallucination risk
CFATF examiner has no traceable record

Offshore AI vendor — managed hosting

Data still leaves the region

Contractual assurances, not architectural ones

Managed infrastructure
Data jurisdiction unverifiable
Exit rights depend on vendor cooperation
Audit trail depends on their logging

VELA — On-premise · Nassau

Data stays in your building

Architecture, not a contract. Verifiable, not promised.

Zero outbound calls during inference
Every answer cited to source document
Structural audit trail — examiner-ready
Exit rights structural — corpus is yours

Common questions

What institutions ask before deploying.

It means the model runs on hardware inside your building — not a cloud server, not a regional data center, not a managed third-party host. When your staff asks VELA a question, the query never leaves your network. The answer is generated locally and returned locally. Zero outbound API calls during live inference. This is not a configuration option. It is the architecture.
Each institution's documents are indexed in a separate corpus. There is no cross-contamination between clients — no shared embeddings, no data from another institution's files touching yours. Your documents are indexed on your hardware, in your building, under your control. The index is a standard FAISS format you can export, audit, or migrate at any time without Cova's involvement.
Yes. Every query, every retrieved document, every generated answer, and every timestamp is logged at the architecture level — not as a feature toggle, as the way the system works. Your compliance officer can trace any answer to the exact source document and the moment it was produced. This is the record a CFATF examiner asks for. It is in the database. Not in a person's inbox.
Every architectural decision in VELA is documented in a 110-entry governance register using the NIST AI Risk Management Framework as a reference standard. Each entry follows a three-part form: what was proposed, why this structure was chosen over the alternatives, and what tradeoff was accepted. A procurement officer, auditor, or regulator can read any entry and verify the implementation against the stated standard. The knowledge is in the documentation — not in the builder's head.
There is nothing to exit from. Your corpus is markdown files with YAML front-matter. Your index is a standard FAISS vector format. Your audit log is plain text. Every artefact the system runs on is in formats readable without VELA's involvement. You cannot be locked out of what you already own. Exit rights are structural, not contractual — that is the difference between a vendor promise and an architectural fact.

Your institution's documents.
Answerable. Auditable. On-premise.

VELA handles the intelligence layer your compliance team needs — without your documents leaving the jurisdiction. On-premise inference. Every answer cited to source. Structural audit trails. Built in Nassau, running now.

Schedule a Demo → Talk to Nicolas →

Government or regulated institution? VELA meets six open-standards conditions for institutional technology procurement — architecturally, not as a claim. See the architecture →

VELA — Sovereign AI for Caribbean institutions. On-premise inference.

Every answer cited  ·  Full audit trail  ·  Zero data offshore