Saasy - SaaS for Rails

January 5th, 2009

I’ve been working on an open source SaaS solution for Rails over Christmas called Saasy (pronouced “sarrsy” - using a posh voice).

Saasy provides:

  • Subscription management
  • Recurring billing
  • Credit card management
  • User authentication and SSO
  • Mailers for invoices etc

Saasy follows a componentised design. The idea is that you build your custom site, and then the generic authentication, account management and credit card management is split into a separate Rails app (Saasy) - a reusable component.

None of the credit card information is stored locally - but rather at a payment gateway. This greatly simplifies PCI DSS (formally known as CISP) compliance. However, you still have control over when the card is charged - rather than using some of the gateway specific subscription systems - which means you don’t have to worry about gateway callbacks.

Sassy also deals with authentication (both OpenID and credential based) - your main app can forward users to the Saasy SSO, and then they’ll get redirected back once they’ve been authenticated. This means you don’t have to bother generating and customizing authentication code - and also means you can use the same code for authenticating multiple sites (DRY).

Checkout the README on github for a full list of all the features and installation info.

Uncategorized | Comments | Trackback Jump to the top of this page

8 comments on “Saasy - SaaS for Rails”

  1. 01

    On the surface, looks pretty cool, and I got it up and running, but not without some trouble. A bit more documentation on the required gems to install and the *.sample.yml files to update (I missed application.yml and subscription.yml).

    Two questions I have:

    How do you intend for that first admin account to get established so you can start tweaking and managing the system?

    How does one “play” (or test, if you will) new account signups without tinkering with a real gateway?

    Michael at February 16th, 2009 around 12:13 am
    Jump to the top of this page

  2. 02

    The README contains instructions for copying the config files. What gems are needed that aren’t vendorized?

    There isn’t an ‘admin’ account - there’s no admin interface.

    This is mentioned in the README too, use the Braintree test gateway.

    maccman at February 17th, 2009 around 7:05 am
    Jump to the top of this page

  3. 03

    SaaSy looks good.

    Got as far as Signup with saasy but got this error message.

    “There were some errors setting up that account”

    Also getting this error:-
    “Identity url can’t be blank”

    Read Braintree requirements for card test number, verification and address rules - all seem OK.

    Any suggestions.

    ray at March 9th, 2009 around 4:55 pm
    Jump to the top of this page

  4. 04

    Try pulling from the git repo now - I’ve committed a few fixes. If that doesn’t work, let me know.

    maccman at March 10th, 2009 around 5:24 am
    Jump to the top of this page

  5. 05

    Thanks for the response on saasy.

    1. The latest git repo (10/03/2009)failed to run initially due to a missing folder “/log” in the GIT repo.

    2. Created new “/log” folder and created an empty development log in the folder.

    3. Saasy now running OK on server.

    4. Signup now working OK. Used braintree recommended test (a) credit card number and (b) CVV verification code defaults from their developer test site.

    http://dev.braintreepaymentsolutions.com/test-transaction/

    5. Got the email activation url from the development log and pasted into the browser address - worked.

    6. login now working OK.

    7. auth_code was registered in the subscriptions table from the default gateway (braintree in config/subscriptions.yml) indicating successful communications with the credit card gateway on signup.

    8. Now to integrate saasy with my existing Rails App! The fun begins!

    Thanks again.
    Ray

    ray at March 10th, 2009 around 2:18 pm
    Jump to the top of this page

  6. 06

    Love saasy! Thanks for contribution.

    A brief question:). Is saasy held separately or within the main rails app, i.e. within the vendor/plugins, or can it be in any place on the server as long as the main app is able to access saasy?

    Thanks,

    Alex

    Alex at March 23rd, 2009 around 3:17 pm
    Jump to the top of this page

  7. 07

    Alex:

    It’s held separately in another Rails app - although you can share the same DB if necessary.

    maccman at March 31st, 2009 around 10:59 am
    Jump to the top of this page

  8. 08

    its very useful for sso integration
    – i feel that more documentation needed for complete understanding
    for me :
    1. when i add new user under one account in saasy app, i want to add the same in my app db will it be possible or give me any alternetive

    2. when use the saasy for multiple applications ( each app will have it’s own lay-out and style ) i want the saasy should open in the same(Myapp) lay-out and styles.

    3. when i log-out from Myapp it logged out and shows the login screen in saasy - from here how can i come back to myapp

    please provide help docs this will be great help

    Thanks for your kind effort on saasy

    venkat at April 29th, 2009 around 7:33 am
    Jump to the top of this page

Leave a Reply

  •  
  •  
  •  

You can keep track of new comments to this post with the comments feed.

19yr old hacking away at Ruby on Rails and Flex

Pages

Meta