Applied AI lab · Bratislava

We do the research.
Then we ship it.

Sinorom is an applied AI lab. We work on language models, agent architectures and the data infrastructure underneath them — and everything we conclude gets tested the only way that counts, by running in production under real load.

  • Published & patentedPreprints, articles and granted US patents
  • We run what we buildFive products live on our own infrastructure
  • Evaluated, not demoedMeasured on your cases before it ships

Research

What we're working on.

We keep a handful of open questions running at any time. They get picked because a client problem hit a wall, or because we needed the answer for one of our own products — never for their own sake. Everything here is applied: if it doesn't eventually change what we ship, we drop it.

AGENTS

Agent architectures

How to give a model tools, memory and a task boundary it won't wander out of — and how to tell when it has. Duckerhub is where we test this against real users.

RETRIEVAL

Grounding & retrieval

Getting the right context in front of the model: chunking, ranking, and the underrated problem of recognising when the answer simply isn't in the corpus.

EVALUATION

Evaluation methodology

Most AI projects stall because nobody agreed what “better” means. We build the measurement before the feature, and keep it running afterwards as a regression suite.

STORAGE

Database internals

Separating database compute from durable logs and immutable object storage. DBlicious is the long-running experiment, and the hardest thing on our bench.

Services

What the lab does for clients.

The research is the interesting part; this is how it reaches you. Most engagements start in one of these and grow into another — we're happy to own the whole lifecycle, or just the part your team can't cover right now.

AI systems & agents

Models and agents taken from prototype to something you can depend on.

This is the centre of what we do. We build AI systems that survive contact with production: grounded in your own data, measured against real cases before and after the change, and with defined behaviour for the times the model is wrong. Where the received wisdom doesn't fit your problem, we run the experiment ourselves rather than guessing.

  • Retrieval-augmented generation and grounding
  • Agent design, tool use and multi-step workflows
  • Evaluation harnesses and regression suites
  • Document processing, extraction and classification
  • Prompt and context engineering, versioned like code
  • Model selection, routing and cost/latency tuning
  • Fine-tuning and small-model deployment
  • Data pipelines and warehousing to feed them
  • Self-hosted and EU-resident inference

Typical engagement — a discovery spike that establishes a baseline and an evaluation set, then a scoped build once the numbers justify it.

Approach

How an engagement actually runs.

No discovery theatre and no open-ended hourly drift. Four stages, and you can stop after any of them.

01

Understand

We start with the problem, the constraints and the deadline that genuinely matters. If we think you're solving the wrong thing, you'll hear it before you spend money.

02

Scope

You get a written proposal: what's included, what deliberately isn't, what it costs and when it lands. Changes are re-quoted rather than absorbed silently.

03

Build

Short cycles, working software you can click on, and a direct line to the person writing the code. Everything sits in your repository from day one.

04

Operate

We deploy it, watch it, and hand over documentation someone else could act on. If you'd rather we kept running it, that's a separate, honest line item.

Stack

Tools we reach for.

Boring, well-understood technology by default. We'll happily work in yours instead — the list below is preference, not a requirement.

Models & inference

ClaudeOpenAIOpen-weight modelsvLLMOllama

Retrieval & evaluation

pgvectorHybrid searchRerankersEval harnessesTracing

Languages

PythonTypeScriptGoSQLBash

Backend & data

Node.jsFastAPIPostgreSQLRedisAirflowREST

Frontend

ReactNext.jsVueTailwind CSSVite

Infrastructure

LinuxDockerNginxTerraformGitLab CIS3Hetzner

About

A lab small enough to ship.

Sinorom is deliberately small, and there is no wall inside it between the people who try things and the people who make them run. The same engineers write the evaluation harness, argue about the results, and carry the thing to production — which is the only arrangement we've found that stops research becoming a slide deck.

We fund the open questions by building products out of the answers. Duckerhub, Jipidy, Golem, eBVB, Skimetric and DBlicious are all places where an idea met real users and real load before we ever recommended it to a client.

We work with founders, product teams and IT departments around the world — usually remotely, and used to running a project across time zones. We're comfortable being your only technical partner, and equally comfortable slotting in alongside a team that already knows what it's doing.

“Measure it before you believe it. Then measure it again in production, where it counts.” — the only house rule

Publications & patents

The work, in the open.