Earth Force Technologies

**Product and the concrete problem it solves.** Earth Force Technologies is tackling a very physical bottleneck in wildfire resilience: communities and land managers know that reducing hazardous fuel and restoring forest health can lower fire intensity, but the work is slow, labor-intensive, dangerous, and difficult to supervise across large or remote landscapes. Conventional vegetation-management projects often depend on crews manually marking trees, flagging boundaries, driving long distances to inspect work, and assembling reports after the fact. That operating model makes it hard to treat enough acreage before the next fire season, particularly when trained forestry labor is scarce and projects must satisfy landowner, environmental, and public-funding requirements. Earth Force's current public website describes a platform for precision fuel treatments at landscape scale. Its Guide product uses precision sensors and an in-cabin tablet to provide operators with maps, alerts, and tree-level insights while work is underway, while Portal is a web application that automates field reporting and gives administrators a near-real-time view of project progress and ground truth. The commercial promise is not merely wildfire detection; it is to make prevention work itself more scalable, auditable, and operationally consistent.

**Core technology and how it actually works.** The technology stack combines physical sensing, positioning, operator assistance, connectivity, and software workflow rather than relying on a single novel sensor. Earth Force says Guide brings precision sensors and an in-cabin tablet into forestry machinery, allowing an operator to see mapped prescriptions, alerts, and tree-level information while navigating a treatment area. The intended loop is: convert a forest-management plan into machine-readable boundaries and treatment instructions, localize the equipment and its work, surface relevant information at the point of operation, and transmit field observations to the administrative layer. The earlier financing announcement described a broader productivity system centered on jobsite connectivity, teleoperations, digital tools, and sensor data, including the possibility of conducting work from a safer workstation. An IVC ecosystem record additionally describes precision GPS, field connectivity sensors, remote-controlled machines, material handling, fire monitoring, and spot-fire suppression as parts of the company's development direction. The current website is more specific and restrained than that earlier description: it emphasizes treatment preparation, real-time guidance, and transparent administration, not a proven autonomous firefighting fleet. Public materials do not disclose sensor brands, localization error, connectivity protocols, autonomy boundaries, machine-control interfaces, data architecture, or independently measured productivity improvements, so those details remain important technical diligence questions.

**Market, customers, and go-to-market.** Earth Force sells into a fragmented but strategically important market spanning forestry contractors, timber and plantation operators, conservation organizations, land managers, utilities, public agencies, and communities exposed to wildland-urban interface risk. The company describes collaboration with innovative land managers but does not publicly name current customers, contract values, treated acreage, annual recurring revenue, or renewal rates. Its go-to-market appears to combine software with field hardware and operational integration: Guide must fit into existing machinery and work practices, while Portal gives project owners and administrators a reason to adopt the system beyond a single machine operator. That creates several possible commercial models, including software subscriptions tied to managed acres, equipment or sensor packages, implementation services, and partnerships with forestry-service providers. The U.S. is an obvious initial market because wildfire prevention budgets and the scale of catastrophic fires are large, but the underlying problem also exists in Mediterranean Europe, Australia, Canada, and other fire-prone regions. The Tel Aviv branch and Israeli technical team provide ecosystem relevance, but there is no public evidence that Israel is the primary revenue market or that the company has secured Israeli government or defense procurement. The central commercial test is whether Earth Force can move from a useful field-operations tool to a repeatable platform with measurable savings in project preparation, crew productivity, inspection time, compliance reporting, and acres treated per season.

**Traction, funding, and third-party validation.** Earth Force announced an $8.6 million seed round on November 29, 2022, led by Alley Robotics Ventures with participation from Bold Capital Partners and Third Sphere. The announcement said the capital would support a vegetation-management system built around teleoperation, jobsite connectivity, sensors, and digital tools, and framed wildfire prevention as an urgent market constrained by labor shortages and physically dangerous work. IVC lists the company as an R&D-stage cleantech business established in 2022, with 18 employees, a San Francisco headquarters, and a Tel Aviv branch; it identifies Justin Dawe and Ran Livneh as CEO/co-founder and CTO/co-founder and records the seed financing. LinkedIn currently places the company in the 11–50 employee range, lists both San Francisco and Tel Aviv locations, and shows recent recruiting for a Hardware Manufacturing Lead, Director of Program Success, and Head of Product for Forestry. The Tel Aviv Sparks innovation festival identifies Livneh as CTO and co-founder and connects him to the company's resilient-forest mission. These are credible operating and ecosystem signals, but they do not prove scaled deployment. No reviewed source establishes a named commercial reference, a government contract, recurring revenue, a completed production rollout, or independent field-performance data. The positive interpretation is that the company is still building a difficult hardware-software operating system; the cautious interpretation is that commercialization remains to be demonstrated publicly several years after the seed round.

