Product engineering · Taguig, Philippines
We build web platforms, mobile apps, backend services, cloud infrastructure and AI automation for businesses in the Philippines and abroad. Then we stay on to monitor what we ship, respond to incidents and release changes.
Capabilities
Each area has a page of its own, with what we deliver and the stack we use.
Public sites, portals and admin consoles, built in TypeScript and React.
iOS and Android apps from one codebase, built with React Native and Expo.
The services behind a product: APIs, data, payments and devices.
Cloud infrastructure described in code, with deployments that repeat.
We stay on after launch to monitor, respond and release.
Automation for repetitive work, with AI where it saves real time.
Selected work
Each case study covers the problem, what we built, the platforms and the stack.
EV charging
We built VoltHub's driver app, public website and operator console, along with the back end that talks to its chargers.
Platforms
Deals and local commerce
We built the consumer app, the consumer website and the merchant portal for a deals platform in the Philippines, along with the APIs and payments behind them.
Platforms
Beauty and skin care
We built a website in English, Simplified Chinese and Malay for a skin care studio in Kuala Lumpur, with its services, published rates and a booking path that starts on WhatsApp.
Platforms
How we work
We start by learning how your business works and which steps the software has to support. We check those flows before we commit to a plan.
We build in TypeScript, with review and automated checks on every change. Schema changes live in migration files, so every change can be read and repeated.
Each release goes to staging before production. For mobile apps, we submit builds through Expo EAS and keep the release steps written down.
We stay on after launch. We watch errors and traces, keep a runbook for each system, cover production on call and release changes through the same staged steps.
Engineering standards
The practices we use day to day on production systems.
TypeScript is our default, so many mistakes show up in the editor before they reach a user.
Changes go through review and automated checks in GitHub Actions before they ship.
Cloud resources are described in code with Pulumi, and changes to them go through review like any other code.
Errors and traces go to Sentry, and uptime checks run in Better Stack, so we can see what failed and where.
Each system we operate has a written runbook, so the engineer on call knows what to check first.
Releases move from development to staging to production, so problems can show up in staging first.
Stack
Prefer email? official@fundamental-it-solutions.com
