Uvoz

Company: Uvoz — a cybersecurity-focused temporary file-sharing platform with smarter access control, AI insights, and malware protection.

What Changed: The project description indicates this is a self-contained, single-developer hackathon submission that builds on the author’s prior experience with file sharing, identity verification, and AI integration. It represents an early-stage prototype focused on improving the security and control of temporary file transfers.

Single Most Important Open Question: Is there evidence of traction, revenue, or customer adoption beyond the author's own development efforts?

The description states that Uvoz is a temporary file-sharing platform. It allows users to upload files for a limited time using either public or private links.

• Users can upload without creating an account but must verify their email via OTP before initiating a transfer.
• For private transfers, the sender can add approved email addresses and manage access requests (grant, deny, revoke, restore).
• The platform supports AI-based risk summaries, AI-driven sharing-setting suggestions, and optional malware scanning on download.
• Files are stored using signed URLs to offload transfer traffic from the backend.
• Backend is built with FastAPI, authentication handled by Clerk, data stored in Supabase PostgreSQL, and files stored in Supabase Storage.

Note: This is a self-reported description. No independent verification of functionality or performance exists.

The author positions Uvoz as a solution to the problem of insecure and uncontrolled file sharing — specifically, where sending files is easy but controlling access afterward is not.

Key claims:

• Keeps the convenience of temporary sharing while giving senders more control.
• Offers smarter access control, AI insights, and malware protection.
• Supports both public and private transfers with fine-grained permissions.
• Integrates AI for risk assessment and policy suggestions.

Inference: The positioning suggests a move toward secure, user-controlled file sharing in contrast to traditional platforms like Google Drive or Dropbox, which lack granular access control for temporary use cases.

The description does not define a specific customer segment or ideal customer profile (ICP). However, based on the features described:

• The platform targets individuals who need secure, temporary file sharing.
• It is designed for users who want to limit access, track permissions, and assess risks before sharing sensitive files.

Inference: Likely use cases include professionals or developers who share code snippets, documents, or binaries with collaborators, but do not want long-term exposure or lack of control over those files.

There is no evidence in the description of a business model or pricing structure. The project appears to be a single-developer hackathon submission, and no mention of monetization, subscriptions, or paid tiers is present.

Note: No revenue, pricing, or monetization strategy is described.

The author built Uvoz using:

• Frontend: Nuxt.js, Tailwind CSS, Nuxt UI
• Backend: FastAPI
• Authentication: Clerk
• Storage: Supabase (PostgreSQL + Storage)
• AI tools: Codex, GPT-5.6
• Malware scanning: ClamAV
• Deployment: Docker, Vercel

Key technical features:

• No-login upload workflow with OTP verification.
• Signed URLs for efficient file transfer.
• ACL-based access control for private links.
• Background tasks handled via Celery.
• AI integration for risk summaries and policy suggestions.

Inference: The stack suggests a modern, scalable architecture suitable for future expansion. However, no production-grade deployment or infrastructure details are provided.

There is no evidence of traction, customers, or adoption beyond the author’s own development efforts.

• The project was submitted to a hackathon.
• No mention of users, downloads, or usage metrics.
• No funding rounds, headcount, or partnerships are referenced.

Note: This is an early-stage prototype with no verified user base or commercial activity.

The description does not reference competitors. However, based on the features described (temporary sharing, access control, AI insights, malware scanning), Uvoz could be positioned in a space that includes:

• Traditional file-sharing services (e.g., Google Drive, Dropbox)
• Secure file transfer platforms (e.g., WeTransfer, SendGB)
• Developer-focused tools for secure code sharing

Inference: Uvoz may differentiate itself through AI-driven insights and granular access control, but no competitive analysis or market positioning is evident.

• Single developer team — limits scalability and support.
• No verified users or traction — raises questions about real-world demand.
• Self-reported features — no independent validation of AI, malware detection, or access control.
• Hackathon origin — implies a prototype rather than a mature product.
• Unproven monetization strategy — no evidence of how the platform will generate revenue.

Inference: The project is in an exploratory phase and lacks commercial viability indicators.

1. What specific use cases or customer problems are you solving?
2. Have you validated demand for this product with real users?
3. How do you plan to scale beyond a single developer?
4. Are there any existing competitors, and how does Uvoz differentiate from them?
5. What is your roadmap for monetization?
6. How do you ensure the accuracy of AI-generated risk summaries and access suggestions?
7. Have you tested malware detection in real-world scenarios?