PHP 8
The primary application language across the portal, RIVARO, KamalaTreats and Living Nations.
HomeTechnology
01 Technology
The stack is part
of the product.
What we run, and what we use it for. Nothing on this page is here because it sounds good on a website — if we do not run it, it is not listed.
Application
Python
Automation, data processing and tooling that sits beside the web applications.
JavaScript
Browser behaviour — kept to vanilla modules so pages stay fast and dependency-free.
C# / Unity
Simulation and interactive prototypes, as on Vastro.
Data
MySQL
Primary relational store for portal, platform and application data.
MariaDB
Drop-in relational store on NAS-hosted deployments.
PostgreSQL
Used where an application needs stricter types or Postgres-specific features.
PDO
The only path to the database in our PHP applications — prepared statements, emulation off.
Infrastructure
Docker
Every service runs in a container, so a rebuild is reproducible rather than remembered.
Linux
The host layer under the container and storage stack.
TrueNAS
Storage server for pools, datasets, shares and snapshots.
Synology
Smaller NAS deployments where a client needs storage on site.
Apache
Virtual-host web server for the sites we host — one vhost per project.
Nginx
Frontend and API gateway routing where a platform needs split document roots.
NVIDIA GPU
Specified and built into workstations for compute-heavy and render work.
Edge & Interfaces
Cloudflare
DNS, edge proxying and TLS — configured Full (Strict), so the origin certificate is validated too.
Stripe
Payment handling on e-commerce builds, so card data never enters the application.
REST APIs
How our own services and third-party systems talk to each other.
Gemini API
The language model behind the content assistant, called server-side only.
Cron
Scheduled work — world state, syncs and maintenance that must run without a visitor.
Git
Version control and the deployment record for project code.
Deliberately absent: Ollama, CUDA compute workloads, Proxmox and Windows Server. They are common in this industry and we do not currently run them, so they are not claimed here. If that changes, this page changes.
02 How we think
We think
in systems.
We design the application, the data and the infrastructure as one system. Most problems that look like software problems are one layer down.
- 01 User The person with the actual job to do. Every layer below exists for them.
- 02 Application The interface and the business rules. Where most agencies stop.
- 03 AI / Logic Decisions, derivations and model calls — server-side, structured, replaceable.
- 04 Database Schema, constraints, migrations, and the backup that has been restored at least once.
- 05 Infrastructure Containers, web servers, processes and the boxes they run on.
- 06 Network DNS, TLS, routing, and what is allowed to reach what.
- 07 Hardware Disks, memory, CPU, GPU. The layer that decides what the ones above can promise.
Your next system starts here.
Have a technical problem worth solving?