Build Cost Estimation Service with Predictive Billing Calculation for Template Complexity

[temma02]

Description

apps/backend/src/services/billing/cost-estimation.service.ts exists but only estimates costs based on tier. Add template complexity scoring that factors in: number of Soroban contract invocations, enabled features, and estimated Vercel compute usage to produce a per-deployment cost prediction.

Requirements and Context

• Complexity score: base cost + N × soroban_invocation_cost + M × feature_cost
• Expose the estimate via GET /api/deployments/[id]/estimate-cost
• Estimate must update in real-time as the user changes customization options
• Accuracy target: within 10% of actual Stripe charge on billing reconciliation

Suggested Execution

Branch: feat/deployment-cost-estimation-complexity

Implement Changes

• Extend cost-estimation.service.ts with a template complexity scoring function
• Add the /api/deployments/[id]/estimate-cost route
• Implement real-time re-estimation on customization config change via the preview update endpoint
• Add tests for complexity scoring accuracy against known billing outcomes

Test and Commit

Run pnpm test -- cost-estimation and confirm estimate accuracy is within 10% for test fixtures.

Example Commit Message

feat(billing): add template complexity scoring to cost estimation service

Co-authored-by: <your-name>

Guidelines

• Branch off main, keep PRs focused on one issue
• All new code must include unit or integration tests
• Ensure pnpm lint and pnpm typecheck pass before review
• Link this issue in your PR description
• Request review from at least one maintainer before merging

[Chideraakude]

@Chideraakude has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello,
I would love to help resolve this issue. Please assign to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Chideraakude to this issue.

[OkonkwoEmeka]

@OkonkwoEmeka has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer, I’d like to work on this issue.

I understand the current cost estimation service only estimates by tier, and the goal is to make it smarter by factoring in template complexity — Soroban contract invocations, enabled features, and expected Vercel compute usage.

My approach would be to extend "cost-estimation.service.ts" with a clear complexity scoring function, expose the result through "GET /api/deployments/[id]/estimate-cost", and make sure estimates refresh when customization options change through the preview update flow.

I’ll also add tests using known billing fixtures to check the scoring logic and confirm the estimate stays within the expected 10% accuracy target.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @OkonkwoEmeka to this issue.

[drips-wave]

Congratulations, @Chideraakude! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Chideraakude: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