Network admission · Cloud control plane

Network admission that stays out of the way

NetAdmit decides who gets on the network — and keeps that decision durable when controllers, portals, and operators disagree. Brand-agnostic captive-portal SaaS (Omada first).

Static site · no tracking pixels on this page · contact by email

Built for real guest networks

Captive portals fail in boring ways: controller-only deauth, sticky sessions, dual orchestration paths, and vendor lock-in. NetAdmit separates duties so proof, grant, and enforcement do not collapse into one brittle script.

Brand-agnostic by design

Guest UX and commercial grants stay stable while NAS adapters change. Omada ships first; MikroTik and others are on the roadmap shape, not bolted hacks.

Durable admission

Authorize/deauth is job-backed. Cloud intent and commercial grants survive controller quirks so guests can re-enter without inventing a second product path.

Small production footprint

Static portal + one edge API + managed Postgres + Cron reclaim. No required queue consumer for V1 happy-path admit.

How NetAdmit thinks about admission

One sentence operators can trust: identity proves, entitlement decides, network enforces, billing charges, audit remembers.

That separation of duties is the product. Portals and webhooks share one composer. The NAS never runs without a durable job row.

  • Identity Shared password, click-through, WhatsApp reverse-link, and more — proof only, never the grant engine.
  • Entitlement Free windows, vouchers, and later subscriptions decide whether the guest deserves access.
  • Network Sessions, devices, and authorize jobs talk to the controller through a NAS adapter.
  • Operators Dashboard JWT auth, kick, failed-job replay — built for support, not only happy-path demos.

Frequently asked questions

Direct answers for humans and machines. Same text is published as FAQ structured data.

What is NetAdmit?

NetAdmit is brand-agnostic captive-portal software for guest Wi‑Fi. Guests authenticate through a cloud portal; the control plane grants access through a NAS adapter. Omada is the first supported controller family. (Formerly marketed as Captixa.)

Who is NetAdmit for?

Businesses that offer guest Wi‑Fi (cafés, coworking, hospitality, clinics) and small ISPs that need voucher-style or identity-gated admission without locking into a single vendor portal.

Which network gear does NetAdmit support?

Omada is first. The architecture is brand-agnostic: a job-based authorize/deauth path with pluggable NAS adapters so additional controller brands can be added without rewriting the guest or billing spine.

How does guest admission work at a high level?

The captive portal creates a session, identity proves who the guest is (or click-through), entitlement decides the grant, and the network module instructs the NAS. Durable state lives in Postgres; the API runs as a single edge Worker with a Cron backstop.

Is NetAdmit open source?

Product repositories under the netadmit GitHub organization are currently private while the pilot hardens. Public status and licensing will be announced when they change — do not assume MIT or public source today.

What happened to Captixa?

Captixa was the earlier product name. The same captive-portal control plane is now NetAdmit — one name for company and product.

How do I get access or talk to the team?

Email hello@netadmit.com with your venue or ISP use case. There is no public self-serve signup on this marketing site yet.

Running guest Wi‑Fi that needs a real control plane?

Tell us about your controller, site count, and identity needs. We reply from hello@netadmit.com.

Email NetAdmit