Research infrastructure built for citation and care
Your research dataset deserves provenance, version history, and a home you control. ParseQuest is built to make that possible.
Why ParseQuest exists
Researchers, journalists, and archivists need datasets they can cite, defend, and reproduce. ParseQuest provides the infrastructure: provenance on every record, version history, and storage you control.
Your browser session does the capture. Your machine stores the results. You own the dataset - citable, portable, and built to last.
Principles
Credentials stay local. Authentication happens on your machine. ParseQuest never sees your passwords, tokens, or session data.
Your research, your device. Captures are stored locally by default. You decide what, if anything, leaves your machine. Cloud sync is optional and covers records only.
Every record is versioned. Results are stored as versioned files with provenance. Changes create a new version rather than editing in place, so your history stays intact. Deletion is available when you need it.
Roadmap
- Local collector for X (Twitter)
- Versioned record storage (JSON)
- Basic export (CSV/JSON)
- Single workspace per user
- Async push to ParseQuest Cloud
- Full-text search across collections
- Cross-device workspace access
- Version history viewer
- Shared collections within a team
- Role-based access control
- Activity timeline
- Team-level export
- Additional platform collectors
- Import support for sanctioned data sources
- Provenance across data sources
All future collectors follow the same principles: user-present, rate-respecting, local-first.