Roadmap

Acceso follows a capability-driven roadmap, not a date-driven one.

We prioritize stable primitives over publishing timelines.

Roadmap principles

• Build reusable capabilities, not one-off features.

• Keep changes additive where possible.

• Prefer predictable contracts over rapid breaking changes.

• Scale coverage via clear service boundaries and ownership.

Items below are directional.

Order and scope may change based on usage signals and platform constraints.

Current focus (now)

• Core API stability

• Solana & DeFi data coverage

• Real-time systems

• SDK maturity

Core API stability

• Consistent request/response shapes and error envelopes.

• Backward-compatible endpoint evolution.

• Clear versioning rules for contract changes.

• Guardrails at the request edge (auth, quotas, validation).

Solana & DeFi data coverage

• Expand coverage where demand is proven.

• Improve normalization across heterogeneous upstreams.

• Clarify coverage boundaries per domain.

Real-time systems

• Reliable delivery for streaming and webhook-style integrations.

• Operational visibility into delivery outcomes.

• Clear retry and backoff behavior for event delivery.

SDK maturity

• Stable interfaces and predictable upgrades.

• Thin abstractions over API contracts.

• Clear environment and key-management ergonomics.

Upcoming evolution (next)

• Expanded protocol support

• Deeper analytics primitives

• Improved automation tooling

• Community-driven feature prioritization

Expanded protocol support

• Add protocol support where it improves platform coverage.

• Keep semantics consistent across domains.

Deeper analytics primitives

• More composable analytics building blocks.

• Stronger aggregation and derived-signal surfaces.

• Focus on deterministic semantics and repeatability.

Improved automation tooling

• Safer operational workflows for configuration changes.

• Better observability surfaces for debugging and triage.

• Reduced manual intervention for common platform actions.

Community-driven feature prioritization

• Prioritize based on real usage and integration pain points.

• Favor changes that unblock multiple use cases at once.

Compatibility policy

Evolution is intended to be additive and backward-compatible.

When a breaking change is unavoidable, it should be explicit and controlled.

Signals that influence prioritization

• Integration friction and support volume.

• Usage concentration by endpoint and domain.

• Reliability hotspots (latency, error rates, upstream instability).

• Requests that unlock multiple use cases.

How to read this roadmap

• “Now” describes current engineering focus.

• “Next” describes near-term expansion areas.

• The list is not exhaustive.

• Specific delivery dates are intentionally omitted.