How a CTO Assessed Brazil Market Readiness in 35 Minutes

NeonEdge is a crypto-native iGaming platform incorporated in Estonia and operating globally, built for players who demand provably fair outcomes and on-chain settlement. The platform supports four blockchains — Ethereum, Tron, Polygon, and Solana — serves roughly fifteen thousand monthly active users, and generates approximately $5M per week in GGR, with crash games accounting for just under half that volume. It is technically sophisticated by any iGaming standard: real-time RNG attestation, wallet-native authentication, and a data warehouse that ingests on-chain events alongside behavioral signals.

Now the board has approved exploring Brazil. The country passed its sports betting regulation framework in late 2023 and the licensed market is opening fast. Brazil is one of the most sports-passionate and mobile-first populations on earth, and the BRL is stabilizing. The opportunity is obvious. The execution risk, for a crypto-native platform, is not.

Priya Desai is NeonEdge's CTO and Head of Data. The board wants a technical readiness report at next Thursday's call — specifically whether NeonEdge's current data infrastructure can support a Brazilian launch, what gaps exist, and how long remediation will realistically take. Priya opens Gaming Mind AI on a Tuesday afternoon in Tallinn with seven days on the clock.

Products used: Data Architecture Analyzer, Compliance Data Mapping, Integration Assessment

35 minutes | end-to-end assessment session

8 integration gaps identified

Assessment scope that would take an engineering team one full week

---

Challenge

NeonEdge was designed for a crypto-native world. Everything about its data architecture reflects that origin: wallets instead of accounts, on-chain transaction hashes instead of payment reference numbers, anonymous player profiles enriched over time by behavioral signals. The platform never had to store BRL amounts, verify CPF numbers, report to a national gaming authority, or satisfy LGPD data residency requirements. Its entire payment layer is denominated in crypto assets, settled on public blockchains.

Brazil changes all of that. The country's regulated betting market requires operators to collect and verify taxpayer identification from every player, report flagged transactions to Coaf — Brazil's financial intelligence unit — within 24 hours, and store personal data on servers physically located within Brazilian territory or in jurisdictions with an adequacy decision under LGPD. For a platform whose data warehouse runs on European cloud infrastructure and whose player records contain wallet addresses but not government IDs, the gap between "where we are" and "where we need to be" is not obvious. It is also not small.

"I could have spent a week asking three different engineering teams to audit their own systems. Everyone would come back saying their piece was fine. I needed someone who could look at the whole architecture at once, cross-reference it against the actual Brazilian requirements, and tell me where the gaps were — specifically. Not approximately."

— Priya Desai, CTO / Head of Data, NeonEdge

The secondary challenge was format. The board isn't technical. They need to understand what's broken, what it costs to fix, and how long it takes — not a list of schema changes. Priya needed an assessment she could hand directly to non-engineers and have it land clearly, within a week, without pulling her senior engineers off their current sprint.

---

Solution

Priya structured her session as a technical audit: start with the current architecture, map it against Brazil's specific regulatory requirements, identify the concrete gaps, price them in engineering time, and end with a board-ready recommendation. Gaming Mind AI pulled NeonEdge's data architecture profile, cross-referenced it against its compliance data maps for the Brazilian market, and ran the analysis as a single connected conversation.

Here is what that session looked like:

---

Priya: "I need to assess whether our current data architecture is ready for a Brazilian market launch. Start with where we actually are — current data infrastructure, storage, player identity model."

Layer	Component	Technology	Location	Notes
Primary database	Postgres cluster	PostgreSQL 15	Frankfurt, EU	Player records, wallet sessions
Analytics warehouse	ClickHouse cluster	ClickHouse	Amsterdam, EU	Event aggregations, reporting
Event bus	Kafka streams	Confluent Cloud	EU-West	~2.3M events/day at peak
Player identity model	Wallet-first UUID	Custom	—	Wallet address → UUID; email optional at withdrawal
KYC	None at registration	—	—	No government ID collected
Payment layer	Crypto-native only	ETH, Tron, SOL, Polygon	On-chain	No fiat rails
Geo routing	None	—	—	Single-region architecture

Identity Model Detail

Field	Collected?	Source
Wallet address	Yes	Required at registration
UUID	Yes	System-assigned
Email address	Optional	Collected at withdrawal
Full name	No	—
Government ID / CPF	No	—
Date of birth	No	—
Residential address	No	—

