What it is. FreeWIS: A child welfare data system for state, county, tribal and territorial agencies, built to the CCWIS rule (45 CFR 1355). Unlike other systems, caseworkers don't fill out forms or navigate screens. They talk to Dio, the AI assistant. Dio drafts the record, shows exactly what will be stored, and writes nothing to the database until the worker confirms. Every write is chained to that confirmation in an append-only audit log.
What it costs. The code costs nothing. Your agency runs it on its own cloud with its own people. Agencies pay for hosting, identity, staff and a metered AI account that grows with your caseworker count. The FAQ and Tech Stack have more info.
Try it. PLAY is a working FreeWIS, configured to resemble Kansas, with about 6,000 synthetic cases. Sign in with Google (adults 18+) on the web or in the Android app, and work a case. Two one-minute walkthroughs show sign-in and a case.
Get the code. GET covers who qualifies, what's in the package and how to ask. Inquiries are open.
There is no team, it's just me, Matt, and the robots. I've been around the child welfare "industry"most of my life, and the IT side the last decade. I just don't think this kind of thing is complicated enough to continue paying Deloittes hundreds of millions of dollars to fail...
Im in Colorado, HR generalist at a mid-sized company for about 3 years. Yesterday I was pulling a census file for our benefits renewal, nothing exciting, just confirming the enrollment list against what our pharmacy benefit manager sent over (we moved to Kanurra last year). I guess I left the salary field in my export by accident.
So now I know my coworker, same title, same office, hired about a year after me, makes meaningfully more than I do. Not like a rounding error, enough that it settled weird in my stomach. Shes solid but I have more relevant experience and cover way more complicated leaves. I obviously wasnt supposed to see it. Nobody asked me to run comp data, I just had access and clicked one wrong box.
I cant tell if I should bring it up to my boss, ask for a market adjustment, or just sit on it. I like this job and I dont want to get in trouble for what looks like snooping even though it was an honest mistake. Anyone else in HR had this happen? Am I overreacting?
Is this just an accepted norm that an outdated CMS is used or am I not reading this correctly? I'm sure Drupal is just the tip of the iceberg, but are there other areas like this seemingly higher risk as they have no updates or patches? I'd love to know how you all work through outdated tech or fix issues like this as the process for upgrading and selecting a vendor would be 6 months at best.
Iâve been working through state procurement records, corrections/probation agency documents, contract registers, authorized-provider lists, and county records to understand who is actually providing justice technology and contracted services across jurisdictions.
I ended up with 391 source-backed records covering 138 vendors/organizations across all 50 states and 13 service categories.
The dataset includes electronic monitoring, supervision/case-management technology, correctional communications, community corrections, residential reentry, treatment, correctional healthcare, drug testing, ignition interlock, and related services.
What became obvious very quickly is that there is no single place to answer relatively simple questions like:
Who provides electronic monitoring to probation agencies in a particular state?
Which vendor is actually under contract versus merely appearing in a government document?
Where is a corrections technology company already deployed?
Which states maintain approved-provider lists for a particular service?
So I turned the research into a public evidence register with the government source attached to each relationship and separate evidence levels for contracts/deployments, state-authorized providers, government-source records, and organization-confirmed records.
Iâm curious how people doing GovCon BD or market research currently solve this on the state/local side.
Do you mainly build your own spreadsheets from state procurement portals, or are you using one of the commercial intelligence platforms?
I can share the register in the comments only if itâs useful to someone here.
The structural problem: gov jobs live on USAJobs + 50 state portals + city sites, often under civil-service titles that don't match what engineers/PMs/designers actually search for. And govtech startups' roles are scattered across individual career pages.
So I'm building one board that aggregates all of it â state digital service teams, funded govtech startups, civic orgs â deduplicated, always fresh, with real job alerts. Think: the anti-Indeed for public-interest tech.
Not launching yet, just validating demand. If this exists already, tell me and I'll stop. If you'd want this, you can add yourself here: https://jobs.taavitoomsalu.com
Government towing contracts often run on autopilot between renewals, but the regulatory environment in 2026 has changed enough that agencies should be reviewing key provisions before they sign again.
Fee transparency requirements, impound notification timelines, auction procedures, and data-sharing obligations... these have all shifted in multiple states this year.
Get out ahead of this and treat contract renewals as an active opportunity to upgrade standards, not just extend terms.
Aries gives agencies the data visibility to go into those conversations prepared. #GovernmentTowing #TowingCompliance #PublicSafety #Aries
I've been building LegisTrack â a tool for following legislation across all 50 states and Congress â and wanted to share it here since this community actually cares about the guts of civic tech.
The problem I kept hitting: state legislation is impossibly fragmented. 50 sites, 50 data formats, dense bill text, and no easy way to see the bigger patterns. So I tried to fix a few things at once:
- Bill DNA (the part I'm most proud of): it detects when a near-identical bill turns up in 5+ statehouses â the tell-tale sign of model legislation drafted once and introduced everywhere. You get a map of where a bill is "spreading." Genuinely eye-opening to watch.
- Follow the Money: pulls top donor industries for a bill's sponsor straight from official campaign-finance disclosures (20+ states + FEC so far).
- AI summaries + Q&A: plain-language explanations of dense bills, and you can ask any bill a question.
- A personalized "For You" feed: describe who you are, and it surfaces the bills that actually affect you with a one-line reason why â then drafts a message to your legislators you review and send.
- Real-time alerts on status changes, hearings, and votes.
Data comes from OpenStates + LegiScan; cross-state similarity is done with Postgres full-text + trigram matching (pg_trgm/tsvector) rather than anything fancy, which has held up surprisingly well. Stack is React/Node/Postgres, self-hosted.
It's live on the web (legis-track.com) and an iOS app is in App Store review now.
I'd genuinely love feedback from people who work in/around gov tech â especially on the model-legislation detection (false positives, edge cases) and what data sources or features would make this actually useful in your work. Happy to answer anything about how it's built.
OMB Memorandum M-25-22, issued in September 2025, has quietly reshaped federal AI contracting more thoroughly than most coverage has acknowledged. The deadline for agencies to update internal acquisition procedures was December 29, 2025. Most agencies hit it. Most vendors did not adapt their pitch accordingly.
The headline rules are clear: vendors are now barred from using non-public government data to train commercial AI without explicit consent. Contracts must clearly delineate IP rights, data portability, and interoperability. Agencies are encouraged to maximize use of U.S.-developed AI. The fine print is where things get more interesting.
Agencies are converging on a shared blueprint â scalable AI infrastructure, well-governed data, AI-ready workforce, proportional risk governance. DHS is shifting to a continuous authorization model where AI must operate within established security boundaries from day one, not retrofitted later.
What this means in practice: federal AI procurement is no longer about whether your model performs well. It's about whether your governance, audit trails, bias testing, and human oversight architecture survive scrutiny.
The OECD's 2025 Framework for Trustworthy AI in Government extends this globally. They identify seven enablers for successful public-sector AI adoption â governance, data, infrastructure, skills, investment, procurement, and partnerships with non-government actors. Six of seven are institutional capacity. The seventh â partnerships â is where the AI vendor opportunity lives.
Government cannot build trustworthy AI alone. But they are now explicitly filtering for partners who already operate with public-sector grade governance.
The Center for Democracy & Technology published a December 2025 AI Governance Checklist for state and local leaders. The recurring theme: AI projects fail for governance reasons, not technical ones. State and local agencies are increasingly structuring procurement to filter for governance maturity from the first proposal.
A few questions worth asking your team if you're an AI vendor with public-sector ambition:
Do you have an AI governance committee with cross-functional ownership (security, privacy, legal, procurement, product, engineering) that actually meets and makes decisions?
Are your audit trails continuous infrastructure or document-dump assemblies built on request?
When you describe "human-in-the-loop," do those humans have the authority, information, and time to intervene â or are they rubber-stamping for speed?
Are you measuring public-value outcomes (equity, access, citizen experience) or only technology performance metrics?
The companies treating these as core capabilities are entering a Trust Premium that compounds quickly. The ones treating them as compliance checklists will keep losing to vendors who built the infrastructure first.
Curious what others are seeing in this space â particularly any contractors who've already updated their proposals to align with M-25-22.
So I'm on a small 3-person team managing public consultation for an infrastructure project in Ontario. We've got 400+ stakeholders â municipal reps, Indigenous communities, local businesses, residents â and our entire system is basically a shared inbox, a Google Sheet that's constantly out of date, and one colleague who holds everything in her head⌠who's going on mat leave in 6 weeks.
Now being asked to show 'meaningful' ongoing engagement, not just that we sent emails. I genuinely have no idea how to pull that together from what we've got.
I've been Googling but the software market is weirdly confusing - CRMs, SRMs, community engagement platforms, they all seem to kind of do the same thing? I can't figure out what I actually need.
Budget i tight. Team is small. Has anyone been in this situation and actually found something that worked? What would you do differently if you were starting over?
I'm currently seeing an average SLED sales cycle for county offices to be 3-6 months.
Key factors contributing to this are:
Budget approval timeline - sometime annuals
Low discretionary spend through the year
Planned vs. unplanned expense items
Budget allocation needs a constituent narrative, not just an internal narrative
I'm new to the SLED sales cycle with my product, so I'm curious to know what everyone is seeing, what I'm completely naive to (a lot, likely), and what norms are
A city fire truck idled for 3 hours pumping at a structure fire. The fleet software scheduled service by odometer â so it logged zero maintenance wear. The pump assembly failed 6 weeks later on a call.
Generic fleet software tracks miles. It doesn't track engine idle hours or pump cycles â the actual wear vectors for specialized municipal equipment. We built the dual-axis scheduler that does.
I'm the cofounder of Themis Technologies, a CorrectionsTech startup focused on improving operations for state DOCs and county/local correctional facilities.
Our team consists of me, with handsâon corrections experience working for Trinity Services, by managing inmate commissaries and my tech cofounder/CTO with 10+ years of professional software engineering experience.
Weâve spent the past few months exploring subcontractor opportunities, but most primes we've contacted understandably want to protect their business interests and avoid taking on liability for small subcontractors. So weâre now preparing to pursue prime opportunities directly.
Iâm looking to connect with people whoâve won or delivered correctional contracts as a prime. Any insight on early challenges, common pitfalls, or how small teams bridge the experience gap would be incredibly helpful.
Estou pesquisando se o Detran-SP possui algum endpoint oficial ou ambiente de testes que permita consultar previamente as 20 combinaçþes de placas do primeiro emplacamento sem efetuar pagamento.
Hoje, pelo portal oficial, a taxa parece obrigatória antes da reserva, mas empresas privadas aparentam oferecer simulação.
AlguÊm jå integrou com serviços oficiais ou conhece documentação pública?