Skip to content
See packages

Contact

Tell us what you want to automate.

Describe the physical task and the equipment you use. We reply within one business day.

Packages

Start with a package

Four packages, each with its price on the page. Pick one and buy it online.

Billing
Add project details (optional)

We reply within one business day.

By email

By phone

(214) 723-2510

If you would rather talk than type.

For procurement

Entity
Hyrax LLC d/b/a Computing America
NAICSNorth American Industry Classification System. The six-digit code for what a seller does. A solicitation names one, and it decides which firms are eligible to bid.
541512 · this division
PSCProduct and Service Code. The four-character code for what the government is buying. A solicitation names one of these and one NAICS: the PSC says what, the NAICS says who.
R499
Venue
Texas, United States

The firm's primary code is 541511; every NAICS and PSC held, and the state of each registration, is on the government page.

A W-9 is available on request. We do not hold a certificate of insurance yet; send your requirements and we will say what we can meet. Payment is net 30, by purchase card, ACH or purchase order.

How the work runs

  1. 1First call45 minutes · no charge
  2. 2Discovery1–4 weeks typical · fixed fee
  3. 3Pilot build4–6 weeks typical · scope dependent
  4. 4Refine and roll outOngoing, by agreement
  5. 5Maintenance & supportOngoing, for as long as you want it

Before you write

Answers to what you were probably about to ask.

Cost, timing, your engineers and how to leave. The process page covers the rest.

  • Yes, and it is usually the fastest way to get a useful answer: several of the pieces we publish end by asking for exactly that. Two things worth knowing first. This is an ordinary web form: it is encrypted in transit and the message lands in our mailbox and our own console, but it is not a secure document channel, so redact freely. A workbook with the numbers changed, a clause with the parties removed, a day of messages with the identifiers swapped: each of those answers the question as well as the original does, and we would rather read a redacted one. And if you would rather have an agreement in place before you send anything, say so in a line: we work under your paper rather than asking you to work under ours, and we redline rather than refuse.

  • Hardware work starts with a fixed-fee feasibility study and automation plan, agreed in advance, which can end in a recommendation not to build. The pilot build and each rollout phase are then quoted against a written scope, with acceptance tests, before that phase starts. Tell us the budget you have on the first call and we will tell you what is achievable inside it.

  • On résumé, they are ahead, and you should discount anyone who tells you otherwise. There are onshore firms in this space that have been doing it for eighteen, thirty, even fifty years, with senior engineers and named clients in your industry. The difference we would ask you to weigh is structural rather than technical. Most firms our competitors’ size specialize in one layer and subcontract or decline the rest, so the seams between the control network, the application, the estate and the security review end up owned by whoever is left in the room. We run those as four divisions inside one company, under one contract, which is why the escalation path ends somewhere useful instead of at a vendor boundary. That is the trade on offer: longer history and more logos on one side, and on the other a smaller senior team that can follow the problem across every layer it touches.

  • Yes. Your engineers contribute business knowledge and review the work with ours. Shared development and documentation also prepare your team for handover.

  • Thirty days’ notice after the first release, for any reason, with no termination fee. What you take with you when you go is settled in the engagement agreement before any work starts, and the hand-off phase is in the plan from the beginning rather than negotiated on the way out. We’d rather you were able to leave easily and chose not to.

  • Yes. We work under client paper rather than asking you to work under ours, and we redline rather than refuse. Security is handled through an exhibit written for your data rather than a pointer to our own policy, and the terms we will agree to there include notification of any actual or suspected incident within 24 hours, the content and timing of any notification to your customers or regulators left entirely in your control, a BAA where PHI is involved, and support for joint security testing. Questionnaires are part of onboarding rather than an afterthought. Send the requirements early, including whatever insurance you require us to carry, and we’ll flag anything we can’t meet.

  • Usually one of three ways, and we will tell you which is fastest for your institution rather than the one that suits us. First, subcontracting: we work under a prime who already holds the vehicle, which is the most common route for a firm at our stage and needs nothing new from your procurement office. Second, your own delegated authority: many institutions can issue a purchase order directly for services under their own limit, and those limits are set locally rather than centrally, so the number is yours to confirm. Third, a cooperative or state vehicle you already use. Being plain about that third one: we hold no cooperative or state contract awards today. Awards on those come through competitive solicitation cycles rather than on request, they are published, and any vendor implying otherwise is worth checking. If a vehicle is the only viable path for you, the honest answer is that we are the wrong firm this fiscal year, and we will say so on the first call rather than in month two.