The tool we always wanted.
So we built it.
Quevell is built from six years inside heavyweight trackers: running real projects, administering them, and keeping a list of everything that slowed people down, got in the way, or quietly disrespected their work.
Quevell is the tool without that list.
Principles
Opinions we hold, written into the product
Every one of these came from a real scar. None of them is marketing first.
Fast is a feature
A tracker is opened hundreds of times a day. Every screen renders instantly, every list answers at once, with no loaders standing where your work should be.
Your data answers to you
Every successful change is recorded: who, what, the values before and after. Deactivating a person shows the full impact before anything moves; nothing is ever silently orphaned.
Your data is actually yours
A complete export in open formats is available at any moment: a standard capability, not a negotiation with support. For backups, your own reporting, or simple peace of mind, you always have first-class access to everything you’ve put in.
The work
Built and working today
Not a roadmap, the part you can touch. Every card below is covered by tests, not by intentions.
Workflows with a memory
Edit a live workflow safely: every publication is an immutable revision with an author and a timestamp. Restoring the past is a new reviewed publication, never a quiet rewrite of evidence.
Every change on the record
Who, what, the values before and after, recorded at the substrate level, not bolted on. When someone asks “who moved this and why”, the answer is one query away.
A query language, not a search box
QQL: typed fields, =, in, ~, AND, ORDER BY. Instantly recognisable if you come from Jira. Queries bind to stable IDs, so renaming a field or a status never breaks one.
Administration is borrowed, not held
Admin rights are granted for a reason and a window, approved by a permanent administrator, logged, and self-expiring. No more “why does John still have full access”, because John never had it permanently.
Visibility that narrows, never widens
Issue-level security overlays project permissions and can only restrict. No configuration mistake can accidentally show an issue to someone the project wouldn’t.
Notifications people don’t mute
Tenant-authored rules decide who hears about what: typed events, role recipients, project narrowing, personal declines. Less noise is a feature.
Tell us about your team
We are onboarding early teams now. Write a few lines about how you work and which tool you are moving from. The founder reads every letter. There is no support tier between you and the person who builds this.
hello@quevell.com