Core Concepts

Organizations, Customers, and Users

Prismatic writes software for other software companies who have their own customers, so it's important to disambiguate terms like organization and customer.

When your company signs up with Prismatic, you create an organization. Your organization has multiple customers that you can manage. Users can be created for both your organization and your customers, with organization users have broader, company-wide roles and permissions, and customer users having permissions limited in scope to their company.

Integrations and Instances

Within your organization you can assemble together multiple components to create an integration. That integration can be tested using our integration designer. Once you are satisfied with your integration, the integration can be published, and instances of the integration can be deployed to one or many of your customers.

Integrations are versioned, so you can choose to push integration updates selectively to customers, and roll back instantaneously as needed.

Configuration Variables and Credentials

Instances of integrations can reference configuration variables, which are a list of key-value pairs that save things like API endpoints of customer UUIDs. Instances can also utilize credentials to interact with external services - credentials securely store API keys, username/password pairs, etc.

Config variables can be organization-wide or customer-specific. When an instance is deployed, configuration variables and credentials are saved statically into the deployment.

Logging, Monitoring, and Alerting

When an integration behaves unexpectedly (takes too long to run, or fails to run to completion), you want your team to be notified. Prismatic's alert monitors can be configured to monitor your instances, and notify your team in the event of an issue. Logs of all instance runs are retained, so you can debug production issues and rapidly resolve problems.

Last updated on