Annict (アニクト) is an AGPL-3.0 licensed, Go-based anime viewing-record and social networking platform, published as the annict/annict repository and operated in production at annict.com, built for anime watchers who want to find the next title to watch and for the developers who run or contribute to an instance.

What it is

Annict is the open-source codebase behind the hosted service at annict.com. The repository describes itself in one line as "a platform for anime addicts," and its Japanese README expands that into a viewing-record service whose purpose is discovering the next work a user wants to watch (次に観たい作品が見つかるアニメ視聴記録サービス). The registry files it under Community & Social / Social Networking, with a topic list of anime, annict, go, golang and social-network, and Go as the declared primary language. Two separate continuous integration workflows appear in the README badges, go-ci.yml and rails-ci.yml, which indicates that the running system is more than a single Go binary and includes a Rails component alongside the Go application.

The concrete problem it addresses is fragmented viewing history and discovery. A viewer following several seasonal series needs one place to record what has been watched, and one place to look for what comes next, with a social layer that connects that record to other watchers rather than to a closed, single-provider tracker. Because the software is published under AGPL-3.0 with source available, the same application that powers the hosted instance can be read, forked and run by someone else, so the record and the community around it are not tied to one operator's discretion.

Key capabilities

• Viewing-record and discovery service built around the promise of finding the next title to watch, as stated in the Japanese README.
• Go application with a dedicated GitHub Actions workflow, go-ci.yml, for continuous integration.
• Separate Rails continuous integration workflow, rails-ci.yml, showing a Rails component in the same system.
• Distribution under the AGPL-3.0 licence, with the source hosted publicly.
• Bilingual documentation, with a Japanese README as primary and a README.en.md English translation.
• Contribution and vulnerability processes defined in CONTRIBUTING.md and SECURITY.md respectively.
• Community channels beyond the repository: a Discord server and a community wiki hosted at wikino.app.

Who uses it and how

• Anime watchers using the hosted instance at annict.com to log viewing history and browse for titles to watch next.
• Operators who take the repository and run their own instance of the Go application plus its Rails component.
• Contributors who work through the guidance in CONTRIBUTING.md and rely on the two Actions workflows for checks.
• Community members who coordinate outside GitHub, on the Discord server and on the wikino.app community pages.
• Security reporters, who are directed by SECURITY.md to a defined disclosure path instead of public issues.
• The project's visible scale is modest: 780 stars, 97 forks and 203 open issues at the time recorded.

Getting started

The README excerpt offers the hosted route directly, at https://annict.com/, rather than a package name, Docker image or compose file. It gives no install or run commands, so anyone deploying an instance should treat CONTRIBUTING.md as the entry point for setting up a development or contributor environment.

How it compares

The facts provide no list of paid products this project replaces, and name no comparable tools in the same space. On the evidence available, Annict stands alone in this registry.

When to use it — and when not to

A self-hoster takes on both the Go application and the Rails component, since both appear in the project's own integration workflows, and the README excerpt does not enumerate the backing services such as database, storage or mail that an operator must supply, so those requirements need checking before any deployment is planned. The documentation is Japanese-first, with English available only as a translation, and 203 open issues suggest a backlog that a new operator or contributor will inherit. Anyone wanting a fully managed product with no operational surface, or a project with small, clearly documented deployment requirements, should look elsewhere.