PUBLIC BETASwyft Filings is connected for provider evaluation; website order submission remains disabled pending API partnership and sandbox approval.Integration status
MABNEEBUILD ON SOLID GROUND.Start My Business →
PRODUCT STATUS

The operating foundation is connected. Consequential actions stay gated until their rails are authorized.

Mabnee now connects the customer account, business context, Business Passport, roadmap, application preparation, jurisdiction discovery, compliance mapping, and operating-status surfaces. Third-party or government-controlled actions are exposed as readiness states instead of being presented as live before authorization.

Live production foundation

  • Production public site on mabnee.com
  • Four-step guided business onboarding
  • Mabnee accounts with Neon Auth and authenticated Data API access
  • Cross-device onboarding draft synchronization for signed-in users
  • One protected business context reused across Mabnee workflows
  • Cloud-connected non-sensitive Business Passport profile and document checklist
  • Personalized roadmap with RLS-backed progress synchronization
  • Formation and EIN preparation work queues created from completed onboarding
  • Authenticated licenses and permits discovery across all 50 states and Washington, DC
  • State-aware compliance obligation mapping with official-source verification guardrails
  • 51-jurisdiction provider architecture with 663 governed capability and official-handoff paths
  • Operations Center for application, filing, compliance, vendor, payment, invoice, and provider-job status
  • Customer-readable/server-controlled payment, invoice, provider, and filing state boundaries
  • Google Workspace email routing plus Google SPF/DKIM authentication for mabnee.com
  • Verified Resend sending-domain DNS and deployed transactional email/contact architecture
  • Private-route noindex/no-store behavior and baseline browser security headers

Integrated but externally gated

  • Swyft Filings production order submission until partner approval, credentials, webhook verification, and submission enablement are present
  • Live Stripe Checkout until server credentials, webhook verification, authoritative pricing, and explicit checkout enablement are present
  • Government-fee collection until the current authoritative fee is loaded and separated from Mabnee and third-party charges
  • Direct IRS, government, or licensing submission except through a confirmed official or authorized provider channel
  • Secure document upload until an approved object-storage, malware-scanning, access-control, retention, and deletion stack is activated
  • Transactional email delivery until the Resend production API key and signed delivery webhook are active in the deployment runtime
  • Identity verification or high-risk identifier storage until the dedicated secure-data/provider controls are activated
  • Registered-agent fulfillment until an eligible provider and jurisdiction-specific service agreement are active
  • Legal, tax, accounting, or regulated-profession advice unless delivered through a separately engaged qualified professional

Activation standard

A consequential capability moves from “gated” to “live” only after the applicable provider contract, credentials, security review, privacy treatment, user authorization, fee disclosure, error handling, audit record, source verification, and legal/compliance review are complete.

A connected database, API route, provider adapter, marketing description, roadmap card, or interface control does not by itself mean Mabnee transmitted a filing, collected a fee, verified an identity, stored a sensitive document, or obtained an agency approval.