Ryft
Ryft is the intelligent Apache Iceberg management platform - a data lakehouse optimization layer that continuously monitors, manages, and optimizes Iceberg tables across query engines and clouds. It provides automated table compaction, snapshot and data lifecycle management, orphan-file and compliance cleanup (GDPR/CCPA), an Asset and Query Explorer, and usage-based self-tuning that reduces lakehouse TCO and speeds up queries. Ryft integrates with AWS (Athena, Glue, Redshift, S3 Tables), Google Cloud/BigLake, Azure, Microsoft OneLake, Databricks, Snowflake, Starburst, Trino, StarRocks, and any Iceberg REST Catalog. For engines it does not natively support, the Ryft Ingest API accepts query telemetry directly, and the Ryft MCP server enriches AI agents with live lakehouse context. Backed by Bessemer Venture Partners and Index Ventures; acquired by Cyera in 2026.
Ryft publishes 1 API on the APIs.io network: Ingest API. Tagged areas include Company, Data, Data Lake, Lakehouse, and Apache Iceberg.
Ryft’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, signup flow, authentication, and 13 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Ryft Ingest API
Push query-execution telemetry to Ryft.
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
ryft-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type