Busabase
Busabase is an open-source (MIT) database and workspace for AI agents — data, docs, skills, and apps in one place. Run it locally, self-host it inside your network, or use Busabase Cloud, and turn age
翻訳待ち
Materialize is the live context layer for agents and apps. It lets engineering teams use SQL to transform siloed operational data into real-time data products they can trust. Organizations from Notion
翻訳待ち
データRust · PythonGitHub @MaterializeIncオンライン所有者未確認
Have you tried it? One tap is enough. No sign-in needed.
The live data layer for apps and AI agents. Create up-to-the-second views into your business, just using SQL
翻訳待ち
Loading the full README. The saved excerpt is shown below.
Materialize is a real-time data integration platform that creates and continually updates consistent views of transactional data from across your organization. Its SQL interface democratizes the ability to serve and access live data. Materialize can be deployed anywhere your infrastructure runs.
Use Materialize to do things like deliver fresh context for AI/RAG pipelines, power operational dashboards, and create more dynamic customer experiences without building time-consuming custom data pipelines.
The three most common patterns for adopting Materialize are the following:Read the full README ↗Materialize is a real-time data integration platform that creates and continually updates consistent views of transactional data from across your organization. Its SQL interface democratizes the ability to serve and access live data. Materialize can be deployed anywhere your infrastructure runs.
Use Materialize to do things like deliver fresh context for AI/RAG pipelines, power operational dashboards, and create more dynamic customer experiences without building time-consuming custom data pipelines.
The three most common patterns for adopting Materialize are the following:
Ready to try out Materialize? You can sign up for a free cloud trial or download our community edition, which is free forever for deployments using less than 24 GiB of memory and 48 GiB of disk!
Have questions? We'd love to hear from you:
Materialize focuses on providing correct and consistent answers with minimal latency, and does not ask you to accept either approximate answers or eventual consistency. This guarantee holds even when joining data from multiple upstream systems. Whenever Materialize answers a query, that answer is the correct result on some specific (and recent) version of your data. Materialize does all of this by recasting your SQL queries as dataflows, which can react efficiently to changes in your data as they happen.
Our fully managed service is cloud-native, featuring high availability through multi-active replication, horizontal scalability by seamlessly scaling dataflows across multiple machines, and near-infinite storage by leveraging cloud object storage (e.g., Amazon S3). You can self-manage Materialize using our Enterprise or Community editions.
We support a large fraction of PostgreSQL features and are actively expanding support for more built-in PostgreSQL functions. Please file an issue if you have an idea for an improvement!
Materialize can read data directly from a PostgreSQL or MySQL replication stream, from Kafka (and other Kafka API-compatible systems like Redpanda), or from SaaS applications via webhooks.
Once you've got the data in, define views and perform reads via the PostgreSQL protocol. Use your favorite SQL client, including the psql you probably already have on your system. Customers using Materialize in production tend to use dbt Core.
Materialize supports a comprehensive variety of SQL features, all using the PostgreSQL dialect and protocol:
min, max, count, sum, stddev, etc.HAVINGORDER BYLIMITDISTINCT->, ->>, @>, ?, jsonb_array_element, jsonb_each. Materialize automatically plans lateral joins for efficient jsonb_each support.We’ve also extended our SQL support to enable recursion that supports incrementally updating tree and graph structures.
Here's an example join query that works fine in Materialize, TPC-H query 15:
This is the beginning of the README. Read the rest at the original. Read the full README ↗