INQUIRIES?
ASKED AND ANSWERED.

CANIS is a self-contained command and control platform for field operations. It runs a full TAK server, fuses several radio networks into one shared map, and works with no internet connection at all. Everything runs on a single Raspberry Pi 5 you can carry.

Two groups. Search and rescue, wildland fire, ski patrol, backcountry and small public-safety agencies on one side. SWAT, EOD, and federal teams on the other. The platform is the same; the tools you'd reach for differ.

Three things. It carries its own TAK server, so there's no cloud and no subscription. It bridges radio networks that normally can't see each other. And it refuses to answer when it doesn't have the data rather than producing a confident guess — which matters when the answer is where a helicopter lands.

Cattle Dog Drones builds working systems for people in the field. CANIS is the software half — the command picture that ties the hardware, the radios, and the team together.

Yes, completely. The map, the TAK server, the radios, the tools and the reference library all run on the box itself — pull the network and it keeps working. That's independence from the internet, not isolation from it: when there IS a connection you can also reach the box remotely.

Before you go out, you stage an area of operations — satellite imagery and terrain elevation for the region you'll be working in. That's the one thing that needs a connection, and it's done ahead of time. After that the box is independent.

Anything that depends on a live feed stops updating — weather alerts, aircraft tracking, stream gauges. CANIS says so rather than showing you stale data as if it were current. Tools that need terrain will refuse to run outside a staged area instead of guessing.

An offline reference library ships with the box — medical references, Wikipedia, disaster response guides, amateur radio material and repair manuals. Available with no connection.

Three answers depending on where you are. Near the box: phones and tablets join its Wi-Fi — short range, tens of metres. Spread out beyond that: LoRa mesh radios carry positions and messages; phones alone won't. Anywhere with internet: reach the box over the encrypted private network. Same map in all three.

Yes. If the box has a connection and you have a connection, you can reach it — cell, Wi-Fi or ethernet. It runs over an encrypted private network, so it isn't exposed to the open internet and there's no third party in the middle. Full interface, not a read-only view.

Both are true and that's the point. The box doesn't NEED the internet — pull the plug and the map, the radios and the tools keep working. But when there is a connection, you can reach it from anywhere. Independence, not isolation.

Everyone you enrol. Phones and tablets running ATAK or iTAK connect to it as a TAK server. Anyone else opens a browser. A command post two states away and a team standing on the ground see the same picture.

Common setup: the box goes with the team, and an incident commander or a supervisor follows the same map from wherever they are. Nothing special to configure — it's the same interface either way.

The box keeps working for the people near it — their radios, their map, their tools. Remote viewers lose the live feed until it's back on a connection. Nothing is lost; it catches up when it reconnects.

It sits on an encrypted private network rather than being published to the open internet — no port forwarding, no public address. For specifics on how that's set up, our team can walk through it directly.

A Raspberry Pi 5 with 8GB of memory, in an IP-rated housing built for field use. That's the whole box. It draws little enough power to run off a battery pack in a vehicle or a pack.

Two ways in. ATAK and iTAK connect to it as a normal TAK server. Or open a browser — CANIS has its own mobile view built for someone standing in the field, with no app to install. Either works from next to the box or from across the country.

As a complete unit — a Raspberry Pi 5 in an IP-rated housing built for field use, with the SD card installed and staged for first boot. Power it on and walk through the setup wizard. No assembly, no build process, no dependencies to chase.

Both. A 3D globe with real terrain for planning and rehearsal, and a flat map for the work that's easier flat. The same data appears on both.

CANIS brings several networks onto one map: LoRa mesh (Meshtastic), Wi-Fi HaLow, cellular, and Starlink satellite. A team on LoRa and a team on cellular see each other, which they normally wouldn't.

CANIS runs its own TAK server on the box. Your EUDs connect to it directly. No external server, no internet dependency, no per-seat cost.

Voice runs on the box for anyone connected to it — over the encrypted private network or over the hotspot. Separate from your radio nets, so it works when the team is co-located but the radios aren't reaching.

