Two ways to win
with integrations.
Ship the integrations your customers ask for as a feature, or embed Specc as the infrastructure your whole platform connects through.
Track A
Ship integrations as a feature
Say yes to the integrations your customers ask for. Build one or activate a ready workflow, and the runtime runs the version you deploy.
No dev sprint
Specc builds each integration from a description.
Self heal
Investigates failed runs and proposes fixes for you to approve.
Track B
Embed the infrastructure
“Stripe for connections.” Embed Specc inside your platform under your brand. Your customers connect natively, and you earn a revenue share on every connection.
White-label embed
Customers never see Specc.
Revenue share
Earn on every active connection.
The infrastructure under the connection market.
Like Stripe for payments or Twilio for messaging. Build your product on Specc, and the switching cost compounds over time through history, trust, and volume.
Embedded hub · your brand
Versioned
every change, deployed when you choose
0 exits
customers stay in-platform
Rev share
on every connection
FAQ
Can I start with Track A and move to Track B?
Yes. Ship integrations first, embed the infrastructure later.
Is the AI in production?
Not in the runtime. Each run follows the deployed specification. AI builds and changes integrations, and with Self heal enabled it investigates failed runs and proposes fixes for you to approve.
How does revenue share work?
Flat fee to embed plus a commission split on usage.