Accelerating Interactive Book Creation for Ojje

Accelerating Interactive Book Creation for Ojje

Business Problem

  • While AI has reduced the story creation process from 70 to 2 days, allowing a book to be completed in a day with manual selections, Ojje aims to streamline this process further to bring it down to just a few hours.
  • GCP’s infrastructure previously posed challenges to rapid content production, but Ojje has since shifted to AWS for better performance, scalability, and cost efficiency.
  • Ojje is now evaluating AWS to ensure it meets operational and financial objectives. A proof of concept is needed to demonstrate faster book creation and validate AWS’s potential.

About Ojje

Ojje is a pioneering learning product that enhances children’s reading skills through self-guided interactive books. Its mission is to become the leading self-driven interactive book publisher globally and address the decline in reading skills globally.

Explore Now

Solution

GoML became a vital partner for Ojje by delivering comprehensive solutions that addressed their key challenges. 

Accelerating Interactive Book Creation for Ojje
Click to View in Full Size

Architecture

  • API Gateway
    – Manages API requests and directs traffic to backend services.
  • AWS IAM
    – Controls user permissions and secures access to AWS resources.
  • Claude Bedrock (Amazon Bedrock)
    – Powers scalable and flexible story generation with the Anthropic Claude 3.0 model.
  • Story Writer Service
    – Generates and refines story content using Claude Bedrock.
  • Story Image Generator
    – Creates visual content aligned with story prompts using MidJourney.
  • MidJourney
    – Provides high-quality artistic and thematic storybook images.
  • AWS Lambda
    – Executes serverless code in response to story and image processing events.
  • AWS CloudWatch
    – Monitors and logs AWS resources and application performance.
  • AWS EC2
    – Manages Docker container images for application deployment.
  • Private Network
    – Ensures secure communication between AWS resources.
Outcomes

0%

Reduction in interactive content creation by moving to AWS from GCP, From 2 days to less than 1 hour

0%

Improved Efficiency with
automated prompt engineering.

0%

Scalable Infrastructure and AWS infrastructure are leveraged to
handle increased demand

Technology Stack​