Launch Release - Dark Edition - Self-Hosted by Default

Deploy an embeddable
private AI application
that grows through plugins.

GotChat packages chat_js into a website-ready product: native embedding, self-hosted chat, model orchestration, plugin-driven tools, shared sessions, and reusable workflows in one deployable platform.

Local
Runs on your hardware
Multi-user
Built for shared workspaces
Extensible
Plugins, flows, and model routing

Why this launch matters

It is not just another chat box. It is a productized local AI workspace teams can actually deploy, operate, and extend.

Private by architecture

Keep models, prompts, files, and workflows on your side

Run against local llama.cpp servers, embedded runtimes, or your own controlled endpoints. The system is built for people who want AI capability without surrendering operational control.

Built to extend

Turn chat into a working system with plugins and agent flows

Attach tools, route tasks, automate repeatable work, and layer structured workflows on top of conversations instead of treating AI as a one-off prompt surface.

Shared workspace

Support members, sessions, and collaborative usage

Let people sign up, join projects, work inside shared sessions, and operate from one interface while still keeping the deployment under your control.

Operator-friendly

Manage models, routes, plugins, and runtime behavior from one place

Model deck controls, plugin management, AI routing, and runtime integration give operators visibility instead of hiding the moving parts behind a black box.

What GotChat does on day one

These are the product launch strengths worth leading with for chat_js.

Unified AI workspace

  • Chat with local or self-hosted models from one interface
  • Work across text, vision, image, and workflow-assisted tasks
  • Keep session context organized for real ongoing work

Operational control

  • Choose runtimes, GPU strategy, routing, and model behavior
  • Manage plugins and feature surfaces without rebuilding the app
  • Run in Docker or local environments depending on your setup

Workflows that go beyond chat

  • Use agent flows for multi-step tasks and tool orchestration
  • Route work to the right model instead of forcing one model to do everything
  • Support repeatable processes for teams, labs, and internal ops

What you need to run it

The launch message should be simple: start small, scale into stronger hardware when your workload grows.

Minimum path

Modern browser, a machine that can run the app stack, and either Docker or a local Python environment.

Recommended path

16–32 GB RAM, local storage for models, and a dedicated GPU if you want stronger local inference and media workloads.

Operator path

One machine for the workspace, optional host-managed llama.cpp servers, and room to add plugins, workflows, and team accounts over time.

Quick start shape Docker or local
1. Create a member account
2. Deploy the app stack
3. Connect your local or managed model runtime
4. Turn on the plugins and flows you need
5. Start using shared AI sessions immediately

Where this solution fits

Lead with concrete situations where a self-hosted AI workspace removes friction that hosted tools create.

Teams that need privacy without losing usability

Use GotChat when public SaaS AI feels operationally risky, but your team still needs a modern chat workspace they can adopt quickly.

Builders who want one product instead of five disconnected tools

Combine chat, local runtimes, plugins, workflows, and session management instead of stitching separate dashboards together.

Internal copilots for labs, startups, and departments

Launch a shared AI environment for support, research, operations, or product teams without sending sensitive work outside your stack.

Open-source contributors and self-hosters

Fork it, patch it, run it locally, and make the product yours. The value is not only the UI. It is the ability to operate and evolve the system directly.

Open source launch

Ship with a signup flow. Grow with the source.

This launch page is designed to convert visitors into members first, then pull serious operators and contributors into the repository. That is the right product launch motion for chat_js: get people into the product fast, and give technical users a clear path to inspect and extend it.

Get started now

Bring your members into a real self-hosted AI product.

Sign up, deploy, connect your models, and start using GotChat as a working AI workspace instead of a demo.