From sketch to production and operations. Paperphyte helps companies build, ship and operate digital products with a focus on platform engineering, DevOps, developer experience and modern product development.
The services overlap. Start with what hurts, and we will point to where it is usually solved.
Looking for drone photography? Aerial photos and 4K video for estate agents, property owners and construction projects is a service of its own, with its own pages.
Short sprints or multi-year partnerships — we shape the format around the problem, not the other way round.
From first sketch to shipped product. We take ownership of design, code and delivery when you want a dedicated team that owns the outcome.
Cloud infrastructure, CI/CD and developer experience that actually lets teams ship. No PowerPoint architectures.
We bring dev and ops together for real — not a team called DevOps, but a way of working where the same people build and run. Measurably better incident response, shorter lead time.
We make delivery a discipline: pipelines, release trains, feature flags and progressive delivery. From monthly releases to multiple deploys a day.
The internal product no one else is building for you: developer portals, golden paths, templates and self-service that make the next team productive in hours — not weeks.
Aerial photo and 4K video for estate agents, construction projects and property owners – the plot, the location and the roof from where the details matter.
Problem, approach and outcome. Real code in production at real clients — not a list of references.
01DeLavalProblemSoftware for robotic dairy barns was built and released at hardware pace — a release was a manual, risky event.ApproachTerraform-defined AWS platform, GitLab CI/CD for embedded artifacts, telemetry in InfluxDB/Grafana.Read the case →
02QRGenoProblemA product without a platform: idea, payment flow and compliance had to reach market before the money ran out.ApproachFastAPI + React on Fargate, Terraform from day one, Playwright in the pipeline, Mollie and Auth0 instead of building our own.Read the case →Four tools that answer before you talk to us. All compute locally in your browser: no forms, no email, nothing stored.
Try it now: what does waiting for the build cost you?
Assuming 60% of the waiting is really lost and 850 kr per developer hour. Both can be changed in the full calculator.
Keep calculating →Is your codebase ready to pair-program with AI? Twelve questions about the guardrails that decide whether AI-assisted development brings speed — or just more mistakes, faster.
Start the check →What does waiting on the build cost you? Turns build time into lost developer hours and kronor per year — with the whole calculation visible on the page.
Open the calculator →The page a coding agent reads first. Nine questions about your repository become a finished AGENTS.md or CLAUDE.md — commands, checks, deploys, rules and what the agent must ask about before acting.
Write your AGENTS.md →Paste a public GitHub repo and get it X-rayed: README, AGENTS.md, lockfile, CI, CODEOWNERS and thirteen more things that decide whether the repo can be understood without asking anyone.
X-ray a repo →We pick engagements where technology is the core of the business — not a cost center on the side.
Route optimization, parcel tracking, driver apps
OSS/BSS, 5G services, edge compute
Regulated markets, real-time bets, anti-fraud
Procurement, DIGG, e-services
C/Rust, RTOS, hard real-time
Time-to-market, multi-tenant
CRM, business systems, integrations
Field notes on platforms, delivery engineering and AI-assisted development — written by the people doing the work. In Swedish.
Delivery EngineeringBygget blev rött på ett test ingen rört på ett halvår, så någon klickade ”kör om” och det blev grönt. Nästa vecka händer det igen. Ett test som ger olika svar på samma kod är inte otur utan en skuld, och varje omkörning är en räntebetalning. Så här sätter ni flakiga tester i karantän, lagar orsaken med isolering och får tillbaka ett rött som betyder något.
Delivery EngineeringNio förändringar gick ut på releasekvällen. En gick sönder, så alla nio rullades tillbaka — och de åtta som fungerade fick vänta två veckor på nästa tåg. Att driftsätta är en teknisk händelse, att släppa är ett beslut. När de sitter på samma knapp kostar varje release lika mycket som den största förändringen i den. Så här skiljer ni dem åt, och var det brukar gå sönder.
DrönarefotoMäklaren ringer en torsdag och vill ha en bild över läget till söndagens visning. Flygningen går att ordna. Tillståndet att publicera just den bilden gör det inte. Det här avgör en drönarfotografering — vad bilden ska visa, ljuset, luftrummet och spridningstillståndet — och vad ni kan ha klart innan ni ringer.
Observability is the ability to understand what's happening inside a system from what can be observed — metrics, logs, traces and events — so you can answer questions nobody anticipated when the system was built.
Chat with us on WhatsApp. We reply within 48 hours.