Most rooms seat one role. fsyncDATA seats the whole decision chain of a GCC data estate, from the person who signs the budget to the person who gets paged.
Platform heads agree the CDO does not understand cost; CDOs agree the platform team is slow; DBAs agree nobody asked them. Put them at one table, under rules that let them tell the truth, and the conversation becomes the one you cannot have at work.
The roles at the table
| Role | Tier | What they bring | What they come for |
|---|---|---|---|
| Chief Data Officers, Chief Data and Analytics Officers | Circle | Governance, value framing, the board’s questions | What the platform must have before analytics and AI charters can be honoured |
| Chief Data Architects | Circle | The target architecture, the engine map, the standards | How other estates retired engines, consolidated platforms and made it stick |
| CIOs, CTOs, GCC site leaders | Circle | Portfolio ownership, the HQ view, the budget | How centers earned platform ownership from HQ and kept it |
| Chief AI Officers, Chief Data Scientists | Circle | Model programmes and what they need from data | The foundations work that precedes every model, and what it cost elsewhere |
| Principal Database Architects, heads of data platform | Circle or Guild | Reliability, cost, the upgrade calendar, on-call reality | The numbers behind other estates’ decisions, and a bench on a bad day |
| Data Architects | Guild | Models, pipelines, the contract between platform and consumers | Patterns that held up at scale, and the ones that did not |
| DBAs and Database Reliability Engineers | Guild | Production: backups, failover, tuning, the 3 a.m. page | Peers on the same engine who have seen this failure before |
| Database Engineers, data platform engineers | Guild | Automation, migrations, schema change, platform tooling | Reference designs, runbooks and honest post-mortems |
Eighteen industries, eight tables
The sector mix is deliberate. The same engine behaves differently under different regulation and different load, and the room hears both.
| Sector group | Industries | What their estates teach the room |
|---|---|---|
| Technology | Software, SaaS, technology product companies | Cloud-native estates, multi-tenant design, DBRE culture, fast upgrade cadence |
| Financial services | Banking, BFSI, insurance, fintech | Regulated change, audit trails, zero-data-loss DR, ledger-grade consistency |
| Commerce | Retail, online commerce, consumer packaged goods, FMCG | Peak-season load, real-time inventory and pricing, demand analytics |
| Telecom | Telecom operators and network platforms | Very high ingest rates, CDR and network telemetry analytics, long retention |
| Media and gaming | Media and entertainment, gaming | Spiky concurrency, leaderboards and session stores, event analytics |
| Health | Healthcare, life sciences | Validated environments, patient-data governance, research data platforms |
| Mobility and logistics | Aviation, airline operations, logistics | Operational systems that cannot stop, schedule and crew data, tracking telemetry |
| Analytics centers | Big data and analytics GCCs | Warehouse and lakehouse scale, cost per query, data products for the parent |
Three center stages
Day-1 centers
Building the platform for the first time: engine choices, standards, the first on-call rotation.
Scaling centers
Taking production ownership from HQ and from outsourced towers, one estate at a time.
Portfolio owners
Running global platforms and budgets from India, and answering to the parent’s platform council.
A Day-1 DBA learns what a portfolio owner wishes it had done in year one; a portfolio owner learns what the newest centers are being asked to build.
Who is not eligible
A sales, pre-sales, partnerships, alliances or marketing role at any database vendor, cloud provider, consultancy or analytics firm, including MinervaDB and ChistaDATA; attending on behalf of a company rather than as yourself; a prior breach of a comparable confidentiality charter. Engineers at vendors and consultancies are welcome to speak at the open conferences.
Apply, ask, or nominate someone better
Practitioners apply to a Guild. Leaders request a Circle invitation. Anyone may nominate a peer. Every message to the secretariat is answered by a person within two working days.