Excede
// about

A dev machine that isn’t a machine.

Excede is a coding workspace that lives in a browser tab. Open it and your files, your editor and your terminal are already there — down to the line the cursor was on when you closed the lid. The code you write runs on the computer in front of you, at full speed, and the workspace itself follows you to the next one.

There is nothing to install, nothing to configure, and no machine to keep alive. It works on a laptop you own, a desktop you borrowed, and the locked-down school machine you are not allowed to put a compiler on.

Excede (live)
Runs onyour own machine
Languages that run8
To installnothing
Usage meternone
Your codestays yours

Why it exists

Writing code usually starts with an hour of not writing code: install the toolchain, fix the PATH, find out the version is wrong, start again. Do that on a second machine and you do it twice. Change laptops and you do it from scratch — and the half-finished thing you were working on last week is still sitting on the old one.

The online editors that solve the setup problem tend to introduce a new one: your code goes to somebody else’s server to run. That means a queue, a cold start, a session that expires while you are thinking, and a limit on how much you may compute before somebody wants paying.

Excede takes a different split. Execution happens on your computer — it already has a processor, and it is doing nothing while you read this. Memory happens on ours: the files, the open tabs, the cursor. Split that way, the setup disappears without your work being handed to a server to babysit.

// the computer is temporary. the workspace is permanent.


How it works

  1. 01

    Your code runs on your machine

    Programs execute inside the tab, on the hardware in front of you — not on a server you are sharing with strangers. No queue, no wake-up wait, no meter running. Interactive programs stay interactive: input stops and waits for you, output arrives as it happens, and Ctrl+C actually stops the thing.

  2. 02

    The workspace outlives the tab

    Your files are stored, not cached — there is no container that quietly expires and takes your afternoon with it. Sign in somewhere else and the tabs you had open, the file you were in and the position you were at are all restored.

  3. 03

    Your work is never stuck in here

    Real Git in the browser: clone, commit, push and pull. Connect a GitHub account and your work is versioned the ordinary way; skip it and you can still download your files whenever you like. Nothing about Excede is a one-way door.


What you can run

A real editor with the shortcuts you already know, a terminal that speaks ls, cd, git commit and npm install, and language support that is the whole language rather than a teaching subset of it.

Start a dev server and a live preview opens beside the editor. Notebooks you write here open in Jupyter, VS Code or Colab — and theirs open here. Point Excede at a folder on your disk and it becomes a workspace, checked for keys and tokens on your machine first, with the final say left to you.

// anything else opens and edits fine — it just can’t be run yet.


What we hold to


Where it’s going

More languages that run rather than just open. Sharper code intelligence in the editor — real errors and go-to-definition, not just highlighting. Easier ways to hand somebody a workspace and have it open for them the way it looks for you.

None of that comes with a date on it. What is on the site today is what works today.


Straight answers

Do I need to install anything?

No. A current browser is the whole requirement, and Chrome or Edge give you the fullest set of runtimes.

Does it cost anything?

No. Excede is free to use today, with no card and no trial clock.

Where does my code actually run?

In the tab, on your computer. Nothing is uploaded to be executed — the only thing our side does is remember your files so the workspace survives the machine.

Is my code private?

Yes. Your files are stored so the service can hand them back to you, and for nothing else. The Privacy Policy sets out exactly what is kept and for how long.

What about API keys and .env files?

Files you open in Excede are saved to your workspace, .env files included, and they are not filtered out. Keep live credentials out of a synced workspace — here, or anywhere.

Can I get my files out?

Any time — push to a GitHub repository, or download them. Keeping your own copy of anything you cannot afford to lose is a good habit on any service, this one included.

Is Excede open source?

No. The Excede software itself is proprietary. That is a statement about our code, not yours: what you write here belongs to you.

Open a tab. Start coding.

No setup, no install, no machine to configure.