Technology
Structure, platforms and machines, chosen for your team.
Twelve plain-language pages on how OlDevs structures a product and what it builds on: front-end and back-end platforms, mobile, cloud, data, AI compute and chipsets, the processors and devices your users hold, security, integrations, and what changed in 2026.
Updated September 2026 You own everything Reply within one business day
build-orchestrator
mainsrc/
queue.ts
pool.ts
retry.ts
types.ts
index.ts
1
2
3
4
5
6
7
8
export interface BuildJob {
repo: string;
region: "ca-west-1";
}
export async function queue(
job: BuildJob,
): Promise<Run> {
return await pool.add(job);
212
Tests passed
0
Type errors
1.4s
Build time
Watching src/ — optimised rebuild on save
Technology, in short
OlDevs chooses technology for the team that will run it after launch, not for novelty.A modular structure, mainstream platforms with long support lives, Canadian or US hosting regions to match your data-residency needs, and AI hardware sized to the job. Every recommendation is explained on these pages and confirmed at scoping.
Key facts
- 01Studio
- Vancouver, British Columbia
- 02Updated
- September 2026
- 03Default database
- PostgreSQL
- 04Front-end defaults
- React / Next.js, Vue, Svelte
- 05Mobile
- Swift, Kotlin, React Native, Flutter
- 06Hosting
- AWS, Azure, Google Cloud, Cloudflare
Technology pages
Everything we build on, explained.
Each page covers the options, what changed in 2025–2026, how we choose, and the questions clients ask first.
Architecture & Structure
Modular monolith or microservices, queues or direct calls, one tenant or many: the shape of a system decides how cheap it is to change in year three. Here is how OlDevs picks a structure, what each one costs later, and how we hand it over.
- Modular monolith
- Microservices
- Serverless functions
Front-End Platforms
React, Next.js, Vue, Svelte, Angular, Astro and WordPress each earn a place on our shortlist for different jobs. Here is how we choose one for a corporate site, member portal, store or dashboard, and what each choice costs the team that maintains it.
- React 19 and Next.js (App Router)
- Vue 3 and Nuxt
- Svelte 5 and SvelteKit
Back-End Platforms
Seven runtimes, three API styles and the plumbing around them: sign-in, queues, caching, file storage, email and SMS, rate limits. We recommend each one for a reason you can repeat to your board, and we say plainly what it costs to hire for later.
- Node.js with TypeScript
- Python with FastAPI or Django
- PHP with Laravel or WordPress
Mobile Platforms
Native iOS in Swift and SwiftUI, native Android in Kotlin and Jetpack Compose, or cross-platform with React Native, Flutter and Kotlin Multiplatform. Here is what each asks of you after launch, and how we decide which fits your app, team and budget.
- Native iOS: Swift 6 and SwiftUI
- Native Android: Kotlin and Jetpack Compose
- React Native with Expo
Cloud & Infrastructure
AWS, Microsoft Azure and Google Cloud, plus Vercel and Cloudflare where a smaller footprint fits. Canadian regions by default, infrastructure as code, backups you can actually restore, and monthly costs sized to the site or app you really run.
- AWS with Canadian regions
- Microsoft Azure
- Google Cloud
Data & Databases
Your database outlives every framework in front of it. We default to PostgreSQL, add Redis, document stores, vector search or a warehouse only when the workload asks for it, and hand over schemas, migrations and backups you own outright.
- PostgreSQL as the default
- MySQL and MariaDB for WordPress and legacy
- SQLite for edge and embedded
AI Compute & Chipsets
Most AI projects never need a training cluster. We match each workload to the right silicon, rent before we buy, and confirm availability, region and cost at scoping, because chip names and supply change quickly.
- NVIDIA Hopper and Blackwell in the cloud
- AMD Instinct and Intel Gaudi 3
- Google TPU and AWS Trainium or Inferentia
Processors & Devices
Phones, tablets and laptops changed more in 2025 and 2026 than in the five years before, mostly because of the neural processors now inside them. Here is what that means for the software we build for you, and how we decide what to support.
- Apple iPhone: A18 to A19 Pro
- Android flagships: Snapdragon, Tensor, Dimensity, Exynos
- Apple silicon Macs and iPads: M4 and M5
Machines & Hardware
From the workstations we build on to the kiosks, terminals, scanners and sensors your product ships with, hardware decisions shape cost, support and lifespan. Here is how OlDevs specifies, integrates and supports it.
- Developer workstations, CI runners and device farms
- On-premises servers for regulated clients
- Edge and industrial devices
Security & Compliance
Every OlDevs project ships with threat modelling, OWASP ASVS checks, encrypted data, single sign-on and audit logs as standard, plus the documentation your auditors, insurers and enterprise buyers will ask for. Here is how we decide what each build needs.
- Threat modelling and secure SDLC
- Dependency and SBOM management
- SSO, MFA and passkeys
Integrations & Platforms
Payments, CRMs, ERPs, identity, e-commerce, membership systems and AI providers, connected with the plumbing that matters: signed webhooks, retries, rate-limit handling, documented field mappings and sandbox tests, with every account registered to you.
- Payments and digital wallets
- CRM and marketing data sync
- ERP and finance connectors
Technology Radar 2026
A working radar, not a trend list. Each entry says which ring it sits in, why it moved, and what the choice will cost a client three years from now. Updated September 2026 by the team that builds and maintains the work.
- Adopt: AI coding agents in the delivery workflow
- Adopt: Model Context Protocol for tool integration
- Trial: Agent frameworks paired with evaluation suites
CMS & Site Builders
From WordPress and Shopify to Webflow, Drupal and headless stacks pairing Sanity or Payload with Next.js, we match the platform to your content, your editors and your budget of change, then hand you the keys to all of it.
- WordPress
- Shopify
- Webflow
AI & No-Code App Builders
Prompt-to-app generators and no-code platforms are the fastest way to test an idea. We use them for prototypes and internal tools, tell you plainly where they run out of road, and carry validated work into custom code without starting over.
- AI app generators
- No-code app platforms
- Internal-tool builders
Portals & Intranets
A client portal, a member portal and an intranet solve different problems with the same engineering underneath: sign-in, permissions, documents, notifications. Here is what we build for each audience and how we choose between custom and off-the-shelf.
- Client portals
- Member portals for associations
- Staff portals and intranets
How we choose
Six rules behind every technology decision.
Your team runs it
We pick platforms your people or any competent agency can maintain, so you are never dependent on us.
Boring where it counts
Databases, auth and payments use proven, long-supported tools. Novelty goes where it earns its keep.
Residency first
Canadian and US hosting regions are chosen to match your privacy obligations before anything else.
Accessible by default
Every front-end ships to WCAG 2.2 AA with bilingual capability where you need it.
Sized to the job
From a single GPU for a prototype to cloud clusters for training — never more machine than the work needs.
Reviewed every quarter
Our technology radar is refreshed as platforms change; this section states its update date.
Around the build
Related services
FAQ
Questions about our technology choices.
Mainstream, long-supported platforms: React, Next.js, Vue and Svelte on the front end; Node.js, Python, PHP, Go and .NET on the back end; Swift, Kotlin, React Native and Flutter for mobile; PostgreSQL as the default database; AWS, Azure, Google Cloud and Cloudflare for hosting. Each has its own page here.
No. You own the code, the accounts and the infrastructure, and we choose tools your own team or any competent agency can maintain. Handover documentation is part of every engagement.
Yes. AWS, Azure and Google Cloud all run Canadian regions, and we design hosting around your residency requirements from the first architecture conversation. US clients get US regions the same way.
The Technology section was last reviewed in September 2026. Product names, chip generations and versions change quickly, so we confirm the exact choices for your project at scoping.
Usually, yes. We integrate with existing servers, point-of-sale terminals, scanners, kiosks and IoT devices, and tell you plainly when something is too old or insecure to keep.
Request a quote with a short description of what you need. We reply within one business day with a suggested structure and platform choices, and we explain the reasoning.
Insights
More on the technology.
Where these platforms are heading, and what we now recommend by default.
Web security and privacy in 2026: what changed and what to do now
Passwords gave way to passkeys, privacy law arrived in force, accessibility got deadlines and AI added new risks. What changed through 2026 and the checklist to…
Performance marketing that proves itself: attribution basics for non-marketers
Attribution decides which marketing gets credit for a sale. No model is perfect; the aim is a fair, consistent method that shows where budget actually works.
What an AI copilot actually costs to run in production — and how to keep it reliable
Model fees are the smaller share of a copilot's running cost. Tokens, latency, monitoring and guardrails are the larger one, and they decide whether it stays…
Let’s connect
Tell us what you’re building.
We’ll reply within one business day with a recommended structure, platforms and a tailored quote — no obligation.