YOUR CLOUD
Your StorageA new photo or video is uploaded
FyreMemories ProcessorStarts as soon as the event fires
Photo and Video AnalysisReads the file and creates a summary
Upload photos and videos,
FyreMemories turns them into memories.
Keep your existing upload flow. FyreMemories picks up each new photo or video, processes it inside your cloud, and delivers personalized memories back to your app. We're the memories-generation layer for any surface, delivered through native SDKs, starting with Android.
Runs in your cloud Event-driven No polling Zero maintenance
HOW IT WORKS
From upload to memory feed.
Your cloud handles the incoming files. FyreMemories turns the results into memories your app can render.
summary
only
only
FYREMEMORIES CLOUD
Data LayerThe summary is stored and indexed
Memories EngineMemories are built for each user
Memories APIYour SDK reads the results live
FyreMemories reads each photo and video inside your environment and sends only a summary downstream.
FyreMemories' processor only needs permission to read from your storage bucket.
Most teams finish setup in an afternoon, with our team available to help live.
FOR YOUR ENGINEERING TEAM
Three integration steps. No custom memory UI required.
Install the SDK, initialize it after sign-in, and choose the surface that fits your app. Steps below are for the Android SDK; other platform SDKs follow the same pattern.
Add the SDK dependency
Install FyreMemories from Maven Central, keep Maven Central enabled, and compile your app with the required Android and Java 17 toolchain.
Initialize after Firebase sign-in
Call FyreMemories.init() once a user is signed in. The SDK reads the current Firebase user automatically and prepares caching, analytics, and per-user memory data.
Render the experience
Drop MemoriesCarouselView into your layout, open the full-screen feed, or use the headless repository if you want complete control over the UI.
WHO OWNS WHAT
What stays with you, and what FyreMemories handles.
Clear boundaries from day one.
Your infrastructure
- Storage bucket: unchanged, nothing moves
- Processing runtime: FyreMemories code runs in your cloud
- Access permissions: read-only, scoped by your team
- Upload event trigger: one config, fires automatically
FyreMemories infrastructure
- Processing package: we ship it, update it, maintain it
- Analysis logic: runs in your cloud, IP stays ours
- Memory storage: all memories live in FyreMemories systems
- Memories API: your SDK reads from here
Set up the backend in one afternoon.
Most teams are fully integrated the same day. We can stay close while your engineers wire it up.