Your hosting choice
Cresec is built to run the tool for you, or for you to run it on your own container platform: the tool host is a container image. Your team keeps ownership of the workflow and chooses its runtime.
Self-hosting
Cresec is designed so a tool runs on Cresec or where your company runs software, with the same sign-in, personal connections, action controls and signed records either way. Neither option is deployed for customers yet.
Cresec is built to run the tool for you, or for you to run it on your own container platform: the tool host is a container image. Your team keeps ownership of the workflow and chooses its runtime.
The tool holds no app or model keys. Governed calls pass through Cresec’s gateway, which checks the person, tool version and action before using the appropriate connection.
A tool using Cresec’s hosted gateway needs outbound HTTPS access to it. For a restricted network, review the gateway location, identity provider and connected apps with enterprise support.
You retain your workflow; plan and measure the work required to leave. You can restore direct vendor access under your own credential management. For your workflow, we measure the code and configuration changes, credential migration and elapsed time with you.
Enterprise support
Tell us where the tool needs to run, which systems it calls and what your network permits. We’ll review the deployment with your IT and security teams and reply by email.
Rather talk it through live? Book 30 minutes (opens Cal.com in a new tab)
We’ll reply to the email you gave us. If you need to add anything, write to support@cresec.ai.