Ship Your App
Submit project details, your Infoblox IT GitHub repo, and SSO info — then we analyse and ship automatically.
New deployment request
Complete all steps to ship your application through ABCD.
Paste the repository name that follows Infoblox-IT/. We'll validate it's accessible and pull metadata.
We build and deploy from this branch every time it's updated.
-abcd is always appended before the domain.
Your app uses OKTA SSO, so it will be auto-approved. If you had chosen public auth, InfoSec would need to manually review before it goes live.
What we use this for
Prefills your cloud app name on the SSO step. Should match what your team calls the product.
Identify who to contact for access and approvals during rollout.
Decides prod and/or non-prod URLs (-abcd / -abcd-dev).
Typical deployments complete once all four steps are submitted and validated.
GitHub requirements
URL must be under github.com/Infoblox-IT/ so ABCD can validate ownership.
Use the repo that will be built and deployed — typically the default branch (e.g. main).
After this step, we analyse the stack and continue to SSO configuration and review.
Shipcode has read access to your repo via the ABCD GitHub app. No personal tokens needed.
Everything checks out
We ran validations on your configuration.
Submit when ready. We'll deploy immediately and notify you once it's live.
Deployments
Every app shipped through ABCD. Click a row for details, pipeline history, or live URL.
InfoSec Audit
All applications, scan results, compliance posture, and audit trail — for the InfoSec team.
Security Gate Compliance
Across all 47 apps in the registry
CVE-2024-3912 · lodash@4.17.20 prototype pollutionapi/config.js:47CVE-2024-3912 · lodash@4.17.20 prototype pollution
How ABCD takes your app
from idea to production
ABCD is a guided path for "vibe-coded" prototypes and team-owned services alike: connect GitHub under your org rules, pass automated gates, then hand off a deployment your security partners can recognize — not a black box.
Every step is visible, accountable, and audit-ready
Each step shows progress clearly, assigns someone to handle any issues, and keeps a record of approvals that can be reviewed later in a demo or audit.
Share release tier, SSO needs, and your Infoblox GitHub repo. ABCD clones the truth source for every later gate.
We scan what you built and verify it against your policies, and we address any issues before anything ships.
CI runs with SonarQube, Qualys, Wiz, and Terraform checks. Optional integrations pause the line until credentials are wired safely.
Deployments tracks every app: redeploy from Git, manage Okta access, and pull AI Assist when you need context on a row.
Built for the whole path, not just one team
These pieces are wired into the UI you already see — Ship, Deployments, InfoSec, and the optional AI side panel.
One repo, many gates
Branches and commits flow through the same CICD Pipeline. Redeploy always points at Git — not a mystery zip — so audits stay repeatable.
Read the flowWant me to suggest a fix
AI when you ask
The right panel stays out of the way until you open AI Assist from Deployments. That keeps the workspace calm while specialists work.
See it in DeploymentsInfoSec visibility
The audit view summarizes who did what and ties chatter to apps. It complements the engineering tabs rather than replacing them.
Open audit dashboardReady to ship your app?
Four steps, typically under 12 minutes. Your deployment flows through the same gates your security partners already trust.
src/data to match your own narratives without touching layout code.