Skip to content
0101Stack

Four services.One contract.One team for two years.

Most studios sell one slice and disappear. We bring the whole stack — and we stay. Build, run, integrate, support. Same engineers throughout.

Built to be hired once.

01/ 04Chapter 01

Development.

Black DNA-like helix with burnt-orange neon threads — code structure being assembled.

We build the product itself.

From the first idea on a napkin to the version your team ships every Friday for the next two years. Same engineer writing the code on day one as on day seven hundred.

── What’s covered
  • Product engineering — web and native
  • API and platform design
  • Internal tools your team actually uses
  • Greenfield builds and slow rebuilds
── How it works

Weekly demo. Friday ship. Same engineer end-to-end. We attend your standups when it helps. We argue when we disagree. We document decisions.

── In your stack
  • Code in your repository, your license
  • Architecture decision records, versioned
  • Test specs and CI pipeline you can read
  • Friday changelog, every week
── Tools
  • Next.js
  • React Native
  • TypeScript
  • Postgres
  • Python
02/ 04Chapter 02

Maintenance.

Matte black radiator fins receding in perspective, cut by a continuous burnt-orange line — the signal that never breaks.

We're on call when something breaks.

Production runs 24/7 — so do we. The same engineers who built it are the ones who answer at 2 a.m. Not because the contract says so. Because that's how we treat work that matters.

── What’s covered
  • Monitoring and alerting
  • Security patches and dependency hygiene
  • Performance budgets, kept
  • On-call rotation — humans, not chatbots
── How it works

Monthly written review of what shipped, what broke, what we changed because of it. A delta your board can read. No surprise invoices.

── In your stack
  • Monitoring dashboards, in your accounts
  • Runbooks for every recurring incident
  • Monthly review PDF, board-grade
  • On-call rotation — with your team, not instead of it
── Tools
  • Datadog
  • Sentry
  • GitHub Actions
  • PagerDuty
03/ 04Chapter 03

Integration.

Six matte black pillars connected at their tops by a continuous burnt-orange thread — power lines between transformers.

We make your tools talk to each other.

Quietly. So nobody on your team copies numbers between two screens again. The hard part of integration is never the API — it's the agreement between systems. We do both.

── What’s covered
  • APIs and webhooks
  • Data pipelines and ETL
  • Payments, CRM, billing, support
  • Internal data unification
── How it works

We map the systems before we write a line. We pick the integration that survives the next vendor change. We document the contract — and the workaround.

── In your stack
  • System map, kept up to date
  • Data contracts, version-controlled
  • API documentation, deployed and searchable
  • Migration runbooks, signed off before we move
── Tools
  • Stripe
  • Salesforce
  • Segment
  • Airbyte
  • Postgres
04/ 04Chapter 04

Cloud & DevOps.

Matte black server rack with horizontal burnt-orange light strips between units — infrastructure alive.

We take infrastructure off your team's plate.

Every quarter it gets faster, cheaper, or simpler. Usually all three. Most partnerships save more on cloud than they cost to run, by year two.

── What’s covered
  • AWS, GCP, Vercel, on-prem
  • Kubernetes when needed, never by default
  • Infrastructure-as-code
  • Cost engineering — measured, not guessed
── How it works

We start by reading your cloud bill. Then we cut the obvious 30%. Then we keep going. Every quarter, a written review of what we changed and what it saved.

── In your stack
  • Infrastructure-as-code, in your repo
  • Quarterly cost report, line by line
  • Disaster recovery runbook, tested twice a year
  • Security review, with patch log
── Tools
  • AWS
  • GCP
  • Vercel
  • Kubernetes
  • Terraform
── Inside a partnership

What twenty-four monthslooks like, week by week.

Most studios show you the deliverables. We show you the depth — what changes between month one and month twenty-four, in your codebase and in our heads.

  1. Day 1

    First email

    We read every one. We reply by name within 48 hours.

  2. Week 2

    Written report

    What's working, what's quietly broken, the three changes that compound. Yours to keep — partnership or not.

  3. Month 1

    First Friday ship

    Code in your repo. The same engineer writing it now will be writing it in twenty-three months.

  4. Month 3

    First quarterly delta

    What we built. What it moved. What we changed our mind about. A document your board can read.

  5. Month 6

    We finish your sentences

    We know your business, your customers, your edge cases. Standups speed up. So does shipping.

  6. Month 12

    Half the new commits are ours

    We're part of the team. Onboarding new hires gets easier. Roadmap conversations get sharper.

  7. Month 24

    First renewal conversation

    Most partnerships keep going. We talk openly about scope, fit, and what could be better. No autorenewal.

── Cadence

We're not available.We're integrated.

Here's what ends up in your calendar — and ours. Same engineer, every meeting, for as long as we work together.

  • Daily

    Your standup, when it helps the work

    Same Slack, same channels — we read every thread.

  • Weekly

    Friday demo

    Written changelog. What shipped. What we cut. What's next.

  • Monthly

    Review of what shipped, broke, changed

    A delta you'd send to your board. Honest about what didn't move.

  • Quarterly

    Board-grade review and cost report

    Infrastructure spend, line by line. Next three months, scoped.

  • Yearly

    Partnership review

    Scope, fit, ambition. Open. No autorenewal.

── In writing, every year

Depth, counted.

What you'll see on paper across one year of partnership. The reason most clients keep us is what compounds in these documents.

  • 0

    Friday demos

    Every week. Written changelog attached.

  • 0

    Monthly reviews

    Shipped, broke, changed. Honest.

  • 0

    Quarterly deltas

    Board-grade. Numbers your CFO can read.

  • 0

    Partnership letter

    Yearly. Scope, fit, ambition.

  • ∞

    Code, ADRs, runbooks

    Continuous. In your accounts, your license.

── How we work across borders

Based in Tanger.Working across four time zones.

Tanger sits 14 km from Europe — same time zone as London, an hour from Madrid. Our mornings overlap with Paris and London. Our afternoons catch New York. Our evenings still answer Dubai.

Same engineer. Same cadence. No handoffs. No "I'll get back to you Monday."

  • Paris—:—
  • London—:—
  • Tanger—:—
  • Dubai—:—
  • New York—:—
── What we don't do

We're not for every team.

  • We don't sell hours.
  • We don't dispatch resources.
  • We don't take projects we can't see ourselves caring about in eighteen months.
  • We don't replace your team. We become part of it.

If you need a body for two weeks, we know good people. Email us — we'll introduce you.

── Ready to start?

Tell us what you'retrying to ship.

Write to usWe read every email. We reply by name within 48 hours.