Summary: Sentio is best understood not as just another hosted indexer, but as an observability and analytics stack that is trying to migrate from a centralized developer platform into a decentralized data-and-compute network. Its core mechanism is the Processor: developer-authored logic that watches onchain activity, transforms raw chain data into structured outputs, and then feeds dashboards, alerts, queries, and applications through separately scaled compute and storage layers. That makes Sentio a useful comparison class for data providers and risk-intelligence tooling, especially where analytics access, query infrastructure, and agent-readable chain context start becoming their own control surface.
What it does:
Lets developers write Processors that watch contracts and chain activity, execute custom logic, and emit structured metrics, logs, and entities
Provides dashboards, alerts, SQL/GraphQL-style querying, debugger/simulator workflows, code intelligence, and multi-chain analytics on top of those processor outputs
Extends the hosted platform into the Sentio Network, where storage and processor execution move onto decentralized node operators instead of remaining with one service provider
Splits the decentralized system into a Compute Network, Storage Network, and Sentio EVM layer that tracks metadata, exposes staking/voting, and provides data-access precompiles
Uses $ST and Sentio Units / job-serving incentives to align developers, node operators, and delegators around indexing, query, and compute work
Positions itself as AI-native infrastructure by exposing natural-language queries, automated debugging, predictive analytics, and an MCP service layer for agent applications
Key claims:
The main docs overview says Sentio is building next-generation crypto-data infrastructure spanning real-time indexing, customizable analytics, alerting, dashboards, APIs, simulation, and debugging
The Sentio Network docs say the project is decentralizing its storage and processor layers into a distributed network so data pipelines become verifiable and governance/indexing no longer depend on a single provider
Those same network docs define a three-layer architecture: Compute Network, Storage Network, and Sentio EVM built on OP Stack for metadata, staking, voting, and onchain data access
The platform site shows the product is broader than raw indexing alone, emphasizing analytics, transaction debugging, fund-flow analysis, code search, and developer-facing diagnostics
The public GitHub org exposes current repos for sentio-core, storage-network-daemon, sentio-sdk, docs, network configs, and related tooling, which supports the claim that the decentralized-network surface is being actively built
The docs explicitly surface a Litepaper PDF, making the decentralization/token-economy claims more than a homepage narrative
Whitepaper: A canonical public litepaper PDF exists and is saved locally at ../whitepapers/sentio-litepaper.pdf. See also ../whitepapers/sentio-primary-sources-2026-05-08.md.