Automative Market Intel and VoIP Dialer App
Budget: €1,500 – €3,000 EUR
Title: Real-Time Automotive Market Intelligence Engine, Split-Screen UI & Staggered Asterisk VoIP Auto-Dialer
Description:
NOTE: Start your proposal with the word "SNIPER" or you will be ignored instantly.
I am looking for a top-tier full-stack developer / IT-security specialist to build a custom, highly sophisticated real-time automotive market intelligence engine. The platform must be fully containerized via Docker and deployed on my Linux VPS hosted in the Hetzner datacenter in Falkenstein, Germany. This system needs to compete with the speed and logic of premium commercial dealer applications, but serve as an exclusive, private web application optimized for desktop browser use with an integrated automated VoIP infrastructure.
PROJECT ARCHITECTURE & DELIVERABLES (To be executed in structured phases):
PHASE 1: Real-Time Scraper Engine & Token Extraction
* Mobile API Reverse Engineering: Instead of standard, high-latency web scraping, the engine must target the official Mobile App APIs (Android/iOS endpoints) of three major German classified and automotive platforms. You must reverse engineer the API hooks, bypass SSL pinning, and extract the security tokens. (The exact target domains will be shared privately in chat).
* Async Proxy Layer: Implement an advanced asynchronous proxy rotation layer using my private Decodo residential proxies to completely mimic organic mobile user behavior and bypass heavy enterprise WAF filters (Akamai/Cloudflare Bot Management) with zero request throttling.
* Anti-Fabrication Clause: The application-level byte counters and traffic monitoring logs must accurately reflect physical network data consumption. Any artificial duplication of log files or falsification of data traffic metrics will result in immediate termination for cause.
PHASE 2: Core Data Processing, Multi-Platform Deduplication, Text Parsing & Split-Screen UI
* Core Data Schema Fields: The core data processing pipeline must reliably extract and store the following fields from the mobile API payloads:
* Vehicle Core: Make, model, price, mileage, first registration (EZ), fuel type, transmission, power (kW/HP), and VAT status (MwSt. ausweisbar).
* Seller Profile: Strict classification between PRIVATE and DEALER.
* Location: Zip code (PLZ), city, and a dynamic distance calculation (KM radius) relative to my specific German home zip code.
* Contact: Official exposed phone numbers AND parsed numbers.
* Cross-Platform Deduplication: Since many private sellers cross-post the exact same vehicle on multiple networks simultaneously, the backend engine must implement an intelligent deduplication algorithm (matching based on ZIP code, price, mileage, and title/description similarities) to prevent duplicate alerts and duplicate automated calls across the three hidden target platforms.
* Mandatory Description-Text Parsing (Regex/NLP): The system MUST analyze the raw text descriptions (free-text body) using immediate Regex/NLP to extract typed-in, spaces-separated, or obfuscated phone numbers from private sellers (e.g., extracting numbers hidden within text like "0173 58 77..."). This is a core deliverable of Phase 2. Additionally, screen for critical commercial keywords (e.g., "Motorschaden", "Getriebeschaden", "Unfall", "Export").
* WebSocket Streaming UI: Build a password-protected React/Vue desktop dashboard. Data from the scraper must be pushed to the browser via a permanent WebSocket connection with a target latency of 1-2 seconds from the platform's ingestion timestamp (measured from when the ad first physically appears on the sorted search results page 1, NOT platform cache timestamps). Include a toggleable audio alarm for new hits.
* UI Filter Requirement (Seller Type & Real-Time Sorting): The dashboard's search profile filter bar must include two mandatory dropdown selection menus:
1. Seller Type Filter: Options to filter listings by [All Sellers], [Private Only], or [Dealers Only]. The backend must strictly evaluate the account status from the API payload to enforce this.
2. Ingestion Timing Filter: An option to toggle [Real-Time New Listings Only]. When enabled, the engine must completely ignore historical, cached, or baseline deduplication listings and strictly push only brand-new ads dynamically into the WebSocket stream based on the exact creation_timestamp.
* 50/50 Split-Screen Layout: Clicking a vehicle on the left live-feed panel must instantly render the original platform listing on the right panel using an advanced iframe-wrapper (bypassing X-Frame security blocks). This allows me to inspect details and send direct platform messages instantly without leaving the custom app.
* 4-Way Multi-Platform Quick Search: The UI must feature an "Express Research" button. Clicking this must instantly open 4 separate pre-filled browser tabs simultaneously targeting DasTelefonbuch.de, DasOertliche.de, 11880.com, and Google Deep Search using the seller's name and location data to quickly cross-reference hidden phone entries.
* Proxy Traffic Conservation (Night-Mode): The dashboard must feature a global Master ON/OFF toggle. Additionally, implement an automated backend Cronjob to completely pause all scraping operations between 11:00 PM and 06:00 AM (German time) to freeze data traffic and save Decodo bandwidth.
PHASE 3: Automated Local Phoner/VoIP Dialer Integration
* Local Phoner/URI Integration: In this initial phase, the server core will not handle the PBX infrastructure. Instead, the real-time vehicle scraper dashboard must seamlessly interface with my existing local VoIP dialer software (Phoner/PhonerLite interface) running on my desktop PC via standard Windows URL protocols (e.g., phoner:// or tel: handler configurations).
* Automated Stream Triggering: The dashboard must support a fully automated outbound mode. When a brand-new listing hits the live-feed via the WebSocket stream, the frontend must dynamically trigger the local URI handler to execute the call instantly without requiring manual user clicks.
* Master Automation Toggle (ON/OFF Control): The header of the dashboard must feature a prominent, easily accessible global Master ON/OFF toggle switch. When turned ON, the automated outbound call stream is active. When turned OFF, the automation is immediately frozen, pausing all automatic call triggers and switching the system to manual review mode instantly.
* CTI Panel Controls: Integrate a streamlined control header into the web dashboard allowing me to easily toggle between [Manual Click-to-Dial] and [Fully Automated Outbound Stream]. Provide a manual phone number input field for quick-dialing directly from the web layout to the local software application.
STRICT TRANSACTIONAL TERMS (NON-NEGOTIABLE):
* DEVELOPMENT ENVIRONMENT & CODE OWNERSHIP: All initial coding and stress tests must be conducted on your internal servers using your own proxy/server resources. Full repository access (GitHub/GitLab) and well-documented source code must be delivered upon completion of each phase before the respective milestone is released.
* NO DELIVERABLES = NO RELEASE: Milestone funds will only be released upon formal submission of the verifiable source code/codebase. Videos, logs, or external screenshots alone are not accepted as proof of delivery.
* PAID TRIAL ENFORCEMENT: Before awarding the main contract, selected top candidates will be hired for a small, separate test project (€50 - €150) to prove their mobile API bypass competence with 1 of the target platforms on their own server. No funds are released until a live video demo with a current timestamp OR access to a temporary guest endpoint proves 100% data ingestion with under 1-2 seconds latency compared to my active setup.
* 60-DAY WARRANTY HOLDBACK: 25% of the main contract budget will remain frozen in a final milestone for exactly 60 days post-deployment on my VPS. This milestone will only be released after the system runs 100% stable for 60 consecutive days. Any API updates, WAF bypass adjustments, or layout fixes required during this period must be done free of charge.
* MAINTENANCE TRANSPARENCY: You must explicitly state your fixed maintenance rate or terms for future platform API/WAF updates in your initial proposal. No hidden fees allowed.
Budget & Compensation:
Our initial baseline budget is set around €1,500.00 - €2,500.00 EUR. However, we know this is a highly sophisticated cryptographic, reverse-engineering, and VoIP trunking task. We are fully open to realistic counter-proposals and higher bids from proven experts who can demonstrate they have successfully built ultra-fast automotive scrapers before. Quality, reliability, low latency, and long-term stability are our absolute priorities.
Description:
NOTE: Start your proposal with the word "SNIPER" or you will be ignored instantly.
I am looking for a top-tier full-stack developer / IT-security specialist to build a custom, highly sophisticated real-time automotive market intelligence engine. The platform must be fully containerized via Docker and deployed on my Linux VPS hosted in the Hetzner datacenter in Falkenstein, Germany. This system needs to compete with the speed and logic of premium commercial dealer applications, but serve as an exclusive, private web application optimized for desktop browser use with an integrated automated VoIP infrastructure.
PROJECT ARCHITECTURE & DELIVERABLES (To be executed in structured phases):
PHASE 1: Real-Time Scraper Engine & Token Extraction
* Mobile API Reverse Engineering: Instead of standard, high-latency web scraping, the engine must target the official Mobile App APIs (Android/iOS endpoints) of three major German classified and automotive platforms. You must reverse engineer the API hooks, bypass SSL pinning, and extract the security tokens. (The exact target domains will be shared privately in chat).
* Async Proxy Layer: Implement an advanced asynchronous proxy rotation layer using my private Decodo residential proxies to completely mimic organic mobile user behavior and bypass heavy enterprise WAF filters (Akamai/Cloudflare Bot Management) with zero request throttling.
* Anti-Fabrication Clause: The application-level byte counters and traffic monitoring logs must accurately reflect physical network data consumption. Any artificial duplication of log files or falsification of data traffic metrics will result in immediate termination for cause.
PHASE 2: Core Data Processing, Multi-Platform Deduplication, Text Parsing & Split-Screen UI
* Core Data Schema Fields: The core data processing pipeline must reliably extract and store the following fields from the mobile API payloads:
* Vehicle Core: Make, model, price, mileage, first registration (EZ), fuel type, transmission, power (kW/HP), and VAT status (MwSt. ausweisbar).
* Seller Profile: Strict classification between PRIVATE and DEALER.
* Location: Zip code (PLZ), city, and a dynamic distance calculation (KM radius) relative to my specific German home zip code.
* Contact: Official exposed phone numbers AND parsed numbers.
* Cross-Platform Deduplication: Since many private sellers cross-post the exact same vehicle on multiple networks simultaneously, the backend engine must implement an intelligent deduplication algorithm (matching based on ZIP code, price, mileage, and title/description similarities) to prevent duplicate alerts and duplicate automated calls across the three hidden target platforms.
* Mandatory Description-Text Parsing (Regex/NLP): The system MUST analyze the raw text descriptions (free-text body) using immediate Regex/NLP to extract typed-in, spaces-separated, or obfuscated phone numbers from private sellers (e.g., extracting numbers hidden within text like "0173 58 77..."). This is a core deliverable of Phase 2. Additionally, screen for critical commercial keywords (e.g., "Motorschaden", "Getriebeschaden", "Unfall", "Export").
* WebSocket Streaming UI: Build a password-protected React/Vue desktop dashboard. Data from the scraper must be pushed to the browser via a permanent WebSocket connection with a target latency of 1-2 seconds from the platform's ingestion timestamp (measured from when the ad first physically appears on the sorted search results page 1, NOT platform cache timestamps). Include a toggleable audio alarm for new hits.
* UI Filter Requirement (Seller Type & Real-Time Sorting): The dashboard's search profile filter bar must include two mandatory dropdown selection menus:
1. Seller Type Filter: Options to filter listings by [All Sellers], [Private Only], or [Dealers Only]. The backend must strictly evaluate the account status from the API payload to enforce this.
2. Ingestion Timing Filter: An option to toggle [Real-Time New Listings Only]. When enabled, the engine must completely ignore historical, cached, or baseline deduplication listings and strictly push only brand-new ads dynamically into the WebSocket stream based on the exact creation_timestamp.
* 50/50 Split-Screen Layout: Clicking a vehicle on the left live-feed panel must instantly render the original platform listing on the right panel using an advanced iframe-wrapper (bypassing X-Frame security blocks). This allows me to inspect details and send direct platform messages instantly without leaving the custom app.
* 4-Way Multi-Platform Quick Search: The UI must feature an "Express Research" button. Clicking this must instantly open 4 separate pre-filled browser tabs simultaneously targeting DasTelefonbuch.de, DasOertliche.de, 11880.com, and Google Deep Search using the seller's name and location data to quickly cross-reference hidden phone entries.
* Proxy Traffic Conservation (Night-Mode): The dashboard must feature a global Master ON/OFF toggle. Additionally, implement an automated backend Cronjob to completely pause all scraping operations between 11:00 PM and 06:00 AM (German time) to freeze data traffic and save Decodo bandwidth.
PHASE 3: Automated Local Phoner/VoIP Dialer Integration
* Local Phoner/URI Integration: In this initial phase, the server core will not handle the PBX infrastructure. Instead, the real-time vehicle scraper dashboard must seamlessly interface with my existing local VoIP dialer software (Phoner/PhonerLite interface) running on my desktop PC via standard Windows URL protocols (e.g., phoner:// or tel: handler configurations).
* Automated Stream Triggering: The dashboard must support a fully automated outbound mode. When a brand-new listing hits the live-feed via the WebSocket stream, the frontend must dynamically trigger the local URI handler to execute the call instantly without requiring manual user clicks.
* Master Automation Toggle (ON/OFF Control): The header of the dashboard must feature a prominent, easily accessible global Master ON/OFF toggle switch. When turned ON, the automated outbound call stream is active. When turned OFF, the automation is immediately frozen, pausing all automatic call triggers and switching the system to manual review mode instantly.
* CTI Panel Controls: Integrate a streamlined control header into the web dashboard allowing me to easily toggle between [Manual Click-to-Dial] and [Fully Automated Outbound Stream]. Provide a manual phone number input field for quick-dialing directly from the web layout to the local software application.
STRICT TRANSACTIONAL TERMS (NON-NEGOTIABLE):
* DEVELOPMENT ENVIRONMENT & CODE OWNERSHIP: All initial coding and stress tests must be conducted on your internal servers using your own proxy/server resources. Full repository access (GitHub/GitLab) and well-documented source code must be delivered upon completion of each phase before the respective milestone is released.
* NO DELIVERABLES = NO RELEASE: Milestone funds will only be released upon formal submission of the verifiable source code/codebase. Videos, logs, or external screenshots alone are not accepted as proof of delivery.
* PAID TRIAL ENFORCEMENT: Before awarding the main contract, selected top candidates will be hired for a small, separate test project (€50 - €150) to prove their mobile API bypass competence with 1 of the target platforms on their own server. No funds are released until a live video demo with a current timestamp OR access to a temporary guest endpoint proves 100% data ingestion with under 1-2 seconds latency compared to my active setup.
* 60-DAY WARRANTY HOLDBACK: 25% of the main contract budget will remain frozen in a final milestone for exactly 60 days post-deployment on my VPS. This milestone will only be released after the system runs 100% stable for 60 consecutive days. Any API updates, WAF bypass adjustments, or layout fixes required during this period must be done free of charge.
* MAINTENANCE TRANSPARENCY: You must explicitly state your fixed maintenance rate or terms for future platform API/WAF updates in your initial proposal. No hidden fees allowed.
Budget & Compensation:
Our initial baseline budget is set around €1,500.00 - €2,500.00 EUR. However, we know this is a highly sophisticated cryptographic, reverse-engineering, and VoIP trunking task. We are fully open to realistic counter-proposals and higher bids from proven experts who can demonstrate they have successfully built ultra-fast automotive scrapers before. Quality, reliability, low latency, and long-term stability are our absolute priorities.