About the company
Independent since 2012.
R & T BrightLight Technologies, LLC is a software practice based in Panama City, Florida. We were founded to do one thing well: bring genuine enterprise engineering to companies that could never justify an enterprise engineering department.
How we work
Senior engineers, start to finish.
Senior engineers scope your project, design it, and build it. The people making the decisions are the people doing the work, and you talk to them directly rather than through an account manager.
We work the way agile is meant to work: in short cycles, each one ending with something real you can look at and react to. You are not handed a finished product months later and asked whether it was what you meant — you help steer it the whole way, while changes are still quick and cheap to make.
That rhythm is also what makes the end result better. Small corrections made early compound into a product that fits how you actually work and performs the way it should, instead of one that technically matches a document nobody has reread since the kickoff.
We also say no. If what you actually need is an off-the-shelf product rather than custom software, or if the work isn't something we'd do well, we'll tell you that before you spend money finding out.
Founded, and independently operated ever since
Of enterprise engineering experience behind the practice
States we take on work in, coast to coast
Sectors — defense and private — with contracts delivered in both
Company history
How the practice took shape.
Each phase of this company's work left something behind — a capability, a standard, or a hard lesson. All of it is still in use.
-
2012
Founded in Panama City, Florida
The company opens its doors as an independent software practice, procuring and delivering contracts across both the defense and private sectors — owning architecture, delivery, and quality end to end rather than staffing someone else's project.
-
2013 – 2015
The cloud years
Cloud infrastructure design for SaaS products and the RESTful services behind them. Customer onboarding automated end to end, eliminating manual setup for every new account. QA environments, build agents, and CI/CD pipelines stood up from scratch — the beginning of our insistence that pipelines come before features.
-
2015 – 2020
Enterprise scale
The work grew. A unified search platform consolidating 15M+ customer records from 30 disparate repositories. An enterprise electronic document signing platform built as multi-service REST with a backing SQL data layer. A mission-critical document delivery service routing to email, enterprise print, database, archival, and eDocs destinations, with anomaly tracking and daily reconciliation.
-
2018 – 2022
Standards, identity, and teaching
Homegrown identity management replaced with modern OpenID Connect at enterprise scale. Engineering standards — code review policy, coding standards, CI/CD, properly structured delivery teams — written and adopted broadly. Boot camps and curricula delivered in SQL design, advanced C#, and RESTful API development, a practice that continues today.
-
2022 – 2024
Cloud platform architecture
Backend platform architecture for business-critical revenue systems — service topology, data flow, and security model — with modern identity extended to secure every internal service behind them.
-
2024 – present
AI-native product development
The current chapter. A provider-agnostic AI architecture — one response schema served interchangeably by an on-device model, a model on a local network, or a cloud provider — shipped in our own product, Remedy Lab, so that it runs fully offline, fully private, at zero per-query inference cost.
-
July 2026
AI Discipline published
A field manual on engineering discipline in the age of agentic development, published independently through the company. It is the written form of the argument we make to every client.
What carried through
- Pipelines before features Every project since 2013 has had automated build, test, and deploy in place before the first feature was considered done.
- Identity is architecture Authentication and authorization get designed at the start, not retrofitted after a security review.
- One version of the truth Consolidating scattered data into something trustworthy is the highest-leverage work most companies aren't doing.
- Teach, don't gatekeep We document and train so your team can maintain what we build. Dependence isn't a business model.
How we operate
Three commitments we don't negotiate.
Estimates include the boring parts
Testing, deployment, documentation, security review, and store compliance are in the number we quote. A cheap estimate that omits them isn't cheaper — it just moves the cost somewhere you can't see it yet.
We'll tell you when you're wrong
Including when the thing you're wrong about is something you're paying us to build. An agreeable vendor who lets you walk into a bad decision is more expensive than a blunt one.
Quality is enforced, not promised
Every change is automatically tested against our standards before it can ship, so they hold when a deadline is close and everyone is tired — which is exactly when promises don't.
Where we work
A remote company. On site when it counts.
We are based in Panama City, Florida, and we work remotely. Not "remote delivery from a head office" — remote is how the company itself operates, and it's how this practice has run for over a decade rather than something we adopted recently.
That's why we can take on work anywhere in the United States without it being a special arrangement. In practice it means working sessions scheduled in your time zone, shared access to the repositories and environments throughout, and decisions recorded in writing you can read later instead of a meeting you had to attend.
It does not mean you'll never see us. When being in the room genuinely changes the outcome — discovery workshops, a go-live, training your team — we get on a plane. Just tell us when you need us there.
Practically speaking
- Your hours, not ours Working sessions scheduled in your time zone, whichever coast you're on.
- Written by default Decisions, designs, and trade-offs recorded in writing so nothing depends on who was in the room.
- Shared environments You have access to the repositories, pipelines, and cloud accounts throughout — not on handover day.
- On site when you need us We travel for discovery workshops, go-lives, and training — anywhere in the United States. Ask and we'll be there.
Let's talk
Fourteen years in, still taking on new work.
If you have a problem that software should solve, we'd like to hear about it — even if you're not sure yet whether it's worth building.