Technology that keeps working when the power and internet don't
We've started building this: offline-first, solar-powered digital infrastructure for schools, clinics, farms, government offices, and businesses in areas where electricity and connectivity aren't guaranteed. It builds directly on the Local AI, Custom Solutions, and Automation work we already do.
Where this stands today
We're actively building the architecture and the first modules below. This page walks through what we're building, how it works, and where we plan to take it.
The problem with normal software here
Most software assumes power and internet are always available. In many rural and semi-urban areas, neither is guaranteed — a cloud-only system simply stops working when the connection drops, and data entered during an outage can be lost entirely.
That's a design problem, not just an infrastructure problem. The real constraint isn't only "no internet" — it's power, connectivity, and cost, all at once. A normal cloud SaaS product is often the wrong architecture for that environment, so we designed around the constraint itself: a system that doesn't stop just because the power or the internet does.
One platform, not a custom project every time
Power, connectivity, a local server, the software itself, and optional AI — one shared platform, built once and deployed repeatedly with a module swapped in per sector, engineered so that losing the grid or the internet is a non-event.
Proposed system architecture
Central Cloud Dashboard
Analytics · AI · backups · admin
On-Site Edge Server
Local database · offline app · local AI
Staff & Field Devices
Phones, PCs, POS/lab/gate devices
Runs independent of grid power
Solar panels
Battery / UPS
Router + edge server + network gear
- Solar panels sized to the site
- Battery / UPS backup
- DC backup dedicated to the router, mini-PC, and cameras/network equipment
- Dual-SIM / dual-network 4G/5G router with automatic switching between available connections
- High-gain outdoor antenna where appropriate
- Point-to-point wireless link between nearby buildings where practical
- Optional licensed satellite or other backhaul where terrestrial connectivity isn't sufficient
- Small, low-power mini PC on-site
- Local database
- Local Wi-Fi / LAN
- Automatic local backups
- Our web/mobile application, offline-first by design
- Data stored locally when the internet disappears
- Automatic synchronization the moment it returns
- SMS/WhatsApp notifications where appropriate
- Remote administration whenever connectivity allows
- Local AI for selected tasks, where sensitive data or unreliable cloud access make it the better choice
- AI document search
- A staff assistant for reports and summaries
- Voice/text workflows where practical
One platform, ten modules
Rather than a separate custom system for every sector — or one giant everything-app — this is one shared foundation with a module swapped in per use case. Some of these are near-term; the community hub concept is a longer-term direction we're being upfront about.
Schools
Offline learning & school administration
- Curriculum content, lessons, videos, PDFs, and a digital library on the local school network — accessible with zero internet
- Attendance, student records, exam results, and teacher resources kept locally and synced automatically once connectivity returns
- An optional AI teaching assistant — e.g. generating a quiz on a lesson, or explaining a topic in the local language — while the core curriculum stays available locally regardless of the network
Healthcare
Offline clinic & hospital management
- Reception, patient registration, and queue/token management that keep functioning through an outage
- Doctor records — history, diagnosis, prescriptions, follow-ups — pharmacy inventory and expiry tracking, and lab test results, all stored locally first
- Daily management reporting: patient counts, medicine consumption, staff attendance
- A separate store-and-forward telemedicine layer: a health worker captures history, vitals, photos, and lab reports on-site, and the system forwards them to a remote doctor for review the moment a connection is available — no dependency on a live video call
Agriculture
Offline field & farm operations
- Field workers record farmer profiles, land/acreage, crop and input records, irrigation, harvest, and GPS-tagged fields from a mobile app with no signal, syncing once they reach connectivity
- AI-generated crop summaries, field reports, and procurement forecasts — presented strictly as decision support, always pointing back to qualified agricultural guidance rather than acting as an agronomic authority
- The stronger business case is often organizational, not individual: the same platform lets a seed company track its field network and trial plots, a fertilizer distributor track dealers and stock, or a cooperative manage members and collective produce sales
Livestock & dairy
Offline animal health & collection records
- Animal health, vaccination, and breeding records kept at the point of care — a livestock officer or vet working village to village with no connectivity
- Milk collection point logging for dairy cooperatives: farmer-wise volumes, quality grading, and payments due, synced to a central ledger once online
- A natural sibling module to Agriculture, sharing the same field-data and sync infrastructure
Water & public utilities
Offline monitoring for rural water & solar systems
- Monitoring and maintenance logging for solar-powered water pumps, RO/filtration plants, and small utility systems serving a school, clinic, or community
- Local alerting when a system needs attention, with a maintenance history kept on-site
- Usage and output logs synced to a central dashboard for the operating department or organization once connectivity is available
Local government & citizen services
Offline-first e-governance for local offices
- Union council / local office services — certificate issuance, applications, and complaint registration — that keep working when the office loses power or connectivity
- A queue and case-tracking system so a citizen's request isn't lost between visits
- Sync to a district-level dashboard once a connection is available, giving oversight without requiring permanent connectivity at every office
Disaster & relief coordination
Offline-capable emergency response tools
- Relief camp registration, needs assessment, and aid-distribution tracking designed to run in exactly the conditions a flood or emergency creates — power and connectivity both down
- Local logging of who received what, where, and when, so distribution stays accountable even before a connection is restored
- Sync to a central coordination dashboard the moment connectivity returns, for district or provincial-level visibility
Businesses & retail
Offline point-of-sale & inventory
- Point-of-sale, inventory, and basic accounting workflows for shops, pharmacies, and small distributors that keep running through power and internet outages
- Local records of sales and stock, synced to a central view once connectivity returns
- A natural entry point for a single-location pilot before scaling to a multi-site organization
Warehouses & enterprise sites
Offline operations management
- Larger deployments for a rice/flour mill, cotton operation, cold storage facility, or agricultural warehouse: gate entry, weighbridge integration, procurement, stock movement, vehicle records, and maintenance logs
- Staff attendance, purchase orders, sales, and reporting kept on-site and available immediately, not dependent on a head-office connection
- The head office sees synchronized data across every site once connectivity allows — a bigger-ticket deployment suited to organizations already running multiple locations
Community digital hub
A longer-term, capstone concept
- One central, solar-powered location — school, community center, or NGO site — offering local Wi-Fi, computer access, printing/scanning, digital learning, a telemedicine connection point, and basic business/government-information services
- Designed to be operated with an NGO, school, hospital, agricultural organization, CSR program, or development project under an ongoing service arrangement
- This is the furthest-out module, worth stating honestly as a longer-term direction once the sector-specific modules above are proven
Data privacy & security
This platform will hold patient records, citizen data, and farmer information — none of that is treated as an afterthought:
- Data stays on local, on-site infrastructure by default — it isn't sent to a third-party cloud unless and until sync is authorized
- Local AI runs on-site for exactly this reason: sensitive records don't need to leave the building to be useful
- Role-based access, so pharmacy staff don't see full patient histories and a field officer only sees their own assigned records
- Encrypted backups, both locally and once synced to a central dashboard
- Every deployment is configured to match the data-residency and access requirements of the department or organization operating it — this isn't a one-size-fits-all cloud product
Powering it: partnering, not competing
We don't intend to become a solar installation company. Our plan is to partner with existing solar installers and provide the software and edge-computing layer on top of their hardware — "solar-powered digital infrastructure" as a joint offering, rather than Brightcodex competing with companies that already do solar installation well.
How we're rolling it out
Our own plan, in three phases — meant to prove the platform before scaling it.
Phase 1
Prove it with a small number of pilots
Start with organizations that can move quickly — a private school, a private clinic, an agricultural dealer, a warehouse, a pharmacy, an NGO, or a cooperative — rather than large procurement processes. Faster to deploy, faster to learn from, faster to produce a real result to point to.
Phase 2
Turn pilots into a case study, then approach larger partners
Once a handful of pilots are running and syncing real data, use those results — not projections — to approach larger institutional and government programs with evidence instead of a concept.
Phase 3
Expand module by module
Grow the same shared platform into more sites and more sectors, adding modules as demand and proof from earlier phases justify each one — not all at once.
How this works commercially
We'd structure this around setup plus ongoing support, rather than a one-time build fee — the model that makes a platform like this sustainable rather than a one-off project:
Setup
Hardware, installation, and initial software configuration for a site.
Ongoing support
Hosting, backups, monitoring, updates, and software support, billed as a recurring service rather than a one-time fee.
Optional add-ons
Connectivity management, hardware replacement, additional sites, deeper analytics or AI, and integrations as an organization's needs grow.
Actual cost depends heavily on hardware, connectivity, number of users, and site-specific requirements — we work through real numbers directly with each organization once scope is clear.
What each side would bring
Being upfront about this now avoids surprises later — here's a realistic split of responsibilities for a site.
Brightcodex would provide
- The software platform and edge server setup, configured for each module a site needs
- Integration with solar and connectivity hardware, working alongside solar/network installer partners
- Ongoing software support, monitoring, and updates
- Training for on-site staff to use the system day to day
The partner organization would provide
- Physical space and basic site access for the local server and network equipment
- A local point of contact or staff member to operate the system day to day
- Any permissions, land access, or approvals needed for solar or connectivity installation
- Existing records to migrate in where applicable — e.g. a patient list or farmer registry
Built by a working studio, not just a pitch deck
Brightcodex already designs and builds AI agents, automation, web apps, mobile apps, and custom software for real clients. This initiative applies that same team and technology to a new, offline-first context — it isn't coming from a team with nothing behind it.
Who we'd want to build this with
Questions departments and organizations usually ask
- What happens if the local hardware fails?
- Local backups mean data isn't lost even if a device needs replacing. A maintenance and replacement plan is part of the ongoing support model, not something left for the site to handle alone.
- Isn't this the same as just installing internet at the site?
- No. Even with a connection, outages are common in these areas. Having a local server means staff never lose access during one, and nothing entered offline is ever at risk of being lost when the connection drops.
- How is patient, citizen, or farmer data protected?
- It stays on local, on-site infrastructure by default and isn't sent anywhere until sync is authorized. Access is role-based, so, for example, pharmacy staff wouldn't see full patient histories, and a field officer would only see their own assigned records.
- Do staff need technical training to use it?
- It's designed for the people already doing these jobs — reception staff, teachers, field officers — not IT specialists. Training on the actual workflow is part of setup.
- Can this integrate with a system we already use?
- Where an organization already has an existing system or dataset, we'd design the sync and migration around it rather than requiring a clean slate — that gets scoped per organization.
- What if we only need one module, not all ten?
- Each module is independent. A school doesn't need the healthcare module, a clinic doesn't need agriculture — you'd start with only what's relevant to you.
Want to see this in more detail?
We're happy to walk through the architecture, the modules, and the rollout plan in person — for a district, a department, or an organization looking at what a first site would look like.