bas-in is no longer the home of Basin.
The engine, the CLI and all ten client SDKs now live together in a single
repository under the vul-os organisation.
Part of VulOS — the open, self-hostable web OS & app suite. Runs standalone, or as an app hosted by the Vulos OS.
Basin used to be spread across a dozen repositories in this organisation. They
were merged into one monorepo, with every commit preserved — the SDKs and
CLI kept their full authorship and history, rewritten only so their file paths
sit under the directory they now occupy. git log and git blame work
normally across the join.
The old repositories have been removed. Everything they contained is in the monorepo:
| Was | Now |
|---|---|
bas-in/basin |
vul-os/basin |
bas-in/basin-cli |
vul-os/basin → cli/ |
bas-in/basin-js |
vul-os/basin → sdks/js |
bas-in/basin-py |
vul-os/basin → sdks/py |
bas-in/basin-go |
vul-os/basin → sdks/go |
bas-in/basin-rust |
vul-os/basin → sdks/rust |
bas-in/basin-java |
vul-os/basin → sdks/java |
bas-in/basin-ruby |
vul-os/basin → sdks/ruby |
bas-in/basin-dotnet |
vul-os/basin → sdks/dotnet |
bas-in/basin-php |
vul-os/basin → sdks/php |
bas-in/basin-dart |
vul-os/basin → sdks/dart |
bas-in/basin-swift |
vul-os/basin → sdks/swift |
Links to github.com/bas-in/basin still redirect to the new location, so old
bookmarks and clone URLs keep working.
A bucket-native, multi-tenant Postgres alternative. Projects are S3 prefixes rather than databases, so operator cost tracks bytes actually stored instead of databases provisioned. One binary — pgwire on the front, Vortex-compressed columnar files on any S3-compatible bucket on the back. Your existing Postgres drivers work unchanged.
Apache-2.0, written in Rust, and self-hostable on your own box and your own bucket.
Read the docs · Source · VulOS