/Services
AWS cloud engineering and DevOps services
From the first line of code to 24/7 operations: we build applications and AI-native products, the platform they run on, and we keep security and cost under control.
AI-native: AWS + Claude
Claude, agents and MCP in production, on Amazon Bedrock.
Claude on Amazon Bedrock
Claude model integration through Amazon Bedrock: model selection, prompt caching, tool use, guardrails, evaluation and quotas, with your data staying in your AWS account.
Learn moreClaude Code for teams
Claude Code adoption for engineering teams: setup, CLAUDE.md, permissions, MCP, CI/CD, code review, credential security and measuring the impact on delivery.
Learn moreMCP servers
Custom MCP servers that connect Claude and other agents to your internal systems and AWS, with authentication, least privilege, audit logging and deployment in your account.
Learn moreAI training
AI workshops for engineering teams: Claude Code, agents and RAG on Amazon Bedrock, MCP servers and AI security, with exercises built on your own codebase.
Learn moreAI-native on AWS
Products and platforms with generative AI at the core: Amazon Bedrock, agents, RAG, evaluation, guardrails, LLMOps and inference costs under control.
Learn moreAI Agents with Bedrock
Agents that carry out real tasks with Amazon Bedrock and AgentCore: tool use, MCP, Knowledge Bases, multi-agent orchestration, identity and observability.
Learn moreAI and machine learning
Machine learning on AWS with SageMaker: predictive models in production, with MLOps pipelines, a model registry, drift monitoring and retraining.
Learn moreGenerative AI on AWS
Generative AI on AWS with Amazon Bedrock: assistants, RAG over your documents and GenAI features in your product, with evaluations, guardrails and cost control.
Learn moreApps and development on AWS
We build the product and the platform it runs on.
AWS Application Development
Backends, APIs, frontends on CloudFront and Amplify, databases and CI/CD: cloud-native software built on AWS and ready to run in production.
Learn moreServerless on AWS
Lambda, API Gateway, Step Functions, EventBridge, DynamoDB and SQS: event-driven architectures that scale on their own, tolerate failures and bill only for real usage.
Learn moreKubernetes on Amazon EKS
Amazon EKS clusters with Karpenter, Helm and Argo CD, pod-level security and zero-downtime upgrades, run through Terraform and GitOps.
Learn moreDevOps and platform
Ship fast without breaking production.
DevOps with AI agents
DevOps operations assisted by AI agents: Terraform changes by pull request, alert triage, cost reviews, runbooks and postmortems, always with human approval.
Learn moreDevOps as a Service
An ongoing external DevOps team for your AWS infrastructure: Terraform, CI/CD, security, costs and on-call coverage, on a monthly subscription.
Learn morePlatform Engineering
An internal developer platform on AWS with golden paths, Backstage and Terraform self-service, for autonomous teams that ship quickly and safely.
Learn moreObservability and SRE
CloudWatch, OpenTelemetry and Grafana, SLOs with error budgets, actionable alerts, incident management and postmortems to run AWS on data.
Learn moreBuilding on AWS
AWS architecture designed and built from scratch: accounts, networking, access, CI/CD and observability in Terraform, ready to grow without a rebuild.
Learn morePerformance and scalability
AWS performance and scalability: load testing, bottleneck analysis and tuning of the database, caching and auto scaling, measured before and after.
Learn moreIncidents and availability
AWS incident response and high availability: stabilization, root cause analysis, Multi-AZ architecture and disaster recovery with defined RTO and RPO.
Learn moreMigration and modernization
From your data center or previous cloud to AWS, without surprises.
AWS migration
AWS migration from a data center or another cloud: dependency mapping, migration waves, a Terraform landing zone and cutovers with validation and a tested rollback.
Learn moreCloud modernization
AWS application modernization: from mutable servers and monoliths to containers, serverless and managed services, in stages and without stalling the product.
Learn moreSecurity, governance and cost
Accounts, access, compliance and FinOps under control.
Well-Architected Review
A review of your workloads across the 6 AWS Well-Architected pillars, with Generative AI and SaaS lenses and a remediation plan you can actually execute.
Learn moreAWS Landing Zone
A multi-account AWS foundation with Control Tower, Organizations, SCPs, IAM Identity Center and centralized logging, automated in Terraform.
Learn moreSecurity and compliance
AWS security: access, network, encryption and secrets fixed, with automated controls and continuous evidence for SOC 2, ISO 27001, PCI DSS, HIPAA or Spain's National Security Framework (ENS).
Learn moreFinOps and cost optimization
AWS cost optimization: spend visibility, rightsizing, Savings Plans, removal of idle resources and FinOps practices that keep the results in place.
Learn moreData on AWS
Data ready for analytics and AI.
/FAQ
Frequently asked questions
Another question? Write to hello@nubent.com and an engineer will answer.
Where should we start if our AWS platform grew without a plan?
Almost always with an assessment or an AWS Well-Architected Review. You get a clear picture of security risks, avoidable cost and fragile operational points, plus a prioritized roadmap. From there you decide whether we execute, your team does, or both.
Can you combine several services in one project?
Yes, and it is usually the most efficient option. An AWS migration, for example, normally includes the landing zone, CI/CD pipelines, observability and FinOps from the start. We build a single phased plan with one team covering every front, instead of separate vendors.
Do you work on fixed-scope projects or on an ongoing basis?
Both. Projects with a clear scope (a migration, a landing zone, a first AI agent) are priced by phases and deliverables. For ongoing operations and evolution we offer DevOps as a Service, with a dedicated team, optional on-call and a shared backlog.
Next step
What should we build next on AWS?
30 minutes with an engineer. Concrete next steps, whether or not you work with us.