Solar Protocol

A naturally intelligent network.

This website is hosted across a network of solar powered servers and is sent to you from whichever server is in the most sunshine.

Presently you are on a server called Solar-Power for Hackers that is located in Kiambu Road, Nairobi, Kenya.

Server Battery:
City: Nairobi
Country: Kenya
Local time: 08:04 AM
Weather: n/a
Temp: n/a ° C
Feels like: n/a ° C
Sunrise: n/a
Sunset: n/a
Last update: 08:04 AM in TZ n/a
Battery Level: 77.0%
Battery Voltage: 13.2 volts
PV Power: 6.46 watts
PV Voltage: 14.63 volts
PV Current: 0.44 amps
Load Power: 1.58 watts
Load Voltage: 13.2 volts
Load Current: 0.12 amps

GUIDE: Developing Projects and Hosting Sites

What kind of projects can run on Solar Protocol?

Solar Protocol can provide solar powered, community-owned server space for web projects and it gives open access to the solar energy data from all the server’s in the network via the system’s open API.

This guide describes some different types of projects that could be developed with Solar Protocol, categorizing them as: external (projects using Solar Protocol open API data but are hosted elsewhere), single server (projects are hosted on a single Solar Protocol server and that may also experiment with that server’s local energy data), or network (projects that are hosted on the Solar Protocol software platform, and get served with it from whereever there is sun in the network).

Projects that utilize and experiment with Solar Protocol energy data from the API could be created and hosted anywhere on the web. The API is open so these types of projects do not need to be hosted directly on a Solar Protocol server and do not require any support from the Solar Protocol team. For this reason we call these types of projects ‘External Projects’. Projects that are to be hosted on the Solar Protocol platform and servers, i.e. single server or network projects, require various levels of collaboration and support from the Solar Protocol team. Opportunities for single server and network projects are typically available based on specific calls for work or collaboration that we put out periodically.

External projects are the simplest to produce, single server projects are a little more complicated, and network projects can potentially get very complex.

Types of Projects

External Projects

External projects are purely client side projects that use the publicly available open API (insert link to API tutorial) to get data from Solar Protocol and do something with it. Because these projects can be hosted anywhere and because our API is open, you do not need to coordinate with or get permission from us (though we’d love to learn about them). Client side projects could, however, also be hosted on a single solar server or on the Solar Protocol software platform (see below).

To develop an external project, check out the API tutorial.

Single Server Projects – Projects Hosted on One Server

A single server project is a project that runs on a specific Solar Protocol server. In addition to the open API, these projects make use of something specific to the server they are running on. There are a number of technical and conceptual reasons a project might need to run on a specific Solar Protocol server. For example, it might require additional types of data that aren’t available on the public API or it might be engaging with the specific place, geographic location, materiality, or intermittency of the server itself.

One example of a single server project is the Low Carbon Methods website. Low Carbon Methods is a lab at Trent University and so it was important that the site is hosted at that location, the website is also an exploration of intermittency and uses energy-centered design principles to communicate energetic aspects of the server.

The path of the sun over New York City in August.

Network Projects – Projects Hosted Across the Network

Projects can also be hosted on the Solar Protocol software platform, that is distributed across all the servers in the network. The location where the project is hosted will change throughout the day and season. Like the Solar Protocol website, the project will therefore be served from whereever there is the most sunshine in the network at the time. This option is best for projects that need to be reliabily available with minimum downtime, or that seek to explore the Solar Protocol network behaviors (the way the site is served from different places at different times of the day or season). These works may still use data from the API, for example, querying how much power is being generated or used at a particular moment, at a particualar server.

Image of solar data from each server

Solar data and change of active server over a 72 hour period.

Project Considerations

Consider daily and seasonal changes across the network

Image of solar daily change of longitude

Servers across different longitudes will have light at different times of the day.

Image of solar data from each server

Servers across different latitudes will have different light levels and energy resources in different seasons.

Back to guides