And what is in the way. We will tell you honestly whether we can help, what it would take, and who from the team would run the work.
A single-tenant Kubernetes environment installed into the AWS account and network boundary you already operate. The first call is about your boundary and your workloads, and whether Drydock fits — if it does not, we say so on that call.
Cloud architecture, vertical AI builds, platform engagements. Send a paragraph about what you are trying to do; we will reply with whether we are the right team, and if not, who is.
Retrieval, document intelligence, agents, evaluation harnesses — production AI on Bedrock and Claude, with the infrastructure and governance layers carrying the weight rather than a demo notebook.
Questions about the reference architectures, the evaluation methodology, or anything else in the research library. These reach the engineers who wrote them.
We post roles when we are hiring for them. If the right role is not listed and you have already shipped something we would recognize, introduce yourself anyway.
One inbox, same address. Mark the subject line and it will route to the right person.
We do not run a sales pipeline. The person who reads your message is the person who would be on the engagement. If we are not the right fit, we tell you so — and point you somewhere that is.