Instead of gINT
gINT is being retired. Own your geotechnical database.
We build your version around how your engineers log, test and report, bring your gINT projects across and run it for you, instead of moving everyone onto another per-seat subscription.
Bentley's Australian store lists gINT Professional from AU$3,360 and Professional Plus from AU$4,675 per user for 12 months, and says gINT is being retired in favour of OpenGround.
- 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 seat for every engineer, then a forced move
Bentley publishes its gINT and OpenGround prices. They show how the bill is built: a subscription per person, and now a cloud platform on top.
Every logger on a seat
gINT Logs starts at AU$1,040 per user for a 12-month subscription, just to produce logs.
Reporting costs more
Fence diagrams and 3D views are gINT Professional, from AU$3,360 per user. Lab testing calculations are Professional Plus, from AU$4,675.
The product is ending
Bentley says gINT is being retired, will no longer be sold or updated, and that staying on it means relying on an unsupported system.
The successor is a platform fee
OpenGround needs a cloud service first, from AU$3,595 for Band 1, or AU$19,055 for i5 Band 1 if you want the API.
Then a seat each again
Every OpenGround user is bought on top of the cloud service: AU$365 for Base, AU$1,055 for Advanced.
Your ground data, their system
Years of boreholes, logs and lab results your clients paid for move from one vendor format to the next, on the vendor's timetable.
Your own geotechnical database
Ask about logs, tests and the lab in plain words
Logging
Logs checked before anyone signs them
Each stratum is checked against the field description guidelines as it is logged, and every log runs from the surface to its final depth.
- check Soil without a strength, density or moisture term flagged as it is logged
- check Rock without weathering or strength flagged
- check Gaps and overlaps in a log found, and a log short of the final depth
- check Sign-off refused for the person who logged it, or while checks are open
In situ tests
SPT and vane results you can trust
N is worked out from the blows and refusal is caught, and every shear vane carries its sensitivity.
- check Recorded N values that do not match the blows
- check Refusal recorded when an increment reaches 50 blows
- check Vanes with no remoulded reading, so sensitivity is missing
- check Every soil with a sensitivity of 8 or more, across every job
Samples and the lab
Know where every tube is
Samples, lab schedules and results stay joined, and the standard method for New Zealand or Australia is filled in when a test is scheduled.
- check Undisturbed tubes sitting more than a week unscheduled
- check Schedules with no lab receipt, and results past due with a chase drafted
- check Tests with no method stated, and labs with no IANZ or NATA number
- check Moisture content, Atterberg limits, fines and CBR side by side with the soil type
Reports and the NZGD
Factual reports and uploads on time
The factual report schedules come straight from the records, and uploads to the New Zealand Geotechnical Database are tracked to the day.
- check Location, strata, SPT, vane, groundwater and lab summaries laid out for the report
- check Locations started with no services check, or finished with no surveyed position
- check NZGD uploads due and overdue, with the AGS4 file written for upload
- check Reports issued without a reviewer, or reviewed by their own author
Make it yours
Design your own gINT replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from gINT. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your gINT data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real answers from three fictional demo projects in Takapuna, Christchurch and Brisbane. Ask about the logs, the lab and the database uploads, then see the records behind each answer.
Geotechnical Data for Claude Code
Connected to your own database
What needs fixing across our projects before we report?
COORDS
- Project
- HV26
- Subject
- TP01
- Issue
- Coordinates are still the planned position
FD_ROCK
- Project
- LR
- Subject
- BH01
- Issue
- Rock 6.0 to 9.0 m has no weathering
FD_SOIL
- Project
- HV26
- Subject
- BH02
- Issue
- Stratum 0.6 to 4.0 m has no moisture
GROUNDWATER
- Project
- HV26
- Subject
- TP01
- Issue
- No groundwater observation recorded, not even "not encountered"
LAB_ACCREDITED
- Project
- HS3
- Subject
- Riverside Testing
- Issue
- Schedule LS-HS3-01 went to a lab with no accreditation number on file
LAB_LATE
- Project
- HV26
- Subject
- LS-HV26-01
- Issue
- Results were due 2026-10-25 from Otahuhu Soils Lab: 3 of 5 tests in
LAB_METHOD
- Project
- HS3
- Subject
- HA01
- Issue
- Test PSD on B1 has no test method stated
LAB_RECEIPT
- Project
- HS3
- Subject
- LS-HS3-01
- Issue
- Sent to Riverside Testing 2026-11-02, no receipt after 6 days
LOG_CHECK
- Project
- HS3
- Subject
- HA01
- Issue
- Checked by the person who logged it (Liam Ford)
LOG_CHECK
- Project
- HS3
- Subject
- HA02
- Issue
- Finished 2026-10-30, log not checked after 9 days
LOG_CHECK
- Project
- HV26
- Subject
- BH02
- Issue
- Finished 2026-10-25, log not checked after 14 days
LOG_CONTINUOUS
- Project
- HS3
- Subject
- HA02
- Issue
- Gap in the log from 0.8 to 1.0 m
LOG_CONTINUOUS
- Project
- HS3
- Subject
- HA02
- Issue
- Log ends at 2.2 m but the final depth is 2.5 m
NZGD
- Project
- HS3
- Subject
- CPT02
- Issue
- Finished 2026-09-24, not uploaded to the NZ Geotechnical Database a...
PIEZO_DUE
- Project
- HV26
- Subject
- BH01
- Issue
- Standpipe piezometer reading due 2026-10-30 (last read 2026-10-16)
REPORT_REVIEW
- Project
- HS3
- Subject
- HS3 Factual Report
- Issue
- Issued 2026-11-03 with no reviewer recorded
SERVICES
- Project
- LR
- Subject
- BH01
- Issue
- Started 2026-10-13 with no services check recorded
SPT_N
- Project
- HV26
- Subject
- BH02
- Issue
- SPT at 6.0 m: recorded N=18, blows give N=15
TUBE_SCHEDULE
- Project
- HV26
- Subject
- BH02
- Issue
- Tube U1 at 2.0 m taken 2026-10-24, not scheduled after 15 days
VANE
- Project
- HS3
- Subject
- HA01
- Issue
- Vane at 2.7 m has no remoulded reading, so sensitivity cannot be st...
| Rule | Project | Subject | Issue |
|---|---|---|---|
| COORDS | HV26 | TP01 | Coordinates are still the planned position |
| FD_ROCK | LR | BH01 | Rock 6.0 to 9.0 m has no weathering |
| FD_SOIL | HV26 | BH02 | Stratum 0.6 to 4.0 m has no moisture |
| GROUNDWATER | HV26 | TP01 | No groundwater observation recorded, not even "not encountered" |
| LAB_ACCREDITED | HS3 | Riverside Testing | Schedule LS-HS3-01 went to a lab with no accreditation number on file |
| LAB_LATE | HV26 | LS-HV26-01 | Results were due 2026-10-25 from Otahuhu Soils Lab: 3 of 5 tests in |
| LAB_METHOD | HS3 | HA01 | Test PSD on B1 has no test method stated |
| LAB_RECEIPT | HS3 | LS-HS3-01 | Sent to Riverside Testing 2026-11-02, no receipt after 6 days |
| LOG_CHECK | HS3 | HA01 | Checked by the person who logged it (Liam Ford) |
| LOG_CHECK | HS3 | HA02 | Finished 2026-10-30, log not checked after 9 days |
| LOG_CHECK | HV26 | BH02 | Finished 2026-10-25, log not checked after 14 days |
| LOG_CONTINUOUS | HS3 | HA02 | Gap in the log from 0.8 to 1.0 m |
| LOG_CONTINUOUS | HS3 | HA02 | Log ends at 2.2 m but the final depth is 2.5 m |
| NZGD | HS3 | CPT02 | Finished 2026-09-24, not uploaded to the NZ Geotechnical Database a... |
| PIEZO_DUE | HV26 | BH01 | Standpipe piezometer reading due 2026-10-30 (last read 2026-10-16) |
| REPORT_REVIEW | HS3 | HS3 Factual Report | Issued 2026-11-03 with no reviewer recorded |
| SERVICES | LR | BH01 | Started 2026-10-13 with no services check recorded |
| SPT_N | HV26 | BH02 | SPT at 6.0 m: recorded N=18, blows give N=15 |
| TUBE_SCHEDULE | HV26 | BH02 | Tube U1 at 2.0 m taken 2026-10-24, not scheduled after 15 days |
| VANE | HS3 | HA01 | Vane at 2.7 m has no remoulded reading, so sensitivity cannot be st... |
Ask it anything
Ten questions your geotechnical database answers
Each works against the records in the free version today. Your version adds your own.
Switching
How to switch from gINT
The move involves exporting your project data, checking the import, and running the new database alongside gINT before you switch over.
- 1
Export your projects
Export each project from gINT as AGS4. The import brings across locations, strata, SPTs, shear vanes, samples, water strikes and index test results. AGS4 does not include who logged or checked each log, or services dates, so note that you will need to add those separately as part of the move.
- 2
Preview, then load
Start with the import’s test run before loading the records. Review the preview, then load the AGS4 export into the database when you are ready. You do not need to operate a command line yourself to plan this step. If Enterprise DNA is running the system for you, they handle the import process with you.
- 3
Review flagged records
Check anything the import flags and compare it with the source records in gINT. Resolve issues before treating the imported project as complete. Pay particular attention to the information AGS4 does not carry, including who logged and checked each log and the services dates. Add that information separately, as it is part of the switch.
- 4
Run both side by side
Keep gINT available for a short period while you use the new database for live work. Compare project and location records, logs, tests and results between the two systems, and make sure your team can find and use the records they need. Record any gaps or corrections, then address them before you rely on the new system alone.
- 5
Switch off gINT
Once you have checked the imported records, added the missing information and completed your side-by-side review, move your team’s work to the new database. Keep any gINT records you still need to retain according to your own record-keeping requirements. Stop using gINT for new work when the team is ready to rely on the new system.
Where the real effort goes
The main work is usually mapping your own fields and house rules, then deciding how much history to bring across. AGS4 carries the core investigation records, but some information, such as who logged or checked each log and services dates, needs separate handling. If Enterprise DNA runs the system for you, they do this migration work with you.
Not ready for a call?
Get your gINT switch plan by email
We will send you the step-by-step plan for moving your business off gINT, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your gINT switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to own it
Choose who builds and runs your version
Open source
Do it yourself
Free, MIT licence
- 1 Clone the repo and run npm install
- 2 Run npm run demo and ask Claude Code what needs attention
- 3 Works with Claude Code, Codex, OpenCode or Cursor
- 4 Import a gINT AGS4 export with one command
Built around your business
We customise it
One setup fee, then a retainer
- check Your projects, legend codes, house limits and lab methods
- check Your gINT projects brought across and checked, log by log
- check A graphic borehole log in your practice's layout, and a field logging form if your crews want one
- check Your labs' results formats and your councils' upload rules
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 results loaded and checked as they arrive
- check Backups, support and changes as the practice grows
- check Database uploads and report checks kept current
Questions
Instead of gINT, answered
What comes across from gINT? expand_more
gINT exports projects in the AGS4 format, the same format the New Zealand Geotechnical Database and most labs use. Locations, strata, SPTs, shear vanes, samples, water strikes and moisture content and Atterberg results come across. Who logged and checked each log and the services dates are not in AGS4, so we add them as part of the switch.
Do we still get proper borehole logs? expand_more
The free version prints a clean borehole log for every borehole, test pit and hand auger with your name and logo, plus a factual summary for every project. A graphic log with columns and hatching in your house layout is something we build into your version.
Our loggers fill in sheets on site. What happens to that? expand_more
Most read the sheet out at the end of the day and each stratum, SPT and sample is logged and checked as they go. If your crews want to enter it on a phone or tablet in the field, we build that form on the same records.
Does it work in Australia as well as New Zealand? expand_more
Yes. Each project carries its country, coordinate system and height datum, and the lab method filled in for each test follows the country: NZS 4402 in New Zealand, AS 1289 in Australia. The checks follow the NZGS field description guideline and AS 1726-2017.
What does Enterprise DNA charge? expand_more
One setup fee, then a retainer for the agreed work. Sam looks at your current gINT or OpenGround seats, 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 geotechnical database look like?
Spend 30 minutes with Sam going through your gINT renewal or OpenGround quote, 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.
Geotechnical Data for Claude Code is free and open source, published by Enterprise DNA.
Done paying for gINT?
Get your version built