Hi Joe,
Yes Hystrix is intended for use on the consumer side. Applications in distributed systems are often both producers and consumers, so it's not about the app being a "client" or "server" but about isolating a function being invoked that is accessing functionality that may be faulty or latent. Typically this means it's on the consumer end of a network call.
Whether the HystrixCommand is coded by the consumer, or delivered by the producer in a client library does not matter, it is invoked on the client-side of the RPC relationship.
If this general response does not answer the question, please elaborate with examples of what you meant by your question and I'll try again.
Ben