Services
Cloud Software Development Services
Build the application around the cloud it actually needs.
Code & Pepper's cloud software development services cover the application and the infrastructure around it, from architecture and backend engineering to deployment, integrations, observability and production changes.
Our client, Pelago runs a digital-health platform on AWS services including Lambda, DynamoDB, RDS, SNS, SQS and EventBridge.
We build new cloud applications, move existing software into cloud environments and change systems whose current architecture is getting in the way.
Cloud engineering already inside real products
Our cloud work spans applications where infrastructure choices affect the product itself, from data-heavy platforms to financial and healthcare software.
Pelago
AWS serverless services inside a live digital-health platform.
Pelago uses Lambda, DynamoDB, RDS, SNS, SQS, EventBridge and Cognito across its application environment.
Code & Pepper engineers work on the Node.js backend, authentication, shared libraries, application performance and deployment through CircleCI.
The cloud architecture sits inside the product work instead of being treated as a separate infrastructure project.

Global Trade Alert
A locally hosted data platform rebuilt for cloud deployment.
Global Trade Alert started with a locally hosted system supporting a large international trade-policy database.
Code & Pepper redesigned parts of the data architecture, checked database dependencies, optimised data filters, prepared historical data for migration and configured the infrastructure required for the new environment.
The same team also worked on the application, admin interface and data-processing workflows.

