Projects, helpdesk, knowledge base, time and CRM, hosted or on your own servers

All your work in one place.

Alba Ticket runs your helpdesk and your software projects side by side: a customer portal, queues and SLAs for support, boards and sprints for delivery, and workflows you shape to the way your team already works. Every hour of it is tracked against the customer's contract, so the same data shows what a project cost and makes the invoice, the documentation lives beside the tickets it explains, and the customers you serve are the contacts and companies of a CRM, with the deals, the email and the meetings on one timeline. Use it in our cloud or run it yourself.

Start a hosted workspace Install it yourself See the five modules Cloud or self-hosted Talk to us

Already have a workspace? Open it at your-team.albaticket.com.

Try it first

The demo workspace has a software project with boards and sprints, an IT helpdesk with queues, SLAs, a customer portal and help articles, and a knowledge base with a company handbook. Change whatever you like: it is reset to the sample data every hour. Everything is switched on there, the API and the MCP server too; only connecting an account of your own elsewhere (a calendar, a mailbox, a repository) is left for a workspace of your own.

Workspace
demo.albaticket.com
Agent login
demo@example.com
Customer login
customer@example.com
Password
try-alba-ticket
Open the demo

Five modules, one set of data

A CRM, projects, a helpdesk, a knowledge base and time tracking work on the same tickets, people and customers, so nothing is copied between tools. Every workspace has all five, at one price per seat; nothing is held back for a bigger plan. An administrator chooses which modules and features the team uses, and switches the rest off.

CRM

The people and companies you deal with, the deals you are working, and everything said and done with each, on the records the helpdesk and the invoices already use.

  • Contacts and companies, shared with the helpdesk and invoicing
  • A sales pipeline on a board, with quotes and a weighted forecast
  • Calls, meetings, email and follow-ups on one timeline
  • Consent, export and erasure for every contact
More about crm

Projects

Tickets that move through workflows you define, with every change recorded, and the boards and sprints to plan and run the work. The module every team uses.

  • Workflows with conditions, validators and post functions
  • Kanban and scrum boards, a ranked backlog, burndown and velocity
  • Epics, sub-tasks, links, versions, components and custom fields
  • Commits and pull requests from GitHub and GitLab on the ticket
More about projects

Helpdesk

A service desk customers can use: a portal, request types, forms on your own website, queues, internal notes, SLAs and approvals. Customers are never a seat.

  • A customer portal with help articles that answer before they ask
  • Public request forms for people with no account
  • Queues in JQL and internal notes customers never see
  • SLA clocks that count working hours, with goals per customer
More about helpdesk

Knowledge base

Spaces of Markdown pages for the workspace and every project, every version kept, linked both ways with the tickets, and kept in step with a Git repository.

  • Workspace, project and personal spaces with a page tree
  • Every version kept, compared and restored; comments on a passage
  • Pages and tickets linked both ways, help articles for customers
  • Docs from Git, and Confluence or any tool imported whole
More about knowledge base

Time

Every hour tracked against a customer's contract, whatever it was spent on, so the same data shows what work took and cost and makes the invoice.

  • Activities on a ticket, a project, a customer or free-form
  • Contracts with rates, phases with a budget of days, cost rates
  • Effort and cost by project, epic, ticket, queue or member
  • PDF invoices from the hours, with tax and category breakdowns
More about time

In every module

What the five share: configuration rather than code, and the things that make a tool quick to use all day.

Shaped to the way you work

Configuration, not code, and different for every project if it needs to be.

Workflows you define

Statuses, transitions, conditions, validators and post functions. Each project and ticket type can work its own way.

Custom fields

Typed fields scoped to the projects and ticket types that need them, on the form, the ticket and in search.

Permissions and security levels

Project roles, groups and per-ticket security levels decide who sees what. Every change to a ticket is kept in its history, field by field.

On every page

What makes it quick to use all day.

Live, without the noise

A change one person makes appears for everyone looking at the same ticket, queue or board, without a refresh. Watch what matters: updates arrive in the app as they happen and by email as one digest, not a message per change.

Find it from the keyboard

Quick search from any page and typo-tolerant full-text search, showing only what you are allowed to see. Shortcuts for moving, creating, assigning and commenting, and Markdown everywhere people write.

Your identity provider

Login links and passwords for individuals, OpenID Connect single sign-on per organisation, and registration that can be open, by invitation or SSO only.

Our cloud or your servers

Some teams want nothing to run. Others have a data policy that says where tickets, customer details and attachments may live. Alba Ticket is the same software either way, and a workspace can move between the two whenever your policy changes. How the two compare, in detail: who holds the data, who does the work, and what a data policy makes of each.

