Build on Apex.

Apex is a browser, and it is also a platform. Its companion works in real tabs, its kit lets anyone build apps and games that run inside it, and everything people make can travel to others as a pack. The code is open, so the platform belongs to everyone who builds on it.

Read docs/developers.md

Personal AI that belongs to people

  • Personal AI should belong to people, not to platforms.

    Apex puts an AI companion in a browser you own: the code is open, your data stays on your computer, and you choose the model it runs on.

  • A platform gets stronger with everyone who builds on it.

    Every pack, app, companion and connector someone makes makes Apex more useful for everyone else, and every contribution to the core makes the base better for all of them.

  • Open standards, no lock-in.

    Apex speaks the web, runs Chrome Web Store extensions and connects to any MCP server. What you build for Apex builds on standards you already know.

Together we can build something no single company can: a browser and an AI platform that belongs to the people who use it and build on it.

What you can build

From a one-line skill to a change in the core. Each starts with a guide in the repository.

  • Packs

    Skills, routines, site tweaks, themes, panels, commands and page menu items, shared as one signed file.

    docs/packs.md
  • Apps and games

    Small apps the companion builds with you, or you build by hand with the Apex kit. They run sandboxed inside Apex, and companions can appear in their scenes.

    docs/apps.md
  • Companions

    Characters with their own look, personality, skills and routines. A character you make can be your brand’s mascot inside Apex.

    docs/companion-system.md
  • Connectors

    Any MCP server becomes a tool the companion can use, with your approval.

    docs/architecture.md
  • The browser itself

    New model providers, platforms, languages, accessibility and features in the open-source core.

    CONTRIBUTING.md

For creators and organisations

The licences are written so that people can build real things on Apex, including things they sell.

  • Earn from what you make. Packs, apps and companions for Apex may be sold, including ones that use Apex’s companion art.
  • Bring your brand into Apex. A pack, app or world can carry your own character as its mascot, inside Apex. Outside Apex, and for the six Apex characters, the art licence says no.
  • Run it in your organisation. An organisation’s policy can force-install, allow or block packs and hand them managed values and sign-in.
  • Say it’s for Apex. You may say truthfully that what you made works with Apex, as long as it doesn’t look official.

The details are in the companion art licence and the trademark policy.

The principles we build on

  • The person stays in control. The companion asks before anything that matters, and it is never allowed to enter passwords or card details.
  • Private by design. Apex keeps your data on your computer and has no analytics.
  • Safe to share. Packs are signed, reviewed before every install and sandboxed.
  • Open by default. The code is MPL-2.0, and Apex builds on open standards.

Start building

  1. Make something today. Ask your companion to build a skill, a routine or a small app with you, then share it as a pack. To build by hand, start with the kit and the examples in apex-apps.
  2. Learn the core. Clone the repository and run npm install and npm run dev (Node.js 22.12 or later). Then read architecture.md and the specs in docs/design.
  3. Contribute. Pick a good first issue and read CONTRIBUTING.md.
  4. Join the community. Say hi on Discord and in GitHub Discussions, and see what others made in apex-packs.

Build the thing you’ve been missing.

Download Apex, or clone it and run it from source. Then share what you made, and tell us on Discord.

Download Apex Free and open source. Runs on Claude with your own Anthropic API key. How to get started