Sentio primary sources — 2026-05-08

Classification takeaway

Sentio is best cataloged as observability, indexing, and crypto data-and-compute infrastructure. The key mechanism is the Processor model: developers define programmable data-transformation logic, and Sentio wraps that logic with query, dashboard, alerting, simulation, and debugging surfaces. The notable evolution is that Sentio is now trying to decentralize this stack into separate compute and storage networks plus an OP-Stack-based coordination/staking layer, turning developer analytics into an explicitly tokenized and operator-mediated infrastructure market.

Primary sources reviewed

1. Platform page — https://www.sentio.xyz/platform/

   • Shows that Sentio is broader than a raw indexer: dashboards, SQL & GraphQL access, debugger, simulator, dynamic logs, and code intelligence are first-class product surfaces.
   • Important classification signal because it positions Sentio as workflow infrastructure for protocol teams, not just a backend ETL pipe.

2. Docs overview — https://docs.sentio.xyz/docs/readme

   • Frames Sentio as next-generation crypto data infrastructure with real-time indexing, customizable analytics, alerting, dashboards, API access, simulation, debugging, and multi-chain support.
   • Repeatedly emphasizes Processors as the main developer abstraction, which matters because it is the mechanism through which Sentio converts raw chain data into structured outputs.

3. Sentio Network docs — https://docs.sentio.xyz/docs/sentio-network

   • The most important source for current classification. It says Sentio is moving storage and processor execution into a decentralized network instead of a single provider.
   • Defines the architecture as a Compute Network, Storage Network, and Sentio EVM on OP Stack for metadata, staking, voting, and onchain data-access precompiles.
   • Names the economic participants: developers/analysts, node operators, and stakers/delegators, with $ST and job-serving incentives.
   • Also surfaces the AI/MCP layer, which is analytically notable because it turns indexed blockchain data into agent-readable context infrastructure.

4. Litepaper page / PDF — https://docs.sentio.xyz/docs/litepaper and https://github.com/sentioxyz/docs/raw/HEAD/assets/sentio-litepaper.pdf

   • Confirms there is a canonical public litepaper covering the network’s vision, architecture, and token economy.
   • Important because it elevates the decentralization and incentive claims above generic marketing copy.

5. GitHub org — https://github.com/sentioxyz

   • Public repos for sentio-core, storage-network-daemon, sentio-sdk, docs, and network configs support the view that the compute/storage network is an actively built system.
   • Helps distinguish Sentio from a pure SaaS analytics dashboard with no inspectable technical surface.

Whitepaper / technical-doc status

• A canonical public litepaper PDF exists and has been saved locally as sentio-litepaper.pdf.
• The docs pages remain the most useful source for current product shape and network roles.

Why it stays in the active corpus

• Useful comparison class for analytics, observability, and risk-intelligence infrastructure because it makes query access, data transformation, and agent-facing blockchain context into an explicit market/control plane.
• Helps reason about where soft power migrates when protocols rely on a third-party observability stack for dashboards, alerts, debugging, and query interfaces.
• The decentralized-network and AI/MCP framing makes it more analytically interesting than a generic hosted dashboard vendor.