Become a Founding Member.
Membership details
Who can join
If you care about deployment reality more than hype, you’re in the right place.
Practitioners and operators
Teams running real systems and accountable for uptime, safety, and performance: operations, engineering, reliability, OT/IT, security, data/AI platform, field services
Technology and solution providers
Organisations building GenAIoT capabilities across: industrial IoT platforms, edge compute, connectivity, cloud, AI tooling, observability, cybersecurity, CMMS/ERP/ITSM
Ecosystem organisations
Standards bodies, research groups, and developer communities working on: interoperability, safety, governance, evaluation methods, lifecycle and assurance
Member benefits
Build GenAIoT with the practitioners deploying it.
GenAIoT moves fast, but adoption happens where latency, safety, reliability, cost and regulation matter.
Founding Members help shape a community-driven category and operating model grounded in what teams are building and running now.
Founding Members contribute deployment experience to practical guidance for the wider community.
Influence the definition and direction
- Opportunities to join working groups on definitions, terminology and boundary conditions
- Direct input into “what’s in / what’s out” for GenAIoT and how the category is explained publicly
- Opportunities to propose or refine reference architectures and patterns
Visibility and working groups
Practitioner-grade visibility (credibly earned)
- Potential Founding Member profile placement, subject to editorial review
- Potential inclusion in ecosystem pages and community briefings
- Optional case study participation: What you learned, what you changed, and what improved
Peer exchanges and working groups
Discuss real deployment decisions: operational retrieval, bounded agents, edge readiness, evaluation and governance.
Briefings and pilot-to-production support
Briefings that accelerate adoption
- Opportunities to shape practitioner briefings and templates as they are developed
- Ability to contribute examples and real constraints that make the guidance credible
- Option to co-author community outputs (with review and editorial standards)
From pilot to production
Share what works in deployment: where AI helps, what needs human approval, and how to measure results.
Participation requirements
You don’t need to share trade secrets. You do need to participate.
We ask for:
- A primary point of contact (and optional SME bench for working groups)
- A commitment to practitioner-grade contribution (patterns, lessons learned, deployment constraints)
- Alignment with responsible adoption: safety, transparency, auditability, and measurable outcomes.
- Optional (but powerful): share one use case (sanitised), contribute to a checklist/pattern review, or participate in a briefing interview.
Active build areas
Members can contribute across operational context, hybrid retrieval, model routing, tool integration, governance and deployment readiness.
Success measures
The aim is clearer shared language, reusable deployment patterns and more measurable, accountable outcomes. Founding Members help shape that work through practical contributions.
How to join
We look for practitioners, technology providers and ecosystem organizations prepared to participate, provide subject-matter expertise and support responsible adoption.
01 · Short application
Tell us:
- Your domain (manufacturing, utilities, mobility, built environment, etc.)
- Your deployment maturity (pilot → production)
- Your focus areas (context, RAG, agents/tools, governance, edge)
- What you want to build / learn / influence
02 · Fit and alignment
We confirm:
- Goals, contribution areas, and mutual value
- Where you can plug into working groups and outputs
03 · Onboarding and contribution
Together we agree on a contribution plan, suitable working groups and any profile or briefing participation before publication.