OpenMake 1.19.0 / Desktop 1.7.1
A self-hosted AI workspace. One local model answers by default, and every external provider stays opt-in — your key, your policy.
Both routes use the same product, but the hosted demo is operated for you while self-hosting makes you responsible for the application, model endpoint, and deployment boundary.
Open the hosted demo, or install the Desktop app on an Apple Silicon Mac. The desktop app is currently available for macOS only, with no infrastructure to stand up first.
Install it on your own machine so the model, the database, and the network boundary all stay yours.
Everything below is read from the running 1.19.0 source rather than from a roadmap. Where a feature is optional or off by default, this site says so.
Chat is the entry point, not the whole product. The same conversation can hand a goal to an autonomous task, ground an answer in sources you supply, or return a reviewable artifact instead of a wall of text.
One local model answers each request. Response style and mode stay visible controls, not hidden presets.
When the opt-in task sandbox is enabled, multi-turn runs use a Docker workspace with shell, Python, browser, and file tools. Desktop local work uses a separate, confirmation-gated bridge.
Decompose the question, gather sources, cross-check them, then write a report that keeps its citations.
Governed tool servers, and results you can open, re-run, and share instead of scrolling back through a thread.
Chat with OpenMake from Discord through an optional gateway bot. Messages relay to the OpenAI-compatible API, with per-user sessions and role- or mention-based access control.
OpenMake does not fan every message out to a panel of specialist agents. The default route resolves one model and runs the regular chat/tool loop. Turn on Discussion when the question benefits from independent specialist views and an explicit synthesis pass.
This is MoA-style orchestration in a bounded mode: the system selects a panel, gives each expert the same evidence package and context priorities, then compares the work before composing the answer. The progress events are visible in the chat instead of hiding the pipeline behind a spinner.
The topic is matched to two or more related agents. The panel can use the conversation, documents, web context, and image descriptions without giving every agent every credential.
Within each round, independent expert opinions run through a bounded parallel batch. A failed opinion is retried selectively; a partial result is not presented as a full panel.
A cross-review pass identifies strengths, shared claims, and conflicts. When enabled, the same evidence package is collected before the opinions so every expert reasons from the same sources.
The composer receives the opinions, review, evidence, and consistency signals, then returns one answer with participants, sources, and degraded-state truth when the panel shrinks.
With a local default endpoint configured, the standard answer path stays inside your gateway. When a job genuinely needs a different model, register a key and assign it to a single functional role — agent, judge, research, spawn, review, or summary — instead of switching the whole workspace over.
Resolution is fail-open. A per-user mapping wins first, then the admin-set global default, then the environment default, then the local qwen3.6-35b-a3b. If an external call fails, the local model still answers.
The reference deployment runs the application on a single host. PostgreSQL is required, Redis is optional for shared multi-instance storage, and Docker is used when you enable the task, MCP, or artifact isolation services.
Access is governed by JWT authentication and role-based permissions, privileged actions are written to the audit log, and the audit log is wired to alerts.
OpenMake is not a company. It is a team of people who enjoy open source and open hardware, sharing what they build and keeping the habit of running their own machines alive. That same spirit now guides the openmake_llm project.
rasplay.org opens as a maker community, alongside a printed Raspberry Pi practical guide.
People who enjoy open-source software and open hardware gather at openmake.cc as a team, not a company.
Registered with the Raspberry Pi Foundation as Korea's official Raspberry Pi JAM.
The team's open-source, local-first AI workspace, currently at OpenMake 1.19.0.
The demo is the fastest way to form an opinion. The installation guide is the shortest route to an environment you own. The release notes are where you check what changed before you upgrade.
OpenMake