Your company's brain — but you own it.
Sign in with Google. Connect your Gmail, Drive, Slack, and GitHub.
Ask any question — townsquare answers it across your whole company,
with each person's data queried under their own credentials.
You: "What's the status of the Q3 launch?"
townsquare:
→ fans out to Bob, Carol, and Dan (they're in #q3-launch + the recurring meeting)
→ each query runs under that person's own Google + Slack creds
→ 4.2 seconds later
Beta freeze is set for May 14 [via bob@acme.com · calendar].
Carol's design doc passed legal review on Apr 28 [via carol@acme.com · drive].
Dan flagged an open auth bug yesterday in #q3-launch [via dan@acme.com · slack].
Carol's draft job-offer email never reaches the central agent. Slack DMs Bob isn't in stay invisible. Privacy is enforced at the source, not bolted on after.
- Your infrastructure, your data. Self-host with one
make up. The only outbound calls are to your chosen LLM and the data sources each user connected — nothing else. No telemetry. No phone-home. - Per-user, not per-bot. Most "company brain" tools install one Slack bot that sees everything the bot is invited to. townsquare uses each employee's own OAuth. Removable, auditable, scoped.
- Apache 2.0, no strings. Fork it, run it, sell it. No commercial restrictions.
git clone https://github.com/townsquare-os/townsquare
cd townsquare
cp example.env .env
make gen-secrets # paste FERNET_KEY + SECRET_KEY into .env
# fill GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, WORKSPACE_DOMAIN, ANTHROPIC_API_KEY
make up
open http://localhost:8000That's the whole installation. The full step-by-step (Google OAuth setup, TLS, first admin) is in docs/SELF_HOSTING.md.
| Source | How it connects | Privacy unit |
|---|---|---|
| Gmail | granted at SSO | per-user |
| Google Drive | granted at SSO | per-user |
| Google Calendar | granted at SSO | per-user |
| Slack | per-user OAuth (xoxp, not bot) | per-user |
| GitHub | per-user fine-grained PAT | per-user |
| Notion · Linear · Jira | coming in v0.2 | per-user |
| Self-host in 30 min | The end-to-end setup guide |
| Google OAuth setup | The fiddly bit, broken down |
| Operations | Backups, upgrades, secret rotation |
| Troubleshooting | Common failure modes |
| SPEC.md | RFC-2119 spec — implement townsquare in any language |
| Roadmap | What's coming next |
| Contributing | The contract every connector must satisfy |
| Security | Reporting vulnerabilities, supported versions |
Python · FastAPI · Postgres · HTMX · Tailwind · Anthropic Claude · Authlib · cryptography.fernet
Apache 2.0 — free for any use, including commercial.
Built by Swathi, released as OSS so any company can run their own.
If townsquare helps you — ⭐ the repo. It's the only signal we get.