<p><a href="https://ripple.com/wiki/Gateway_Integration_Manual" rel="noreferrer">The documentation</a> does assume you will run a local server. But anyone can build a gateway, with or without the server. To operate a gateway, you really only need to be able to process transactions just like a client does. When a transaction happens you need to know. When you need to perform a transaction, you need to perform it.</p>

<p>Probably the easiest way to do it is to implement the gateway's interface to the Ripple network using JavaScript and node.js -- this lets you use <a href="https://github.com/rippleFoundation/ripple-lib" rel="noreferrer">ripple-lib</a> which is a supported, open source interface to the Ripple network.</p>

<p>If you do decide to run your own server, nothing really needs to change. Just point your gateway interface to your local server instead of the public server pool.</p>

<p>Whatever you do, please don't send your secrets to the public server pool. If you use ripple-lib, make sure local signing is on. If you use anything else, use ripple-lib's <code>rsign.js</code> program to sign transactions for you.</p>

CC BY-SA 3.0
2013-06-11T05:10:30.440Z
2013-06-11T05:10:30.440Z
David Schwartz
<p>If you are not connected to a trusted rippld server then you must make sure all your transactions are signed with your account secret key before submitted them to a public or untrusted rippld server for propagation on the network.</p>

CC BY-SA 3.0
2013-11-19T23:00:14.743Z
2013-11-19T23:00:14.743Z
Steven Zeiler
<p>I've noticed that several Ripple gateways now exist, most notably Bitstamp. However, the only documentation I can find on how to create an automated gateway seems to imply that you must have OpenCoin's <a href="https://github.com/ripple/rippled" rel="nofollow">rippled program</a>.</p>

<p>Can anyone build a Ripple Gateway, or is this ability limited to OpenCoin's inner circle?</p>

CC BY-SA 3.0
2013-06-11T03:30:42.687Z
https://ripple.com/wiki/RPC_API simple gateways don't need a local rippled
dchapes
CC BY-SA 3.0
2013-11-12T14:21:19.263Z
See also: [How to create a ripple gateway?](http://bitcoin.stackexchange.com/questions/10489/how-to-create-a-ripple-gateway)
dchapes
CC BY-SA 3.0
2015-06-21T15:22:09.017Z
rippled is open source now: https://github.com/ripple/rippled
Nick ODell
<ripple><ripple-gateways><ripple-api>
How do you build a Ripple gateway without rippled?
user5513
# How do you build a Ripple gateway without rippled?

(Asked by: username_0 on 2013-06-11)

I've noticed that several Ripple gateways now exist, most notably Bitstamp. However, the only documentation I can find on how to create an automated gateway seems to imply that you must have OpenCoin's [rippled program](https://github.com/ripple/rippled).

Can anyone build a Ripple Gateway, or is this ability limited to OpenCoin's inner circle?

**Tags:** ripple, ripple-gateways, ripple-api

> **Comments:**
> **username_1**: https://ripple.com/wiki/RPC_API simple gateways don't need a local rippled  
> **username_1**: See also: [How to create a ripple gateway?](http://bitcoin.stackexchange.com/questions/10489/how-to-create-a-ripple-gateway)  
> **username_2**: rippled is open source now: https://github.com/ripple/rippled  

---

## 2 answers

### Answer by username_3 on 2013-06-11. Score: 5

[The documentation](https://ripple.com/wiki/Gateway_Integration_Manual) does assume you will run a local server. But anyone can build a gateway, with or without the server. To operate a gateway, you really only need to be able to process transactions just like a client does. When a transaction happens you need to know. When you need to perform a transaction, you need to perform it.

Probably the easiest way to do it is to implement the gateway's interface to the Ripple network using JavaScript and node.js -- this lets you use [ripple-lib](https://github.com/rippleFoundation/ripple-lib) which is a supported, open source interface to the Ripple network.

If you do decide to run your own server, nothing really needs to change. Just point your gateway interface to your local server instead of the public server pool.

Whatever you do, please don't send your secrets to the public server pool. If you use ripple-lib, make sure local signing is on. If you use anything else, use ripple-lib's `rsign.js` program to sign transactions for you.


---

### Answer by username_4 on 2013-11-19. Score: 0

If you are not connected to a trusted rippld server then you must make sure all your transactions are signed with your account secret key before submitted them to a public or untrusted rippld server for propagation on the network.


---

