There are three modes in which users can use the Faros AI platform:
Most commonly, users connect to the fully managed SaaS version of the Faros platform. In this mode, users simply provide API tokens for their engineering data sources, and the Faros platform manages the data ETL in addition to hosting the APIs, metrics, and other applications that operate on top of the data. Our Data Dictionary describes the data that gets pulled for different data sources. For added control, many of the connectors, such as the Jira connector allow the user to specify an explicit exclusion list of fields that should not be pulled.
Some users whose security protocols prohibit external systems from connecting to their engineering sources (e.g GitHub Enterprise, Jira Server) choose to operate in the hybrid mode. In this mode, the users manage and run the Faros data connectors themselves so as to have complete control over the data that gets sent to the Faros SaaS platform. Other than the data ETL however, they directly use the SaaS platform for everything else, e.g., APIs and metrics. The Faros data connectors are open source Airbyte connectors and the source code for them can be found here.
In this mode, users spool up an entire instance of the Faros platform in their own infrastructure, e.g., in their own AWS VPC, via the Faros Terraform module. All the Faros platform services are containerized and users manage the entire platform themselves, which comes with its pros and cons. Please reach out to us at [email protected] to learn more.
Updated 3 months ago