CANIS tracks how each node actually reaches you — heard directly over the air, relayed through a gateway, or bridged from a different radio network. That distinction matters: a node on the map isn't necessarily a node you can reach, and CANIS won't imply otherwise.

If the box loses its network, it becomes its own Wi-Fi access point after a short delay. Your team connects their phones directly to it and the map keeps working. That covers people NEAR the box — Wi-Fi reaches tens of metres, not miles. A team spread wider than that needs mesh radios, not phones.

That's the job the mesh radios do. LoRa (Meshtastic) nodes carry positions and short messages between people spread beyond Wi-Fi range, relayed node to node, no cell service involved — and CANIS puts every node on the one map. Phones alone won't span that distance: phones for the people near the box, a mesh radio per distant element is the working setup. Exact reach depends on terrain — our team can spec a kit for your ground.

Draw a box around your casualty and CANIS shades the ground by slope, so you can see where a helicopter could physically sit. You place the centre yourself. It records obstacles, computes density altitude, generates a brief, and pushes the whole thing to every ATAK device.

Plans a static-line jump: run-in, release point, drift, and the descent to the DZ. It checks the descent against real terrain and flags where the path would clip ground.

Projects where a fire could reach within one, three and six hours and draws evacuation bands on the map — GO, SET, READY. It's a conservative planning estimate, labelled as one, and it doesn't replace official evacuation orders.

Plans routes on foot and by vehicle across real terrain, with elevation profile, travel time, and turn-by-turn directions on vehicle routes — a normal instruction where OpenStreetMap has a road name, a compass bearing with junction shape and exit count where it doesn't. Every route states how much of it is name-backed. Still a planned route you read, not a navigation app talking while you drive.

Shows what's visible from a point, using real terrain. Useful for observation posts, and for understanding why you can't see a team you should be able to.

Predicts radio coverage across terrain, so you can see where a team will drop out before you send them. Separate from viewshed, because radio bends around terrain that blocks line of sight.

Helps you place mesh nodes so the network actually connects. It tells you which nodes reach the gateway and which don't, and it excludes nodes on other radio types rather than pretending they're on the mesh.

Search area definition, pattern generation, and team assignment, with the results pushed to everyone's device.

Tracks who's on scene, what team they're on, and when they last checked in. Runs a PAR when you need one.

Drone position, telemetry and video feed into the same picture as everything else, so the aircraft isn't a separate screen.

Live aircraft tracking, including whether a rotorcraft is inbound and how far out. CANIS distinguishes what an aircraft actually declares from what we've inferred, and labels which is which.

Draw zones and get alerted when someone enters or leaves.

Camera and video streams alongside the map, from drones or fixed positions.

HF propagation planning — which band will work on which path at which hour. Useful when your team is far enough out that VHF won't reach.

Weather alerts, wildfire perimeters and hotspots, stream gauges, earthquakes, volcanoes, air quality, radiation monitoring, GPS jamming reports, cell coverage, hospitals, public lands, tides, sea state, satellite constellations and weather radar — among others.

Every hazard layer shows how old its data actually is. If a feed hasn't updated, the layer says so instead of showing you old readings that look current. Reference data that never changes is labelled as reference data, with its vintage.

Running CANIS never requires a cloud connection, and updates don't change that. The exact mechanism for delivering releases isn't published yet — our team can walk through how updates arrive.

Export formats and record-keeping detail aren't published, and incident records are worth getting right. Ask our team what comes off the box after an operation.

CANIS ships on an SD card in a Raspberry Pi 5. What happens to incident data if hardware fails — and what the recovery path is — isn't published yet. Our team can answer directly.

There's no published tested device count, so none is quoted here. It runs a full TAK server for the team plus browser clients; whether it fits your team size is a question for our team.

The box: a Raspberry Pi 5 in an IP-rated housing built for field use, SD card installed and staged for first boot. Complete hardware, not a card you assemble. No subscription, no per-seat cost.

CANIS runs its own TAK server on the box. Whether it can also join or federate with an agency's existing TAK infrastructure isn't published — our team can answer.

