Everything you need to know about IwiConnect, from pricing to compliance, data sovereignty, and how the platform works.
IwiConnect is Aotearoa's national iwi engagement platform. It provides secure, auditable digital infrastructure for managing formal compliance engagement between iwi, hapū, councils, developers, infrastructure providers, and government agencies.
It creates a single, trusted channel for formal engagement requests and responses, with clear time-stamped records.
If you need to demonstrate defensible engagement, this is built for that.
Book a demo to see how the workflow operates in practice.
Engagement was fragmented. Iwi were receiving requests across email, consultants, council teams, and informal channels. Councils and developers struggled to prove what had been sent, when, and to whom.
IwiConnect was built to bring structure, visibility, and accountability to that system without removing iwi authority.
It reduces duplication, protects capacity, and creates audit clarity.
Iwi and hapū use IwiConnect to receive and manage formal engagement within their rohe.
Councils, government agencies, developers, infrastructure providers, planners, and consultants use it to notify iwi and maintain an auditable engagement record.
It is designed for organisational use, not individual consumers.
No. IwiConnect is an independent Māori-led platform. It works alongside council and Crown processes but is not owned or controlled by government.
No. It supports formal compliance engagement. Hui, site visits, tikanga-based engagement, and relationship building continue directly between parties.
The platform ensures the formal compliance layer is structured and recorded.
No. IwiConnect facilitates notification and creates a defensible record. Councils and developers remain responsible for understanding statutory requirements, monitoring timeframes, and ensuring obligations are met.
It strengthens your compliance evidence. It does not replace your legal duties.
Iwi gain:
It supports capacity without interfering in decision-making.
Next step for iwi: Request onboarding information.
You gain:
It simplifies compliance and reduces uncertainty.
Next step: Request a tailored demo for your team.
One engagement covers a project from the moment you submit it to iwi. It includes verified identification of the iwi for the project, the notification to each of them, their review and response, and the compliance report and audit trail.
Once a project is submitted, you and iwi can message, share updates and follow up as many times as you need. Nothing after the first submission is charged, however long the conversation runs.
Submit a request through the website and we will arrange a walkthrough specific to your organisation.
The demo covers project submission, iwi notification, reporting dashboards, governance controls, and audit records.
Iwi onboarding typically takes 1–2 hours including setup and training.
Customer onboarding can be completed within several days once access and billing are confirmed.
Yes. Iwi receive full onboarding and support at no cost. Customer onboarding is included as part of setup.
Enterprise-level onboarding support can be arranged if required.
Customers pre-purchase engagement tokens. Tokens are deducted when formal notifications are submitted. Each token covers one project, including every follow-up with iwi after it is submitted. This creates simple, predictable pricing aligned to engagement volume.
Tokens are non-refundable except where required by law.
Yes. Government and council clients are subject to specific pricing structures based on organisational size, number of authorised users, and estimated annual engagement volumes.
Custom pricing arrangements are available for councils and government agencies. Any agreed pricing structure or procurement terms are documented in the applicable order form.
For bespoke pricing discussions, please contact IwiConnect directly.
Each iwi portal has a formally mandated Owner appointed by the iwi Chair or Chief Executive.
The Owner manages user access, permissions, and workflow settings.
Yes. Role-based permissions allow organisations to manage multiple users with appropriate access controls.
Access can be immediately updated or revoked by the Owner or organisational administrator.
Iwi and hapū retain ownership of their responses and cultural information.
IwiConnect does not claim ownership of iwi intellectual property.
Only with iwi consent.
Responses are provided for the specific notified project or statutory purpose.
Engagement records and audit logs are retained long term to preserve compliance integrity.
This protects both iwi and customers in the event of review, audit, or dispute.
Yes. Iwi can request export of engagement records at any time.
Customers can request export of project data within the timeframe set out in the Terms.
IwiConnect uses encryption in transit and at rest, secure cloud infrastructure, role-based access controls, and system monitoring.
Reasonable safeguards are in place to protect information.
Enterprise SSO and integration discussions are available for larger organisations and councils.
Yes. Security information can be provided to support procurement and risk assessments.
The platform is hosted on secure cloud infrastructure with appropriate safeguards consistent with New Zealand privacy requirements.
If a notifiable privacy breach occurs, affected parties will be notified in accordance with the Privacy Act 2020.
The platform supports standard data exports and can operate alongside existing compliance, planning, and project management systems.
API discussions are available for enterprise clients.
Scheduled maintenance or unforeseen outages may occur.
We use reasonable efforts to restore service promptly and preserve engagement records and audit integrity.
Engagement volumes are increasing. Regulatory scrutiny is rising. Expectations are higher than ever.
IwiConnect provides structure, visibility, and audit clarity at a time when informal systems are under pressure.
It is scalable infrastructure for the future of iwi engagement in Aotearoa.