Head to head
Current vs Proxuma
An honest, sourced side-by-side of Current and Proxuma for MSP project management — where Proxuma is stronger, and where Current fits.
Written by the Current MSP team · Reviewed by Chad McDonald, Chief Technology Officer (CTO), ITPartners+
Last updated July 18, 2026
YesPartialNo?Not documented
| Capability | Current | Proxuma |
|---|---|---|
| Gantt / timeline view | Yes — native Native Gantt/timeline boards plus a dependency map (@xyflow/react). | Yes — native Full Gantt over every Autotask project; drag to reschedule/stretch task bars. |
| Critical-path analysis | Yes — native engine Real native critical-path engine with client-side cycle detection. | No No critical-path engine documented; scheduling is manual drag/stretch of bars. |
| Task dependencies (FS/SS/etc.) | Yes — dependency-aware Dependency-aware scheduling with a dependency graph and cycle detection. | ?Not documented No Proxuma page documents creating/editing predecessor links in its own Gantt; organizes by phases/tasks/hours. |
| Dependency-aware auto-scheduling | Yes — incl. back-scheduling Dependency-aware scheduling and back-scheduling across timeline, dependency map and what-if scenarios. | No — manual only Rescheduling is explicitly manual drag/stretch; no engine that ripples a slipped predecessor. |
| Resource management & capacity planning | Availability-driven Availability/PTO-aware scheduling via resource_availability and what-if scenarios; not a multi-year capacity forecaster. | Yes — flagship Capacity-based calendar, live per-day overbooking bars, capacity visibility years ahead. Its core product. |
| PTO / availability-aware scheduling | Yes PTO/availability-aware scheduling and back-scheduling across timeline, dependency map and scenarios. | Yes — Outlook-fed Capacity computed from service calls plus Outlook PTO/holidays/meetings; two-way Outlook sync. |
| Kanban board | Yes — native Native drag-and-drop Kanban (@dnd-kit) for tasks. | Yes — writes back Kanban module where Autotask statuses are columns; moving a card changes status in Autotask. |
| Milestones | Yes Milestones with scheduling/criticality. | ?Not documented Product pages describe phases/tasks/hours; a milestone feature is not documented (low-confidence). |
| Portfolio / multi-project view | Yes Portfolio tiles/views across projects. | Yes Every Autotask project on one timeline; filtered views per team/lead/client; bulk operations. |
| Time tracking | Yes Native time entry that flows to your PSA for billing — Autotask, ConnectWise, or Halo PSA. | Planning layer Plans/allocates estimated hours and writes service calls to Autotask; time actuals live in Autotask. |
| Billing / PSA integration & source-of-truth | Syncs to PSA or native 'autotask_synced' keeps Autotask as billing source of truth (Current owns scheduling); or fully Current-native. Also integrates ConnectWise and Halo PSA. | Deep 2-way (Autotask) Real-time two-way Autotask sync via API+webhooks; Autotask stays system of record. Autotask-only today. |
| Client / partner portal (with financial isolation) | Yes — DB-level isolation Partner portal with genuine DB-level financial isolation (RLS + partner-safe views + restrictive policies); partners never see financial data. | No portal Internal staff tool; no client/partner-facing portal or external isolation model. |
| Templates / playbooks | Yes — PMI playbooks PMI/post-merger playbooks and 24 managed-intelligence playbook templates per tenant. | Yes Build a template from scratch, a past project, or a library; template-to-timeline in minutes. |
| Automation / workflow rules | Monitors + notifications Score/monitor engine (run_current_monitor) and notifications; not a general user-built trigger-action rules builder. | Sync-driven + shifts Automation is mostly two-way sync plus a Shifts rotation/load-balancing module; no general rules engine. |
| Microsoft 365 integration (SharePoint/Teams/Calendar) | Yes — via Graph SharePoint, Teams and Calendar integration via Microsoft Graph. | Outlook only Two-way Outlook Calendar sync and M365 as a Power BI source; no SharePoint/Teams integration documented. |
| AI insights | Yes — Anthropic AI insights powered by Anthropic across the platform. | BI/Copilot-oriented AI framed around the Power BI/MCP/Copilot layer; an in-app 'AI plan assistant' is vendor-described but not detailed. |
| Modern UI & architecture (recency of rebuild) | 2026 ground-up rebuild Fully rebuilt/renamed Cascade→Current in 2026 on React 19 + Supabase. | Purpose-built recent Founded 2023, live 2025-26; modern drag-and-drop interface, SOC 2 Type I. |
| Setup / onboarding effort | Modern self-serve Modern SaaS with transparent per-seat pricing; low-friction adoption alongside your PSA. | Fast Layers onto Autotask; vendor claims 'go live in 24 hours'; 14-day no-credit-card trial. |
| Pricing model & public price | Transparent — $50/user/mo Public pricing: $50/user/month or $540/user/year. | Model public, price hidden Per-role seat model (EUR) is public but per-seat prices show only via a calculator or demo; longer terms carry an unspecified discount. |
| Best-fit user | Modern delivery + partner isolation MSPs wanting purpose-built dependency-aware/critical-path delivery, a financially-isolated partner portal, and billing sync to their PSA — Autotask, ConnectWise, or Halo PSA. | Autotask capacity planning Autotask MSPs wanting visual capacity/resource planning and a shared timeline on top of Autotask as system of record. |
Where Proxuma wins
Deep, native resource-capacity planning is its core product — a capacity-based calendar with live per-day overbooking bars and multi-year forward visibility, fed by real Outlook availability (PTO, holidays, meetings). Its capacity forecasting is genuinely more specialized than Current's.
Where Current fits: Proxuma is an Autotask-only planning overlay with no critical-path engine, no dependency-aware auto-scheduling, no client/partner portal, and opaque pricing. Current is a full delivery platform — critical path, dependency scheduling, partner isolation, PMI playbooks — and works in native mode or synced to any of three PSAs (Autotask, ConnectWise, or Halo PSA), not just Autotask.
Why MSPs choose Current
- A modern 2026 ground-up rebuild (React 19 + Supabase), not a project module bolted onto a decades-old help-desk or PSA core — so the delivery experience is fast and purpose-built rather than layered onto legacy screens.
- A real, native critical-path engine plus dependency-aware scheduling and back-scheduling — native to the product, not a paid Moovila/TopLeft add-on the way it is for Autotask, ConnectWise and HaloPSA.
- PTO/availability-aware scheduling that runs consistently across the timeline, the dependency map AND what-if scenarios — availability-aware planning most incumbents only partially document.
- Kanban AND Gantt AND an interactive dependency map all native in one tool (Autotask lacks native project Kanban; Syncro lacks project boards entirely).
- A partner portal with genuine database-level financial isolation — Postgres RLS + partner-safe views + restrictive policies — so partners can never see financial data. Incumbent portals (Autotask, ConnectWise, Syncro, Halo) are designed to EXPOSE invoices to clients; Current is the opposite by construction.
- Flexible source-of-truth: 'autotask_synced' keeps Autotask as the billing record while Current owns scheduling, or 'current-native' where Current is the source of truth — plus shipped ConnectWise and Halo PSA integrations and Datto/Addigy/ScalePad connectors.
This is the two-tool view. See the full msp project management software, compared for all 7 tools side by side.