>_rp

Root-Path: web, mobile & cloud engineering. Small team. Direct access. Faster decisions.

Web, mobile & cloud engineering

The people on your first call are the people who design and build your product.

No account layer in between. You talk to the engineers writing the code.

Fewer hand-offs between a question and the person who can answer it, so the work keeps moving.

01 · Services

Focused digital services for teams ready to move.

Four routes from the root of the problem to a working result your team can own. Take one, or combine them.

01Web development

Web platforms built for the next release

From marketing sites to enterprise platforms, we make the structure, content, and performance work together.

Stack
  • Next.js
  • React
  • TypeScript
  • GSAP
  • Three.js
  • WebGL

How we work

  • Rendering strategy chosen per route: static, server or client
  • Typed component system with design tokens shared with design
  • Motion and 3D with GSAP and Three.js, held to the performance budget
  • Performance budgets for Core Web Vitals, measured before release
  • Accessible to WCAG 2.2 AA
your-product.comcomponent systemReact · TypeScriptperformance baselineSSR · edge · Core Web Vitalsmotion and 3DGSAP · Three.js · WebGLclear handoffdocumented for your teamnext release

02Mobile app development

Mobile apps with a clear path from screen to screen

We shape the core flows and build the app for iOS, Android, React Native, or Flutter.

Stack
  • Swift
  • Kotlin
  • React Native
  • Expo
  • Flutter

How we work

  • Native (Swift, Kotlin) or cross-platform (React Native, Flutter), chosen on product needs
  • Offline behaviour and data sync designed in where needed
  • Release pipelines for the App Store and Google Play
  • Crash reporting and analytics from the first build
screen 01entryscreen 02core flowscreen 03resultiOSAndroidReact NativeFlutter

03Cloud and API engineering

APIs and infrastructure without the black box

Clear APIs, infrastructure, and integrations for products that need to move without unnecessary complexity.

Stack
  • Docker
  • Kubernetes
  • Temporal
  • Redis
  • PostgreSQL
  • GraphQL
  • AWS
  • Terraform

How we work

  • Contract-first APIs: schemas agreed before implementation
  • Containerised services and infrastructure as code (Docker, Terraform)
  • Durable, retryable workflows with Temporal; caching with Redis
  • Logs, metrics, tracing and alerting from day one
  • Least-privilege access and managed secrets
clientweb · mobileGraphQLAPI gatewayservicesDocker · KubernetesworkflowsTemporalcacheRedisdataPostgreSQLAWSinfrastructure as code · Terraform

04Technical consulting

Turn technical complexity into a clear next move

Architecture reviews, legacy modernization, and product strategy for teams deciding what to build next.

Stack
  • C4 model
  • ADRs
  • OpenTelemetry
  • DORA metrics

How we work

  • Architecture and code review with written findings, mapped in C4
  • Keep, refactor or replace, decided per component
  • Decision records (ADRs) your team can revisit
  • Delivery health measured with DORA metrics
  • A roadmap sequenced by risk and dependency
current systemtodayarchitecture reviewassesskeep / refactor / replaceper componentmodernization plandecidetechnical roadmapsequencenext move

> start --build --beyond

Not sure which route fits? Tell us where you are and we will map the path with you.

02 · Engagements

Start the way that fits where you are.

Each one starts with a short request, and asking commits you to nothing. Pick the situation closest to yours.

your request

01fixed scope

You know what needs to be built.

A defined product, release or rebuild with a clear finish line.

commitment
One project, start to finish.
scope
Agreed with an estimate before work begins.

02embedded team

You have a roadmap, not one project.

Designers and engineers working alongside your team, release after release.

commitment
Ongoing, not project by project.
scope
Priorities set with you as the roadmap moves.

03review first

You need a decision before you build.

A focused look at your system, your options and the risks, so the build you commit to is the right one.

commitment
Short and bounded. Act on it with us or without us.
scope
The decision in front of you, answered in writing.

03 · Process

Clear thinking, close collaboration, careful delivery.

The work stays close. You speak directly with the people making the technical decisions, from first conversation through handoff.

01discover

Start with context

We begin with the problem, the users, what exists today, and what needs deciding. Engineers and designers review the current system before anyone proposes a solution.

Practices

  • Stakeholder and user interviews
  • Audit of code, infrastructure and analytics
  • Constraints, risks and success criteria agreed

Leaves in your repo

  • discovery/
  • brief.md
  • system-audit.md
  • success-criteria.md
02architect

Set a clear path

We turn the findings into an architecture and a delivery plan. Options are written down with their trade-offs, and you decide with the people who will build it.

Practices

  • Architecture options with trade-offs
  • Data model and API contracts agreed up front
  • Milestones, estimates and known risks

Leaves in your repo

  • decisions/
  • 0001-architecture.md
  • 0002-data-model.md
  • contracts/
  • schema.graphql
03build

Build in the open

We work in small, reviewed increments. Every change runs through automated checks and gets a preview you can click through while it is still easy to change.

Practices

  • Code review on every change
  • Type checks and automated tests in CI
  • A preview environment for each change

Leaves in your repo

  • src/
  • tests/
  • .github/workflows/
  • ci.yml
04ship

Deliver with care

We release with monitoring in place, write down how the system runs, and hand over a codebase your team can understand and continue to own.

Practices

  • Staged releases with a rollback path
  • Monitoring, alerting and runbooks
  • Handover sessions and documentation

Leaves in your repo

  • runbooks/
  • deploy.md
  • incidents.md
  • docs/
  • handover.md

~/your-product

What stays with you

Everything we produce lives in your repository, as plain files your team can read, review and extend.

  • your-product/
  • discovery/3 files
  • decisions/2 files
  • contracts/1 file
  • src/code
  • tests/code
  • .github/workflows/1 file
  • runbooks/2 files
  • docs/1 file

04 · Contact

Tell us what you are building.

Ask for a quote, a full proposal or a review. Share the problem, the timeline, and anything that is already in place. Your request goes straight to the team that would do the work.

What happens next
We read every request and reply with questions or a scoped plan.
What would you like?

A defined build, with an estimate before work begins.

We use your details only to reply to this request.

Start with a conversation

A clearer next move starts here.

Bring a product question, a technical constraint, or a release that needs a sharper path.

See how we work
>_rp

Designed and developed in-house, every pixel and every line of code.

>_rp$ start --build --beyond

design · frontend · backend · engineering management