Work should be visible
If an agent used a tool, you can see the call. If a person approved a gate, that is on the log too.
About
A studio for work that has a shape.
Aipena started from a simple irritation: AI products kept handing people a blank chat and calling it a workplace. We wanted a bench — somewhere you could assemble a team of agents, lay out tools, wire the apps you already use, and draw a path you could run again on Monday.
The name is a nod to the pen: a tool you pick up, not a genie you plead with.
We are based in Florida and build for U.S. teams who already have a way of working — Slack threads, docs, tickets, calendars — and do not want to abandon it for a new tab that forgets everything overnight.
Human gates
Named agents
Visible logs
Least privilege
What we hold to
Four things we will not trade away.
Roles beat blobs
A single omniscient assistant is hard to trust. A researcher, a writer, and a reviewer are easier to brief.
The apps stay yours
Integrations listen and write back. We are not asking you to migrate a company into our chat.
People keep the pen
Publish, mail, and money-adjacent actions wait. Automation is a path, not a blank check.
The first bench
A small studio in Windermere wired agents to a handful of tools because chat windows kept losing the plot.
Integrations, then paths
Slack and docs came first. Workflows followed once teams asked to run the same sequence every week.
Aipena as a workspace
Named agents, scoped tools, human gates, and recipes you can copy — the product as it sits today.
Say hello