CI on the project
Pipeline status is not a separate dashboard tab.
Check outcomes written to the share view
For teams that ship
Domain, CI, and host beside the code
Deploy is part of the build record, not a separate project.
The category
On Arvad, preview URL, checks, secrets scope, and cost write back to the project that produced the change.
CI status mirrored onto the run, not a separate dashboard
Domain and host shown on the deploy topology
Failed checks block a shareable green status
Rollback target stored with the run on the project
Wire the release path
From repo to preview in one workspace: connect, map, gate, and ship without losing the original ask or the last good deploy.
From repo to preview in one workspace: connect, map, gate, and ship without losing the original ask or the last good deploy.
01Connect the repo
02Map domain and host
03Ship with checks
04Rollback from the project
Connect the repo
Branch rules and checks attach to the project so pipeline status lives beside the change.
CI status mirrored onto the run
Map domain and host
DNS and target environment stay in your accounts. Arvad orchestrates wiring, not credential custody.
Domain record linked on the deploy topology
Deploy evidence
Checks
- Unit suite
- Integration
- Deploy health
Cited files
- app/api/checkout.ts
- lib/billing/invoice.py
- tests/checkout.spec.ts
Blast radius
3 services · 11 files · 0 shared schemas
Checks green. Staging URL live. Spend recorded on the same thread.
Ship with checks
Suites gate promotion. No shareable green status until checks pass.
Failed checks block a shareable green status
What the deploy path includes
Domain wiring
Hostname attached to the environment record.
Domain shown on deploy topology
Host targets
Staging and prod as first-class environments.
Environment ID stored on the run
Scoped secrets
Credentials stay in your vault path.
Secrets never appear in the share link
Health gates
Promotion waits on green checks.
Deploy health on the share link
Branch-aware releases
PR and issue stay linked to the deploy.
Git ref recorded with the preview URL
Rollback path
Prior good deploy remains one action away.
Rollback target named on the project
Cost with the ship
Cost sits beside the environment URL.
Cost line on the share view
One topology, one story
Domain, CI, secrets, and host in a single diagram tied to the run.
Deploy topology is the product diagram, not clipart
Deploy scripts vs a release path in the workspace
DIY CIArvad
Arvad sits where the thread keeps the plan, staging, spend, and checks.
| Capability | DIY CI | Arvad |
|---|---|---|
| Tied to the original ask | ||
| Preview URL | Slack paste | On the share link |
| Checks + change scope | Separate tools | One panel |
| Rollback from the run | Tribal knowledge |
Plans for you and your team
Solo or team. Upgrade when usage grows.
Save 20% on Team.
Compare plansPick the plan that matches how you build. | FreeStart free | StarterChoose plan | ProfessionalChoose plan | EnterpriseChoose plan |
|---|---|---|---|---|
| Credits included | 120 credits included | 240 credits Included | 500 credits Included | |
| Projects per week | 1 mini project | 2 mini projects | 4 mini + 2 medium projects | |
| Documentation access | Essential | Standard | Full | |
| Planning & task breakdown | ||||
| Dependency resolution | ||||
| Queue-based processing | ||||
| Daily questions | Limited | Up to 10 / per day | Up to 25 / per day | |
| Upgrade options | ---- | Large projects | Large-scale projects | |
| Price | $0.0 | $25 | $50 |
Straight answers
Limits stated plainly. No demo theater.
One question
When the build finishes, can you show a teammate the plan, preview, tests, and deploy status without digging through chat?
If you cannot, you still have a chat log. Arvad keeps that work in one workspace.
Deploy it. Keep the record.
Domain, CI, and rollback beside the change that caused them.
Keep exploring