Product Documentation

Platform overview

Uzanova combines secure authentication, workspace level data management, configurable analysis engines, historical validation tooling, role based administration, and collaboration features in one operational surface so teams can move from raw files to reviewed outcomes without switching between fragmented tools that create avoidable risk and process drift.

The platform is structured around four practical layers which include identity and access, data ingestion and governance, analysis execution and review, and community communication with moderation controls, which allows organizations to set a stable internal process and still scale usage across new users and additional projects.

Onboarding and setup

A clean onboarding sequence keeps account security and workspace consistency aligned from the first session, so the recommended approach is to create an account, confirm profile details, configure privacy preferences, and set security options such as password rotation cadence and session hygiene before the first dataset is uploaded.

1. Open an account through the signup flow and confirm your preferred login method with either local credentials or Google OAuth.
2. Visit account settings to complete profile fields and choose the visibility level that matches your collaboration model.
3. Review notification controls so operational updates and security alerts reach the right recipients without unnecessary noise.
4. Run a first sign in check from a second browser or device to verify that session management behavior aligns with your internal access policy.

Workspace and data lifecycle

Data workflows are designed for traceability and operational safety through type validation, ownership checks, visibility controls, and malware scanning, which means each file enters the platform with verifiable metadata and can be audited later without relying on informal naming conventions or untracked local copies.

Teams can keep datasets private when the work is still in draft state, expose selected assets to shared lists when collaboration is needed, and import approved shared datasets into personal workspaces so every user can continue with a consistent source while retaining independent execution history.

Analysis and validation workflow

Uzanova supports a repeatable workflow where teams define parameters, run analysis jobs, compare outcomes, and then execute historical validation windows before publishing results, which helps maintain discipline in decision making and reduces inconsistencies that often appear when parameters are changed without formal review.

Parameter defaults can be stored per algorithm at the account level so repeated runs remain consistent across sessions, and the dashboard surfaces recent activity with status visibility so operators can identify queued, completed, and failed jobs quickly during active cycles.

Collaboration and community

Community features include public and private forums, invitation based membership controls, thread level posting tools, and direct or group chat threads, which together provide a practical space for operational discussion and review without forcing teams to rely on external channels that are disconnected from workspace context.

Moderation and upload safeguards are applied to media surfaces, and notification events are emitted for relevant account activity so users can track key updates such as invitations, request changes, and thread responses while preserving a clear activity trail.

Security controls

Core controls include JWT based authentication with refresh token rotation, bcrypt password hashing, route scoped rate limits, strict security headers including CSP and content type protections, upload validation and scanning, and ownership enforcement across private resources, all of which are built to reduce common web application attack paths while keeping normal operations straightforward for teams.

Independent penetration testing with Strix is integrated into the project workflow and is used as a recurring verification layer for new releases, which means security findings are tracked, remediations are implemented with regression tests, and controls are continuously reviewed as the platform evolves.

Plans and billing

Subscription management is available through tiered plans with Stripe backed billing, and each tier can define limits for storage, monthly workload volume, and access to advanced capabilities, which allows organizations to align spend with operational scope while preserving a clear upgrade path as demand grows.

Administrators can review subscription status, manage user level entitlement data, and monitor usage patterns from the admin surface so billing actions are based on current platform activity instead of manual estimation.

Support and operations

For routine operational issues, teams should document the affected area, relevant account, and approximate timestamp, then share that context with administrators so incident triage can begin quickly using audit data and execution records that already exist in the platform.

For policy, privacy, or contractual questions, review the Privacy and Terms pages linked in the site footer and top navigation, then escalate unresolved items through your internal owner so legal and compliance approvals remain synchronized with production usage.