Live demo

See the product before you install anything

A running BareBones Ticketing 1.1.0 with a fictitious manufacturer's service desk already in it. No download, no form, no email address. Two minutes from here to a live queue.

Just open the demo

Start here

One login gets you in

Username: demo.agent.6ad4d2

Password: Demo-326361-1AE32E39!Aa1

The green button copies the username and opens the demo in a new tab; this page stays here with the password. Same password for every account on this page.

Once you are in

Three things worth seeing

You land on the agent queue. Together these take about two minutes and show what the product decides on your behalf.

Open the breached ticket in the At Risk lane.
Follow the SLA clock on the ticket, including where a hold pauses it and who is on the hook. That clock is the audit trail you did not have to assemble.
Sign out, sign back in as demo.manager.6ad4d2.
Same queue, wider lens: work an agent cannot close alone, and approvals waiting on a named person. Then try demo.observer.6ad4d2 to see how little a confined account gets.
Open the admin workspace as the agent's manager.
Departments, catalog, workflows, SLAs. Notice how little ceremony it takes to change something, and that every change is recorded.

Other roles

Nine ways to look at the same desk

Each account lands in its own workspace, which is the point: the product decides what each person sees, not a setting someone has to remember to apply. Pick whichever view resembles your operation. Same password every time.

Role	Username	What you see
Service agent	`demo.agent.6ad4d2`	The richest starting point: an active queue, SLA lanes, and the work in flight.
Support manager	`demo.manager.6ad4d2`	The same queue through a wider lens, including work an agent cannot close alone.
Ordinary requester	`demo.requester.6ad4d2`	The asking side: submit a request, then watch it from a requester's limited view.
Operations requester	`demo.ops.requester.6ad4d2`	A heavier catalog user, for how intake feels when someone files often.
Project manager	`demo.pm.6ad4d2`	Where tickets meet project-linked work rather than living on their own.
People operations	`demo.people.6ad4d2`	A newly onboarded department still finding its shape.
Compliance approver	`demo.approver.6ad4d2`	The approval path from the side that has to say yes, and be recorded doing it.
No department access	`demo.observer.6ad4d2`	A real account that can barely see anything. Confinement from the inside.

Password for all of them: Demo-326361-1AE32E39!Aa1 — open the demo sign-in.

Outside the organization

See the same ticket as an outside vendor

Worth doing right after the agent view, so you see both sides of the same conversation.

Casey Vendor

Sign-in page: demo.finlay.works/external/login

Invitation email: casey.vendor.6ad4d2@aster-bay.example.test

Same password again.

What she can and cannot see

Casey is not an Aster Bay employee. She was invited onto one ticket, and that is the entire extent of her access.

No queue, no service catalog, no other customers; just her ticket.
Her own entrance, separate from the staff sign-in.
External participants never count against your worker limit.

Plainly

What this demo is and is not

It resets every night

Everything you do here is wiped daily and the scenario is restored. Break it, file nonsense, delete things; that is what it is for.

Everything in it is invented

Aster Bay, its people, and its tickets are fictitious. No real customer data has ever been in this instance, and none should be entered into it. It cannot send email.

It runs the shipping build

This is the same 1.1.0 general-release package customers download, installed the documented way and upgraded the documented way. What you see here is what you get, not a mockup or a marketing build.

The 1.1.0 release has a validation package

The published 1.1.0 release has an executed validation package designated by the validation team, written for QA and compliance readers. Professional and Lifetime customers download it from their account; it does not replace validation of their own installation and intended use.

What it is and is not

Seen enough?

BareBones is self-hosted, so your data stays behind your firewall. Trial and Free Edition run on your own hardware, and the packages are ready to download once you have a key. If you would rather have a written assessment against your own operation first, ask for one and you will get a straight answer.

Get a trial or Free Edition key Request a written fit assessment