We let the people who know a process build the agents that automate it.
It is early, and that is the point.
Last updated · September 28, 2026
What we are doing
The person who knows how an order gets approved rarely writes code. Today their process ends up in a canvas of nodes nobody else can read, or in a queue waiting for the engineering team. That gap is the company.
With Stackbone, that person describes the process in plain language and gets agents and workflows that automate it. The result is a TypeScript repository, so IT reviews and changes it with its own coding agent through pull requests. Customers run it on Stackbone Cloud, or in their own infrastructure down to air-gapped installs for banks and public bodies. We are model-agnostic and cloud-agnostic on purpose, because a bank will not hand its data to a vendor.
How we work
We are a small distributed team between Madrid and Montreal. Small enough that what you build ships the same week and you see who uses it.
A few things that are true about working here:
- You will talk to customers. Engineers included. We do not have a layer of people between the team and the people using the product.
- Decisions get written down. Distributed across time zones means asynchronous by default, which means writing things down properly.
- Scope is wide. At this size nobody has a narrow job description. If you want clear boundaries and a defined lane, this is the wrong stage.
- Two languages. The team works in Spanish and English. You need to be comfortable in English; Spanish is useful, not required.
Our stack
TypeScript across the board, Node, Docker for everything deployable, Postgres and Redis, S3-compatible storage. Monorepo on GitHub with Actions for continuous integration. Linear and Slack.
Open roles
We do not have a formal opening right now.
That does not mean we are not hiring. At this stage the right person usually arrives before the job description does. If you read the above and thought you would be good at it, write to us.
Send a note to [email protected]. Tell us what you would want to work on and point us at something you have built. Skip the cover letter.
Working with us without joining us
If you run an agency or a consultancy and want to build your clients’ automations on Stackbone rather than work for us, that is a different conversation and we would like to have it. How agencies use it. Same address: [email protected].
No job description fits you?
Good. Point us at something you built and say what you would want to own here. One paragraph is plenty.