The product
BareBones Ticketing is the product. Everything else on this site exists to help you evaluate it, adopt it, and run it yourself.
Finlay.works
Service management software, written plainly.
Finlay.works makes BareBones Ticketing: a self-hosted service desk for teams that have to show, later, who approved what. Structured intake, owned tickets, controlled workflows, and an audit trail you did not have to assemble, on servers you own. For each release the validation team designates a separate validation package, written for QA and compliance readers; Professional and Lifetime customers download it from their account.
What you get
- Self-hosted packages for Windows Server and Linux Docker Compose; your servers, your data.
- An executed validation package designated for each release, in the account for Professional and Lifetime.
- A live demo, an open manual, and a 60-day no-card trial before anyone asks you for money.
Best first step
Open the live demo or read the manual. Questions go in writing. Replies are written and asynchronous; allow several business days.
Validation package
Each release carries an executed validation package, designated by the validation team; Professional and Lifetime include it as an account download.
Help, in writing
Fit questions and implementation help are handled in writing, at the pace of a small vendor. Replies are written and asynchronous; allow several business days.
Product focus
BareBones Ticketing
Requests in a group mailbox and a tracking spreadsheet work — until someone has to show who approved what. BareBones Ticketing replaces that with structured intake, tickets that have owners, workflows you control, and evidence that builds itself, running on servers you own.
Each release carries an executed validation package, designated by the validation team; Professional and Lifetime include it as an account download.
Self-hosted control surface
Queue signals, access posture, workflow context, and audit-minded operations.
Choose a path
Find the right starting point quickly
See it running, read how it works, compare it against your operating problem, or ask in writing.
Evaluating governed ticketing?
BareBones Ticketing is the flagship Finlay.works product for self-hosted service desk control.
View BareBonesWant to see it running first?
A live demo with a worked service desk in it: sign in as any of nine roles. No install, no form, resets nightly.
Try the demoComparing service desk options?
Start with the operating problem: self-hosting, access scope, workflow control, evidence, and buyer readiness.
Read the buyer guideHave a question before you buy?
Send the service desk problem in writing. Replies are written and asynchronous; allow several business days. Implementation help is scoped the same way.
Ask in writingRelated services
Service management implementation support
Finlay.works helps teams evaluate, plan, configure, and document self-hosted service desk work around BareBones Ticketing.
BareBones fit assessment
Help deciding whether BareBones Ticketing fits the way your team handles service work.
- Current request paths and ticketing pain
- Self-hosting and operating constraints
- Requester, agent, admin, and external participant needs
- Workflow, SLA, approval, and audit questions
- Clear proceed, pilot, defer, or fit-check recommendation
Implementation support
Help shaping the first useful operating path around BareBones.
- Service catalog and intake structure
- Workflow, status, and SLA configuration planning
- Department-scoped access and role mapping
- Launch checklist and operating handoff
- Narrow import, integration, or reporting support when scoped
Documentation and continuity
Readable records so service teams can operate and hand off the system without guesswork.
- Service desk operating notes
- Requester, agent, and administrator guidance
- Decision logs and change records
- Access and support-boundary documentation
- Handover notes for maintainers and future staff
How work runs
Structured, written, predictable
The process is designed to reduce human variability. Scope, decisions, and delivery notes are written and shared in plain language.
Scope boundaries
- Projects are defined in writing before work starts.
- Changes are reviewed and re-scoped before implementation.
- No hidden recurring costs or surprise renewals.
- Work begins only after scope and estimate are approved in writing.
-
Written brief
You send a short written brief with goals, constraints, and stakeholders.
-
Scope and estimate
We reply with written scope direction, useful questions, or a next-step estimate.
-
Build and review
Work proceeds in small, documented checkpoints with written updates.
-
Handover
You receive documentation, credentials, and a clean wrap-up summary.
Values
Values, practiced without pressure
Our values shape the way we work. The goal is honest service, careful stewardship, and respect for people—without pressure or manipulation.
If a request is unsafe, dishonest, or likely to cause harm, we will decline it plainly.
Read the full values statementHonesty
Truthful estimates, transparent tradeoffs, and clear explanations even when the answer is no.
Stewardship
Responsible use of time, budget, and technology with long-term care in mind.
Care for people
Respect for users, teams, and stakeholders, including their limits and their time.
Integrity in delivery
Work that can be maintained, documented, and handed over with confidence.
Contact
Start with a written brief
Send the service management context once, in writing. A few paragraphs are enough to start a BareBones fit, service, proof, or procurement conversation.
What to include
- How service requests, tickets, approvals, or handoffs work today.
- Who needs a lane: requesters, agents, administrators, approvers, auditors, or outside participants.
- Known constraints: self-hosting, timeline, budget range, workflow, access, audit, or compliance pressure.
- Any existing documentation and a description of current systems (do not send passwords).