AI software house · Curitiba, BrazilAI software house · Curitiba · since 2017

Artificial intelligence systems in production.

We build and operate AI solutions for your company: computer vision, copilots, forecasting and MLOps.

A free 30-minute technical assessment. A proposal with scope and a delivery date within 48 business hours.

Clearly defined scopeDeliverables and acceptance criteria defined before the first line of code
The code is yoursRepositories, models and pipelines inside your company's environment
Architecture of a solution

From data to system.

Connected parts that turn information into applications you actually use.

01 Data sources
CamerasVideo and images
DocumentsInternal knowledge
OperationsBusiness data
02 Kroon engineering
Artificial intelligence
integrated into operations
ModelsAPIsPipelines

Evaluation · Integration · Monitoring

03 Applications
EventsDetect and alert
AnswersLook up and find
ForecastsAnticipate and plan
Illustrative architecture. Every project connects the sources and applications in your own context.
01Philosophy

Technical rigor. Business judgment.

At Kroon Software House every project starts where most consultancies stop: with the real problem. We combine deep technical skill in artificial intelligence and infrastructure with a genuine understanding of your context, to deliver solutions that work in production — not just in slide decks.

We do not sell technology for its own sake. We build systems that scale, that monitor themselves and that produce measurable value, from raw data to the informed decision. And we do it with the commitment that separates a software house from a consultancy: clearly defined scope, a declared deadline and accountability for the outcome.

02What we do

What we do

We build artificial intelligence systems that reach production and keep working: computer vision, copilots over documents, operations forecasting, the infrastructure that sustains them and the security that protects them. Every project starts from your operation's problem, not from the technology.

AI development

Custom models for specific business challenges, with the acceptance criteria declared before the first experiment.

Computer vision

Computer Vision in Production

RTSP cameras, video files or live streams start producing reliable events: counting, presence, PPE, queues, zone occupancy, line defects and access control.

  • An inference pipeline with a defined accelerator (on-premises GPU or cloud)
  • An event dashboard, search by period and alerts by webhook, email or WhatsApp
  • A target accuracy declared in the proposal, measured on validation cameras
  • Deployment on your own server or in the cloud, with an operations manual
Who it is for Retail, manufacturing, logistics and physical security Success Fewer unattended events and less loss per store
Generative AI

Enterprise Copilot over your documents

Search and answers with source citations over internal documents, standards, manuals and tickets, inside your environment, with per-user access control and an audit trail.

  • Document ingestion and indexing, including scanned PDFs
  • An automatic evaluation layer: faithfulness, coverage and correct refusal
  • A web interface and API, with usage logging and per-department permissions
  • A plan for refreshing the index as documents change
Who it is for Legal, compliance, operations and internal support Success Response time and the share of answers that carry a source
Forecasting and optimization

Operations Forecasting and Optimization

Demand, inventory, predictive maintenance and routing — always measured against a published baseline. If the model does not beat the simple baseline, it does not go to production.

  • A transparent baseline (moving average, current rule or last cycle)
  • A forecasting model with confidence intervals and error monitoring
  • Recommended actions, not just charts
  • A report on the gain measured in the first quarter in production
Who it is for Manufacturing, distribution and field services Success Forecast error below the baseline in production

Platform and operations

From proof of concept to a system in production, with high availability, controlled cost and observability from day one.

Platform

MLOps Platforms and Pipelines

The platform that keeps the model working: pipelines, versioning, inference and observability, operated by Kroon, with the code inside your company's environment.

  • CI/CD for models, version registry and reproducible training
  • Inference on Kubernetes with autoscaling and an hourly cost ceiling
  • Monitoring of model drift, latency and data quality in production
  • A quarterly review of cost per inference and capacity
Who it is for Companies that already have a model and no operation around it Success Operation availability, cost per inference and actionable alerts
Squad

Dedicated AI Squad

An engineering team allocated to your product: a machine learning engineer, a platform engineer and a part-time tech lead, in two-week sprints with the scope agreed at the start of each cycle.

  • A shared backlog and joint prioritization every sprint
  • Delivery metrics reported at the end of each cycle
  • Knowledge transfer: mandatory documentation and pairing
  • Guaranteed handover: your team takes over whenever you want
Who it is for Teams that already have a product and need to accelerate their AI roadmap Success Sprints delivered and roadmap met

Security

Protection for AI systems already running in production, from hardening through to penetration testing.

Cybersecurity

AI Application and Infrastructure Security

Hardening, detection and response for systems already running in production: a mapped attack surface, secrets and access under control, anomaly detection in logs and an incident response plan your team can execute without us.

  • An attack-surface map, with a review of access, secrets and dependencies
  • Hardening of cluster, inference and pipelines, with least-privilege policy
  • Anomaly detection in logs and events, wired into the alerts you already use
  • An incident response plan, rehearsed in a simulation with your team
Who it is for Engineering and security teams with an AI system in production Success Detection and containment times measured in simulation
Pentest

Penetration Testing for Applications, APIs and Models

