BamalX documentation

BamalX is the central control plane for your network products. You onboard once, request deployments (cloud-managed or on-premises), enable the products you need on each deployment, and manage billing, health and support from a single console. The product software itself runs on your deployments — BamalX keeps them provisioned, in sync and observable.

Everything below follows the real lifecycle: create your workspace → verify your domain → request a deployment → enable services → set up product access → operate.

Getting started

1. 1
   Create your workspace

   Click Get started and register with your company details. This creates your organization and your first user account — no credit card required.
2. 2
   Sign in

   Use your email or username. If you lose access, the sign-in screen has one-time-code recovery for both password and username.
3. 3
   Take the dashboard tour

   The Overview screen shows your onboarding checklist, deployments, open tickets and outstanding balance at a glance.

Verify your domain

Domain verification proves your organization owns its domain and unlocks the smoothest provisioning path. It is strongly recommended before requesting a deployment — and it is required before cloud services can be enabled.

1. 1
   Set your domain

   Open Settings (gear icon) and enter your domain. BamalX issues a verification token.
2. 2
   Add the DNS record

   Create a DNS TXT record at the domain apex with the value yansutra-verify=<token>.
3. 3
   Verify

   Back in Settings, click Verify. DNS changes can take a few minutes to propagate — retry if the first check fails.

Deployments

A deployment is where your product software runs. You don't create deployments directly — you request one, our team reviews it with you, and approval provisions it.

Cloud vs on-premises

Cloud deployments are provisioned and managed on BamalX infrastructure (one per organization). On-premises deployments run anywhere you like — your data centre, your cloud account — and you can have as many as you need.

Requesting one

1. 1
   Open Deployments → Request deployment

   Pick the type, a preferred region, the products you expect to run, and add any notes on scale or timeline.
2. 2
   Review

   Our team reviews the request and may contact you to finalise sizing. You can track (or cancel) the request from the Deployments screen.
3. 3
   Provisioning

   Approval creates the deployment with your selected services enabled. On-premises deployments receive sync credentials that are installed into your cluster during setup.

Deployment status

Pending — created, no heartbeat yet · Active — live and reporting · Down — heartbeats stopped · Suspended — paused by an administrator.

Services & limits

Each product is enabled per deployment as a service— from the Products screen or a deployment's detail page. Enabling a service makes the deployment provision it automatically on its next sync (about two minutes); disabling stops it for that deployment.

Every service carries constraints — the limits your plan is sized to (devices, subscribers, access points, sites, endpoints, storage). Constraints are set with our team and pushed to your deployment automatically; the deployment enforces them locally. Your service window (start/end dates) works the same way.

Product access

Each product app has its own admin console with its own password — BamalX never sees it. Access is bootstrapped with a single-use setup token:

1. 1
   Mint a token

   On the deployment's detail page, open the service and click Set up access. The token is shown once and expires quickly.
2. 2
   Open the product’s setup page

   For cloud services the dashboard can open the product's /setup page directly with the code pre-filled; otherwise enter the token on the product's /setup page yourself.
3. 3
   Set the admin password

   The token is consumed, the password is set locally in the product, and you sign in to the product console. Mint a new token any time — issuing one invalidates the previous pending token.

Product guides

Coming soon: Software BNG (disaggregated broadband network gateway) and DNS Management (recursive DNS with filtering and analytics).

Health & monitoring

Deployments report heartbeats and per-service telemetry to BamalX continuously. A deployment's detail page shows its live status, last heartbeat, per-service stats (subscribers, sessions, devices, captures — whatever the product reports) and your configured limits next to actual usage.

For platform operators, the same page adds cluster-level health — node CPU/memory/disk, workload status, storage volumes and 24-hour load trends — plus safe remote operations (restart, scale, logs) that are queued and executed by the deployment itself.

Billing

Billing is constraint-based and per-deployment: your price follows the limits each deployment is sized to and the services you actually enable — there are no seat licenses or flat per-product rates. Invoices are issued per deployment, always in ₹ INR, and the Billing screen shows every invoice with its line items and payments. Questions about sizing or pricing? Use the Talk to us link on the pricing page.

Support tickets

Raise a ticket from the Tickets screen for any issue or request — optionally linked to a product and a deployment so it lands with context. Tickets move through a clear lifecycle (open → assigned → in progress → pending → resolved → closed), you can comment at every step, and priorities carry response targets. Closing is final; a resolved ticket can be reopened if the problem returns.

Something this page doesn't answer? Open a ticket — or mail us from the pricing page.