Vycko
VYCKO FOR MSPs & IT PROVIDERS

Less chasing.
More resolving.

Your customers, computers and support work in one place. Rocky handles routine fixes and checks the result. When he can’t resolve an issue, your engineers get the findings and the steps already tried.

Built for the people behind good IT support.

Vycko browser remote support with an illustrative desktop and sample customer data.
Product preview with sample data.

Start with the customer context.

Keep devices, sites and support history together, with access scoped to the customer.

Investigate. Repair. Verify.

Move from an alert to diagnostics, remote support and a reviewed repair in the same workflow.

Set the rules for routine work.

Take routine work off the queue while keeping approvals, customer rules and outcomes visible.

BRING THE AI YOUR ENGINEERS ALREADY USE

ChatGPT or Claude.
Meet your remote tools.

Connect your engineer’s assistant to Vycko through MCP. Inspect real device evidence, request authorised repairs and check the result from the conversation they already use.

No Vycko AI tokens for direct MCP tools.

Your own AI account handles the reasoning. Vycko provides the permitted device evidence and remote actions.

Explore ChatGPT, Claude & MCP

Your AI provider’s subscription, usage limits and charges still apply. Vycko’s built-in AI is a separate workflow. Connection support depends on your assistant and plan.

ENGINEER + ASSISTANT + VYCKOIllustrative workflow
“Why won’t this computer print? Check the evidence and help me fix it.”
  1. 01

    Inspect the evidence.

    Read the service status and recent events. Find the cause before changing anything.

    remote_services · remote_event_log
  2. 02

    Request the right repair.

    Use a reviewed runbook within the customer’s permissions and approval rules.

    request_runbook
  3. 03

    Check what happened.

    Verify the job result and service state. Keep the action recorded with the support work.

    get_job · remote_services

The engineer decides. Customer rules apply. The result still needs checking.

WHAT YOUR TEAM CAN DO

From the first alert
to the checked result.

Explore all eight areas of Vycko, with the full explanations and controls behind every feature.

Monitoring & support

Keep health checks, alerts, incidents and the next support step connected.

Explore monitoring

Remote support

Use screen control, console, files, services and event logs to investigate.

Explore remote tools

Patching & automation

Plan updates and reviewed fixes around maintenance windows and customer rules.

Explore automation

Customer experience

Give people a useful view of their assets, requests and monthly reports.

Explore customer tools

Administration & integrations

Manage enrolment, roles, scoped access and authorised API, MCP and webhook connections.

Explore integrations
The connected platform. Practical explanations for every area.Explore the full feature catalogue
A PRACTICAL START

Built around your support team.

A demonstration can focus on the customers, devices and tasks you actually support.

  1. 01

    Start with your support model.

    Show us your customer mix, device estate and the workflows your engineers want to improve.

  2. 02

    Set the right boundaries.

    Configure customer scope, roles, permissions and the actions that need approval.

  3. 03

    See it in your own workflow.

    Explore dashboards, remote tools and automation, and confirm the integrations that fit your team.

EXPLORE THE WORKFLOWS

The details behind
the tools.

More about the workflows, permissions and customer experience behind the platform.

Keep customer environments organised

Customers, sites and devices provide a structure for the estate. Scoped access and role settings control what each reader or technician can see. Hardware and software inventory, performance history, device notes and change records help establish context before work starts. Search connects the team with supported customer, device and incident fields, while enrolment and deployment tools support connecting devices and managing agent health.

Build an overview for the work you do

Configurable dashboards combine numbers, charts, attention lists, actions and notes. Move and resize widgets, save named views and start from shared templates. A morning dashboard can show alerts and approvals; another can focus on patches, warranties or scheduled work. Evidence timing and coverage remain relevant, especially when a device is offline or a reading is unavailable.

Investigate with AI and practical remote tools

Vycko AI brings questions, device evidence, proposed repairs and follow-up into a support conversation. Reviewed runbooks and the repair library help turn repeatable knowledge into procedures that can be checked. Remote screen control, console, file transfer, services, processes, event logs and supported Windows Registry tools provide different ways to investigate. AI screen assistance and session evidence follow the configured permissions, consent and stop controls.

Make the path from request to outcome visible

The work queue brings requests and tasks needing a technician together. Incidents keep findings, conversation, jobs and approvals in a chronological record. A decision to approve a plan is separate from the job running; the result still needs checking. Session history and available audit exports help the team review who did what and provide context when another person takes over.

Automate within each customer’s rules

Schedule reviewed runbooks, plan patch installation and application deployment, or configure reviewed remediation for known conditions. Customer rules determine diagnostics-only, approval-required, pre-approved or prohibited actions. Rollout controls, maintenance windows, controlled batches and stop settings bound the work. Visible per-device results give technicians evidence to investigate failed or skipped actions.

Explain the service to customers

The portal gives customer contacts their own access to computers, understandable alerts, requests and available reports. Asset registers and replacement planning support conversations about the estate; readiness views organise available technical evidence without claiming certification. Authorised API, MCP and webhook access can connect supported tools, with keys and scope configured for the environment.

Turn technician repairs into future automatic fixes

When Rocky cannot resolve an issue, your engineer takes over with the investigation and attempted work. Once they solve it, Rocky can draft a reusable repair from their notes. Your team reviews and approves it, then chooses where it may run. That gives Rocky an approved fix to use automatically when the same problem returns, within each customer’s rules.

See how Vycko fits your support model

Tell us about your customer mix, device estate and the workflows you want to improve. We can show the full system, confirm device and integration support, and discuss deployment and pricing. Feature availability depends on operating system, agent installation and configured access, so the demonstration can focus on the circumstances your team actually supports.

LET’S MAKE IT WORK FOR YOU

See the full system.
Bring your real questions.

Tell us about your customers, your engineers and the work you want to make easier.

Features depend on the operating system, installed agent and configured permissions. Windows is the main focus; ask us about support for your devices. Readiness evidence is not certification.