Skip to content
Calango Lab — homeCalango Lab
Team

Whoever builds it keeps it standing.

Shipping software and keeping software running are two crafts. Almost everyone who sells the first outsources the second — and it’s exactly on the border between them that projects die, with each side pointing at the other.

There are three of us, and both sides live under the same roof: development on one, DevOps and infrastructure on the other. There’s nobody to point at in here, and that’s the difference you’re hiring.

[ photo ]
pedro sampaio
workbench, not studio
Product and code

Pedro Sampaio

Development and technical lead

Twelve years building for the web. Long enough to have watched a site launch, deliver, age badly and need rescuing — and that, more than any technology, is what teaches you to build with what comes after launch day in mind.

Looks after what the client sees and what holds up what they see: research, interface design, data modeling, integration with ERPs and payment providers, and the architecture call that decides whether a system ages well or becomes debt within two years.

On a project, responsible for
  • Requirements and scope
  • E-commerce, portals and custom software
  • ERP, payment and invoicing integration
  • Architecture and code review
Next.jsNuxtWordPressPHPTypeScriptMySQL
[ photo ]
devops
workbench, not studio
Pipeline and operations

DevOps and continuous delivery

The part of the work a client only notices when it fails. Builds the pipeline that takes code from the repository to production with no manual step: automated builds, a staging environment that matches production, and a deploy that undoes itself when something slips through.

Also the one who instruments what’s running — logs, alerts and metrics — so a problem shows up on a dashboard before it shows up as a customer complaint. Software nobody watches isn’t under control; it’s running on luck.

On a project, responsible for
  • Build, test and deploy pipeline
  • Staging and rollback
  • Logs, metrics and alerting
  • Automating operational routine
[ photo ]
infraestrutura
workbench, not studio
Servers and resilience

Infrastructure and reliability

Sizes and maintains the ground the application stands on: servers, network, database, certificates, backups and restores. The difference between having a backup and having a backup that comes back is a test — and that test comes from here.

Works cost alongside capacity. A good share of a company’s cloud bill is machines oversized out of caution, and correcting that usually pays for the work itself within the first six months.

On a project, responsible for
  • Servers, network and databases
  • Backup, restore and continuity
  • Hardening and incident response
  • Cloud sizing and cost
How we work

Small team, short decisions

Nobody here is an account manager. Whoever gathers the requirement writes the code, and whoever writes the code is in the same conversation as whoever will keep the server up — and that conversation fits in a room, not in a ticket queue.

On larger projects the team brings in specialist partners as the scope demands. That exists so you don’t pay for structure you aren’t using, and so a big project doesn’t stall for lack of hands. What we do not outsource is what sustains the project afterwards: whoever built it keeps answering for it.

Tell us what you need to solve

The first conversation costs nothing and commits you to nothing.