⚠️ Gaming Mind flags: NeonEdge's architecture is well-suited for its existing crypto-native user base. Three structural characteristics require assessment against Brazilian regulatory requirements before any launch decision: (1) wallet-first identity with no government ID collection, (2) no fiat payment rails or BRL denomination, (3) all player PII physically stored in EU jurisdiction with no Brazilian-region presence.

Gaming Mind AI returned NeonEdge's infrastructure profile as a structured technical snapshot: a Postgres primary cluster in Frankfurt, a ClickHouse data warehouse in Amsterdam, and an event bus handling roughly 2.3 million events per day at peak — mostly on-chain transaction receipts, crash game round completions, and wallet-connect sessions. The player identity model is wallet-first: a UUID assigned at wallet connection, optionally enriched with an email address at withdrawal. No government ID collection, no formal KYC at registration, and no fiat payment rails. Gaming Mind flagged that this architecture is well-suited for the existing crypto-native user base but noted three structural characteristics that will require assessment against Brazilian regulatory requirements before any launch decision.

---

Priya: "What does Brazil's regulated market actually require in terms of data — KYC, transaction reporting, data residency? Specifically Loterj and the federal framework."

Requirement	Regulator / Law	Obligation	Deadline / Frequency
Full KYC at registration	Federal / SPA	Collect and verify CPF (Cadastro de Pessoas Físicas) before first deposit	At account creation
CPF verification	Federal	Hard mandatory check — no deposit allowed without verified CPF	Before any deposit
Transaction reporting to Coaf	Coaf / AML law	Report all transactions above R$2,000 to Brazil's financial intelligence unit	Within 24 hours
AML transaction log retention	Coaf	Maintain complete AML monitoring log	Minimum 5 years
LGPD data residency	LGPD	Player personal data must be stored on servers within Brazil or an adequacy-recognized jurisdiction	At time of storage
Game-type licensing — crash games	Loterj (Rio state)	Crash games classified as instant lottery, not sports betting — requires separate license category	Before operating in-state
Responsible gambling disclosures	SPA	Mandatory player protection and self-exclusion tools	At launch

LGPD Adequacy Status

Jurisdiction	LGPD Adequacy Decision	NeonEdge Current Location	Compliant?
Brazil	— (domestic)	—	—
EU	Pending (not yet confirmed)	Frankfurt + Amsterdam	🔴 Not confirmed
United Kingdom	Pending	—	🔴 Not confirmed
Switzerland	Pending	—	🔴 Not confirmed

⚠️ Gaming Mind flags: Brazil's regulated market imposes four categories of data obligation that NeonEdge does not currently meet: mandatory CPF KYC at registration, Coaf transaction reporting within 24 hours on amounts above R$2,000, LGPD data residency requirements (EU adequacy not yet confirmed), and crash game licensing under Loterj's instant lottery classification rather than sports betting. The last point is material — NeonEdge's primary revenue driver may require a separate license category in some Brazilian states.

Gaming Mind pulled Brazil's applicable regulatory stack and summarized the data obligations in plain terms. Federal law requires full KYC at account creation, including CPF (Cadastro de Pessoas Físicas) verification — a hard mandatory check before any deposit. Operators must report transactions above R$2,000 to Coaf within 24 hours and maintain an AML transaction monitoring log for a minimum of five years. Under LGPD, player personal data must be stored on servers within Brazil or in a jurisdiction recognized by Brazil's data protection authority — currently limited to a narrow list of countries, with the EU on the pending-adequacy list but not yet confirmed. Loterj, which regulates Rio de Janeiro state operations, adds a layer of game-type licensing that affects crash games specifically, classifying them under instant lottery rules rather than sports betting. Gaming Mind noted that this last point is material: NeonEdge's primary revenue driver may require a separate license category in some Brazilian states.

---

Priya: "Where does our current schema break down against those requirements? Show me the gaps."

