71 sources, one connection form each, one vault for all of them.
Every connector in the registry declares its fields, which of them are secrets, and how Fletch reaches the system. Secrets are sealed in the credential vault on save and never returned by the API. The list below is generated from the registry at build time, so it cannot drift from the product.
71 shown
Database 29
Applications 11
Lakehouse catalog 7
Object storage 9
Query engine 6
NoSQL & Search 3
Streaming 1
Observability 2
Graph 1
Engine-to-engine 1
Custom 1
Not listed? A REST / HTTP API connector covers systems with a documented endpoint. Databases on a standard wire protocol usually work through the nearest family member. Ask, and we will measure it rather than promise it.
Pick it, fill in the form, test it, vault it.
The gallery shows every family with a search box. Each form carries only the fields that connector needs, with Advanced, Security and Caching tabs for the rest, and a Test connection button that runs the driver before anything is saved.
- Secrets are sealed with AES-256-GCM under a per-owner key
- Object-storage destinations are administrator-only and write-probed
- Connector visibility can be narrowed per group by an administrator
Your sources, in the gallery, before the call.
Tell us what you run and we prepare the demo around it.














