Case Study: 123RF
123RF is a global digital content marketplace serving the creative media industry with stock photos, vectors, videos, audio, and AI-generated visual content. The platform supports designers, marketers, publishers, enterprises, and businesses worldwide, enabling millions of users to access high-quality visual assets for commercial, editorial, marketing, and creative projects at scale.
As the platform expanded globally, the engineering organization was responsible for building and maintaining a large-scale distributed architecture that powers content discovery, licensing, payments, search, AI services, and creator workflows.
Challenges
As the platform and engineering organization scaled, 123RF began experiencing several
challenges that impacted development velocity, software quality, and operational efficiency.
Declining Engineering Velocity
The growing microservices architecture increased system complexity, making it more difficult for developers to understand service dependencies, navigate the codebase, and deliver new features efficiently. Engineers were spending increasing amounts of time writing repetitive boilerplate code, tracing integrations, and debugging cross-service issues.
Code Review Bottlenecks
Senior engineers were dedicating an estimated 30–40% of their time to pull request reviews, reducing their availability for higher-value activities such as architecture planning, innovation, and mentoring. Many reviews focused on repetitive issues including formatting, style inconsistencies, and common implementation mistakes.
Slow Developer Onboarding
New developers required approximately 3–4 weeks to become productive due to fragmented documentation, inconsistent knowledge sharing, and the complexity of the existing codebase. Critical institutional knowledge often remained siloed within specific teams or individuals.
Inconsistent Test Coverage
Under tight delivery timelines, automated testing was frequently deprioritized. This resulted in uneven test coverage across services, increased regression risks, and higher engineering effort spent resolving production issues and bug fixes.
Requirements Misalignment
Product and engineering teams occasionally interpreted requirements differently, leading to multiple development iterations before features aligned with business expectations. The lack of a structured specification workflow contributed to avoidable rework and delivery delays.
Fragmented Documentation
Documentation across systems and services was often outdated or incomplete, making troubleshooting, onboarding, and cross-team collaboration more difficult as the organization scaled.
Why AWS Kiro
123RF selected AWS Kiro to modernize its software development workflow and improve engineering productivity across teams.
AI Assistance Within the Development Workflow
Kiro provides AI-assisted development capabilities directly within the IDE, minimizing context switching and enabling developers to remain focused throughout the development lifecycle.
Spec-Driven Development
Kiro’s spec-driven workflow encourages teams to define requirements, architecture, and implementation tasks before coding begins. This improved alignment between product and engineering teams while significantly reducing rework caused by requirement ambiguity.
Context-Aware Code Generation
Unlike generic AI coding assistants, Kiro leverages codebase awareness to generate suggestions aligned with 123RF’s architecture, coding patterns, and engineering conventions.
Built-In Automation and Governance
Agent hooks and automation workflows enabled the engineering organization to automate validations, enforce coding standards, and trigger quality checks throughout the development lifecycle.
Scalable Engineering Standards
Steering files allowed 123RF to codify engineering best practices, architectural decisions, and team standards in a reusable and scalable way, ensuring consistency as the organization continued to grow.
Outcomes Achieved
By adopting Kiro, 123RF significantly improved engineering efficiency,
software quality, and development consistency across teams.
Faster Feature Delivery
The spec-driven development model reduced requirement ambiguity and minimized rework cycles. Engineering teams were able to deliver features with fewer iterations and stronger alignment between product intent and implementation outcomes.
Reduced Code Review Burden
Automated pre-review checks allowed Kiro to identify common issues — including style violations, logical inconsistencies, and security concerns — before pull requests reached senior engineers. This enabled reviewers to focus on architecture, scalability, and strategic design decisions.
Improved Test Coverage
Automated test generation made comprehensive testing more practical within normal development workflows. Testing evolved from a separate, deprioritized activity into an integrated part of everyday engineering practices.
Faster Developer Onboarding
New engineers became productive in days instead of weeks by leveraging Kiro’s natural language capabilities to understand unfamiliar systems, services, and workflows more efficiently.
More Consistent Code Quality
Automated enforcement through agent hooks eliminated recurring style debates and improved consistency across engineering squads, regardless of team size or developer experience level.
How AWS Kiro Is Integrated Into the Development Workflow
Use Case | How Kiro Helps |
Feature Development | Spec-driven workflows (requirements → design → implementation tasks) improve alignment before development begins |
Code Generation | Developers describe intent in natural language while Kiro generates implementations aligned with existing architecture and conventions |
Code Review Assistance | Kiro performs automated pre-review checks for style issues, logical errors, and security concerns before human review |
Test Writing | Automated generation of unit, integration, and property-based tests for critical business logic |
Bug Investigation | AI-assisted analysis of stack traces, code paths, and likely root causes with remediation suggestions |
Documentation | Automatic generation of API documentation, architecture decision records, and inline technical documentation |
Developer Onboarding | New engineers use natural language queries to explore and understand unfamiliar parts of the codebase |
Infrastructure as Code | Assistance with Terraform modules, deployment configurations, and CI/CD pipeline definitions |
Quantifiable Business Benefits
Following the adoption of Kiro, 123RF achieved several measurable improvements:
- Developer onboarding time reduced from approximately 3–4 weeks to about 1 week
- Code review turnaround time reduced by approximately 50% through automated pre-review workflows
- Test coverage across critical services increased from approximately 45% to 75% without requiring dedicated testing sprints
- Boilerplate development tasks — including API endpoints, database models, and service integrations — reduced from hours to minutes
- Estimated 20–30% improvement in overall engineering velocity based on sprint delivery metrics
- Reduction in production incidents attributed to stronger automated testing and quality enforcement processes
Business Transformation and Future Innovation
Kiro fundamentally transformed how 123RF’s engineering teams operate.
By automating repetitive development tasks — including boilerplate generation, debugging assistance, documentation maintenance, and code quality enforcement — developers can focus more on solving business problems and building differentiated capabilities for customers worldwide.
The adoption of spec-driven development improved planning discipline and reduced costly implementation rework. As the engineering organization scales, Kiro continues to act as a force multiplier by maintaining consistency, accelerating onboarding, and reinforcing engineering standards across teams.
123RF is currently expanding Kiro adoption across all engineering squads while exploring deeper integration with CI/CD pipelines through agent hooks and workflow automation. The organization is also leveraging Kiro’s specification workflows for larger architectural initiatives where upfront design alignment delivers the greatest engineering and operational impact.
Customer Testimonial
“Kiro has become an essential part of how our engineering team operates. The spec-driven development approach alone has saved us countless hours of rework by ensuring we think through design decisions before implementation begins. Our developers ship faster, our code quality is more consistent, and new team members become productive much more quickly. It’s like giving every developer access to a senior engineering partner throughout the development lifecycle.”
AWS Partner Involvement
G-AsiaPacific Sdn Bhd worked closely with 123RF to introduce and operationalize Kiro across the engineering organization.
Their engagement included:
- Conducting hands-on enablement workshops with engineering squads
- Configuring steering files aligned with 123RF’s coding standards and architectural practices
- Establishing spec-driven development workflows tailored to the organization’s delivery cadence
- Supporting automation setup for agent hooks and engineering governance
- Providing ongoing advisory support and best practices to maximize developer productivity with Kiro
The collaboration helped accelerate adoption while ensuring Kiro was integrated effectively into existing engineering processes and workflows.
Level Up with Us
Looking to venture into the clouds?
Evolve your business with cloud technology today!