One switch takes a release live across Guidewire and digital.
FTF, the Feature Toggles Framework, is built around how InsuranceSuite teams release. Finished work goes live in PolicyCenter, BillingCenter, ClaimCenter and your digital channels the day the business is ready, and each feature keeps its own kill switch, so one that misbehaves can be stopped for new work in seconds.
Works on its own, or in front of the LaunchDarkly or ConfigCat account you already have.
The FTF service runs today. The Guidewire integration is fully designed, and we're looking for a Guidewire customer or SI partner to build and prove it with us.
Still merging long-lived project branches before every release? Here's the case for trunk-based development and feature toggles →
Built around how InsuranceSuite teams release
FTF's model comes from core insurance delivery: long test cycles, several systems going live together, and data that can't be rolled back.
Policy, billing, claims and digital, together
A product change usually touches several systems. One release switch takes them live at the same moment, and a feature stays off in any application that hasn't built it yet.
Stop a feature, not the release
Switching a feature off stops new work from using it in seconds, with no redeploy. Records already created with it, such as a policy, a claim or an exposure, stay; the toggle decides how they are processed from then on. Data model, typelist and API schema changes can't be toggled; they ship ahead in small, compatible steps. How
Native to your configuration
The FTF GW client is a small footprint of Gosu code, data model and APIs, reviewed, versioned and upgraded like the rest of your configuration, on any Java or JavaScript version your Guidewire release uses.
For every Guidewire customer, not only the newest
The FTF GW client is plain Gosu plus one HTTP call, so it isn't tied to any Java or JavaScript version. It runs wherever your Guidewire version runs, on Guidewire Cloud, on your own infrastructure, or on a long-standing version 8 installation.
- Guidewire CloudInsuranceSuite on Guidewire's cloud
- On-premSelf-managed, in your data centre or your own cloud
- Version 8 and upEstablished installations included
Start with one application. Grow to every application you run.
The same toggles and the same code at every step. Link your applications into releases that go live together, or simply give each one the same, consistent way to switch features.
-
Step 1
Standalone app
One Guidewire application with its own toggles and console. No FTF service to run.
Guidewire client: designed -
Step 2
Integrated apps
PolicyCenter, BillingCenter and ClaimCenter on one FTF, with releases across them and promotion to production.
Guidewire client: designed -
Step 3
Every OFREP-compliant app
Portals, digital channels and services in any language join the same FTF through OpenFeature. One release can span them all.
Available now
Why not just LaunchDarkly or ConfigCat?
They're good at the switch itself. FTF adds what an insurer's delivery needs around it, and it can sit in front of the account you already have.
- Keep your vendor, or leave itFTF works on its own, or in front of the LaunchDarkly or ConfigCat account you already have. Your applications talk only to FTF, so moving between them, or to FTF on its own, changes nothing in them.
- Native to GuidewireA small Gosu client (code, data model and APIs) that your team maintains like the rest of the configuration, built for how InsuranceSuite evaluates and releases.
- One release across applicationsOne switch takes a product change live in PolicyCenter, BillingCenter, ClaimCenter and digital, and each feature keeps its own kill switch.
- Promotion, not re-entrySettings move from test to UAT to production with a preview. Nothing is retyped by hand, so environments don't drift apart.
- The open standard, built inAny other service evaluates through OpenFeature's remote evaluation protocol (OFREP), with no vendor SDK and no proxy to host.
What runs today, and what needs a partner
FTF service Available now
- Toggles, releases across applications, and business attributes such as brand, state and claim amount
- Promotion from test to production with a preview
- OpenFeature (OFREP) for Java, .NET, Go, Python, Node and browser apps
- On its own, or in front of your LaunchDarkly or ConfigCat account
- Your identity provider decides who switches what
Guidewire client Designed
- A small footprint of native Gosu code, data model and APIs
- Designed for Guidewire Cloud, on-prem, and version 8 and up
- One Gosu call, evaluated in-process from the application's own copy
- Keeps answering if FTF can't be reached
- Toggle and release screens in the application's admin area
- The same answers as every other FTF client, held to one shared set of test cases
- Read the full design →
Design partners wanted
We're looking for one or two Guidewire customers or SI partners to build the Guidewire client with, on a real InsuranceSuite release.
Who we're looking for
- A Guidewire customer
- Or a Guidewire SI partner
What you get
- A Guidewire client shaped around your products and versions
- The FTF service for your environments during the partnership
- Founding-partner terms afterwards
What we need from you
- Access to an InsuranceSuite development environment
- A Guidewire developer or architect to work with
- A release to try it on
Who's behind FTF
Alex Zak has been a Guidewire architect for 18 years, across PolicyCenter, BillingCenter, ClaimCenter and digital. He works independently as founding director of PNT Computer Consultants Pty Ltd in Sydney.
Feature toggles aren't a new idea; Alex first worked with them for InsuranceSuite on a client project. FTF, a feature toggle product for Guidewire customers, is his own, grown into a standalone, OFREP-compliant toggle service for every platform an insurer runs.
Talk to us
About becoming a design partner, a trial, or your release process. Or email info@pntnet.au.