One box serves a team. How multiple CANIS boxes behave together — sync, merge, shared picture — isn't published. Worth asking our team.

The built-in layer list is published; whether you can import your own data — KML, shapefiles, parcel maps — isn't. Our team can tell you.

CANIS is built to refuse rather than guess. If it doesn't have terrain for an area, the slope tool says 'no terrain data and here's why' instead of computing against a flat earth. If a radio path can't be verified, it isn't drawn as connected. A tool that looks like it's working while producing wrong answers is worse than one that stops.

It reports measurements and the standards they're measured against. It doesn't render verdicts. The landing zone tool won't say a site is safe; the route tool won't say a road is passable. Those calls belong to the pilot, the driver, and the incident commander.

Where a threshold comes from published doctrine, CANIS cites it. Where no published number exists, it says the number is unsourced rather than presenting it as authoritative. You can see which is which.

Every measurement carries how it was obtained — computed from data, observed by someone on the ground, or unknown. A slope someone walked and a slope derived from a map look different on screen, because they mean different things.

It generates turn-by-turn directions for vehicle routes: named-road instructions where OpenStreetMap has a name, compass bearings with junction shape and exit count where it doesn't — a bearing can be checked, 'bear left' can't. Every route states how much of it is name-backed. It is still not a navigation app talking at you while you drive — it's a planned route with instructions you read.

It doesn't make operational decisions. It presents what it knows, labels what it doesn't, and leaves the call to the person responsible.

It's only as good as the data underneath it. A road washed out last week isn't in any map. CANIS states what it checked and what it didn't, so you know what you're relying on.

CANIS pricing isn't published yet — the CANIS page is marked coming soon and takes pre-orders. The robot platforms have published base prices on their product pages, each with a downloadable capability sheet. For a CANIS number, talk to our team.

No subscription and no per-seat licensing. The box is yours and it works without calling home.

Three small ground vehicles, a survey drone, a rail-launched interceptor, a wired controller, and the CANIS software. All three ground vehicles are shipping now; the rest are in development. Everything is NDAA-compliant and built in Sonora, Texas.

• Send something into a building before people go in → K9 Scout for tight interior spaces, K9 Breacher for rougher ground or heavier payloads
• Carry a robot in a pack → K9 Brute
• Search a large area from the air → The Kestrel (in development)
• Check fence lines, water and livestock on a ranch → The Kestrel (in development)
• Control a vehicle without carrying another controller → The Leash (in development)
• A shared map that works with no internet → CANIS
• Counter-drone → that conversation goes through our team directly

AVAILABLE FOR PROCUREMENT · BASE $5,000

A two-wheel-drive reconnaissance robot that goes into hallways, stairwells, attics, crawlspaces and hazmat scenes first, so your operators don't have to.

AVAILABLE FOR PROCUREMENT · BASE $6,000

Four-wheel-drive version of the same idea, built for deliberate entries and rougher ground. Around 20 lbs, roughly twice the driving range of the Scout.

AVAILABLE FOR PROCUREMENT · BASE $6,500

Tracked, and small enough to pack into a standard rucksack or assault pack. Built for dismounted operators on urban raids.

IN DEVELOPMENT · BASE $6,000

A long-endurance survey quadcopter. It started as an agricultural survey aircraft for a West Texas ranch and grew into a multi-role platform — ranch work, search and rescue, comms relay and overwatch.

IN DEVELOPMENT · BASE $600

A rugged wired controller that plugs into the Android device an operator is already carrying. That phone running ATAK becomes the full ground control station.

The command and control software that ties everything together — a self-contained operations picture that runs offline on a small computer you can carry. There's a full CANIS section on this page with much more detail.

IN DEVELOPMENT · COUNTER-UAS

REMUDA is a rail-launched counter-UAS interceptor, currently in development. It's an engagement system, so its performance and employment aren't discussed here — that conversation goes through our team directly, and export classification is handled per enquiry.

Every vehicle uses the same mission control interface. Train an operator on one and they can run the others — training transfers across a mixed fleet instead of starting over per platform.

