Real-time Sync: How aukimi Connects Modules in Under 0.1 Seconds

The biggest productivity killer in creative work isn't rendering.

It's workflow fragmentation.

Separate tools. Separate timelines. Separate copies of the same asset. Lag between tools. Lag between decisions. Lag between iterations.

Export. Import. Convert. Re-link. Repeat. Version chaos. Broken paths. Lost changes.

Traditional creative software isolates modules like separate apps. No shared state. No live propagation. Files as the transport layer.

That design creates two constant failures:

• Fragmented workflows. Context switching every few minutes.
• Lag between tools. Updates arrive late. Or never.

1. THE PROBLEM

Creative work crosses disciplines constantly. 2D. 3D. Video. Audio. Game logic. UI. Motion.

In legacy stacks, every boundary costs time. Serialization to disk. Re-import. Cache rebuild. Proxy generation. Then a second cost: Human attention. Broken flow state.

Typical chain. Same pattern everywhere:

• Edit texture
• Export file
• Switch app
• Import asset
• Fix color space / scale
• Re-export / Re-import / Re-link paths

Ten minutes of creation. Forty minutes of transfer. Fragmentation stays. Lag stays. Work slows.

Kill the gap.

2. LA SOLUTION TECHNIQUE

aukimi runs modules on one runtime. One session. One asset graph. One source of truth.

Not separate apps. Not file handoffs. Shared state. Event-driven updates. Deterministic propagation.

UNDER 0.1s means one thing: Edit committed. Dependency graph resolved. Consumers invalidated. Views refreshed. No disk I/O. No format export. No cold import.

REAL-TIME SYNC ARCHITECTURE

Core pieces. Always on:

• ASSET GRAPH: Nodes for media, transforms, renders, timelines, and metadata.
• SHARED STATE: Canonical data model. Same IDs across all modules.
• CHANGE LOG: Small diffs, not full-file rewrites.
• SUBSCRIPTIONS: Each module watches exactly what it uses.

A texture edit stays a texture edit. No PNG detour. No "where did the file go".

WEBASSEMBLY + WEBGPU

Compute runs in WebAssembly for near-native performance. Threading via Web Workers ensures no UI lock. Heavy tasks like baking or simulating happen off-thread and sync back in diffs.

Rendering uses WebGPU for modern, low-latency redraws. One edit triggers a targeted refresh, not a rebuild of the entire world.

3. CE QUE ÇA CHANGE POUR LES CRÉATEURS

Speed changes behavior. Under 0.1 seconds turns "update later" into "update now".

FLOW STATE

No export ritual. No import ritual. No "hold on while it reloads". You stay inside the work. Eyes on the frame. Hands on the tool. Context preserved. Decisions faster.

ZERO FRICTION

One asset graph removes the hidden chores:

• No path management or relinking.
• No format negotiations or proxy pipelines.
• No "which version is latest".

CROSS-DISCIPLINE FEEDBACK

2D and 3D stop being separate phases. Video and audio stop being separate passes. You see consequences immediately. That feedback loop is the real product. Not "faster exports". No exports.

4. CTA

Build inside the connected suite. Start here: aukimi.com

Back the build. Join the crowdfunding: aukimi.com/crowdfunding

Get into the technical loop on Discord: Join our Alpha

---

aukimi is developed by nammu, a Geneva-based web development company focused on building human-first creative technology.