IleZa.pl (ileza)
Live website: IleZa.pl - personal price estimates and Polish salary calculator
Personal price estimates and dated histories by Bahdan Hal for products in Poland, paired with a private browser-based salary and income calculator.
Related projects: Bahdan Hal - software engineering consulting · Stackhal - free developer and DevOps tools
Shared Packagist packages: bahdan/symfony-privacy-analytics-bundle · bahdan/lead-capture-bundle
1. Overview
IleZa.pl ("Ile za?") publishes Bahdan Hal’s personal opinion on what he would pay for a product. Different information and experiments inform these judgments; the author chooses the final price and has no single fixed methodology. It is designed to cover any product category, including electronics, vehicles, and cosmetics, alongside a browser-only Polish employment and tax comparison calculator.
Core Features & Canonical Routes:
- Fair-Price Catalog (
/, PL:/pl/): Catalog of products with the author’s personal price estimates. - Product History (
/ceny/{slug}, EN:/prices/{slug}): Dated personal price estimates, price ranges, availability, and historical changes. - Employment & Tax Calculator (
/kalkulator-wynagrodzen, EN:/salary-calculator): Browser-only comparison of UoP, Umowa Zlecenie, Umowa o Dzieło, and B2B from a single company employer budget using 2026 Polish tax rules. - Product Addition Request (
/zglos, EN:/request): Community submission queue for new models. - Price Tip Submission (
/ceny/{slug}/okazja, EN:/prices/{slug}/price-tip): Community price alerts for admin review. - Model Context Protocol (
POST /mcp): MCP tools for price lookups, tax calculations, and authenticated admin operations.
Price research queue
The authenticated get_next_price_research_batch MCP tool (with legacy alias get_next_polish_fair_price_batch)
returns up to twenty products by default (configurable up to 50 via limit), with exact definitions,
configurations, latest prices, availability, and observation dates. Products without observations come first,
followed by the oldest observation date and slug. Observations from today or yesterday in Europe/Warsaw
are excluded, including unavailable observations. The response includes eligible_count and has_more
for the current queue. Verified observations are submitted via record_price_observation (alias: update_polish_fair_price_observation).
Call it again after saving a verified batch. It reads observation histories in bulk on every call;
it does not make one database query per product or reserve work. Concurrent coordinators must
coordinate assignments separately. Optional exclude_slugs defers explicitly tracked products;
excluded products are not included in eligible_count and must remain in the coordinator's ledger.
Repeated calls without writes or exclusions return the same batch. An empty batch means no
eligible products under these freshness and exclusion rules, not proof that deferred work is complete.
2. Verification
docker build --target test -t bahdan-landing-test .
docker run --rm --env-file .env.example -e APP_ENV=test bahdan-landing-test vendor/bin/phpunit --fail-on-phpunit-notice
docker run --rm bahdan-landing-test vendor/bin/phpstan analyse --no-progress --memory-limit=512M
docker run --rm bahdan-landing-test vendor/bin/phpcs
3. Privacy & Security Invariants
- Zero Marketplace Scraping: The service never crawls marketplace pages automatically.
- Voluntary Community Price Tips: Submitted URLs are stripped of tracking parameters, never fetched automatically, stored privately for manual review, and automatically pruned after 90 days.
- IP Hashing: Client IP addresses are irreversibly hashed using HMAC-SHA256 before persistence.
- Database Isolation: PostgreSQL operates exclusively within an internal Docker network.