Penetration testing on the scope that matters: application, API, inference infrastructure and, where one exists, the model itself — prompt injection, inference leakage and endpoint abuse. A report with step-by-step reproduction and retested fixes.

  • Scope and rules of engagement defined before the first test
  • Manual and automated testing of the application, API and inference infrastructure
  • AI-specific cases: prompt injection, inference leakage and endpoint abuse
  • A report with step-by-step reproduction, severity and retesting of fixes
Who it is for Products with sensitive data or an audit requirement Success Critical findings fixed and retested

We also work with Machine Learning and Deep Learning · Natural Language Processing · Autonomous agents · Cloud architecture · Kubernetes

03Method

The Kroon method, in five named stages.

Every Kroon project follows the same delivery design. You know which stage you are in, what comes out of it and what it costs before authorizing the next one.

Week 0

Technical assessment

Thirty minutes with the decision maker and thirty with the people who operate. We assess the data available, the network constraints and what already exists in production. No corporate slide deck.

A written opinion within 48h: feasible, feasible with conditions, or we do not take it on.
Week 1

Scope, investment and acceptance criteria

A closed proposal: deliverables, go-live date, investment and the metric that defines success. Signed by both sides before the first line of code.

A proposal with scope, deadline and an objective acceptance criterion.
Weeks 2–3

Proof of value with your data

A model running on your real data, on your infrastructure, measured against the same acceptance criterion, as early as possible — because this is where the risk shows up.

The metric measured and a live demonstration. This is where the decision to continue or stop is made.
Weeks 4–8

Production and acceptance

Deployment with a dashboard, alerts, authentication and observability. Acceptance with the people who will really use it, a recorded 2-hour training session and a documented operations manual.

System in production, acceptance signed and a 30-day warranty.
Afterwards

Support and evolution

Twelve months of minimum SLA: monitored availability, model drift correction and two evolution windows per quarter, with a usage and cost-per-inference report.

A quarterly report and the right to take over the system with a documented handover.
04Technology

Technology

Production-grade tools for performance without compromise. We choose every component by its cost of running in production, not by novelty, and we record the choice in the proposal.

Computer vision

OpenCVUltralytics YOLODetectron2TensorRTDeepStreamGStreamer

Modeling and research

PythonPyTorchTensorFlowscikit-learnHugging Face

Data and language

PostgreSQLpgvectorAirflowSparkdbtFastAPI

Platform and inference

DockerKubernetesMLflowTritonONNXTerraform

Cloud and observability

AWSGCPAzureGrafanaPrometheusOpenTelemetry

On-premises environments are supported too: the entire stack above runs on your own Kubernetes, with no dependency on a public cloud.

05FAQ

Frequently asked questions

The objections that come up in almost every first meeting, answered the same way we would answer them live.

Do you use our data?
Yes, and only under a data processing agreement signed before the first access. We follow LGPD and GDPR strictly, from collection to disposal. You choose the arrangement: training inside your environment (the default when there is personal data or images of identifiable people), prior anonymization, or a dedicated cloud account under your control. No client data ever enters a model that serves another client, and the dataset used in the proof of value is identified in writing.
What if the model does not reach the agreed acceptance criterion?
That is precisely what the proof of value in week 3 is for. We measure the agreed metric on your data and your infrastructure before building the rest. If the target is not met and there is no declared technical path, the project ends there, and you keep the code, the experiments and the measurement report to carry on by yourself.
How long until the first usable result?
Three weeks to a proof of value measured on your data, and six to eight weeks to go live in most computer vision and enterprise copilot scopes. Forecasting projects take longer because of the baseline comparison cycle: generally eight weeks.
Do you replace our technology team?
No. We work in your team's repository, with code review in both directions, weekly pairing and mandatory documentation. Every project includes a guaranteed handover: whenever you want, your team takes over the operation, with a manual, videos and 30 days of side-by-side support.
Do you work with companies outside Brazil?
Yes. We work in Portuguese, English and Spanish and cover meetings from the Lisbon time zone to the west coast of the United States. For data with a residency requirement, we keep training and inference in the region you choose.
Do you do a free proof of concept?
No. A free proof of concept usually means a model rushed out on data that does not represent production. The 30-minute assessment and the written opinion are free; the proof of value is the first stage of the project, with its own scope and acceptance criteria, not a courtesy sample.
06Contact

Talk to an engineer.

Tell us the context of your project: data available, deadline and infrastructure constraints. Every message is read by an engineer, and we reply with feasibility, timeline and investment range.

Reply within 4 business hours

Message received. An engineer will reply within 4 business hours.

We will read your context and come back with feasibility, timeline and investment range — or with the one question we still need answered.

Reference KRN-0000
Keep this number

Next steps

  1. 1A technical read of your context by an engineer, not by a sales team.
  2. 2A 30-minute assessment to confirm the data available, the cameras or the document base.
  3. 3A proposal with clearly defined scope, acceptance criteria and a delivery date, within 48 business hours.