Your exploration data, secured and validated. Ready for your AI.
Load drill logs, assays and QC once. geoDB checks them, keeps the originals, and serves one clean copy to your team, your tools and the AI you already use.
No credit card · first 30 days free · your data stays yours
- Drill collars & surveys38
- Assays from 3 certificates4,882
- Standards, blanks, duplicates212
- Holes missing a survey2 to review
- Claude
- ChatGPT
- Grok
- QGIS
- Leapfrog via ODBC
- iOS & Android
- ALS & any lab
Connect the AI you already use to your exploration data.
MCP (Model Context Protocol) is the open standard AI assistants use to plug into other software. geoDB has an MCP connector: add it once, and Claude, ChatGPT, Grok or any MCP client can work on your real projects.
It reads your drill holes, assays and QC with your permissions, pulls what it needs to run the analysis itself, and writes changes back when you ask. Every write is a dry run first, is sent only after your yes, and can be undone.
https://api.geodb.io/mcp
Steps for Claude, ChatGPT and Grok on the connect page
- Ask in plain English"Which holes cut over 1 g/t Au below 100 m?"
- Analysis on live dataYour AI pulls the tables and runs the stats and charts itself.
- Load a folderSpreadsheets and lab certificates, mapped and checked first.
- Writes with your yesEvery change is a dry run you approve.
- Undo any writeStep back whenever you change your mind.
- Your permissions, loggedIt sees what you can see. Every request is in your access log, under Settings → Connected AIs.
Hiring a consultant or an AI vendor? Give them a grant instead of an export: one project, expiring, logged, and read-only unless you choose to let it write.
The foundation under whatever you run next. Own your data, rent the AI. Open spec: geodb-protocol · geodb-client on PyPI
Enter it once. Never reformat it again.
-
1
Bring it in
Hand over the folder: spreadsheets, lab certificates (even PDFs), field data. Every column is mapped and previewed. Nothing lands until you approve.
-
2
Keep it right
Each assay stays tied to its certificate, lab and detection limit. QC is checked for you, and every change is on the record.
-
3
Use it everywhere
Your team, your AI, QGIS, Leapfrog and your investors all read the same live copy. No more exports.
One database for the whole program.
Your drilling in 3D, minutes after upload.
Holes are desurveyed for you and drawn under your own terrain, in the browser. No export, no desktop licence.
- Drill traces coloured by the element you choose
- Terrain, imagery drape and cross-sections
- Publish read-only, or embed in a dataroom
Logged at the outcrop, not retyped at the motel.
geoDB Field runs offline on iOS and Android and syncs into the same database the office reads.
- Drill logging with your own interval sets
- Samples, structures, photos and GPS tracks
- Works all day without signal, syncs when back
A record that never rounds off the truth.
Every assay stays tied to its certificate, lab, method and detection limit. Standards, blanks and duplicates are checked against their limits for you.
- Original coordinates kept in their own CRS
- Below detection stays below detection
- Nothing silently deleted, full audit trail
Keep the tools you're fast in. Lose the exports.
The QGIS plugin reads and writes the same database as everyone else. Leapfrog connects over ODBC and models from live data, not last month's CSV.
- Two-way QGIS sync, claims included
- Live ODBC in the CRS you choose
- One documented, open API under everything
The dataroom that maintains itself.
Raising, selling or reporting? Share a live room with maps, 3D and documents. New drilling shows up on its own.
- Invites, open links or password links
- Watermarked downloads
- A log of who viewed what, and when
No AI of your own? Petra is built in.
Petra imports your files, checks your QC, runs the geochemistry and draws the figures, on your real project. Nothing lands without your approval.
- Lab certificates in, even PDFs, with QC routed for you
- Standards, blanks and duplicates checked by certificate
- Plots that stay tied to the samples behind them
lossy conversions
Coordinates and lab numbers are kept exactly as you received them. Everything else is derived.
Yours to keep
Your data outlives your subscription. Export all of it, any time, in open formats.
Nothing without your yes
Every import and every AI write is previewed first, and can be undone.
One price per project.
Everything included, for every user. Each project is on one of three plans — change it whenever the work changes.
Holding
Keep the project and its claims in good standing. See, share and export everything, your AI reads it, claims upkeep keeps going. No new geology.
Field
Everything in Holding, plus surface work, mapping, samples, photos and documents, holes up to 100 ft with their logging, and assays and QAQC.
Drilling
Everything, including holes of any depth.
Every subscription includes everything
- Unlimited users & role-based permissions
- Drilling & core logging — DSRs, RC & core, cutsheets
- The full database — assays, certificates, QAQC, methods, labs
- Mobile app for field data collection
- Interactive maps & claims management
- 3D drillholes, surfaces & cross-sections
- Geochemical data analysis
- Petra, your AI geologist — usage scales with your plan
- Reports — sections, figures, PDF & DOCX
- QGIS plugin & ODBC access
- Full API access
- Dataroom publishing for JV & investors
What does geoDB replace?
The spreadsheets, the local database and the file shuffling between them. geoDB is one system of record for drill holes, surveys, samples, assays and certificates, QC, logging, field data, photos, documents and mining claims. Everything else reads from it.
How do I get my existing data in?
Hand Petra, or your own AI assistant, the files you have: CSVs, spreadsheets, lab certificates including PDFs, whole folders. It reads the actual bytes, shows you the mapping and a preview, and nothing lands until you approve. You can also import from the web app's upload screens or sync from QGIS and the field app.
What is MCP, and can my AI change my data?
MCP (Model Context Protocol) is an open standard that lets an AI assistant use other software. Claude, ChatGPT, Grok or any MCP client connects through the geoDB connector at https://api.geodb.io/mcp, with your own permissions. It reads your projects and changes them only when you ask: a dry run first, then your yes, then an undo if you change your mind. Steps for each assistant.
Will geoDB tell me where to drill?
No. Petra is AI for data stewardship — importing, categorizing, QAQC, analysis, figures, reporting. Third parties do AI for discovery. Petra makes your data AI-ready; it never claims to find deposits. Use any targeting vendor you like: they pull clean, QAQC'd data through a grant you control.
Do I have to give up QGIS or Leapfrog?
No. The QGIS plugin syncs both ways from the official plugin repository, and Leapfrog reads your project live over ODBC in the coordinate system you choose. The field app, the plugin and the web app all use the same documented API.
What happens to my data if I stop paying?
It stays intact and exportable. CSV, GeoParquet, the API and ODBC are on every plan, because leaving being easy is why people stay.
Does the field app work without signal?
Yes. geoDB Field on iOS and Android is offline-first: log all day, and it syncs when you are back in range. Conflicts are resolved on the server.
What's coming next?
- In developmentGeostatistics: compositing and variography today; kriging, block models and grade-tonnage are in active development.
- In developmentTechnical reports: NI 43-101, SK-1300 and JORC data sections drafted from the live database, figures included.
Is my data secure?
Access follows your team's roles, every change is audited, and every outside grant is scoped, expiring, revocable and logged. Read security at geoDB for the details and how to report a vulnerability.
Stop touching your data.
Start a project, drop in last season's files, and be looking at your drilling in 3D before the coffee's done.