Xignite

• If fully transparent self-serve pricing and instant signup with predictable monthly spend are required, other vendors with public pricing may be preferable.
• If the requirement is low-cost end-of-day equities data only, lower-cost providers may be more economical.
• If procurement requires publicly documented SOC 2 / ISO 27001 evidence upfront and the vendor does not provide those artifacts in a timely manner, this can impede procurement.
• If strong community validation (Reddit/Hacker News/open-source ecosystem) is a procurement requirement, the vendor’s public community presence appears limited relative to developer-first brands.
• If vendor dependency for mission-critical UI components or data flows is unacceptable, consider architectural redundancy or alternative providers to mitigate single-vendor risk.

G2 listings show limited public review volume for Xignite in the sources reviewed; the sample size in public listings is not statistically representative.

Positive review excerpts (G2):

• Reviewers described the solution as cloud-based with a strong perception of security.
• Other reviewers referred to data accuracy and the vendor’s usage-based pricing options.

Negative/critical excerpts (G2):

• Reported difficulty with the software UI/console.
• Concerns in older reviews about vendor size and longevity prior to the acquisition.

Interpretation:

• Positive comments relate to perceived reliability and security posture; negative comments focus on usability and strategic/vendor risk rather than documented data correctness.

Searches performed for this report did not surface prominent, high-signal community threads about day-to-day developer experience, outages, or pricing surprises. This could reflect an enterprise/procurement-driven customer base or that discussions are focused on specific API names rather than the vendor brand.

Organizations seeking unfiltered feedback should consider:

• Reference calls with customers in similar industries or use cases
• RFP responses and security review artifacts
• Trial validation under production-like workloads

• The vendor publishes case studies claiming material market-data spend reductions for clients. Headline metrics are vendor-produced; methodology (baseline definitions, included cost categories, time period, and whether savings are gross or net of vendor fees) is not provided in public materials.

Critical evaluation: Treat such savings figures as directional. Procurement teams should request:

• Before/after architecture and vendor lists
• Exact cost categories included in reported savings
• How entitlement and usage governance were applied
• Verification evidence (e.g., audited invoices or independent assessments)

Xignite is a financial market data Data-as-a-Service provider focused on delivering market data via APIs (REST and SOAP) and related cloud tooling. The offering spans real-time, delayed, end-of-day, historical, reference, and fundamentals datasets across multiple asset classes (equities, ETFs/mutual funds, FX, futures/options, indices, fixed income/rates, company fundamentals, master/reference data, earnings/news). The product is primarily positioned around:

• Programmatic market data delivery (developer-facing APIs)
• Market data management and cost optimization for enterprises (positioned for market data managers, CDO/CIO/CTO personas)

The vendor describes the product as providing APIs and developer documentation, delivered from cloud infrastructure, with an emphasis on reliability, availability, broad coverage, and tiered support options.

Based on vendor positioning and public customer mentions, Xignite targets:

• Fintech applications and digital brokerages needing investor-facing quotes, charts, corporate actions, and multi-asset coverage.
• Wealth management and institutional platforms needing scalable consumption, entitlement control, and market data management capabilities.
• Enterprises modernizing market data stacks (cloud migration, cost governance, legacy interface emulation).

The vendor positions the product as APIs intended for enterprise market data use, occupying a space between lower-cost developer APIs (e.g., Alpha Vantage/Marketstack) and incumbent terminals/data feed vendors (e.g., FactSet/Bloomberg/Refinitiv). Competitive overlap varies depending on dataset scope and licensing requirements.