by SQLStack
Streaming pipelines for ClickHouse, in typed SQL.
Change your SQL, see exactly what will rebuild, and replay it from retained stream history.
Website ·
Get started ·
Docs ·
Demo
SQLTide brings dbt-style authoring and deployment to streaming. Models compile into ClickHouse tables and materialized views, every build shows its plan first, and a change to your logic is rebuilt from retained Kafka history.
uv tool install sqltide # or: pip install sqltide
Key features
- Typed SQL models. Explicit output types,
__source()and__ref()dependencies, and offline compilation with no warehouse connection. - Replay-aware builds. Affected models are reconstructed from retained stream history.
- Plans before changes.
sqt planis read-only, andsqt buildreplans against current warehouse state before it runs. - Staged deployments. Build virtually, then audit, promote, and roll back.
- Quality built in. SQL tests, audits, sensors, and SQLClean rules and formatting.
- A UI for operating it. Sources, lag, lineage, plans, runs, and quality in
sqt dev, with trusted-proxy or password authentication for shared installations.
Example
A source and a model:
sources:
- name: orders
kind: kafka
broker_list: kafka:9092
topic: source.orders
replay_boundary:
mode: offsets
MODEL (
engine "MergeTree()",
order_by ["order_id", "_replay_partition", "_replay_offset"],
);
SELECT
order_id::String AS order_id,
_replay_partition::Int32 AS _replay_partition,
_replay_offset::Int64 AS _replay_offset,
_replay_timestamp::DateTime64(3) AS _replay_timestamp
FROM __source("orders")
Quick start
sqt discover # inspect authored resources
sqt compile # validate offline
sqt plan # read-only warehouse plan
sqt build # confirm and execute
sqt test
sqt audit
sqt dev # local UI at 127.0.0.1:8000
The orders demo runs the whole workflow locally with Redpanda and ClickHouse. See the quickstart to start your own project.
Documentation
- Models and pipelines
- Replay and lineage
- Deployments
- Destructive operations
- Project configuration
- SQL Rules and formatting
- Changelog and contributing
License
Apache-2.0
1 maintainer
Metadata
1 maintainer
Release files for sqltide 0.65.16
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sqltide-0.65.16.tar.gz | 2.3 MB | With provenance | Details for sqltide-0.65.16.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| sqltide-0.65.16-cp312-abi3-win_amd64.whl | CPython 3.12 | abi3 | Windows x86-64 | Details for sqltide-0.65.16-cp312-abi3-win_amd64.whl |
| sqltide-0.65.16-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl | CPython 3.12 | abi3 | Linux glibc 2.17+ x86-64 | Details for sqltide-0.65.16-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
| sqltide-0.65.16-cp312-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl | CPython 3.12 | abi3 | Linux glibc 2.17+ ARM64 | Details for sqltide-0.65.16-cp312-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
| sqltide-0.65.16-cp312-abi3-macosx_11_0_arm64.whl | CPython 3.12 | abi3 | macOS 11.0+ ARM64 | Details for sqltide-0.65.16-cp312-abi3-macosx_11_0_arm64.whl |
| sqltide-0.65.16-cp312-abi3-macosx_10_12_x86_64.whl | CPython 3.12 | abi3 | macOS 10.12+ x86-64 | Details for sqltide-0.65.16-cp312-abi3-macosx_10_12_x86_64.whl |
Total release size: 110.1 MB
Release files / sqltide-0.65.16.tar.gz
| Download URL | sqltide-0.65.16.tar.gz |
|---|---|
| Size | 2.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
191ba97e87b558e42d701af2f77546cf420a03db5771f19fac9e8f1abf45810b
|
|
BLAKE2b-256 checksum How to use checksums |
273a4d91101d0a35de297d9c1b0aed843e5735a3635ff8cb9ef4bfd7449aa1f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logRelease files / sqltide-0.65.16-cp312-abi3-win_amd64.whl
| Download URL | sqltide-0.65.16-cp312-abi3-win_amd64.whl |
|---|---|
| Size | 23.6 MB |
| Tags | CPython 3.12 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
4da2759b85c6b08a1cc5a0f0ad4afa47e6ec097f32898778d70b52963b3b8e15
|
|
BLAKE2b-256 checksum How to use checksums |
c0dac020047c56b339780a7d2cf8ea1117d79f20f5e7360179f039202541d2b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logRelease files / sqltide-0.65.16-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | sqltide-0.65.16-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 21.4 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
77d89ac4c1c5484699c48e8c7d0c85019015707da91c8eb641724a7784e3413b
|
|
BLAKE2b-256 checksum How to use checksums |
fb002da66fbbd8878fb31043111337e9fd849ea18da031d5681f187c1f2cef09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logRelease files / sqltide-0.65.16-cp312-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
| Download URL | sqltide-0.65.16-cp312-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
|---|---|
| Size | 20.7 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
d6f4bc5a71a800ebae1bb97f21d5dbf5e841c881c6dc32b864d03afab9d1756d
|
|
BLAKE2b-256 checksum How to use checksums |
fafb6d0b58d5af20670fc58c726122eede1bbd3b5b4d36160c2dfa5d670c43ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logRelease files / sqltide-0.65.16-cp312-abi3-macosx_11_0_arm64.whl
| Download URL | sqltide-0.65.16-cp312-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 20.6 MB |
| Tags | CPython 3.12 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
3632c26b65b600e119e7ed1ee342b5684d050256bd45ca367ac6772c0073bfc2
|
|
BLAKE2b-256 checksum How to use checksums |
97f17e324276e2544b647d83db85cb9c28a7621ae5461b1d08aaa2c901d0c431
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logRelease files / sqltide-0.65.16-cp312-abi3-macosx_10_12_x86_64.whl
| Download URL | sqltide-0.65.16-cp312-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 21.4 MB |
| Tags | CPython 3.12 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
310cf5b0ecb700b89f55591aaadf17c5c9502582aa63706f2a24434db5b8c7ad
|
|
BLAKE2b-256 checksum How to use checksums |
57b949429c5c5f3f9593abcb2d6c0a1ba94e698c8be74d8d55fbe89de1f2b6ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logSecurity for sqltide 0.65.16
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 6 files in this release have been uploaded with provenance metadata.
Attestation for sqltide-0.65.16.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
