What is the Nidulus Platform


"Easy to setup, with no setup"

Nidulus is a software platform specifically designed to eliminate the need for expensive system architects and DevOps teams, while also lowering the size of developer teams required when building easy or complex IT solutions.

Setting up, configuring, and maintaining a complete software infrastructure for any project, is as easy as starting up one application.

Nidulus helps software developer teams roll out and update features on a daily basis rather than annually.


"Runs everywhere"

Being highly optimized, Nidulus is deployable to any Linux cloud, barebone Linux server, or embedded Linux device.

Remotely deploy and manage features developed with support for the plentitude of js packages from the npm repositories.

Your work will get much easier, starting today. It's almost like magic!

edit

Easy to setup, with no setup

When the Nidulus server is started the first time it does its own setup automagically. No tedious configuration required from you.

import_export

Communicates securely without configuration

Every Nidulus process deployed (API and feature) will find each other across your network, without additional configuration from you (apart from your firewalls). The communication is always encrypted.

access_time

Time to Market

Each feature is hot-deployable to Nidulus. You do not need to schedule a massive restart/downtime window to deploy new functionality to your customers. That is so 1990's, this isn't Java Spring Boot. The features are self-contained processes and do not interfere with other processes when you write mistakes in the code.

attach_money

Overall cost

Extremely lightweight and extremely asynchronous with a small hardware footprint, even if advanced. You can process 1,1 billion requests/day on your home PC if you lack server hardware (hardware is overrated anyways when the code is great), and you will always know what the platform cost you due to the fixed-price license we agree upon.

Download the Platform

Join us at our Slack channel , tell us your story, your thoughts, your hickups on the road, let us find a way together to create magic!
Nidulus Platform 2.0.1 (64-bit)
Tested on CentOS 6 + 7, Fedora 28, openSUSE
Leap 15.0 and Ubuntu Server 16.04 + 18.04

Firewall configuration

$0

  • 1 Api / 3 Features
  • Unlimited Time
Download
Nidulus Web Client 2.0.0 (64-bit)

$0

Nidulus DevTools 2.0.0 (64-bit)

Development package



Enterprise License

Per agreement

  • Agreed Apis
  • Agreed Features
  • 1 Year
Let's talk



Non-Profit Opensource Projects

We support you

  • Unlimited Apis
  • Unlimited Features
  • Unlimited Time
Tell us about you



Nidulus ARM 2.0.1 (64-bit)

Contact us


With so many variants of ARM systems, we decided not to provide a generic ARMv6 and ARMv7 version. We rather build and test it ON your hardware, on the Linux distribution you will be running. It must support Nodejs 8.

Let's talk

The "oh, so advanced" guide to get started mass producing APIs with Nidulus


Welcome, we assume you just downloaded your Nidulus server for the first time and panic over not knowing what to do now. Take a deep breath and let us get to work.


Unpack your download


unzip nidulus_x_x_x.zip (where x_x_x is the version of your download). 

Start nidulus


cd nidulus; ./nidulus 

Web interface


The web client you downloaded will have its web interface running on port 7999. Point your browser to http://<your Nidulus client ip>:7999/ to get to the login page. Login with admin/password123


Initial configuration


After logging on, you will be directed to the server page. There are no servers pre-populated, so you will have to add one. Click the "Add Server" button and enter the IP/URL of the machine where you started the nidulus server on. No port must be added, just IP/URL.

The certificate that is asked for will have been created when you started up your Nidulus server, in the home folder of the user you started it with: ~/client.crt

Once done, you will have finished setting up graphical monitoring/management of your server in your web client.



When configuring the localhost instance (through the cogwheel menu on the server card), you will have two options:

Adding/setting your activation key
Changing security key


Activation key is your license key (if you purchased/were given one).

The security key, which must be 16 characters long, is randomized for every new machine you start a Nidulus server on but can be changed into any 16 character sequence. If you wish to communicate between two Nidulus machines (service network scaling), you need to update the security key to be same on both machines to avoid getting an unauthorized reply. No other configuration is needed as every API and service automatically find each other on the network.


If you accidentally "delete" a server in the web client, nothing will happen to the server. You will just stop monitoring it from the web client and can add it back later on. Everything you deployed on it will continue to run, it just won't show up in your web client.


What do I do now?


Now you can go to the "Process List" on your newly added server and add new APIs, deploy features (the devtools package you downloaded) and schedule timed triggers of your features, as needed.

It really isn't harder than this to build advanced APIs, and shouldn't be.

We added an in-app help-center with explanations of each part if you wonder about something while in the app. You can find it in the upper-right corner of the web app, in the cogwheel menu. You can also change the password for the admin account from there.