Skip to content
let's build

Ideas today. A brighter tomorrow.

Where yourbright ideas becomepolished software

let's build

Companies we have worked with

  • Pinterest

Our expertise

Software expertise, clearly defined

From a first product to an existing system, the work starts with a clear problem and a practical next step.

Custom software

A real problem turned into a product people use, from a new idea to an internal tool.

let's build

Backend & architecture

APIs, data models and system boundaries your product can grow on.

AI & agent engineering

Language models behind a real interface, with limits you can check.

Integrations & automation

Tools connected and repetitive work gone, with people still deciding.

Web & mobile product build

The interface people use, accessible and quick on their devices.

Cloud, deployment & reliability

A predictable release path and the monitoring that goes with it.

Technical consulting

A read of an existing system and a practical next phase.

Maintenance & handover

A running system kept healthy, documented and handed over.

Discovery & technical due diligence

Scope before the build, or a codebase read before you commit.

Selected partnerships

Companies we have worked with

Aurora has worked with these companies across software projects and contracts.

  • Pinterest

    A visual discovery platform where people find and save ideas, and discover products.

  • A proactive health company offering whole-body MRI screening and personalized health insights.

  • Brazilian commerce platform connecting sellers to marketplaces, with ERP, logistics and payment tools.

  • A software development company providing engineering teams and end-to-end delivery.

  • A nearshore technology staffing company connecting Latin American engineers with US teams.

  • A Brazilian real estate developer creating residential properties in São Paulo.

  • Sintalk

    A customer engagement platform bringing messaging channels, identity and attribution together.

Clarity at every step

  1. 01

    Understand the context

    Start with the problem, the people affected and the constraints.

  2. 02

    Define the next step

    Agree on scope, architecture and a useful milestone, with trade-offs visible.

  3. 03

    Build and review

    Deliver working software in small increments, with tests and room for feedback.

  4. 04

    Evolve with care

    Hand over the context and use what you learn to decide what comes next.

I started Aurora to do this properly.

After fifteen years I have watched enough software get shipped half-finished to know what it costs the people who inherit it. Aurora is me building the way I always argued it should be built, with whoever is paying for it in the room.

What leads us

  • No spec needed. Bring the mess.
  • Decisions get written down the day they are made.
  • What is included is in writing before we start.
Giovani MoutinhoFounder

Projects and open source

Tools we share, and fixes we send upstream.

AI Cursor InitAI-powered documentation framework for the IDE.Myinstants BotDiscord bot for playing MyInstants sounds.CC ArsenalReusable skills for coding agents.gh-agent-screenshotGitHub screenshot uploads from agents and the command line.Covid Data TrackerData collection and tracking for Covid cases in Montes Claros.Claude WhatsAppWhatsApp channel for Claude Code conversations and tool approvals.VigilantFocus app with music and an audible interruption.stopslopDeterministic linter for AI coding artifacts.

Open-source contributions

A few things worth knowing

A good project starts with clear expectations.

Can we start with an idea, not a specification?

Yes. Bring the problem, the people affected and what you hope to change. Discovery turns that context into a clear scope and a useful first milestone.

Can you work with our existing software?

Yes. An initial review establishes the architecture, constraints and risks. From there, we can define focused improvements, integrations or a staged evolution without assuming a rewrite is the answer.

How are scope, timing and pricing agreed?

After understanding the work, the proposal sets out deliverables, assumptions, review points and the commercial model. Dates and fees are agreed for your context, not pulled from a generic package.

How does collaboration work?

With a shared plan, written decisions and regular reviews of working software. Communication tools, review cadence and responsibilities are agreed at the start.

What happens after launch?

The engagement defines handover, documentation and any ongoing support. You should know what is included, what needs a separate agreement and who owns each next step.

contact

Let's build something bright

Tell us what you want to build or improve. For a direct conversation, email [email protected].

[email protected]