#	Domain	Gap	Requirement Violated	Severity
1	Identity	No CPF field in player table	Federal KYC — CPF mandatory before deposit	🔴 Blocker
2	Identity	No government document storage	Federal KYC — document verification required	🔴 Blocker
3	Identity	No CPF verification workflow	Federal KYC — must verify at registration	🔴 Blocker
4	Transactions	No BRL amount field — amounts stored in crypto units only	Loterj reporting + Coaf threshold monitoring (R$2,000)	🔴 Blocker
5	Transactions	No fiat conversion audit trail	Loterj reporting standards	🟡 Significant
6	AML reporting	No Coaf R$2,000 threshold monitoring rule	Coaf AML reporting within 24 hours	🟡 Significant
7	Data residency	All player PII in Frankfurt + Amsterdam; no Brazilian-region replication	LGPD data localization for Brazilian-resident players	🟡 Significant
8	Game classification	Crash game rounds not tagged with game-type taxonomy	Loterj licensing audit trail	🟢 Deferrable

Gap Priority Summary

Priority	Count	Description
🔴 Blocker — must resolve before launch	4	CPF field, document storage, CPF workflow, BRL schema
🟡 Significant — address in parallel	3	Fiat audit trail, Coaf monitoring, LGPD residency
🟢 Lower priority — deferrable to post-launch	1	Game classification taxonomy
Total gaps	8

⚠️ Gaming Mind flags: 4 of 8 gaps are hard blockers that prevent compliant registration and deposits entirely. The identity gaps (gaps 1–3) block every Brazilian player from registering. The BRL schema gap (gap 4) blocks both Loterj reporting and Coaf threshold monitoring. These 4 items are on the critical path and must be resolved before any Brazilian player can legally interact with the platform.

This is where the assessment became concrete. Gaming Mind identified eight integration gaps across five domains. On identity: NeonEdge's player table has no CPF field, no government document storage, and no CPF verification workflow — three gaps that block registration compliance entirely. On transactions: the current schema records amounts in crypto asset units with no BRL equivalent field and no fiat conversion audit trail, which fails both Loterj reporting requirements and Coaf threshold monitoring. On AML: there is no transaction monitoring rule engine configured for BRL amounts or the Coaf R$2,000 threshold — the existing risk scoring model is calibrated for crypto wallet behavior, not fiat spend patterns. On data residency: all player PII and transaction records are physically stored in Frankfurt and Amsterdam with no Brazilian-region replication policy, which violates LGPD data localization requirements for any player identified as a Brazilian resident. And on game classification: crash game rounds are not tagged with a game-type taxonomy that maps to Brazilian licensing categories, which creates a compliance blind spot for future regulatory audits. Gaming Mind ranked the gaps by severity: three blockers that must be resolved before launch, three significant gaps that can be addressed in parallel, and two lower-priority improvements that can be deferred to post-launch.

---

Priya: "Which payment providers support BRL fiat rails and are already operating with Brazilian gaming licenses? What do they need from us on the integration side?"

Provider	Brazilian Gaming License	BRL Settlement	CPF Required at Transaction	Local Entity Required	API Real-time Feed	NeonEdge Integration Effort
Provider A	Yes — active	Yes	Yes	Yes (or licensed intermediary)	Yes	High — depends on identity gap fix
Provider B	Yes — active	Yes	Yes	Yes (or licensed intermediary)	Yes	High — depends on identity gap fix
Provider C	Pending	Partial (BRL + USDT)	No (crypto path)	No	Limited	Medium — crypto path only, not Loterj compliant
Provider D	No	No	No	No	No	🔴 Not viable for regulated BRL

Critical Integration Dependencies

Requirement	Blocks Which Gap?	Notes
CPF-verified player ID passed at transaction initiation	Gaps 1–3 (identity)	Both licensed providers require this field at API call
BRL amounts at field level (not post-settlement conversion)	Gap 4 (BRL schema)	Conversion layer not accepted; native BRL required
Local BRL settlement account or licensed intermediary	Corporate structure	Outside data architecture scope — raise with board

⚠️ Gaming Mind flags: Both technically mature BRL payment providers require CPF-verified player identifiers at transaction initiation — looping directly back to the identity gaps. They also require BRL amounts at the field level, not applied post-settlement, confirming the BRL transaction schema gap is on the critical path for payment integration. NeonEdge's Estonian corporate structure does not automatically satisfy the local entity requirement — this must be raised with the board alongside the technical findings.