NoMo
A backend refactor followed by deployment to Microsoft Azure.
Code & Pepper rewrote NoMo's backend from Java to C# and .NET Core and introduced hexagonal architecture before deploying the application to Azure.
The environment used Azure App Service, SQL Database, Application Insights, Docker and Azure Notification Hub. The product connected with 16 banks through its financial-data integrations.
What our cloud software development services cover
The scope can include a complete cloud application or the parts of an existing system that need to change.
Cloud application development
Build web, mobile and backend software around cloud services selected for the application's real workload.
That can include:
- Backend services
- Web applications
- Mobile backends
- Authentication and permissions
- Databases
- File and object storage
- Background processing
- Notifications
- Scheduled workloads
- Internal tools
The cloud provider supplies infrastructure and managed services. The application architecture still determines how those pieces behave together.
APIs and distributed services
Cloud products often depend on communication between internal services, external providers and client applications.
We build REST and GraphQL APIs, asynchronous processing, webhooks, event-driven workflows and service integrations.
A useful design covers failure behaviour too: retries, duplicate events, timeouts, partial failures and services becoming temporarily unavailable.
Our API Development Services cover those boundaries when integration work becomes a substantial part of the product.
Data-intensive applications
Cloud platforms make storage and compute easier to provision. They do not decide how data should move through the product.
We work on ingestion, transformation, databases, data-processing jobs and application services that consume that data.
Global Trade Alert required dependency checks, historical-data preparation and changes to data architecture before the platform was ready for cloud deployment.
Cloud infrastructure
Application and infrastructure decisions need to agree on deployment, availability and workload behaviour.
Our work can cover:
- AWS
- Microsoft Azure
- Google Cloud
- Infrastructure as Code
- Containers
- Serverless services
- Managed databases
- Networking
- Environment configuration
- Monitoring
For AWS-specific architecture and services, AWS Consulting goes deeper into that platform.
Cloud architecture changes product decisions
Cloud architecture becomes useful when it reflects how the software behaves in production.
Managed service or application code
A managed database, queue or authentication service can remove operating work from the engineering team.
It also introduces provider-specific behaviour, limits and pricing.
The decision should account for how central that component is to the product and how difficult replacing it would be later.
Serverless or long-running compute
Serverless infrastructure fits event-driven work, variable demand and services that can operate within the platform's execution model.
Long-running applications, predictable workloads and processes with different resource behaviour may fit containers or conventional compute better.
Pelago uses several AWS serverless services because they match parts of its application architecture. That does not make the same pattern the default for every product.
One service or several
Splitting an application into services creates independent deployment and scaling boundaries.
It also creates network calls, distributed state, additional monitoring and more failure modes.
A smaller product may be easier to operate with fewer boundaries. We introduce them when the application or organisation has a concrete reason for them.
Where the data lives
Database location, storage, backups, regions and data transfer affect performance, cost and regulatory requirements.
The decision becomes more important when the product works with financial records, healthcare information or other sensitive data.
Our Regulated Software Development work covers products where infrastructure decisions have to respect those operating constraints.
Moving existing software to the cloud
Cloud migration starts with understanding the application that already exists.
The useful questions concern dependencies, data, deployment, external systems and which parts of the architecture should change during the move.
Application assessment
Map what the software depends on before changing its environment.
That can include:
- Runtime and frameworks
- Databases
- File storage
- Network dependencies
- External APIs
- Background jobs
- Authentication
- Scheduled processes
- Deployment
- Monitoring
A migration plan should distinguish components that can move largely unchanged from components that need engineering work.
Architecture changes
Some applications benefit from refactoring during migration.
NoMo moved to Azure after its backend was rewritten and hexagonal architecture was introduced. Global Trade Alert needed data-architecture work and database dependency checks before cloud deployment.
Migration can therefore include application engineering, database changes, infrastructure work or all three.
Deployment and cutover
The new environment needs a defined path to production.
That covers infrastructure provisioning, deployment automation, data migration, testing, monitoring, rollback and the cutover itself.
Our DevOps Services cover CI/CD, Infrastructure as Code and operational work around that delivery path.
Cloud-native development without architecture theatre
Cloud-native software uses cloud capabilities where they solve a product or operating problem.
That may mean managed databases, event services, serverless compute, containers, object storage or provider-managed authentication.
It does not require every application to use Kubernetes, microservices or dozens of independently deployed components.
The architecture should make the software easier to build, release or operate under its expected workload. Extra components need an engineering reason to exist.
Cloud software in regulated products
Cloud adoption in finance and healthcare carries constraints that ordinary SaaS products may not have.
Access control, data location, encryption, audit trails, backups, environment separation, availability and operational traceability can affect architecture before development starts.
Pelago uses AWS Cognito for authentication within its healthcare platform. Our broader work across financial and healthcare products also involves cloud infrastructure around sensitive data, external integrations and role-based access.
The applicable controls depend on the product, jurisdiction and client requirements. Code & Pepper works with the client's legal, compliance and security specialists where formal interpretation is required.
The FinTech Development Services and HealthTech Software Development pages cover those product-specific requirements in more depth.
Three ways to use Code & Pepper for cloud development
The engagement depends on what already exists inside the product and engineering organisation.
Build a new cloud product
Code & Pepper can cover product work, architecture, application engineering, cloud infrastructure, integrations, QA and release.
This model fits products where application and infrastructure decisions need to stay inside one delivery scope.
Modernise or migrate existing software
Bring us into a live system with software, users and infrastructure worth preserving.
The work can cover application changes, cloud migration, database work, integrations, deployment and continued development without assuming the whole system needs replacement.
When infrastructure cost is the main problem, Cloud Cost Optimization and Management focuses specifically on spend, rightsizing and cost controls.
Add cloud engineers to your team
A company that already owns architecture and delivery may need additional backend, cloud or DevOps capability.
Software Team Augmentation can add those engineers inside the existing roadmap and engineering process.
Cloud technology follows the workload
We work across the application and infrastructure layers needed to run cloud software in production.
Cloud platforms
- AWS
- Microsoft Azure
- Google Cloud
Application engineering
- Python
- Node.js
- TypeScript
- .NET
- Java
- Ruby
- React
- Angular
- React Native
Infrastructure and delivery
- Terraform
- AWS CDK
- CloudFormation
- Docker
- Kubernetes
- CI/CD
- Monitoring and observability
Architecture
- REST
- GraphQL
- Event-driven systems
- Queues
- Serverless
- Containers
- Managed databases
- Object storage
The stack should be explainable in terms of the application's workload and operating requirements.
Tell us what is running today.
Send us the application, current infrastructure, cloud provider if there is one, the main technical constraint and what needs to change.
Cloud software development FAQ
These questions usually affect architecture, migration scope or the team required.
What are cloud software development services?
They cover the engineering required to build or change software that runs on cloud infrastructure.
The scope can include application architecture, backend development, APIs, databases, cloud services, Infrastructure as Code, deployment, monitoring and migration.
Can Code & Pepper build a complete cloud application?
Yes.
We can work across product design, frontend, backend, integrations, QA, cloud infrastructure and deployment when the project requires one team across the full product.
Which cloud platforms does Code & Pepper work with?
Our engineering work covers AWS, Microsoft Azure and Google Cloud.
The platform choice depends on the existing environment, application requirements, team experience and services the product needs.
Can Code & Pepper migrate an existing application to the cloud?
Yes.
Migration can include application assessment, architecture changes, data migration, infrastructure provisioning, deployment automation, testing and production cutover.
The first step is understanding which parts of the existing application can move and which need engineering changes.
Do cloud applications need microservices or Kubernetes?
No.
Those patterns solve specific deployment, scaling and organisational problems. An application with fewer components may be easier to develop and operate.
We use them when the workload or team structure gives them a clear job.
Can you take over software that already runs in the cloud?
Yes.
We can join an existing AWS, Azure or Google Cloud environment to develop the application, change infrastructure, improve deployment, add integrations or continue production work.
The current architecture is assessed before deciding what should change.
How much does cloud software development cost?
Cost depends on the application scope, existing software, cloud architecture, data, integrations, availability requirements and the engineering responsibility Code & Pepper owns.
A backend service running on one managed database and a multi-application platform with event processing, several environments and regulated data require different teams and infrastructure.