Bug tracking built for agencies managing client projects
One install. A separate project per client. Read-only client access included. Self-hosted so your clients' data stays on your server — no SaaS middleman. Free with no seat limits.
How agencies use BugTrack
One project per client
Create a project for each client. Bugs, comments, and screenshots stay isolated — a team member added to Client A can't see Client B's work.
Client viewer access
Add clients as viewer accounts on their project. They can see all bugs and comments, filter by status, and read the full history — but can't modify anything.
Data stays on your server
Self-hosted means your clients' bug reports never touch a third-party server. Useful under NDA, in regulated industries, or when clients simply expect their data to stay in-house.
Screenshot attachments
Paste screenshots directly into bug reports and comments. Visual bugs get reported with context — no more "here's a bug" with no image.
Slack per project
Each project gets its own Slack webhook. Route Client A's bug notifications to one channel and Client B's to another — or keep everything in one place.
No seat costs
Adding a new client viewer costs nothing. BugTrack is free with no user limits — so onboarding a new client doesn't mean a larger bill.
How it works for a typical agency setup
- Install BugTrack on your own VPS or shared hosting — takes about 15 minutes.
- Create a project for each client engagement.
- Add your developers as members on the relevant projects.
- Create a viewer account for each client contact and add them to their project.
- Developers report and manage bugs. Clients log in to see progress without being able to interfere.
- Configure a Slack webhook per project if your team tracks work in Slack.
Clients see only their own project's bugs. They can filter by status, priority, and assignee, and read every comment thread — but the viewer role blocks writing, so the bug list stays clean and managed by your team.
Frequently asked questions
Can clients see only their own project?
Yes. Users only see projects they've been explicitly added to. Give each client a viewer account and add them to their project only — they'll never see other clients' work.
Can clients file bugs themselves?
Not with a viewer account — viewers are read-only. If you want clients to file bugs, give them a member role on their project. Members can report bugs and add comments but cannot manage the project or other members.
Does it cost more per client?
No. BugTrack is free with no seat limits. Adding a client viewer account costs nothing.
Where does client data go?
On your server. BugTrack is self-hosted — client bug reports and comments stay on the machine you control, not a third-party cloud.
What if a client engagement ends?
Archive or delete the project and remove the client's account. All data stays on your server — you control retention.