Roadmap

flinq ships a deliberately small surface today. The items below are committed directions, stated plainly so you can plan against them. Dates are not promised during the beta.

Async batch endpoint

An asynchronous POST /v1/batches endpoint, OpenAI-shaped: submit a file of requests, poll for completion, download the results. It runs offline rather than in your request path and is billed at a 50% discount on the standard per-token EUR rate, making it the cost-efficient path for large, non-interactive ingests. See Bulk & batch for the synchronous recipe you can use today.

The GPU-served production model

The current service runs the pilot models we evaluate on BauSatz. The production deployment moves serving onto GPU for higher throughput and lower latency at scale, without changing the API or the vector space your index is built on.

BauSatz across European languages

BauSatz starts with German, built on real GAEB tender data. The direction is an open, neutral benchmark for construction language across European languages, so models can be compared on the same terms beyond a single market. flinq’s first model is German; broader language coverage follows the benchmark.

Layout-aware PDF ingestion and OCR

The Documents category reads GAEB today. PDF joins it as one coherent release: layout-aware extraction that understands headings and tables (so PDF chunks can be hierarchy-based, under the same versioned strategy contract as GAEB), with opt-in OCR for scanned documents. Deliberately not shipped piecemeal — naive text-layer chunking without layout understanding would be no better than what any client library does locally.

Multimodal

The built environment is not only text. Drawings, BIM geometry and IFC property sets carry meaning that a text-only model cannot read. Multimodal inputs extend flinq from a domain text-embedder toward the full foundation model for the built environment.