Canonical source
Historical equities
Twelve Data
Canonical certified history
Completed U.S. equity and ETF candles are fetched by protected server-side jobs, stored, checked, and labeled before they can support customer-facing ORB analytics.
Data transparency
Every number shouldhave a source.
ORBLYTICS makes the provider, storage, freshness, and certification state visible before historical analytics are treated as available.
Server-side storageFreshness monitoredFail closed
- Pilot baseline
- 12 tickers
- Minimum history
- 120+
- Freshness lag
- 0 days
- Fallback
- None
Frozen readiness universe
Verified sessions per ticker
Required for readiness
No production demo data
Source map
What powers each product layer.
Provider data, ORBLYTICS-derived analytics, and unavailable product modes are labeled separately so one source is not mistaken for another.
Never replaces Twelve Data
Validation & reference
Alpaca SIP
Non-canonical, disabled by default
Eligible delayed or completed-session SIP history can cross-check canonical candles. Asset identity, market calendars, early closes, clock state, and corporate actions are retained only as summarized internal evidence.
Display off by default
Optional live context
Alpaca IEX
Partial-market context only
The free real-time IEX feed covers one venue, so it cannot certify ORB levels or fill missing canonical candles. Customer display remains off unless the applicable rights are documented.
Not a provider signal
Derived analytics
ORBLYTICS engine
Calculated from certified history
Opening-range levels, confirmations, retests, target outcomes, matched sessions, and hit rates are derived by ORBLYTICS from the qualified stored sample.
Fail-closed boundary
Futures history
Databento
Disabled in this pilot
Futures require a configured feed, certified history, and documented customer-display rights before a future product mode can expose them.
Certification lifecycle
Four gates before publication.
Availability is earned by completing each gate. A provider response alone is not enough to publish historical analytics.
01
Acquire
Protected provider request
Server-side jobs request the required historical window. Provider credentials and raw ingestion stay outside the browser.
02
Store
Durable historical record
Qualified candles and provider identity are stored so calculations do not depend on a temporary browser response.
03
Validate
Session and policy checks
Timestamps, session boundaries, candle completeness, policy version, and required sample coverage are checked.
04
Publish
Certified derived analytics
Only eligible history can power customer-facing ORB cards. Missing or stale data produces an unavailable state instead of demo values.
Frozen readiness baseline
Historical stock pilot
These tickers define the production-readiness baseline. A broader U.S. search universe can appear only after each selected symbol passes its own history, freshness, policy, and display-rights checks.
SPYIWMQQQXLFXLKAALAMZNNFLXNVDATTDGOOGGOOGL
Current product boundary
Historical—not live execution
- No live quote or provider fallback is used in historical-only mode.
- Alpaca IEX is partial-market context and is never used to certify an ORB level.
- Live streams, alerts, order routing, and broker account state are not included.
- Futures remain disabled until feed, history, and customer-display requirements are satisfied.
- The System Status page shows current certification and freshness health.
Why charts can differ
Your broker remains the execution source.
Historical context can be useful without being identical to the current chart or executable market available through your broker.
Feed coverage
A broker, exchange, and third-party provider can include different venues, corrections, or consolidation rules.
Session definition
Regular-session boundaries, early closes, timezone handling, and premarket inclusion can change an ORB high or low.
Candle construction
Corrections, adjustments, timestamps, and minute aggregation can create small OHLCV differences.
Execution reality
A historical target touch does not model your fill, spread, slippage, liquidity, partial exits, fees, or taxes.
Verify before every trading decision.
Confirm the current price, range levels, liquidity, order details, and account risk with your broker or an exchange-authorized feed. Historical analytics do not control orders or fills.