**Founders and team background.** The public record identifies Justin Dawe as founder and CEO, Dan Schreter as a co-founder, and Ran Livneh as CTO and co-founder. Livneh is the most strategically relevant technical figure disclosed: Tel Aviv Sparks describes him as a Talpiot alumnus with a PhD in astrophysics from the Weizmann Institute of Science, an MBA from Tel Aviv University completed with distinction, and prior senior roles in an IDF intelligence technology unit where he led teams applying advanced technology to difficult operational problems. IVC lists Alon Shavit as Chief Architect and notes prior system-architecture work at Huawei Israel R&D, alongside Geoff Staneff as VP Product and Systems and Itamar Goldminz as VP Corporate. Dawe's public role is tied to the climate and technology commercialization side, while Livneh provides a credible bridge between Israeli deep-tech engineering, sensing, and resilience use cases. The team composition appears appropriate for a system that has to combine machinery, embedded software, field operations, and administrative workflows. However, the public record does not establish the full engineering roster, manufacturing capacity, forestry-domain staffing, safety organization, or government-sales capability. For a company operating in remote and hazardous environments, the next diligence step is to understand who owns machine certification, operator safety, sensor calibration, fleet support, data security, and deployment economics.

**Competitive dynamics.** Earth Force competes against several layers of alternatives rather than one direct software rival. **BurnBot** uses remotely operated machines and prescribed-fire techniques to treat vegetation, competing for the same fuel-reduction and operational-safety budgets through a different physical intervention. **Drone Amplified** applies drones and precise ignition systems to prescribed burns, offering a more aerial approach to controlled treatment. **Overstory** uses satellite, aerial, and geospatial AI to analyze vegetation and wildfire risk, competing for the intelligence and planning portion of the workflow. **Pano AI** and **Dryad Networks** address wildfire detection and monitoring rather than fuel-treatment execution, but they can absorb resilience budgets when buyers prioritize early warning over prevention. The incumbent alternative is the large network of forestry, land-management, and fuels-reduction contractors using conventional machinery, maps, spreadsheets, radio communications, and manual inspection. Earth Force's possible edge is workflow integration: the company can connect a treatment prescription to machine guidance, field evidence, and administrative reporting instead of selling only imagery, only a robot, or only a detection alert. That position could create useful data and switching costs if it proves that operators treat more acreage with fewer preparation hours and better compliance evidence. The vulnerability is that large equipment manufacturers, geospatial vendors, contractors, or wildfire-technology platforms could add overlapping guidance and reporting features, while customers may prefer familiar service providers to a new hardware-software stack.

**Defense, security, and resilience dual-use relevance.** Earth Force's core capability has credible dual-use value through critical-infrastructure and territorial resilience, although the public record does not show a defense product or military customer. Wildfire prevention protects communities, energy corridors, water infrastructure, transport routes, communications sites, and other assets whose loss can create cascading security and continuity problems. The same combination of positioning, sensors, remote supervision, machine guidance, and distributed field reporting could support vegetation clearance around bases, airports, power lines, pipelines, rail corridors, and emergency-access routes. Teleoperation also has a direct safety value in post-fire or disaster environments where unstable terrain, smoke, heat, unexploded hazards, or damaged infrastructure make close human inspection undesirable. Livneh's prior IDF intelligence-technology experience creates a credible Israeli defense-technology adjacency, but it should not be converted into an unsupported claim of defense deployment. There is no public evidence of military procurement, classified work, defense accreditation, secure communications, cyber-hardening, degraded-GPS operation, or integration with government command systems. The most defensible assessment is therefore resilience-first dual use: Earth Force's commercial forestry platform could strengthen civil protection and infrastructure continuity, and selected modules could transfer to security and emergency-management missions if they are ruggedized, secured, and validated in those environments. Diligence should examine data sovereignty, remote-control cybersecurity, fail-safe behavior, spoofing and jamming tolerance, operator authorization, and the consequences of a wrong treatment decision near a protected asset.

**Growth stage, trajectory, and key diligence risks.** Earth Force is best classified as early stage. It has a real platform thesis, a disclosed seed round, an identifiable Israeli-linked technical team, and current recruiting, but public evidence does not yet establish scaled commercial operations. Its trajectory depends on turning difficult field work into a repeatable product and service model: prove that Guide improves operator performance and treatment precision, prove that Portal reduces project-administration costs, build reliable integrations with forestry machinery, and show that land managers will pay for the system across multiple seasons and geographies. The key risks are: (1) hardware and field-service intensity may make deployment expensive and constrain gross margins; (2) forests vary materially by species, terrain, climate, regulation, and treatment prescription, limiting simple software generalization; (3) remote operations create safety, connectivity, cybersecurity, and liability obligations; (4) public agencies and land managers often buy services through slow, fragmented procurement cycles; (5) established contractors and equipment makers may bundle enough software to neutralize the platform's differentiation; (6) the company has not publicly disclosed revenue, named customers, treated acreage, unit economics, patents, or independent performance benchmarks; and (7) the dual-use upside remains an adjacency until security-sector validation occurs. Milestones worth tracking are named repeat customers, field productivity and safety measurements, acres treated through the platform, machine-manufacturer partnerships, multi-season renewals, deployment outside the U.S., and a documented critical-infrastructure or emergency-management evaluation.