InlaySQL v0.0.6

InlaySQL v0.0.6

The engine, three ways: the inlaysql CLI (and MCP server),
the WASM module for JavaScript, and the C-ABI shared libraries
any FFI language can load in-process — the SQLite-like shape,
no server.

Artifacts

file	what it is
inlaysql-0.0.6-x86_64-unknown-linux-gnu.tar.gz	the CLI + MCP server (Linux)
inlaysql-ffi-0.0.6-aarch64-apple-darwin.tar.gz	C-ABI library (macOS, Apple silicon)
inlaysql-ffi-0.0.6-x86_64-unknown-linux-gnu.tar.gz	C-ABI library (Linux)
inlaysql-wasm-0.0.6.tar.gz	WASM module + the JS glue

Each .tar.gz ships beside a .sha256; verify with
sha256sum -c <file>.sha256.

No Windows build: the file layer is Unix-only today
(pread/pwrite, advisory locks) — a Windows port has not
been written. The WASM module runs anywhere a browser or
Node does, Windows included.

Use it like SQLite, in one command

Downloads the library for this machine and the client file for
your language into the current directory, and verifies both:

curl -fsSL https://github.com/inlaySQL/inlaysql/releases/download/v0.0.6/get-inlaysql.sh | sh -s -- php     # or python, ruby, csharp, java

Or take the two files by hand — each is its own asset below, with
a .sha256 beside it, and releases/latest/download/<file>
always points at the newest release:

file	what it is
libinlaysql_ffi-aarch64-apple-darwin.dylib	the engine, macOS Apple silicon
libinlaysql_ffi-x86_64-unknown-linux-gnu.so	the engine, Linux x86_64
inlaysql.php / inlaysql.py / inlaysql.rb / InlaySQL.cs / InlaySQL.java	the whole client for that language, one file
inlaysql.h	the C header, for anything else

The archives

Each FFI archive carries the 0.0.6 library, the
inlaysql.h header, and the wrappers/ directory — a
one-file class per language (inlaysql.php, inlaysql.py,
inlaysql.rb, InlaySQL.cs, InlaySQL.java), each the whole
binding for its language. Copy the one you need and open the
file like SQLite; the quickest introduction, with copy-paste
quickstarts for all five, is
docs/clients.md.

WASM payload

artifact	bytes	KiB	gzipped KiB
inlaysql_wasm_bg.wasm	3146401	3072	1038

Status: beta

The on-disk format is pre-1.0 — recreate, not migrate: a
database written by this version may not open in a later one.
The MySQL server mode binds 127.0.0.1 and is plaintext unless
you configure TLS; a bind that reaches another machine is
refused without accounts of the database's own and TLS
required, or --plaintext-network on a segment it checks is
private. The wire parser is young and its fuzzing campaigns
are new. Read
What this is not
before relying on this for anything real.

Reproduce every number in these notes with the scripts in
TESTING.md and bench/run.sh.

InlaySQL v0.0.5

InlaySQL v0.0.5

The engine, three ways: the inlaysql CLI (and MCP server),
the WASM module for JavaScript, and the C-ABI shared libraries
any FFI language can load in-process — the SQLite-like shape,
no server.

Artifacts

file	what it is
inlaysql-0.0.5-x86_64-unknown-linux-gnu.tar.gz	the CLI + MCP server (Linux)
inlaysql-ffi-0.0.5-aarch64-apple-darwin.tar.gz	C-ABI library (macOS, Apple silicon)
inlaysql-ffi-0.0.5-x86_64-unknown-linux-gnu.tar.gz	C-ABI library (Linux)
inlaysql-wasm-0.0.5.tar.gz	WASM module + the JS glue

Each .tar.gz ships beside a .sha256; verify with
sha256sum -c <file>.sha256.

No Windows build: the file layer is Unix-only today
(pread/pwrite, advisory locks) — a Windows port has not
been written. The WASM module runs anywhere a browser or
Node does, Windows included.

Using the C-ABI libraries

Each FFI archive carries the 0.0.5 library, the
inlaysql.h header, and the wrappers/ directory — a
one-file class per language (inlaysql.php, inlaysql.py,
inlaysql.rb, InlaySQL.cs, InlaySQL.java), each the whole
binding for its language. Copy the one you need and open the
file like SQLite; the quickest introduction, with copy-paste
quickstarts for all five, is
docs/clients.md.

