Enterprise DNA

Instead of MX Deposit

Stop renting MX Deposit. Own your drillhole database.

We build your version around how your exploration team logs, samples and reports, bring your MX Deposit data across and run it for you.

MX Deposit lists US$3,705 a year for each Standard user, US$5,055 for a Shift licence two people share and US$1,265 for each read-only Reviewer, excluding tax.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

A licence for every geologist, every year

Seequent publishes its MX Deposit prices. They show how the bill is built: one named licence per person, renewed every twelve months.

badge

Every logger licensed

Each Standard user who logs, imports or edits data is US$3,705 a year, excluding tax.

groups

Shift crews share at a price

Two people on opposite shifts can share one licence for US$5,055 a year, as long as only one is signed in.

visibility

Even reading costs

A manager or consultant who only needs to look is a Reviewer at US$1,265 a year.

event_repeat

Twelve months, then again

Only twelve-month named licences are sold online. Shared and enterprise licences are quoted on request.

engineering

The database person on top

Most junior explorers still pay a database consultant to load lab files, chase QAQC and build reports.

lock

Your drilling, their system

The holes your company paid to drill, and the results you report to the market, live inside a vendor's system.

Your own drillhole database

Ask about holes, results and QC in plain words

QAQC

Bad standards caught first

Every standard is checked against its certified value, every blank against the detection limit, every duplicate against its original, the moment results load.

  • check Standards outside three standard deviations flagged, with the batch
  • check Blanks carrying grade found after a high-grade run
  • check Field duplicates that do not repeat, with the difference
  • check Batches sent short of your standards, blanks or duplicates

Samples and the lab

Know where every batch is

The sample sheet, the lab batch and the results stay joined, so nothing sits at a lab unnoticed.

  • check Sample tickets with standards, blanks and duplicates at your rates
  • check Batches with no lab receipt after a week
  • check Batches at the lab past your turnaround, with a chase drafted
  • check Lab results files loaded with below detection kept as below detection

Results

Intercepts ready for the release

Significant intercepts are worked out from the samples at your cut-off and dilution, with the collar list beside them.

  • check "5 m @ 3.22 g/t Au from 31 m" written for you
  • check Holes with results pending listed, not left out
  • check Open QC failures listed above the intercepts
  • check A draft for the competent person, never released from here

Tenements and the field

Reports and rehabilitation on time

Each tenement's anniversary sets its report date, and each hole carries its collar survey, cap and rehabilitation date.

  • check Annual reports due within 45 days, and any overdue
  • check The collar, survey, geology and assay data for the report, laid out
  • check Holes still at their planned collar or with no downhole survey
  • check Holes not capped, and rehabilitation due within a month

Make it yours

Design your own MX Deposit replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from MX Deposit. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your MX Deposit replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your MX Deposit data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from a fictional demo gold project. Ask about QC, intercepts and the lab, then see the records behind each answer.

forum

Drillhole Data for Claude Code

Connected to your own database

Did the standards, blanks and duplicates pass in batch KR-D001?

standards

KR90001

Standard
CRM-LOW
Dispatch
KR-D001
Element
Au
Value
0.53
Certified_value
0.52
Z
0.50
Result
pass

KR90002

Standard
CRM-HIGH
Dispatch
KR-D001
Element
Au
Value
2.41
Certified_value
2.10
Z
4.43
Result
fail

KR90003

Standard
CRM-LOW
Dispatch
KR-D001
Element
Au
Value
0.50
Certified_value
0.52
Z
-1.00
Result
pass

blanks

KR90004

Dispatch
KR-D001
Element
Au
Value
0.09
Detection_limit
0.01
Result
fail

duplicates

KR90005

Original
KR10010
Dispatch
KR-D001
Element
Au
Original_value
0.020
Duplicate_value
0.02
Diff_pct
0.0
Result
pass

KR90006

Original
KR10035
Dispatch
KR-D001
Element
Au
Original_value
4.80
Duplicate_value
2.90
Diff_pct
49.4
Result
fail

KR90007

Original
KR10050
Dispatch
KR-D001
Element
Au
Original_value
0.74
Duplicate_value
0.69
Diff_pct
7.0
Result
pass

Ask it anything

Ten questions your drillhole database answers

Each works against the records in the free version today. Your version adds your own.

