Account home
The Hub becomes the user-facing home for sign-in, account state, workspace routing, profile controls, and eventually organization access.
accounts.acetechdigi.com
One secure entry point for every AceTech application.
AceTech Hub is the account home, app launcher, and future workspace center for AceTech Digital. Sign in once, access approved tools, review your workspace, and move between products managed by BeastModeConnect.
- Identity
- Clerk-ready account home
- Access
- BMC-managed app routing
- Architecture
- Build once, reuse everywhere
Application launcher
Each app card explains what the product does, who it is for, and whether the current visitor can open, request access, or join a future waitlist.
Commercial control layer
BeastModeConnect remains the source of truth for product access, subscriptions, workspace state, and cross-app entitlement decisions.
AceTech applications
A clear doorway into every product.
These cards are intentionally plain-language: users should understand the value of each app before they authenticate.
Public beta candidate
FileToolKit
Fast file conversion for everyday documents and images, designed around privacy, clarity, and practical limits before paid plans launch.
- Convert supported files without workflow clutter
- Privacy-first messaging and transparent file handling
- Future BMC-managed access for Pro and Business tiers
Platform foundation
BeastModeConnect
The commercial and operational backbone for AceTech apps: product access, customer state, subscriptions, usage, and platform coordination.
- Central app and entitlement management
- Commercial state definitions before billing work
- Future admin workflows for supported AceTech products
Future suite
AceTech AI Tools
A growing family of practical AI-assisted tools for documents, writing, automation, and business workflows.
- Document and writing assistance
- Reusable platform patterns across products
- Access managed through the Hub as apps mature
Developer layer
AceTech Platform SDK
Shared product infrastructure for future AceTech applications, including consistent auth, entitlement, analytics, and deployment conventions.
- Reusable engineering standards
- Consistent product and billing language
- Designed to reduce one-off SaaS rebuilds
Ecosystem architecture
The Hub should be thin, trustworthy, and reusable.
This page should not become a second billing system or a hard-coded list of special cases. Its job is to authenticate users, explain the ecosystem, and route people based on BMC-managed product state.
Clerk
Authentication, profile, sessions, and organization-ready identity.
BeastModeConnect
Commercial source of truth for products, access, usage, and entitlements.
AceTech Apps
FileToolKit and future apps consume shared identity and BMC decisions.
Trust posture
Built for confidence before complexity.
No fake ownership language
Use “account,” “workspace,” “subscription,” “access,” and “plan” instead of implying software ownership.
Clear access states
Users should see whether an app is available, in beta, planned, or restricted before they click.
Privacy-forward entry
Keep public copy concise, avoid unnecessary trackers, and explain the purpose of authentication plainly.
Recommended rollout
Ship the Hub in controlled layers.
-
1
Static public landing page
Launch a polished explanation and app directory with Clerk routes reserved but not wired in static mode.
-
2
Clerk account shell
Add sign-in, sign-up, profile, session handling, and protected account pages after auth requirements are approved.
-
3
BMC app-state integration
Replace static cards with BMC-driven app availability, entitlement states, and workspace routing.
-
4
Billing and subscription visibility
Surface plan status only after Stripe/BMC contracts and commercial state definitions are frozen.