Updated 2026-09-08 — what changed on main since this tag. The
inlaysql.php and inlaysql.py in this archive are the first, thin
clients (run/query/first, positional parameters, one exception
type). main now carries their second edition — execute with
rows_affected and last_insert_id, query returning iterable rows,
insert(table, row) returning the id, transaction(fn) with rollback and
conflict retry, :name parameters, typed exceptions — and the ABI grew
last_insert_id on the written outcome to support it, so those files need
the next library, not this one. The next release also attaches every
client file and each platform's bare library as its own asset, plus a
get-inlaysql.sh that fetches the right pair in one command:

curl -fsSL https://github.com/inlaySQL/inlaysql/releases/latest/download/get-inlaysql.sh | sh -s -- php

Until then, this archive's wrappers/ directory is the way in, and
docs/clients.md at this tag
describes exactly what it contains.

WASM payload

artifact	bytes	KiB	gzipped KiB
inlaysql_wasm_bg.wasm	3146234	3072	1038

Status: beta

The on-disk format is pre-1.0 — recreate, not migrate: a
database written by this version may not open in a later one.
The MySQL server mode binds 127.0.0.1 and is plaintext unless
you configure TLS; a bind that reaches another machine is
refused without accounts of the database's own and TLS
required, or --plaintext-network on a segment it checks is
private. The wire parser is young and its fuzzing campaigns
are new. Read
What this is not
before relying on this for anything real.

Reproduce every number in these notes with the scripts in
TESTING.md and bench/run.sh.

InlaySQL v0.0.4

InlaySQL v0.0.4

The engine, three ways: the inlaysql CLI (and MCP server),
the WASM module for JavaScript, and the C-ABI shared libraries
any FFI language can load in-process — the SQLite-like shape,
no server.

Artifacts

file	what it is
inlaysql-0.0.4-x86_64-unknown-linux-gnu.tar.gz	the CLI + MCP server (Linux)
inlaysql-ffi-0.0.4-aarch64-apple-darwin.tar.gz	C-ABI library (macOS, Apple silicon)
inlaysql-ffi-0.0.4-x86_64-unknown-linux-gnu.tar.gz	C-ABI library (Linux)
inlaysql-wasm-0.0.4.tar.gz	WASM module + the JS glue

Each .tar.gz ships beside a .sha256; verify with
sha256sum -c <file>.sha256.

No Windows build: the file layer is Unix-only today
(pread/pwrite, advisory locks) — a Windows port has not
been written. The WASM module runs anywhere a browser or
Node does, Windows included.

Using the C-ABI libraries

Each FFI archive carries the 0.0.4 library, the
inlaysql.h header, and the wrappers/ directory — a
one-file class per language (inlaysql.php, inlaysql.py,
inlaysql.rb, InlaySQL.cs, InlaySQL.java), each the whole
binding for its language. Copy the one you need and open the
file like SQLite; the quickest introduction, with copy-paste
quickstarts for all five, is
docs/clients.md.

WASM payload

artifact	bytes	KiB	gzipped KiB
inlaysql_wasm_bg.wasm	3146234	3072	1038

Status: beta

The on-disk format is pre-1.0 — recreate, not migrate: a
database written by this version may not open in a later one.
The MySQL server mode binds 127.0.0.1 and is plaintext unless
you configure TLS; a bind that reaches another machine is
refused without accounts of the database's own and TLS
required, or --plaintext-network on a segment it checks is
private. The wire parser is young and its fuzzing campaigns
are new. Read
What this is not
before relying on this for anything real.

Reproduce every number in these notes with the scripts in
TESTING.md and bench/run.sh.

InlaySQL v0.0.3

InlaySQL v0.0.3

The engine, three ways: the inlaysql CLI (and MCP server),
the WASM module for JavaScript, and the C-ABI shared libraries
any FFI language can load in-process — the SQLite-like shape,
no server.

Artifacts

file	what it is
inlaysql-0.0.3-x86_64-unknown-linux-gnu.tar.gz	the CLI + MCP server (Linux)
inlaysql-ffi-0.0.3-aarch64-apple-darwin.tar.gz	C-ABI library (macOS, Apple silicon)
inlaysql-ffi-0.0.3-x86_64-unknown-linux-gnu.tar.gz	C-ABI library (Linux)
inlaysql-wasm-0.0.3.tar.gz	WASM module + the JS glue

Each .tar.gz ships beside a .sha256; verify with
sha256sum -c <file>.sha256.

No Windows build: the file layer is Unix-only today
(pread/pwrite, advisory locks) — a Windows port has not
been written. The WASM module runs anywhere a browser or
Node does, Windows included.

Using the C-ABI libraries

