On-grid, hybrid, or off-grid: choosing the right solar architecture for your site.

The first question is what problem the system is supposed to solve.

This sounds obvious, and it is consistently skipped. Buyers ask about panels, kWp ratings, brand options, and price per kilowatt. Sellers respond on those terms because that is what is being asked. By the time anyone asks what the system is actually meant to do, the architecture has already been quietly assumed — usually toward whichever option produces the largest invoice.

A serious solar conversation starts with the objective, then identifies the architecture that serves that objective, then sizes the system, then selects equipment. Reversing that sequence — equipment first, sizing second, objective fitted afterward — is how sites end up with systems that do not fit their actual needs.

Almost every solar project in Morocco serves one of four objectives. The architecture follows from the objective, not the other way around.

Bill reduction. The site has a working grid connection, the grid is reasonably stable, and the goal is to produce solar electricity during the day to reduce the energy purchased from the grid. This is the most common objective, and the one that on-grid architecture serves most efficiently.

Backup for selected loads. The site has a working grid connection, but power cuts are frequent or operationally costly enough that certain circuits — refrigeration, lighting, pumps, IT, medical equipment, critical production — must keep running through outages. This is the territory of hybrid architecture, where solar production, battery storage, and grid availability are managed together.

Energy autonomy. The site wants to operate independently of the grid for ideological, operational, or strategic reasons. This is a more demanding objective than backup. It requires more storage, more design discipline, and continuous attention to consumption patterns. Off-grid architecture serves this objective, sometimes paired with a generator for difficult periods.

Remote-site electrification. The site has no grid connection, or extending the grid is impractical or prohibitively expensive. Solar is not a choice between options here; it is one of the only options. Off-grid architecture is the default response, often with a generator for backup.

These four objectives are not always mutually exclusive. A site can have a primary objective and a secondary one — for example, bill reduction with light backup capability for a small set of critical loads. The architecture decision then becomes a question of which objective is primary and how the secondary objective is served without compromising the primary one.

An on-grid system is usually designed for self-consumption. The site uses solar electricity while it is being produced, reducing the amount of electricity bought from the grid during the day. Solar panels produce electricity, an inverter converts it to grid-compatible AC, and the energy flows directly into the site’s loads in real time. At night and during low-production hours, the grid supplies whatever the site needs.

In some countries, unused solar electricity can be exported or credited easily. Morocco should not be presented that way for ordinary low-voltage clients. As of the date of this article, surplus-sale rules are clearer for medium-voltage and higher-voltage projects. For low-voltage projects connected at 230/400 V — most homes, villas, small shops, and many small businesses — the practical design should not depend on selling unused electricity to the grid.

This is why on-grid sizing matters. A system that is too large may produce electricity the site cannot fully use, store, or value. The decision logic for on-grid is therefore built around three conditions. The grid must be reasonably stable. The site must have enough daytime consumption to absorb solar production directly. And backup during outages must not be a requirement, because on-grid systems shut down when the grid is unavailable — a safety requirement that protects line workers and the grid itself.

What on-grid does well: it delivers the highest production-to-cost ratio of the three architectures, requires no battery, ages slowly when properly installed, and is the simplest to monitor and maintain. What it does not do: it provides no backup, no autonomy, and no protection against grid quality issues unless paired with separate equipment.

For most grid-connected sites where the objective is genuinely bill reduction — a primary residence in a stable urban area, a daytime-occupied office, a hotel with strong daytime consumption, a workshop running daylight hours, an agricultural site with daytime pumping — on-grid is the architecture that should be considered first. It is also the architecture most often unnecessarily complicated by quotes that bolt on batteries the site cannot economically justify.

Hybrid systems use a hybrid inverter capable of managing solar production, grid availability, and a battery simultaneously. During the day, solar charges the battery and supplies loads. In the evening, the battery covers selected loads. The grid remains available as a fallback, both for charging the battery during prolonged low-production periods and for supplying loads beyond what the battery is sized for.

When the grid fails, the hybrid inverter — paired with the battery — keeps designated circuits running. This is what makes hybrid architecture distinct from on-grid: it survives grid outages, but only for the loads it was designed to carry, and only for the autonomy duration the battery supports.

