Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can it replace a paid Desktop agent? #158

Open
jfbaro opened this issue Sep 18, 2024 · 2 comments
Open

Can it replace a paid Desktop agent? #158

jfbaro opened this issue Sep 18, 2024 · 2 comments
Assignees

Comments

@jfbaro
Copy link

jfbaro commented Sep 18, 2024

Support Question

Hello,
We are exploring the implementation of FDC3 to enable communication between our custom desktop applications (Windows .NET-based), custom web-based applications (typically Angular), and off-the-shelf solutions like Excel, Salesforce, and other SaaS platforms we use.
We're considering using FDC3-Sail as our desktop agent. Could you please advise whether we can use FDC3-Sail as-is and achieve all the benefits that paid solutions like Glue42 offer?
Our main objectives are to implement the core features of FDC3:

  1. Unified Desktop Environment: Run desktop and web-based applications within a single "desktop" environment, primarily on Windows laptops (no MacOS or Linux support needed).
  2. Two-Way Communication: Enable seamless two-way communication between applications.
  3. Automatic Application Launch: Automatically launch desktop or web applications when an intent is triggered.
  4. Workspace Persistence: Save the "desktop" layout, including screen sizes and other properties, so it can be restored in the same state the next day.
  5. App Directory Management: Utilize an App Directory to manage applications that respond to intents.
  6. Administrative Configuration: Provide an admin interface where we can configure desktop agents for different user types or roles (e.g., limiting intents for particular users). This admin should integrate with our Single Sign-On (SSO) system so administrators can use their normal internal credentials.
  7. Security and Compliance: Ensure privacy, compliance, and SSO access to meet typical financial institution audit and regulatory requirements.
  8. Production Deployment: Deploy this solution in a production environment for internal users only—not for our customers or brokers.
    We would greatly appreciate any guidance or insights you can provide.
    Thank you!
@nkolba
Copy link
Contributor

nkolba commented Sep 28, 2024

Hi,

Sail is an open source electronjs implementation of FDC3. It is focused on primarily the first 3 points. For workspace persistence, App Directory management, Admin, SSO, audit trail, etc, you would want to pair it with a backend solution.

-Nick

@jfbaro
Copy link
Author

jfbaro commented Oct 24, 2024

Thanks @nkolba !

Just to confirm, FDC3-SAIL is fully compliant with FDC3 standards (https://github.com/finos/FDC3-conformance-framework), correct?

Looking forward to using FDC3-SAIL for our use case.

Much appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants