The stack we build on

Everything below is a tool Magic Ship works with on real client work. This is not a partner directory and it is not a list of logos we like: it is what one shop in Vancouver, BC, reaches for, grouped by the job it does.

There are 51 of them. Each has a page saying what it is, how we use it, and where it is the wrong choice. The last part is the one worth reading.

Product names and trademarks belong to their owners. Naming a tool here implies no partnership, certification, or endorsement in either direction.

Model providers

The labs whose models we call, hosted or run on hardware you own.

Agent frameworks

The harnesses that turn a model into something that takes actions.

Retrieval and vector

Ingestion, indexing, and search over a company's own documents.

Data and backend

The databases, languages, and services under everything we ship.

Application and frontend

The interfaces people actually touch, and what we build them with.

Evaluation and observability

How we tell whether a change made the system better or worse.

Infrastructure and deploy

Where the code runs, and how it gets there.

Automation and integration

Workflow tools and the APIs of the systems a client already runs.

Checking our stack against yours

If the thing you are building runs on something above, say so and we can skip the introductions. If it runs on something we have never touched, say that too - it is a shorter conversation either way.

Start a project