JWS Platform
Deployment Passport
Your app's deployment contract, portable
- Teams avoiding lock-in
- Developers documenting infra
- Agencies handing off projects
The problem
Deployment knowledge usually lives in one person's head or one vendor's dashboard. Lose either and redeploying becomes archaeology.
How JWS solves it
A generated jws.yaml that describes exactly how your app builds, starts, and stays healthy — owned by you, usable anywhere.
What you get
Generated jws.yaml
Produced from real analysis, not a blank template.
Complete contract
Build/start commands, runtime, ports, services, env keys.
Versioned per import
Each re-import refreshes the passport.
Portable by design
Readable YAML you can commit to your repo.
How it works
- 1
Analysis completes
Detections feed the passport generator.
- 2
Review the passport
Open it from your project page.
- 3
Commit it
Keep jws.yaml with your source for reproducible deploys.
Security & privacy
The passport lists env var keys and metadata only — never values — so it is safe to commit to your repository.
Cost impact
The passport is free and makes migration off JWS as cheap as migration onto it — that is deliberate.
Honest limitations
- Some advanced options are staged rollouts — status is shown honestly.
- Complex stacks may need a manual review step.
- Your application code quality remains your responsibility.
FAQ
Do I need DevOps experience?
No — the workflow is built for builders, not operators.
Can I leave later?
Yes — the Deployment Passport keeps your app portable.
What does it cost?
Estimates in EUR are shown before any provisioning.