Your pass to private datasets.
Traditional Sharing vs DataPass
๐ฅ
Traditional
Share dataset
โ
User downloads everything
โ You lose control of your data
๐
DataPass
User asks question
โ
Gets only the answer
โ Data stays private on HF
MCP Does the Heavy Lifting
When a subscriber asks a question, here's what happens behind the scenes:
1
User asks: "What are the top 10 categories?"
2
DataPass validates the access token
3
LLM converts question to SQL
4
DuckDB queries parquet files on HF
5
Only the result is returned to user
The user never sees the SQL, never touches DuckDB, never accesses HF directly.
Why DataPass?
For Dataset Owners
- ๐ Keep your data private
- โฑ๏ธ Grant time-limited access
- ๐ซ Revoke anytime
- ๐ฐ Monetize with Stripe
For Subscribers
- ๐ฌ Query with SQL or plain English
- โก No setup - just use MCP tools
- ๐ Get answers, not giant files
- ๐ Works with Claude, Cursor, etc.
Security Model
๐๏ธ
Dataset files never leave Hugging Face
๐ซ
DataPass validated on every request
๐
Results capped - no SELECT * dumps
DataPass โ Your pass to private datasets.
Powered by Hugging Face & MCP