Skip to content
Big Picture

Hybrid Software and Desktop Agents

Many software vendors ship hybrid solutions that combine SaaS web applications with desktop agents, services, or companion clients. The SaaS component provides control and coordination, while the desktop component handles local operations, offline capabilities, or system integration.

Big Picture manages the desktop component of hybrid systems. It provides release governance and licensing for the endpoint-resident software while remaining independent of how the SaaS component is deployed or updated.

When This Scenario Applies

Section titled “When This Scenario Applies”

This scenario applies when you ship:

  • SaaS applications with desktop agents that run locally
  • Web-based control planes with companion desktop services
  • Cloud-managed software with local clients or helpers
  • Hybrid architectures where desktop components need independent update governance

Big Picture focuses on the desktop component. The SaaS component may use its own deployment mechanisms, but the desktop agent benefits from Big Picture’s policy-driven release governance and licensing.

How Big Picture Addresses This

Section titled “How Big Picture Addresses This”

Big Picture treats the desktop component as an independent product with its own release lifecycle. The SaaS and desktop components can have different update cadences, versioning schemes, and deployment requirements.

Release Coordination

Section titled “Release Coordination”

The desktop agent checks Big Picture for updates independently of the SaaS component. This allows:

  • Desktop agents to update on schedules that match IT requirements
  • SaaS components to update through their own mechanisms
  • Coordinated releases when both components need to update together
  • Independent security patches for desktop components without waiting for SaaS releases

License Synchronization

Section titled “License Synchronization”

Big Picture’s lease-based licensing works independently of SaaS authentication. Desktop agents obtain license leases from Big Picture’s license server, which can be:

  • Cloud-hosted alongside or separate from SaaS infrastructure
  • Local license servers for air-gapped deployments
  • Synchronized with SaaS user accounts through tenant configuration

The desktop component maintains its own license state while respecting the same user or organization boundaries as the SaaS component.

Tenant-Aware Policy

Section titled “Tenant-Aware Policy”

Big Picture’s tenant-aware policy system aligns with SaaS multi-tenancy. When a desktop agent checks for updates, Big Picture evaluates:

  • Which tenant the agent belongs to
  • Tenant-specific update policies
  • Staged rollout eligibility for that tenant
  • License entitlements for that tenant

This creates consistent governance across SaaS and desktop components without requiring tight coupling.

Key Considerations

Section titled “Key Considerations”

Update Independence

Section titled “Update Independence”

Desktop agents can update independently of SaaS components. This is useful when:

  • Desktop components need security patches more frequently than SaaS releases
  • IT departments require different approval workflows for desktop software
  • Desktop components have longer testing cycles than SaaS deployments

Shared Licensing Models

Section titled “Shared Licensing Models”

License leases from Big Picture can align with SaaS subscription models. Configure tenant policies to reflect SaaS entitlements, ensuring desktop agents respect the same license boundaries as the SaaS application.

Deployment Coordination

Section titled “Deployment Coordination”

When both components must update together, coordinate through release channels and tenant policies. Big Picture supports staged rollouts that can align with SaaS deployment schedules, but the desktop component maintains its own update decisioning.

Integration Points

Section titled “Integration Points”

Desktop agents typically integrate with SaaS components through APIs or message queues. Big Picture does not manage these integration mechanisms. It focuses on release governance and licensing for the desktop component, leaving application-level integration to your architecture.

Next Steps

Section titled “Next Steps”