Who it is forA developer or IT owner at a marketing team that wants citation evidence kept on infrastructure it controls.
The problemMarketing teams need evidence of AI citations for stakeholders, and they want that record hosted and governed in-house.
The outcomeA self-hosted Cited instance with an owner account, a health check, and a documented path for exports and notifications.
What you need first
- Docker Compose v2
- Node.js 22 or newer
- About 4 GB RAM recommended
- A domain and brand you want to monitor
- DataForSEO API credentials, only if you want live monitoring instead of mock mode
Steps
- Run
npm ci - Run
npm run self-host:up - Run
npm run self-host:token, then open /setup to create the first owner - Run
npm run self-host:doctorto confirm the installation is healthy - Read docs/security/ before inviting others, then stop safely with
npm run self-host:downwhen not in use
Prompt for your agent
In the cited-cc/cited repo, self-host Cited with Docker Compose, run the doctor command, and report the health output and the default URL. Verify that the secrets directory .cited/secrets/ exists and that no secret values were printed to the output.
Caveat. The README says Cited is not claimed to be penetration-tested or certified for regulated compliance frameworks, so review the security guides before using it for sensitive data.
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page