Home / Companies / Port / Blog / Post Details
Content Deep Dive

How SPS Commerce built an AI Software Factory on Port

Blog post from Port

Post Details
Company
Date Published
Author
Zohar Einy
Word Count
1,490
Company Posts That Month
6
Language
English
Hacker News Points
-
Post removed?
No
Summary

SPS Commerce, which operates a retail network connecting about 50,000 companies and supports more than 3,000 services, built an AI software factory using Port to connect previously isolated coding, planning, and migration agents with existing developer tools and governance processes. Its first agentic workflow begins when a developer labels a Jira ticket, after which a planning agent creates an implementation plan using shared context from Port, developers approve the plan, a coding agent produces code and opens a GitHub pull request, and developers review and merge the result. Port integrates context from Jira, Azure DevOps, Kubernetes, and other systems while providing orchestration, status reporting through Slack and dashboards, feedback collection, and approval checkpoints. In its first four months, the workflow processed more than 500 tickets and roughly 400 story points with no related incidents, while over half of participating developers described it as helpful. SPS plans to extend this human-reviewed agentic model to further stages and use cases across its software development lifecycle.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Developer Experience 3 No monthly metrics for this publish month.
Platform Engineering 3 No monthly metrics for this publish month.
AI Agents 2 No monthly metrics for this publish month.
AI Coding Assistant 1 No monthly metrics for this publish month.
Kubernetes 1 No monthly metrics for this publish month.
MCP 1 No monthly metrics for this publish month.
Real-time 1 No monthly metrics for this publish month.
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.