Daykeeper

Daykeeper, as described by its author, is a personal journaling and social platform built by a 15-year-old developer in Brazil. The project began in February 2024 and has evolved over more than two and a half years into a full-stack application with features including photo/video posts, AI moderation, calendar-based organization, privacy controls, and social networking elements.

The author states that Daykeeper is not intended to be a scrolling feed but rather a tool for users to "pay attention to their own lives" and preserve meaningful memories. It combines familiar social media features with journaling tools and personal organization capabilities.

Key technical aspects include:

• Built on Node.js, Express, MongoDB, AWS services
• Uses custom authentication, AI moderation via AWS Rekognition, asynchronous processing queues
• Supports time zone-aware calendar functionality
• Open-source with public API and web/mobile applications

The author reports no revenue or customers, and the platform is described as being in beta. The project has been presented at an official IB event and has led to opportunities outside of development.

Most important open question: What is the actual user demand for this type of product? The description contains no evidence of users beyond the creator's own use, nor any indication of whether others find value in the platform or its features.

The description states that Daykeeper is a social journal that helps people capture each day through photos, notes, tasks, and memories, then organize everything in a personal calendar.

It includes:

• Posts with text, photos, videos
• Automatic AI moderation for uploaded media
• Social features: likes, comments, replies, follow requests
• Privacy controls (public, private, Close Friends visibility)
• Personal calendars with posts, tasks, and events
• Recurring task templates
• Streaks and activity history
• Notifications and session management

The author describes it as a platform that combines "familiar social features with tools inspired by journaling and personal organization."

The description states that Daykeeper began with the author's fear that days pass without being noticed or remembered. The core positioning is to help people "pay attention to their own lives, preserve meaningful memories, and understand how their time is being spent."

The platform is positioned as:

• A social journal rather than a scrolling feed
• A tool for personal organization and memory preservation
• An alternative to traditional social media consumption patterns

The author emphasizes that the goal is not to encourage hours of scrolling but to help users "pay attention" to their own lives.

The description states that Daykeeper is designed for people who want to:

• Maintain a meaningful record of their lives
• Capture daily experiences through photos, notes, tasks, and memories
• Organize their time and activities in a personal calendar
• Preserve meaningful moments that might otherwise be forgotten

The author describes the platform as being built for "people" generally, without specifying particular demographics or user segments beyond those who would value journaling and memory preservation.

The description states that Daykeeper is completely free. The author mentions investing more than R$5,000 into its design, branding, servers, testing, and development, but does not indicate any monetization strategy or pricing model.

There is no evidence of revenue streams, subscription models, advertising, or paid features in the description.

The author built Daykeeper as a full-stack project using:

• Backend: Node.js, Express, MongoDB, Mongoose
• Authentication: Custom access and refresh tokens, Passport, Google authentication
• Media storage: Amazon S3
• AI moderation: AWS Rekognition
• Asynchronous processing: BullMQ, Redis
• Notifications: Firebase Admin, Nodemailer
• Date/time handling: date-fns, date-fns-tz

The platform includes features like:

• Session management
• Email verification and password recovery
• Responsive design across screen sizes
• Public and private user accounts
• Reporting and administrative systems

The author notes that the project is open source with API, web application, mobile application, and API documentation publicly available.

The description states:

• The platform has been in development for more than two and a half years
• It was presented as the author's IB Personal Project
• The author built a landing page and demonstrated the functioning API through Postman at that stage
• The application is now functional and in beta
• The author personally invested over R$5,000 into development

However, there is no evidence of users, customers, or revenue. The description explicitly states that no traction data beyond the creator's own use is available.

The description does not mention any direct competitors. It positions Daykeeper as a platform that combines "familiar social features with tools inspired by journaling and personal organization," but provides no information about existing products in this space or how Daykeeper differentiates from them.

• No evidence of users or customers - The description contains no data on actual user adoption, engagement, or demand
• Single-person development - The platform was built by one person (the author) with no indication of team size beyond that
• Lack of commercial traction - No revenue, monetization strategy, or customer base is evidenced
• Unproven market demand - The description does not establish whether others find value in the product or its features
• Limited scalability concerns - While technical architecture is described, there's no evidence of performance testing or scaling challenges faced by users

1. What specific user problems are you solving that existing solutions don't address?
2. How many actual users do you have, and what is their engagement level?
3. What is your plan for monetization if you want to scale beyond personal investment?
4. How do you plan to handle content moderation at scale?
5. What are the key technical challenges you've faced that you haven't yet solved?
6. How do you plan to acquire users organically or through marketing?
7. What metrics do you use to measure product success and user satisfaction?