QuestDB

ALT QuestDB banner for FOSDEM 2027, Brussels, January 30, titled 'QuestDB + OpenC3 COSMOS at FOSDEM 2027.' A pill reads: joint stand, QuestDB and OpenC3 COSMOS. Body text reads: one joint stand, a working desktop CubeSat, and core engineers from both projects. Come and find us. On the right, a line drawing of a small cube satellite with two solar panels and an antenna sends signal arcs toward a pink telemetry trace labeled 'telemetry, live'. Below, three boxes linked by arrows read CubeSat, COSMOS 7 and QuestDB. Under 'every measurement it ever reported,' two green chips read SAMPLE BY and ASOF JOIN. A footnote reads: January 30, Brussels.

ALT QuestDB banner titled 'ADBC drivers for QuestDB.', tagged Integrations · adbcBridge, with a pill reading adbcBridge, third-party. Body text reads: Arrow from C#, Java, Go, TypeScript, or any tool that takes an ADBC driver. On the right, under 'our own arrow clients,' grey chips read C / C++, Rust, Python and Ruby. Under 'adbcBridge reaches,' pink chips read C#, Java, Go, TypeScript and any ADBC tool. Under 'two flavours,' two cards: QuestDB 10+, native QWP driver, Arrow batches for reads and bulk ingest; and QuestDB 9 or older, ODBC bridge over PGWire, also the pick when one driver serves several databases.

ALT QuestDB Enterprise 4.1 banner titled 'Object visibility, per principal.', tagged Access control, with a pill reading tables(), SHOW TABLES, pg_catalog. Body text reads: a principal only sees the objects it holds a permission on. Everything else is simply not there, information_schema included.

ALT QuestDB blog banner titled 'A trading day, replayed in 32.5s.' Body text reads: 353M rows of US equities top of book, streamed into Python as Arrow. The network ran out before the database did. On the right, a bar chart of market activity across the day, with a white playhead partway through: bars to its left are pink, already replayed, and bars to its right are grey, still to come.

ALT QuestDB banner titled 'QuestDB, in Ruby.', tagged New client · Ruby, with a pill reading gem install questdb. Body text reads: a new client, published as the questdb gem. QWP over WebSocket, both ways, written the way Ruby is written. On the right, under 'written the way Ruby is written,' a diagram shows Ruby connecting to QuestDB with an arrow labelled QWP over WebSocket, captioned 'Keyword args. Time as a timestamp. I/O without the GVL.' Under 'both ways,' three rows read: Write, rows, column arrays, or Arrow from Polars. Read, Enumerable, Polars, nanoarrow, Red Arrow. Blocks, leases released on the way out, even on raise. A footnote chip reads Threads: ingestion threads overlap

ALT QuestDB banner titled 'QuestDB, from the browser.', tagged New client · Browser, with a pill reading @questdb/browser-client. Body text reads: a new client that speaks QWP over WebSocket straight from the page. No proxy service to write, deploy and keep in step with the schema. On the right, under 'straight from the page,' a diagram shows browser connecting to QuestDB with an arrow labelled QWP over WebSocket, captioned 'No Node modules. No polyfills. No proxy.' Under 'both ways,' three rows read: Write, row API, typed writers, batching, transactions. Read, streaming SELECT, bind params, cancellation. Survive, pooling, failover, replays unacked rows. A footnote chip reads Enterprise: follows the primary when a replica is promoted.

ALT QuestDB blog banner titled 'One table, three readers.' Body text reads: QuestDB SQL, Polars and DuckDB reading the same Parquet partitions, and agreeing. On the right, a glowing blue Parquet logo connects through a single point to three branching lines, each ending at a tile: the QuestDB logo, the Polars bear, and the DuckDB logo.

ALT QuestDB banner titled 'Governance, on one page.', tagged Docs · Governance. Body text reads: every governance feature, grouped by the question it answers. Map it straight onto your own policy or an auditor's checklist. On the right, under the heading 'grouped by the question it answers,' six numbered rows read: 01 Who may reach the data, and what can they do. 02 Who can do what right now. 03 Who read the data. 04 Where the data came from. 05 How long it is kept, and can it still change. 06 How to get it back. Below, two chips read Enterprise and Open source, followed by 'every item marked'.

ALT QuestDB banner titled 'Kafka connector, version 0.25.', tagged v0.25 · Kafka connector, with a pill reading 0.25, http::, ws::, tcp:: keep working. Body text reads: nothing changes in your configuration. The improvements come from client 1.3.10 and apply when you connect over QWP. On the right, under the heading 'keep idle connections alive,' a code card shows client.conf.string with keepalive_interval_millis set inside it. Below, under 'also over QWP,' three rows read: no symbol ceiling, past one or two million distinct values; quicker commits, flush stops waiting out the ack timeout; and clearer errors, missing or blank config caught up front. A footnote reads: keepalive is off by default. Pings stop idle timeouts dropping quiet links.

ALT QuestDB Enterprise banner titled 'Trading hours, in the filter.', tagged Enterprise · Exchange calendars, with a pill reading #XNYS, a MIC code, not a holiday list. Body text reads: no holiday list, no session window, no timezone math. A MIC code in the time filter, and daylight saving comes for free. On the right, under the heading 'january on the nyse, sessions only,' a code card shows: WHERE ts IN '[2026-01]#XNYS'. Below, under 'one filter, any market,' three rows read: XNYS, no weekends, no holidays, real early closes; XHKG, both sessions, lunch break taken out; and your own, custom sessions, overrides, internal codes. A footnote reads: NYSE, 14:30 to 21:00 UTC in winter, 13:30 to 20:00 in summer. Same filter.

ALT QuestDB banner titled 'Compression, without ZFS.', tagged Storage · Parquet, with a pill reading Parquet partitions, open source and Enterprise. Body text reads: Parquet partitions are compressed in the format itself and stay fully queryable. On Enterprise, storage policies convert them by age. On the right, under the heading 'where compression happens,' two stacks compare before and now. Before shows three layers: QuestDB table in native format, ZFS compression struck through as a filesystem layer, and disk. Now shows a pink QuestDB table box labeled Parquet partitions, compressed, sitting directly on disk. Below, a panel headed 'codec, set in server.conf' lists LZ4_RAW as the default, plus zstd, gzip, snappy and brotli. A footnote reads: ALTER TABLE converts existing partitions you point it at.

ALT QuestDB Enterprise banner titled 'Service accounts, not your login.', tagged Enterprise · Service accounts, with a pill reading no groups, nothing inherited. Body text reads: a principal for an application, not a person. Every permission it holds was granted to it explicitly, so the grants are the blast radius. On the right, under the heading 'one table, one protocol, nothing else,' a code card shows: CREATE SERVICE ACCOUNT ingest_app WITH PASSWORD 'pwd'; GRANT HTTP TO ingest_app; GRANT INSERT ON sensor_data TO ingest_app; ALTER SERVICE ACCOUNT ingest_app CREATE TOKEN TYPE JWK; Below, under 'memory limits too,' a card reads: SET MEMORY LIMIT 1G, per account, not inherited. A footnote reads: no personal login in the pipeline.