Gaming Mind returned an assessment of the BRL payment integration landscape, focusing on providers with active Brazilian gaming licenses. The two most technically mature options for NeonEdge's profile both require the operator to pass CPF-verified player identifiers at transaction initiation — which loops back directly to the identity gap identified in the previous step. Both also require a local BRL settlement account registered to a Brazilian legal entity, or a licensed payment intermediary to hold the settlement layer. Gaming Mind flagged that NeonEdge's current corporate structure in Estonia does not automatically satisfy this requirement and noted that the legal entity question is outside data architecture scope but should be raised with the board alongside the technical findings. On the integration side, both providers need BRL amounts at the field level — not a conversion layer applied post-settlement — which means the transaction schema gap is on the critical path for payment integration as well.

---

Priya: "Data residency — what are our actual options for LGPD compliance given our current European cloud setup? What does it cost to add a Brazil region?"

Option	Architecture	LGPD Compliance Certainty	Engineering Time	Monthly Cost (incremental)	Risk
1 — Dedicated Brazilian cluster	All Brazilian player PII + transactions in BR region; analytics pseudonymized and replicated to Amsterdam	High	2–3 months	~$4,800/month	Low — clear separation
2 — Data routing layer	Residency classification at write time; Brazilian-resident records routed to BR database; all other markets unchanged	Medium-High	3–5 months	~$2,200/month	Medium — misclassification risk at registration
3 — Third-party LGPD processor	Licensed Brazilian data processor as passthrough for player PII and transactions	Medium	4–8 weeks	~$1,400/month + legal overhead	Medium — vendor dependency, DPA required

Option 2 Risk Detail

Risk	Detail	Consequence
Residency misclassification	Brazilian player identified as non-resident at registration	LGPD violation at moment of storage, not at audit
Detection lag	May not surface until regulatory audit	Retroactive remediation required
Mitigation	Robust CPF-based nationality detection layer	Increases implementation complexity

⚠️ Gaming Mind flags: Option 2 (data routing layer) is the most operationally elegant for a multi-market platform but carries the highest risk if the residency classification layer misidentifies a Brazilian player — the LGPD violation occurs at the moment of storage, not at the moment of audit. Option 1 (dedicated Brazilian cluster) provides the highest compliance certainty at ~$4,800/month additional cloud cost. Option 3 is fastest but introduces a vendor dependency and adds legal overhead for data processing agreements.

Gaming Mind laid out three architectures for data residency compliance and assessed each against NeonEdge's existing infrastructure. Option one: deploy a dedicated Brazilian cluster for all PII and transaction data, keeping analytics replicated but pseudonymized in Amsterdam — the highest compliance certainty, estimated at two to three months of infrastructure work and roughly $4,800 per month in additional cloud cost. Option two: implement a data routing layer that sends Brazilian-resident player records to a Brazilian-region database at write time, while retaining the existing architecture for all other markets — lower infrastructure cost but higher engineering complexity, requiring a robust residency classification layer that must correctly identify Brazilian players at registration. Option three: use a third-party LGPD-compliant data processor with a Brazilian operation as a passthrough layer — fastest to deploy, but introduces a vendor dependency and requires contractual data processing agreements that add legal overhead. Gaming Mind noted that option two is the most operationally elegant for a multi-market platform but carries the highest risk if the residency classification layer is wrong, since misclassifying a Brazilian player as non-resident creates an LGPD violation at the moment of storage, not at the moment of audit.

---

Priya: "Timeline estimate — if we started remediation today, what's the realistic sequence and how long does each gap take to close?"

Phase	Gap(s)	Work Item	Person-Weeks	Parallelizable?	Critical Path?
Phase 1 — Blockers	1–3	CPF field addition + verification workflow	3 weeks	No (must finish first)	Yes
Phase 1 — Blockers	4–5	BRL transaction schema + fiat conversion audit trail	2 weeks	After CPF field design finalized	Yes
Phase 1 — Blockers	7	LGPD-compliant data residency infrastructure (Option 2)	3–6 weeks	Limited — depends on identity + transaction schema	Yes
Phase 2 — Significant	6	Coaf AML transaction monitoring (BRL threshold R$2,000) + reporting pipeline	5–7 weeks	Yes — can start after week 2 of Phase 1	No
Phase 3 — Deferrable	8	Crash game taxonomy tagging + game classification schema	2–3 weeks	Yes — fully independent	No (pre-licensing)

Timeline Summary

