The Consumption Layer of the Bud Ecosystem

Bud Studio

A desktop app that gives every employee a personal AI assistant — connected to approved tools, learning from their work, and coordinating with other agents to get things done.

Bud Studio desktop app
What is Bud Studio

Enterprise AI, in everyone's hands.

Bud Studio is a desktop app that gives every employee their own AI assistant — connected to the models, tools, and data their organisation has already approved. It's the consumption layer of the Bud ecosystem: where the AI you build actually reaches the people doing the work.

Instead of scattered chatbots and shadow AI, teams get one governed assistant that learns how they work, coordinates with other agents, and gets real tasks done — safely, inside your own environment.

01

Productivity in every employee's hands

A personal assistant that drafts, summarises, monitors, and automates routine work through plain chat — turning AI from a novelty into everyday leverage across the whole workforce.

Adoption at scale
02

Governed and secure by design

Every assistant inherits the models, connectors, permissions, and guardrails set in Bud AI Foundry — so employees get powerful AI without exposing data or bypassing enterprise controls.

Zero shadow AI
03

One layer, not a dozen tools

Assistants coordinate as an agent network on your organisation's own infrastructure — consolidating fragmented AI point-solutions into a single, adopted, cost-controlled workspace.

Consolidated & cost-controlled
How it fits the Bud ecosystem

Foundry controls. Studio consumes.

Administrators configure models, connectors, and guardrails in Bud AI Foundry. Employees consume that work through Studio, inheriting every restriction automatically.

Control & deployment

Bud AI Foundry

Deploy models, build purpose-built agents, apply guardrails, and enable connectors — centrally governed.

ModelsConnectorsGuardrailsPermissions
Consumption

Bud Studio

Every employee gets a personal agent that runs on the organisation's own models and governance.

Personal agentAgent networkSkillsLocal tasks
The core idea

One agent. Two roles.

Every employee's agent is independent — its own memory, its own context, its own personality — playing two roles at once.

A personal assistant

Handles the routine work

Monitors email, drafts minutes from finished calls, sets reminders, and updates task systems like Jira — treated as one of your assistants, all through chat.

EmailMinutesRemindersJira
One agent
A personalised agent

Learns and adapts to you

Its own memory remembers feedback from everyday conversation and adjusts. Shape its personality too — playful, technical, or formal, whatever suits you.

MemoryPersonalityFeedbackContext
Key capabilities

Everything an assistant should do. And more.

Personal assistant

Monitors email, drafts minutes of meeting, reminds you of what's due, and updates task systems — all from chat.

Memory & personality

Remembers feedback from normal conversation and changes how it works. No settings screen — you just tell it.

Agent-to-agent

Your agent reaches a colleague's agent for information — no manual back-and-forth. The capability that sets Studio apart.

Inbox

An observability view into how agents talk to each other — who asked whom, and how they responded.

Connectors

The same tools defined in Foundry. Authorise each with your own account — no raw credentials shared.

Schedulers & reminders

One-off, interval, or recurring tasks created from chat — like a morning routine that flags what's pending.

Skills

Defined procedures for repeated tasks. The agent follows a known flow instead of re-deriving it each time.

Canvas

Turns repeated conversations into workflows automatically, then converts them into evolving skills.

Auto-generated interface

Answers rendered visually where it helps — a price series shown as a chart, generated from the request.

What sets Studio apart

Agents that talk to each other.

Need something from a colleague? Ask your own agent. It reaches theirs, retrieves the information if permitted, and returns with the answer — no one has to be interrupted.

Your agent
Priya's agent
Marketing
Sam's agent
Sales
Finance agent
Purpose-built
HR agent
Purpose-built
Request sent Answer returned
Works in the background Returns only the final answer Subject to each agent's permissions Reach any agent for basic information
The inbox

See the conversation behind the answer.

Agents communicate through an email-style inbox. You make requests from chat — the inbox is where you can look deeper into who asked whom, and respond directly if you choose.

Agent inbox — observability
Your agent → Finance agent
Requesting Q3 spend summary for the review deck
Asked
Finance agent → Your agent
Shared summary — within reporting permissions
Answered
Your agent → Priya's agent
Latest draft of the partnership brief
Asked
HR agent → Your agent
Leave balance confirmed and returned
Answered
Connectors

Your tools, your credentials.

Whatever the administrator enables in Foundry becomes available to your agent. You authorise each connection with your own account through a sign-in flow — raw credentials are never shared.

Foundry
Admin enables tools & configures keys
Authorise
You sign in with your own account
Connected
Your agent can use the tool
Email
Jira
Calendar
Read AI
Docs
Storage
Canvas & auto-evolving skills

Your repeated work, turned into skills.

Studio watches the conversation, spots the procedures you repeat, draws them as a workflow, and converts them into a skill automatically. Change the flow and the skill updates.

Repeated conversation
"Take the notes from today's call…"
Drafted minutes of meeting
"Email them to Alex and log the actions"
Sent & logged in Jira
Workflow on canvas
1Pull call notes
2Draft minutes
3Email to Alex
4Log actions in Jira
Auto-generated skill Meeting → Minutes

Only repeated tasks become skills. One-off requests are ignored. Tell the agent to change the approach and the skill updates itself.

Auto-generated interface

Answers you can see, not just read.

Where the content supports it, Studio renders a visual response instead of text — generated automatically from your request. The direction is for this to become the primary way answers are shown.

You ask
"Show me how our weekly active users trended last quarter."
Weekly active usersQ3
Administration & control

Consumed by users. Governed by admins.

Studio is the consumption side. Control sits with the administrator in Bud AI Foundry — and Studio inherits it.

Models

Admins publish models; users pick from what's published, chosen from chat.

Connectors

Enabled and configured in Foundry; authorised per user without sharing credentials.

Guardrails & security

Set on model deployments in Foundry — including custom guardrails — and applied in Studio.

Permissions

Admins control which tools each user and agent can access, including agent-to-agent behaviour.

What makes Studio different

Three things comparable assistants don't do.

01

Agent-to-agent communication

Each user's agent can reach other users' agents to retrieve information and complete tasks, subject to permissions. Comparable assistants are standalone.

02

Tool permission control

Administrators define which tools each user and agent can access — a level of permission control that is not common in comparable tools.

03

Auto-evolving skills

Repeated workflows become skills automatically and update as your process changes — no manual authoring required.

Deployment & platforms

A desktop app, by design.

Studio is desktop-first so it can access the local file system and carry out tasks on your machine — something a web app cannot provide.

macOS
Native desktop app
Windows
Native desktop app
Linux
Native desktop app

Desktop-first for local file system access, so Studio can carry out tasks on your machine. A web application is not currently offered.

Where Studio fits

Built for how enterprises actually work.

Enterprise rollout

Deploy assistants for every employee. Alongside their personal agent, they use purpose-built agents the organisation publishes — request leave, retrieve a salary slip, and more.

OEM shipment

Ship Studio pre-installed on your systems, so the assistant is available to users out of the box.

Cloud service providers

Offer a Copilot-style or co-working assistant as the consumption layer — applicable as a product, not as infrastructure.

A personal agent for everyone you employ.

Give every employee an assistant that runs on your models, your governance, and your infrastructure — and coordinates across your whole organisation.