As @estus said, Redux and recompose are not equivalent.
As you maybe know, Redux is only for keeping the state of the app, thats means when you consume a service and get a response, modify the value of some UI component, etc, an action is dispatched and through the reducer it updates the state of the app in the store. Then, the UI component which is subscribed to the store is re-rendered.
On the other hand, Recompose allows you to enhance functional components.
For example, add custom props, add lifecycle and also state and handlers to functional components.
Additionally, the recompose philosopy is to keep the components as thin as possible and split it to separate the responsabilities, then compose it with enhancers.
It makes sense because you can reuse repetitive logic in different components.
Here an example without using Recompose
Here the same using Recompose
As a conclusion, I'd say that you can use Redux for keeping the state and Recompose to keep it simple, separating the responsabilities, having functional components enhanced by little enhancers which encapsulate specific logic.
In future version of React, I think most utilities of Recompose could be added to the library.