One person.
One studio.
Zero middlemen.
Complete ownership. I design, code, ship, and maintain. Every project has its own repo, CI/CD, documentation, and handover. No intermediaries filtering what I say — no surprises at the end.
I'm Tiago.
Since 2019 I've been building software — at first as a studio, then as an obsessive hobby, and now as my job. I started with Flutter because I wanted to ship to iOS and Android without duplicating code, and I stayed in mobile because that's where you see if you know product or just throw features at the wall.
Backend was taught to me by Node. Infrastructure was taught to me by making mistakes. AI is being taught to me by hype vs. what actually works in production — I'm learning live, and I tell you what's worth it and what's not.
Creapolis is not a disguised agency. It's one person — me — who designs, codes, publishes, and maintains. If you hire me, you talk to me. If I deliver something, I wrote it. There's no team behind that's going to change the game mid-project.
From an empty repo to apps in stores.
It's not a straight line. Every project is a technical decision: which stack, which architecture, what to sacrifice. Some made it to production, others died at commit 47. Everything contributed.
Flutter & Node.js
Started with Flutter to ship to iOS and Android from a single codebase. Node.js for backend. The stack that would define the next years.
Creapolis is born
I began signing work under the Creapolis name. Own projects, experiments, and first collaborations with real clients.
Apps in stores
Pepinillo and Películas reached Google Play. Honest product exercises: what happens when one person decides, builds, and publishes?
Solennix
The first own app as a commercial product. iOS, Android, and web. Event management for LATAM. The studio stopped being just code and became product with real users.
One-person studio
Direct consulting, apps in production, and products in development. Every project has its own repo, CI/CD, docs, and handover. No middlemen.
Four non-negotiable
principles.
None of these are revolutionary. All of them are rare in the industry. Here they are in writing so you know what to expect before hiring me.
Concepts before code
I don't write a line until I understand the problem. If you can't explain why a feature exists, it shouldn't exist.
Direct, no middlemen
You talk to whoever writes the code. No project managers, no translations, no "let me ask the team and get back to you".
Honesty over marketing
I tell you what I can and can't do. If I don't know something, I research it. If something can't be done, I tell you before billing you.
Product over brief
The brief is the starting point, not the Bible. I build what people will actually use, not what's written in a PDF.
Real infrastructure.
What separates a professional project from an amateur one: not the code, but how it is maintained after launch.
Own repo per project
Each client gets their own repository. Versioned code, complete history, no dependency on anyone.
Automated CI/CD
Tests, linting, and automated deploy on every push. No "try it on your machine" — if CI passes, it works.
Technical documentation
Architecture, decisions, local setup, troubleshooting. Your team can maintain it without asking me every time.
Backups & monitoring
Database with automatic backups. Uptime and performance monitoring. Alerts before your users notice.
Complete handover
At project end, I deliver documentation, access to all services, and a transfer session. I don't disappear.
Post-delivery support
30 days of included support after launch. Bugs, minor adjustments, questions — no extra cost.
What I use daily.
This isn't a list of what I put on my CV three years ago. It's what I write this week. If it's not here, either I don't know it or it's not worth it.
Does this way of working resonate?
If you're looking for a direct collaborator who asks before coding and responds the same day — we're on the same page.