MX Deposit is the most widely adopted cloud-native core logging platform, and for good reason — modern UX, native mobile apps, deep Seequent integration, and a real-time collaboration model. Most teams that evaluate it end up with a real, working logging workflow. But it’s also $4,800 USD per named user per year, locks you into the Seequent ecosystem, and has known weaknesses around strip logs and data export.
That mix is why “MX Deposit alternative” gets searched. This piece covers seven platforms exploration teams actually choose over MX Deposit, what each one is genuinely good at, and where each one breaks. No vendor wrote this. The goal is to help you pick the right alternative for your program, not avoid MX Deposit for the wrong reasons.
When teams outgrow MX Deposit
Teams that move away from MX Deposit usually run into one of the same issues.
Per-seat pricing is the most common friction point. At $4,800/user/year on a named-license model, mid-sized field crews end up coordinating who’s “logged in” rather than letting everyone log freely. One geologist in the field is manageable; five rotating through one core shed gets expensive fast. Teams with rotating contractors, summer field staff, or part-time consultants feel this immediately.
The MX Deposit → Excel → Leapfrog pipeline is a daily tax for anyone not fully in the Seequent stack. MX Deposit exports cleanly within Seequent. Outside it — to ArcGIS, Datamine, Vulcan, or a bespoke modeling workflow — most teams route data through Excel for reformatting. That intermediate step is where coordinate-system mismatches, column-type drift, and depth-rounding errors sneak in, and where a meaningful chunk of the week goes.
Strip log output is a consistent complaint. MX Deposit’s strip logs are usable but regularly flagged as inadequate for management reporting, government submissions, and investor decks. Teams end up generating final strip logs in a separate application, which means data has to leave MX Deposit cleanly enough to drive that downstream tool — and that closes the loop right back to the export problem.
These are the reasons teams look at alternatives.
The 7 alternatives
1. acQuire GIM Essentials
Best for: Mid-tier exploration teams that want acQuire’s data governance approach without the full enterprise lift.
GIM Essentials launched in mid-2025 as acQuire’s response to a problem they couldn’t ignore: their flagship GIM Suite product is enterprise-grade, priced around $15k+/user/year, requires database administrators, and takes weeks to deploy. Essentials strips that down — same underlying philosophy of centrally managed business rules and audit-quality data governance, but pitched at teams that don’t have a dedicated IT function.
It’s still new, the feature parity with GIM Suite is intentionally limited, and pricing is quote-only. You’re also still buying into the acQuire ecosystem and configuration model — which is a long-term commitment, not a quick experiment.
2. Datamine DH Logger / Fusion
Best for: Operations already running Datamine Studio RM, or multi-country programs that need centrally managed configuration cascading to remote sites.
Datamine’s standout is centralized configuration propagation — a change made at headquarters cascades to every field instance worldwide, no manual updates, no version drift across sites. Fusion supports six languages including Russian, Indonesian, and Portuguese, which matters for global operations. DH Logger is the lighter field-capture front end that feeds the same database.
The technology stack is dated — .NET 4.8, Windows-only, desktop installation required. The Central / Remote / Local database architecture with check-in/check-out workflows is designed for an era before reliable cloud sync. The UI shows its age, and “klunky” is a word that comes up.
3. GeoSpark Core
Best for: Canadian junior explorers and independent consultants on a tight budget who need something proven and affordable.
GeoSpark’s value proposition is hard to argue with on price: CAD $5,800 per project site (one-time), CAD $500 for independent consultants. The support model is equally distinctive — you can email the founder directly and get a real answer. It’s a real database (SQL Server / Access backend) with a working field workflow, and Gold Fields Canada is among the customers who have reached for it on new projects.
Data loss and sync issues are the most consistently cited concern in the field. When two geologists export simultaneously, version conflicts are a real risk. The Access/SQL Server architecture limits how far it scales, there’s no modern browser interface or REST API, and a small team behind the product creates key-person risk for long-horizon programs.
4. maxgeo LogChief
Best for: Australian and African operations that need pXRF integration and automated lab workflows built in.
maxgeo’s plug-in architecture is distinctive: CoreShed for photography, LooK for spatial viewing, SQL Reports for custom reporting, all sitting on the DataShed database. Native pXRF integration with Olympus Vanta and Thermo Fisher Niton streams data directly from handheld analyzers into the logging workflow. Automated assay loading with ALS, Intertek, and SGS handles a bottleneck most competitors leave to manual upload. maxgeo lists 350+ clients and has strong Australian market presence.
The company is mid-transition. LogChief 3.x is a Windows desktop application; LogChief Lite is a newer cross-platform PWA. The dual-product strategy means existing customers are navigating a migration that hasn’t fully landed. Pricing is opaque (quote only), and tight coupling to the DataShed ecosystem means you’re adopting maxgeo’s full stack, not just a logging tool.
5. Micromine Geobank
Best for: Teams already invested in Micromine’s modeling and mine-planning tools who want a unified stack from logging through resource estimation.
Geobank is the data management layer in the broader Micromine ecosystem — drill hole database, validation rules, reporting, and direct hand-off into Micromine for modeling. The AI work Micromine has been publishing (Grade Copilot, hyperspectral case studies) is largely modeling-side, but the data foundation for it is Geobank.
Micromine was acquired by Weir Group in April 2025 for £624M. Large acquisitions often bring pricing changes, product rationalization, and shifting priorities — worth factoring into a multi-year decision. Pricing reportedly runs A$250–300/day per user, which compounds quickly. Geobank-specific content is also limited; most Micromine messaging promotes the modeling tools.
6. 1point
Best for: Cloud-first teams in the Australian/Asia-Pacific market looking for a lighter-weight alternative to the entrenched enterprise platforms.
1point is one of a small number of pure cloud-native geological database vendors. It targets teams that want to skip on-premises infrastructure entirely and aren’t already locked into a Seequent or acQuire ecosystem. Real-time multi-user editing and modern UI conventions put it in roughly the same category as MX Deposit on architecture.
It’s a smaller vendor with less visibility outside its core regional markets, public information is limited, and integration breadth (Leapfrog, ArcGIS, Datamine) is narrower than the larger players. For teams outside Australia/Asia-Pacific, finding local references and support coverage is harder.
7. Blue Butterfly
Best for: Junior to mid-tier exploration programs that need a single source of truth, same-day setup, and a clean path to Leapfrog — without per-seat licensing or specialist IT setup.
Blue Butterfly is a browser-based core logging and data management platform with a cloud PostgreSQL database underneath. Every team member gets their own account against the same live database, with real-time sync and offline fallback. Validation rules fire at the point of entry — depth overlap checks, dropdown constraints, numeric bounds, required-field enforcement — so errors surface during logging, not six months later. Strip logs render directly inside the data table. 3D drill hole visualization is built in. Export to Leapfrog runs as a configured workflow with no Excel intermediary.
It’s a newer entrant relative to MX Deposit or acQuire. Integration breadth is currently strongest for Leapfrog, with ArcGIS and Datamine workflows actively expanding. Teams already deeply embedded in the Seequent stack will find MX Deposit’s in-ecosystem integrations more mature.
Choosing by situation
Seat pricing is the most straightforward decision. Blue Butterfly’s per-project model and GeoSpark’s one-time license remove the seat-counting problem entirely. Datamine and acQuire are quote-only, so that math depends on negotiation.
Already living in Leapfrog? MX Deposit is the path of least resistance — it’s built by the same company. The question is whether MX Deposit’s weaknesses on pricing, strip logs, and non-Seequent exports outweigh that convenience. Blue Butterfly is the closest alternative on Leapfrog-export quality without the Seequent dependency.
Strip logs matter more than people admit until they have to produce one for a board or a regulator. Blue Butterfly, Micromine Geobank, and Datamine (via Report Manager) all generate them directly. maxgeo handles it through plug-ins. GeoSpark’s are customizable but need setup. Avoid platforms where strip logs are clearly an afterthought.
For small teams (2–10 people), Blue Butterfly, GeoSpark, and acQuire GIM Essentials are built — or being repositioned — for this range. GIM Suite, Datamine Fusion, and Micromine assume enterprise context. MX Deposit works technically at small team sizes, but the per-seat math is where it gets uncomfortable.
Offline field work in remote locations is worth testing, not just watching in a demo. MX Deposit, Blue Butterfly, maxgeo, and Datamine all handle offline, but the implementation differs — MX Deposit and Blue Butterfly sync transparently on reconnect; Datamine uses explicit check-in/check-out; maxgeo’s PWA is the newest of the lot. Run it against realistic scenarios before committing.
Multi-country, multi-language deployments are a narrower problem. Datamine Fusion’s six-language support and centralized configuration cascading is hard to match. acQuire is the other serious enterprise option at that scale.
Migration considerations
A few things to get right when moving off MX Deposit:
Export early and validate against a known hole. MX Deposit exports cleanly to CSV, but coordinate systems, depth precision, dropdown encoding, and audit history don’t always survive intact. Pull a small subset of holes first, import them into your candidate platform, generate a strip log and a Leapfrog-format export, and compare against the same hole rendered in MX Deposit. Discrepancies surface here that don’t surface in a feature demo.
MX Deposit timestamps every record — don’t lose that in transit. Whatever you migrate to should preserve that history, either by capturing the original timestamps on import or by recording the migration event as a versioned snapshot. Auditors and JORC/NI 43-101 reviewers will ask about this, and reconstructing it after the fact is a real project.
Re-wire Leapfrog before you switch fully. The biggest workflow risk in a migration is breaking your modeling pipeline mid-program. Build the new export workflow against your new platform, run it in parallel with MX Deposit for a few weeks, and only retire MX Deposit once you’re confident the Leapfrog model rebuilds cleanly from the new source.
MX Deposit is a good product. Teams that evaluate alternatives are typically looking for a different price point, a different integration story, or a better fit for team size — not escaping something broken. Pick the alternative that matches the constraint that’s actually limiting you, not the one with the best demo.
For teams whose limiting constraint is per-seat pricing, specialist setup, or a cleaner pipeline to Leapfrog without Excel in the middle, Blue Butterfly was built specifically for that gap. Browser-based, per-project pricing, validation at entry, real-time cloud sync with offline fallback, and full SQL export of your own data at any time — including on cancellation. If that’s the shape of the problem you’re solving, the product overview covers the rest.
For a broader market view, the 2026 comparison of the platforms exploration teams are actually evaluating covers the same ground in a different frame.