Home
Softono
c

canner

Professional software vendor delivering innovative solutions on the Softono platform. Specialized in both open-source and proprietary software development.

Total Products
2

Software by canner

WrenAI
Open Source

WrenAI

<div align="center" id="top"> <a href="https://getwren.ai"> <picture> <source media="(prefers-color-scheme: dark)" srcset="./misc/wrenai_logo_white.png"> <img src="./misc/wrenai_logo.png" width="300px" alt="WrenAI"> </picture> </a> ### The open context layer for AI agents over business data. *Your agent doesn't know what your data means. We fix that.* [Docs](https://docs.getwren.ai) Β· [Discord](https://discord.gg/5DvshJqG8Z) Β· [Vision](https://www.getwren.ai/post/the-missing-context-layer-for-ai-agents-over-business-data) Β· [Blog](https://www.getwren.ai/blog) [![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE) [![PyPI](https://img.shields.io/pypi/v/wrenai?label=wrenai)](https://pypi.org/project/wrenai/) [![GitHub Release](https://img.shields.io/github/v/release/Canner/WrenAI?logo=github&label=release)](https://github.com/Canner/WrenAI/releases) [![Discord](https://img.shields.io/discord/1227143286951514152?logo=discord&label=Discord)](https://discord.gg/5DvshJqG8Z) [![Last commit](https://img.shields.io/github/last-commit/Canner/WrenAI)](https://github.com/Canner/WrenAI/commits/main) [![Follow on X](https://img.shields.io/badge/follow-@getwrenai-blue?logo=x&logoColor=white)](https://x.com/getwrenai) [![Made by Canner](https://img.shields.io/badge/made_by-Canner-blue)](https://cannerdata.com) ![Stars](https://img.shields.io/github/stars/Canner/WrenAI?style=social) <a href="https://trendshift.io/repositories/9263" target="_blank"><img src="https://trendshift.io/api/badge/repositories/9263" alt="Canner/WrenAI | Trendshift" width="250" height="55" /></a> </div> > πŸ“£ **2026-05-07** β€” Wren Engine has merged into this repo under [`core/`](./core). The previous `Canner/wren-engine` repo is archived. The previous WrenAI GenBI app is preserved on the [`legacy/v1`](https://github.com/Canner/WrenAI/tree/legacy/v1) branch (tag `v1-final`). [Read the announcement β†’](https://github.com/Canner/WrenAI/discussions/2205) <!-- πŸ“Ί HERO DEMO (place here) ───────────────────────── Suggested: a 5–10 second silent loop showing: 1. Terminal: `wren skills get onboarding` (agent fetches the workflow guide from the CLI) 2. Agent walks the user through setup, then writes SQL via `wren query` β€” visible reasoning trace 3. Final result table Format: .gif (≀2 MB) or .mp4 (autoplay-muted). Save under /assets/wrenai-demo.gif and use the line below: <img src="./assets/wrenai-demo.gif" alt="Wren AI in action" width="820" /> --> --- ## What WrenAI is WrenAI is the **open context layer** that gives your agents what schemas don't: business semantics, examples, memory, governance, and β€” soon β€” the unstructured corporate knowledge that lives in your docs, wikis, and chat threads. Built for the agent frameworks you already use. ![Wren AI architecture](./misc/wren-ai-architecture.png) ## Why agent builders pick WrenAI - **Open by default** β€” Open-sourced core, SDK, and skills through Apache-2.0 license. - **Built for AI agents** β€” Skills, agentic architecture, context retrieval are first-class. Ships as SDKs for the agent frameworks that engineers already use. - **Correctness as primitives** β€” rich schema retrieval, dry-plan validation, structured errors with hints, value profiling, eval runner. The agent orchestrates; the trace lives in the agent's reasoning. - **Reviewable, reproducible context** β€” every definition, example, and mapping is versionable and evidence-linked. Git-friendly. - **Sits on top of your existing stack** β€” warehouse, transformation pipelines, your existing semantic layer. Not another tool to maintain. ## With & Without Wren AI Agents are everywhere. Claude Code, Cursor, ChatGPT, Aider, LangChain pipelines, Pydantic AI flows, in-house copilots, customer-facing apps. None of them should have to rediscover your business logic from scratch. With Wren AI, "the context layer," they query through a standalone, shared interface usable by every agent and person, not gated behind a single vendor's UI and architecture. <img width="1445" height="758" alt="before & after" src="https://github.com/user-attachments/assets/d6ef8b73-b844-4e11-9586-b4f7ab6ae9dc" /> ## Quickstart WrenAI is **agent-driven by design**: install the CLI, install a one-file discovery stub for your AI client, then let your AI agent drive the rest. Workflow guides live inside the CLI itself and are served on demand, so content always matches the installed version. ### 1. Install the CLI ```bash pip install wrenai # core (DuckDB included) pip install "wrenai[postgres,memory]" # add per-datasource and memory extras as needed ``` > **Tip for users in mainland China:** If `pip install` is slow or fails, use the Tsinghua mirror: > ```bash > pip install wrenai -i https://pypi.tuna.tsinghua.edu.cn/simple > ``` > If HuggingFace model downloads time out, add `export HF_ENDPOINT=https://hf-mirror.com` before running the CLI. ``` ### 2. Install the discovery stub for your AI client ```bash npx skills add Canner/WrenAI # auto-detects Claude Code, Cursor, Cline, Codex, … ``` The stub is ~50 lines. It teaches your agent to fetch workflow guides via `wren skills get <name>` and shaped prompts via `wren ask "<question>" --guided|--direct` β€” everything else lives in the CLI. ### 3. Ask your agent to set things up Open your agent in a project directory and say something like: > "Use Wren to set up my Postgres database." The agent runs `wren skills get onboarding`, follows the guide step-by-step, checks your environment, creates a connection profile, scaffolds the project, and runs a first query. ### 4. (Optional) Enrich the project Once onboarding finishes, ask: > "Enrich my Wren project with the business context in `raw/`." The agent runs `wren skills get enrich-context` and follows the guide in **grill** mode (one question at a time) or **auto-pilot** mode (agent reads `<project>/raw/` and proposes). Both modes write to MDL, instructions, queries, and memory β€” all reviewable, all Git-friendly. ### 5. Ask questions > "Who are our top 10 customers by sales this quarter?" Your agent fetches MDL context, recalls similar past queries, writes governed SQL, and executes via `wren query`. **Want to try it without your own database?** Ask your agent to use the bundled `jaffle_shop` sample dataset β€” same flow, querying a real warehouse end-to-end in a couple of minutes. ## Two beats: scaffold fast, enrich deep ```bash # Day 1 β€” agent-driven wren skills get onboarding # workflow guide: set up project + first query wren skills get enrich-context # workflow guide: add business context (cubes, units, enums) # Day-to-day wren query --sql '...' # query through the MDL semantic layer wren ask "<question>" --guided # wrap a question for a weaker agent wren ask "<question>" --direct # wrap a question for a stronger agent ``` Fast at first. Deep when you need it. Always reviewable and Git-friendly. <!-- πŸ“· OPTIONAL: 2-up screenshot showing grill mode (left) vs auto-pilot mode (right). Save under /assets/two-beats.png --> ## What's Included - **Modeling Definition Language (MDL)** β€” models, columns, relationships, views, cubes, metrics, row-level / column-level access control (RLAC / CLAC) - **Engine** β€” Apache DataFusion based, 22+ data sources - **Memory & examples** β€” LanceDB-backed, hybrid retrieval, versionable - **Agent SDK** β€” `wren-langchain` (LangChain / LangGraph), `wren-pydantic`; reference Python integration for other stacks - **Governed execution primitives** β€” functions, dry-plan, row limits, access control ## What's next - **Context enrichment skill** β€” `/wren-enrich-context` (grill + auto-pilot modes) hardened across MDL, instructions, queries, and memory - **End-to-end correctness primitives** β€” value profiling, rich retrieval, structured errors, golden eval runner - **Agent-native distribution** β€” first-class SDKs across major agent frameworks; see [GitHub Discussions](https://github.com/Canner/WrenAI/discussions) for what's prioritized next - **Full governed execution** β€” audit logs, rate limits, approval workflow, data-flow inspector <!-- TODO: vision_paper_en.md is currently at .tmp/roadmap-discuss/vision_paper_en.md β€” move to a published path (e.g. docs/vision-paper.md or repo root) and update this link before publishing. --> Full roadmap and design notes: see the [vision paper](https://docs.getwren.ai/oss/introduction). ## Documentation - [Quickstart](https://docs.getwren.ai/oss/get_started/quickstart) β€” from skill install to first answer - [Concepts](https://docs.getwren.ai/oss/concepts/what_is_context) β€” what context is, what MDL is, how memory works - [Connect a database](https://docs.getwren.ai/oss/guides/connect/overview) β€” Postgres, BigQuery, Snowflake, DuckDB, and more - [Agent SDKs](https://docs.getwren.ai/oss/sdk/overview) β€” what's shipping today, what's next ## Community - πŸ’¬ [Discord](https://discord.gg/5DvshJqG8Z) β€” chat with the team and other builders - πŸ™ [GitHub Discussions](https://github.com/Canner/WrenAI/discussions) β€” design conversations, RFCs, longer threads - 🐦 [Twitter / X](https://x.com/getwrenai) β€” release notes and short updates - πŸ—ž [Blog](https://www.getwren.ai/blog) β€” vision, post-mortems, deep dives ## Contributing We build in the open. Issues, PRs, connector contributions, SDK integrations, docs fixes β€” all welcome. - [Contributor guide](./CONTRIBUTING.md) - [Connector ecosystem program](./docs/contributing-a-connector.md) β€” three-tier ownership: official, community-blessed, community-owned - [Architecture map](./docs/architecture.md) β€” find the right place to land your change - Looking for somewhere to start? Try the [`good first issue`](https://github.com/Canner/WrenAI/labels/good%20first%20issue) label. <details> <summary><strong>Project structure</strong> β€” click to expand</summary> ``` core/ wren-core/ Rust semantic engine (Apache DataFusion) wren-core-base/ Shared manifest types + MDL builder wren-core-py/ Python bindings (PyPI: wren-core) wren-core-wasm/ WebAssembly build (npm: wren-core-wasm) wren/ Python SDK and CLI (PyPI: wrenai) wren-mdl/ MDL JSON schema sdk/ wren-langchain/ Reference agent SDK integration skills/ Agent skills for context authoring docs/ Module documentation examples/ Example projects ``` </details> ## Contributors <a href="https://github.com/Canner/WrenAI/graphs/contributors"> <img src="https://contrib.rocks/image?repo=Canner/WrenAI" alt="WrenAI contributors" /> </a> ## License Apache 2.0. See [LICENSE](./LICENSE). --- <div align="center"> *Come build the context layer with us.* **If WrenAI helps you, drop a ⭐ β€” it genuinely helps us grow!** <p><a href="#top">⬆️ Back to top</a></p> </div>

