Product studio and engineering consultancy · Vienna

For products where the launch is just the beginning.

offbrand plans, builds and operates digital products across the whole stack: architecture, frontend, backend, infrastructure. Not a supplier for one slice of it, but one point of contact for the finished product. What we can do is not only described on this page. It is publicly accessible and can be checked in detail.

A few lines about the problem are enough to start
Your enquiry is answered the same working day
No pitch deck, no sales call
You speak directly to the person who will build it

How Kor gives your project a head start

What we do
From a single review through individual architecture decisions to a finished product we then keep running.
Experience
Engineering since 2008, at principal and architect level. Trading platforms, comparison portals, industrial applications.
Technology
Vue and Nuxt, TypeScript, Node and Nitro, Python, PostgreSQL and SQLite, Storyblok, Docker, Traefik, GitLab CI.
Partnership
Storyblok MVP and Certified Partner.
Capabilities

Four layers, one point of contact

Most suppliers cover one of these layers and coordinate the rest. We build all four, which is why the expensive mistakes at the seams never arise.

Architecture and product planning

System design, data model, interfaces, and the technical product decisions. In other words, the part that determines years later whether a product gets extended or rebuilt.

Solution Architecture · Data and domain modelling · API-Design · Technical product leadership · Reviews · Mentoring

Frontend

Vue and Nuxt across every rendering mode, from statically generated through server-rendered to hybrid. Plus design systems, multi-tenancy and technical SEO. Performance and accessibility belong in the requirements, not in the clean-up.

Vue · Nuxt · TypeScript · SSR, SSG, ISR & hybrid modes · Design Systems · Multi-Tenant-Theming · Technical SEO · Core Web Vitals · WCAG · Rive

Backend and data

Interfaces, computation, data models, integrations and content layers. Node and Nitro as the default, Python where it is the better choice, PostgreSQL as the backbone, and Storyblok as the preferred content source.

Node · Nitro · Python · PostgreSQL · SQLite · REST & GraphQL · Storyblok · Headless CMS · Authentication

DevOps and operations

Pipelines, containers, deployments, monitoring and backups. Then maintenance, updates and further development over years. We do not hand over to an operator. In our own products we are one.

GitLab CI/CD · Docker · Traefik · Hetzner · EU-infrastructure · Monitoring · Backups · Maintenance and evolution · GDPR

If you want a head start, there is one: in Kor, our own platform layer, those four levels already work together, which saves the first months of foundation work.

Services

Four ways to work with us

From a single review to a finished product. The shape follows the problem, not a package.

Solution architecture and technical leadership

Architecture decisions, reviews, and the questions that have been open for three sprints. Fractional, on retainer, with genuine ownership of the decisions and none of the fixed cost of a hire.

For teams that need seniority, not another full-time seat

Product engineering across the whole stack

Concept, data model, interfaces, UI, deployment, operations, maintenance and further development. One line of responsibility the whole way, instead of the handovers between agency, freelancer and host where half the problems come from.

For products that will be run for years, not merely launched

Technical audit, fixed price

The report within 72 hours of access, a prioritised list of measures, and a 90-minute session. The lowest-risk way to get to know us, and usually the first step.

For anyone who wants to know where they stand before investing

Design systems, platforms, migrations

Multi-tenant design systems and theming, major version upgrades and migrations in Vue and Nuxt, CMS replatforming, and rescue work on projects that have stalled.

For teams running several products on one shared foundation

Technical audit: architecture, performance, SEO

Within 72 hours of access you know where your application stands, what it costs you if nothing changes, and in what order fixing it pays off.

  • Architecture: components, state, interfaces, typing
  • Backend and data layer, as far as accessible
  • Core Web Vitals and bundle analysis
  • Rendering strategy, SSR and hydration
  • Build and deploy pipeline
  • Technical SEO: metadata, structured data, indexing
  • Security and GDPR baseline
  • Prioritised measures, ranked by effort and impact
2,400 EURfixed price · report within 72 hours of access · session at your convenience

For a typical application size, larger systems on request. Implementing the main measures afterwards is at day rate, with no obligation.

Request the audit
Work

What we build and operate

Our own products, live and open to inspection. The best work sample is the one you can open.

