JWS Platform
Source Import
Every way to get code into JWS
- GitHub-first teams
- AI-builder users with ZIPs
- Contractors receiving handoffs
The problem
Every platform locks you to its own import ritual. If your code doesn't fit the ritual, you're stuck before you start.
How JWS solves it
Import from GitHub, any public Git URL, or a ZIP archive. Your code is indexed and analyzed — never executed during import.
What you get
GitHub import
Point at a repository and branch; archives fetch over the API.
Public Git URLs
Any reachable Git host works the same way.
ZIP upload
Up to 100 MB, extracted and indexed server-side.
Safe handling
SSRF-guarded downloads; code never executed.
How it works
- 1
Choose a source
GitHub, Git URL or ZIP.
- 2
Import runs
Download, extract, index.
- 3
Analysis begins
Detections and readiness follow automatically.
Security & privacy
Downloads are restricted to validated public URLs, archives are size-limited, and imported code is parsed — never run — during import.
Cost impact
Import and analysis are free; infrastructure costs start only when you choose to deploy.
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.