The decision logic for hybrid is built around defined purpose. A hybrid system without a clearly defined backup purpose is a hybrid system that is going to disappoint. Which circuits will the battery feed? For how many hours? How often is it expected to discharge? These questions belong in the proposal, not in a vague "you’ll have backup" reassurance.

Hybrid is the right architecture for sites where outages have an operational cost — hospitality, healthcare, food storage, cold chain, IT-dependent businesses, remote-controlled systems — and for sites where evening shifting of solar energy is genuinely valuable. It is the wrong architecture when "backup" is asked for vaguely, without analysis of what actually needs to be backed up.

Off-grid systems have no grid connection. Production comes from the panels, storage comes from a battery bank, and a generator is often included to cover extended low-production periods. The site depends entirely on this combination, and the system must be designed to survive a worst-case sequence of bad weather days, high consumption events, and equipment service intervals.

The decision logic for off-grid is built around the absence of a real grid alternative. The site has no grid connection, the grid extension is uneconomical, or the grid that exists is so unstable that disconnecting from it is operationally cleaner than depending on it. These are specific contexts: remote farms, isolated rural homes, mountain auberges, desert installations, agricultural pumping sites distant from infrastructure, certain eco-lodges, off-network telecommunications equipment.

Off-grid is more expensive than hybrid. It requires larger battery banks, more conservative system design, planned generator integration, and more disciplined consumption behavior from the site’s users. It is also more demanding to maintain, because the consequence of a fault is not "the grid takes over" — there is no grid to take over.

What off-grid is not: it is not a premium upgrade for a grid-connected site. It is not "the most independent" version of solar that aspirational buyers should default to. For most sites with a working grid connection, off-grid is overengineering with significant ongoing costs and behavioral demands. For most sites with a working grid connection, the honest answer is usually no — unless there are unusual operational, reliability, or strategic reasons that justify the additional complexity.

A common assumption is that hybrid is the "next level" after on-grid — the upgraded version with batteries added. This framing produces poor decisions.

A battery is a major component with its own cost, its own lifespan, its own maintenance profile, and its own replacement schedule. Adding a battery to a system that does not have a defined backup purpose adds expense, complexity, and a future replacement cost without proportional benefit. The system produces the same solar energy whether or not a battery is attached. The only thing the battery adds is the ability to use that energy at a different time, or to keep selected loads running during a grid outage. If neither of those abilities is needed, the battery is decorative.

Hybrid is the right choice when there is a defined purpose. It is the wrong choice when it is added to a quote because it makes the proposal look more comprehensive, or because the seller benefits from a higher invoice. The honest test is straightforward: if removing the battery from the proposal would cost the site nothing in real operational terms, the battery is not justified.

Off-grid is sometimes positioned as the most advanced, most independent, most premium version of solar. It is none of those things — it is a specific solution for specific constraints, and outside those constraints it is a more expensive, more demanding, more failure-sensitive version of solar than the alternatives.

A grid-connected home that switches to off-grid is taking on full responsibility for energy availability. Every kilowatt-hour the site consumes must come from solar production or from stored energy. There is no fallback. Bad weather sequences, unexpected consumption events, and equipment faults all become events the site itself must absorb, often with consumption restrictions or generator intervention.

For sites that genuinely need off-grid — remote, gridless, or operationally isolated — off-grid is the right answer and the only answer. For sites with a working grid connection, off-grid is generally a downgrade in resilience compared to a properly designed hybrid system that can use the grid as one of multiple resources.

The three architectures are not abstract. The same architecture behaves differently and is sized differently depending on the type of site it serves. A hybrid system for a riad is not a hybrid system for a dairy farm. An on-grid system for an office building is not an on-grid system for a rural pumping installation. Recognizing how site type affects architecture is what turns this framework into a real decision tool.

Homes and villas