chat_bubble Which standards in last month's batches fell outside three standard deviations?
chat_bubble Which batches went to the lab short of standards, blanks or duplicates?
chat_bubble Which batches has the lab had for more than 21 days with no results?
chat_bubble What are the intercepts above 0.5 g/t with 2 m of internal dilution?
chat_bubble Which completed holes are still at their planned collar or have no downhole survey?
chat_bubble Which tenement reports fall due in the next 45 days, and which holes go in each?
chat_bubble Which holes are not capped, and which are due for rehabilitation?
chat_bubble Do the driller's metres for September match the holes we completed?
chat_bubble Which RC samples have no recovery recorded?
chat_bubble Which holes have gaps or overlaps in their geology log?

Switching

How to switch from MX Deposit

A move involves exporting your MX Deposit tables, mapping the records you need, testing the import, and checking both systems side by side before switching.

  1. 1

    Export your MX Deposit tables

    Export each table from MX Deposit as a CSV in one ZIP. Include holes, downhole surveys, geology, samples with standards, blanks and duplicates, and results. Dispatch dates, certified values, core photos and custom tables need separate handling, so include the records you rely on in the migration scope and check with MX Deposit if you are unsure what your account allows.

  2. 2

    Preview the import

    Before loading the records, run the import's test preview. It offers a dry run, so you can check the export before records are loaded. Use this pass to see what needs attention and identify custom fields or records that may need mapping. Do not treat the preview as the completed migration. It is a chance to resolve issues before the live load.

  3. 3

    Review flagged records

    Check every warning or flagged record from the import, then decide how to handle it before loading. Pay particular attention to dispatch dates, certified values and custom tables, which need a step each, as well as any fields your team has added. Make sure the chosen handling matches how you use those records, rather than leaving gaps without a decision.

  4. 4

    Load and compare records

    Load the export after the preview and flag review are complete. Keep MX Deposit available while you check the loaded records against it. Compare holes, surveys, geology, samples, QC and results, and check the batches or records your team still needs to work with. Run both systems side by side for a short period so your team can spot issues before relying on the new database.

  5. 5

    Switch off MX Deposit

    When your checks are complete and the team is working from the new database, make it the system of record and stop entering new data in MX Deposit. Arrange the end of your MX Deposit use through your own account process. Keep any export or records you need for your business, reporting or future reference.

construction

Where the real effort goes

The main work is usually mapping your own fields and rules, then deciding how much history to bring across. Standard records have an import path, but dispatch dates, certified values, core photos and custom tables need individual handling. If you have Enterprise DNA run the migration, they handle the mapping and import work as part of the switch.

Not ready for a call?

Get your MX Deposit switch plan by email

We will send you the step-by-step plan for moving your business off MX Deposit, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose who builds and runs your version

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone the repo and run npm install
  2. 2 Run npm run demo and ask Claude Code what needs attention
  3. 3 Works with Claude Code, Codex, OpenCode or Cursor
  4. 4 Import an MX Deposit export of CSV files
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your projects, tenements, standards, cut-offs and QC limits
  • check Your MX Deposit holes, samples and results brought across and checked
  • check A tablet logging form for the rig if you want one
  • check Your lab's results format and your state's reporting rules
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Lab files loaded and QC checked as they arrive
  • check Backups, support and changes as the programme grows
  • check The report dates and rules kept current
Talk about your project

Questions

Instead of MX Deposit, answered

What comes across from MX Deposit? expand_more

MX Deposit exports each kind of record as a spreadsheet file in one download. Holes, downhole surveys, geology, samples with their standards, blanks and duplicates, and results come across. Batch dates and certified values need a step each, and we map any custom records for you as part of the switch.

Our geologists log at the rig on a tablet. What happens to that? expand_more

The free version takes the log sheet as a spreadsheet, or one interval at a time. If your team logs on a tablet, we build a logging form on the same records as part of your version.

Does this replace our competent person? expand_more

No. It checks the records against the parts of the JORC Code checklist that show in data, such as recovery, logging, collar surveys and QC, and drafts the intercepts for the release. The competent person still reviews and signs off before anything is released.

Does it work outside Western Australia? expand_more

Yes. The report date, the datum rule and the rehabilitation period are settings. We set them to your state or to New Zealand, and add your own tenement conditions as checks.

What does Enterprise DNA charge? expand_more

One setup fee, then a retainer for the agreed work. Sam looks at your current licences, your labs and the reports you produce before setting the scope. The free version has no licence fee; hosting and agent subscriptions cost what they cost.

What would your own drillhole database look like?

Spend 30 minutes with Sam going through your MX Deposit renewal, one project and the jobs your team does each week. We agree what to bring across, what to build around it and how we run it for you.

Book a 30-minute call Get the free version

Drillhole Data for Claude Code is free and open source, published by Enterprise DNA.

Done paying for MX Deposit?

Get your version built