Question 1

What does Mirio Technologies do?

Accepted Answer

Mirio Technologies is a software engineering studio registered in Hong Kong under business registration 76928444. We work in three areas: product engineering, meaning backends, web and mobile applications; fractional CTO work, meaning cloud architecture, cost control and delivery process; and helping enterprise teams adopt large language models without putting their data at risk. The studio runs as a senior core plus a small group of freelance partners we bring in per project, so the people on your work are chosen for the problem rather than for who happens to be free.

Question 2

Who will actually work on my project?

Accepted Answer

A senior core led by the founder, an AWS Certified Solutions Architect with ten years of production experience, plus freelance partners we have shipped with before when a project needs a specialist. You meet everyone who will touch the codebase before they start, you work with them directly in your repository and your Slack, and nobody is put in front of you on a call and then swapped out afterwards.

Question 3

What expertise can you bring in through partners?

Accepted Answer

Frontend React and React Native, AWS, Google Cloud and Alibaba Cloud infrastructure, AI engineering, and systems work in Go and Rust. These are people we have worked with on previous projects rather than a recruitment pipeline, so we can tell you honestly at the start whether we have the right person available or whether you would be better served elsewhere.

Question 4

How quickly can you start, and what happens first?

Accepted Answer

We read your codebase and infrastructure on day one and write down what is actually slowing the roadmap. A written architecture plan follows around day three, with the monthly AWS cost worked out before anything is built. Commits usually start landing in your repository during the first week, rather than after a multi-week discovery phase.

Question 5

Which parts of the cloud stack do you work in?

Accepted Answer

Mostly AWS: serverless and container workloads on Lambda and ECS Fargate, EventBridge, SQS and SNS, DynamoDB and RDS with PostgreSQL, IoT Core for device fleets, and Athena and Glue for data pipelines. Infrastructure as code with AWS CDK or with Terraform and Terragrunt, and continuous delivery through GitHub Actions. On Google Cloud we have built data warehousing on BigQuery with reporting in Looker Studio. We also work with Alibaba Cloud, which matters if you need to serve users inside mainland China, and partners cover deeper GCP and Alibaba Cloud work when a project calls for it.

Question 6

Can we adopt LLMs without sending company data to a third party?

Accepted Answer

Yes, and that is most of the LLM work we do. We deploy self-hosted setups inside your own network, including the open-source OpenClaw agent, with retrieval over your internal documents so nothing leaves your infrastructure. Where a hosted model is acceptable we work with Claude, OpenAI, Google Gemini and AWS Bedrock, and we settle data governance before rollout rather than after.

Question 7

Do you work on existing systems or only new projects?

Accepted Answer

Mostly existing systems. The typical engagement is joining a team whose roadmap has stalled: reading the code, repairing the delivery pipeline, reducing the AWS bill and shipping the features that were stuck. On one smart-facilities platform that work cut the AWS bill by 60 percent and shortened release cycles by 70 percent.

Question 8

Where are you based and which timezones do you cover?

Accepted Answer

The company is registered in Central, Hong Kong, and we work with teams across Europe and Asia. Recent clients have been based in France, Singapore and Taiwan, so both European and Asian working hours are normal for us.

Question 9

What do we keep when the engagement ends?

Accepted Answer

Everything. We write standard TypeScript, Python and AWS infrastructure rather than a proprietary framework, so there is nothing to license and nothing only we can maintain. Handover includes runbooks, documented deploys and a walkthrough with whoever picks the system up after us.

Writing

Serverless Computing for a Modern-Day Development