MicrogridModeler vs Energy Toolbase: off-grid feasibility or solar-and-storage proposals in 2026?

Key takeaways

• MicrogridModeler and ETB Developer can both be used through a web interface, but they are optimized for different deliverables: remote-site adequacy versus solar-and-storage project economics and proposals.
• ETB Developer is especially useful when tariff details, demand charges, net metering, incentives, financing, and client-facing documents can decide whether a commercial project moves forward.
• MicrogridModeler keeps PV, battery state of charge, diesel operation, unmet load, fuel use, and lifecycle economics tied to one deterministic chronological feasibility case.
• Energy Toolbase has separate modeling, control, and monitoring products; a controls deployment does not by itself establish the diesel-sizing or off-grid-adequacy boundary of ETB Developer.
• HOMER Pro and REopt remain important alternatives when the study needs broader hybrid components, sensitivity analysis, formal DER optimization, or resilience analysis.

Comparison matrix

Direct answer: choose the deliverable before the tool

Choose MicrogridModeler when the immediate deliverable is a defensible answer to an off-grid adequacy question: how much PV, battery power and energy, and diesel capacity the site needs; how the system operates through the modeled chronology; which hours are difficult; how much fuel it burns; whether any load is unserved; and what the lifecycle economics look like.

Choose ETB Developer when the project is a commercial solar or storage opportunity and the central work is reconstructing the utility bill, applying the correct tariff and net-metering rules, estimating solar and storage savings, comparing incentives and financing structures, and turning the result into a proposal. Its public product materials emphasize front-of-meter and behind-the-meter solar and storage, not remote diesel-hybrid adequacy as the core workflow.

That is not a quality ranking. It is a boundary check. A remote telecom site and a grid-connected warehouse can both contain PV and batteries while requiring very different software. HOMER Pro is a stronger candidate when the first question spans many hybrid components and sensitivities. REopt is a strong candidate when a facility or campus needs formal DER sizing, dispatch, lifecycle-cost, and resilience optimization.

A web interface does not make two tools interchangeable

Both MicrogridModeler and ETB Developer reduce the friction of a desktop-only workflow. Energy Toolbase describes ETB Developer as a web-based platform that can be accessed anywhere with an internet connection. MicrogridModeler likewise runs its focused modeler in the browser. For distributed EPC and consulting teams, that shared accessibility is useful.

Energy Toolbase also says ETB Developer calculations run on the user’s local device, which is why its minimum-system guidance discusses processor speed and memory. In other words, “web-based” describes access, not necessarily remote compute. That distinction matters when teams set hardware expectations or use browser architecture as a proxy for model behavior.

The workflows diverge beyond the browser frame. MicrogridModeler is organized around a deterministic energy-feasibility ledger for an islanded PV + battery + diesel plant. ETB Developer is organized around leads, meters, energy-use profiles, designs, proposals, documents, and web proposals. Its hierarchy reflects a project-development and sales process in which utility data, customer scenarios, and deliverables matter as much as the energy assets.

Ask what must be true at the end of the study. If the answer is “the system survives the difficult hours without violating the unmet-load rule,” start with an adequacy model. If the answer is “the customer sees a credible bill, savings, financing, and proposal comparison,” start with a tariff-and-project-development model. Some projects need both.

Where MicrogridModeler fits

MicrogridModeler deliberately narrows the technology set to off-grid solar PV, battery storage, and diesel generation. That focus makes it possible to keep capacities, dispatch, state of charge, generator operation, curtailment, unmet load, fuel, replacements, NPC, LCOE, and the diesel-only baseline connected in one reviewable run.

The deterministic search and standardized output package are useful when multiple analysts must reproduce the same answer or explain why one design passed the constraints and another failed. A site planner can inspect the hours that actually drive storage depletion or generator operation instead of relying on annual production and savings alone.

Its boundary is equally important. MicrogridModeler is not a utility-bill proposal system, a rate-maintenance service, a CRM, an onsite EMS, or a substitute for electrical design, protection, controls, commissioning, and vendor engineering. Use its result to establish and explain the candidate energy architecture, then hand that architecture into the next project workflows.

• Use it when the site is islanded or remote and PV, battery storage, and diesel are the core technologies.
• Use it when chronology, state of charge, generator operation, fuel, and an unmet-load constraint decide feasibility.
• Use it when planners, students, and reviewers need a consistent browser-run case with visible assumptions.
• Add other software when tariffs, customer proposals, electrical networks, controls, or broader technologies can change the decision.

