JustyBase
Developer tools for data teams
Focused database tooling for Netezza, SQL workflows, and data platforms — from the editor to drivers and libraries that keep context visible and results close.
01 / PRODUCTS
Five flagship projects for the path from editor to query result.
A Netezza-first SQL extension for Visual Studio Code with a built-in JavaScript driver, full Netezza/PureData tooling, and optional packs for other databases.
Explore the VS Code extensionCross-platform desktop SQL IDE for IBM Netezza with a fast editor, schema exploration, Git-aware workflows, data tools, and optional local AI assistance.
Explore JustyBaseWindows desktop SQL client for Netezza-first authoring — SQL editor, result grid, object explorer, encrypted connection profiles, and tagged releases with an Inno Setup installer.
Explore JustyBase.LegacyC#/.NET project for bringing UCanAccess-style Microsoft Access database connectivity into the JustyBase toolkit.
View on GitHubHigh-performance IBM Netezza driver for Python — hard fork of nzpy with a C extension, async API, streaming bulk load, and pre-built wheels for Linux, macOS, and Windows.
pip install nzpy-extended
02 / OPEN SOURCE
Supporting libraries across .NET, Java, TypeScript, and Python — same org, same focus.
.NET libraries for Netezza SQL parsing, formatting, linting, DDL generation, and catalog metadata queries.
Pure C# ADO.NET driver for IBM Netezza — no native dependencies, sync/async API, pooling, and AOT-compatible.
DBeaver extension for clipboard/Excel import-export, table creation, and Netezza-friendly DDL.
High-performance .NET library for reading and writing Excel files (.xlsx, .xlsb).
High-performance TypeScript library for XLSB/XLSX read and write — XLSB markedly faster than XLSX.
Python library for efficient XLSB/XLSX read and write, with optional C acceleration.
Pure TypeScript Netezza / PureData driver for Node.js with connection pooling, SSL, and an ADO.NET-style Connection/Command/Reader API.
03 / APPROACH
Database work is already complex. The tools around it should make state, intent, and results easier to see — from the editor through drivers and SQL toolkits to spreadsheet I/O.