Each FFI archive carries the 0.0.3 library, the
inlaysql.h header, and the wrappers/ directory — a
one-file class per language (inlaysql.php, inlaysql.py,
inlaysql.rb, InlaySQL.cs, InlaySQL.java), each the whole
binding for its language. Copy the one you need and open the
file like SQLite; the quickest introduction, with copy-paste
quickstarts for all five, is
docs/clients.md.

WASM payload

artifact	bytes	KiB	gzipped KiB
inlaysql_wasm_bg.wasm	3140887	3067	1036

Status: beta

The on-disk format is pre-1.0 — recreate, not migrate: a
database written by this version may not open in a later one.
The MySQL server mode is plaintext and localhost-first unless
you configure TLS. Read
What this is not
before relying on this for anything real.

Reproduce every number in these notes with the scripts in
TESTING.md and bench/run.sh.

InlaySQL v0.0.2

InlaySQL v0.0.2

The engine, three ways: the inlaysql CLI (and MCP server),
the WASM module for JavaScript, and the C-ABI shared libraries
any FFI language can load in-process — the SQLite-like shape,
no server.

Artifacts

file	what it is
inlaysql-0.0.2-x86_64-unknown-linux-gnu.tar.gz	the CLI + MCP server (Linux)
inlaysql-ffi-0.0.2-aarch64-apple-darwin.tar.gz	C-ABI library (macOS, Apple silicon)
inlaysql-ffi-0.0.2-x86_64-unknown-linux-gnu.tar.gz	C-ABI library (Linux)
inlaysql-wasm-0.0.2.tar.gz	WASM module + the JS glue

Each .tar.gz ships beside a .sha256; verify with
sha256sum -c <file>.sha256.

No Windows build: the file layer is Unix-only today
(pread/pwrite, advisory locks) — a Windows port has not
been written. The WASM module runs anywhere a browser or
Node does, Windows included.

Using the C-ABI libraries

Each FFI archive carries the 0.0.2 library, the
inlaysql.h header, and the wrappers/ directory — a
one-file class per language (inlaysql.php, inlaysql.py,
inlaysql.rb, InlaySQL.cs, InlaySQL.java), each the whole
binding for its language. Copy the one you need and open the
file like SQLite; the quickest introduction, with copy-paste
quickstarts for all five, is
docs/clients.md.

WASM payload

artifact	bytes	KiB	gzipped KiB
inlaysql_wasm_bg.wasm	3140887	3067	1036

Status: beta

The on-disk format is pre-1.0 — recreate, not migrate: a
database written by this version may not open in a later one.
The MySQL server mode is plaintext and localhost-first unless
you configure TLS. Read
What this is not
before relying on this for anything real.

Reproduce every number in these notes with the scripts in
TESTING.md and bench/run.sh.

InlaySQL v0.0.1.beta

InlaySQL v0.0.1.beta

The engine, three ways: the inlaysql CLI (and MCP server),
the WASM module for JavaScript, and the C-ABI shared libraries
any FFI language can load in-process — the SQLite-like shape,
no server.

Artifacts

file	what it is
inlaysql-0.0.1.beta-x86_64-unknown-linux-gnu.tar.gz	the CLI + MCP server (Linux)
inlaysql-ffi-0.0.1.beta-aarch64-apple-darwin.tar.gz	C-ABI library (macOS, Apple silicon)
inlaysql-ffi-0.0.1.beta-x86_64-unknown-linux-gnu.tar.gz	C-ABI library (Linux)
inlaysql-wasm-0.0.1.beta.tar.gz	WASM module + the JS glue

Each .tar.gz ships beside a .sha256; verify with
sha256sum -c <file>.sha256.

No Windows build: the file layer is Unix-only today
(pread/pwrite, advisory locks) — a Windows port has not
been written. The WASM module runs anywhere a browser or
Node does, Windows included.

Using the C-ABI libraries

Each FFI archive carries the 0.0.1.beta library, the
inlaysql.h header, and poc.php — a working PHP FFI example
that is the fastest way to see the shape of the surface. A
Python ctypes binding is a dozen lines; see
docs/clients.md.

WASM payload

artifact	bytes	KiB	gzipped KiB
inlaysql_wasm_bg.wasm	3140887	3067	1036

Status: beta

The on-disk format is pre-1.0 — recreate, not migrate: a
database written by this version may not open in a later one.
The MySQL server mode is plaintext and localhost-first unless
you configure TLS. Read
What this is not
before relying on this for anything real.

Reproduce every number in these notes with the scripts in
TESTING.md and bench/run.sh.