About Feasibly
Australian planning data was already public. Nobody had codified the council-specific rules. So we did.
Feasibly is the screening layer that runs before a planner does. Address in. Zone, schedule, overlays, envelope, source links out. One credit, one site.
The thesis
A property professional sees a site, gets excited, hires a town planner for $1,500–$3,000 of desktop review. Two weeks later the same answer comes back on dead-end sites. The information to screen those sites was already public: what was missing was the layer that read it for you.
A property professional sees a site, gets excited, hires a planner for $1,500–$3,000 of desktop review. Two weeks later: wrong zone, killer overlay, council schedule kills the density.
That information is publicly available: Vicmap, council ordinances, state spatial APIs. But it's scattered, written in planning-scheme English, and requires you to know which clause to read.
One address in. Zone, schedule, overlays, envelope, source links out. Get an answer in eight seconds, only call the planner on sites that pass. Step one of due diligence, not a substitute.
Classification
We're explicit about this on every response, in marketing copy, in the disclaimer block. The boundary keeps the product honest and keeps you out of trouble.
It is
A screening tool that helps you decide which sites are worth investigating with qualified professionals.
It is not
Not a substitute for a town planner, surveyor, architect, or lawyer. Always verify with the relevant council before making decisions.
By the numbers
Coverage isn't uniform across Australia and we're honest about that. Victoria is schedule-deep; the other six states are state-API-deep. Both are real depth tiers, just different shapes.
Methodology
Three principles applied on every response, every endpoint, every state. They're what a credit actually buys you, not an opinion, a measurement.
All screening data comes from official sources: Vicmap Planning, NSW EPI APIs, SA PlanSA Code, QLD council endpoints, WA SLIP, ACTmapi, theLIST. We don't guess zones, we don't infer them. Every value is traced to its source URL and tagged in the _meta block.
Victorian Planning Provisions are uniform statewide, but every council overrides them in their own schedules. Min lot size in Yarra GRZ1 isn't the same as Brimbank GRZ1. We codify those overrides: 790 schedules across 79 VIC councils, so the answer Feasibly returns is the answer the council would.
Every parameter ships with a confidence tag: verified_schedule, verified_vpp_default, or unverified_vpp_default. If we read the schedule and confirmed the value, you see it. If we couldn't verify, we say so. See full coverage.
Production validation
Feasibly is an independent planning-data company. Its production validation environment is SQM Architects, a practising Australian architecture firm (a separate company) that runs its client feasibility work on Feasibly daily: the same lookup, the same citations, the same wrong-zone guarantee you get. If a schedule is wrong, it gets hit on a live project before you ever see it.
Feasibly is an independent product, not an architectural service: separate ABN, separate brand. That keeps the data neutral infrastructure any professional can rely on, whichever side of a deal they're on.
Every schedule we codify is one SQM depends on for real client work. There is no special version with better data: the tool you screen with is the tool SQM screens with.
When a live project surfaces a wrong value, it becomes a permanent dataset fix, published in the changelog. Production use is our QA loop, not a marketing line.
Free tier. No credit card. 20 lookups per month, every month.
If we get the zone wrong, that lookup is free and we credit ten more.