obolus.at
offbrand.works
In preparation
Kor
Every product we run stands on the same core. A new one does not start at zero, it starts with the platform already built.

obolus.at

Finance · Built and run by offbrand · since 2026

Austria's ad-free salary and tax platform. Most calculators approximate. This one does not.

  • Rules-based tax engine, accurate to the cent and checked against the official references
  • A versioned rate registry per tax year: the January change is a new version, not a rebuild
  • Computation runs in the browser. No salary figure ever leaves the device.
  • From data model through computation and interface to pipeline, hosting and monitoring
  • Built on Kor, which is why a tax engine, a content layer and a deployment path did not each have to be invented for it

Vue · Nuxt · TypeScript · Nitro · SQLite · Storyblok · Kor · Docker · Traefik · GitLab CI

Kor

/kɔːr/
Platform · The shared core of our products · since 2024

From the Turkish for embers: the concentrated heat a fire keeps, and the reason a small team keeps the pace of a large one.

  • A new project starts with routing, theming, authentication, pipelines and a deployment path already working. That is the part that usually eats the first months.
  • A design system of more than fifty components, token-based theming for light, dark and per-tenant variants
  • Three-layer configuration and multilingual routing in the core: a tenant overrides what differs and inherits the rest
  • A content layer with Storyblok as the first source, swappable for another system without touching the application
  • Strict conventions and documented structure. That is precisely what makes AI-assisted development reliable rather than merely plausible.
  • obolus and this page both run on it.

Vue · Nuxt Layer · TypeScript · Design Tokens · Nitro · Storyblok · Docker · Traefik · GitLab CI

offbrand.works

Studio site · You are reading it · since 2026

The studio's own site. It runs on the same platform as the products, so the page you are reading is itself one of the examples it points at.

  • Two locales with their own routes and their own metadata, not a language toggle on one page
  • Content comes through the same layer Kor ships, with Storyblok as the intended source; until the CMS is switched on it reads from the repository, which is a one-line change
  • The same design system, theming and build gates as every other product we run
  • Deployed like the rest: container image, pipeline, Traefik in front, hosted in the EU

Vue · Nuxt · TypeScript · Nitro · Storyblok · Kor · Docker · Traefik · GitLab CI

In preparation

Product · not announced yet

A third product is being built on the same platform. It is not public, and it will not be until it is worth your time.

  • Same core as obolus and this site, so none of it starts from zero
  • Announced when it runs, not when it is planned
  • The interesting part is not the product. It is that a third one costs a fraction of the first.

Vue · Nuxt · Kor

Approach

Seven rules you can hold us to

  • Maintainability beats speed in the first sprint. We build systems that do not age: clear boundaries, few dependencies, no deferred compromises, and a foundation kept current instead of left to accumulate technical debt. Performance is a standing requirement, not a clean-up at the end.
  • EU infrastructure and GDPR as the starting point. Not an add-on module, not a separate line in the quote.
  • Cited sources instead of assumptions. In our products and in our reports, a figure states where it came from.
  • Your project IP is yours. Our prior work stays ours without turning into a licence obligation. Handover documented, and no dependency you did not order.
  • No display advertising on our products, no dark patterns in yours. Both cost us money, and both are deliberate.
  • No invented references, no figures we cannot show you. Which is roughly where the name came from.
  • AI speeds up the work; it does not make the decisions. Architecture, the data model, and the judgement of whether something is correct come from a person, are reviewed by a person and are answered for by a person. Nothing goes from a model into your product unreviewed.
Experience

Where this way of working comes from

We have worked since 2008 mostly on systems where a mistake shows immediately: trading platforms, comparison portals, applications in industrial settings. We tend to get called once something has been built and no longer holds.

Our own products, and the platform underneath them

offbrand · continuous · architecture, engineering and operations

Everything below this was learned on someone else’s system. It is kept sharp on our own: Kor, the platform every product we run sits on, and the products themselves. Building and operating both means the decisions we make for you are ones we have to live with too.

The hard part

A platform several products depend on cannot be changed casually, and cannot be left to rot either. Every improvement has to reach every product without a rewrite. That is the same problem your codebase has, at a smaller scale and with nobody else to blame.

Frontend foundation for an enterprise inspection platform

