S/01
Automation & Internal tools
I turn manual, repetitive tasks into systems shaped around how your organization actually works. Forms and data capture, validation, offline processes, reports, dashboards and document automation.
Technology Consulting · Spec-Driven Development
I turn operational friction
into systems that work.
Centeran is the brand; Rolando QR is the person, a hands-on Technology Director and Spec-Driven Developer. I take complex business processes —slow, manual, expensive—, turn them into a clear specification first, and then into internal tools that are useful, deployable and maintainable: automation, self-owned infrastructure, data and applied AI.
01 Services
I don’t sell technology. I solve problems with it.
Four fronts where I turn real business needs into concrete solutions. The question is always the same: which manual, costly or error-prone task can become a more orderly, secure and scalable system?
S/02
Self-owned infrastructure & Hosting
Virtualization with Proxmox, Linux servers and Docker containers. Private networks, reverse proxies and secure tunnels; deployment, monitoring, backup and restore designed from day one, with real persistence. Managed hosting and self-hosted solutions so you depend less on closed platforms.
S/03
Data & Applied AI
AI as a purposeful accelerator, not a fad. Data extraction, document reading, transcription, classification and semantic search. Data that isn’t just stored: it’s queryable, exportable, auditable and actionable.
S/04
Security & Consulting
Company and internal network audits with actionable reports and specific recommendations. Data protection, email (alternatives to Workspace/365, cPanel, backups, POP/IMAP) and advice for smart purchasing: hardware, software, internet, and cloud vs. physical server.
02 Spec-Driven Development
Spec first. Code second.
Before writing a single line, I write the spec: what gets built, what must never break, and how we prove it works. It’s the project’s source of truth —for you, for your team, and for the AI agents that speed up the build.
-
P/01
The spec is the source of truth
Requirements, data contracts and acceptance criteria in writing, reviewed with you before anything is built. What isn’t in the spec isn’t assumed: it’s asked.
-
P/02
Non-negotiable principles
Security, backups and audit trails are set at the start. No phase, shortcut or deadline gets to weaken them.
-
P/03
Phases with exit criteria
Safeguards first, logic second. Every phase closes with green tests against the spec; nothing moves forward with the previous one half done.
-
P/04
AI on a script, not improvising
AI agents build faster, but against the spec, and their work is checked against it. What the AI says it did isn’t evidence: the diff and the tests are.
The result: clearer budgets, fewer surprises, and a system another team can maintain, because it’s been documented since day one.
03 How I work
From friction to system, in four steps.
A real process, not a promise. Each step answers a concrete question: how it’s built, how it’s deployed, how it’s backed up, how it’s protected, and what happens if something fails.
-
01
Diagnosis
I find where there’s friction, cost, dependency or unnecessary manual work. I start with the business, not the tool.
-
02
Specification
I write the spec: requirements, architecture, data, security, deployment and backup, with measurable acceptance criteria. We review it together before building.
-
03
Build
In phases and against the spec: a concrete tool that runs in real conditions —not a pretty idea on paper—. Every phase closes with green tests.
-
04
Operation
Backup, restore, protection and scaling. The question “what if something fails?” is already answered before handover.
03B In motion
This is what it looks like when friction falls into order.
Nine loose processes —invoicing, inventory, payroll, tickets— lined up on a single spine, with status and capacity in plain sight. That’s what I build.
04 Professional profile
A hands-on technical director, not a specialist locked into a single technology.
My strength is connecting real business problems with concrete technology solutions. I can analyze a need, break it down into requirements, define the architecture, choose the infrastructure, and think through databases, security, deployment, backups and maintenance. Closer to a solutions architect than to a single-tool profile. And it all starts in writing: a spec that defines the system before it’s built.
“Find where there’s friction, cost, dependency or unnecessary manual work, and turn it into a solution that’s simpler, faster, more controlled and smarter.”
01
Practical technical judgment
I look for solutions that work in real conditions, not just in theory.
02
Internal-product mindset
I think about users, flows, permissions, screens, exports and audit trails.
03
Automation-oriented
I quickly spot repetitive tasks or slow processes that can become systems.
04
Business vision
I weigh technology by cost, impact, maintenance, control and operational value.
05 Infrastructure
I understand the layer the application lives on, not just the application.
A practical infrastructure mindset: I can get into the server, see what’s going on, check services, fix permissions, inspect containers, read logs and leave the system stable. I move comfortably across every layer —from the physical server to the end user— and that reduces dependence on third parties.
-
Layer 06
End user
Access, permissions, flows and screens people actually use.
-
Layer 05
Network & access
Reverse proxies, private tunnels, SSH, firewall and controlled service exposure.
-
Layer 04
Data & persistence
Databases, persistent volumes, snapshots, backup and restore.
-
Layer 03
Runtime & containers
Docker: images, networks, variables, ports, dependencies, restarts and redeploys.
-
Layer 02
Operating system
Linux in depth: users, services, cron, Bash scripts, logs and resource monitoring.
-
Layer 01
Physical / virtual server
Proxmox and virtualization: VMs, disks, snapshots, storage, CPU, memory and network.
06 Technical skills
The stack I build with.
A preference for solutions that are controllable, affordable, backed up and simple to maintain. Less dependence on expensive external platforms, more technological autonomy.
- Spec-Driven Development
- Acceptance criteria
- AI-assisted development
- Automated testing
- Proxmox & virtualization
- Linux
- Docker
- Containers
- Private networks
- Reverse proxy
- Private tunnels
- SSH & permissions
- Firewall
- Cron & Bash
- Snapshots
- Persistent volumes
- Automated backups
- Databases
- Deployment & CI
- Resource monitoring
- Self-hosted
- cPanel
- Google Workspace / 365
- Applied AI
- Data extraction
- Semantic search
- Transcription
- Forms & capture
- Reports & dashboards
- Document automation
- Systems integration
- Security & audits
07 Open source
I don’t just recommend it: I build it and share it.
I lead by example. Tools that are my own, controllable and open — like these ones I maintain in the open.
VideoCAT
Free softwareA private catalog for videos stored on external hard drives. Built for collections spread across many drives that aren’t always connected: you know what you have and which drive it’s on, even when that drive is unplugged.
FixTab
Free softwareA Chrome extension that remembers your pinned tabs and puts them back with one click, a keyboard shortcut, or on its own when the browser starts. It restores without duplicating: it opens the missing ones, re-pins the loose ones and keeps the saved order. No accounts, no analytics, no network requests.
CodexBar for Windows
Free softwareCodex and Claude Code usage limits, right in the Windows tray: how much of the session and the week is left, when it resets, and which account still has quota, with multiple accounts per provider. It’s a fork of CodexBar by Peter Steinberger, to which I added a native Windows 11 port.
KRK Wakeup
Free softwareA native, portable Windows utility that sends a short audio pulse every so often so KRK GoAux speakers don’t fall asleep during long pauses. The pulse always goes to the chosen output, even if you switch the default to Bluetooth headphones. Interval, duration, frequency and level are set from a compact window next to the clock.
08 Let’s talk
Which manual task is costing you time and money?
Tell me about the problem in your own words. I’ll reply with an honest read: what makes sense to automate, what doesn’t, and how I’d approach it. No strings attached.
The vendor just wants to sell. I want you to make a smart purchase.