NEARWEB SERVICE
modes
NEAR PLATFORM / MULTI-SURFACE CLIENT

SELECT MODES

A minimal public surface for users, a working console for operators, and one backend that keeps orchestration hidden where it belongs.

Current Stage
Framework Shell
Primary Scenario
Image Enhance
Enter AppEnter Console
User sees a mode. Backend handles orchestration. Console keeps operations visible.
Image Enhance
User Mode

One prompt, input images, one generate action, a result stage, and a gallery. Hidden behind it can live VLM analysis, prompt writing, tiled generation, and routing.

Minimal outside / deep inside
NEAR Console
Admin + Dev

Users, licenses, runs, balances, pipeline versions, and internal traces should stay observable in one working surface.

Visibility without exposing secrets
Orchestration Layer
Backend Core
VLM -> LLM -> Tiles -> Generate -> Check
One external contract, many internal steps
PRODUCT LOGIC

Simple surfaces. Hidden machinery.

User seesone mode, one action, one result
Backend doesanalysis, prompting, generation, validation, routing
Console keepslicenses, runs, pipelines, and failures observable
ARCHITECTURE

One backend. Three clients.

01

NEAR App

Public browser client with product modes, credits, runs, and results.

02

NEAR Console

Operator surface for balances, runs, pipelines, and error visibility.

03

Photoshop Plugin

Future client to the same backend, while direct Fal mode stays untouched for now.

ROADMAP

Build in layers, not rewrites.

Phase 1

Web Shell

Create landing, app, console, visual language, and local docs.

Phase 2

Real App MVP

Connect run creation, status polling, result view, and history.

Phase 3

Console Ops

Expose licenses, manual balances, pipeline catalog, and run inspector.

Phase 4

Plugin Integration

Connect near_cloud_mode only after backend and web flow become stable.