lang:ende

Development

Custom software, end-to-end. We write the frontend that doesn't fight your users, the backend that scales without surprising you on the invoice, and the hybrid mobile builds that ship to both stores from one codebase. Typed top-to-bottom, tested where it matters, deployed on infrastructure we also operate.

SECTION DEV(1)
CATEGORY software
SINCE 2021
AVAILABILITY ● accepting

What we actually build.

Four practice areas, one team. We don't shuffle your project between specialists who've never spoken to each other.

[01] // frontend

Frontend

$ npm run dev

Component libraries, design systems, marketing sites, dashboards, internal tools. Fast page loads, keyboard-friendly. We write CSS, not just classnames.

VueNuxtReactTypeScriptViteyarn
[02] // backend

Backend

$ ./server --listen :8080

HTTP APIs, gRPC services, background workers, scheduled jobs. Boring tech we trust at 3am. Postgres-first. Idempotent endpoints, structured logs, useful metrics, no magic.

Node.jsExpressNest.jsTypeScriptPostgreSQLRedis
[03] // fullstack

Fullstack

$ make ship

Full product builds where one team owns frontend, API, schema, and deployment. Typed requests end-to-end. CI/CD that actually deploys. Tests that catch regressions, not collect dust.

NuxtTypeScriptDockerGitHub ActionspnpmVite
[04] // hybrid mobile

Hybrid Apps

$ cap run ios && cap run android

One codebase, two stores, native APIs when they matter. Flutter for pixel-perfect custom UI, React Native when the project leans heavily on existing JS ecosystem.

ReactNativeFlutterApp StorePlay Store

How a project runs.

No 80-page proposals. No discovery phases that produce slide decks. We start small, ship often, course-correct loudly.

// 01 — kickoff

Discover

30-min call, then a paid 1-week scoping sprint. Output: a written brief with rough budget & risk list. No-obligation walk-away.

// 02 — design

Sketch

Wireframes, then hi-fi prototypes. We ship interactive Figma or HTML mocks — never PDFs. You click before we code.

// 03 — build

Iterate

2-week sprints. Live staging URL from day one. You see commits, not status reports.

// 04 — ship

Operate

Deploy, monitor, iterate. Optional retainer for fixes & new features. We hand over docs & access whenever you want them.

A typical layer418 stack.

Adjusted per project, but this is what we'd reach for on a new fullstack web app today.

// stack.toml — opinionated defaults, swappable per project

[frontend]
framework  = "vue / nuxt"       # react if the project calls for it
build      = "vite"
packages   = "yarn / pnpm"

[backend]
language   = "typescript"
runtime    = "node"
framework  = "express / nest.js"
db         = "postgres"
cache      = "redis"

[mobile]
hybrid     = "flutter"          # or react-native for js-heavy apps

[ops]
ci         = "github-actions"
iac        = "pulumi"
containers = "docker"
deploy     = "layer418-cloud"   # or your hyperscaler of choice
observability = "prometheus + grafana + loki"
tls        = "let's encrypt"

Things people ask.

Can you work with our designers / agency?

Happily. We're used to translating Figma into production-quality code, and we'll push back on patterns that won't survive contact with real data. If you don't have designers, we have a small bench of independents we trust.

What's the smallest project you'll take?

1–2 week scoped engagements are fine if the brief is tight. Below that, you probably want a freelancer, not a studio — we'll happily refer you.

Do you sign NDAs?

Yes, mutual NDA on request before kickoff. We won't sign one-sided ones that prevent us from saying we worked with you.

Tell us what you want to build.

Brief, repo link, half-formed idea — whatever stage you're at, write us at hello@layer418.de.