TRONThe next generation of internet

What TRON is

TRON is a downloadable Windows desktop app rather than a website that happens to look like a browser. The desktop app owns the window, the browser controls, the home screen, the tab strip, the address bar, and the transitions between local TRON pages and external web pages.

The core idea is simple: search what TRON already knows locally, then open the result you choose. Search is handled by a local API and a local SQLite corpus. A web page is loaded into a tab only when you decide to open it. This keeps the first interaction focused and makes the boundary between local search and external browsing clear.

TRON is part of the broader TronXVI product system, but it is not the same thing as Infinity, Genesis, Manifest, Platform, or Inbox. Those products have their own roles. TRON is the desktop browser and local search layer.

The TRON experience

The home screen

The home screen gives you one central search field. You can type a search phrase, use the local shortcuts, or enter a web address. The page is intentionally quiet: the main action is deciding where you want to go, not managing a wall of controls before you start.

One window, separate surfaces

TRON keeps its local pages and external pages in the same desktop window while treating them as different surfaces. The home page and search results are rendered by TRON. External pages are loaded in Chromium web views. This lets the browser feel continuous without pretending that an external website is part of TRON’s own trusted interface.

Navigation that behaves like a browser

Each tab can hold a local TRON page or an external web page. The back, forward, reload, new-tab, close-tab, keyboard, and address-bar actions follow the same mental model as a conventional browser. Internal search pages also support pagination when the local corpus contains more results than one page can display.

Search and results

What a search request does

1. You enter a phrase in the home search field or address bar.
2. TRON keeps the request inside the desktop app and sends it to the local API.
3. The API searches the stored SQLite corpus using the indexed search fields.
4. TRON renders the returned titles, URLs, descriptions, domains, dates, and page controls.
5. You choose a result when you are ready to open the external page.

The local search route is /api/search. It accepts a query, page number, and result limit. The desktop client uses the local address http://127.0.0.1:938 by default, and the backend URL can be changed for a controlled installation with the TRON_BACKEND_URL process setting.

Search results are not a live copy of the entire internet. They are the records present in TRON’s local corpus. If a result is missing, that means the local corpus does not currently contain a matching record; it does not mean the page is unavailable on the wider web.

Result details

A result can show a title, canonical URL, display URL, description, domain, collection date, and a favicon. Favicon requests are handled by the local API and cached so that repeatedly seeing the same domain does not require downloading its icon every time.

Local time answers

TRON also includes a local time tool for supported locations. A time request is returned as structured data with a location, timezone, abbreviation, readable time, date, and ISO timestamp. It is separate from web search and does not require opening an external page.

Tabs and web pages

Internal tabs

A new TRON tab starts on the local home screen. Searching from that tab turns it into a local results tab. Internal tabs use a tron://search?q=... address representation so the current search can be understood and restored inside the browser experience.

External tabs

Selecting a result or entering a normal web address creates an external tab. The page is loaded by Chromium inside the TRON window, with its own title, favicon, URL, history, and loading state. Links that request a new window are opened as additional TRON tabs rather than silently escaping the browser flow.

Once an external page is open, that website’s own network requests, cookies, scripts, permissions, and privacy policy apply. TRON does not claim ownership of the content or policies of sites you choose to visit.

Keyboard controls

• Ctrl/Cmd + L focuses and selects the address bar.
• Ctrl/Cmd + T opens a new internal TRON tab.
• Ctrl/Cmd + W closes the active tab.
• The browser back, forward, reload, and new-tab controls remain available in the window chrome.

The local service

The desktop client uses a small FastAPI service to keep search and browser support code out of the renderer. It runs on the local machine and is designed to be an internal service for the desktop app, not a public website or a public developer API.

Health and status routes

The service exposes a health route at /api/health, a metrics route at /api/metrics, and a crawler status route at /api/crawler/status. These routes support local operation and diagnostics. TRON intentionally disables the FastAPI documentation and OpenAPI routes in the current desktop backend because this is not meant to be a hosted API surface.

Why the service is local

Keeping the browser’s primary search request local provides a predictable boundary. The desktop renderer does not need direct database access, and the backend can own indexing, pagination, caching, and crawler state without exposing those implementation details to every UI action.

The optional crawler

TRON includes an optional crawler for building and refreshing the local search corpus. It is disabled unlessTRON_CRAWLER_ENABLED=true is explicitly configured. This is an important product boundary: installing TRON does not silently turn the machine into a crawler.

When enabled, the crawler can use multiple workers, keep one shared SQLite frontier, claim work atomically, recover leased work after an interruption, enforce canonical URL uniqueness, and apply per-domain politeness limits. It also validates redirects, caches sitemap results, and performs public-host DNS checks before work proceeds.

Crawler controls

• POST /api/crawler/start starts a configured crawl.
• POST /api/crawler/stop requests a clean stop.
• POST /api/crawler/seeds adds seed URLs to the local frontier.
• GET /api/crawler/status reports enabled state, queue counts, domains, pages, and the current run.

