Onboard the clouds you have
On the infrastructure you have
Nexus connects to your existing data-centre regions through a guided onboarding kit, without changing what already runs there.
Sovereign cloud. Your data, your regions, your rules.
Nexus is the platform behind NubeStack Cloud: a public cloud that runs in-country, on infrastructure we operate in Pakistan. Customers get one account, one console and one API across every region. Each region is independent, so if one has trouble, the others keep serving.
Run by us as NubeStack Cloud. Licensed to providers who want to run their own.
Running servers in one data centre is the easy part. A public cloud needs everything around it: organizations and the people in them, projects with their own quota, roles people understand, an audit trail, prices in rupees and a console that does not assume you are an administrator. Nexus is all of that, over regions that each stand on their own. Every project lives in the region you choose for it, and its data stays there.
Inside Nexus
The console our customers use
Captured from a demonstration organization on our two regions. Every name and figure is sample data.
A project at a glance
A project lives in one region. Its overview counts instances by state, networks, volumes, public IPs and load balancers, lists the latest operations with their progress, and shows quota against what the project was given.
One menu, and a scope you choose
The menu never changes. The selector in the top bar picks what it shows: the organization, or one project, listed under the region it lives in. In a project its services are yours to change; in the organization they are read across every project.
Instances, the way a cloud should list them
Name and image first, then state, address, size and age. Actions sit in one menu per row, every change runs as an operation you can follow, and the list says when the region was last read.
The price before you create
Every create page is one page of numbered sections. The summary beside it shows the cost per hour or per month at the published rates, in PKR, and what the new resource takes from the project’s quota.
Volumes, snapshots and schedules
Volumes with their size, type and what they are attached to, with snapshots, images and backup schedules alongside. Attach, extend, snapshot or change type from one menu per row.
Private by default, Internet when you ask
Each project gets a private router. Its networks route to each other, and an Internet gateway adds the outside leg only when you want it. The topology shows it all.
Empty pages that explain
A list with nothing in it yet shows a drawing of the service, three facts about it, how it is billed among them, and a link to the guide.
One organization, every region
Projects and the region each one lives in, people, quota against the budget, this month’s usage, and anything waiting on someone. The organization view is the organization admin’s console.
People, roles and service accounts
Each person’s organization role and the projects they can reach, with the role they hold on each. Built-in and custom roles, and nobody can give a permission they do not hold.
Cost explorer and statements
The month’s cost day by day, by project, service or region, against last month and with a projection. Each month closes into a statement in PKR whose every line traces back to the usage behind it.
The operator console: customers
The provider’s own console, separate from the customer’s: every organization with its tier, state and projects, and the budgets, limits and locations each one may use.
The operator console: prices
The rate card in PKR: a price per instance-hour for each catalog size, per GiB-hour for each volume type, and for public IPs, gateways and load balancers. A change is a new version from a date you choose.
What customers get
A complete public cloud console
Organizations and projects
One account for your company, approved by us. Invite your team and organize work into projects; each project lives in one region, and a team that runs in both keeps a project in each.
Compute
Instances from a catalogue of sizes and images, SSH keys, start-up scripts kept sealed, server groups to keep machines apart, browser consoles, and instance groups that keep a number of them running.
Launch templates
Save an instance’s whole setup as a versioned template, launch up to ten at once, and add them to a load balancer as they start.
Storage
Volumes in the types each region offers, snapshots, images from instances, backup schedules with their own retention, extend and transfer.
Networking
Private routing by default, an Internet gateway on request, public IPs, security groups with readable rules, and load balancers with listeners, pools, health checks and HTTPS certificates.
Access control
Organization and project roles, custom roles bounded by what their maker holds, a second factor for owners and admins, and service accounts with API keys for automation.
Native tools still work
Use the command line and Terraform with the same account, or each region’s own dashboard. Nexus never fights the tools you already use.
Audit and activity
Every change is an operation you can follow step by step, and every accepted change, refusal and sign-in is in the organization’s audit log.
Usage and statements
A price estimate on every create page, hourly usage per project and region, a cost explorer, and a monthly statement in PKR whose every line traces back to the usage behind it.
How it is built
One cloud for the customer, independent regions underneath
Most multi-region clouds share more than they admit. Nexus keeps each region separate on purpose, and does the joining-up in the layer above.
Joining regions the usual way
- One shared sign-in system that every region depends on
- A console that fails when one region is slow
- Accounts, roles and quotas per region, kept in step by hand
- Each region’s own dashboard as the only view of what exists
How Nexus does it
- Each region stands on its own, and one sign-in reaches all of them
- Pages read from a stored inventory, so a region in trouble shows as stale, not missing
- One organization, one set of roles and one quota policy across every region
- One console and one API, with each region’s own tools still there
For cloud providers
Building a public cloud of your own?
Nexus is the platform we built to run ours. We license it, with our team, to data centre operators and telecoms who want a sovereign public cloud on their own infrastructure.
An operator console
Run the business, not just the hardware
Approve organizations, set budgets and limits, watch capacity and region health, schedule maintenance, publish prices and support customers with time-limited, audited access.
Installed and supported by us
Backups and upgrades included
We install the platform in your data centre and stay on as the team behind it, with nightly backups, tested restores and planned upgrades.
Common questions
Worth asking early
No. Nexus is a commercial NubeStack product. We run it ourselves as NubeStack Cloud, and we license it, with installation and support, to providers who want to run their own public cloud.
NubeStack Cloud runs in pak-khi-1 (Karachi) and pak-isb-1 (Islamabad). Each is an independent cloud with its own power, network and storage. Each project lives in the one region you choose when you create it, and its data stays there. A team that wants both, for example for disaster recovery, keeps a project in each.
Yes. Your projects work with standard cloud tooling: the command line, Terraform and each region’s own dashboard, signed in with your Nexus account, or a service account for automation. Nexus shows what those tools create and marks it as made outside the console.
The other region keeps working, and so does the console. Pages read from a stored inventory, so a region in trouble shows its resources as stale rather than making a page fail. Your workloads in that region are as available as that region is: Nexus does not move machines between regions for you.
By organization and project roles in Nexus, including custom roles you define. In each region a person only ever gets the access their role allows, never administrator rights, and removing someone takes their access away in every region.
By the hour, per resource, from Nexus’s own usage records, priced by the published rate card. Each month closes into a statement in PKR whose lines trace back to the usage behind them, and a correction after close appears as an adjustment rather than a change to a closed month. Figures are marked provisional until our measurement has been checked against the clouds themselves.
Your data-centre regions and a place to run the platform. We install Nexus with you, connect your regions and stay on as the team behind it. Book a call and we will walk through your estate.
See the console, then tell us what you need
Take the tour to see the console as our customers use it. Then talk to us about an account on NubeStack Cloud, or about running Nexus for your own public cloud.
