Software development · Salt Lake City, UT
Software development for Salt Lake City companies
Your product was built by a founding team moving fast, and now every change breaks something and the people who know why are busy selling. Our senior engineers join your team and make the platform safe to change, with tests, a deploy you can roll back and documentation your next hire can read. Along the Wasatch Front that's a founder-run software company on Silicon Slopes, or a Salt Lake distributor whose ordering system grew up with it.
Founded
2017, and still independent
Bench
115+ engineers, 80 Databricks-certified
Experience
Fifteen years average, per engineer
Serving
Salt Lake City, Provo, Lehi, Ogden
A substantial fintech and software base along the Wasatch Front, a large integrated health system beside it, and an unusually high share of companies still run by their founders. If that's you, you want the AI system in production and its operating cost known, without a transformation programme in front of it.
AzureTechFabric is a Databricks partner with an award-winning Databricks engineering team, 80 of them Databricks-certified, and a Temporal partner. Where a system reaches past the workspace we build on Azure, AWS and Google Cloud.
What software development covers
Web applications
Applications built to be changed safely years after the original team has moved on. That means tests that mean something, seams where the business logic can move, and a deployment nobody is afraid of.
Mobile applications
iOS and Android, built as products rather than as ports. The maintenance story is decided at the start, while it is still cheap.
APIs and integration
The seams between systems, done once and properly. Most of the expensive failures we are called into are integration failures wearing another name.
Data platforms
The layer underneath the application, on Databricks, Azure, AWS or Google Cloud. If the reporting and the application disagree, the platform is the reason.
Modernisation of what exists
Often the work arrives as something already built that has become hard to change. We would rather read it and tell you honestly whether it is worth keeping than sell a rewrite you may not need.
Durable, auditable workflows
Processes that take days, call several systems and must never half-complete. Getting that right is a different discipline from getting a request handler right, and it is where we spend most of our time.
App development in Salt Lake City
Fintech and healthcare products here are often founder-led and moving fast, with an app that has to be handed to a team that keeps changing it. We build it with the maintenance story decided at the start, when it is still cheap.
Mobile app developmentDynamics 365 consultants in Salt Lake City
Utah's direct-selling companies, many of them in Provo, Orem and Lehi, pay distributor commissions out of several entities at once, and Dynamics 365 Business Central keeps that beside finance and inventory, as it does for Salt Lake City's fintech lenders and Ogden's outdoor gear makers. We implement it with Dynamics 365 CRM and automate month-end with Power Automate.
The first enterprise deal brings the questionnaire
Plenty of software and fintech companies between Salt Lake City and Lehi are still run by their founders, and the first large customer usually arrives with a security questionnaire and a SOC 2 Type II requirement. A fintech partnering with one of Utah's industrial banks, chartered by the state's Department of Financial Institutions, gets a second list on top, because the bank's examiners expect it to oversee its vendors.
Most founders treat that as a compliance project for after the build, and they lose two quarters to it. We'd rather the platform produce its own evidence from day one. Access reviews come from the grant tables, change history from the deploy pipeline, and the audit log is written by the system, so the questionnaire turns into a document exercise and the Type II window opens on something already running.
Your stack gets read against the Trust Services Criteria your auditor will test, and we mark which controls the platform can evidence by itself. Single sign-on with role-based access goes in first, then a single pipeline for every production change, then log retention long enough to cover the observation period. The product roadmap keeps moving beside it.
Clients we have done this for
If your application database has quietly become your warehouse, read how TotalLoop moved. It started as a cloud-native platform on Azure with its own CRM and a sales dashboard, and later moved off Cosmos DB and SQL Server onto Databricks Lakebase, converted with TechFabric Airlift and cut over in reversible waves.
B2B ecommerce
DealerIQ
TotalLoop finds a dealership's customers with equity in their vehicle and matches them to cars on the lot. DealerIQ brought the idea and the dealership know-how, and our senior engineers worked inside its team to build it on Azure, test it with one dealer account and ship a lean first version. Later we moved it off Cosmos DB and SQL Server onto Databricks Lakebase, in waves that could each be rolled back.
How an engagement runs
01
A technical conversation
Not a sales call. An engineer, asking what you are trying to do, what has been tried and what it will actually take. Where the work needs them, product and design people join the same conversation.
02
Two weeks, fixed fee
A short assessment ending in a written plan with a scope, a sequence and a number. You own the document whether or not you carry on with us.
03
Build with your team in the repo
Senior throughout, and no pyramid with one architect over a floor of juniors. The person in your standup is the person writing the code.
04
Run it
We stay on the pager. Nobody designs a fragile thing they will personally be woken by, which is most of why this arrangement produces different software.
Two weeks, fixed fee, and a written plan whether or not you build it with us.
Tell an engineer what you want to build
A senior engineer reads it and replies within one business day, usually with the questions that decide the first two weeks.
Around Salt Lake City
KubeCon at the Salt Palace
KubeCon + CloudNativeCon North America chose the Salt Palace Convention Center for its 2026 edition, four days on West Temple for people who run Kubernetes for a living. The year-round rooms are older. SALT, the nonprofit that met for years as the Utah Java Users Group, has been going since 1999 and now usually meets at Lucid Software in South Jordan, while SLCPython gathers on the first Wednesday.
Software you commission will outlive the contract, and somebody in Utah will end up maintaining it. The size of those rooms is a fair guide to which stacks a team here can keep staffed, and JavaScript is the obvious case, with UtahJS running monthly meetups in Salt Lake City, Lehi and Logan and a conference each September. Pick a language with a local community and the second team inherits something familiar.
The Salt Lake City-Murray metro area. Utah: Salt Lake and Tooele counties.
Lighter shape: the city itself. Dot: downtown. County boundaries from the US Census Bureau, 2023.
User group · Monthly, Thursday evenings
SALT: Software Aficionados Learning Together (formerly Utah Java Users Group, UJUG)
Meeting since 1999, SALT is proof that a Java codebase you commission today will have local engineers to maintain it for decades.
SALT, a nonprofit user group. Lucid Software, 10355 S Jordan Gateway, South Jordan.
User group · Monthly meetups, plus an annual conference in September
UtahJS (meetups and UtahJS Conf)
With monthly meetups in three cities and a conference every fall, UtahJS suggests JavaScript is among the easiest stacks to staff along the Wasatch Front.
Volunteer organisers. Software Technology Group, 555 S 300 E; also Lehi and Sandy.
User group · Monthly, usually the first Wednesday evening
Salt Lake City Python (SLCPython)
Working and aspiring programmers share the room, so a hiring manager learns quickly what a Python developer here can do in their first year.
Volunteer organisers. Rotates between The Shop, 350 E 400 S, and Salt Lake County libraries.
User group · Several events a year, plus DevFest SLC each September
GDG Salt Lake City (Google Developer Group)
Angular and Google Cloud come up often at these talks, useful context if your platform is built on either and you want local engineers who know them.
Google Developer Groups volunteers. Venues vary, including Salt Lake City Public Library, 210 E 400 S.
More in Salt Lake City (1)
- KubeCon + CloudNativeCon North America 2026
The North American edition of the CNCF's cloud native conference, covering Kubernetes, platform engineering and cloud native infrastructure, with co-located events around it.
9 to 12 November 2026. Salt Palace Convention Center, 90 S West Temple, Downtown.
Each listing was checked on its organiser's own page on 12 October 2026. Dates and venues move, so the link is the source.
FAQ
Software development in Salt Lake City: common questions
Do you work with Salt Lake City companies?
Yes, and with companies across the United States. Arizona does not observe daylight saving, so from November to March we are on the same clock as you and from March to November we are an hour behind. The working day overlaps almost completely.
Do you have an office in Salt Lake City?
The office is in Gilbert, Arizona, with teams in Amsterdam, Dnipro and Hyderabad. Delivery is remote or hybrid, and we travel for discovery, workshops and the opening weeks of a build.
We are founder-run and our first big customer wants SOC 2.
Then the useful thing is a platform that already produces the evidence, so the questionnaire becomes a document exercise. We would rather get one system into production with the trail built in than run a compliance programme alongside a build.
What kinds of custom software do you build?
Web applications, mobile applications, APIs and the data platforms underneath them. The work we do best is the sort that has to be governed and auditable, where a wrong write is expensive and somebody has to be able to explain afterwards what changed and why.
Do you take over an existing codebase?
Often, yes. A good part of the work arrives as something already built that has become hard to change. We would rather read it and tell you honestly whether it is worth keeping than sell you a rewrite you may not need.
Where to go deeper
Web application development
Applications that hold up on the thousandth day
Mobile application development
iOS and Android, built to be maintained
Ecommerce development
The storefront and the ERP behind it
APIs and integration
The seams between systems, done once
Published work
Named clients and checkable outcomes
Also in Salt Lake City
What else we build for Salt Lake City companies.
AI consulting and development in Salt Lake City
Your AI pilot answers well in the demo, and nobody can yet say what it'll cost a month or whether this week's change made it better.
Databricks consulting in Salt Lake City
Founder-run fintech and software companies here usually have a Postgres that became the warehouse by accident and a BI tool pointed at it.
Software development elsewhere
The same work, in other metros. The full list is here.
New York, NY
New York, Brooklyn, Queens
Boston, MA
Boston, Cambridge, Somerville
Atlanta, GA
Atlanta, Alpharetta, Marietta
Miami, FL
Miami, Fort Lauderdale, Coral Gables
Charlotte, NC
Charlotte, Concord, Gastonia
Philadelphia, PA
Philadelphia, King of Prussia, Wilmington
Detroit, MI
Detroit, Ann Arbor, Dearborn
Tampa, FL
Tampa, St. Petersburg, Clearwater
Chicago, IL
Chicago, Naperville, Evanston
Phoenix · Dallas · Houston · Austin · Nashville · Minneapolis · Denver · Los Angeles · San Francisco · Seattle · San Diego · Washington · Orlando · Raleigh · Portland