Jaleel | Web Dev for Truckers

I help trucking companies build a strong online presence 🚛 Boosting trust, transparency, and growth.

[Jaleel | Web Dev for Truckers @JaloByte]

Ready, Set, Go!

[Jaleel | Web Dev for Truckers @JaloByte]

i almost shipped JaloPermit without The Atlas.

just the permit decoder. drop a PDF, get your route card, done.

then a driver asked me something simple.

"what's the escort rule in Oklahoma if i don't have my permit yet?"

he wasn't pre-trip. he was quoting a load. needed a quick answer before committing.

i had nothing for him.

that conversation stuck with me. there's a whole window before the permit even exists brokers pricing freight, dispatchers checking if a load is even legal to move, drivers figuring out if they need an escort pilot.

so i built The Atlas.

48 states. plain English. no permit upload required. just open it and look up the state you need.

it's reference only always confirm with the state DOT before you rely on it. but for that first question, the one you need answered before you even have a PDF in hand, it's there.

[Jaleel | Web Dev for Truckers @JaloByte]

@irentdumpsters In January 2025, Google Business Profile Diamond Product Expert Ben Fisher publicly stated that the pin-move attack had been resolved internally by the GBP team and was “permanently fixed.”

[Jaleel | Web Dev for Truckers @JaloByte]

@maybedanielleee Got to look into FL

[Jaleel | Web Dev for Truckers @JaloByte]

@SimonHoiberg Simon, you never stop cooking. This is awesome!

[Jaleel | Web Dev for Truckers @JaloByte]

“Get AWS, it scales with you” yeah it scaled my credit card first (wrong AMI gang rise up) 🤦‍♂️

[Jaleel | Web Dev for Truckers @JaloByte]

1,732+ truck stops mapped inside JaloPermit.

not random pins on a map.

only stops that sit along the permitted route itself.

so when a driver is 4 hours into a heavy-haul run and needs to know where he can actually pull over he's not guessing.

the permit already told us the corridor. we just built the stops into it.

that detail took longer than i expected to get right.

[Jaleel | Web Dev for Truckers @JaloByte]

@jonathan_wilke It’s “read” only.

[Jaleel | Web Dev for Truckers @JaloByte]

She only sees $$$ AMERICAN ONLY AMERICA FIRST 🇺🇸

[James Li @5149jamesli]

Make this go viral.

[Jaleel | Web Dev for Truckers @JaloByte]

i used to think the hard part of oversize trucking was getting the permit.

turns out the hard part is reading it.

a state DOT permit isn't written for drivers. it's written for compliance officers. dense paragraphs, state-specific legal language, curfew windows buried mid-page, escort thresholds that require you to cross-reference load dimensions you wrote down somewhere else.

a driver at 5:30am doesn't have 25 minutes to work through that.

that's the gap JaloPermit sits in. permit's already issued. it's in your hand. you just need to know what it's actually saying before wheels roll.

drop the PDF. get back the corridor, the escorts, the curfews, the weigh stations, the clearances in seconds.

that's the whole thing.

[Jaleel | Web Dev for Truckers @JaloByte]

@garrett_makes Hell yes 🙌

[Jaleel | Web Dev for Truckers @JaloByte]

@garrett_makes It’s not 16h and going i hope it’s not a bug

[Jaleel | Web Dev for Truckers @JaloByte]

can anyone beat my loop? Longest loop with claude 15h+

[Jaleel | Web Dev for Truckers @JaloByte]

the shareable route card almost didn't ship.

i kept thinking who actually needs to share this? the driver has the permit, dispatch has a copy, everyone knows the route.

then i talked to a driver running an oversize load solo across three states.

he said the worst part of the job is the phone call at 5am from the dispatcher asking "where are you, what's your next turn, do you have your escort lined up?"

while he's driving.

the card isn't for the driver. it's for everyone else who needs to know what's on that permit without asking the guy behind the wheel.

one tap and the whole route load specs, turns, escorts, curfews is in the group chat before the truck leaves the yard.

that's the feature now. took me way too long to understand why it mattered.

[Jaleel | Web Dev for Truckers @JaloByte]

talked to a dispatcher last week who said she texts permit details to drivers by hand.

copies dimensions, route restrictions, escort rules — one by one — into a group chat.

every single load.

i asked how long it takes.

"20, 30 minutes if the permit is clean. longer if it's not."

that's not a workflow problem. that's just time stolen from someone's day, over and over, for years.

the shareable route card in JaloPermit took maybe a week to build.

one tap and the whole card — route, specs, escorts, directions — goes straight to the chat.

the gap between "this is painful" and "this is fixed" was smaller than i expected.

https://t.co/wvhDMEyKbD — 3 free decodes a day, no account needed.

[Jaleel | Web Dev for Truckers @JaloByte]

weigh stations are something i never thought about until i started building JaloPermit.

turns out there are 870+ of them across the lower 48.

and most oversize drivers have no idea which ones are open, where the entrance is, or what milepost to watch for — until they're already on the road.

so we put all of them on the route card.

highway, exit number, milepost. right there alongside the permitted corridor.

small thing. but drivers keep bringing it up unprompted.

[Jaleel | Web Dev for Truckers @JaloByte]

we almost didn't include low-bridge alerts.

felt like scope creep. the permit already tells you the route, right?

then i learned that permit routes and bridge clearance data live in completely different places. the permit clears you legally. it says nothing about that 13'2" railroad bridge on county road 7.

drivers carry that knowledge in their heads. or they call someone who's run the road before. or they find out the hard way.

so we pull the rated clearances near the route and check them against the load height automatically. one less thing to hold in your head at 5am before a move.

it's now one of the features i'm most glad we built.

[Jaleel | Web Dev for Truckers @JaloByte]

every oversize permit has a curfew buried somewhere in it.

page 4, footnote 3, "no movement between 7am and 9am within city limits."

drivers miss it.

not because they're careless.

because the permit is 11 pages of dense state legalese and they're reading it at a fuel stop on a phone screen.

that one line costs them a $1,200 fine and four hours sitting on the shoulder.

[Jaleel | Web Dev for Truckers @JaloByte]

@starter_story Tell me you’re single without telling me you’re single lol

[Jaleel | Web Dev for Truckers @JaloByte]

@Kriptocrite @FreightAlley as if you have 51 fleets. It is pretty damn impressive if a company has 50 trucks running.

[Jaleel | Web Dev for Truckers @JaloByte]

i spent two hours reading oversize permit PDFs from different states last week.

every single one is formatted differently.

some are clean. some look like they were scanned on a fax machine from 2003. some bury the curfew in paragraph 7 of the legal notes.

drivers are expected to read all of this, understand it, and be road-ready in minutes.

that's what JaloPermit is actually solving. not a paperwork problem. a "i need to leave the yard in 20 minutes and this permit makes no sense" problem.

we pull out the route, escorts, curfews, and turn-by-turn directions and put them in one card. any state. any format. even the ugly scanned ones.

try it free at https://t.co/wvhDMEyKbD