Roadmap

Institutional Roadmap

Key milestones for JIL Sovereign policy and attestation infrastructure. Factual timeline, no hype.

Q1 2026 Complete

Foundation and Validation

  • External technical validation complete - independent architecture review of settlement protocol, MPC key management, and SCN validator consensus
  • 10 mainnet SCN validators active across 13 compliance zones
  • 301 production services deployed and operational
  • 83 patent claims filed (37 independent, 88 dependent)
  • JIL utility token deployed on Ethereum mainnet. Token sale infrastructure operational. See getjil.com for token details.
Q2 2026 Active

Mainnet Settlement Protocol

  • Mainnet settlement protocol live - full settlement flow operational with 14-of-20 SCN validator consensus and sub-2-second finality
  • Cross-chain bridge operational for ETH, USDC, USDT, WBTC, DAI
  • Institutional API documentation and sandbox environment available
  • Settlement execution layer (AMM V5) integrated with mainnet verification layer - deterministic batch execution with fair ordering, no front-running, no MEV extraction
  • SentinelAI fleet monitoring active across all SCN validators with automated health recovery
Q3 2026 Planned

Institutional POC and Integration

  • First institutional proof-of-concept corridor - controlled settlement corridor with selected institutional participants
  • NACHA/SWIFT integration gateway - translation layer enabling interoperability between JIL settlement and traditional payment rails
  • Expanded wrapper token bridge - additional asset pairs based on institutional demand
  • Institutional onboarding toolkit - compliance documentation, integration guides, and dedicated support channel
Q4 2026 Planned

Compliance Certification

  • SOC 2 Type I process initiated - formal engagement with audit firm for controls assessment
  • Institutional settlement volume reporting and analytics dashboard
  • Enhanced compliance engine with configurable policy templates for different regulatory jurisdictions
  • Additional SCN validator nodes provisioned based on settlement volume requirements
2027 Planned

Expansion

  • SCN Validator partner expansion - onboarding additional SCN validator operators to increase network decentralization and geographic coverage
  • Additional jurisdiction onboarding - extending compliance coverage based on institutional demand and regulatory developments
  • SOC 2 Type II certification target Q4 2027 (per docs/strategy/CANONICAL_LOCK.md)
  • Advanced settlement corridors - multi-asset, multi-jurisdiction settlement flows for complex institutional transactions
Strategic Track · Platform Compliance Inheritance

Compliance posture by inheritance: Snowflake Native App + Databricks Brickbuilder.

In parallel to the standalone Build Track above, JIL is shipping native deployments inside the customer's existing certified data platform - Snowflake Container Services and Databricks Apps. The customer's data plane is unchanged. JIL services run as containers inside the customer's account. The compliance posture is inherited from the platform: HITRUST r2, SOC 2 Type II, ISO 27001, HIPAA + BAA, FedRAMP MOD, PCI DSS - already in place at Snowflake and Databricks. JIL Cloud (Amazon EKS) is the third path for federal and air-gap workloads.

Q2 2026 Active

Snowflake Native App - Snowpark Container Services

  • Verdict Engine running inside customer Snowflake account via Snowpark Container Services
  • Inherited compliance: HITRUST r2, SOC 2 Type 2, ISO 27001, HIPAA + BAA, FedRAMP MOD, PCI DSS
  • Customer data never leaves customer account; hashes only cross to CourtChain™
  • Marketplace listing in flight
Q3 2026 Active

Databricks Brickbuilder Apps

  • Verdict Engine deployed inside customer Databricks workspace
  • Delta Lake substrate, Unity Catalog governance, Photon query engine
  • Same inherited compliance posture as Snowflake (HITRUST / SOC 2 / ISO 27001 / HIPAA / FedRAMP MOD)
  • Best fit for lakehouse-native, ML-heavy customers running Unity Catalog
Q4 2026 Planned

JIL Cloud - Amazon EKS

  • Direct deployment on JIL-operated EKS infrastructure (KMS, IAM, GuardDuty)
  • SOC 2 Type 1 signed; SOC 2 Type 2 target Q4 2027
  • HITRUST i1 signed; r2 target 24 months
  • FedRAMP MOD roadmap, GovRAMP Ready 3-4 months, StateRAMP roadmap
  • For federal customers requiring authorization paths and any institution requiring maximum operational control
Q1 2027 Planned

Federal Channel Activation

  • Channel partnerships through Accenture Federal Services, Leidos, SAIC, Peraton
  • 60-120 day path to fielded capability under partner ATO/FedRAMP authorities
  • Reference Medicare model: 12.5% of disclosed PI spend (annual, capped) plus 10% contingency on net cash recovered. 4-year retroactive scan baseline. 90-day pilot, $1M all-in, asymmetric downside (contingency drops 10% to 7.5% on miss), ~$786M net to partnership
  • Cross-agency CREB™ evidence reuse across CMS, OIG, DOJ, federal program integrity
Note: This roadmap reflects current plans and may be adjusted based on regulatory developments, market conditions, and institutional feedback. All dates are targets, not commitments. For the latest status and evidence of completed milestones, visit the Proof Artifacts page.
Policy and Attestation Infrastructure

Interested in participating?

We welcome conversations with institutions interested in early access to policy and attestation infrastructure or SCN validator partnership.

Schedule a Consultation View Proof Artifacts