Architecture diagrams, operational dashboards, and engineering plans on a work surface.

Founded in 2026. Built on decades of experience.

Engineering that works so well your users never notice.

Independent consulting for cloud, AI, security, resilience, performance, and software systems.

We guide first and build second. Every recommendation is backed by evidence you can inspect — not hype, vendor quotas, or partner loyalty.

Experience behind the company

The company was founded in 2026. The record behind it belongs to its founder, earned in prior roles — not presented as CoreFeld client work.

  • 24 years Building and operating production systems, from public-facing government platforms to modern cloud and AI workloads.
  • $4M → $2.5M Annual cloud spend cut by $1.5M for a federal health agency, in a prior role, through automated cost-optimization tooling and architecture change.
  • AWS certified Three active certifications — Security – Specialty, DevOps Engineer – Professional, Developer – Associate — and continuous AWS certification since 2018.
  • A decade inside CMS Four named CMS programs — Office of Communications, QPP, MACPRO, and MDCT — as agency staff and as a vendor, plus the Social Security Administration and state Medicaid platforms.

Guide first. Build second.

Start with the problem, not the platform.

Most expensive technical mistakes are decisions, not code. CoreFeld helps organizations make a clear, defensible call before they commit to a migration, rewrite, AI system, cloud provider, or architecture path — and then builds it when building is the right answer.

Services

Senior engineering across the hard parts of modern systems.

Cloud Architecture

Design a cloud footprint you can afford, operate, and leave if you need to.

AWS, Azure, GCP, hybrid, multi-cloud, infrastructure as code, landing zones, observability, portability planning.

AI Engineering

Find out whether AI earns its place in your workflow — then build the part that does.

AI fit assessment, custom AI applications, enterprise assistants, RAG, workflow automation, model evaluation, governance.

Security

Make the architecture itself the control, not a layer of tools bolted on afterward.

Secure architecture, threat modeling, DevSecOps, repository protection, identity, secrets, encryption, incident readiness.

Disaster Recovery

Know what you can recover, how fast, and what happens the day you have to prove it.

Business continuity, restore testing, ransomware recovery, multi-region planning, immutable backups, runbooks, RTO and RPO.

Platform Engineering

Give delivery teams a safe default path so shipping stops being an act of courage.

CI/CD, developer platforms, golden paths, deployment safety, policy as code, secure build pipelines, release automation.

Software Engineering

Build and modernize systems your team can still understand a year from now.

Custom applications, APIs, integrations, distributed systems, modernization, architecture reviews, project rescue.

Performance

Replace opinions about what is slow with measurements of what is slow.

Profiling, load testing, benchmarking, latency, throughput, capacity planning, database tuning, cost-performance decisions.

Cost Optimization

Cut the bill without cutting the reliability you are paying for.

Cloud cost assessment, rightsizing, licensing, data transfer, storage, TCO, build-versus-buy, expensive-default removal.

Technical Leadership

Senior architectural judgment on the org chart without a full-time executive hire.

Fractional CTO, chief architect, technical strategy, due diligence, vendor evaluation, architecture governance, mentoring.

Approach

Every major recommendation should survive measurement.

01

Understand

Clarify the business problem, users, constraints, risks, and success criteria.

02

Measure

Use benchmarks, cost models, threat models, failure testing, and operational review.

03

Decide

Compare realistic paths, including simpler options and doing nothing when that is best.

04

Build

Implement systems that are documented, observable, secure, testable, and operable.

Evidence-based engineering

The right technology, not the loudest technology.

We do not recommend AI when conventional software, automation, process change, or no software is the better answer.

We do not push AWS, Azure, GCP, on-premises, hybrid, or multi-cloud designs without a reason the client can inspect.

We optimize total cost, not merely the cloud bill.

Where we stand

The better you know a provider, the more honest you have to be about it.

AWS

We know AWS deeply, and that depth is exactly why we are candid about where it falls short. No provider earns deference here for its size. We build on AWS, and build it well, when it is the best option for the problem or when it is what your organization requires.

Azure

We know Azure deeply, and we hold it to exactly the same standard. Depth earns candor, not deference. We build on Azure, and build it well, when it fits the problem or when it is what your organization requires.

Cloudflare & GCP

We know them both and hold them to the same standard. So far they have given us little to be candid about. That may change as depth grows — and if it does, you will hear it from us first.

Depth produces candor. Anyone who knows a platform well and thinks critically ends up with a clear-eyed view of where it falls short, and we hold one for every provider we work in. We walk through the parts that touch your architecture during the engagement, where they can actually be acted on, rather than litigating them on a marketing page. Being candid about a provider does not make it useless — it is what makes our recommendation of it mean something.

We are not anyone's partner. No partner tiers, no resale margins, no agreements that require us to praise a vendor's roadmap. When a provider oversells a capability or a default quietly costs you money, we say so plainly — and we bring the strategies that keep your architecture free to move: exit paths, portability planning, egress-cost math, and expensive-default removal.

That independence is what you actually need in a consultancy.

About CoreFeld

You get engineers, not a sales team.

CoreFeld is an engineering firm based in Rochester, Minnesota, founded in 2026 by Jonathan “Jon” Holman — 24 years of professional IT experience across federal health systems, regulated public-sector platforms, enterprise cloud practices, and AI product engineering.

Our team brings decades of hands-on experience across several generations of technology. That span is what makes it possible to tell durable innovation from hype, and we add the depth an engagement actually calls for rather than headcount to bill against.

Whoever does the analysis is who you talk to. Work is not handed to a junior team after the sale, and everyone who touches your system is named to you before they start.

Available now for corp-to-corp subcontracting with primes and boutiques delivering federal health work, and for direct engagements. Resume, rate, and availability on request — ask and you get them the same day.

We do not invent client lists, staff biographies, offices, or case studies. Every number on this page is founder-attributed and earned in a prior role, and it is labeled that way.

Contact

Bring the hard technical problem.

We will help decide what should be built, what should be changed, and what should be left alone.

  • Replies come from a person, usually within one business day.
  • The first conversation is a scoping call, not a sales call, and it is free.
  • Recruiters and primes: say so in a line and you get the resume, rate, and availability the same day.
  • Prefer email? hello@corefeld.com

We review every inquiry before recommending a next step. We do not sell or share what you send.