How Quevell began
Quevell grew out of 19 years of practical work with corporate IT systems.
Quevell's founder progressed from systems administrator to head of corporate IT at an international fintech company. Most recently, he was responsible for a team of 15 specialists, around 50 services and 130 integrations supporting 1500 employees in 30 countries.
That experience showed that adopting a tool is only the beginning. It also needs ongoing support, changes, access control, a record of decisions and continuity of service.
This was particularly clear in issue and project management systems. Years of operating, administering and migrating them shaped the principles that would guide Quevell.
This led to Quevell.
Principles behind the product
Changes must remain transparent. Workflows keep a history of published revisions. Issue history and the company audit trail show what happened, when and who initiated it.
Access rights must be manageable. Access is governed by roles and security settings. Administrator rights can be requested for a limited period and expire automatically when that period ends.
Automation must be predictable. Rules can be checked against real data without saving changes. The result shows which actions would have been carried out.
The company owns its data. Quevell supports exporting issues, attachments and knowledge pages in open formats.
These principles are part of the product architecture and guide its future development.
Development approach
Changes to Quevell must pass several levels of verification.
Every change goes through automated tests and checks. Before release, the new version is deployed to a separate staging environment. The release mechanism blocks any commit that has not completed the required verification process.
Regular checks also cover security, the interface and whether the documentation matches the implementation. Problems are recorded for review. Automated checks do not make fixes without a separate decision.
Architectural decisions are documented with their rationale, so the reasons remain available and decisions can be reconsidered without losing their history.
Quevell's founder is responsible for product development, technical decisions and acceptance of changes.
Company and accountability
Quevell is provided by Quevell, LLC. The product infrastructure is hosted in a Russian data centre.
Terms of service, personal data processing practices and supplier information are published on this site.
For product and collaboration inquiries: hello@quevell.com.
Try it with your own work
30 calendar days, up to 10 seats, the full product.