Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Tortoise Labs Panel - In House?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Tortoise Labs Panel - In House?

VPNshVPNsh Member, Host Rep

Hey guys,

Just wondering which panel tortoise labs are using for their server management and billing? I haven't seen it elsewhere so was wondering whether or not it's in house?

Thanks,
Liam

Comments

  • SpencerSpencer Member
    edited March 2014

    Its just solus and whmcs API, jk its custom.

    Thanked by 1eric1212
  • @Spencer said:
    It is just using whmcs and solus API

    That, with Bootstrap on top, basically.

  • chauffer said: That, with Bootstrap on top, basically.

    Yea I think it was an admin template he got on themeforest for like $20

  • iirc it's nulled solus with a custom theme and a couple features added from fiverr, not too shabby i guess.

    Thanked by 1Spencer
  • VPNshVPNsh Member, Host Rep
    edited March 2014

    Thanks @serverian - anywhere else using this?

    image

  • @liamwithers Yeah, they outsourced JS/HTML to ThemeForest and prettified Solus/WHMCS through their APIs, not too hard at all

    Thanked by 2Spencer manacit
  • Yeah, it's a WHMCS/Solus frontend made with Microsoft FrontPage and Adobe ColdFusion

  • @liamwithers: some components of our panel are open source, but the parts related to our core product are proprietary at this time.

    Thanked by 1VPNsh
  • jbilohjbiloh Administrator, Veteran

    @kaniini said:
    liamwithers: some components of our panel are open source, but the parts related to our core product are proprietary at this time.

    How long have you been in development?

  • @jbiloh said:
    How long have you been in development?

    ~1.5 years

  • @serverian said:
    ~1.5 years

    longer than that really, some of the concepts were concepts that were originally developed as part of the rapidxen platform.

    albeit these are radically redesigned in a lot of ways, for example, the original appliancekit was extended using python, which seemed to be the future at the time... the new appliancekit uses bytecode compiled from a JSON representation of nodes containing commands or templates to render. and, the new appliancekit can run on bare metal.

    there's also a different asynchronous queue method than the original rapidxen system, called Edia, which uses a signature scheme using shared secrets instead of XML document signing which is a complete design disaster.

    Thanked by 1VPNsh
Sign In or Register to comment.