Industrial group · ongoing engagement · architecture and technical leadership

An application grown over years was rebuilt onto a core layer with a component catalogue and theming. That layer is now the basis for every further frontend in the group, together with the standards, the reviews, and the mentoring of the team working inside it.

The hard part

The existing product was in daily use and could not stand still. The replacement had to ship incrementally, and the result had to be adopted by teams who had never asked for a shared foundation. The technical half was the smaller half.

Storyblok relaunch of Comparis.ch

Swiss comparison platform · solution architect · 2021 to 2023

Architecture and migration tooling for the move from Sitecore to Storyblok: ten languages, some two hundred pages, moved through the Management API rather than by hand, plus the extensions that let the editorial team actually work in it afterwards.

The hard part

Two hundred pages in ten languages cannot be re-entered, and the relaunch date was fixed. The migration itself had to become software: repeatable, verifiable, and runnable as often as it took to be right.

QR generator platform at Egoditor / Bitly Europe

Solutions architect · headless frontends · 2022 to 2023

Architecture, prototypes and implementation with Storyblok, Vue, Nuxt and TypeScript, plus several extensions for content that editorial and marketing maintain themselves.

The hard part

Marketing wanted to change pages without waiting for a deployment, and the pages still had to stay fast and cleanly indexable. Where the line between editors and engineers runs is decided in the extensions, not in the concept.

Frontend for a sports betting platform

European operator · architecture and implementation · real time

Live odds and bet placement in the browser, where the numbers move continuously and the screen has to stay honest about what someone is actually committing to.

The hard part

Odds change while a person is looking at them. The interface has to show the current price, make the change visible, and never let a stale number become a placed bet.

Trading interface for a European trading platform

Architecture and implementation · real time · 2018 to 2019

Architecture and implementation of the real-time trading interface, with Vue, Nuxt, Canvas, Node and WebSockets.

The hard part

An order book changing several times a second, in a browser where a dropped or reordered frame is not a rendering glitch but a wrong price in front of a user. Rendering budget and correctness at once, under a live connection.

Further projects

Systemair · Tender Service

Composable web solutions with Vue, Nuxt, Node and Storyblok, including custom Storyblok tooling and plugin integrations.

These engagements typically run over years. References and contactable referees on request.

Questions

Frequently asked

Who is behind offbrand?

A studio led by Lukas Brand, who does the work himself rather than passing it on. For larger undertakings, specialists we have worked with before join in. So you get principal-level work on the project, not only in the proposal.

Who is this for, and who is it not for?

For companies that need one party accountable for a whole product, from the data model to the server it runs on, and that intend to operate it for years rather than launch it once. It is a poor fit for a one-off marketing site, for staff augmentation inside someone else's architecture, and for anyone whose main criterion is the lowest day rate. Saying so early saves both sides a call.

Does everything depend on one person?

The code sits in your repositories, the infrastructure in your accounts, the architecture is documented, and the conventions are strict enough for someone else to get up to speed quickly. That is a design decision, not a reassurance.

What does a project cost?

The usual entry point is the fixed-price audit. After that we work at a day rate or on retainer, depending on the shape of the work. You get concrete figures after the first conversation, once it is clear what we are talking about.

Do we own the code?

Yes. The project IP is yours and is handed over documented, including the parts we wrote before you arrived that end up in it. What stays ours is our own prior work, and using it creates no licence obligation for you.

How quickly can you start?

An audit usually within two weeks. Larger engagements by arrangement, mostly at the start of a month.

How much of our time does this take?

For an audit: the time it takes to grant access, plus the 90 minutes we spend going through the findings. For a build the demand is decisions rather than hours, so someone who can answer questions about the domain and sign off on direction, usually a few hours a week. We do not run a process that needs your people to staff it.

Do you work remotely or on site?

Remotely across Europe, hybrid in Vienna. Workshops and kick-offs on site gladly; the build itself tends to go better with distance and quiet.

Contact

Tell us what you are dealing with

Tell us what you are building and what is in the way. The more concrete it is, the more useful the first reply.

  1. You describe the problem, the timeframe and the budget range.
  2. We say plainly whether we are the right people for it. If not, we usually know who is.
  3. You get a first read on effort and priority, even if we do not end up working together.