Contact

Write to a human

No ticket portal, no chatbot, no contact form that disappears into a queue. Pick the right mailbox below — we read it and reply.

General · Primary
Hello

Engagement enquiries, product questions, press, partnerships, feedback — anything that isn’t a live incident.

Security
Vulnerability reports

Coordinated disclosure. Acknowledged within one business day. See security.txt.

Response — what to expect
Hours
Mon–Fri, 09–17 CET
First reply
Usually within 1 business day
Languages
Dansk · English
Where we are
Entity
Runi Consulting ApS
CVR
39337487
Based in
Copenhagen, Denmark

How to write a good first email

Say what you’re working on in the first paragraph — sector, stack, what you’re trying to move. It helps us reply well instead of asking five clarifying questions.

Incidents on an active engagement

Use the escalation channel named in your engagement contract (typically a shared Teams channel with a named on-call operator). That reaches us faster than email. Otherwise, write to kontakt@runi.services and mark the subject [urgent].

Elsewhere

LinkedIn · GitHub · Writing.

Generelt · primær
Hej

Forespørgsler, spørgsmål, presse, partnerskaber, feedback — alt der ikke er en akut driftshændelse.

Sikkerhed
Sårbarhedsindberetning

Koordineret offentliggørelse. Kvittering inden for én hverdag. Se security.txt.

Svartid — hvad du kan forvente
Åbningstid
Man–fre, 09–17 CET
Første svar
Som regel inden for én hverdag
Sprog
Dansk · English
Hvor vi er
Selskab
Runi Consulting ApS
CVR
39337487
Hjemsted
København, Danmark

Skriv en god første e-mail

Fortæl hvad du arbejder på i første afsnit — branche, stack, hvad du prøver at flytte. Så kan vi svare skarpt i stedet for at stille fem uddybende spørgsmål.

Driftshændelser på aktiv aftale

Brug eskalationskanalen fra din aftale (typisk en delt Teams-kanal med navngivet vagthavende). Det er hurtigere end e-mail. Ellers: skriv til kontakt@runi.services og mærk emnet [akut].

Andre steder

LinkedIn · GitHub · Writing.

Page last updated 2026-04-19. For support terms and vulnerability policy details, see Support.