Ctrl K
ComunidadGuías…
GITHUB · ANALIZADO

veritech-site-checker

Evidence-first technical pre-screening for web-business acquisitions. Built with Next.js, FastAPI, PostgreSQL, Redis, Dramatiq, and Playwright.

Ficha actualizada 22 sept 2026, 22:24 · upstream 22 sept 2026, 22:07 · release sin release detectada

Ver códigoProblemas y ayudaRepositorio ↗
00

Qué es veritech-site-checker

Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.

Veritech Site Checker is a product of Veritech Diligence that provides evidence-linked technical pre-screening for web-based business acquisitions. A user enters a public web domain, confirms they are authorized to assess it, and receives a structured Technical Acquisition Brief: a prioritized risk register where every finding is traceable back to the exact evidence that produced it.

It answers one practical question for a prospective buyer of a web-based business:

> Is this web property worth deeper technical diligence, and what should I investigate next?

Current version: v1.11. Release history in CHANGELOG.md. Build story: A Technical Due Diligence Scanner for Web-Business Buyers (https://dvoorhees.com/2026/08/15/building-a-technical-due-diligence-scanner-for-web-business-buyers/). Live app: sitechecker.veritechdiligence.com.

CASOS DE USO
  • Pre-screen a potential acquisition target to identify technical risks before investing time in deeper due diligence
  • Automate the initial assessment of web properties during M&A or business sales processes
  • Provide buyers with an evidence-backed risk register that eliminates guesswork about what needs investigation
  • Reduce the scope of technical due diligence by surfacing only high-impact findings first
  • Enable repeatable, reproducible assessments across multiple potential targets using versioned rules
PUNTOS DESTACADOS
  • Evidence-first architecture: all findings are derived from normalized evidence items rather than raw responses, ensuring traceability to the original data source
  • Deterministic rule engine with 26 versioned rules that produce reproducible results without any LLM involvement in finding generation
  • On-demand scan runner model using Fly.io Machines instead of a persistent worker or queue system, eliminating idle compute costs between scans
  • Supabase-powered database layer with session pooler connections, providing TLS-encrypted communication and external data source access
  • No payment processor integration: all scans are free for now, with only a per-user scan counter to enforce usage limits
PRECAUCIONES
  • Only assesses publicly accessible web properties; cannot evaluate private or non-public domains
  • Does not perform penetration testing, vulnerability scanning, or access control testing — it only evaluates technical posture and evidence
  • Relies on Fly.io for infrastructure; requires a paid account to run scans in production
  • No automated remediation capabilities: findings are reported but do not execute any fixes themselves
  • Limited to web-based business properties; does not assess software, hardware, or physical assets
  • Rules engine is static and versioned — no machine learning or adaptive behavior is supported
01

Perfil de infraestructura

Estimación inicial derivada del repositorio y de los servicios detectados.

CPU2 vCPUrecomendación inicial
MEMORIA2 GBRAM estimada
DISCO30 GBalmacenamiento base
COMPLEJIDADmediumnivel de operación
02

Despliegue detectado

Qué señales reales de instalación hemos encontrado.

Docker detectado

Deploy using Fly.io with a single Dockerfile containing two images: 'web' (Next.js + FastAPI) and 'scan-runner' (adds Playwright/Chromium). Use the Fly Machines API to create an on-demand scan runner for each scan, then destroy it after completion. The web/API machine runs always-on without auto-stop or auto-start. For local development, run a background subprocess instead of calling the Fly API. Always use TLS-encrypted connections via Supabase's session pooler endpoint.

✓Dockerfile
—Compose
—One-click
03

Stack y dependencias

Componentes inferidos a partir de manifests, configuración y documentación.

FRAMEWORKS
Next.jsNode.jsFastAPIPHPPython
SERVICIOS
PostgreSQLRedisS3/MinIO
BASES DE DATOS
PostgreSQLRedis
PUERTOS
3000543280008080
05

Puede sustituir a

Relaciones detectadas por el análisis del repositorio y su categoría.

06

Experiencia real de la comunidad

Ayuda a contrastar la estimación automática con instalaciones reales.

Todavía no hay datos comunitarios para este proyecto.