Campus

Company profile:

Startup name: Campus

Tagline: One project space for teams and AI agents

Elevator Pitch: Campus keeps your repository, terminal, project knowledge, conversations, and AI agent work in one persistent workspace. Built for software teams and independent builders, it organizes collaboration around each project so people and agents can return to the same context instead of searching across chats, documents, tickets, and tools.

Target Market: Software teams and independent builders who want one persistent workspace for code, docs, and AI agent collaboration.

How will you make money?:

How much capital have you raised?: None

Website: https://campus.flutterflow.io

City/Country:

AI-assisted summary:

Campus is a macOS-native workspace from FlutterFlow that places development tools on a persistent, infinite canvas rather than across separate application windows and browser tabs. (Source: https://campus.flutterflow.io) It matters because it is designed around an emerging workflow in which developers and product teams work alongside coding agents, while needing to retain shared project context between sessions. (Source: https://www.linkedin.com/posts/flutterflow_ai-agents-made-writing-code-dramatically-activity-7483143360854020097-Y0Bd)

Problem and target users

Campus targets software builders and teams whose work is fragmented among terminals, browsers, documents, design files, repositories, and AI-agent sessions. (Source: https://www.linkedin.com/posts/flutterflow_ai-agents-made-writing-code-dramatically-activity-7483143360854020097-Y0Bd) FlutterFlow frames the central problem as lost context: users can return to a project, or join a teammate’s work, without having to reconstruct the relevant tools and materials from scratch. (Source: https://www.linkedin.com/posts/flutterflow_ai-agents-made-writing-code-dramatically-activity-7483143360854020097-Y0Bd)

The product appears especially oriented toward developers using terminal-based coding agents such as Claude Code and Codex, as well as teams managing several active projects or workstreams at once. (Source: https://campus.flutterflow.io) A Campus “work area” is presented as a project-organizing space associated with a folder, including an option for a Git worktree-oriented work area. (Source: https://www.linkedin.com/posts/flutterflow_20-terminal-tabs-3-ai-sessions-a-doc-you-activity-7485359739808264192-BETZ)

Product and solution

Campus turns terminals, web apps, notes, documents, files, Git worktrees, designs, and embedded app surfaces into movable tiles on a spatial canvas that users can pan, zoom, and arrange. (Source: https://campus.flutterflow.io) Its terminal tiles use live pseudo-terminals that the company says continue running and retain scrollback through restarts. (Source: https://campus.flutterflow.io)

Collaboration is a major part of the product proposition: users can share a link to bring colleagues into the same canvas with live cursors and shared tile context. (Source: https://campus.flutterflow.io) The site also says Claude and Codex can operate as tiles, while the Campus CLI enables agents to perform actions such as creating or moving tiles, typing prompts, and clicking within webviews. (Source: https://campus.flutterflow.io)

Campus describes itself as local-first, with workspace state stored in plain files, and says it uses a custom Flutter engine. (Source: https://campus.flutterflow.io) For extensibility, the company advertises a Dart SDK for defining custom tiles, commands, rendering, and tool orchestration. (Source: https://campus.flutterflow.io)

An official GitHub repository also shows an extension registry, where Campus users can browse curated extensions through the product’s settings; the currently listed extension displays Claude Code and Codex usage in compact cards. (Source: https://github.com/FlutterFlow/campus-extensions) The registry documentation says extensions are validated before publication and that users are shown requested access before enabling them, although extensions may run with permissions granted by the user. (Source: https://github.com/FlutterFlow/campus-extensions)

Business model, pricing signals, and traction

Campus was described by FlutterFlow as being in alpha at launch, indicating that the product is still early and its feature set, reliability, and commercial packaging may change. (Source: https://www.linkedin.com/posts/flutterflow_ai-agents-made-writing-code-dramatically-activity-7483143360854020097-Y0Bd) The public Campus site offers a macOS download, but it does not present public pricing or a subscription plan, so a business model cannot be verified from currently available first-party information. (Source: https://campus.flutterflow.io)

FlutterFlow stated in a later post that Campus ranked third on Product Hunt, but public information reviewed for this overview does not establish sustained adoption, revenue, customer counts, or enterprise deployment. (Source: https://www.linkedin.com/posts/flutterflow_20-terminal-tabs-3-ai-sessions-a-doc-you-activity-7485359739808264192-BETZ)

Expert take

Campus has a clear product thesis: the coordination layer for AI-assisted software work may be a persistent visual workspace, not another chat interface or IDE pane. Its strongest differentiator is the attempt to make human collaborators, live development environments, and agents operate in one shared spatial context.

The key question is whether the canvas becomes a genuinely lower-friction daily workspace than established combinations of IDEs, terminals, browser tabs, Git tooling, and collaboration software. Its alpha status and absent public pricing leave important questions about reliability, security controls, team administration, and monetization unanswered.

Note: Information based on publicly available sources at the time of writing, and summarized by AI.