Make Every Data
Stream, API & Network Programmable

Lolo Code is an Integration Function as a Service (iFaaS) platform that allows you to build cloud agnostic serverless applications and reusable functions in a Node.js environment with one-click multi-cloud deploy.

We are currently in private beta but apply for a sign up code above to receive access. Your first two apps are completely free.

Lolod (Coming Soon)

Lolod turns your laptop or embedded device running Linux into a Lolo runtime where you can run your application. So you can have Lolod running on your Raspberry Pi.

What makes Lolo unique?

Lolo was built in response to some of the shortcomings of certain serverless computing platforms, i.e. Lambda, Azure Functions. Lolo simplifies the user experience by being an event-driven serverless computing platform with real-time data streaming and monitoring with a baked in state store. The interface is flexible as it allows you to create and connect multiple functions in response to event triggers within the application. This will let you build complicated workflows that you can visualize. Along with being more visual, the Lolo Code creators have eradicated certain limitations that made building serverless applications a complicated affair, hoping that it would streamline the process, while keeping performance high. Although this list is not exhaustive, see our 6 key features below.

Fast Function Invocation.

Without network delays or cold starts.

Cloud Agnostic.

Not tied to a specific cloud vendor.

Visual Workflow.

Easier to understand and maintain.

Limitless Scalability.

Run production apps at cloud scale.

Build Things Faster.

State store / NPM Module Support.

One-click Deploy.

Run your apps with one-click deploy.

If you want to go into more detail read up on our documentation.

Lolo Code is a serverless event-driven platform so the idea is to have the code within the application be triggered by actions (i.e. events). Events can be triggered by timers, HTTP requests, a connecting WebSocket, streaming data and so on. Events will then run the functions you have them connected to. I.e. you specify the code you want to run when the event happens.

An example that is common is obviously an API that will use an HTTP trigger and then return a response of some kind that you program, usually working with a database. Webhooks are another ideal use case for serverless, when the specified activity occurs you can decide what you want to happen. Since webhook calls are event-driven, building a webhook management system with Serverless is a great choice.

If you're familiar with event-driven serverless computing platforms such as AWS Lambda, what you can do there you can do here a lot faster. Lolo pretty much provides you with the same tools as Lambda, Kensis, Cloud Watch, API Gateway, DynamoDB and Cloud Formation in one place. Nevertheless, you don't need any previous serverless experience to use this platform as it is quite intuitive. Check out our quick Hello World demo here but also check out our youtube channel for other demos by us and other users here to get some inspiration.

The platform requires you to have some knowledge of JavaScript as we only provide runtimes for Node.js. What's unique here though is that you don't need to be any kind of expert when it comes to serverless architecture. Lolo was built for beginners and advanced coders alike who want to build robust serverless applications that can run at cloud scale in a flexible and straightforward environment. Without having to worry about excessive costs.

There are several workflow systems out there today but not many are made for coders. These systems are usually quite expensive and don't come close to offering the kind of flexibility and robustness of serverless computing platforms. Lolo is trying to provide the same serverless experience but in a more visual and straightforward environment. Our dream is also to provide top notch documentation without making things unnecessarily complicated while listening to our community to build what they need to be effective.

To give you an idea of how Lolo works, try to create a WebSocket or a CRUD API with our 2 minute guides. These guides are using Library Functions as triggers, i.e. code we have already written by setting up a template to share with you. This is so you don't need to create your own HTTP trigger, Timer or WebSocket Trigger and so you can focus on creating something faster. However, you don't have to use Lolo's Library Functions, you can create your own Library Functions. If you are interested in creating your own event triggers, see our docs here on producing events and setting up your own http server. If something is missing write in our forum and if it doesn't exist we'll make sure to discuss it internally.

With serverless, the whole idea is to remove the need for a server to be running 24/7 waiting to recieve requests while trying to plan out the amount of calls to your application on a day by day basis. No point in paying for a server to sit idle.

Essentially it’s about effeciency. You can have someone else take care of server configuration, balancing and scaling. Although not necessary for smaller apps, when you need to you can outsource your server management, cut the need to for large DevOps teams and run applications for a fraction of the cost. If you want read more on serverless, we suggest reading Serverless is Eating the Stack and People are Freaking out — As They Should Be by Forrest Brazeal.