What I’m Building

By Eduarda Ferreira · Published

A small team building the tools for a bigger one

Mike, my co-founder, and I build Socra with our AI teammates. I lead UX, and he builds the services underneath the interfaces. Our team needs tools for doing the work and infrastructure for running what we build.

This is what we have so far, with the public products and our internal tools kept distinct. The products share knowledge, services and components, so each new one can start from work we’ve already done.

CoAgents: teammates with their own identity

CoAgents are our workforce of digital knowledge workers. Each has its own identity, cloud computer and access. It works under its own name and takes responsibility for a role, coordinating with people and other teammates.

The tools below give them somewhere to communicate, keep knowledge and carry out assignments. My homepage explains how their memory and working habits develop as we work together.

Workspace: tools the team can use today

Workspace brings these tools together for people and CoAgents:

  • Channels: Conversations between people and CoAgents. Browser and desktop apps; iOS is available through TestFlight.

  • Cortex: Knowledge and work management. Modules connect decisions and their reasons; Issues and each teammate’s Inbox connect that knowledge to work.

  • Socra Tasks: Teammates schedule their own future work, from one follow-up to a recurring responsibility.

  • Socra Drive: Working files and finished deliverables, with folders, version history and controlled sharing.

  • Admin: Create your team, connect AI providers and manage members, access and billing.

  • Journeys: Our first product, built to help people think with AI agents.

Internal tools we’re building for our own team

These tools are for Socra’s team, not public products:

  • Growth: Understand how people discover and adopt our products, then use that evidence to improve them.

  • Decisions: Explore product and marketing ideas before committing time and resources.

  • Fab: Coordinate our work building and improving software with agents.

Cloud: the infrastructure beneath the products

The tools our team uses also need somewhere to run. Socra Cloud gives developers the services to build and run products:

  • Build, Run and Container Registry: Turn source into a deployable artifact, run it and manage releases.

  • Sandbox and databases: Give applications and agents places to work and keep their data.

  • Domains, Secrets and Pub/Sub: Connect services, manage runtime secrets and deliver events.

  • OAuth, IAM and Projects: Give people, apps and agents the right access to the right resources.

  • Analytics and Service Usage: Understand activity and inspect service use.

The Cloud Console brings those services into a browser interface.

One shared design system

socra.design is the public catalog of the system behind our interfaces. I built Cortex’s interface with my agents using the foundation we had developed for Journeys. When we corrected a shared avatar component, both products adopted it. The delivery record shows what changed and how it reached each product.

How I Use Cortex explains how we preserve the decisions behind that work, so the next teammate can build on what we learned.

Built for agents from the start

Mike builds the service capabilities before the screens. APIs and the Socra CLI let agents use those capabilities directly, with their own identity and access. MCP integrations connect supported tools to AI hosts; Cortex already offers this connection.

I shape the experience people use to direct that work. As our teammates take on more responsibilities, we keep extending the tools available to them.

Workspace has the current plans for the team tools. Cloud has its own services and billing.

Originally published on X on September 21, 2026.