Enterprise
The planning record, inside your own GIS.
Every plan below Enterprise is a seat: someone signs in and works the leads. Enterprise is a licence for planning and construction intelligence. It puts the live planning pipeline, the strategic-infrastructure pipeline and the area intelligence layer into QGIS, ArcGIS Pro or whatever your team already runs, without a row cap, with a service level behind it and paperwork your procurement can actually read.
What the licence grants
GeoJSON layers, straight into your GIS
The live planning pipeline and the strategic-infrastructure pipeline, served as GeoJSON for QGIS and ArcGIS Pro. Every feature carries a stable integer id, unique across the corpus, so a refresh tells an update from an insert, and pages walk the whole layer exactly once. The planning layer filters by bounding box, authority or change date, and by the building (housing body, construction method, heating fuel), heritage and area (Local Electoral Area, Electoral Division) filters the app uses; the infrastructure layer by bounding box, authority, category and decision. On the infrastructure layer the applicant is on every project and the connection voltage on 55% of them, which is the field worth joining to a network; generating capacity in MW is stated on 5 of 331, so treat it as a bonus rather than a column to plan against.
Area intelligence feed
GET /api/v1/feeds/areas/{lea|ed}.geojson: every Local Electoral Area or Electoral Division in the State as a polygon, carrying its leads, on-site work and pipeline value, its Census 2022 profile (homes built before 1980, oil or solid-fuel heating, vacancy) and its Pobal deprivation score, each beside the national baseline. The lead counts take the same filters as the lead feed, so approved housing body starts by Local Electoral Area is one request. Refreshed weekly and built on CC BY sources. Made for councils, SEAI One Stop Shops and utilities planning where to act next.
The caps come off
A Max seat is held to 5,000 rows a day across export and API reads, which is sized to stop a mirror rather than to serve one. A feed licence removes the row budget entirely and raises the request rate to 20,000 an hour, or higher on a custom plan.
You hold the key, and we never do
We issue the licence to your organisation and send your named contact a one-time link. They sign in and create the API key themselves; it is shown once, in their browser. There is no screen here that reveals it, no way for us to re-send it and no re-issue path, so compromising an account of ours does not yield a working credential of yours. Lost a key? Revoke it and create another within your seats.
The licence has a term, and the term is enforced
Terms of 12 or 24 months. A licence carries an end date, and the keys issued under it expire with it rather than outliving the agreement. Revoking a licence ends every key under it on the next request. Your licence page shows the date, the seats in use and your usage across the term, so a renewal conversation starts from a shared record.
Redistribution rights
Every other plan is licensed for your own organisation's internal use. Enterprise is the only licence under which you may embed, republish or resell the compiled dataset, within the scope your order form sets out.
A written service level
99.5% monthly availability, defined support response targets, a named contact, a maintenance notice period and service credits if we miss. The commitments and their exclusions are published in full rather than summarised.
Procurement paperwork that already exists
A data processing agreement, our security and data-protection posture, the lawful-basis analysis behind the dataset, and a documented erasure and suppression path. Written for a public-body procurement to read, not assembled after you ask.
Onboarding on your geography
A working session on your counties, your network extent and your asset classes, with the filters and the feed URLs set up against them before you integrate.
Where Enterprise sits
Access is governed by the scope on your API key, not by the plan on your account. The two feed scopes are the Enterprise layer, and they are granted with an agreement rather than at checkout. A Max subscription on its own does not reach them, which is why this page exists. Once the agreement is signed we record the licence against your organisation and your named contact gets a one-time link to create the key themselves.
| Scope | Rate | Fields | Feeds & bulk | How it is granted |
|---|---|---|---|---|
| commonwealth | 600 / hour | Public, PII-free | No | Any account, free |
| ent_api | 5,000 / hour | Enriched | No | Included with Max |
| ent_feed | 20,000 / hour | Enriched | Yes, plus bulk | Enterprise agreementEnterprise |
| custom | 120,000 / hour | Enriched | Yes, plus bulk | Enterprise agreementEnterprise |
The controls that come with it
The underlying records are a public statutory register, which is exactly why access at volume needs governing. These are the controls a buyer's data-protection officer will ask about, and they are in place before you ask.
No individual is ever in the payload
Applicant names, agent names and every contact channel are marked never-resold in the licence layer and are stripped at a single choke point on the way out, at every scope including custom. Three in five applications are lodged by a private individual, and for all of them that field comes back empty. This is enforced in code, not by policy.
Every pull is audited, and so is every grant
Each export, keyset page and keyed search writes an audit row naming the account, the key, the row count and the filters applied. Separately, issuing or ending a licence is itself logged against the administrator who did it, with the scope, the seats, the term and the contract reference. The log is append-only and outlives the account, so both halves of the question have an answer: what you pulled, and who authorised you to pull it.
Bulk data carries traceable markers
Every bulk export contains a very small number of marker records unique to your account. They match no real application and hold no personal data, and they exist only so licensed data can be traced if it appears somewhere it should not. We will identify them on request for your data-quality process.
Suppression and erasure flow through
A suppression applied at source removes a name from every downstream surface, including the feeds. The register itself stays with the council, which we do not control, and we say so plainly rather than promising more than we can deliver.
The full posture is in the Privacy Notice and the Terms of Use.
Before we grant a feed licence
A feed scope is the widest access we issue, so it is granted deliberately. This is not a long process and it is not a credit check. It is four questions and an order form.
- 1
Who you are
A named organisation with a company or public-body registration, and a named individual accountable for the key.
- 2
What it is for
The purpose the data serves, the systems it will sit in, and who inside your organisation will reach it.
- 3
What you may do with it
An order form fixing the scope, the term and whether redistribution is granted, alongside the acceptable-use terms. Each of those becomes a recorded field on the licence rather than only a line in a document: the term in particular is enforced, so access ends when the agreement does.
- 4
What happens if that changes
A right of revocation, and a defined process if the audit trail shows use outside the agreed scope. Revocation is immediate and total: the licence and every key issued under it stop working on the next request.
Pricing is by agreement
Enterprise is priced on the scope you need: which layers, what geography, how many keys your teams need under the licence, and whether redistribution is in or out. Terms of 12 or 24 months, because the service level and the processing agreement are commitments on our side too. Tell us what you are trying to put on a map and we will come back with a number and a draft order form.
Every endpoint, parameter and response schema is documented on the API page and in the in-app docs.
Prefer to see it working first? Book a 20-minute demo on your counties, or read how a network team uses it on the utilities page and how councils and public bodies use the area feed on the public sector page.