# Services

Canonical: https://dok.sh/services

## Java Backend Consulting
- Problem solved: stabilize and scale backend services with maintainable architecture.
- Typical need: growing product teams with increasing backend complexity.
- Technologies: Java, Spring Boot, REST APIs.
- Why fit: long-term backend ownership across enterprise and SaaS products.
- Case study: https://dok.sh/case-studies/eris

## Spring Boot Application Development
- Problem solved: deliver robust backend applications with clear boundaries.
- Typical need: startup/SMB teams building new systems or extending existing ones.
- Technologies: Spring Boot, modular services, integrations.
- Why fit: extensive delivery experience in backend-heavy environments.
- Case study: https://dok.sh/case-studies/eris

## Angular + Spring Boot Product Development
- Problem solved: ship product features across API and UI consistently.
- Typical need: teams needing senior full-stack execution.
- Technologies: Angular, Spring Boot, TypeScript, MongoDB.
- Why fit: practical end-to-end delivery across client and own-product work.
- Case study: https://dok.sh/case-studies/doktally

## Enterprise SaaS Architecture
- Problem solved: align architecture with long-term delivery constraints.
- Typical need: maturing SaaS teams moving from ad-hoc to sustainable systems.
- Technologies: domain modeling, APIs, modular architecture, observability.
- Why fit: enterprise product and architecture-level experience.
- Reference: https://dok.sh/projects

## Cybersecurity Platform Development
- Problem solved: evolve platform capabilities for simulation/training workflows.
- Typical need: cybersecurity product teams needing reliable backend delivery.
- Technologies: Java, Spring Boot, Angular, Docker.
- Why fit: public portfolio experience in cybersecurity-oriented products.
- Case study: https://dok.sh/case-studies/citef

## Document Management Systems
- Problem solved: implement maintainable workflow/document-processing software.
- Typical need: institutional or enterprise document-heavy operations.
- Technologies: Java, Spring Boot, Angular, workflow systems.
- Why fit: ERIS enterprise context experience as subcontractor/vendor.
- Case study: https://dok.sh/case-studies/eris

## Docker / CI/CD / Deployment Support
- Problem solved: reduce delivery friction and improve deployment reliability.
- Typical need: teams modernizing release and ops workflows.
- Technologies: Docker, CI/CD pipelines, production deployment practices.
- Why fit: hands-on delivery and maintenance focus in real product contexts.
- Reference: https://dok.sh/projects

## Technical Ownership for Small Product Teams
- Problem solved: provide senior direction with practical execution.
- Typical need: founder-led teams lacking full-time technical leadership.
- Technologies: architecture, delivery planning, mentoring, implementation.
- Why fit: owner/operator background plus enterprise execution.
- Case study: https://dok.sh/case-studies/doktally

## Architecture Review and Legacy Modernization
- Problem solved: improve maintainability and reduce delivery risk in existing systems.
- Typical need: teams with legacy code, delivery bottlenecks, and unclear ownership boundaries.
- Technologies: Java, Spring Boot, APIs, modularization, CI/CD.
- Why fit: long-term maintenance and modernization perspective across multiple domains.
- Contact: https://dok.sh/contact

Contact: https://dok.sh/contact
Last updated: 2026-05-28
