DocForge vs Logotypes

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d100%82.4%
Uptime · 30d100%76.7%
P50 · ms15833861
P95 · ms24854993
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DocForge vs Logotypes: common questions

Which is more reliable, DocForge or Logotypes?

On our scheduled checks, DocForge leads on measured uptime — DocForge at 100% versus Logotypes at 82.4% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, DocForge or Logotypes?

DocForge has the lower median latency in our checks — DocForge responds in 1583 ms versus Logotypes at 3861 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do DocForge and Logotypes need an API key?

Neither needs a paid key — DocForge is callable with no signup, and Logotypes is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call DocForge and Logotypes from the browser?

Only Logotypes is browser-friendly — it returns CORS headers over HTTPS. DocForge needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are DocForge and Logotypes free for commercial use?

DocForge has unclear commercial terms, and Logotypes has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.