AI in production, on your own cloud, with predictable cost.
We take assistants, agents and language models from pilot to production on AWS. Your data never leaves your account, every answer is traceable and the cost per query is known before launch.
Bedrock · SageMaker · open modelsData in your VPCEvaluation before deployment
Use cases
What we usually build.
We start with the case that already has data available and a measurable return. An assistant that saves support hours is worth more than ten demos.
Internal knowledge
Assistants over your documentation
Answers with source citations over manuals, contracts, tickets or wikis. Permissions inherited from your systems: each person only sees what they could already see.
RAG with per-document access control
Incremental sync from S3, SharePoint or Confluence
Precision and coverage metrics per collection
Operations
Agents that run tasks
Agents that query your APIs, open tickets, reconcile data or prepare reports, with human approval where the risk demands it.
Tools exposed via MCP or Lambda
Action, budget and time limits per agent
Full log of every step for audit
Documents
Extraction and classification
Invoices, contracts, medical reports or case files turned into structured data with validation and exception review.
Textract and multimodal models combined
Output schemas validated before writing to your database
Human review queue for doubtful cases
Platform
An AI platform for your team
A shared base so your developers can launch new cases in days: model access, evaluation, observability and spend control.
Model gateway with quotas per team
Evaluation sets and regression tests
Cost dashboards per use case and per model
Models and cost
We pick the model by task, not by hype.
Every case is evaluated with several models on your real data. We compare quality, latency and cost per thousand queries before deciding.
Task
Usual options
Decision criterion
Indicative cost
Reasoning and agents
Claude Fable 5.1, Claude Opus 5 via Bedrock
Quality on long tasks and tool use
High per query, low volume
High-volume chat and RAG
Claude Sonnet 5, Claude Haiku 4.5
Latency and cost per thousand queries
Medium / low
Classification and extraction
Haiku 4.5, open models on SageMaker
Precision on your validation set
Low, scalable
Regulated data
Open models in your VPC, private endpoints
Data residency and compliance requirements
Fixed per instance
Costs are calculated with your real volume during the assessment. No recommendation includes vendor commissions.
Process
From idea to production in four phases.
Discovery
1 week
Inventory of use cases, available data and risks. We leave with one or two prioritised cases and their estimated return.
Evaluated prototype
2 to 3 weeks
Working prototype on real data with an evaluation set. If quality does not reach the threshold, we say so here.
Production
4 to 8 weeks
Deployment in your account as infrastructure as code, with guardrails, observability and spend control.
Continuous improvement
Monthly, optional
Quality and cost review, model updates and expansion to new cases with your team in charge.
Principles
What we do not negotiate.
Data under your control
Everything runs in your AWS account. Bedrock models do not train on your data and private endpoints avoid going out to the internet.
Evaluation before opinion
Every prompt, model or index change goes through a versioned evaluation set. No numbers, no deployment.
Cost known upfront
Budget per use case, spend alerts and prompt caching where it cuts the bill without losing quality.
Humans where it matters
Actions that affect customers, money or personal data carry human approval and a full log.
Frequently asked questions
What we get asked before starting.
Is my data used to train models?
No. With Amazon Bedrock, input and output data is neither stored nor used for training. With open models on SageMaker, the model runs entirely in your account.
Do we need a data science team?
Not to start. Most cases are solved with available models, good data engineering and rigorous evaluation. We train your development team to maintain it.
How much does it cost to run an assistant in production?
It depends on volume and model. During the assessment we calculate the cost per query with your estimated traffic and propose the cheapest model that clears the quality threshold.
Can we comply with GDPR and sector regulations?
Yes. We choose a region in your jurisdiction, encryption with your KMS keys, private endpoints and access logging. We coordinate the impact assessment with your DPO when it applies.
Most teams pick a vector store from a benchmark chart and then discover the thing that hurts is metadata filtering, tenancy or reindexing. If you already run PostgreSQL, pgvector is usually the right answer for longer than people expect.
The cost per token looks obviously cheaper until you account for utilisation. GPUs bill by the hour whether or not anyone is asking questions, and that single fact decides most of these decisions.
A classifier on every request costs time and money on every request. What to check on input, what to check on output, and how to decide whether the guardrail is worth what it takes.