Webanion

The platform around the model that takes AI features from demo to production: agents that plan, act and verify, and MCP servers over a business's own systems. Around them sit routing across model providers, durable workflows for long jobs, memory scoped per client, and guardrails that keep a person on every write. The live MCP server behind this site is the working example, and the same engineering ran on an agent-first AI workflow platform serving more than a thousand tenants. It runs on self-hosted infrastructure, so nothing leaves the building.

An open source terminal app for macOS and Linux, released by Webanion under the MIT license: saved commands that open up to four terminals side by side in one tab, in a layout Termi remembers, and can start with the app; split, reopen, a command palette, a shortcut sheet, a built-in guide, and CPU, memory and network figures in the sidebar. Electron, React, TypeScript, xterm.js and node-pty, built with electron-vite and tested with Vitest, with an MCP server so an assistant can manage the saved commands. Source at github.com/webanion/termi.

A quiet desktop app for Linux, Windows and macOS that counts keyboard and mouse use, charts it and exports reports, built for Ja Turna in five weeks. It counts presses without recording what anyone types, charts a day or a lifetime and stays smooth over months of data, downloads any table as a PDF a manager can share, and backs up its whole history to one file for a new machine. Electron, React, TypeScript and Redux from one codebase.

BD

Full-time

On-site

1

5.0

A cooperative finance organisation was running member records, savings, loans and investor capital across paper and spreadsheets, with no way to audit a branch or close a day cleanly. We built one system that holds all of it: member registration, daily collections, loan application through to disbursement, a multi-branch ledger, investor capital and an audit log that records who did what. Officers record each collection the moment it is made, managers approve loans and close the day, and the permission model decides what each role can see and do rather than hiding buttons. Everything shown in this case study runs on seeded demonstration data; real member records never appear in portfolio material.

BD

Full-time

On-site

A static portfolio site could not carry work in five languages or keep pace with the writing behind it, so we replaced it with a platform. A headless CMS holds every case study, article and record; a Next.js front end renders them in English, Bengali, Spanish, Hindi and Chinese; and an MCP server exposes the same content to AI assistants, so an agent asked about this work reads the source rather than guessing from a scrape. Search, media handling, an approval flow and a public discovery layer all run on it. The proof is recursive: the page you are reading is served by the system this entry describes.

A website for the Sukalyan Research Group at the Department of Pharmacy, Jahangirnagar University, led by Professor Sukalyan Kumar Kundu: seven research areas with their techniques and papers, a filterable publication list of one hundred and twenty-four Google Scholar entries grouped by year, the principal investigator's profile, the members by name and portrait, an alumni destinations wall, a Lab Life gallery and a four track join page with an email checklist. Next.js with static export, React and TypeScript, Tailwind CSS, all content behind one query function so the move to a headless CMS changes nothing else. Deployed as a single container on a self-hosted Kubernetes cluster.

BD

Full-time

On-site

A custom WordPress website that Grace Bangla Language Center's own staff have run for years, for a school that teaches Bangla to foreigners living in Dhaka. The site carries the school's own identity, explains the courses and teaching method before a newcomer's first call, and lets the staff change every page, notice and event themselves. The project closed with video tutorials instead of a support contract.

BD

Full-time

On-site

1

5.0

The studio's own infrastructure on a self-hosted Kubernetes cluster, planned in February 2026 and maintained every day since: its website, CMS and MCP servers and the client platforms it looks after, served through Cloudflare tunnels, with every database dumped and checked each night, metrics and alert rules that reach a phone, an outage monitor outside the house, a container registry and an npm registry, and one private console that joins merges, runs, images, pods and nodes on a single page.

Builds and deploys moved from GitHub's hosted runners, where every run started on a fresh machine and releases waited on queues and incidents, to a runner pool at home: a build machine that takes every job while it is up, and standby runners on an always-on server behind a watchdog that fails towards shipping. Images go to a private container registry and the studio's libraries to a private npm registry, both in the building, and every run is archived past GitHub's retention. The slowest deploy went from eight minutes twenty-four seconds to three minutes five, and CI came out a third faster.

A second machine that can be switched off at any moment joined a running single-node cluster without a change to any application. An always-on server keeps the control plane, every database and volume and the first copy of every service; the build machine takes the builds and second copies of stateless services behind a taint, and those copies wait rather than fall back when it sleeps. It powers itself off when the work runs out and comes back when a job is queued, a console shows every node, workload and availability span, and every CPU request on the always-on server was measured, taking its reservations from eighty-four to fifty-six percent of what it can allocate.

A family of versioned, framework-neutral packages that every Webanion frontend and backend starts from, with a NestJS layer on the server and React, Vue and Expo bindings in the client: authentication with passkeys and single sign-on, feature flags, an audit trail, multi-tenant data, encryption, files, documents, messaging, real-time and offline, webhooks, workers and a UI kit. Each lives in its own private repository with its own releases and is installed from the studio's private npm registry, and the studio's console shows which consumer is behind on which release.