Where Energy Toolbase is the practical choice

ETB Developer is especially strong when the project lives on a customer meter, while Energy Toolbase also positions it for front-of-meter solar and storage projects. Its official workflow accepts monthly electric bills, spreadsheet interval data, Green Button data, or a utility-data integration. If only bills are available, the platform can construct a representative interval profile from the customer history and building type, which is useful during early development as long as the synthetic profile is clearly identified.

Tariff detail is a major differentiator. Energy Toolbase maintains a large utility-rate library and supports time-of-use periods, demand charges, ratchets, net-metering and billing configurations, rate switches, and custom tariffs. Those details can materially change a commercial solar or storage result even when annual energy stays the same.

The platform also connects technical scenarios to project development. Current materials describe solar and storage modeling, incentives, equipment configurations, cash purchases, PPAs, leases, loans, proposal templates, web proposals, and integrations with PV design and financing providers. For a commercial developer or EPC sales team, producing a consistent analysis and a client-ready document can be the job, not an afterthought.

The right caution is to preserve the exact tariff version, interval-data treatment, assumed degradation, dispatch strategy, incentives, financing terms, equipment data, and scenario settings behind the proposal. A polished document is easier to trust when the analyst can reconstruct every number.

“Optimization” means little until the objective is named

Energy Toolbase, MicrogridModeler, HOMER Pro, and REopt all use optimization language, but they do not optimize the same decision. ETB documentation says its Power Rating and Storage Capacity Optimizers calculate and display dollar savings for ten different system sizes. Its storage strategies include demand-charge management, energy arbitrage, a combination of the two, and solar self-consumption.

Those are valuable grid-connected objectives. They are not the same as proving that an islanded system maintains adequate energy through a multi-day low-solar event while tracking generator fuel and an explicit unmet-load rule. MicrogridModeler centers that latter question. HOMER Pro evaluates hybrid configurations and sensitivities. REopt uses a mixed-integer linear program to recommend technology sizes and hourly dispatch for lifecycle cost, resilience, or other modeled goals.

A fair comparison therefore starts with one written objective and one shared dataset. Hold load, resource, equipment performance, costs, project life, degradation, financing, and operating limits steady wherever the tools allow. Then explain any difference in time resolution, boundary, dispatch logic, tariff model, feasibility rule, and objective before comparing the headline result.

Do not confuse ETB Developer with ETB Controller

Energy Toolbase is a product suite. ETB Developer handles modeling and proposals. ETB Controller is an energy-management product for deployed battery systems, and ETB Monitor provides operational and financial visibility. Current Controller materials describe remote configuration, real-time and historical monitoring, utility-aware battery dispatch, demand-response and grid-program participation, and operational support.

Energy Toolbase also publishes compatible-hardware documentation with some islanding arrangements that combine a BESS, PV, and controlled or uncontrolled generators, so it would be inaccurate to call the entire suite grid-tied only. At the same time, a current microgrid buyer-scope document assigns low-voltage drawings, sequence of operations, backup-load analysis and battery sizing, switchgear, PV equipment, and generator or generator-controller scope to the buyer, while describing ETB guidance and equipment-specific requirements. That is a useful reminder that controls deployment is not the same as complete microgrid design.

Before treating an Energy Toolbase controls project as a substitute for an off-grid feasibility model, ask the vendor to demonstrate the exact generator, islanding, black-start, reserve, fuel, autonomy, and failure-mode scope that applies to the proposed hardware and service plan. Likewise, do not treat a MicrogridModeler feasibility run as an EMS specification. The planning result and the deployed controller belong to different stages of the project.

Build the audit trail around the decision, not the brand

MicrogridModeler standardizes a narrow run package so that the inputs, model version, dispatch, constraints, and economics stay together. ETB Developer supports a broader customer-development record with leads, meters, profiles, designs, documents, and proposals, and its documentation lets users download all design data or selected interval-data outputs. Either workflow can be reviewed well or poorly depending on what the analyst retains.

For an Energy Toolbase study, archive the original bills and interval files, time zone and units, tariff name and effective date, every custom charge or net-metering rule, the baseline and post-project rate, PV and storage equipment assumptions, degradation, dispatch strategy, incentives, transaction terms, and the exact document issued to the customer. Recheck demand ratchets and historical peaks that may fall outside the supplied data window.

For an off-grid study, archive the load and weather chronology, initial battery state, usable capacity, efficiency, generator fuel curve and minimum loading, reserve and unmet-load settings, replacement assumptions, project life, discount rate, difficult-hour dispatch, and the precise model version. Good auditability is the ability to reconstruct the decision, not merely the ability to export a PDF.

