284313f908
Excluded: .git, node_modules, secrets/, compose.env, assemblyscript tgz Source: /opt/alga-psa on psa.joliet.tech
3.3 KiB
Product
Register
product
Users
Alga PSA serves two primary product audiences:
- MSP owners and operators working in the
/msparea, managing service delivery, client relationships, billing, projects, assets, tickets, automations, and business performance. - MSP customers working in the
/clientarea, checking tickets, projects, billing, assets, documents, appointments, and service progress without needing to understand internal MSP complexity.
Both groups need a product that feels fast, organized, and trustworthy during real operational work. MSP owners need density and control. MSP customers need clarity, confidence, and a guided view into their relationship with the provider.
Product Purpose
Alga PSA is an open-source Professional Services Automation platform for Managed Service Providers. It exists to help MSPs run daily operations across support, billing, client management, projects, time tracking, assets, documents, reporting, and workflow automation.
Success means users can move from signal to action with minimal friction: resolve tickets, track time, approve billing, understand project status, manage clients, and automate repeated work without feeling buried in legacy enterprise clutter.
Brand Personality
Efficient, powerful, modern.
The product should feel like a thoughtful operations workspace: structured, capable, and calm under load. It can borrow the purposeful simplicity of Notion and the modern business-object clarity of Twenty.com, while staying optimized for dense service operations rather than note-taking or CRM alone.
The tone should be direct, useful, and confident. The interface should make complex MSP work feel manageable, not simplified past usefulness.
Anti-references
- Dated enterprise MSP software, especially the heavy, cluttered feeling associated with ConnectWise.
- Generic AI-generated SaaS UI, including decorative gradients, purposeless cards, vague empty states, and components that feel placed without intent.
- Screens where every element competes equally for attention.
- Consumer-style gloss that reduces trust for operational, financial, or service-delivery workflows.
- Low-density dashboards that look polished but fail to support real MSP throughput.
Design Principles
- Purpose before presence. Every visible element should support a task, explain state, or create trustworthy orientation. If it does not earn its place, remove it.
- Modern without novelty. Use contemporary patterns and clean structure, but avoid invented affordances that slow experienced operators down.
- Density with hierarchy. MSP workflows are information-rich. Preserve useful density while making priority, status, ownership, and next action obvious.
- Two audiences, one system. The MSP workspace can expose depth and control. The client portal should translate the same system into clear, calm status and action.
- Operational confidence. Billing, tickets, projects, and automation should feel dependable, reversible where possible, and explicit about consequences.
Accessibility & Inclusion
Target WCAG 2.1 AA as the baseline. Support keyboard-first workflows, visible focus states, reduced motion preferences, and color-blind-safe status communication. Do not rely on color alone for priority, ticket status, billing state, or destructive actions. Preserve readable contrast in both light and dark themes.