Built to be repaired in the field with ordinary tools, using commercial parts you can source through normal distributors. That's deliberate — a robot you can't fix in a shop is a robot that stops working.

No proprietary controller. Live video and control go to an Android or Windows device you already have. ATAK's UAS Tool works with them.

All critical components are NDAA or Blue UAS compliant, with no covered foreign components in the supply chain. Everything is made in the USA, in Sonora, Texas.

The vehicles run the Auterion Skynode X — a Blue UAS Framework listed autonomy stack already used on aerial platforms across DoD and allied forces. Same backbone on the ground.

Commercial components, simple mechanical design, and a small shop with no layers between you and the person who built it. The trade is that these are focused tools rather than everything-boxes.

Cattle Dog Drones is veteran-owned, founded by our team — a former Recon Marine and Scout Sniper. Based in Sonora, Texas. Small enough that you'll talk to the person who designs and builds the systems.

Warranty terms aren't published here, and guessing at coverage helps nobody. Our team can give you the terms directly.

Driving range and control range are different numbers — the published distance figures are driving range. Control range: 100 m on the onboard 2.4 GHz Wi-Fi link, nationwide with the optional cellular radio, and K9 Brute's optional tactical mesh radio extends control to several kilometres.

On file: K9 Breacher handles taller obstacles than the Scout, and the ground line is built for urban interiors. Specific obstacle heights and stair capability per platform aren't published. Our team can answer for your structure type.

K9 Scout IP-62 · K9 Breacher IP-62 · K9 Brute IP-64 · Kestrel IP-62. K9 Brute carries the highest ingress rating of the line.

Payload capacity figures aren't published. K9 Scout is used to deliver a phone or radio; K9 Breacher takes modular payloads. For weight limits, ask our team.

Every vehicle runs the same control interface, and one controller drives the line. Whether one operator can run several vehicles simultaneously isn't published — our team can answer that one.

THE KESTREL is Remote ID compliant, and its weight class is flown under a Part 107 remote pilot certificate. Licensing specifics, waivers, and anything beyond visual line of sight are conversations for our team, not something this page will interpret.

CANIS is built to unify feeds into one picture, and drone position, telemetry and video already flow in. The current state of ground-vehicle video inside CANIS isn't published — our team can confirm.

We run a Fusion3 EDGE in Sonora, Texas and take outside print work. Industrial FDM — engineering plastics, not hobby prints. Prototypes, replacement parts, short production runs, brackets and enclosures.

It's an industrial machine running engineering-grade materials — carbon-fibre reinforced nylon, polycarbonate, polypropylene, ESD-safe plastics. We use it daily to build our own hardware, so these are materials we actually know how to run rather than ones we'll experiment with on your part.

Our own products. The Leash controller enclosure, robot chassis components, brackets, mounts. Parts that get dropped, sat on, and left in a truck bed in a West Texas summer.

Ten material families: PLA, PETG, ABS, ASA, nylon, polycarbonate, polypropylene, co-polyesters, flexible TPU, and HIPS. Plus a stainless steel filament that sinters into a solid metal part. Carbon-fibre and glass-fibre reinforced versions of most of them.

Carbon-fibre reinforced nylon or polycarbonate. That's what we use for parts that have to survive being dropped and handled roughly. Polycarbonate also holds up to heat better than most.

ASA. It's made for it — it holds up to UV and weather where ABS goes brittle and chalky. That's the one for anything living outside.

Polycarbonate for the highest heat tolerance, then ABS or ASA. PLA is the wrong choice — it starts softening in a hot car.

Flexible TPU, in a few hardnesses from soft and rubbery to semi-rigid. Good for gaskets, bumpers, grips and strain reliefs.

Polypropylene — chemically resistant and very tough, and one of the materials only the EDGE-class machine can run. Nylon is the other good option depending on what it's exposed to.

Some materials use FDA food-contact-safe raw material. Worth flagging though: a printed part has layer lines that hold bacteria, so 'made from food-safe material' isn't the same as 'safe for repeated food use'. Talk to our team about the application.

