AdmitPulse

The description states:

• AdmitPulse monitors public university admission data.
• It shows applicants available places, submitted applications, estimated ranking, competition level, and current admission status.
• Users receive Telegram alerts when their position changes or new data appears.
• The backend is built with Python (FastAPI, SQLAlchemy, SQLite, APScheduler), the frontend with React/TypeScript.
• It collects HTML/XML data from universities, normalizes it, stores historical records, and schedules updates.
• It uses OpenAI Codex for development assistance.

Inference The tool appears to be a web-based application that scrapes public university admission pages and presents them in a structured way, with alerting capabilities.

The description states:

• The author built it while applying to university.
• It brings scattered information into one clear dashboard.
• It is not just another directory but a decision-making tool for applicants.
• It reports data reliability (live, stale, unavailable, unsupported) instead of presenting unreliable data as current.

Inference The positioning is that AdmitPulse is a utility for applicants to track admission chances and make informed decisions — not a general-purpose university directory or marketplace.

The description states:

• The primary users are university applicants.
• It supports 47 universities and 33 identified data sources.
• It also mentions potential future use by schools, consultants, and education services.

Inference The core customer is individual applicants. Secondary audiences may include educational institutions or consultants, but no evidence of actual customers beyond the author’s own use case.

The description states:

• No pricing information is provided.
• The author mentions API access for education services as a future feature.
• There is no indication of monetization or revenue streams.

Inference There is no evidence of a business model or pricing structure. The tool appears to be self-funded and built by one person with no commercial traction.

The description states:

• Backend built with Python (FastAPI, SQLAlchemy, SQLite, APScheduler).
• Frontend uses React/TypeScript.
• Deployment on Linux VPS using Docker, Nginx, systemd.
• Tests written with pytest.
• Uses OpenAI Codex for development.
• Supports scheduled updates and Telegram notifications.

Inference The technical stack is standard for a small-scale SaaS or data aggregation tool. The use of Docker and systemd suggests some level of production readiness, but no evidence of scaling or robust infrastructure beyond MVP.

The description states:

• MVP with support for 47 universities and 33 identified data sources.
• Supports live monitoring for the first university.
• Includes historical records, automated tests, Docker deployment, backup scripts.
• The author claims to have built a working MVP.

Inference There is no evidence of users, customers, or adoption beyond the author’s own use case. No revenue, ARR, or user base are mentioned.

The description states:

• No mention of competitors.
• It is described as not being another university directory.
• The focus is on data reliability and decision-making support.

Inference No evidence of competitive analysis or market positioning beyond the author’s own claims. The tool does not appear to be part of a larger ecosystem or platform.

The description states:

• Universities do not provide standard APIs, so data collection is inconsistent and error-prone.
• Data sources can return outdated, incomplete, or unavailable information.
• Ranking calculations are complex due to equal scores and missing fields.
• The author acknowledges that collecting data is easier than proving it can be trusted.

• What is the actual adoption rate among applicants?
• Are there any users beyond the author’s own use case?
• How does the tool handle data inconsistencies from universities?
• Is there a plan to monetize or scale beyond the MVP?
• What are the legal and ethical implications of scraping university admission data?
• How is the data validation process implemented, and how reliable is it?