We have a non-membership WordPress + vBulletin site to which we are currently adding a Web app that will allow members to make their own pages, sort of a MySpace idea. We need member signup and payment capability, plus we'd like the WordPress and vBulletin integration. But our Web app has tables to hold member's app specific settings, and the various personal data that they input to create their own pages. Is a Member appropriate for such a site? The app needs to know who is signed in, in order to give them access to editing their own area of the site. Would this require extra development on our part? Can it be done? And how much work would it be? In other words, would it be less work for our developers to implement payment from scratch, using the various open source code out there for that, or to use aMember and implement our app integration? Another question: In signing up for this forum to ask this question, I see that you are using aMember for the vBulletin registration. Nice, eating your own dog food. However, the signup was extremely slow. The confirmation page from the e-mail confirmation link took forever to appear, and after logging in, the account page also took a long time. I'll try registering with an different e-mail later, but are there performance problems with aMember?