Hosted by us

A workspace at your own address in a couple of minutes, with upgrades, backups and search looked after for you.

  • Your data is isolated from every other workspace in the database itself
  • Delete the workspace and nothing of it is left behind
  • Export everything, attachments included, at any time
Start a hosted workspace

Self-hosted

One container image and a compose file, on your own hardware or your own cloud account, behind your own firewall if that is what the policy asks for.

  • Tickets in your PostgreSQL, attachments in your S3-compatible bucket
  • Pages load no fonts, scripts or trackers from anyone else
  • Stateless nodes that cluster when one server is not enough
  • A licence key checked on your server, with no call home
Read the installation guide Get a trial or licence key

Moving between them is one file: export the workspace from one and import it into the other, with every ticket, its history and its attachments.

Not sure which your policy allows, or what running it yourself would take? Ask us.

Why teams pick Alba Ticket

One tool, not two
Support and engineering work in the same place, so a customer request can be linked to the bug that fixes it and both sides can see where it stands.
Your data stays yours
Choose where it lives, take all of it with you in an open format, and know that deleting it really deletes it.
It fits the way you work
Workflows, fields, ticket types, roles and boards are yours to define, per project, without writing code or buying a plugin.
Fast enough to stay out of the way
Pages arrive rendered and update themselves. Nobody waits for a spinner to read a ticket.
One entry, everywhere it counts
The hour you log on a request is an activity on the ticket, an hour on the customer's contract and a line on the invoice, all at once. The same contract sets the customer's response times, and the home page puts the request nearest its target first.
Documentation beside the work
The runbook, the decision and the how-to sit next to the tickets they explain, found by the same search and linked from the same pages, so nobody keeps a second wiki in step with the tracker.
Nothing is ever lost
Every change is recorded with who made it and what it was before. Deleted tickets are archived and keys are never reused.
Private by design
Attachments go straight from the browser to storage, secrets are encrypted in the database, and the application carries no third-party trackers.

Bring your history with you

Leaving Atlassian? Alba Ticket reads a full Jira backup, from Server, Data Center or Cloud, and keeps every key, comment, custom field, workflow and attachment; and it reads your Confluence spaces whole, every page in every version with its comments, files, restrictions and old addresses. The people in both are matched, so the author of a page and the reporter of a ticket are one person here. Each import reports how everything maps before it writes anything, and can be run again safely until its verification matches.

Documentation from Notion, Obsidian, GitBook, Outline, MkDocs, Docusaurus or any folder of Markdown or HTML comes across from a ZIP, in the tree it had and with its links and images working.

From GitHub or GitLab, a repository's issues with their comments and history, read with a token you give. From anywhere else, a CSV file: Trello, Asana, Linear, Zendesk or a spreadsheet, one file into one project, with the columns mapped on screen.

Your time comes too: an Elastic Time account whole from its export, and Toggl Track, Clockify, Harvest, Timely or any tracker's CSV of entries, with the time zone chosen and duplicates skipped.

How the import works Moving from Confluence Ask about your migration
  1. 1

    Analyse

    Counts, mappings and anything that needs a decision, from the export alone.

  2. 2

    Dry run

    The full import inside a transaction that rolls back, so you see the review items first.

  3. 3

    Import and verify

    Users, projects, workflows, tickets, attachments, boards and sprints, then a count-by-count comparison.

Work with your AI agents

Connect Claude, ChatGPT, Cursor or VS Code and ask for what you want in your own words: they find, read, create, move and plan tickets through the workspace's MCP server. Your own scripts get the same through a REST API with an OpenAPI description.

  • An agent acts as the person who connected it, with their permissions and nothing more
  • They choose read only, or read and change, and can disconnect it at any time
  • Every change it makes is in the ticket's history, with its name beside theirs
  • Off until an administrator switches it on: the MCP server and the REST API each have their own switch
  • Nothing is sent to an AI provider by Alba Ticket itself: an agent reads only what it asks for
  • Hosted and self-hosted alike, with nothing extra to buy
Connect an agent API documentation

Things to ask an agent

“Which open bugs in WEB are assigned to me?”

“Summarise HELP-88 and add a draft reply as an internal note.”

“Move WEB-142 to In Review and tell Grace it is ready.”

“Put the top five backlog tickets into Sprint 15.”

“Log an hour on WEB-142 for the review. How many hours went to ACME this week?”

Claude Code, in one line

claude mcp add --transport http alba https://your-workspace/mcp

Start with a workspace, or with your own server.

A workspace takes a couple of minutes and asks for no card. An installation is one container image and a compose file.

Start a hosted workspace Open the demo Install it yourself See the pricing Talk to us