Architecture review
Diagrams of the services, data stores and network paths, reviewed with your architects before deployment.
How we work
You decide how much we build.
We deploy Cortex as it is, build to your specification, or work beside your IT team on a system you own.
Engagements
Pick a starting point. Each one ends with software in your cloud and a team that runs it.
Deploy the platform
We install Cortex in your cloud, configure it for your programs and train your team. Then you run it, or we run it with you.
What we do
- Install Cortex with your IT team, on infrastructure you control
- Connect sign-in to your identity provider
- Set up approval paths and limits for each program
- Train your reviewers, approvers and administrators
What you keep
- Your records, in your database
- An append-only change history
- The choice to run it yourselves or with us
Phases
Discovery
We map your programs, data sources and approval paths with your compliance and IT leads.
Govern your own build
AI writes code fast. Your release checks decide what ships.
Changes pass the same checks whether an engineer or an AI coding agent wrote them.
Change
Add a fair market value check to engagement requests
Written by an AI coding agent, opened by Priya N.
Checks
Tests, type checks, secret scanning, and a dependency check against known vulnerabilities and licences.
Waiting for a change
The practices we put in place
Version control
Changes live in a repository with a reviewed history, and main stays releasable.
Review gates
Merges need an approving review from someone other than the author.
Dependency management
Pinned versions and automated checks for vulnerabilities and licences.
Testing
Tests run before anything merges, and a failing test stops the merge.
Release and rollback
Small, frequent releases with a rehearsed way back.
AI agents inside policy
Agents work on branches with scoped credentials, and their changes go through the same review as anyone else's.
Validation evidence
Test records, approvals and release notes your quality team can use when it validates your system for GxP use.
For IT and security
Your IT team runs the infrastructure. We give them what they need to review it.
Security questionnaire
Answers to your vendor security assessment, written by the people who build the platform.
Service inventory
The cloud services, sizes and network rules Cortex uses, listed before we install anything.
Runbooks
Steps for upgrades, backups and restores that your operations team can follow.
Questions
What procurement asks us.
In your own cloud, in the region you choose. EthicsVue keeps no copy of your records.