Where HOMER Pro and REopt fit

HOMER Pro remains a broad direct comparison for remote and islanded hybrid planning. Current official materials describe full-year simulation at time steps from one minute to one hour, solar, wind, batteries, diesel and other fuels, configuration evaluation, least-cost optimization, controller choices, and sensitivity analysis. It is a sensible choice when technology breadth and “what if?” cases outweigh the value of a narrower browser-first workflow.

REopt is closer to Energy Toolbase when utility economics matter, but its model boundary and output are different. Current NLR materials describe a mixed-integer linear program for buildings, campuses, and microgrids that recommends DER sizes and an hourly dispatch, models utility charges and market revenues, and can evaluate lifecycle cost, resilience, and critical-load support. The public web tool, API, and open-source code support several levels of use.

A practical map is: MicrogridModeler for focused, auditable off-grid PV + battery + diesel feasibility; ETB Developer for commercial solar-storage tariffs, savings, finance, and proposals, with separate ETB products for controls and monitoring; HOMER Pro for broad hybrid configurations and sensitivity analysis; and REopt for formal facility DER and resilience optimization.

A practical workflow for EPC and consulting teams

Start with the commercial and operational boundary, then use the smallest tool that answers the current decision. Do not force an islanded adequacy model to become a tariff CRM, and do not assume that a bill-savings optimizer has proved remote-site autonomy.

• Define the point of interconnection, outage or islanding expectation, critical and noncritical loads, technology set, project objective, and required deliverables.
• Clean the source load data and preserve timestamps, interval length, time zone, units, gaps, bills, meter identifiers, and provenance.
• For a remote PV + battery + diesel concept, use MicrogridModeler to screen capacities, chronological dispatch, difficult hours, state of charge, diesel operation, fuel, unmet load, NPC, and LCOE.
• For a grid-connected commercial solar or storage opportunity, use ETB Developer to reconstruct the bill, verify the tariff, compare PV and storage scenarios, apply incentives and financing, and build the customer proposal.
• If the project needs broader hybrid technologies or systematic sensitivities, add HOMER Pro; if it needs formal facility DER and resilience optimization, add REopt.
• For an Energy Toolbase controls deployment, separately define the controller, communications, meters, switchgear, islanding equipment, generator interface, sequence of operations, commissioning, warranties, and buyer responsibilities.
• Reconcile annual energy, interval peaks, battery throughput, grid imports and exports, generator energy, project cash flow, and all constraints before explaining differences between models.
• Move the selected architecture into electrical, protection, controls, civil, permitting, safety, vendor, and stamped-engineering workflows before procurement.

A useful tool-selection exercise for students

Students can learn more by modeling two sites than by declaring one platform the winner. Give the first site an islanded load, PV, battery storage, diesel generation, and a zero-unmet-load target. Use MicrogridModeler to find the hours that determine capacity, fuel, and feasibility.

Give the second site a utility meter, time-of-use energy charges, demand charges, rooftop solar, storage, an incentive, and two financing choices. Use Energy Toolbase or a carefully audited spreadsheet to examine bill reconstruction, tariff effects, storage value, and the proposal. Then use HOMER Pro or REopt to show how a different optimization boundary changes the question.

The report should state the objective, model boundary, inputs, time resolution, dispatch rule, feasibility definition, financial assumptions, outputs, and missing engineering for every case. Tool selection is part of the engineering argument.

Bottom line

Choose MicrogridModeler for a focused, deterministic, auditable answer to off-grid PV + battery + diesel feasibility. Choose ETB Developer when a commercial solar or storage project turns on utility-rate accuracy, bill savings, incentives, financing, scenario management, and client-ready proposals. Consider ETB Controller and Monitor separately when the project needs deployed storage control and operations.

Choose HOMER Pro when broad hybrid-system choices and sensitivity analysis are central. Choose REopt when the facility needs mathematical DER optimization, hourly dispatch, lifecycle economics, resilience, and web or API access. Advanced projects can use more than one tool, provided each handoff preserves assumptions and reconciles the overlapping outputs.

The generous answer is that each product is strongest when its model boundary matches the decision. Write the question first, keep the evidence behind the result, and let the project—not the software category—choose the workflow.

Continue your comparison

Sources and review notes

This comparison is based on public product and documentation pages reviewed for the 2026 planning context. Always verify current licenses, modules, and pricing before making procurement decisions.

FAQ