When you’re looking for a new system, you’ll probably draw up a list of what you need. You’ll have a list of functional requirements, you’ll want to know about security, support, and about the supplier. And you’ll want to know about the cost.

We have always tried hard to be really transparent about all these things. Our pricing has always been public, and isn’t something we negotiate about (so you don’t have the suspicion that you’re subsidising a better negotiator). We have various factsheets on our website or this blog which try and answer the questions you might have about us and the product. And we really like doing walkthroughs so that you get to see an actual system, and have a chance to actually use it, so that you know what you’ll be getting before you commit. And there are often questions or further conversations we’ll have to ensure that you’re happy.

Sometimes we’re asked to complete a formal tender document to support your decision making process. For may years now our policy has been not to do so. Our experience was that it was an awful lot of work for us, and that the organisations requesting tenders really wanted a much more expensive custom built system. And although it might seem free to you, you are of course paying at some point for the production of all that documentation and making presentations. Suppliers don’t have spare money around to do this: it all comes from the price you eventually pay.

So if you do want to go through a formal tendering process, and you do want Lamplight on your list, we’d ask that you:
1. look at the pricing page of our website, and read some of the other documents that might answer your questions. Tick them off your specification sheet.
2. book a walkthrough. Have your specification open as you do it, and tick off the functional requirements as you see them. Ask us to show you things if we don’t cover them.
3. ask us other questions that haven’t already been covered, either during the walkthrough or afterwards to address any other issues.

This should provide you with all the information you need to make an informed decision, and you’ll be doing so on the basis of functionality you’ve actually seen, and had a chance to use.

For all system administrators – we have put together a new handbook showing how to use your system admin powers effectively! It includes advice and instructions on how to delete an old database operators, insert new custom fields in profiles and activity records, set up a report template, merge duplicate profiles – and much more!  Why not download your copy here and have a browse…

We will shortly be moving existing customers to Amazon Web Services (AWS) servers, and new customers will be hosted on AWS too.  Some questions you may have:

Why are you moving?

AWS offers a more scalable and resilient setup than we can deliver on our existing host.  Because AWS provide this platform at such a large scale they are able to invest in technologies that take care of some of the hard server problems, so that we don’t need to.  Hosting on AWS should improve the resilience and performance of Lamplight – it’ll be quicker and less likely to experience server problems.

Where will our data be?

In London (UK!).  We are using the AWS London region exclusively.

What will it cost us?

Nothing.  The hosting charges will not change as a result of the move, and there is no charge to transfer you to the new servers.

Is it secure?

Yes, and in some ways more secure than at present.  As currently, databases and files are encrypted at rest and in transit.  Servers exist in private networks that are inaccessible from the internet.  Security features already present will continue.  Amazon do not access your data.

Snapshot backups of databases are automatically taken nightly, encrypted, and multiple copies stored on Amazon S3 storage.  These can be restored quickly if needed.  File storage also uses S3 and multiple copies are automatically created and stored to ensure high availability.

What will change?

Two things.

  1. The web address will change to https://lamplight.online, and your login at https://www.lamplight3.info will no longer work.  Your existing username and password will continue to work on the new server.
  2. You will not be able to send emails out directly using the Lamplight servers.  The only emails we can send are passwords for operators.  For other email you will need to either
    1. Link Lamplight to your own email server
    2. Use Mailchimp

This Setting up Email Accounts document will explain what settings you need, and how to enter them into Lamplight.

If you use the publishing module you will need to update your implementation when the changeover happens, to use https://lamplight.online instead of https://www.lamplight3.info.

Why to I need to set up email to send sms?

To send sms messages we link up with a company called 24x, who send the text messages.  To get them to 24x, your sms messages are sent by email, and are then transformed into text messages by 24x.  So to send sms messages from the AWS servers, you’ll need working email.

By way of analogy, imagine you want to send a postcard to a lighthouse keeper.  Now the postman won’t row a boat out to the lighthouse to deliver it directly.  So instead, you write your postcard, put it in an envelope, and add a little note asking the lighthouse keeper’s wife (who lives in the cottage on the shore) to pass it on to the lighthouse keeper.  She gets the letter, reads the note, and pops the postcard in the lunchbox and sends it over to the lighthouse keeper.

So the postcard is our text message; the envelope is the email; and the lighthouse keeper’s wife is 24x.

(Update on sending sms – 9/11/2017)

We’ve made some changes to the way Lamplight sends text messages and you no longer need email set up to send sms messages.  Messages are now routed to 24x directly.

When will the change happen?

We can schedule that to suit you.  There will be a short period of downtime (ranging from a few minutes to a couple of hours for customers with large volumes of files and data).  System administrators will soon see a screen when they log in asking them to accept the change to the hosting agreement (as our previous host, Elastichosts, are referenced in it), and asking when they would like to schedule the move.

How long will it take to move our data?

The process is fully automated and typically takes a few minutes.  Customers with large volumes of data will take a little longer, but it won’t be more than a couple of hours.

Do I have to sign anything?

No.  You can confirm your acceptance of the changeover using the tickboxes that admins will see when they log in to their current system.  You will be emailed a Hosting Agreement Amendment for your records.

Why is my question not answered here?

Because we didn’t anticipate it! Please Contact Us and we’ll update this page with other Q&As.