Profiles Of Customers Driving Requirements

These are based on the current customers we are working on. Characteristics of these customers:

• Legacy footprint (in most case Java based)
• Do not have access to strong Javascript framework developers
• Experiment with Backstage but not certain they will use it

Customers are:

• Citi Bank
• Bank Of America
• Raytheon

Parodos High Level Goals

• A simple workflow engine specific to IDP workflows
  • Onboarding to new tools and environment
  • Migrating to existing tools and environments
  • Upgrading existing tools and environments
  • Team level tasks (add/remove developers, promote releases across environments, etc)
• Provide a robust and flexible means of bringing together existing tools and processes into a single workflow that allows developers to navigate confusing/time consuming process in their environments to get access to what they need to start coding:
  • Pipelines
  • Environments
  • Networking
  • Observability tooling
    • For all of these they are required:
      • Permissions
      • Approved configurations
• The Parodos solution needs to be Backstage friendly, but not dependent on it in the event clients choose to build an IDP without it (or are not allowed to use it in their environment)
• Should be easy for IDP developers to use to create/modify/deploy workflows
• Should not require specific tooling (outside of Backstage for the UI) or any bleeding edge technology or products to be used