The operational PSA for MSPs, system integrators and IT teams

From request to report. One connected flow.

Krato is a PSA (Professional Service Automation) platform that brings tickets, projects, hours and reports into one tracked flow. Share what matters with clients and partners while keeping control of access and expiry.

  • Work and ownership in one place
  • Focused access with an expiry
  • Every step stays traceable

Data sovereignty

Your data stays yours, even when you share it.

With Krato, sharing does not mean surrendering control. Choose what people can see, who can see it and for how long. Revoke access at any time while activity and ownership stay traceable.

  • Share only what is neededOpen one project or task, not your entire workspace.
  • Give access for the right amount of timeEvery invitation can have a clear expiry from day one.
  • Take control back in one stepRevoke access whenever you need without losing the work history.

Separate perimeter

Your organization’s information stays separate from that of other Krato customers.

Tailored permissions

Collaborators see only the resource and actions you have chosen to open.

Expiry built in

Access ends on the date you set instead of leaving an open door over time.

Reviewable history

Access and changes stay traceable so you can see who did what and when.

Context carries over
from one module to the next.

Customers, permissions, activities and history stay connected. Operational data never has to be rebuilt between steps.

  1. 01From price list to quote

    The margin stays visible on every line.

    Import the supplier price list, build the offer and see the margin on each item. When the client confirms, the quote becomes an active contract.

    Margin visible
  2. 02From quote to contract

    Service, SLA and renewal in a single record.

    The contract holds service type, SLA target and renewal date, linked to hour packages and billing. The renewal is seen coming, not discovered late.

    Renewal in view
  3. 03From mailbox to ticket

    Every request reaches the right queue straight away.

    Client emails become tickets with the conversation, recipients and attachments together. The team starts with context, not a search across different tools.

    Request tracked
  4. 04From event to ticket

    The rule turns the event into an assigned ticket.

    An alert or a webhook meets your rules and enters as a ticket, with priority, customer and owner already assigned. No event stays in a separate dashboard.

    No event lost
  5. 05From asset to ticket

    The device brings its own history along.

    Devices, licenses and credentials are linked to the customer and the ticket. Warranty and renewal deadlines stay visible before they become a problem.

    History at the ticket
  6. 06From project to delivery

    The project makes work, ownership and deadlines clear.

    Tasks, milestones, checklists and dependencies stay aligned across Kanban, calendar and timeline views.

    Shared planning
  7. 07From activity to time entry

    Every hour stays connected to the work behind it.

    Use the timer or add time manually against a ticket, project, task or customer. The total is already ready to read and review.

    Verifiable totals
  8. 08From time entry to package

    The hour balance updates without manual calculations.

    Billable hours reduce the balance when needed. Top-ups and corrections stay visible and explained, so every change makes sense.

    Explainable balance
  9. 09From time entries to report

    The client sees the report only after your review.

    Work feeds a draft you can check, approve and export to PDF, CSV or XLSX, with scheduled delivery when you need it.

    Report approved
  10. 10From contract to payment

    The recurring charge starts when scheduled.

    Recurring contracts and packages generate the charge on the due date, without rebuilding the invoice each month. If a payment does not arrive, the system flags it before the balance goes negative.

    Recurring income

Quotes, tickets, hours and payments. In the same place.

Information moves from one activity to the next without duplication. The team works from one shared, up-to-date context.

Ticketing

Email becomes organized work.

Receive and reply from the connected mailbox, assign priorities and owners, work in list or Kanban view and keep notes and attachments together.

Project Management

Planning and delivery in the same project.

Tasks, milestones, dependencies, checklists, risks, decisions, calendar and a lightweight timeline.

Time Tracking

Every hour knows which work it belongs to.

Timer and guided manual entry, with a calendar and summaries that show where the team’s time goes.

Hour packages

The balance updates and always remains explainable.

Top-ups, used hours and explained corrections in a clear history, ready for client billing reports.

Customers

One operational record per customer.

Fiscal data, contacts, email domains, hour balance and recent tickets in a single view.

Client reporting

Review first. Then send.

Draft, versioning and approval: client reporting goes out only after review, with PDF, CSV, XLSX export and scheduled delivery.

Activity history

Who did what, and when.

Assignments, hours and approvals stay recorded in a reviewable history, with no after-the-fact reconstruction.

Suppliers & quotes

The price list becomes a quote, without retyping it.

Import prices and terms from your supplier, build the offer and keep the margin visible on every line. Once the client confirms, the quote becomes an active contract.

Contracts

The contract states what is owed, and when.

Service type, SLA target and renewal date in a single record, linked to hour packages and billing. Renewals are seen coming, not discovered late.

Automations

The external event arrives already as a ticket.

Define the rules that turn an alert or a webhook into a ticket, with priority, customer and owner already assigned. No event gets lost between different tools.

Assets

The device reaches the ticket with its history.

A registry of devices, licenses and credentials per customer, linked to the ticket when needed. Warranty and renewal deadlines are visible before they become a problem.

Subscriptions & payments

Recurring billing starts on the scheduled date.

Every recurring contract or package charges the customer on its due date, without rebuilding the invoice each month. If a payment does not arrive, the system flags it before the balance goes negative.

Share one resource.
Not your whole workspace.

Invite a client or partner to one project or task. Choose what they can see and do, set an expiry and revoke access whenever you need.

Connect the work, without copying it.

Bring email, customers and documents into the operational flow. Each organization chooses its own connections and keeps control of what it links.

Communication

Microsoft 365

Turn email into tickets, reply from the same queue and use a separate connection for product notifications.

Email and tickets
Communication

Google Workspace

Bring Gmail into the flow through a dedicated connection, separate from Microsoft: email becomes tickets and you reply from the same queue.

Email and tickets
Records and rates

Fatture in Cloud

Compare customers before importing and choose exactly which details to update, including hourly rates.

Controlled import
Management and contracts

Odoo

Sync customers and contracts with Odoo. When you edit a contract in Krato, the record updates without double entry.

Contracts and records
Attachments and files

Cubbit

Ticket and task attachments go to Cubbit, your organization’s European S3 storage. They stay in your bucket, not on our servers, and only people with access can open them.

Configurable archive
Monitoring and alerts

Checkmk

Every Checkmk alert enters Krato already as a ticket, with priority and customer assigned. No alert stays stuck in a separate dashboard.

Alerts and tickets