Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

inmn's avatar
Level 2

Would you heavily modify Spark, or, Roll your Own?

We have a need for features Spark doesnt offer, like:

Not attaching Payment Details to a User

Not attaching Team levels to a User

Using Custom Team Levels for Subscriptions setup by Team admins

Allowing Members of Teams without subscriptions, yet tracking a members active subscription status

Allowing Teams to manage Offline Payments for Invoices

Allowing Teams to create sub-teams, and manage billing subscription plans

Spark can do it all except attaching a TEAM level to a User's CC; but when we want to extend into other areas, it starts becoming convoluted.

So my question is.. Would you User Spark,. make CustomSparkClasses that extend spark, and do what you can to allow offline payments, etc,

OR

Just make your own?

I know we can always purchase spark then rob the code examples / fork it; etc.

That $99-300 is not an issue. I dont want to waste money on MVP dev if we can extend it, but if you guys think it will be a nightmare to extend it, then its likely worth the 40-80 hours to build/clone a lot of this functionality into our own app.

0 likes
2 replies
ejdelmonico's avatar

Make your with Cashier. All that modification seems like a heck of a lot of technical debt. Besides, Spark is built on top of Cashier. You could probably find plenty of articles on it.

1 like
inmn's avatar
Level 2

Cashier still attaches payments to users, but it seems easier to extend than spark

Please or to participate in this conversation.