Partnerships

Build on the canvas

Deska is a workspace, not a walled garden: terminals, editors, browsers, docs and coding agents share one surface. If you build something a developer keeps open all day, there is a place for it here.

Five ways to work together

Pick the one that sounds like you. If none of them do, write anyway β€” the list grew out of conversations, not the other way around.

Agent and tool integrations

Run inside the canvas as a first-class panel, next to the terminal and the editor the developer is already using.

  • CLI coding agents, the way Claude Code, Codex and OpenCode already run
  • Dev tools with a web UI worth keeping on screen
  • Anything that speaks a terminal or a local port

Model and infrastructure providers

Power the managed side of Deska: the inference behind voice, chat and the coding agents for users who do not bring their own keys.

  • Model providers and inference gateways
  • Speech-to-text and voice infrastructure
  • Sandboxes and remote execution environments

Resellers and education

Put Deska in front of a group at once: a team, a cohort, a classroom. Volume licensing and invoicing, without a per-seat maze.

  • Bootcamps, universities and training programs
  • Consultancies rolling out a standard toolchain
  • Regional resellers with their own invoicing

Creators and community

Teach the workflow you actually use. If your audience builds with AI agents, we would rather support you than run ads.

  • Course authors, streamers and newsletter writers
  • Communities around agentic coding
  • Conference and meetup organizers

Embedded and OEM

Ship Deska as the workspace inside your own product, with your defaults, your agents and your onboarding.

  • Platforms that need a real dev environment on the desktop
  • Internal developer platforms at scale
  • Hardware and OS vendors bundling a toolchain

What the deal looks like

What we bring

  • A place in the canvas: your surface running as a panel users can arrange, not an iframe in a settings tab.
  • Documentation and changelog coverage when the integration ships.
  • A direct line to the people writing the code. No partner portal.
  • Co-marketing on our own channels β€” honest about what the integration does and does not do.

What we look for

  • It works local-first. If it needs the cloud, it says so plainly.
  • It respects the user’s keys and data: no silent routing of prompts or files.
  • Someone on your side owns it, so it does not rot after launch.
  • It earns the screen space. A developer keeps very few things open all day.

How it goes

01

Tell us what you have in mind

One message with what you build, who it is for, and how it would fit inside the workspace.

02

We reply within two business days

A real answer: what we think, what it would take, and whether we are the right fit right now.

03

Pilot, then ship

We scope something small, run it with real users, and only then put it in front of everyone.

Have something in mind?

Send it over. Half-formed ideas are welcome β€” most partnerships start as one.

Contact the team
πŸ’‘ Ideas+πŸ› BugsSuggest a feature or report a bug