AI Agents BI Dashboards
15.5K Github Stars
vulcan-sql
Open Source

vulcan-sql

<p align="center"> <img src="https://i.imgur.com/9xLnLed.png" width="600" > </p> <p align="center"> <a aria-label="Canner" href="https://cannerdata.com/"> <img src="https://img.shields.io/badge/%F0%9F%A7%A1-Made%20by%20Canner-orange?style=for-the-badge"> </a> <a aria-label="NPM version" href="https://www.npmjs.com/package/@vulcan-sql/core"> <img alt="" src="https://img.shields.io/npm/v/@vulcan-sql/core?color=orange&style=for-the-badge"> </a> <a aria-label="License" href="https://github.com/Canner/vulcan-sql/blob/develop/LICENSE"> <img alt="" src="https://img.shields.io/github/license/canner/vulcan-sql?color=orange&style=for-the-badge"> </a> <a aria-label="Follow us" href="https://twitter.com/vulcansql"> <img alt="" src="https://img.shields.io/badge/-@vulcansql-orange?style=for-the-badge&logo=twitter&logoColor=white&labelColor=gray&logoWidth=20"> </a> <a href="https://img.shields.io/codecov/c/gh/Canner/vulcan-sql" > <img alt="" src="https://img.shields.io/codecov/c/gh/Canner/vulcan-sql?style=for-the-badge&color=orange&labelColor=gray&logoColor=white&logoWidth=20"/> </a> </p> ## What is VulcanSQL? **[VulcanSQL](https://vulcansql.com/) is an Analytical Data API Framework for AI agents and data apps**. It aims to help data professionals deliver RESTful APIs from databases, data warehouses or data lakes much easier and secure. It turns your SQL into APIs in no time! ![overview of VulcanSQL](https://i.imgur.com/JvCIZQ1.png) ## Why VulcanSQL? Given the vast amount of analytical data in databases, data warehouses, and data lakes, there is currently no easy method for data professionals to share data with relevant stakeholders for operational business use cases. Without a specialized framework to streamline the creation of APIs for AI agents and apps to interact with databases and data warehouses, developers today must undertake a more manual and complex process. This approach comes with several pain points and challenges: ### Traditional Approach and Pain Points #### 1. Custom API Development: - **Time-Consuming**: Developers need to manually code the APIs, which can be time-consuming, especially for complex applications or when dealing with multiple data sources. - **Error-Prone**: Manual coding increases the risk of bugs and errors, which can affect the reliability and performance of the APIs. #### 2. Integration Complexity: - **Diverse Data Sources**: Integrating multiple data sources with different formats and protocols requires significant effort and expertise. - **Lack of Standardization**: Without a standardized approach, each API might follow different conventions, making it harder for AI agents to interact with them consistently. #### 3. Security and Compliance: - **Security Risks**: Ensuring that APIs are secure and that data access complies with regulations (e.g., GDPR, HIPAA) requires additional layers of work, including authentication, authorization, and data encryption. - **Maintenance Overhead**: Security and compliance requirements can evolve, necessitating ongoing maintenance and updates to the APIs. #### 4. Scalability and Performance: - **Scalability Concerns**: Custom-built APIs may not be optimized for scalability, leading to performance issues as the number of requests or the volume of data grows. - **Resource Intensive**: Optimizing for performance and scalability can require significant resources, both in terms of development time and infrastructure. #### 5. Documentation and Usability: - **Lack of Documentation**: Properly documenting APIs for easy understanding and use by other developers or AI agents can be overlooked or undervalued. - **Usability Issues**: Without clear and comprehensive documentation, it becomes challenging for others to integrate with and effectively use the APIs. ### With **VulcanSQL** you can - **Rapid Development and Integration**: By abstracting the complexities of directly interacting with databases and data warehouses, developers can focus on the higher-level logic of their applications. This reduces the development time and simplifies the process of integrating AI capabilities into applications. - **Standardization**: Utilizing OpenAPI documents for interaction provides a standardized way for AI agents to understand and interact with different APIs. This promotes interoperability among various systems and tools, making it easier to integrate with a wide array of services and data sources. - **Scalability and Maintenance**: A template-driven approach to API creation can make it easier to scale and maintain APIs over time. Changes in the underlying data schema or business logic can be propagated to the APIs more efficiently, without the need for extensive manual adjustments. - **Accessibility**: Making data more accessible to AI agents through well-defined APIs can unlock new insights and capabilities by leveraging machine learning and analytics. This can enhance decision-making processes and automate routine tasks, among other benefits. ## Online Playground Use [Online Playground](https://codesandbox.io/p/sandbox/vulcansql-demo-wfd834) to get a taste of VulcanSQL! ## Installation Please visit [the installation guide](https://vulcansql.com/docs/get-started/installation). ## Examples Need inspiration? Here are a [selected compilation of examples](https://github.com/Canner/vulcan-sql-examples) showcasing how you can use VulcanSQL! ## How VulcanSQL works? πŸ’» **Build** VulcanSQL offers a development experience similar to dbt. Just insert variables into your templated SQL. VulcanSQL accepts input from your API and generates SQL statements on the fly. πŸš€ **Accelerate** VulcanSQL uses DuckDB as a caching layer, boosting your query speed and reducing API response time. This means faster, smoother data APIs for you and less strain on your data sources. πŸ”₯ **Deploy** VulcanSQL offers flexible deployment options - whether you prefer Docker or command-based setups. Our `package` command assists in bundling your assets, ensuring a smooth transition from development to deployment of your data APIs. ❀️ **Share** VulcanSQL offers many data sharing options, seamlessly integrating your data into familiar applications within your workflow and build AI agents. ## Documentation Below are some common scenarios that you may be interested: - [Getting Started](https://vulcansql.com/docs/get-started/first-api) - [Introduction](https://vulcansql.com/docs/intro) - [Guides to Build Data APIs](https://vulcansql.com/docs/develop/init) - [Connecting to Data Sources](https://vulcansql.com/docs/connectors/overview) - [Writing SQL Templates](https://vulcansql.com/docs/develop/overview) - [Caching Datasets](https://vulcansql.com/docs/develop/cache) - [Error Handling](https://vulcansql.com/docs/develop/error) - [API Parameters Validation](https://vulcansql.com/docs/develop/validator) - [Data Privacy](https://vulcansql.com/docs/data-privacy/overview) - [Extensions](https://vulcansql.com/docs/extensions/overview) - [API Configurations](https://vulcansql.com/docs/api-plugin/overview) - [Deployment](https://vulcansql.com/docs/deployment) ## Use Cases πŸ€– **AI agents**: Streamline the creation of APIs for AI agents to interact with databases and data warehouses. πŸ“ˆ **Customer-facing analytics**: Expose analytics in your SaaS product for customers to understand how the product is performing for them via customer dashboards, insights, and reports. πŸ‘ **Data sharing**: Sharing data with partners, vendors, or customers, which requires a secure and scalable way to expose data. βš™οΈ **Internal tools**: Integration with internal tools like Zapier, AppSmith and Retools, etc. ## Community - If there is any issues, please visit [Github Issues](https://github.com/Canner/vulcan-sql/issues).

AI Agents API Tools Data Warehouses
792 Github Stars