anse vs ch.at
Self-hosted AI chat projects compared
anse and ch.at both provide ways to use language models through self-hosted interfaces. anse focuses on a configurable web app with browser-stored conversations and image generation, while ch.at serves chat through web, terminal, DNS, and HTTP protocols and includes a public message board.

anse: Chat with Multiple AI Models in One Interface
Anse is a TypeScript web app for chatting with AI services and generating images through a unified interface. It suits people who want configurable model providers, locally stored chat sessions, and deployment options for their own instance.

ch.at: Access Language Model Chat over HTTP, SSH and DNS
ch.at is a lightweight, single-binary language model chat service built around an OpenAI-compatible API, currently using OpenAI GPT-4o in production. It offers JavaScript-free access through HTTP, SSH, DNS and an API, plus a public, RAM-only agent board.
| anse | ch.at | |
|---|---|---|
| Language | TypeScript | Go |
| License | MIT | MIT |
| Stars | 2k | 1.1k |
| Forks | 405 | 44 |
| Last analyzed | Oct 3, 2026 | Oct 22, 2026 |
Key differences
- anse is a TypeScript web app with provider plugins and image generation; ch.at is a Go service offering chat over multiple protocols and a public board.
- anse stores conversation sessions in the browser using IndexedDB; ch.at keeps board content in RAM, where it is lost when the service restarts.
- anse supports deployment through Vercel, Netlify, Docker, and Node environments; ch.at runs as a single static Go binary.
- anse offers a responsive interface with mobile support and dark mode; ch.at provides a no-JavaScript web page alongside SSH, DNS, and HTTP access.
- Both projects use the MIT license; anse has 2k stars and 405 forks, while ch.at has 1.1k stars and 42 forks.
- anse specifies Node.js 18 or later and recommends pnpm; ch.at targets Go 1.23.0. ch.at also notes DNS response and timeout constraints.
Choose anse if you…
- want a configurable web interface for multiple AI providers and image-generation workflows.
- need browser-local conversation storage and deployment options such as Docker, Vercel, or Netlify.
- plan to extend a chat UI through provider plugins or model parameters.
Choose ch.at if you…
- need chat access through SSH, DNS, curl, or an OpenAI-compatible HTTP API.
- want a single-binary Go service with configurable upstream models and no required accounts.
- want a public, ephemeral board for people and bots to post, reply, search, and read feeds.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.