Opportunities › GraphQL Federation management and routing › Proposed app
Seamwork
Review and approve schema changes across federated GraphQL services
- Score
- 48
- confidence 46
- Evidence
- 4
- items on the page
- Rivals
- 1
- named in sources
- First version
- 45 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2019
- Established market · AI estimate
ScreensConcept
Desktop app: Schema review, composition checks, and GraphQL API governance require sustained focus on complex technical details at a workstation. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Change review
Waiting for sign-off2 breaking
About this appAI proposal
Seamwork is a schema review and change-tracking workspace for teams that run a federated GraphQL API across several services. Each team publishes its subgraph, Seamwork composes the supergraph, and every proposed change is checked and shown to the people it affects.
It is built for platform and API teams in companies with a microservices architecture who want to manage federation without tying their workflow to one proprietary platform. Schemas stay in your repositories; you can export composed output and use it with the gateway you already run.
What is different: review comes first. Changes get a plain-language diff, a list of affected clients and owning teams, and a sign-off step, so schema evolution becomes a conversation instead of a surprise.
- Tagline
- See what a schema change breaks before it ships.
- Voice
- PlainPreciseCalm
- Why this name
- A seam is where separately built pieces join. Federated schemas have seams between teams; the product keeps them clean. Two plain words joined.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Supergraph composition checks
Submit a subgraph schema and see whether the supergraph still composes, with errors tied to the exact field and owning team.
No member yet
Plain-language change diffs
Every schema change is summarized as added, changed or breaking, so reviewers who are not schema experts can follow it.
No member yet
Owner sign-off workflow
Changes that touch another team's types ask that team to approve before the change is marked ready to merge.
No member yet
Client impact view
Upload operation lists from clients and see which of them use a field you plan to remove or change.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#0F4C5CDeep Teal · primary#F6F3ECPaper · surface#1B2326Ink · text#E09F3ESignal Amber · accent#3E8E5AFern · data: safe#B5412FBrick · data: breaking
Typography
Aa
Seamwork
PricingAI proposal
The material gives no competitor prices. These tiers are a starting point to test, not a claim about what Apollo Studio or GraphOS charge.
Free
Free
- 1 project
- Up to 3 subgraphs
- Composition checks
- Plain-language diffs
Team
$49 a month
- Up to 15 subgraphs
- Owner sign-off workflow
- Client impact view
- CI check endpoint
- 10 members
Business
$199 a month
- Unlimited subgraphs
- Unlimited members
- Audit history
- Priority support
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- Users invite others. A platform lead invites subgraph owners from other teams to publish schemas, review changes and sign off. Each team that owns a subgraph needs an account to take part in reviews.
- Do they become customers?
- Invitees are engineers at the same company who can become seat-paying users or push for a team plan. To test: how many invited owners go on to create their own project or request an upgrade.
- First customers
- Platform engineering leads at companies of 100 to 500 staff that run five to fifteen GraphQL subgraphs and pay for, or are weighing, a commercial federation platform.
- Where to reach them
- GraphQL community forums: Answer federation review questions in GraphQL Slack and Discord groups, and share a free schema diff checker as an entry point.
- Technical blog posts: Publish guides on safe schema evolution across teams, with sample reviews built in the product.
- Direct outreach: Message platform leads at companies that list GraphQL federation in job posts and offer a migration walkthrough.
- First milestone
- Five teams run schema checks in CI for 30 days, and two of them pay for a team plan.
Why people already pay for this
- VerifiedGitHub repository gained 1272 stars in 1142 days
- Public claimA market exists for GraphQL Federation tools with paying customers, as Apollo Studio and GraphOS are commercial products from Apollo that teams adopt.
- Public claimGraphQL Federation is an active development practice requiring tooling for multiple distributed services to work together.
- AI inferenceThe repository shows significant adoption with 1,272 stars and 257 forks, indicating developer interest in an alternative to commercial solutions.
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Schema compositionOpen-source federation composition libraryComposition must follow the federation spec, so reuse a maintained library instead of writing one.
- This app · Background jobsQueue worker for schema checksComposition and diff checks can run long and should not block web requests.
RisksAI inference
- CommercialOpen-source alternatives to Apollo already exist, so teams may self-host a free tool. Seamwork must prove that review workflow, not composition alone, is worth paying for.
- TechnicalComposition must match the federation spec exactly. Any difference from the gateway a team runs would give false passes or false failures and lose trust.
- DataClient operation lists are needed for impact checks, and teams must be willing to upload them. Some will see this as too sensitive or too much work.
- PlatformFederation specs and gateway behavior are controlled by others and may change, forcing ongoing updates.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.