Studio is where the project comes together. Connect the systems you run, let Aquifer AI relate them into one model of the project, and build the pages, maps and dashboards everyone reads from it. Describe what you need, review the draft, approve the version.
Add Procore, the ERP, the schedule, drawings, models, point clouds and GIS as Sources. Aquifer AI relates them, so a commitment, its RFIs, its drawings and its place on the site belong together.
Charts, tables, numbers, record details, forms and maps in 2D or 3D, laid out for a laptop and a phone. Every block reads from the model, so the numbers agree across pages.
Describe the page, the layer or the query in a sentence and Aquifer AI drafts it. Every change it makes is labeled, and anything that touches several objects waits for your review.
Fix a status, a superintendent or a set of coordinates as a draft correction or apply it now. Each correction carries a receipt and can be reverted. Every approved change is a version.
The work of building pages, layers, maps and queries moves to Aquifer AI. What stays with you is the part that matters, deciding what is true and what gets published.
"A page with open RFIs by project and a map colored by status." "A layer of sites from the projects table." One sentence, and the draft appears in your project.
Aquifer AI maps the Sources you connect into one model of the project, so the page it builds reads commitments, RFIs, drawings and sites that already belong together.
What Aquifer AI changed is marked Changed by Aquifer AI. A change to one object lands in your draft. A change to several objects waits as a suggestion you accept or discard.
Propose version, read the before and after, approve. The approved version is what Canvas shows, and you can revert to any earlier one.
The YAML and SQL behind any object are one toggle away. Read them, edit them, or paste your own. Nothing the AI does is hidden from you.
The same app, used by the owner, the general contractor and the subcontractor. One example each.
One Source per contractor system, related into one model of the program. The analyst describes the portfolio page and the asset map, approves them, and the program office reads them in Canvas.
Procore, the ERP and the drawings become one model of the project. The project map, the operations page and the owner report are built once and read by everyone, and a wrong site status is corrected with a receipt.
Job cost and billing status from the accounting system, laid out on a page the office reads every morning, with a public link for the general contractor when it is asked for.
Procore, the ERP, the schedule, drawings, models, point clouds and GIS come in as Sources. Aquifer AI relates them into one model of the project, and everything you build reads from it.
Connect a Source and add data from its tables, or upload a file. A preview of real rows and a small map show what you are adding before you add it.
Layer kinds for GIS features, drawings (DWG, DXF, DGN, PDF), models (IFC, RVT), point clouds (LAS, LAZ, E57), imagery and terrain. Color any layer by category, with a legend.
Maps in 2D or 3D with saved views and a timeline. Your view stays personal until you save it as the default for everyone.
Chart, table, number, record details, image, control, form and map blocks, with a live preview of the laptop and phone layouts before anyone reads it.
Propose a version, read the before and after, approve it to publish. Revert to any version at any time. Canvas always shows the approved one.
Correct a status, a superintendent or coordinates as a draft correction or apply it now. Each correction has a receipt and can be reverted.
Aquifer AI edits your draft and labels every change. Changes that touch several objects wait in Review until you accept or discard them.
Share a page by reader link or public link, or embed it with a ready-made snippet for Procore, Autodesk Construction Cloud, Salesforce, NetSuite, Acumatica and Sage Intacct.
View, edit or compare the YAML and SQL behind any object, or paste your own. The curtain lifts whenever you want it to.
Sheets show drawings on paper at true scale with markups. Diagrams are nodes and connectors bound to live data, so they stay right as the data changes.
A tool catalog, visual models and a schema designer. Publish feature, tile and OGC services. Export Shapefile, GeoPackage, GeoParquet, CSV and File GDB. Print layouts with map series.
Procore, the ERP, the schedule, ArcGIS, drawings and models. Aquifer AI relates them into one model of the project.
A page, a layer, a map or a query, in a sentence. Aquifer AI drafts it, labels its changes, and waits where you need to decide.
Read the before and after, approve, and the version is what Canvas shows. Correct a record later with a receipt, or revert.
Pricing follows what you use. Every part of the platform can be taken on its own and kept in sync with the systems you already run. Talk to us about pricing for your company.
Talk to us →Who uses Studio?
The people who own reporting for a project or a program. Operations and project controls, finance, data and GIS staff, in any kind of company on the project. Everyone else reads what they build, in Canvas.
Do I need to know SQL or YAML?
No. Describe what you need and Aquifer AI builds it. The YAML and SQL stay one toggle away for anyone who wants to read or edit them.
What does "one model of the project" mean?
Aquifer AI relates the Sources you connect, so a commitment, its RFIs, its drawings and its place on the site are linked. Pages, maps and queries read from that model, which is why the numbers agree.
What if Aquifer AI gets something wrong?
Every change it makes is labeled and reviewable. A change to several objects waits as a suggestion until you accept or discard it, and any approved version can be reverted.
How does a page get to Canvas?
Approve a version in Studio and Canvas shows it. Readers see the approved version, with its number and when its data was last updated.
Which file formats can I bring in?
GIS formats (Shapefile, GeoJSON, GeoPackage, GeoParquet), drawings (DWG, DXF, DGN, PDF), models (IFC, RVT) and point clouds (LAS, LAZ, E57), alongside the systems connected through Integrations.
We use a small number of first-party cookies to understand which pages visitors find useful. No advertising, no third parties. Privacy notice
