Skip to content
/ section § 4.0 Studio · entity · facts · process · FAQ
/ studio

Five people. Not growing past eight.

Devbuildstudio is a four-engineer, one-lead firm operating out of an office on Damstræde in Gistrup, just east of Aalborg. We have been at this since 2018. The person who scopes your project is the person who pushes the code. We do not subcontract, do not maintain a sales team, and have no plans to scale beyond eight people. The numbers below explain why this works.

studio.01 /// damstræde 91 · main workspace The Devbuildstudio workspace: a long oak desk with three engineers at monitors, code on screen, plants on shelves, north-facing windows
/// terminal · always-on A close-up of a monitor showing a terminal session with a deploy in progress and a Postgres query plan beside it
/// notebook · architecture A hand-drawn architecture diagram in a grid notebook, with a coffee cup and a mechanical pencil beside it
/// shelf · reference A bookshelf with technical books on databases, distributed systems and engineering management

§ 4.1 Facts

The studio, in numbers and registrations.

Useful for procurement, due diligence, and Stripe review purposes.

Founded
2018, Gistrup
Team
4 senior engineers, 1 lead
CVR
DK 41 88 21 06
Active retainers
12
Builds shipped
47
Avg engagement
2.4 years (retained)
Time zone
CET / CEST (UTC+1/+2)
On-call hours
08:00–22:00 weekdays

§ 4.2 How we work

A build engagement from brief to retainer.

The same seven phases for every build, scaled in duration to fit the scope.

§ 0.1 Brief Discovery call, scoping doc, fixed price for build phase, signed engagement letter. 1 week
§ 0.2 Architecture Data model, endpoint inventory, hosting plan, security review, written architecture doc. 1 week
§ 0.3 Vertical slice Thin end-to-end path on a real domain. You see the system running by end of week two. 2 weeks
§ 0.4 Build out Weekly demo Fridays. Written changelog every Monday. No surprise scope drift. 4–8 wks
§ 0.5 Hardening Load tests, security scan, backup drill, runbook, on-call handover. 1 week
§ 0.6 Cutover Production deploy with rollback plan. Pair on first 24 hours of operation. 1–2 days
§ 0.7 Retainer Same engineer continues on retainer for changes, scaling, on-call. rolling

§ 4.3 Frequently asked

Eight things people ask before signing.

Q.01

Do you sign NDAs?

Yes, standard mutual NDAs the same week we meet. We will not sign one-sided NDAs that restrict our right to describe the general nature of work.

Q.02

Will I own the code?

Yes. All source code, infrastructure-as-code, and operational scripts are assigned to you at delivery. We retain no rights other than to mention the engagement existed.

Q.03

Where do you host?

By default: Hetzner Falkenstein and Helsinki, with Cloudflare in front. We are happy to deploy into your AWS / GCP / Azure account if you prefer.

Q.04

Are you GDPR-aware?

Yes. Data processing agreements are standard, we host inside the EU by default, and the audit phase of every project includes a written data-flow diagram.

Q.05

Do you take equity?

No. We bill in EUR, monthly, on 14-day terms.

Q.06

What is your team size?

Five people. We are deliberately not growing past eight. The person who scopes the project is the person who pushes the code.

Q.07

Can you start tomorrow?

Audit-class engagements: usually within two weeks. Build-class: only when a slot opens in the queue (visible at the top of the site). Emergency rescue: we keep two days a month free for these and triage by impact.

Q.08

Do you work with non-Danish clients?

Yes. About 60% of revenue is outside Denmark. We have worked across Scandinavia, Germany, the Netherlands and the UK. All documentation and code review is in English.

§ 4.4 Visit

Office and address.

We are not a co-working studio — the office is a converted ground-floor flat on a quiet street near the woods east of Aalborg. Visitors welcome by appointment.

Street
Damstræde 91, 9220 Gistrup
Country
Denmark
Office hours
Mon–Thu 09:00–17:00 CET · Fri 09:00–13:00 CET