Make it. Put it to work.

A working prototype still needs a database, configuration, a deployment target and a way to see what went wrong. Panacea brings that surrounding work together so a useful app can move from your machine into an environment your team can operate.

• Bring the app you have already made

  Build common Node.js, Python and static applications from source. Projects with other supported Linux requirements can supply a Dockerfile; apps with multiple services can describe the components that need to run together.

• Connect the services behind it

  Give the application a PostgreSQL database, Redis or S3-compatible storage through the configured platform. Bring its backing services into the deployment setup instead of treating each as a separate infrastructure project.

• Keep each environment's configuration in place

  Manage environment variables and secret references alongside the application. Distinguish platform-provided settings from the accounts and values you need to supply for external services.

• Follow a change all the way through

  Inspect build progress, application logs and deployment history. Use configured preview environments to review an update, and retain a previous release to return to when needed.

• Make release checks and failures understandable

  Choose which scans and checks warn or gate a release. If a deployment fails, inspect its logs and a diagnosis that separates application problems, missing configuration and unsupported requirements, with a suggested next fix.