Web applications
Portals, dashboards, internal tools, and workflow software for the processes that do not fit off-the-shelf systems.
guest@make-directory:~$ ls ~/capabilities
make-directory:~/capabilities
What we can take on.
If you are here to check whether we can handle what you have, this is the list. Read as much of it as is useful — or skip it entirely and just describe the problem. Matching your situation to the right approach is our end of the work, and most of the interesting problems draw on several of these at once.
guest@make-directory:~$ cat ./depth.md
thirteen areas
What we work in.
Websites and content systems
Sites that stay fast, accessible, and maintainable, and connect cleanly to the workflows behind them.
Mobile
iOS and Android for customer, field, and internal workflows — built, released, and maintained through the store process.
Automation and integrations
Connecting systems that were bought separately, and removing the manual steps between them.
Backend systems and APIs
Services, data models, and interfaces designed to be read and changed by whoever comes next.
Cloud infrastructure and AWS
Environments, networking, and cost — modelled deliberately rather than accumulated over years.
DevOps and delivery
Deployments that are repeatable, reversible, and not dependent on one person being available.
Legacy modernization
Inherited applications, undocumented systems, and mainframe estates — analysed before anything is moved.
AI and machine learning
Applied where it removes real effort — document handling, extraction, classification — and left out where deterministic code is cheaper to trust.
Product and UX design
Interface and product decisions that make complicated work easier to complete correctly.
Databases and data
Schemas, migrations, and reporting that hold up as the data grows and the questions change.
Security-conscious development
Access, secrets, dependencies, and headers treated as part of the build rather than a later audit.
WordPress and CMS
Maintained, extended, or migrated away from — whichever the evidence actually supports.
guest@make-directory:~$ ls /usr/local/stack --versions
the stack, for anyone who asks
Chosen per project, and kept boring wherever boring works.
react19.x
next16.x
vue3.xpythonautomation
terraforminfrastructure
dockerdeployment
awscloud ops
gcloudcloud ops
mongodbdataredisqueues/cache
wordpress7.x
php8.xguest@make-directory:~$ mkdir ./what-needs-to-change
next step
Still not sure where your problem fits?
That is the usual starting point, and choosing between these is a good part of what we are paid for. Describe what is not working and we will come back with what it would take.
Would you rather look at code?
We build and operate our own software in the open — a multicloud infrastructure modeller, a COBOL modernization toolchain, and a research arm. All of it is public, and it will tell you more than this page can.
What we build