# SecAgg example update

**URL:** <https://discuss.flower.ai/t/secagg-example-update/1214>\
**Category:** Flower Help - Intermediate\
**Created:** [March 2, 2026, 4:26pm UTC](https://discuss.flower.ai/t/secagg-example-update/1214 "2026-03-02T16:26:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![chongshenng](https://dub1.discourse-cdn.com/flex013/user_avatar/discuss.flower.ai/chongshenng/32/153_2.png) [@chongshenng](https://discuss.flower.ai/u/chongshenng)\
**Post date:** [March 2, 2026, 4:26pm UTC](https://discuss.flower.ai/t/secagg-example-update/1214/1 "2026-03-02T16:26:56Z")

</div>

> [@](#):
>
> [**View in #questions on Slack**](https://slack.com/archives/C01RM6LMKQA/p1763378849781389)
> 
> ![Valerio_Bonsignori](https://europe1.discourse-cdn.com/flex013/uploads/flower/original/1X/c45b245994f424cabaf3b24570a932e896fa4071.png) **@Valerio\_Bonsignori:** Hello, I have seen that for the SecureAggregation there is the example/tutorial in the Github. The Client side _implementation_ is straight forward (I need to `from flwr.client.mod import secagg_mod` and using as mod in the ClientApp constructor. But the example uses the (new?) Flow structure for the server implementation, and it is not easy to plug it in my implementation.  
> There is a simpler way to include Sec Agg server side as well ?
> 
> ![Chong_Shen](https://europe1.discourse-cdn.com/flex013/uploads/flower/original/1X/35ad3d046e9b5591f46842633a53d2d629f7ec99.png) **@Chong\_Shen:** Hello @Valerio\_Bonsignori, our [SecAgg example](https://github.com/adap/flower/tree/main/examples/flower-secure-aggregation) actually uses the older approach based on `Strategy` and `NumpyClient`, and our recommended way to build your Flower apps is to use our [Message API](https://flower.ai/docs/framework/how-to-upgrade-to-message-api.html). One way to create a custom server implementation is to adapt the existing strategies like how is done in the advanced PyTorch example [strategy](https://github.com/adap/flower/blob/main/examples/advanced-pytorch/pytorch_example/strategy.py).
> 
> Perhaps if you can share a bit of your implementation, I can provide more detailed explanations?
> 
> > Flower: Upgrade to Message API
> 
> ![Valerio_Bonsignori](https://europe1.discourse-cdn.com/flex013/uploads/flower/original/1X/c45b245994f424cabaf3b24570a932e896fa4071.png) **@Valerio\_Bonsignori:** Hello @Chong\_Shen sorry for the late reply, I wasn’t expecting anymore a reply. I am implementing a one-shot (round) FL application: client local parameter definition, sent to the server. The server aggregates and send them back. It have been easy to do such, using the “flwr[simulation]\>=1.18.0”, version. The example of SecAgg that you pointed [SecAgg Example](https://github.com/adap/flower/tree/main/examples/flower-secure-aggregation) is indeed using the old version but, even in that case, I find the server “workflow” kind of object and not a simpler “plug and play” modifier for the server (as it is instead for the client). Am I missing another different API designing phase between the Server/Client apps and the new version with pure messages?