The main tuning values include worker count, per-domain concurrency, request delay, lease duration, maximum depth, maximum links per page, and maximum queue size. These settings are operational controls for an intentional local crawl, not normal end-user search preferences.

Privacy and security

Local-first does not mean every page is offline

TRON’s search request and stored search corpus are local-first. When you open a result, however, the chosen web page is external content. That page can contact its own servers, load its own resources, and apply its own tracking or account behavior. Local search and external browsing are different privacy contexts.

Renderer isolation

The desktop window is configured with context isolation, disabled Node integration, and a sandboxed preload boundary. The renderer receives a small, explicit bridge for search, update checks, and window controls rather than direct access to Electron internals.

Permissions

External pages can request media and notification permissions through Chromium. Treat those requests as belonging to the website you are visiting. Only grant a permission when you understand why that site needs it and you trust the site.

Credentials and sensitive data

Do not place API keys, passwords, private tokens, or other secrets in the search field, a URL, a screenshot, or a page you do not trust. TRON’s local API is designed for the desktop client; it is not a substitute for a secrets manager or a hardened public service.

Data and storage

TRON stores its search data in a SQLite database inside the backend’s local data directory. Search runs, individual result records, full-text index entries, favicon cache entries, crawler queue state, and crawler run state are all local application data.

The desktop app uses a persistent Chromium partition for external tabs. When TRON opens, the current desktop implementation clears local browser storage and cache for its browser sessions. Website cookies are managed separately by Chromium, so a site’s login behavior can depend on the site and on its own cookie policy.

If you move or remove the backend data directory, TRON may lose its stored search corpus and crawler state. If you need to preserve that information, stop TRON first and back up the application data using your normal Windows backup process before making changes.

What TRON does not promise

• It does not promise that external websites will not track you.
• It does not promise that a local result is current if the corpus has not been refreshed.
• It does not promise recovery of data that was deleted from the local application directory.
• It does not replace a password manager, endpoint security product, or enterprise browser policy.

Installation and first use

Download

Use the Download TRON for Windows button above to download the latest published Windows installer directly from the TRON release channel. The installer is the same packaged desktop application described in this document; it is not a browser-only demo or a link to an unrelated product.

First launch

1. Start TRON from the desktop or Start Menu.
2. Wait for the local service to be available.
3. Use the home search field to search the local corpus.
4. Open a result when you want to browse the external page.
5. Create additional tabs with the new-tab control or Ctrl/Cmd + T.

Advanced local configuration

The desktop client defaults to http://127.0.0.1:938. Controlled installations can provideTRON_BACKEND_URL to point the desktop client at a different internal service andTRON_UPDATE_URL to change the update release endpoint. These are deployment settings and should be managed by the person responsible for the machine, not entered into normal search fields.

Troubleshooting

Search says the service is unavailable

Confirm that TRON is running normally and that its local service can start on port 938. A local health check should return an operational response from /api/health. If another program is already using the configured port, the desktop app and service will not be able to communicate until the port conflict is resolved by the machine administrator.

Search returns no results

Empty results usually mean the local corpus does not contain a match. Search is not automatically a live web search. If you control the installation and need fresh indexed content, review the optional crawler settings, seed the intended public URLs, and check crawler status before starting a run.

A web page will not load

Check the address, the site’s availability, your network connection, and whether the site blocks embedded Chromium views. Try reloading the tab or opening the address in another browser to distinguish a TRON issue from a site issue.

An update check fails

Update checks require access to the configured release endpoint. A network filter, certificate problem, unavailable release, or restricted machine policy can prevent a check. You can also open the release channel directly and install a verified build through your normal software process.

Product boundaries

TRON has deliberately narrow ownership. The desktop app owns browsing and local search. It does not own the Infinity workspace, the Genesis creation surface, the Manifest media surface, the Developers Platform, or the TRONXVI public website. Those products remain separate so that their account, provider, and data behavior can evolve without turning TRON into a hidden replacement for them.

TRON also does not expose a public website, public API documentation site, or hosted OpenAPI contract. Its FastAPI service exists to support the installed desktop client. Any future public search or developer surface would need its own authentication, rate limits, data policy, and deployment boundary.

This separation is useful for users: when you are in TRON, you know whether you are searching local records, viewing a local browser surface, or visiting an external site. The product should not blur those states.

Where TRON goes next

The long-term direction for TRON is a stronger local knowledge and browsing environment: faster indexing, clearer corpus controls, better search quality, more transparent source handling, resilient update delivery, and a polished Windows experience that remains understandable to the person using it.

Future work should preserve the product’s core promises rather than bury them under features: local search should remain visibly local, external pages should remain visibly external, crawling should remain opt-in, permissions should remain understandable, and the installed app should remain separate from the other TronXVI products.

TRON in one sentence

TRON is a Windows desktop browser that searches a local SQLite corpus through a local FastAPI service and opens the web in controlled Chromium tabs when you choose to go there.

If you want the broader TronXVI product experience, open Infinity. If you want developer setup and API documentation, use the Developer guide. TRON remains the focused desktop browser layer.