Milestone	Calendar Weeks from Start
Phase 1 complete (all blockers cleared)	8–11 weeks
Phase 2 complete (AML reporting live)	10–12 weeks (parallel)
Phase 3 complete (game classification)	12–14 weeks (parallel)
Compliant launch ready	12–14 weeks
Required engineering staffing	3 engineers on data infrastructure workstream
Total person-weeks	18–22

⚠️ Gaming Mind flags: The three Phase 1 blockers cannot be fully parallelized — the data residency infrastructure depends on knowing the final identity and transaction schemas. Phase 2 (Coaf AML monitoring) can run in parallel after week 2. Phase 3 (game taxonomy) is not on the launch critical path but must be completed before any state-level licensing application. Total calendar window: 12–14 weeks with three engineers dedicated to the data infrastructure workstream.

Gaming Mind produced a sequenced remediation plan with engineering effort estimates for each gap. Phase one — the three hard blockers — requires eight to eleven person-weeks of work: CPF field and verification workflow (three weeks), BRL transaction schema and conversion audit trail (two weeks), and LGPD-compliant data residency infrastructure using option two above (three to six weeks depending on architecture choice). These three items are on the critical path and cannot be parallelized beyond a limited extent because the data residency layer depends on knowing what the identity and transaction schemas will look like. Phase two — AML transaction monitoring for BRL and Coaf reporting — is five to seven person-weeks and can run in parallel with phase one after the first two weeks. Phase three — crash game taxonomy tagging and game classification schema — is two to three person-weeks and is not on the launch critical path, but must be completed before any state-level licensing application in Brazil. Total estimated remediation: eighteen to twenty-two person-weeks across a twelve to fourteen week calendar window if staffed with three engineers on the data infrastructure workstream.

---

Priya: "Give me a go/no-go recommendation I can put in front of the board, with the three blockers and what it takes to clear them."

Brazil Market Entry — Technical Readiness Assessment

Verdict: CONDITIONAL GO — Market viable, architecture not yet compliant

Blocker	Domain	Status	Remediation Path	Owner Category	Timeline
1. Player identity does not support CPF verification	Identity / KYC	🔴 Not started	Add CPF field + verification workflow; integrate with Receita Federal API	Engineering	3 weeks
2. Transaction data does not meet BRL reporting standards	Transaction schema	🔴 Not started	Add BRL amount fields + fiat conversion audit trail to transaction schema	Engineering	2 weeks
3. Player PII not stored in compliance with LGPD residency	Data residency	🔴 Not started	Deploy data routing layer or dedicated Brazilian cluster (see options)	Engineering + Infra	3–6 weeks

At a Glance

Item	Value
Total engineering effort	18–22 person-weeks
Compliant launch timeline	15–17 weeks from engineering start
Estimated incremental infrastructure cost	~$2,200–$4,800/month
Legal dependency	Brazilian legal entity or licensed payment intermediary required
Market opportunity	Real — strong sports + crash game demand, BRL stabilizing

⚠️ Gaming Mind flags: Brazil is a viable market entry — the GGR opportunity is real and NeonEdge's product has natural appeal in the Brazilian sports and crash game segment — but the launch is not ready under current architecture. All three blockers have defined remediation paths. Combined timeline puts a compliant launch at 15–17 weeks from the start of engineering work. The legal entity question (requirement for a Brazilian-domiciled payment intermediary or corporate entity) is outside data architecture scope but essential to resolve before the engineering work has any value.

Gaming Mind produced a structured board summary in Priya's terminology: a conditional go recommendation with three defined blockers, each with a remediation path, owner category, and estimated timeline. The assessment framed Brazil as a viable market entry — the GGR opportunity is real and NeonEdge's product has natural appeal in the Brazilian sports and crash game segment — but marked the launch as not ready under current architecture. Blocker one: player identity does not support CPF verification. Blocker two: transaction data does not meet BRL reporting standards for Coaf or Loterj. Blocker three: player PII is not stored in compliance with LGPD residency requirements. Each blocker has a defined remediation path, and the combined timeline puts a compliant launch at fifteen to seventeen weeks from the start of engineering work. The summary also flagged the legal entity question — the need for a Brazilian-domiciled payment intermediary or corporate entity — as outside data architecture scope but essential to resolve before the engineering work has any value.

---

Priya: "What would the legal entity and payment intermediary options look like from a data integration standpoint? How does that choice affect the architecture?"

