TrackMyPG

Website

trackmypg.com

Pricing URL

Official TrackMyPG Pricing

$ Details

paid Free Trial $4.0 / Monthly (Basic plan, 1 PG, unlimited tenants)

Platforms

Web Cloud

Release Date

2026 February

Categories

#Property Management #Rental Property Management #Hotel Management Software #Real Estate #Online Bookings

Startup details

Country

India

State

Uttar Pradesh

City

Noida

Founder(s)

Abhinav Kumar Arya

Employees

1 - 9

@imqueue

Website

imqueue.org

Pricing URL

-

$ Details

-

Platforms

-

Release Date

-

Categories

#Developer Tools #Realtime Backend / API #Tech #App Development #Data Integration #Web Service Automation

TrackMyPG features and specs

• Tenant Management
  Manage tenants, track occupancy, and maintain complete resident records in one place. 2. Rent Collection (Razorpay Enabled)
• Rent Collection (Razorpay Enabled)
  Automate rent collection with Razorpay support for UPI, cards, and net banking.
• Direct Owner Settlement (Razorpay Routes)
  Automatically split and transfer payments directly to property owners without holding funds.
• Automated Invoicing
  Generate and send rent invoices automatically every month with zero manual effort.
• Security Deposit Management
  Collect, track, and manage tenant security deposits with complete transaction history.
• Move-Out Settlement
  Handle tenant move-outs with automated final billing, dues calculation, and deposit adjustments.
• Financial Reporting & Analytics
  Get real-time insights into revenue, collections, and outstanding payments.
• Multi-Property Management
  Manage multiple PGs, hostels, or rental properties from a single dashboard.
• Room & Bed Management
  Track room availability, bed allocation, and occupancy status in real-time.
• Dashboard & Insights
  Visual dashboard with key metrics like occupancy rate, revenue, and collections.
• Mobile Access
  Access and manage your PG business anytime, anywhere from any device.
• Alerts & Notifications
  Receive reminders for due payments, invoices, and important updates.

@imqueue features and specs

• TypeScript-first design
  imqueue is built with TypeScript at its core, providing strong typing, better IDE support, and compile-time error checking, which helps catch bugs early and improves the developer experience when building microservices.
• RPC-style messaging abstraction
  It simplifies inter-service communication by abstracting away the complexities of message queue protocols, allowing developers to make calls that feel like local function calls while the underlying complexity of message passing is handled by the framework.
• Built on RabbitMQ
  By leveraging RabbitMQ as its message broker, imqueue benefits from a mature, battle-tested messaging system with reliable delivery guarantees, clustering support, and a large ecosystem of tools and documentation.
• Code generation and tooling
  imqueue provides CLI tools and code generation capabilities that can automatically create service clients and boilerplate code, reducing repetitive work and helping maintain consistency across microservices.
• Microservices-focused architecture
  The framework is specifically designed for building distributed microservices systems, offering features like service discovery and structured communication patterns that address common challenges in distributed system design.

Possible disadvantages of @imqueue

• Smaller community and ecosystem
  Compared to more mainstream microservices frameworks, imqueue has a relatively small user base and community, which can mean fewer third-party resources, tutorials, Stack Overflow answers, and community-contributed plugins or extensions.
• Limited documentation depth
  While basic documentation exists, some users report that advanced use cases, edge cases, and troubleshooting guides are not as thoroughly documented as more established frameworks, requiring more trial-and-error or direct code inspection.
• RabbitMQ dependency lock-in
  Being tightly coupled to RabbitMQ means teams must adopt and manage this specific message broker, which could be a limitation for organizations that prefer or already use alternative messaging systems like Kafka, NATS, or AWS SQS.
• Learning curve for framework-specific patterns
  Developers need to learn imqueue's specific conventions, decorators, and architectural patterns, which adds an additional learning curve on top of understanding TypeScript and general microservices concepts.
• Potential scalability concerns for very large systems
  As with many queue-based RPC frameworks, extremely high-throughput or very large-scale distributed systems may encounter performance bottlenecks or require significant additional configuration and tuning of the underlying RabbitMQ infrastructure.

Analysis of TrackMyPG