Bounded engagements that end in something that runs.

Pandan Labs is a small technical practice. We take a fixed scope, a fixed fee and a date, then hand back working software, a demo that holds up in front of an audience, or an assessment your board can act on.

Demos & walkthroughs Agents & MCP Workshops AI readiness
Lead offering

Demo studio

Demos usually fail in one of two ways. Either the environment falls over, or it holds together and nobody remembers afterwards what they were shown. We script the story, build the environment, rehearse the failure and cut a walkthrough that holds up on a conference floor with bad wifi. Your engineers keep the repo afterwards.

Short demo1–2 min · from USD 600
Product walkthrough3–4 min · from USD 1,400
Stage & boothEvent-scoped
Enablement2 weeks
Method, rate card and full catalogue
Selected work

Recent demos.

Short recordings from product walkthroughs and technical sessions. Hover a tile to preview, click to play.

See the full catalogue
The rest of the practice

Pandan Labs is not only demo work.

The same shape applies across everything below. Scope agreed up front, a date on the calendar, and artefacts your team owns at the end.

Build

Agents & MCP engineering

Agent runtimes, MCP servers and gateways for regulated environments. Auth, audit and residency designed in from the first commit rather than bolted on for the security review.

Go · Python · GCP · self-hosted
Assess

AI readiness

A structured read on where an organisation actually stands, mapped to SDAIA, NCA and PDPL language so the output survives contact with a compliance team.

Gap analysis · scored report · remediation roadmap
Teach

Workshops & enablement

Hands-on sessions for mixed rooms of developers and architects. Everyone leaves with a repo that runs on their own laptop and notes explaining why it was built that way.

Half-day · full-day · series
Prove

Bounded builds

Short, scoped builds and hackathon programmes that answer one question with running code, inside a window agreed before anyone starts.

2–6 weeks
How we work

Three rules, and we hold ourselves to them.

Fixed scope, fixed fee

Dates go on the calendar before work starts. If the scope moves, we requote rather than quietly stretch the timeline.

You keep everything

Repos, infrastructure definitions, runbooks and the reasoning behind the choices are handed over at the end, so another team can pick the work up without calling us.

We say no in week one

If the thing cannot be built inside the window, you hear it early enough to spend the budget somewhere better.

The practice

Two decades of building things and then explaining them.

The work behind Pandan Labs spans MENAT and APAC: developer relations at a hyperscaler, cloud architecture for customers in regulated industries, and a lot of time on stage and in workshops with engineering teams who had to adopt something new.

Engagements here are deliberately small — sized to finish, specific enough to price, and technical enough that the people writing the proposal are the people writing the code.

  • BackgroundDeveloper relations and solutions architecture at a hyperscaler
  • CommunitiesOrganisers of multiple technical communities, covering AI engineering and cloud native
  • Stage timeAWS re:Invent, AWS Summits, LEAP, GITEX, GDG Cloud, AWS Community Days and regional developer user groups
Open source

Small, single-binary tools we build and keep maintained. Source and walkthroughs available on request, which is the fastest way to judge whether we write code you would want in your repo.

Start a project

Tell us what has to be working, and by when.

One paragraph is enough to start: the audience, the date, and the thing that has to run in front of them. You will get a scope and a number back within two working days.

hello@pandanlabs.com