Tarlog

The description states that Tarlog is:

• A privacy-focused time tracking, compliance, and invoicing application.
• Designed for freelancers, consultants, developers, designers, and other independent professionals.
• Capable of local workflow with SQLite (desktop), or self-hosted web deployment using PostgreSQL.
• Supports offline operation, synchronization conflict detection, and audit logging.
• Includes features such as:
  • Time tracking with actual vs. billable time separation
  • Compliance checks (e.g., German working time rules)
  • Invoice generation
  • PDF timesheets and CSV exports
  • Backup and data integrity mechanisms

Inferred from the description:

• It is built using a monorepo structure with shared business logic across desktop, web, and mobile clients.
• The desktop app uses Tauri 2, Rust, React, Vite, and SQLite.
• The web app uses Next.js 15, PostgreSQL, REST APIs, WebSockets, and Docker.
• Mobile support is present but not yet production-ready.
• It supports both local and self-hosted deployment models.

Not evidenced:

• No actual product usage or customer data.
• No pricing model or monetization strategy.
• No evidence of revenue, ARR, or user base.

The author claims that Tarlog:

• Treats time records as reliable business documents rather than temporary timer data.
• Offers a balance between convenience, privacy, and professional reporting.
• Allows freelancers to track actual working time while calculating billable time independently.
• Provides compliance checks without legal advice.
• Enables full control over infrastructure and data.

Inferred from the description:

• The positioning is centered on privacy, self-hosting, and control.
• It attempts to differentiate itself from cloud-based tools by offering local or self-hosted workflows.
• It positions itself as a tool for independent professionals who value data sovereignty.

Not evidenced:

• No evidence of market positioning strategy or competitive differentiation beyond claims.
• No mention of marketing efforts or user acquisition channels.
• No indication whether the product has evolved since submission to the hackathon.

The description states that Tarlog is designed for:

• Freelancers
• Consultants
• Developers
• Designers
• Other independent professionals

Inferred from the description:

• The target audience values privacy and control over their data.
• They may be technically inclined or interested in self-hosted solutions.

Not evidenced:

• No segmentation beyond job title.
• No evidence of customer personas, user interviews, or feedback loops.
• No indication of whether the author has validated this ICP with actual users.

The description states:

• Tarlog supports local and self-hosted workflows.
• It is not described as a subscription-based service.
• The author mentions that it can be deployed locally or on a self-hosted server using PostgreSQL.

Inferred from the description:

• There is no explicit pricing model mentioned.
• The product appears to be free to use, with optional self-hosting.
• No evidence of monetization strategy beyond the self-hosted option.

Not evidenced:

• No revenue streams, pricing tiers, or monetization plans.
• No indication of whether the author intends to offer paid versions or SaaS services.
• No evidence of customer willingness to pay or market demand for such a solution.

The description states:

• Tarlog is built as a pnpm monorepo with TypeScript.
• Core logic is shared across desktop, web, and mobile apps.
• Desktop uses Tauri 2, Rust, React, Vite, SQLite.
• Web app uses Next.js 15, PostgreSQL, REST APIs, WebSockets, Docker.
• Mobile uses Expo, React Native, local SQLite storage.
• Uses Drizzle ORM for database abstraction.
• Implements synchronization using event logs, optimistic version checks, and Hybrid Logical Clocks.
• Supports conflict detection and resolution.
• Includes automated tests covering core invariants.

Inferred from the description:

• The architecture shows a deliberate effort toward cross-platform consistency and data integrity.
• The use of Rust and Tauri suggests performance and security considerations.
• The system is designed to handle concurrency, offline scenarios, and synchronization challenges.

Not evidenced:

• No evidence of production deployment or scalability testing.
• No information on how the product will be delivered to users beyond self-hosting.
• No mention of developer experience or documentation for end-users.

The description states:

• The project was submitted to a hackathon (OpenAI 2026).
• It supports a complete local workflow without requiring a server or cloud account.
• It includes automated onboarding, real customer/project data creation, and progress saving.
• It has continuous verification through builds, type checks, Rust tests, integration tests, and smoke tests.

Inferred from the description:

• The project is in an early stage of development.
• It shows technical maturity in its architecture and testing practices.
• There is no evidence of user adoption or product-market fit beyond the author’s own use.

Not evidenced:

• No customer base or usage data.
• No revenue, ARR, or monetization metrics.
• No evidence of product-market fit or market traction.
• No indication of whether the project has moved beyond prototype or proof-of-concept stage.

The description does not provide any information about:

• Competitors in the time tracking space.
• Market positioning relative to existing tools.
• Differentiation from other privacy-focused or self-hosted solutions.

Inferred from the description:

• The author positions Tarlog as an alternative to cloud-based time tracking tools that may compromise privacy or require external dependencies.
• It is implied to compete with tools like Toggl, Clockify, Harvest, or similar platforms.

Not evidenced:

• No competitive analysis or market sizing.
• No evidence of awareness of existing players in the space.
• No indication of how Tarlog would scale or compete with established solutions.

Key risks and red flags based on the description:

• Lack of traction: No evidence of users, customers, or revenue. This raises questions about product-market fit.
• Single developer: A team size of one may limit scalability and long-term maintenance.
• Unproven market demand: The author’s own account does not include any validation with real users.
• Experimental features: Mobile support is described as “not yet production ready,” and synchronization is incomplete.
• No monetization strategy: No indication of how the product will generate revenue or sustain itself.
• High technical complexity without user feedback: The architecture shows strong engineering, but there is no evidence that it meets real-world needs.

Not evidenced:

• No risk assessment or mitigation plans.
• No evidence of any pilot users or beta testing.
• No indication of whether the author has considered legal or regulatory implications of compliance features.

1. What is your validation process with actual freelancers or independent professionals?
2. Have you conducted any user interviews or usability tests?
3. How do you plan to monetize this product, if at all?
4. What are the specific use cases that drove development of compliance features?
5. Can you describe how synchronization will work in practice for users?
6. Do you have a roadmap beyond the current prototype stage?
7. Are there any legal or compliance risks associated with providing working time rule checks?
8. How do you plan to support mobile users, especially regarding synchronization and data consistency?
9. What is your timeline for completing desktop and iOS synchronization?
10. Is there any intention to offer a hosted SaaS version in the future?