Your EMS decides. Backloop makes it happen on site.

Two controllers per site, one on standby. Drivers as config files. One API for every site. Built for companies that operate batteries, solar, EV chargers and generators on many industrial sites.

Book a 30-minute call Apply for early access

The site layer for your EMS.

Your EMS makes the decisions. Backloop handles everything between it and the devices: the controllers in the cabinet, the device drivers and one API that is the same on every site.

You set up and manage your sites with Backloop. Your control programs run on the site controller or in containers we host in Europe.

You push a container to our registry and deploy it to the site or the cloud. We run the infrastructure, so your team only writes the control logic.

Your EMSoptimization and schedulesBackloop APIthe same on every siteTwo Backloop controllersin the cabinet · safety layerDevicesbatteries · solar · EV chargers · generators · metersBackloop

Drivers for the devices you use.

Backloop is made to connect batteries, solar inverters, EV chargers, generators and meters. We build the drivers together with our pilot customers, for the devices they use.

Tell us your devices. We build the drivers for your pilot.

Grid connection Transformer MeterWh Battery Solar EV chargerEV Building

New devices are added with a config file, not new code.

A driver is a config file. We write the configs for your devices. If you have something special, you can write your own config, without code.

The new device then shows up in the API like every other device.

Driver configa file, no codeNew devicein the API like any other

Every command is checked before it reaches a device.

A safety layer on the controller checks every command against the site’s limits. Commands from your EMS, from your programs and from your own config-file drivers all pass the same check.

A command outside the limits is blocked.

EMS · programor driverSafety layerDeviceCommandSafeOutside limits · blocked

Two controllers on every site.

One controller is active and one is on standby. If the active one stops working, the standby takes over automatically. For example when the active controller

  • loses its power supply
  • loses a cable connection
  • loses its modem or LTE link
  • has a hardware fault
Controller 1 · activeController 2 · standby

Sites keep running without internet.

Programs on the site controller keep running when the connection drops. The data is sent once the connection is back.

Your programEdge · on sitekeeps running offlineCloud · Europeall your sitessync when online

One console for every site.

The Console is the control room for Backloop. Everything you need to bring a site online and keep it running is in one place:

  • set up the site and its devices
  • configure the controllers and their network
  • send test dispatches while you commission a site
  • deploy your apps to the site or the cloud
  • get alerts when something needs attention
ConsoleSite setupControllersNetworkTest dispatchAppsAlerts

Pricing per site.

Hardware plus a fixed monthly fee per site. No revenue share. Early access terms available.

Niklas Timpe working at a laptop

Founded in Gothenburg by Niklas Timpe.

Niklas spent five years deploying microgrids and writing their control software in Germany, then built automated ADRC tuning for vehicle steering control at Einride.

Bachelor’s in mechanical engineering from RWTH Aachen. Master’s in systems, control and mechatronics from Chalmers.

LinkedIn

Tell us about your sites.

Book a 30-minute call Apply for early access

Or email hello@backloop.energy

Apply for early access

Opens your email app with your answers filled in.