bosun-ai/swiftide

Fast, streaming indexing and query library for AI (RAG) applications, written in Rust

Table of Contents

• About The Project

• Latest updates on our blog 🔥

• Example

• Vision

• Features

  • In detail

• Getting Started

  • Prerequisites
  • Installation

• Usage and concepts

• Roadmap

• Contributing

• License

Swiftide

Fast, streaming indexing and query library for AI applications, written in Rust
Read more on swiftide.rs »

API Docs · Report Bug · Request Feature · Discord

About The Project

Swiftide is a data indexing, processing and query library, tailored for Retrieval Augmented Generation (RAG). When building applications with large language models (LLM), these LLMs need access to external resources. Data needs to be transformed, enriched, split up, embedded, and persisted. Queries can then be augmented by retrieving the indexed data and generating an answer. It is build in Rust, using parallel, asynchronous streams and is blazingly fast.

With Swiftide, you can build your AI application from idea to production in a few lines of code.

While working with other Python-based tooling, frustrations arose around performance, stability, and ease of use. Thus, Swiftide was born. Indexing performance went from tens of minutes to a few seconds.

Part of the bosun.ai project. An upcoming platform for autonomous code improvement.

We <3 feedback: project ideas, suggestions, and complaints are very welcome. Feel free to open an issue or contact us on discord.

Caution

Swiftide is under heavy development and can have breaking changes while we work towards 1.0. Documentation here might fall short of all features, and despite our efforts be slightly outdated. Expect bugs. We recommend to always keep an eye on our github and api documentation. If you found an issue or have any kind of feedback we'd love to hear from you in an issue.

(back to top)

Latest updates on our blog 🔥

• Release - Swiftide 0.8 (2024-08-12)
• Release - Swiftide 0.7 (2024-07-28)
• Building a code question answering pipeline (2024-07-13)
• Release - Swiftide 0.6 (2024-07-12)
• Release - Swiftide 0.5 (2024-07-1)

(back to top)

Example

indexing::Pipeline::from_loader(FileLoader::new(".").with_extensions(&["rs"]))
        .with_default_llm_client(openai_client.clone())
        .filter_cached(Redis::try_from_url(
            redis_url,
            "swiftide-examples",
        )?)
        .then_chunk(ChunkCode::try_for_language_and_chunk_size(
            "rust",
            10..2048,
        )?)
        .then(MetadataQACode::default())
        .then(move |node| my_own_thing(node))
        .then_in_batch(10, Embed::new(openai_client.clone()))
        .then_store_with(
            Qdrant::builder()
                .batch_size(50)
                .vector_size(1536)
                .build()?,
        )
        .run()
        .await?;

You can find more examples in /examples

(back to top)

Vision

Our goal is to create a fast, extendable platform for data indexing and querying to further the development of automated LLM applications, with an easy-to-use and easy-to-extend api.

(back to top)

Features

• Fast, modular streaming indexing pipeline with async, parallel processing
• Experimental query pipeline
• A variety of loaders, transformers, semantic chunkers, embedders, and more
• Bring your own transformers by extending straightforward traits or use a closure
• Splitting and merging pipelines
• Jinja-like templating for prompts
• Store into multiple backends
• Integrations with OpenAI, Groq, Redis, Qdrant, Ollama, FastEmbed-rs, and Treesitter
• Sparse vector support for hybrid search
• tracing supported for logging and tracing, see /examples and the tracing crate for more information.

In detail

Feature	Details
Supported Large Language Model providers	OpenAI (and Azure) - All models and embeddings AWS Bedrock - Anthropic and Titan Groq - All models Ollama - All models
Loading data	Files Scraping Other pipelines and streams
Transformers and metadata generation	Generate Question and answerers for both text and code (Hyde) Summaries, titles and queries via an LLM Extract definitions and references with tree-sitter
Splitting and chunking	Markdown Code (with tree-sitter)
Storage	Qdrant Redis

(back to top)

Getting Started

Prerequisites

Make sure you have the rust toolchain installed. rustup Is the recommended approach.

To use OpenAI, an API key is required. Note that by default async_openai uses the OPENAI_API_KEY environment variables.

Other integrations will need to be installed accordingly.

Installation

1. Set up a new Rust project

2. Add swiftide

   cargo add swiftide

3. Enable the features of integrations you would like to use in your Cargo.toml

4. Write a pipeline (see our examples and documentation)

(back to top)

Usage and concepts

Before building your stream, you need to enable and configure any integrations required. See /examples.

A stream starts with a Loader that emits Nodes. For instance, with the Fileloader each file is a Node.

You can then slice and dice, augment, and filter nodes. Each different kind of step in the pipeline requires different traits. This enables extension.

Nodes have a path, chunk and metadata. Currently metadata is copied over when chunking and always embedded when using the OpenAIEmbed transformer.

• from_loader (impl Loader) starting point of the stream, creates and emits Nodes
• filter_cached (impl NodeCache) filters cached nodes
• then (impl Transformer) transforms the node and puts it on the stream
• then_in_batch (impl BatchTransformer) transforms multiple nodes and puts them on the stream
• then_chunk (impl ChunkerTransformer) transforms a single node and emits multiple nodes
• then_store_with (impl Storage) stores the nodes in a storage backend, this can be chained

Additionally, several generic transformers are implemented. They take implementers of SimplePrompt and EmbedModel to do their things.

Note

No integrations are enabled by default as some are code heavy. Either cherry-pick the integrations you need or use the "all" feature flag.

Warning

Due to the performance, chunking before adding metadata gives rate limit errors on OpenAI very fast, especially with faster models like 3.5-turbo. Be aware.

For more examples, please refer to /examples and the Documentation

(back to top)

Roadmap

See the open issues for a full list of proposed features (and known issues).

(back to top)

Community

If you want to get more involved with Swiftide, have questions or want to chat, you can find us on discord.

(back to top)

Contributing

Swiftide is in a very early stage and we are aware that we lack features for the wider community. Contributions are very welcome. 🎉

If you have a great idea, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!

If you just want to contribute (bless you!), see our issues.

1. Fork the Project
2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
3. Commit your Changes (git commit -m 'feat: Add some AmazingFeature')
4. Push to the Branch (git push origin feature/AmazingFeature)
5. Open a Pull Request

See CONTRIBUTING for more

(back to top)

License

Distributed under the MIT License. See LICENSE for more information.

(back to top)