For homes and villas, on-grid is the most common appropriate architecture, particularly for primary residences in urban areas with reasonably stable grid access. Hybrid becomes appropriate when outages are frequent enough or operationally costly enough — water pumps that depend on electricity, cold storage of medication, work-from-home dependencies, families with young children who cannot easily tolerate evening outages — to justify the additional cost. Off-grid is rarely appropriate for a grid-connected home, but it is the right answer for isolated rural homes and remote villas without practical grid access.

Hotels and riads

For hospitality, the architecture decision is operationally driven. Refrigeration, hot water circulation, IT, security, reception, and selected guest comfort circuits cannot tolerate prolonged outages without commercial consequences. This can push many hospitality projects toward hybrid logic, but only when the backup circuits and autonomy target are clearly defined. On-grid remains appropriate for properties where the grid is highly stable and the site’s evening obligations can tolerate outages. Off-grid is appropriate for remote eco-lodges, isolated kasbahs, and sites where grid extension is not realistic.

Farms and solar pumping sites

For agricultural sites, the architecture decision often centers on water storage rather than electrical storage. A solar pumping system that produces water during the day and stores it in elevated tanks may not need a battery at all — the water itself is the storage. Other agricultural sites have continuous loads (cold storage of produce, dairy refrigeration, monitoring systems) that change the equation. The right architecture depends on whether storage is electrical, hydraulic, or operational, and on whether the site has grid access at all.

Businesses and industrial sites

For commercial and industrial sites, the architecture decision depends heavily on load profile and operational continuity requirements. A workshop running daylight hours with predictable daytime loads is a strong candidate for on-grid. A facility with continuous production, sensitive equipment, or critical processes is more often a hybrid candidate, with backup designed around production continuity rather than general site coverage. Power quality concerns may also enter the decision in industrial environments. Off-grid is rare for grid-connected commercial sites and appropriate mainly for isolated industrial installations.

Remote sites

For remote sites — agricultural pumping installations, telecommunications equipment, isolated buildings, off-network monitoring stations — off-grid is often the default architecture, sometimes with generator support for extended low-production periods. The design discipline these sites require is significantly higher than for grid-connected installations, because there is no grid to absorb errors in sizing or consumption forecasting.

The architecture decision can be approached as a structured comparison across criteria that the site’s owner or operator can evaluate honestly. No single criterion produces the answer; the right architecture is the result of weighing several criteria together.

The criteria worth considering include:

• Grid availability and reliability. Is the grid present and stable, present and unstable, or absent? This is the threshold question that determines whether off-grid is even a consideration.
• Outage frequency and operational cost. How often does the grid actually fail, and what does it cost the site when it does? Vague concerns about outages do not justify backup investment; specific operational costs do.
• Daytime consumption alignment. What share of the site’s energy use occurs during sunlight hours? Sites with strong daytime alignment benefit from on-grid more directly than sites with predominantly evening consumption.
• Critical load definition. Are there specific loads that must keep running during an outage? Can they be defined explicitly and sized for? If yes, hybrid is in scope. If no, hybrid may be unjustified.
• Financial objective. Is the goal payback on bill reduction, or is it operational continuity that is being valued for non-financial reasons? Both are valid, but they lead to different architectures.
• Maintenance capacity. Does the site have the operational discipline to maintain a battery system, monitor production, coordinate warranties, and respond to faults? Off-grid in particular demands more of the site than on-grid does.
• Site access and isolation. How quickly can technical support reach the site if something fails? Remote sites need conservative design because they cannot easily be visited.
• Future expansion. Is the site likely to grow its load, add storage, or add additional production capacity later? Some architectures accommodate phased expansion more easily than others.

The right architecture is rarely the result of a single criterion. It is the result of weighing several criteria honestly and recognizing which ones matter most for the site in question.

Real installations are not always clean textbook categories. A serious engineering team will sometimes propose configurations that sit between the three classical architectures, and a knowledgeable reader should recognize what these are.

A hybrid system can be configured to behave mostly like an on-grid system, with a small battery sized only for backup of a defined critical-loads panel rather than for evening shifting. The site captures most of the on-grid economics while gaining narrow backup capability for a specific purpose.

