How zenginby/kromis works
Kromis Studio is a browser-based creative studio: users describe an image or video, refine a prompt and model settings, submit generation, then manage results in a gallery with folders, palettes, and overlays. The web-first product also includes accounts, credits, subscriptions, and provider-key settings. The graph separates the documented studio capabilities from account/billing and the internal queue, worker, and persistence layers. Some subsystems are represented from README claims and indexed file references; unsampled implementations are not assumed to have unverified call links.
Main entry points: core.js Studio interface · app.py Web application · uretim.py Generation routes · providers.py Provider dispatch
Components 26
Creative studio
- Studio interface
static/core.js - Prompt director
static/chat.js - Chat routes
routers/sohbet.py - Palette tools
routers/paletler.py - Palette logic
services/palet.py - Gallery and folders
routers/galeri.py - Brand overlays
composite.py - Provider settings
routers/ayarlar.py
Generation
- Generation routes
routers/uretim.py - Model catalog
catalog.py - Provider dispatch
providers.py - Image providers
azure_client.py - Video providers
veo_client.py - Job routes
routers/isler.py
Accounts and billing
- Identity gate
services/kimlik.py - Account routes
routers/hesap.py - Credit ledger
services/defter.py - Payment processing
services/odeme.py - Polar payments
services/polar.py
Runtime and data
- Job queue
services/kuyruk.py - Generation worker
services/isci.py - Web application
app.py - PostgreSQL session
services/db.py - Data schema
services/tablolar.py - Media storage
services/nesne_depo.py
Other components
- Studio user
Connections 33
- Studio user → Studio interface: uses
README.md - Studio interface → Prompt director: directs prompt
README.md - Studio interface → Chat routes: requests chat
- Studio interface → Generation routes: submits generation
README.md - Studio interface → Palette tools: edits palette
README.md - Palette tools → Palette logic: uses
- Studio interface → Gallery and folders: manages results
README.md - Studio interface → Brand overlays: overlays branding
README.md - Studio interface → Provider settings: sets credentials
README.md - Web application → Generation routes: registers route
app.py - Web application → Chat routes: registers route
app.py - Web application → Gallery and folders: registers route
app.py - Web application → Palette tools: registers route
app.py - Web application → Provider settings: registers route
app.py - Web application → Job routes: registers route
app.py - Web application → Account routes: registers route
app.py - Generation routes → Model catalog: selects model
routers/uretim.py - Generation routes → Job queue: enqueues job
routers/uretim.py - Generation routes → Provider dispatch: dispatches generation
- Provider dispatch → Image providers: calls image APIs
providers.py - Provider dispatch → Video providers: calls video APIs
providers.py - Job routes → Job queue: reads job state
routers/isler.py - Generation worker → Job queue: claims jobs
services/isci.py - Generation worker → Provider dispatch: runs generation
services/isci.py - Generation worker → Media storage: stores results
services/isci.py - Account routes → Identity gate: requires identity
routers/hesap.py - Generation routes → Identity gate: requires identity
routers/uretim.py - Account routes → Credit ledger: reads account credits
routers/hesap.py - Payment processing → Polar payments: uses payment provider
services/odeme.py - Payment processing → Credit ledger: applies paid credits
services/odeme.py - PostgreSQL session → Data schema: maps tables
- Job queue → PostgreSQL session: persists jobs
- Credit ledger → PostgreSQL session: persists ledger