Greater Sydney · live now ·For developers, owners & government

Where to?
Ask it about Sydney.

A structured model of the city — parcels, districts, roads, amenity. Ask a spatial question, get ranked scenarios traceable back to the data. Minutes, not weeks.

Start Nano trial See how it answers
Live product screenshot
Onthology's live product interface mapping healthcare access by district across Greater Sydney, with the spatial memory panel and query bar visible
Onthology·Greater Sydney —

—

—

    Ranked scenarios

      Evidence chain
      decision → metric → relationship → entity → geometry → source
      Sources & method

        Every screenshot is a live capture from the product · Every answer carries its own sourced, re-runnable evidence chain

        The problem

        The four-day answer.
        Then the four-day answer again.

        A site question lands. You search, you email a collaborator, you wait, you assemble. Four days later there's a spreadsheet and a PDF. Then someone asks what happens if you cap parking — and most of those four days start over.

        /01

        Three to five rounds

        A feasibility case rarely clears its committee first time. Each round sends it back.

        /02

        ~90% rework each round

        Almost none of it is new data. It's the same site with a constraint nobody mentioned at the start.

        /03

        "Where's that number from?"

        The one question a spreadsheet can't answer in the room. So it becomes another round.

        Onthology holds the site, the constraints and the scoring in one place. Change the constraint — not the workbook.

        What's loaded

        Greater Sydney is already in the model.

        You don't build a dataset before you get an answer. The city is encoded — parcels, districts, network, population, walk times — and queryable from your first session.

        55,727
        Cadastral parcels

        Real boundaries with actual geometry and footprint area — screened individually, not by suburb average.

        373
        SA2 districts

        Every district scored and rankable, covering a 5.23 million resident base.

        31,405
        Road segments

        Overture network, weighted by road class, clipped to whatever catchment your question defines.

        15 min
        Walk isochrones

        Real routed walking times per facility, resolved at parcel level — not straight-line radii.

        99,472
        Entities in memory

        Parcels, districts, segments and facilities held as one queryable model, with the relationships between them.

        Yours
        Bring your own

        Upload your portfolio, brief or constraints and Onthology reasons over them alongside the city model.

        Counts from the live Sydney model

        How it answers

        Six steps. Order matters.

        Each step constrains the next. Nothing is generated before the city's own rules have been resolved against it.

        /01

        Intent

        Your question, in plain language.

        /02

        Retrieval

        The parcels, districts and relationships that bear on it.

        /03

        Constraints

        Solved against each other, not one at a time.

        /04

        Scenarios

        Options generated across the surviving space.

        /05

        Scoring

        Each option scored on the outcomes you named.

        /06

        Evidence

        Ranked answers, each traceable to source.

        The solver decides the ranking. The model explains it. Not the other way round.

        Pricing

        Start on the full platform.
        Scale when you need your own data in it.

        Nano
        Self-serve · per user
        $48USD or EUR, per user / month. Billed monthly, cancel anytime.
        • +The full Onthology platform — nothing held back
        • +Greater Sydney loaded and live
        • +Ranked scenarios with full evidence chains
        • +Export for reports and approvals
        Start Nano trial
        Micro
        Teams · your constraints
        ContactPriced to the scope of customisation.
        • +Everything in Nano
        • +Your own datasets loaded alongside ours
        • +Your constraints and scoring criteria configured
        • +Team seats and shared scenarios
        Contact for price
        Enterprise
        Cities · owners · operators
        CustomScoped as a development engagement.
        • +Custom development on your spatial estate
        • +Integration with your systems of record
        • +On-prem or hybrid deployment
        • +Named delivery team and support terms
        Talk to sales

        Before you talk to us

        The questions every evaluation asks first

        Do we need to migrate our GIS data before we can use it?

        No. The back end is your own data store — load population figures, parcels, portfolio data or constraints in whatever format you already hold them. Onthology reads alongside your existing GIS estate; it doesn't require you to re-platform onto it first.

        Does this replace our GIS team?

        No — it's built to sit on top of the team you have. Onthology takes the routine, repeatable requests off their queue (the questions that currently mean a ticket and a wait) so they can spend their time on the analysis that actually needs a specialist.

        How do we know an answer is right?

        Every answer carries the layers used, the source and date of each, the method applied, and a one-click re-run. Site selection is threshold-constrained — your parameters, visible and adjustable — not a black-box recommendation you have to take on faith.

        Can this run on-prem, or keep our data in our own region?

        Yes, for teams that need it. On-prem and hybrid deployment are available, and your data stays in open, non-proprietary formats throughout — it isn't locked into a schema only Onthology can read.

        What does a first engagement actually look like?

        Most teams start with a scoped pilot: your own dataset loaded, a defined set of real questions, and a written evidence report you can take into a room — rather than a lengthy platform rollout before you've seen a single answer.

        Six weeks to find out
        it wouldn't have worked.

        That's a study, not an answer. Onthology screens all of Greater Sydney against your constraints in an afternoon, and re-screens it in minutes when the brief moves.

        Start Nano trial Talk to sales
        AI-Powered Planning and Design, for Better Project Delivery and Urban Developments
        GET STARTED
        JOIN Us
        PRODUCTS
        DBF Mass DBF Hikari DBF Signal
        Industries
        15 Minute City Airports Amenity Planning City Development Compact City Complex Factories Data Centers Educational Campus Electrification Facilities EV Factories EV Sites Fulfilment Centers / Warehouses Hospitals Innovation Centers Laboratories Land Use Prediction Logistic Centers Manufacturing Facilities Masterplanning Medical Centers Ports and Repurpose docks Railway Stations Research Labs Smart Cities Tech Campuses Transport Hubs Vertical Takeoff
        About us
        Team Our culture Our mission Careers Pricing Contact us
        © 2026 DigitalBlueFoam
        Legal Information Privacy Policy Terms and Conditions