Backend and APIs
- .NET / ASP.NET Core / C#
- Node.js / TypeScript
- Python / Django / FastAPI
- Java / Spring Boot
- PHP / Laravel
- Ruby / Rails
- Go services
Resource
Supported stacks and intake boundaries
Shipward keeps stack support and source-handling boundaries explicit so the audit can be quoted and delivered without guesswork.
Frontend and product apps
- React / Next.js / Remix
- Vue / Nuxt
- Angular
- Svelte / SvelteKit
- React Native or Flutter when backend and deployment boundaries are clear.
Data and integration
- PostgreSQL, SQL Server, MySQL, and Redis.
- Queues, scheduled jobs, and background workers.
- REST APIs, GraphQL APIs, and webhooks.
Cloud and delivery
- AWS, Azure, GCP-hosted systems.
- Docker/containerized apps.
- Terraform, GitHub Actions, and CI/CD pipelines.
Source intake
- GitHub repository access is the default intake path for connected source.
- Approved .zip archive intake is available when a repository handoff is not practical.
- One primary repository is easiest; multi-repo systems can be assessed once the delivery boundary is agreed.
Fit boundaries
- Shipward works best with mainstream web, API, SaaS, and AI-built MVP codebases where the repository, runtime, data stores, and deployment path can be inspected.
- Shipward can usually make an early fit decision before a recoverability audit.
- Safety-critical systems, embedded or firmware-heavy systems, smart contracts, malware or security exploit tooling, and closed-source systems without inspectable code are not good fits for the current service.