Bripes and ProRequests are now both part of Tarkle Portal. The product stays the same, including the workflows agencies use for service requests, work orders, approvals, payments, and client communication.prorequests+1
Nothing changes for your clients. Your branded portal still runs on your domain, so clients continue to see your brand, not Tarkle.
Why the change happened
Bripes and ProRequests were always built by Tarkle. They launched as separate brands because the product had a very specific focus, but running two brands meant duplicating roadmap decisions, infrastructure choices, and support effort.
Bringing everything under Tarkle means Portal now ships alongside Send and Studio. That gives the team one codebase, one direction, and a faster way to deliver updates.
What stays the same
Your portal workflows stay the same. The core experience for requests, deliverables, approvals, billing, and service delivery is unchanged.tarkle+1
Your login also stays the same. Customers who used Bripes or ProRequests can still log in at portal.tarkle.com with the same credentials they already had.
Your client-facing portal does not change brands on its own. The portal continues to live on your custom domain, so the experience remains white-label.tarkle+1
Pricing for existing customers
Existing customers keep their current pricing. Legacy pricing is honored until the customer cancels or upgrades, and the move to Tarkle Portal does not change that on its own.
That means customers who were on Bripes or ProRequests do not need to re-buy the product. They are simply moving to the new brand name and login surface.tarkle+1
What customers should do
If you were using Bripes, you should now think of it as Tarkle Portal. If you were using ProRequests, the same applies. The product, account, and client data stay in place under the new brand.