Technology & transparency

Be ambitious. Be specific.

A clear distinction between a product you can explore, an experiment we are developing and an idea for the future.

Product availability

Product availability is recorded in our shared product directory. Each application has its own destination. This company website does not establish shared authentication, data synchronization or integrations between them.

Qura Browser foundations

The browser direction builds on Chromium. We are not claiming an independently built rendering engine. Work began on October 1, 2024; limited resources led to a practical shift to Chromium approximately two months later. The public beta has not launched: an NTP issue remains. Release mode works on the founder’s system, not a general security guarantee.

Search and EraA

Qura Search is paused. Qura Bots performed crawling and indexing until the Supabase storage/backend filled. Supabase subsequently stopped the backend, and search results stopped displaying.

EraA Beta and V1 are live. The current implementation is API-based and operates through a free-trial setup. The founder is working toward fine-tuning a self-made LLM; it is not claimed to be complete or powering production. Specific API providers and data handling still remain unconfirmed here and under review by the product.

Future: productivity and storage

Refer to the product directory for current availability. No future delivery dates or infrastructure guarantees are announced here.

The company website

This site uses Next.js, React and TypeScript. Existing submission workflows use Supabase and Resend. Automated certificate lookup is temporarily disabled; manual verification is available through the company contact channel. These workflows are separate from the product implementations.

Research directions

Our areas of interest include human-computer interaction, locally relevant information discovery and responsible AI assistance. Research interests are not completed capabilities, published results or performance benchmarks.

Privacy as an engineering responsibility

Privacy depends on implementation and provider configuration—not just intent. Our policy identifies known data flows and flags the details that need confirmation.

Read the privacy notice