An off-grid system paired with a generator becomes a kind of "off-grid hybrid" — solar and battery cover normal operation; the generator covers extended low-production periods or unusually high consumption events. This is common in agricultural and remote installations and reflects responsible design rather than weakness.

Some larger commercial, medium-voltage, or high-voltage projects in Morocco may operate under grid agreements that allow specific injection or surplus-sale arrangements, subject to the project’s voltage level, distributor or network operator, connection conditions, and applicable framework. These cases are project-specific and must be confirmed for each site — they are not a default for ordinary low-voltage installations. Where they apply, they affect how an on-grid or hybrid system is configured and may push the design toward arrangements that look slightly different from the textbook version.

Solar pumping sites often store energy in water rather than in batteries, with elevated tanks acting as the storage medium. The architecture in these cases may not involve a battery at all, even though the site is technically off-grid.

Some larger or more complex sites are best served by phased designs — an on-grid system installed first, with hybrid functionality added later when battery costs evolve or when a specific backup need is documented. This is engineering discipline, not indecision.

The framework of three architectures remains valid. Recognizing that real designs sometimes blend them is part of what distinguishes engineering from product selling.

A solar proposal worth signing makes the architecture decision visible. It tells you which architecture has been chosen and why, what objective it is designed to serve, and how that decision was made. Specifically, the proposal should contain:

• A clear statement of the architecture chosen (on-grid, hybrid, off-grid, or a defined hybrid configuration).
• The site objective the architecture is designed to serve.
• A reference to actual consumption data, ideally twelve months of bills.
• The basis for the system size — kWp on the panel side, inverter rating, battery capacity if applicable.
• For hybrid systems: the defined backup circuits, expected autonomy under those circuits, and how the system behaves during outages.
• For off-grid systems: the design discipline assumed, generator integration if applicable, and any consumption assumptions the system depends on.
• Estimated annual production based on stated solar-resource assumptions.
• Expected self-consumption ratio.
• A modeled financial scenario with stated assumptions, presented as a range rather than a single guaranteed number.
• Equipment specifications, warranty terms, and post-installation support arrangements.

If most of these elements are missing, what you have received is a price for hardware. It is not a proposal for an engineered system.

Use this before accepting any solar architecture recommendation.

• Has the system's objective been clearly defined before architecture was discussed?
• Is the chosen architecture explicitly justified in the proposal — not just stated?
• If hybrid, are the specific backup circuits defined?
• If hybrid, is the battery sized to a specific autonomy target under those circuits?
• If off-grid, is generator integration addressed honestly?
• Has actual consumption data been used to size the system?
• Are production and self-consumption estimates accompanied by stated assumptions?
• Is the financial scenario presented as a range with assumptions, not a single guaranteed number?
• Are equipment specifications, warranty terms, and post-installation support clearly described?
• Has the architecture decision been engineered to fit the site, rather than commercially defaulted?

ReneWave starts every solar conversation with the architecture decision, not the equipment. The first question is not "how many panels?" but "what is this system supposed to do?" — and the answer to that question shapes everything that follows.

For most sites, this means beginning with the actual consumption data, the operational reality of the site, and the objective the owner is trying to serve. Bill reduction, backup for selected loads, energy autonomy, and remote-site electrification each lead to a different architecture, and that architecture is named and justified explicitly in the proposal — not buried inside a price quote.

For hybrid projects, battery sizing is tied to defined backup circuits and an autonomy target the owner has explicitly accepted. For off-grid projects, the design discipline, generator integration, and consumption assumptions are documented up front, because off-grid systems fail when these are left implicit. For on-grid projects, the proposal explains why hybrid was not added, rather than treating the absence of a battery as a missing feature.

For sites with operational complexity — hotels, riads, businesses, agricultural installations, multi-building properties — a technical audit before architecture is finalised often produces a better outcome. The audit creates the technical baseline that solar sizing depends on, and it sometimes surfaces efficiency opportunities that change the right architecture entirely.

Once the system is installed, ReneWcare Max provides the structured monitoring, preventive maintenance, recurring fault tracking, and warranty coordination that keep the architecture performing as designed over its full operating life.