Use cases
Three situations this was actually built for.
Not a list of industries. These are the three problems teams describe to us most often, and the three where the way GetMyData is built — rather than what it promises — is the reason it helps.
Data residency
Bring your own warehouse
Your extractions write into storage you already own and your dbt models build into a warehouse you already pay for. We hold the schedule, the run log and the metadata — never the rows.
Read it →
Network
Reach a database behind the firewall
A self-hosted runner connects outbound only. There is no inbound firewall rule to open, no port to publish, and no VPN back to us.
Read it →
Consolidation
Replace a stitched-together stack
One tool covering extraction and dbt, with one permission model and one audit log, instead of four products and the glue between them.
Read it →
Not sure which one is you?
Walk the getting-started path instead, or tell us the situation and we will say honestly whether this is the right tool for it.