Skip to content
← Services

Service · Development

Custom development with PostgreSQL at the center, by someone who builds extensions for the engine itself.

Internal systems, APIs and products where the data matters: we design the model, the security and the AI integration from the database outward. Built by someone who writes PostgreSQL extensions and contributes to its core.

It is for you if…

  • You need a system that handles customer, money or inventory data and still works in five years.
  • You want to connect AI to your real data (assistants, agents, search) without copying it to another service or losing control.
  • You have a team, but nobody deep enough in PostgreSQL to decide the data model, the security or the performance.
  • You are coming from a prototype or a legacy system and want to build the serious version.

What it includes

  • 01

    Data model and schema

    Tables, constraints, indexes and migrations designed for the real business, not for the framework of the month. The database guarantees what the application promises.

  • 02

    Backend and APIs

    TypeScript with Bun and Hono, or Python; parameterized queries, transactions used well, errors that make sense. No heavy ORM in between.

  • 03

    Security from the database up

    Roles per function, row-level policies to separate customers, secrets out of the code, a record of what matters.

  • 04

    AI connected to your data

    Agents propose and PostgreSQL decides (pg_agent_gate), vector memory with provenance and date (pg_phasevec, a 0.x preview), semantic search inside your database. Without sending your data out.

  • 05

    Deployment and operations

    Containers, tested backups, monitoring of what matters, short documentation. We deliver something your team can run.

How we work

Tell us what you want to build.

What it must do, who uses it, with which data. That is enough for the first conversation.

Discuss a project
  1. 01

    Understand the problem

    One or two conversations to learn what the system must do, who uses it, and what happens if it fails. A written scope comes out of that.

  2. 02

    A design you can argue with

    Data model, API contracts and security decisions in writing before coding. Changing a diagram is cheaper than changing a table with data in it.

  3. 03

    Build in deliveries

    Short deliveries you can try. Each with tests on what is critical, ready to deploy.

  4. 04

    Handover

    Code, documentation and a session with your team. If you want, we stay on as support or consulting.

What you get

  • Scope and design in writing before building
  • Code with tests on what is critical and versioned migrations
  • Reproducible deployment with tested backups
  • Short documentation and a handover session

So there are no surprises

  • Default stack: PostgreSQL, TypeScript with Bun and Hono, or Python when it fits. If your team already has a stack, we adapt; the database we do take care of.
  • We do not build what is not needed. If a part is solved by an existing tool, we say so.
  • Quoted per scope, after the understanding conversations. There is no public price.

Who does it

Manuel Reyes Bravo, Chilean software engineer: author of the 7 PostgreSQL extensions on this site (Apache-2.0, published on PGXN) and credited on commits in the PostgreSQL core, verifiable on git.postgresql.org. Works in English and Spanish.

Frequently asked questions

Custom development

Do you work with my team or on your own?

Whichever you prefer. It works especially well as the data and backend piece of a team that already has frontend and product.

Can you integrate an AI model I already use?

Yes. The integration does not depend on the vendor: the AI proposes SQL or queries the memory, and the database verifies and decides. Works with local or API models.

Do you use AI to write code?

We use tools, AI included, with review and tests. What we deliver we understand line by line; that is the difference from a generated prototype.

What happens when you are done?

The code is yours, with its documentation. You can continue with your team, with us as support, or with another vendor without being locked in.

Let’s talk

Tell us what you want to build.

What it must do, who uses it, with which data. That is enough for the first conversation.

Discuss a project
Try it Talk