Technologies

The stack we actually use.

Not a padded list to rank for every framework keyword — this is what shows up in our real projects, with links to the work that proves it.

Next.js

Our default for anything customer-facing.

The default language, not a nice-to-have.

Where the ML and data work actually happens.

For the services that cannot afford to be slow or flaky.

The default database until there is a specific reason not to.

For infrastructure that needs to stay boring under load.

Our most common cloud, when a client does not already have one.

Where a client already runs on GCP, or the data tooling favors it.

For enterprise clients already standardized on Microsoft.

One of two default LLM providers, picked per use case.

The other default LLM provider, picked per use case.

The retrieval layer underneath every RAG system we ship.

Orchestration glue, used where it earns its complexity.