About
We build the instrument.
Construction is the largest thing people do together and the least measured. We build the instrument that measures it: sensors that see the site as it is, one record that holds the job against them, and a network trained on both that answers to the crew doing the work.
- Founded
- 2019
- Headquarters
- HYDERABAD
- Offices
- 4
- People
- 380
Why we exist
The trade runs on opinions.
Construction is the largest industry on earth, responsible for around 40% of global carbon, and it still settles most questions by asking someone who was there.
Thirteen trillion dollars a year moves through construction, and the answer to what got built this week is still a photograph, a phone call, and somebody's memory of a conversation on level nine. Disputes are settled by whoever kept better notes. Estimates are carried by whoever has been doing it longest, until the day they retire.
None of that is a dashboard problem. It is a measurement problem, and measurement problems are solved with instruments — a level, a total station, a tape that agrees with the drawing. The trade has always trusted an instrument over an argument. It just never had one that could read a whole site, every day, at scale.
So we built one. Drones and ground robots take the reading. One record holds the job against it. A network trained on your own history reads both and tells the person on shift what changed since yesterday, with the frame that proves it. The output is not a prettier report — it is a fact somebody can point at.
$13T
Built worldwide each year
40%
Share of global carbon from the built environment
$1.3T
Construction managed on GroundReality so far
Principles
Four things we hold to.
These are not values on a wall. Each one decides something concrete — what ships, how we price, who gets a login, and which answers the product is allowed to give.
- 01RULE · CITED OR SILENT · 100%
Truth over opinion
Every figure the platform reports points at the frame, the drawing revision, or the clause behind it. If a number cannot be traced to something captured or signed, it does not ship — not in the product, not in a board pack, not in a sales meeting. The uncomfortable answer with a citation beats the comfortable one without.
- 02GSD 1.8CM/PX · RTK ±1.2CM
Instruments over dashboards
A dashboard reports what somebody typed in last week. An instrument measures what is there right now, states its accuracy, and tells you when it is out of calibration. We build the measurement first — RTK fixes, ground sample distance, verified installed quantities — and only draw the chart once the measurement can carry it.
- 03PROFILES 27 · USERS UNLIMITED
Roles over seats
Software gets priced by the seat and used by the role. Charging per login pushes companies to keep the people closest to the work off the system, which is exactly backwards. We price on volume, give every role its own calibrated projection of the same brain, and let the apprentice open the drawing.
- 04TESTED · LIVE JOBS · 4 MIN RULE
Site before settings
Nothing ships until it has survived a wet Tuesday on a live job: gloves on, one bar of signal, a superintendent with four minutes before the huddle. Our engineers walk the site before they open a configuration screen, and every release is used on a real project before it reaches the rest.
Offices
Four control points.
We put offices where the work is: the Brain in Hyderabad, robotics in a city that gets a real winter, and deployment engineers close enough to your sites to be standing on one by Tuesday.
Headquarters
Hyderabad
--:--localSyncing
Platform engineering and the Brain. Every nightly training run starts on this floor.
LAT 17.4062° N · LON 78.4691° ETZ · Asia/KolkataTRAINING 02:00 · 210 PEOPLEAPAC operations
Singapore
--:--localSyncing
Deployment, flight approvals across nine jurisdictions, and the desk that answers overnight.
LAT 1.3521° N · LON 103.8198° ETZ · Asia/Singapore9 JURISDICTIONS · 54 PEOPLERobotics & autonomy
Stockholm
--:--localSyncing
Dock hardware and the quadruped fleet, tested through a full winter before they ship.
LAT 59.3293° N · LON 18.0686° ETZ · Europe/StockholmDOCK + GROUND FLEET · 61 PEOPLEAmericas
Austin
--:--localSyncing
Forward-deployed engineers, close enough to be standing on your site in week one.
LAT 30.2672° N · LON 97.7431° WTZ · America/ChicagoFORWARD-DEPLOYED · 55 PEOPLE
How we work
We start on site, not in settings.
Forward-deployed engineering is the whole method. Every account gets engineers who walk the job before they open a configuration screen, and who stay on the account long after the rollout is finished.
- Day 0DAY 0 · 2 ENGINEERS · 1 LIVE JOB
On the job
Two engineers fly out before a single account is configured. They walk the active site with your superintendent, fly the first mission from the dock, and write down how work actually gets booked today — including the spreadsheet nobody mentions in the kick-off call.
- Week 2WEEK 2 · PARALLEL RUN · 0 RETYPING
The record is live
Cost codes, drawings, the schedule, open RFIs and the last two years of closed ones come across from whatever you run now. Both systems run in parallel until the old one goes quiet on its own. Nobody is asked to retype a job to prove a point.
- Week 6WEEK 6 · FIRST RUNS · 27 PROFILES
The brain has trained
The first nightly runs fold your own history into your own weights. Role profiles are calibrated against outcomes you can check — bids you won, pours that slipped, hazards that became incidents — and each one is scored in front of you before anyone relies on it.
- Quarter 1Q1 · WEEKLY → MONTHLY · 1 ENGINEER
A cadence, not a handover
Weekly sessions with the same deployment engineer through the first quarter, then monthly for as long as you have jobs running. The engineer who walked your site on day zero is the one who picks up the phone in year three.
Careers
Three open roles.
We hire slowly and write the job down honestly. Every role below reports what it actually involves, including the travel and the mud.
Deployment engineer, forward-deployed
AUSTIN · FULL-TIME · TRAVEL 60%You live on jobsites for the first six weeks of every account: walking the tower with the superintendent, flying the first mission, and turning what you saw into a working deployment. Site experience counts for more here than a framework.
Perception engineer, ground robotics
STOCKHOLM · FULL-TIME · HARDWARE IN LOOPQuadruped autonomy and interior capture where there is no satellite fix, no lighting, and a new floor plan every week. SLAM, sensor fusion, and the unglamorous work of keeping a robot upright on a slab with rebar sticking out of it.
Applied research, organizational models
HYDERABAD · FULL-TIME · TENANT-ISOLATEDPer-tenant training, role calibration against real outcomes, and citation fidelity — making sure every answer can be traced to the frame or clause it came from. Small team, long horizon, no pooled datasets to hide behind.
Nothing here fits, but you have spent ten years on sites and can write software, or you can write software and want to spend ten years on sites? Tell us the job you would do.