Yes — ESD-safe versions of several materials, for electronics handling, trays and fixtures where static is a problem.

There's a stainless steel filament that prints a part which is then sintered into solid metal. It's a specialist process with shrinkage to account for — worth talking through with our team before you design around it.

PLA or PETG for anything that doesn't need to survive heat or hard use. PETG is the better all-rounder — tougher than PLA and doesn't mind being left in a warm room.

The machine is certified for a long list of brands, but what's actually on the shelf changes. Tell our team what you need and we'll confirm.

MATERIAL COST × 2 — SHIPPING AND HANDLING EXTRA

That's the whole formula. It's deliberately simple, but it isn't a self-serve quote: what a part costs in material depends on its weight in the chosen plastic, and that comes from the file. Send it and the quote comes back with the real number.

Send our team your file and what it's for — material, quantity, and anything about how it'll be used. The inquiry form goes straight to us.

One-offs through short production runs. FDM makes sense for low volumes and for parts that would be expensive to tool for — past a certain quantity, injection moulding is the better answer and our team will tell you that rather than take the job.

.stl and .step files are accepted.

Yes — design work is offered. If you don't have a model, send a sketch, photos or measurements and what the part has to do, and it gets modeled before printing.

The Fusion3 EDGE builds up to 367 × 367 × 342 mm — about 14.5 × 14.5 × 13.5 inches. Larger parts can often be split and joined; mention it on the job and our team will say whether it fits or needs splitting.

Typically 2–3 weeks, depending on the queue and the part. Say if it's urgent.

Tolerance is flexible — it varies by material and geometry, and shrinkage differs between plastics, so it's agreed per job rather than published as one number. If the part has to fit something, say so.

Jobs ship nationally, and local pickup in Sonora, Texas is offered. Shipping is billed separately from the print — it's not in the formula.

Yes — brass heat-set insert installation is offered alongside printing, the same process we use on our own enclosures. Note it on the job and our team will spec it with you.

FDM parts are built in layers, which means they're strongest across the layers and weakest along them. Orientation matters. For the right part it's excellent; for a highly stressed part in the wrong direction it isn't. Tell our team how it gets loaded.

You'll see layer lines. Some materials can be smoothed afterwards and most can be sanded and painted, but out of the machine it looks printed. If appearance matters, say so up front.

Parts can be sanded, smoothed or painted after printing, but whether finishing is offered as a service on your job isn't published — say what finish you need and our team will quote it.

Nothing that infringes someone's IP, nothing regulated we're not set up to handle, and nothing where a printed part is the wrong answer and would fail in use. Our team will say so rather than take the job.

For anything safety-critical or load-bearing, that's a conversation rather than a page answer. Tell our team what it's holding and what happens if it fails.

Base prices: K9 Scout $5,000, K9 Breacher $6,000, K9 Brute $6,500, Kestrel $6,000, The Leash $600. Options and payloads are priced separately. For a configuration that fits your use, talk to our team.

K9 Scout, K9 Breacher and K9 Brute are available for procurement now. Kestrel, The Leash and REMUDA are in development. Delivery dates aren't quoted here — our team can give you a real answer.

CAGE 20GV1, UEI T3C1EFXVNNE1. Sonora, Texas. Capability sheets are downloadable per platform, built to be printed and attached to a budget request.

Phone 740-507-6670 · glasscockaustin@cattledogdrones.com · Mon–Fri 0900–1700 CT. HQ: 2051 Loop 467, Sonora, TX 76950. Existing customers and ITAR/EAR-sensitive inquiries go through the customer portal.

Export classification is reviewed per platform, and engagement systems carry stricter handling. That's a direct conversation with our team — for sensitive inquiries, use the customer portal or call.

Worth asking our team directly — the inquiry form goes straight to him.

Every platform has a one-page capability sheet built to be printed and attached to a budget request — specs, compliance, and a price. Our team can help with the rest of what a grant application needs.

Talk to our team directly. Cattle Dog Drones is small enough that you'll deal with the person who built it.