Structure Option	Data Controller for Payments	Raw Transaction Record Access	Coaf Reporting Ownership	Timeline to Operational	Data Architecture Implication
A — Licensed Brazilian payment intermediary	Intermediary (not NeonEdge)	Via reconciliation API only	Intermediary (with NeonEdge notification)	4–8 weeks	Simplifies LGPD residency compliance; introduces API latency risk for Coaf 24-hr window
B — NeonEdge Brazilian subsidiary	NeonEdge	Full, direct	NeonEdge	3–6 months (incorporation + banking)	Full data control; cleanest reporting ownership; extends overall launch timeline
C — Hybrid (intermediary + future subsidiary)	Intermediary initially; NeonEdge post-incorporation	API initially; full access after transition	Shared → NeonEdge	4–8 weeks + 3–6 months	Fastest path to launch; requires schema migration plan for ownership transition

Data-Control Tradeoff: Option A vs Option B

Tradeoff	Option A (Intermediary)	Option B (Subsidiary)
LGPD residency compliance	Simplified — intermediary handles	NeonEdge owns — full control required
Raw transaction visibility	Limited — API reconciliation only	Full
Coaf reporting latency risk	Yes — depends on intermediary API speed	No — NeonEdge controls reporting pipeline
Launch speed	Faster	Slower (3–6 months additional)

⚠️ Gaming Mind flags: Using a licensed Brazilian payment intermediary simplifies LGPD data residency compliance but means NeonEdge loses direct access to raw transaction records and must rely on a reconciliation API — introducing latency risk for Coaf's 24-hour reporting window if the intermediary's API is not real-time. Using a Brazilian subsidiary gives full data control and clean reporting ownership but adds 3–6 months for incorporation and banking setup. Both paths should be presented to the board with the specific data-control tradeoff articulated so the decision reflects full operational consequences, not just legal ones.

Gaming Mind closed the loop between the corporate structure question and the technical architecture. Using a licensed Brazilian payment intermediary — rather than a NeonEdge-owned local entity — has concrete implications for the data layer: the intermediary becomes the data controller for payment records under LGPD, which can simplify residency compliance but means NeonEdge loses direct access to raw transaction records and must rely on a reconciliation API. That introduces latency in Coaf reporting if the intermediary's API doesn't support real-time transaction feeds. Using a Brazilian subsidiary, by contrast, gives NeonEdge full data control and clean reporting ownership but adds three to six months for incorporation and banking setup, which extends the overall timeline by roughly that amount. Gaming Mind recommended flagging both paths in the board document with the specific data-control tradeoff articulated, so the decision can be made by the board with full visibility into the operational consequences, not just the legal ones.

---

Results

Three hard blockers identified with remediation paths before any engineering started

Priya walked into the board call with more than a gap list. She had a prioritized remediation roadmap with effort estimates, a critical path diagram, and a clear distinction between blockers that must be cleared before launch and improvements that can be deferred. The board approved the remediation budget on the call.

Eight integration gaps mapped in a single session

A cross-functional audit of identity, transaction schema, AML reporting, data residency, and game classification would normally require at least a week of engineering interviews, document reviews, and regulatory cross-referencing across three teams. Gaming Mind completed the same scope in thirty-five minutes, with no engineer pulled from their sprint.

Legal and data architecture dependency surfaced early

The connection between the corporate structure decision and the LGPD data residency architecture — specifically, how the choice of payment intermediary determines who controls transaction records and how Coaf reporting latency is managed — would not have surfaced in a standard engineering audit. It required cross-referencing legal structure, regulatory obligation, and data architecture simultaneously. Gaming Mind surfaced it as a natural follow-up in the same session, in time for Priya to include it in the board briefing rather than discovering it mid-implementation.

Assessment delivered as a board-ready document

The output of the thirty-five minute session was a structured technical readiness report with a clear go/no-go verdict, three defined blockers, a remediation timeline, a cost estimate, and a flagged legal dependency. Priya sent it to the board the same day without material editing.

"I expected to spend a week on this and still feel uncertain about what I was missing. Instead I had a complete picture in thirty-five minutes — every gap named, every remediation path scoped, the legal dependency flagged before it could ambush us. The board made a properly informed decision. That's not something I could have guaranteed any other way on that timeline."

— Priya Desai, CTO / Head of Data, NeonEdge