BUILT AND IN TESTING · NOT YET GENERALLY AVAILABLE

VENELX WORKSPACE.

Write, version, build, sign and ship from one place, on hardware you own: a real terminal, your projects, git, previews and agents on your own Mac mini, then the build, signing, store and sharing you already have.

What is available today

Venelx today is a CI/CD platform for mobile and web apps: self-hosted workers on your own Mac, Windows or Linux machine, iOS and Android signing, store submit to TestFlight and Google Play, OTA updates, QR and public install links, teams with SSO and SCIM, and an MCP server so AI assistants can drive it. Workspace builds on that. It is built and passing our tests, but it has not been released: it will be switched off by default and turned on in stages. Anything marked \u201Cnot yet\u201D below is not built, and nothing here is a promise of dates.

WHAT WORKSPACE IS

1

A terminal that feels like yours

Open a shell on your own Mac mini from any browser. It runs your real login shell and startup files, so your prompt, aliases, Tab completion and suggestions work as they do locally. True colour, search, themes (import from iTerm2), a command palette over your own history, and pause and consent controls on the machine itself.

Built · in testing
2

Run, build and preview

Run, build and test buttons that follow the folder you are in, a picker for simulators, emulators and phones, and previews of the web servers you start, shown on a separate domain so the app you are previewing cannot reach your Venelx session.

Built · in testing
3

Projects, git and notes on your machine

Create, clone or import projects on the machine itself. Browse and edit files, see status and diffs, commit, branch, push and open a pull request. A commit that stages a secret is stopped. Notes and project commands live with the project; commands from a repository are only usable after you have read and trusted them.

Built · in testing
4

Agents, watching and recording

Start Claude Code, Codex, Gemini CLI, Aider or your own command, using your own login. Let a teammate watch a terminal read-only, and record sessions if you choose: output only, secrets masked, encrypted, and everyone can see that it is on.

Built · in testing
5

Exactly the access you intend

Give a teammate access to one machine, certain projects and folders, each of terminal, files, git, commands, preview and notes as read or read and write, until a date, and withdraw it instantly. API tokens get the same checklist, like fine-grained GitHub tokens.

Built · in testing
6

Releases, sharing and team analytics

Releases that link builds to a changelog and need approvals before they reach a store; share links with an expiry, a password and a download limit; build success, duration, queue wait and worker utilisation for your team; and a ship-readiness checklist per project.

Built · in testing
7

Team Server on a Mac mini

Installer and backup scripts that run the API, a worker, a local dashboard and the database on a Mac mini you own, for a small team with no cloud account. The scripts have been checked in a dry run only, not yet on a fresh Mac.

Written · not yet tried on a fresh Mac

NOT BUILT YET

SECURITY MODEL

Everything is off until you turn it on

A platform switch, a switch on the machine, and the owner's switch for that worker must all agree. Terminals, project files and previews each have their own.

You can pause it, even offline

A menu-bar switch and a command stop every terminal within a second and refuse new ones, without needing the network.

Other people need your yes

When someone other than you opens a terminal, the Mac asks you, and can run them in a sandbox or a separate account. A copied access link, or a leaked token, is not enough.

Nothing leaves the project

Files are confined to the project: links, parent folders and case tricks are refused, secrets are never shown, and git runs in a locked-down mode so a repository cannot run programs.

Audited, tamper-evident

Sessions, access changes and recordings are logged in a chain you can verify later. Passwords are asked again before anything powerful.

Never on shared cloud workers

Terminals and project files run only on workers you own, or on your own Team Server, never on Venelx-shared runners.

Venelx does not bundle or supply AI. If you run Claude Code, Codex or another agent, you sign in with your own account on your own worker. Read the general security statements too.

WHO IT IS FOR

Solo developer

Pair your own Mac, open a terminal and run your agent of choice, then build, sign and ship from the same account.

Small team

Share one Mac mini as a Team Server, with roles, shared builds and one place to see what shipped.

Mac mini owner

Already have a Mac mini humming in a closet? Turn it into your build farm, dev box and release desk without renting anything.